1x zásek počítača od vtedy rôzne BSOD

cumilko

Zdravím, pred nedávnom sa mi stala taká vec, (pár dni do zadu) zasekol sa mi kompletne celý PC, nemohol som robit absolutne nič iba hýbať kurzorom (na klavesnici reagoval numlock etc.. kontrolky ) myslel som že mi laglo SSD tak som restartol PC a čakal či sa to stane znova takýto zasek sa mi už nestal, no začalo mi to hádzať BSOD (fotka číslo 1) to mi hodilo pár krát,
písal som si s Uplinkom on mi odporučil skontrolovať RAM-ky Memtestom spravené po nejakych 55min mi to vypísalo "no errors", potom kontrola SSD-čka cez Crystaldisk tiež žiadny problem,
tak som to chvílku neriešil hodilo mi to BSOD č. 1 ešte 1x od vtedy nič, dneska sa mi ukázalo zase BSOD (fotka číslo 2) ale už s iným obsahom. nemá niekto nejaký nápad ako zistit čo presne zapričinuje tie BSOD ?

Konfigurácia:
Windows 7 64bit (asi mesačna inštalačka)
MB: Gigabyte 970A-D3
CPU: AMD Phenom II 960T x4 alias plne stabilný 1605T/1600T x6 core @ 3,6ghz bez zmeny napätia. teploty do 46°C
GPU: Asus ENGTX550 Ti/DI/1GD5
RAM: 2x CORSAIR DDR3 4GB 1333MHz CL9 CMV4GX3M1A1333C9
PSU: Asus 450w A-45GA
HDD 1: Intel SSD 330 60gb
HDD 2: Western digital blue 1TB WD10EALX

//jediné čo ma teraz napadá je zamknút tie 2 jadra, skúsit to nechat tak nejaký čas, či sa náhodou po roku pri takomto nastavení CPU niečo nestalo, čo si ale myslím že je nepravdepodobné.

Toto nepomoze?

http://support.microsoft.com/kb/980932/sk

cumilko

skúsil by som to na to druhé BSOD no nejde stiahnut tá rychla oprava skúsim neskôr..

Sapo · Príspevok od používateľa **Sapo** » 03 mar 2013, 23:57

Skus vypnut tie dve jadra a uvidis.

xixo22

mohol by si sem upnut dmp z \Windows\minidump ?

cumilko

tu je obsah troch súborov odtial

Spoiler

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\022713-6177-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 <symbol_path> 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 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Machine Name:
Kernel base = 0xfffff800`02e08000 PsLoadedModuleList = 0xfffff800`0304c670
Debug session time: Wed Feb 27 18:03:36.991 2013 (UTC + 1:00)
System Uptime: 0 days 0:40:26.162
*********************************************************************
* 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 <symbol_path> 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, {fffffa000773f218, 1, fffff800032c2acc, 7}

***** 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 ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+4baacc )

Followup: MachineOwner
---------

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\030113-6162-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 <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Machine Name:
Kernel base = 0xfffff800`02e4c000 PsLoadedModuleList = 0xfffff800`03090670
Debug session time: Fri Mar 1 13:11:48.489 2013 (UTC + 1:00)
System Uptime: 0 days 0:02:14.644
*********************************************************************
* 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 <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** 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, {c000001d, fffff960001660cb, fffff8800d5dd1e0, 0}

Unable to load image \SystemRoot\System32\win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.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 ***
*** ***
*************************************************************************
Probably caused by : hardware ( win32k+c60cb )

Followup: MachineOwner
---------

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\030313-10686-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 <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Machine Name:
Kernel base = 0xfffff800`02e5e000 PsLoadedModuleList = 0xfffff800`030a2670
Debug session time: Sun Mar 3 13:08:09.625 2013 (UTC + 1:00)
System Uptime: 0 days 0:05:49.796
*********************************************************************
* 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 <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** 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, fffff800031d28b6, fffff8800c4aed80, 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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+3748b6 )

Followup: MachineOwner
---------

//autoeditácia príspevku (06 Mar 2013, 13:07)
tak včera som mal zásek (bez BSOD) znova aj na originál 960T (zavreté 2 jadra, a originál takty), tak som si včera večer hodil 8-mičku s UI z win 7, tak uvidím čo to porobí zatiaľ Ďakujem.

//autoeditácia príspevku (11 Júl 2013, 2:05)
Otváram znova tému s problémom s BSOD. v podstate horný popis stále platí PC sa zasekne a nič nejde robiť alebo sa zasekne a pochvílke hodí aj BSOD.
dneska som sa naštval po BSOD a nahodil som čistú inštalačku.. po chvílke používania znova to isté BSOD

v prílohe prikladám Minidumps staršie (pred reinstalaciou nejaky čas.)
a jeden čo som dostal pred chvílkou..

väčšinou čo som mal ešte v minidumpoch tak v podstate obsah bol skoro rovnaký s tým že sa menil
napr.
PROCESS_NAME: Firefox.exe
PROCESS_NAME: Flashplayerxx
PROCESS_NAME: Chrome.exe

ono to bolo asi jedno pri akom procese..

nejaký nápad na fix ? pretože po tom ako som nahodil čistú inštalačku etc.. ma nenapada už nič iné ako HW problém, ktorý by som chcel diagnostikovať a hodiť to na reklamačku..

RAM som zase prešiel MEM testom 2x pass no errors.

//E mám zase Win 7 ultimate 64bit.

MichalkoOo

prilož ešte event viewer, svieži ráno sa na to pozriem

hrban

ja by som to videl na nejakú chybu disku, skús jeden odstrániť a spusti to z druhého

cumilko

MichalkoOo: Príloha snád som uložil správne veci čo potrebuješ.

Hrban: tiež ma to napadlo že to bude SSD-čkom ale chcem si to nejako utvrdiť pretože ak ho dám na reklamačku tak pochybujem že mi ho zreklamujú kedže v nejakych softoch neukazuje absolutne ani náznak nejakého erroru.

//e1 ešte doplním že som robil aj update BIOS-u dosky pred reinstallom.

//e2 všimol som si že aj po inštalacii aktualizácii a následnom reštarte ktorý si vyžadujú sa nevedia "doinstalovat"

//e3 pridal som další minidump BSOD čo som mal par min do zadu.

MichalkoOo

skús to bez aktualizácií, win hodil error pri každej aktualizácií ktorú si nainštaloval

a aktualizácie vedia robiť šarapatu. Momentálne si prezerám tvoj m.dmp, chvíľku strpenia

//autoeditácia príspevku (11 Júl 2013, 13:26)
takže preinštaluj windows, neinštaluj žiadne inštalácie a neinštaluj REALTEK ani zvukovku ani sieťovku (pod win 7 ti bez toho ovládača nepôjde internet, win 8 pôjde). BSOD je software issue a podľa najnovšieho bsodu v tom niečo zohral realtek. Taktiež vylúč ovládače od grafiky. Ak to necrashne vieme kde začíname hľadať problém

cumilko

hmm tak to idem nahodiť síce neviem čo budem robiť na počítači kde absolútne nič nebude.

MichalkoOo

aktualizácie ti netreba, zvuk ti pôjde aj bez realteku a internet tiež ak máš win 8 tak aký problém? akurát hry si nezahráš ale to iba dočasne

cumilko

No chcem nahodit win 7 ale rozmyslam ze nahodim win 8 na chvilu.

MichalkoOo

win 8 je modernejší systém..

cumilko

To nic nmeni na tom ze som napr. V crysis 3 mal menej FPS ako na 7 a dost ma to iritovalo

//e neviem ci som aj tam mal BSOD alebo to boli len fps-ka

//autoeditácia príspevku (11 Júl 2013, 19:00)
tak nahodil som tam tú 8-mičku a dostal som rovnaké BSOD ako jedno z predchádzajúcich.

príloha minidump.

MichalkoOo

tak skús linux a potom už iba HW

cumilko

dneska som testoval či to nieje chyba SSD, nahodil som win 8 na 1TB caviar blue disk a tak isto som dostal BSOD.
nechcel som isť na linux no idem zase zapojiť SSD a nahodiť tam ubuntu..

Gyrxiur

Nemáš ovládače na grafiku 32x.xx a novšie? Hlavne na kartách 450,460,550 a 560 robia dosť ľudom problémy, skús downgrade na 314.22

MichalkoOo

fungovať bež ovládačov som mu už radil..

cumilko

ovladače som skúšal..

ale prehodil som moje
RAM: 2x CORSAIR DDR3 4GB 1333MHz CL9 CMV4GX3M1A1333C9 1.5v
za
1x Patriot 4GB DDR3 1333MHz CL9 1.5v

zatiaľ som bez pádu ak behom dneška nedostanem BSOD idem testovať s ktorou RAM mám problém..

//autoeditácia príspevku (12 Aug 2013, 16:16)
no takže definitívne je to niečo s RAM alebo dual channelom na MB..

ak mám 2x CORSAIR DDR3 4GB 1333MHz CL9 CMV4GX3M1A1333C9 1.5v v dual channel prichádza BSOD (začali to robiť až po roku a niečo (pred tým v inej MB na tejto MB to išlo pár mesiacov úplne bez problémov BSOD som nemal.)

ako náhle jednu vymením za 1x Patriot 4GB DDR3 1333MHz CL9 1.5v tak žiadne BSOD sa nedostaví.

skúšal som tie RAMky testovať jednotlivo akonáhle ich nemám proste v dualchannel som bez BSOD. teraz neviem či je to chyba oboch modulov RAM alebo chyba mojej MB.. a hlavne či to je na RMA.. ak áno tak ako im to dokázať v ageme ? kedže MEM-test nevyhadzuje absolútne žiadnu chybu.

1x zásek počítača od vtedy rôzne BSOD

1x zásek počítača od vtedy rôzne BSOD

Re: 1x zásek počítača od vtedy rôzne BSOD

Re: 1x zásek počítača od vtedy rôzne BSOD

Re: 1x zásek počítača od vtedy rôzne BSOD

Re: 1x zásek počítača od vtedy rôzne BSOD

Re: 1x zásek počítača od vtedy rôzne BSOD

Re: 1x zásek počítača od vtedy rôzne BSOD

Re: 1x zásek počítača od vtedy rôzne BSOD

Re: 1x zásek počítača od vtedy rôzne BSOD

Re: 1x zásek počítača od vtedy rôzne BSOD

Re: 1x zásek počítača od vtedy rôzne BSOD

Re: 1x zásek počítača od vtedy rôzne BSOD

Re: 1x zásek počítača od vtedy rôzne BSOD

Re: 1x zásek počítača od vtedy rôzne BSOD

Re: 1x zásek počítača od vtedy rôzne BSOD

Re: 1x zásek počítača od vtedy rôzne BSOD

Re: 1x zásek počítača od vtedy rôzne BSOD

Re: 1x zásek počítača od vtedy rôzne BSOD

Re: 1x zásek počítača od vtedy rôzne BSOD

Re: 1x zásek počítača od vtedy rôzne BSOD