BSOD podczas grania


(punisher1) #1

Witam. Mam nowo zakupiony komputer i problem z graniem, poniewaz wywala mi niekiedy blue screen'y. Moj sprzet to:

phenom 2 x4 955 be, asus m4a88t-v, kingston hyperx 2x2gb 1333mhz, gtx 460 768mb, ocz stealthxstream 500W.

Probowalem sterownikow od karty graficznej dolaczonych do karty oraz najnowszych pobranych ze strony nvidii.

System to oczywiscie windows 7 ultimate x64.

W dzienniku zdarzen odczytalem cos takiego


(ra-v) #2

Tylko przy grach czy konkretnej grze?

Jeśli nie stery to może zasilacz się nie wyrabia - sprawdź napięcia i oblicz przypuszczalną maksymalną moc pobieraną podczas grania.

Druga sprawa to RAM - sprawdź Memtestem, sprawdź czy się nei przegrzewa, zostaw najpierw jedna, potem drugą kość i zobacz efekty.


(punisher1) #3

Mam taki miernik, ale nie wiem co ustawic do sprawdzenia linii +12V (http://www.google.pl/imgres?imgurl=http://www.rtv.megasam.info/images/miernik_1.jpg&imgrefurl=http://www.rtv.megasam.info/product_info.php%3Fproducts_id%3D636&h=600&w=500&sz=76&tbnid=97mELD9e4a6sZM:&tbnh=135&tbnw=113&prev=/images%3Fq%3Dmiernik&zoom=1&q=miernik&usg=__hVLOuLrW_ib_0g0T2Py4PEbYZAs=&sa=X&ei=b41fTf8sipk6_ZfU1Q0&ved=0CEkQ9QEwBQ.

A pamieci mam sprawdzic memtestem osobno? tzn najpierw jedna, pozniej druga, czy mozna odrazu 2 na raz? Ile taki test trwa?

-- Dodane 19.02.2011 (So) 12:43 --

juz sobie poradzilem, napiecie 12.09V

-- Dodane 19.02.2011 (So) 12:49 --

uzylem debugera i pokazal mi cos takiego:

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 \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 7 Kernel Version 7600 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255

Machine Name:

Kernel base = 0xfffff800`02e57000 PsLoadedModuleList = 0xfffff800`03094e50

Debug session time: Fri Feb 18 21:23:16.123 2011 (GMT+1)

System Uptime: 0 days 4:36:02.886

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

* 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 D1, {fffff8880ad1e218, 2, 1, fffff88013f7921e}


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

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

*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.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***

******

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

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

******

******

***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 : nvlddmkm.sys ( nvlddmkm+11521e )


Followup: MachineOwner

---------

(ra-v) #4

Podczas grania najlepiej, ale to już chyba nieistotne.

Czytając dziennik debuggera myślę że problem jest w sterownikach Nvidia. Użyj sterowników dostarczonych na CD wraz z kartą grafiki czy komputerem, lub innych niż najnowszych z nvidia.com (innymi słowy starszych o ile są).


(Piotrkijak) #5

Zaktualizuj sterowniki do grafiki. Jeżeli nie pomoże, to tak jak jest napisane wcześniej, trzeba każdą kość przetestować osobno memtestem i jeżeli nie wykaże błędów, żrobić torture test GPU, bo może jest zrąbana grafika. Oczywiście zasilacz to też może być, więc najlepiej byłoby pożyczyć od kogoś mocniejszy i sprawdzić czy nadal będzie to samo.


(punisher1) #6

Robiac test furmarkiem wyskoczyl mi ten blad, pare godzin pozniej juz go nie bylo. Jednym slowem jest to bardzo losowe. Przegladajac neta wyczytalem, ze jest to ogolny problem kart opartych o chipset Fermi (http://www.bestpcinfo.pl/newsy/nvidia-i-nietypowe-problemy-fermiego/). Probowalem najnowszych sterow i dolaczonych do zestawu. Nic nie pomagalo i zawsze wywalalo ten blad o utracie sprawnosci sterownika. Tutaj, na glownej forum nvidii jest molestowany podobny watek. Niestety moj angielski szwankuje od czasu zaprzestania nauki ... -> http://forums.nvidia.com/index.php?showtopic=187401&st=0