Wyskakujące BSODy w grach


(shiftF2) #1

Witam.

Komputer mam w sumie od niedawna bo kupiłem go od znajomego.

I podczas grania w gry mam na przemian 2 takie niebieskie ekrany

Pamięci są sprawne na pewno bo kupowałem je osobno oraz sprawdzałem memtestem.

Czy ze względu na słaby zasilacz możliwe są poniższe błędy ?

Microsoft (R) Windows Debugger Version 6.6.0003.5

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 2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

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

Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504

Kernel base = 0xfffff800`02c0f000 PsLoadedModuleList = 0xfffff800`02e53670

Debug session time: Wed Jul 18 09:41:52.885 2012 (GMT+2)

System Uptime: 0 days 1:46:55.555

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

* 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

*** 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, 80050031, 6f8, fffff80002c8c190}


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

******

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


Followup: MachineOwner

---------

oraz

Microsoft (R) Windows Debugger Version 6.6.0003.5

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 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 Personal

Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504

Kernel base = 0xfffff800`02a58000 PsLoadedModuleList = 0xfffff800`02c9c670

Debug session time: Sun Jul 15 12:28:12.831 2012 (GMT+2)

System Uptime: 0 days 1:33:34.330

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

* 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, fffff96000235115, fffff8800779daa0, 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***

******

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

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 2

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

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

*** WARNING: Unable to verify timestamp for hal.dll

*** ERROR: Module load completed but symbols could not be loaded for hal.dll

Unable to load image \SystemRoot\System32\drivers\dxgmms1.sys, Win32 error 2

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

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

Probably caused by : win32k.sys ( win32k+205115 )


Followup: MachineOwner

---------

(djkamil09061991) #2

Bsody wskazują na sterownik od grafiki, tak więc odinstaluj aktualny i spradz inną wersję.


(Xemidra) #3

Screen z zakładki Health i sprawdź temperatury.


(Zeus__) #4

A ja uważam że albo struktura systemu jest uszkodzona wyeksploatowaniem, albo po prostu infekcje. Wrzuć logi OTL i Extras, przeskanuyj program dr.WEb i Malwerbytes Antymalware, dodatkowo wrzuć logi gmer