Problem z powtarzającym się BSOD


(Limsko) #1

Witam,

na świeżo postawionym Windows 7, zainstalowane aktualizacje oraz kilkanaście programów z których korzystam,

wyrzuca mi raz na jakiś czas BSOD'a, załączam LOG, co może być przyczyną?:

 

 

Microsoft ® Windows Debugger  Version 6.6.0003.5

Copyright © Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [E:_user\011215-12963-01.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 argument when starting the debugger. *

*   using .sympath and .sympath+                                    *

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

Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 2

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Windows Vista Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144

Kernel base = 0xfffff80002a07000 PsLoadedModuleList = 0xfffff80002c4a890

Debug session time: Mon Jan 12 09:05:52.929 2015 (GMT+1)

System Uptime: 0 days 0:02:29.209

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

* 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 2

*** 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 3B, {c0000005, fffff80002a74ac5, fffff880074669f0, 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                                     ***

***                                                                   ***

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

Probably caused by : ntoskrnl.exe ( nt+6dac5 )

 

Followup: MachineOwner