Niebieski ekran z ? i restart

MaciejP · 4 Marzec 2006 00:11

Witam. Mam kłopot ze swoim XP ( niebieski ekran z komunikatem na cały ekran, ale trwający 0.5 sek. i restart komputera w czasie np. uruchamiania Firefoxa, klikania na odinstalowanie programu lub na ikonke w Panelu sterowania).

Nie wiem ale problemy zaczeły sie od zaznaczenia opcji “Zaawansowanego zarządzania energią APM”, a która to opcja rozwiązała mi inny problem z niewyłączaniem sie komputera (tzn. monitor gasł, a wiatrak chodził)

Moje pytanie na początek: czy gdzieś na dysku jest plik z tym właśnie komunikatem? Prosze o odpowiedź

PS

Mam wyłączonego DrWatsona , więc jakby ktoś mógby napisać co tam w opcjach jest domyślnie zaznaczone to by było super.

Pozdrawiam

asterisk · 4 Marzec 2006 00:25

Szukajka nie działa ??

===::> Dziennik zdarzeń systemu -?gdzie to jest

MaciejP · 6 Marzec 2006 20:07

Miałem dzisiaj to samo. Z podglądu zdarzeń:

Ściągnełem Debugging Tools for Windows aby odczytać tego dumpa i oto wynik:

Microsoft ® Windows Debugger Version 6.6.0003.5 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C] 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image ntoskrnl.exe, Win32 error 2 *** 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 = 0x8055a420 Debug session time: Mon Mar 6 17:44:26.964 2006 (GMT+1) System Uptime: 0 days 0:18:56.545 ********************************************************************* * 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image ntoskrnl.exe, Win32 error 2 *** 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 sysdrv.sys, Win32 error 2 *** ERROR: Module load completed but symbols could not be loaded for sysdrv.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, fb1038b2, f6791c10, 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 *** *** *** ************************************************************************* Probably caused by : sysdrv.sys ( sysdrv+8b2 ) Followup: MachineOwner ---------

Jakieś pomysły?

PS

sysdrv.sys jest sterownikiem systemowym