Minidump problém.

[Roli]

Není zač a kdyby něco dej vědět.

[kuntakinte]

Zdravím, tak PC zatím neudělalo to co dělalo doteď, avšak problém zjevně vyřešen nebyl. Jednou se mi objevil Crash Reporting Tool hned po startu bez toho aby PC padnulo, a před chvílí mi padla pouze hra, rozbil se mi obraz na snad 8 barev a pár pixlů s chybovou hláškou v ovladačech grafický karty, a PC bylo nutno restartovat. Celý to vypadá asi takhle:

On Sun 25.12.2011 19:44:33 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini122511-01.dmp
This was probably caused by the following module: ati3duag.dll (ati3duag+0xDE617)
Bugcheck code: 0xEA (0xFFFFFFFF893F9528, 0xFFFFFFFF8839AA70, 0xFFFFFFFF890EA380, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER
file path: C:\WINDOWS\system32\ati3duag.dll
product: Advanced Micro Devices, Inc. Radeon DirectX Universal Driver
company: Advanced Micro Devices, Inc.
description: ati3duag.dll
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
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: ati3duag.dll (ati3duag.dll, Advanced Micro Devices, Inc. ).
Google query: ati3duag.dll Advanced Micro Devices, Inc. THREAD_STUCK_IN_DEVICE_DRIVER




On Thu 22.12.2011 19:02:44 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini122211-01.dmp
This was probably caused by the following module: ati2cqag.dll (ati2cqag+0xA2D0)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBF06B2D0, 0xFFFFFFFFA8D358E4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ati2cqag.dll
product: ATI Radeon Family
company: ATI Technologies Inc.
description: Central Memory Manager / Queue Server Module
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: ati2cqag.dll (Central Memory Manager / Queue Server Module, ATI Technologies Inc.).
Google query: ati2cqag.dll ATI Technologies Inc. KERNEL_MODE_EXCEPTION_NOT_HANDLED_M





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

2 crash dumps have been found and analyzed. 2 third party drivers have 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:

ati2cqag.dll (Central Memory Manager / Queue Server Module, ATI Technologies Inc.)

ati3duag.dll (ati3duag.dll, 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.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

[Roli]

Problémy s grafikou pořád dokola.

To znamená že je problém v horším případě s hardware (grafika, základní deska, zdroj)

nebo v lepším případě se perou ovladače.

Zkusil bych použít Driver Sweeper přes který

odinstaluj ovladače od grafiky a pak je nainstaluj znovu.

[kuntakinte]

Nejsem si jist jestli jsem ten program tak úplně pochopil, tak se ptám: Bylo myšleno kliknout na AMD Display-Analyse-Clean a pak po rebootu nainstalovat ovladače z těch co jsme posledné stáhli? Nebo jsem to pochopil absolutně špatně? Jinak po instalaci ovladačů mi napsalo že počas instalace došlo k jakýmsi výstrahám, avšak v konečném logu po úspěšné instalaci bylo pole chybových hlášení prázdné.

[Roli]

Pochopil jsi to naprosto správně

I když na nějaké závěry je asi brzy, ale co stav PC ?

[kuntakinte]

Tak jak říkám, ono už nepadalo ani předtím, tentokrát ty ovladače nedělali zas takový psinec, ale dobrý to nebylo. No zatím ok, zkusil jsem právě ten 3DMark a bez problémů, zkusím nejbližší dny nějaké gamesky Jinak na tu ma desku/zdroj existují nějaký testy které by mě udělali chytřejším?

[Roli]

No zatím ok, zkusil jsem právě ten 3DMark a bez problémů, zkusím nejbližší dny nějaké gamesky

Dobře pak dej vědět.

Jinak na tu ma desku/zdroj existují nějaký testy které by mě udělali chytřejším?

V domácích podmínkách bohužel nee.

[kuntakinte]

Tak já Vás zdravím, jsem tu zas, stejně jak tenhle problém. A znovu bych Vás rád poprosil o radu, jestli ještě nejaká na tohle bude

System Information (local)
--------------------------------------------------------------------------------

computer name: B-3DFA3368B9EC4
windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: C:\WINDOWS
CPU: GenuineIntel Intel(R) Core(TM)2 Quad CPU Q8200 @ 2.33GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 2145628160 total
VM: 2147352576, free: 2041683968



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


On Sun 12.2.2012 21:41:12 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini021212-07.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x3F294)
Bugcheck code: 0x10000050 (0xFFFFFFFFCEECE87D, 0x1, 0xFFFFFFFF8052DDE9, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
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 12.2.2012 20:26:35 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini021212-06.dmp
This was probably caused by the following module: win32k.sys (win32k+0x1FAEC)
Bugcheck code: 0x1000007F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that a trap was generated by the Intel CPU and the kernel failed to catch this trap.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
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 12.2.2012 20:10:06 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini021212-05.dmp
This was probably caused by the following module: oadriver.sys (OADriver+0xE8C9)
Bugcheck code: 0x1000000A (0x0, 0x2, 0x1, 0xFFFFFFFF80522718)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\oadriver.sys
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: oadriver.sys .
Google query: oadriver.sys CUSTOM_ERROR




On Sun 12.2.2012 18:33:22 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini021212-04.dmp
This was probably caused by the following module: snapman.sys (snapman+0x1076A)
Bugcheck code: 0x1000007E (0xFFFFFFFF80000003, 0xFFFFFFFF804F0434, 0xFFFFFFFFBA4FF9F4, 0xFFFFFFFFBA4FF6F0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\snapman.sys
product: Acronis Snapshot API
company: Acronis
description: Acronis Snapshot API
Bug check description: This indicates that a system thread 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: snapman.sys (Acronis Snapshot API, Acronis).
Google query: snapman.sys Acronis SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M




On Sun 12.2.2012 17:08:17 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini021212-03.dmp
This was probably caused by the following module: avkmgr.sys (avkmgr+0x304A)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0x520045, 0xFFFFFFFFA8766BD9, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\avkmgr.sys
product: AntiVir Desktop
company: Avira GmbH
description: Avira Manager 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: avkmgr.sys (Avira Manager Driver, Avira GmbH).
Google query: avkmgr.sys Avira GmbH KERNEL_MODE_EXCEPTION_NOT_HANDLED_M




On Sun 12.2.2012 12:57:31 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini021212-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4E7C1)
Bugcheck code: 0x1000000A (0x1C, 0x2, 0x1, 0xFFFFFFFF805257C1)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 12.2.2012 11:09:24 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini021212-01.dmp
This was probably caused by the following module: scsiport.sys (SCSIPORT+0x1D82)
Bugcheck code: 0x100000D1 (0x157D7E2C, 0x2, 0x1, 0xFFFFFFFF8AD1AF7A)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\scsiport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI Port Driver
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.



--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

7 crash dumps have been found and analyzed. 3 third party drivers have 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:

avkmgr.sys (Avira Manager Driver, Avira GmbH)

snapman.sys (Acronis Snapshot API, Acronis)

oadriver.sys

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.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

[Roli]

Zdravím, to je zase nadělení.

Od ovladačů k základní desce přes antivir až po nějakou chybu v Acronisu.

Mrkni do Správce zařízení zda tam nemáš nějaké žluté vykřičníky.

Po té zaktualizuj ovladače chipsetu, možná Acronis a zkusil bych na nějaký čas odinstalovat nebo vypnout Aviru.

Také doufám že máš pouze jeden antivir a nemáš tam nějaké zkrášlovadla systému..

Průběžně piš co se děje.

[kuntakinte]

Jejda, promiňte že jsem se neozval, nevšiml jsem si odpověď. Každopádně rupli mi nervy nad tím PC a přeinstaloval jsem win, sformátoval disk, takže vše nakonec úspěšně šlape. Každopádně díky moc za všechnu pomoc, opravdu jste mi pomohli

[Roli]

No není zač