Mam problem często (nawet bardzo często) wyświetla mi się BSOD mam win XP sp3 home kiedyś z jakieś dwa tygodnie temu było wszystko ok…
Przeleciałem kompa anty wirem… CCleaner’em i z defragmentowałem… Myślałem, że już po wszystkim a tu nadal… Przesyłam fotkę… A dodam jeszcze, że zawsze to samo się wyświetla…
Z góry dzięki za odpowiedź!
odczytaj zrzut z folderu minidump programem windbg
Folder Minidump jest pusty po zaznaczeniu opcji (pokaż ukryte pliki i foldery) także… Może to dlatego że
wejdź we właściwości mojego komputera w zakładkę zaawansowane, i w ustawienia uruchamianie i odzyskiwanie i zaznacz pod napisem awaria systemu te 3 opcję oraz Zapisywanie informacji o debugowaniu Mały zrzut pamięci i na dole ma być taka ścieżka %SystemRoot%\Minidump. i masz czekać na bsoda i powinien się zapisać w folderze mindump. wejdź w menedżer urządzeń i zobacz czy nie masz znaków zapytania.
– Dodane 22.10.2009 (Cz) 15:00 –
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) 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 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 3) MP (2 procs) Free x86 compatible
Product: WinNt
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Thu Oct 22 10:33:50.312 2009 (GMT+2)
System Uptime: 0 days 0:04:56.021
*********************************************************************
* 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 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 7F, {8, 80042000, 0, 0}
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
***** 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***
******
*************************************************************************
*********************************************************************
* 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+ *
*********************************************************************
*********************************************************************
* 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+ *
*********************************************************************
Probably caused by : ntoskrnl.exe ( nt+88e9 )
Followup: MachineOwner
---------
Nie wiem o co chodzi tak napisali w Minidump…
A macie jakieś konkretne porady?
a może w Konsoli odzyskiwania ,komenda:
expand X:\i386\ntoskrnl.ex_ C:\Windows\system32\ntoskrnl.exe
A możesz mi napisać jak to zrobić konkretnie?
Na razie się powstrzymam do czasu następnego BSOD’a
– Dodane 25.10.2009 (N) 16:23 –
Wykrakałem: