Witam. Już po raz drugi mam do czynienia z taką sytuacją… jakieś 2 miesiące temu wyskoczył mi Blue Screen, komputer się zrestartował, program Debugging Tools for Windows wskazał numer błędu, nazwę pliku, który ten błąd spowodował, okazało się, że chodzi o plik antywirusa Avast5. Usunąłem program i wszystko już było w porządku.
Niestety dzisiaj Blue Screen wyskoczył mi po raz drugi, tym razem nie chodzi raczej o żaden plik, program… :?
Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10000050, {bb9fd000, 1, 8053a8c3, 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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 : win32k.sys ( win32k+36e95 )
Followup: MachineOwner
OTO SKAN Z PROGRAMU DEBUGGING TOOLS FOR WINDOWS
Nie mogę znaleźć czego dotyczy ten błąd, bardzo proszę o pomóc, jakieś wskazówki.
dzięki za pomoc.