Ciągłe BSOD-y. Jak sprawdzić ich przyczynę pojawiania?


(Tom3k3) #1

Witam,

Na nowym sprzęcie od 2 tygodni spotykam się z bluescreenami. Pytałem na forum microsoftu. Nakierowano mnie, aby ściągnąć program, który odczyta mini dumpa, i widzę tam, że w sekcji Probably caused by jest przyczyna, tylko ze 99% przypadków ten problem caused by to: ntoskrnl.exe

Poniżej 2 ostatnie logi z mini dumpa:

Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64

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 \SystemRoot\system32\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 8 Kernel Version 9200 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 9200.16628.amd64fre.win8_gdr.130531-1504

Machine Name:

Kernel base = 0xfffff801`9660f000 PsLoadedModuleList = 0xfffff801`968dba20

Debug session time: Sat Aug 24 19:12:45.122 2013 (UTC + 2:00)

System Uptime: 0 days 0:42:18.812

*********************************************************************

* 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 \SystemRoot\system32\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 50, {ffffffffffffffe8, 0, fffff960000a9147, 0}


***** Kernel symbols are WRONG. Please fix symbols to do analysis.


*************************************************************************

******

******

***Either you specified an unqualified symbol, or your debugger***

***doesn't have full symbol information. Unqualified symbol***

***resolution is turned off by default. Please either specify a***

***fully qualified symbol module!symbolname, or enable resolution***

***of unqualified symbols by typing ".symopt- 100". Note that***

***enabling unqualified symbol resolution with network symbol***

***server shares in the symbol path may cause the debugger to***

***appear to hang for long periods of time when an incorrect***

***symbol name is typed or the network symbol server is down.***

******

***For some commands 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***

******

*************************************************************************

*************************************************************************

******

******

***Either you specified an unqualified symbol, or your debugger***

***doesn't have full symbol information. Unqualified symbol***

***resolution is turned off by default. Please either specify a***

***fully qualified symbol module!symbolname, or enable resolution***

***of unqualified symbols by typing ".symopt- 100". Note that***

***enabling unqualified symbol resolution with network symbol***

***server shares in the symbol path may cause the debugger to***

***appear to hang for long periods of time when an incorrect***

***symbol name is typed or the network symbol server is down.***

******

***For some commands 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***

******

*************************************************************************

*************************************************************************

******

******

***Either you specified an unqualified symbol, or your debugger***

***doesn't have full symbol information. Unqualified symbol***

***resolution is turned off by default. Please either specify a***

***fully qualified symbol module!symbolname, or enable resolution***

***of unqualified symbols by typing ".symopt- 100". Note that***

***enabling unqualified symbol resolution with network symbol***

***server shares in the symbol path may cause the debugger to***

***appear to hang for long periods of time when an incorrect***

***symbol name is typed or the network symbol server is down.***

******

***For some commands 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***

******

*************************************************************************

*************************************************************************

******

******

***Either you specified an unqualified symbol, or your debugger***

***doesn't have full symbol information. Unqualified symbol***

***resolution is turned off by default. Please either specify a***

***fully qualified symbol module!symbolname, or enable resolution***

***of unqualified symbols by typing ".symopt- 100". Note that***

***enabling unqualified symbol resolution with network symbol***

***server shares in the symbol path may cause the debugger to***

***appear to hang for long periods of time when an incorrect***

***symbol name is typed or the network symbol server is down.***

******

***For some commands 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***

******

*************************************************************************

*************************************************************************

******

******

***Either you specified an unqualified symbol, or your debugger***

***doesn't have full symbol information. Unqualified symbol***

***resolution is turned off by default. Please either specify a***

***fully qualified symbol module!symbolname, or enable resolution***

***of unqualified symbols by typing ".symopt- 100". Note that***

***enabling unqualified symbol resolution with network symbol***

***server shares in the symbol path may cause the debugger to***

***appear to hang for long periods of time when an incorrect***

***symbol name is typed or the network symbol server is down.***

******

***For some commands 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***

******

*************************************************************************

*************************************************************************

******

******

***Either you specified an unqualified symbol, or your debugger***

***doesn't have full symbol information. Unqualified symbol***

***resolution is turned off by default. Please either specify a***

***fully qualified symbol module!symbolname, or enable resolution***

***of unqualified symbols by typing ".symopt- 100". Note that***

***enabling unqualified symbol resolution with network symbol***

***server shares in the symbol path may cause the debugger to***

***appear to hang for long periods of time when an incorrect***

***symbol name is typed or the network symbol server is down.***

******

***For some commands 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***

******

*************************************************************************

*** WARNING: Unable to verify timestamp for win32k.sys

*** ERROR: Module load completed but symbols could not be loaded for win32k.sys

*************************************************************************

******

******

***Either you specified an unqualified symbol, or your debugger***

***doesn't have full symbol information. Unqualified symbol***

***resolution is turned off by default. Please either specify a***

***fully qualified symbol module!symbolname, or enable resolution***

***of unqualified symbols by typing ".symopt- 100". Note that***

***enabling unqualified symbol resolution with network symbol***

***server shares in the symbol path may cause the debugger to***

***appear to hang for long periods of time when an incorrect***

***symbol name is typed or the network symbol server is down.***

******

***For some commands 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***

******

*************************************************************************

*************************************************************************

******

******

***Either you specified an unqualified symbol, or your debugger***

***doesn't have full symbol information. Unqualified symbol***

***resolution is turned off by default. Please either specify a***

***fully qualified symbol module!symbolname, or enable resolution***

***of unqualified symbols by typing ".symopt- 100". Note that***

***enabling unqualified symbol resolution with network symbol***

***server shares in the symbol path may cause the debugger to***

***appear to hang for long periods of time when an incorrect***

***symbol name is typed or the network symbol server is down.***

******

***For some commands 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 : win32k.sys ( win32k+5e147 )


Followup: MachineOwner

oraz

Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64

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 \SystemRoot\system32\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 8 Kernel Version 9200 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 9200.16628.amd64fre.win8_gdr.130531-1504

Machine Name:

Kernel base = 0xfffff802`03a0c000 PsLoadedModuleList = 0xfffff802`03cd8a20

Debug session time: Sat Aug 24 23:55:32.351 2013 (UTC + 2:00)

System Uptime: 0 days 4:42:16.040

*********************************************************************

* 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 \SystemRoot\system32\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 1E, {ffffffffc0000005, fffff80203a8e321, 0, ffffffffffffffff}


***** Kernel symbols are WRONG. Please fix symbols to do analysis.


*************************************************************************

******

******

***Either you specified an unqualified symbol, or your debugger***

***doesn't have full symbol information. Unqualified symbol***

***resolution is turned off by default. Please either specify a***

***fully qualified symbol module!symbolname, or enable resolution***

***of unqualified symbols by typing ".symopt- 100". Note that***

***enabling unqualified symbol resolution with network symbol***

***server shares in the symbol path may cause the debugger to***

***appear to hang for long periods of time when an incorrect***

***symbol name is typed or the network symbol server is down.***

******

***For some commands 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***

******

*************************************************************************

*************************************************************************

******

******

***Either you specified an unqualified symbol, or your debugger***

***doesn't have full symbol information. Unqualified symbol***

***resolution is turned off by default. Please either specify a***

***fully qualified symbol module!symbolname, or enable resolution***

***of unqualified symbols by typing ".symopt- 100". Note that***

***enabling unqualified symbol resolution with network symbol***

***server shares in the symbol path may cause the debugger to***

***appear to hang for long periods of time when an incorrect***

***symbol name is typed or the network symbol server is down.***

******

***For some commands 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***

******

*************************************************************************

*************************************************************************

******

******

***Either you specified an unqualified symbol, or your debugger***

***doesn't have full symbol information. Unqualified symbol***

***resolution is turned off by default. Please either specify a***

***fully qualified symbol module!symbolname, or enable resolution***

***of unqualified symbols by typing ".symopt- 100". Note that***

***enabling unqualified symbol resolution with network symbol***

***server shares in the symbol path may cause the debugger to***

***appear to hang for long periods of time when an incorrect***

***symbol name is typed or the network symbol server is down.***

******

***For some commands 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***

******

*************************************************************************

*************************************************************************

******

******

***Either you specified an unqualified symbol, or your debugger***

***doesn't have full symbol information. Unqualified symbol***

***resolution is turned off by default. Please either specify a***

***fully qualified symbol module!symbolname, or enable resolution***

***of unqualified symbols by typing ".symopt- 100". Note that***

***enabling unqualified symbol resolution with network symbol***

***server shares in the symbol path may cause the debugger to***

***appear to hang for long periods of time when an incorrect***

***symbol name is typed or the network symbol server is down.***

******

***For some commands 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***

******

*************************************************************************

*************************************************************************

******

******

***Either you specified an unqualified symbol, or your debugger***

***doesn't have full symbol information. Unqualified symbol***

***resolution is turned off by default. Please either specify a***

***fully qualified symbol module!symbolname, or enable resolution***

***of unqualified symbols by typing ".symopt- 100". Note that***

***enabling unqualified symbol resolution with network symbol***

***server shares in the symbol path may cause the debugger to***

***appear to hang for long periods of time when an incorrect***

***symbol name is typed or the network symbol server is down.***

******

***For some commands 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***

******

*************************************************************************

*************************************************************************

******

******

***Either you specified an unqualified symbol, or your debugger***

***doesn't have full symbol information. Unqualified symbol***

***resolution is turned off by default. Please either specify a***

***fully qualified symbol module!symbolname, or enable resolution***

***of unqualified symbols by typing ".symopt- 100". Note that***

***enabling unqualified symbol resolution with network symbol***

***server shares in the symbol path may cause the debugger to***

***appear to hang for long periods of time when an incorrect***

***symbol name is typed or the network symbol server is down.***

******

***For some commands 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***

******

*************************************************************************

*************************************************************************

******

******

***Either you specified an unqualified symbol, or your debugger***

***doesn't have full symbol information. Unqualified symbol***

***resolution is turned off by default. Please either specify a***

***fully qualified symbol module!symbolname, or enable resolution***

***of unqualified symbols by typing ".symopt- 100". Note that***

***enabling unqualified symbol resolution with network symbol***

***server shares in the symbol path may cause the debugger to***

***appear to hang for long periods of time when an incorrect***

***symbol name is typed or the network symbol server is down.***

******

***For some commands 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***

******

*************************************************************************

*************************************************************************

******

******

***Either you specified an unqualified symbol, or your debugger***

***doesn't have full symbol information. Unqualified symbol***

***resolution is turned off by default. Please either specify a***

***fully qualified symbol module!symbolname, or enable resolution***

***of unqualified symbols by typing ".symopt- 100". Note that***

***enabling unqualified symbol resolution with network symbol***

***server shares in the symbol path may cause the debugger to***

***appear to hang for long periods of time when an incorrect***

***symbol name is typed or the network symbol server is down.***

******

***For some commands 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 : ntoskrnl.exe ( nt+82321 )


Followup: MachineOwner

Wpisałem w google wczoraj ten ntoskrnl.exe + kod błędu i był jeden przypadek, który po zmianie ramu został "wyleczony". Jak sprawdzić co jest przyczyną tego braku stabilności?

-- Dodane 25.08.2013 (N) 15:10 --

Tyle co napisałem posta i znowu bsod :frowning:


(jzelek) #2

Jeśli wyczytałeś, że to może być problem z pamięcią ram to możesz ją przetestować tym programem: http://www.dobreprogramy.pl/Memtest86,P ... 12556.html

Kiedyś na forum był taki problem: bluescreen-blad-ntoskrnl-exe-t472502.html


(StarterX4) #3

Pewnie wina sterowników, zaktualizuj je lub zrób ich reinstalacje.


(Tom3k3) #4

ale jak sprawdzić, których?