Proč dokolečka BSOD? Poraďte

[tomasosi]

Čus, mám takový problém hraju hru pak jí chci ukončit najednou černá obrazovka tak na vteřinu a hned BSOD..:/
Dávám výpis s whocrashed, prosím o kontrolu, díky
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 20.2.2013 21:14:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022013-16125-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x12044)
Bugcheck code: 0xC2 (0x7, 0x109B, 0xB0007, 0xFFFFFFFF86E5CFB0)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 that cannot be identified at this time.



On Wed 20.2.2013 21:14:08 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x12044)
Bugcheck code: 0xC2 (0x7, 0x109B, 0xB0007, 0xFFFFFFFF86E5CFB0)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 that cannot be identified at this time.



On Wed 20.2.2013 20:26:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022013-17203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5ED85)
Bugcheck code: 0x50 (0xFFFFFFFFFFFAE004, 0x0, 0xFFFFFFFF82E65C56, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 20.2.2013 20:02:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022013-27093-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x12044)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF86260FA8, 0xFFFFFFFF86260FC0, 0x803000F)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 that cannot be identified at this time.



On Mon 18.2.2013 20:01:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021813-22593-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x12044)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF86E256E8, 0xFFFFFFFF86E25700, 0x8030019)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 that cannot be identified at this time.



On Mon 18.2.2013 17:20:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021813-17031-01.dmp
This was probably caused by the following module: cmdguard.sys (cmdguard+0x1C11F)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82E60B17, 0xFFFFFFFF911F59D0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\cmdguard.sys
product: COMODO Internet Security Sandbox Driver
company: COMODO
description: COMODO Internet Security Sandbox Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: cmdguard.sys (COMODO Internet Security Sandbox Driver, COMODO).
Google query: COMODO KERNEL_MODE_EXCEPTION_NOT_HANDLED_M



On Mon 18.2.2013 17:18:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021813-18078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5ED85)
Bugcheck code: 0x50 (0xFFFFFFFF9EDF7EBC, 0x0, 0xFFFFFFFF82E2823A, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 18.2.2013 17:15:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021813-16750-01.dmp
This was probably caused by the following module: rdyboost.sys (rdyboost+0x10659)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF89DF0659, 0xFFFFFFFF8E5D1A54, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\rdyboost.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ReadyBoost Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 that cannot be identified at this time.



On Mon 18.2.2013 17:12:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021813-17234-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR



On Mon 18.2.2013 17:10:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021813-16203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5ED85)
Bugcheck code: 0x1A (0x41287, 0x399, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 17.2.2013 22:28:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021713-17515-01.dmp
This was probably caused by the following module: hal.sys (hal+0x3839)
Bugcheck code: 0xA (0x5CE9ABC7, 0x2, 0x1, 0xFFFFFFFF82C0C839)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: hal.sys .
Google query: hal.sys IRQL_NOT_LESS_OR_EQUAL



On Sun 17.2.2013 16:09:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021713-16375-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x1DF02)
Bugcheck code: 0x50 (0xFFFFFFFFBB123D70, 0x0, 0xFFFFFFFF91989F02, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 that cannot be identified at this time.



On Mon 11.2.2013 21:30:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021113-22671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x31834B)
Bugcheck code: 0x124 (0x0, 0xFFFFFFFF85BCF024, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 11.2.2013 21:18:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021113-21531-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x31834B)
Bugcheck code: 0x124 (0x0, 0xFFFFFFFF85CF94DC, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

--- Doplnění předchozího příspěvku (20 Úno 2013 23:36) ---

?

[Reklama]

[MiliNess]

Nejprve udělej test operační paměti (GoldMemory, Memtest)
Soubory ze složky Windows\Minidump upni na www.leteckaposta.cz

[tomasosi]

to už jsem dělal a všechno v pohodě... 0 errors..

--- Doplnění předchozího příspěvku (21 Úno 2013 02:32) ---

http://leteckaposta.cz/958182253
šli mi tam dát jen 2 jinak jich tam mám 13 vždy mi to ukáže " nemáte oprávnění, požádejte vlastníka " mám jen jeden uživ. účet..:/ nevim jak na to

[MiliNess]

Nejprve je překopíruješ do dokumentů a pak upneš.

-používáš steam?
-přetaktováváš něco?
-jaký typ základní desky používáš a jaká verze BIOSu je na ní nahraná?

[El Diablo]

Otestuj HDD utilitou od výrobce, nebo alespoň HD Tune

[tomasosi]

Disk úplně v pohodě, jak v hdtune tak v CDI... přetaktoval jsem procesor ze 3 na 3,3 ale to už mám dýl a předtim to nedělalo..steam nepoužívám deska je od asus p4c800 e-deluxe dal jsem log s toho whocrashed a to napíše vše co je v minidump

[MiliNess]

Mimo jiné u tebe dochází k detekci hardwarových chyb procesorem (WHEA) - chybám vnitřního timeru CPU.
Téměř jistě to není softwarová chyba, ale závada hardwaru. Tato chyba se často objevuje při závadě základní desky.
Vzhledem ke stáří desky může být závada právě na ní.

-já nepotřebuju výpis z nějakýho pitomýho programu, který neřekne vůbec nic, potřebuju přímo ty minidumpy.
-vrať takt CPU do defaultu
-v CPU-Z na záložce Mainboard zjisti verzi BIOSu, kterou používáš. Pokud tam nemáš verzi 1023, tak ji tam nahraj (můžeš zkusit i beta verzi 1024.001)
-vOvládací panely->Nástroje pro správu->Prohlížeč událostí->Protokoly systému Windows->klikni pravým myšítkem na protokol Systém, vyber Uložit všechny události jako, ulož to jako
.evtx soubor a ten upni na http://www.leteckaposta.cz
-spusť HeavyLoad a Hardware Monitor. V HeavyLoad spusť zátěžový test, po 10 min udělej screen Hardware Monitoru a hoď ho sem.

[tomasosi]

Tak už jsem asi přišel na ten problém.
Nainstaloval jsem memtest a nechal jsem to jet do 300% a měl jsem tam 8 chyb na ramkách..:/

[MiliNess]

Něco mohlo být způsobeno vadou paměti, ty WHEA chyby to ale pravděpodobně nezpůsobilo a bude to padat i po výměně pamětí. No uvidíš.

[tomasosi]

nevím no...jak mám nainstalovat ten bios? neni to v iso takže to nemůžu vypálit jako obraz aby to četlo při zapnutí pc j ak teda na to?

--- Doplnění předchozího příspěvku (10 Bře 2013 16:17) ---

podle cpu-z mám bios verzi 080009 datum 21.11.2003

[MiliNess]

Tak updatem nic nezkazíš. Stáhni verzi 1023 nebo beta verzi 1024. Rozbal ZIP archiv, vybalený soubor zkopíruj na flešku.
Restartuj počítač a při startu PC mačkej klávesy Alt+F2. Spustí se ti utilita Asus EZ Flash, ve které ze souboru na flešce updatneš BIOS.
Tu vadnou paměť budeš muset samozřejmě také vyměnit (v první řadě). Je také možné, že se nejedná o chybu paměti, ale některé další části paměťového subsystému.
Tady máš manuál, kdyby ti něco nebylo jasné.