Dsod problem + computer der brummer og crasher
I januar kom der en blå skærm på min computer og den genstartede osv. Siden da har jeg oplevet rigtig mange gange at den crasher uden blå skærm, men ved at den brummer højt og skærmen enten bliver sort eller flimrer. Det sker ofte når jeg flytter på computeren.Jeg har prøvet at læse minidumb-filen, fra den blåskærm, gennem et windows debugging program, men jeg ved ikke helt, hvad det den siger betyder. Jeg har downloadet symbolerne, men det ser ikke ud til at den kan læse dem ordentligt.
Jeg har overvejet at geninstallere Windows 7 eller sende den til forhandleren så de kan kigge på den, men vil egentlig helst selv, da det andet tager tid.
Er der nogen der kan hjælpe mig med at læse minidumb-filen? Og er det, det der er galt med den eller er det noget helt andet?
Min computer er:
HP notebook G62
AMD Turion(tm) II P520 Dual-Core Processor 2.30 GHZ
RAM: 4GB
Jeg har Windows 7 Home Premium SP1
Den er ca. 8 måneder gammel.
Mit debugging program siger dette:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Kirstine\Desktop\040111-16863-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\Symbols;.sympath SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02c4a000 PsLoadedModuleList = 0xfffff800`02e8fe90
Debug session time: Fri Apr 1 19:14:23.604 2011 (UTC + 2:00)
System Uptime: 1 days 7:34:22.009
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 4E, {7, aecdc, 1, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+80640 )
