mój problem polega na tym:
Komputer czasami się nie włącza, gdy próbuje załączyć komputer wszystko jest niby ok, i jak już widzę tapetę pulpitu to pojawia się bluescreen (o różnych kodach błędu...)
Najnowszy bluescreen, który pojawił się przed włączeniem komputera - podaje fotke
Fotka
A więc restart i akurat się włączył. Pojawia się okienko:
System odzyskał sprawność działania po poważnym błędzie.
Kliknij tutaj - a więc klik
Sygnatura błędu:
BCCode : 1000000a BCP1 : 07100019 BCP2 : 00000002 BCP3 : 00000000
BCP4 : 804E469A OSVer : 5_1_2600 SP : 2_0 Product : 256_1
Kliknij tutaj - klik
Następujące pliki zostaną dołączone do tego raportu o błędach:
C:\DOCUME~1\ADMINI~1\USTAWI~1\Temp\WER8e44.dir00\Mini031908-03.dmp
C:\DOCUME~1\ADMINI~1\USTAWI~1\Temp\WER8e44.dir00\sysdata.xml
Szukałem rozwiazania problemu i natknąłem się na ten temat [ [url="http://www.searchengines.pl/index.php?showtopic=50339"]http://www.searchengines.pl/index.php?showtopic=50339[/url] ], który radzi ściągnać program Microsoft Debugging Tools
Ściągnąłem, otworzyłem plik :
C:\DOCUME~1\ADMINI~1\USTAWI~1\Temp\WER8e44.dir00\Mini031908-03.dmp
Log:
Microsoft ® Windows Debugger Version 6.8.0004.0 X86
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Documents and Settings\Administrator\Ustawienia lokalne\Temp\WER8e44.dir00\Mini031908-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image 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 XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620
Debug session time: Wed Mar 19 19:05:12.716 2008 (GMT+1)
System Uptime: 0 days 0:01:35.317
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image 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
............
Unable to load image NDIS.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NDIS.sys
*** ERROR: Module load completed but symbols could not be loaded for NDIS.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000000A, {7100019, 2, 0, 804e469a}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** WARNING: Unable to verify timestamp for pro2000.sys
*** ERROR: Module load completed but symbols could not be loaded for pro2000.sys
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : pro2000.sys ( pro2000+6fd )
Followup: MachineOwner
---------
I moje pytanie... co teraz? : /
Jak sobie z tym wszystkim poradzić? Prosiłbym o pomoc...
