BSOD - što, zašto i kako

Odvrtio sam memtest 64+ pola sata,nije pronašlo ništa sumnjivo .

Imate li kakve ideje zašto bi moglo bacat povremeno BSOD ,na BF3 ili kad ga ugasim...? 

Cijelu konfu sam novu sastavio prije tjedan i po dana ,nekako mi nevjerovatno da bi moglo bit do hardwarea.

 - ... jer je sve povezano s VGA (i driverima) uz stalne izmjenen/nadogradnje flasha i sl. Poneki od tih problema su vezani uz browser i dodatke (pa i malware). Update flasha, jave, test s ie9-ff-chrome.. u pravilu je ie9 najstabilniji, ff kad je čist radi 8ubiju ga pluginovi, prečesto nove verzije), chrome je OK itd.

- flash bi trebao biti v.11 pazi na verziju 32-64, za browsanje je 'pametnije' korištenje 32bitnih verzija browsera (64 je apsolutno nepotrebno i još ima dosta problema, najviše flash i java).

Na stare drivere sam mislio na te koje si stavio tada kada si složio konfu...njih makni, najbolje sa nekim free programom za micanje driver-a...tada podigneš u safe mode-u komp i instaliraš najnovije official drivere za svoju grafulju....i to bi trebalo riješiti bilo kakve probleme sa driver-ima za grafičku...

evo nakon 2 više-manje mirna dana, opet su postali učestali bsod-ovi

učinio sam postupke s uvodnog posta ove teme, evo analize jednog tipičnog dumpa

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffffa8002be3fac, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

Debugging Details:
------------------

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
+0
fffffa80`02be3fac 0000            add     byte ptr [rax],al

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d0b0e0
 ffffffffffffffff

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  d

LAST_CONTROL_TRANSFER:  from fffff80002b14a17 to fffff80002ad4f00

STACK_TEXT: 
fffff880`02d1b0d8 fffff800`02b14a17 : 00000000`0000001e ffffffff`c0000005 fffffa80`02be3fac 00000000`00000000 : nt!KeBugCheckEx
fffff880`02d1b0e0 fffff800`02ad4542 : fffff880`02d1b8b8 00000000`00000000 fffff880`02d1b960 fffff880`009e8180 : nt! ?? ::FNODOBFM::`string'+0x460da
fffff880`02d1b780 fffff800`02ad2e4a : fffffa80`02b9c810 00000000`00000000 fffffa80`02b9c810 fffff880`00d8345a : nt!KiExceptionDispatch+0xc2
fffff880`02d1b960 fffffa80`02be3fac : 00000000`00000011 00000000`00000000 fffff880`02d1bb80 fffff880`009e8180 : nt!KiGeneralProtectionFault+0x10a
fffff880`02d1baf8 00000000`00000011 : 00000000`00000000 fffff880`02d1bb80 fffff880`009e8180 00000000`00000001 : 0xfffffa80`02be3fac
fffff880`02d1bb00 00000000`00000000 : fffff880`02d1bb80 fffff880`009e8180 00000000`00000001 fffffa80`00000001 : 0x11

STACK_COMMAND:  kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+460da
fffff800`02b14a17 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+460da

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0x1E_nt!_??_::FNODOBFM::_string_+460da

BUCKET_ID:  X64_0x1E_nt!_??_::FNODOBFM::_string_+460da

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

uz to, po jedan put su okrivljeni i cdrom.sys, i neki modemski i daemon driveri (oba neutralizirana nakon toga)m odvrtio sam opet memtest, sat vremena ovaj put, opet ništa

pa, imate li koji savjet? možda druga verzija windowsa (iako je prije iša i na xp i win 7 bez ikakvih problema)... možda da memtest odvrtim puno duže? stvarno ne znam, tražeći drugdje po internetu rješenja su obično jednostavnija, i problemi prestanu formatiranjem, možda je stvarno problem u hardware-u?

Gigabyte driver check iz Gigabyte Tools-a. Poznati su po tome da stvaraju probleme. Još malo ....

Najbolje deinstaliraj ,pa onda probaj.

Mislim da više nebi trebalo biti problema ,iako nebi bilo naodmet napravit i system check i repair sa sfc /scannow u cmd-u.

Ali ,samo za informaciju ,ako koristiš neki patch za teme ,morat ćeš to ponovno napraviti.

Eto i mene opet s novim winsima win7 x64 sp1 s bsod-ovima

odradio sam memtest i evo slike ipod a ievo i PS blues screena

MBO: Gigabyte X38-DQ6

RAM: OCZ 4x1 DDR2

CPU: Intel Core2 Quad Q6600, 2.40ghz

GPU: Nvidia GeForce 8800 GT

MEMTEST SLIKA (vrtio se od sinoć)

MINIDUMP

BLUEVIEW

hvala ;)

  ... binarno stablo, kao najbrži način sortiranja.

- osim u ovakvom slučaju, jer..

-ako je problem u utoru, tad je potrebno pojedinačno testiranje,

-brzina testa ovisi i o kolićini RAMa, manje je brže, recimo da je dovoljno testiranje 5-10min za jedan DIMM. Otkriveni RAM s greškom se prebacuje i idući utor i time je test gotov (potvrđen uzrok), s parovima ispada duže.

... ali to je sve akademska rasprava, važno je samo eliminirati grešku, pola sata razlike je sporedno.

sad pavi topic, čišćenje gumicom:

stavi RAM na ravnu podlogu, pobriši mekom gumicom (za olovke) u nekoliko poteza čitavom duljinom, ne previše i ne gurati gumicu prema chipovima da se slučajno neki ne odvoji.

Čim se kontakti poćnu 'sjajiti' (kao poliranje, maknuta masnoća-smeće i patina s bakra) čišćenje je gotovo. To netreba raditi često jer sam bakar je jako tanak, previše 'šmirglanja' ga može potrošiti...

(cilj je samo ukloniti nečistoće, moglo bi se alkoholom i sl. ali postoji opasnost od odljepljivanja ili bubrenja pločice, zato je bolja gumica).

 - prvo zec, pa onda ražanj. Ako je problem rješen (sudeći po memtestu je) tad problema više neće biti. Naravno, uvjek se može pojaviti neki novi problem ali tad se kreće od 'nule' s diagnostikom (ne nastavak na postojeće postove jer novi problem može biti sasvim drugačiji...).

Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sun 11.12.2011. 21:16:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121111-19702-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x7BA8)
Bugcheck code: 0x116 (0xFFFFFA8006BAF230, 0xFFFFF8800416FBA8, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: atikmpag.sys Advanced Micro Devices, Inc. VIDEO_TDR_ERROR




On Sun 11.12.2011. 21:16:58 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x5D000)
Bugcheck code: 0x116 (0xFFFFFA8006BAF230, 0xFFFFF8800416FBA8, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sun 11.12.2011. 16:38:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121111-20451-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x7BA8)
Bugcheck code: 0x116 (0xFFFFFA8007355390, 0xFFFFF88004156BA8, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: atikmpag.sys Advanced Micro Devices, Inc. VIDEO_TDR_ERROR




On Sat 3.12.2011. 18:29:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120311-19250-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x7BA8)
Bugcheck code: 0x116 (0xFFFFFA8003FAC2E0, 0xFFFFF88004007BA8, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: atikmpag.sys Advanced Micro Devices, Inc. VIDEO_TDR_ERROR




On Sun 27.11.2011. 20:47:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112711-19890-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x7BA8)
Bugcheck code: 0x116 (0xFFFFFA800435C010, 0xFFFFF88004007BA8, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: atikmpag.sys Advanced Micro Devices, Inc. VIDEO_TDR_ERROR




Conclusion
5 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.

Dali je tu do drivera ili nečeg drugog?

Moja 2 minidumpa

razlika izmedu njih je nesta sitno oko 15 min nisam siguran neznam dali su isti..

http://www.megaupload.com/?d=T1GNTQMD

http://www.megaupload.com/?d=PN6WMW05

pomagajte!!!!!

  Driver od graficke. Ako si je clockao vrati natrag sve. Ako nisi i ako ne prestaje onda testiraj na "hladno" (Ubuntu ili Hiren`s Boot CD)

  POvadi neispravne ram module i nemas muke

- za probleme s napajanjem nema koristi od dumpova. Dumpovi su samo pokušaj prikaza stanja i detekcije komponente ili drivera, struja je svugdje neophodna, struju kontrolira MBO.

- ako se računalo pali, ako kod pokretanja zahtijevnijih poslova (veća potrošnja, prema max) nema trenutnog gašenja, tad nema veze sa napajanjem. Može biti loša ploča (kondenzatori-VRM...) ili pregrijavanje chipseta. Kvalitetnije MBO se upravo razlikuju po tomu.

- jednako može krivac biti npr kontakt (puknuta žica, u opisu kvara se podrazumijeva da je sve fizički ispravno), to nema veze s teh, ispravnošću i dumpom. Jednako može biti uzrok pad napona u graskoj mreži (kojeg bi možda neka kvalitetnije MBO mogla 'peglati'

-ukratko, uzrok je vjerojatno nešto drugo, sasvim mala šansa da je uzrok napajanje (jer nema 100% ničeg u životu...).

 -ponovi test malo dulje, memtest ne može biti gotov.. traje satima, to je samo neki postotak prolaza raznih testova.

-pošto u memtestu PC troši malo struje, nema promjena napona, to bi eliminiralo napajanje kao uzrok (potvrdilo da je greška u RAMu ili chipsetu-utoru...)