NIEBIESKI EKRAN
Witam. ostatnimi c zasy gdy coś robie na kompie samoczynnie wyskakuje mi niebieski ekran z treścią, coś tam że trzeba go natychmiast wyłączyć ażeby się nie zepsół, kluczowe info dla ludzi którzy by mi mogli pomóc to:
STOP:0X0000007F(0X0000000D),0X000000000,0X00000000,0X00000000
PROSZE O POMOC!!!
Odpowiedzi: 1
Strona 1 / 1
<font size="1"><p>POMOCY po raz kolenjy bez zadnych przyczyn i zadnych nowycj instalek system, sam sie zresetowal....</p><p> </p><p> </p><p>Microsoft (R) Windows Debugger Version 6.6.0007.5<br />Copyright (c) Microsoft Corporation. All rights reserved.</p><p><br />Loading Dump File [P:\ANIA\Mini102406-02.dmp]<br />Mini Kernel Dump File: Only registers and stack trace are available</p><p>Symbol search path is: *** Invalid ***<br />****************************************************************************<br />* Symbol loading may be unreliable without a symbol search path. *<br />* Use .symfix to have the debugger choose a symbol path. *<br />* After setting your symbol path, use .reload to refresh symbol locations. *<br />****************************************************************************<br />Executable search path is: <br />*********************************************************************<br />* Symbols can not be loaded because symbol path is not initialized. *<br />* *<br />* The Symbol Path can be set by: *<br />* using the _NT_SYMBOL_PATH environment variable. *<br />* using the -y <symbol_path> argument when starting the debugger. *<br />* using .sympath and .sympath+ *<br />*********************************************************************<br />Unable to load image ntoskrnl.exe, Win32 error 2<br />*** WARNING: Unable to verify timestamp for ntoskrnl.exe<br />*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe<br />Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible<br />Product: WinNt, suite: TerminalServer SingleUserTS<br />Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420<br />Debug session time: Tue Oct 24 15:08:12.484 2006 (GMT+2)<br />System Uptime: 0 days 3:53:39.031<br />*********************************************************************<br />* Symbols can not be loaded because symbol path is not initialized. *<br />* *<br />* The Symbol Path can be set by: *<br />* using the _NT_SYMBOL_PATH environment variable. *<br />* using the -y <symbol_path> argument when starting the debugger. *<br />* using .sympath and .sympath+ *<br />*********************************************************************<br />Unable to load image ntoskrnl.exe, Win32 error 2<br />*** WARNING: Unable to verify timestamp for ntoskrnl.exe<br />*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe<br />Loading Kernel Symbols<br />..................................................................................................................<br />Loading User Symbols<br />Loading unloaded module list<br />...........<br />Unable to load image kl1.sys, Win32 error 2<br />*** WARNING: Unable to verify timestamp for kl1.sys<br />*** ERROR: Module load completed but symbols could not be loaded for kl1.sys<br />*******************************************************************************<br />* *<br />* Bugcheck Analysis *<br />* *<br />*******************************************************************************</p><p>Use !analyze -v to get detailed debugging information.</p><p>BugCheck 1000008E, {c0000005, 80570d0f, f9657430, 0}</p><p>ANALYSIS: Kernel with unknown size. Will force reload symbols with known size.<br />ANALYSIS: Force reload command: .reload /f ntoskrnl.exe=FFFFFFFF804D7000,213F80,42250FF9<br />***** Kernel symbols are WRONG. Please fix symbols to do analysis.</p><p>***** Kernel symbols are WRONG. Please fix symbols to do analysis.</p><p>*************************************************************************<br />*** ***<br />*** ***<br />*** Your debugger is not using the correct symbols ***<br />*** ***<br />*** In order for this command to work properly, your symbol path ***<br />*** must point to .pdb files that have full type information. ***<br />*** ***<br />*** Certain .pdb files (such as the public OS symbols) do not ***<br />*** contain the required information. Contact the group that ***<br />*** provided you with these symbols if you need this command to ***<br />*** work. ***<br />*** ***<br />*** Type referenced: nt!_KPRCB ***<br />*** ***<br />*************************************************************************<br />*************************************************************************<br />*** ***<br />*** ***<br />*** Your debugger is not using the correct symbols ***<br />*** ***<br />*** In order for this command to work properly, your symbol path ***<br />*** must point to .pdb files that have full type information. ***<br />*** ***<br />*** Certain .pdb files (such as the public OS symbols) do not ***<br />*** contain the required information. Contact the group that ***<br />*** provided you with these symbols if you need this command to ***<br />*** work. ***<br />*** ***<br />*** Type referenced: nt!KPRCB ***<br />*** ***<br />*************************************************************************<br />*************************************************************************<br />*** ***<br />*** ***<br />*** Your debugger is not using the correct symbols ***<br />*** ***<br />*** In order for this command to work properly, your symbol path ***<br />*** must point to .pdb files that have full type information. ***<br />*** ***<br />*** Certain .pdb files (such as the public OS symbols) do not ***<br />*** contain the required information. Contact the group that ***<br />*** provided you with these symbols if you need this command to ***<br />*** work. ***<br />*** ***<br />*** Type referenced: nt!_KPRCB ***<br />*** ***<br />*************************************************************************<br />*************************************************************************<br />*** ***<br />*** ***<br />*** Your debugger is not using the correct symbols ***<br />*** ***<br />*** In order for this command to work properly, your symbol path ***<br />*** must point to .pdb files that have full type information. ***<br />*** ***<br />*** Certain .pdb files (such as the public OS symbols) do not ***<br />*** contain the required information. Contact the group that ***<br />*** provided you with these symbols if you need this command to ***<br />*** work. ***<br />*** ***<br />*** Type referenced: nt!KPRCB ***<br />*** ***<br />*************************************************************************<br />*************************************************************************<br />*** ***<br />*** ***<br />*** Your debugger is not using the correct symbols ***<br />*** ***<br />*** In order for this command to work properly, your symbol path ***<br />*** must point to .pdb files that have full type information. ***<br />*** ***<br />*** Certain .pdb files (such as the public OS symbols) do not ***<br />*** contain the required information. Contact the group that ***<br />*** provided you with these symbols if you need this command to ***<br />*** work. ***<br />*** ***<br />*** Type referenced: nt!_KPRCB ***<br />*** ***<br />*************************************************************************<br />Probably caused by : hardware ( kl1+db4 )</p><p>Followup: MachineOwner<br />---------</p><p>HELP !!!!!!!!!!!!!!!!!!!!!</p></font>