BSOD when playing games or watching flash videos

Hi guys, basically my old 6870 card died because of numerous BSODs it had over the 6 months throunh flash videos and it killed it with artifacts.

I have recently received a brand new XFX 6870 and have been using it over a month and its been happening again with flash videos as occasionally get BSOD randomly like 30 mins or even over an hour. which is pointing out
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\atikmpag.sys

and

Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\dxgkrnl.sys

its even happened once last night on a game FIFA 12 which restarted and had this error
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe


How will I be able to eliminate these problems? my system specs are below and I have built this system over 8 months and nothing is overclocked.

cheers

I've even got it on the desktop when just running IE
the same error below
On Sat 30/06/2012 11:03:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\063012-24788-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0xFFFFF680003BEFE8, 0x0, 0x0, 0xFFFFF800020CFB2B)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 30/06/2012 11:03:20 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFF680003BEFE8, 0x0, 0x0, 0xFFFFF800020CFB2B)
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

Hello GTO and welcome to Sevenforums.

BSOD Analyse

Memory Related or Driver related

Looking at your bugcheck it's likely that a memory corruption event were there. Though a driver could be causing the memory to be borked, but we're usually suggesting a memory test before moving forward. Do a scan with Memtest86+. Memtest is a scanner that'll check your sticks for errors. To ensure that we'll know if it's the slots on the motherboard that's broken, or the sticks itself - we have a little procedure we'll recommend. Remove 1 stick, scan the other with Memtest in the current slot. After 7 passes, move the stick to another slot and scan, and so on and so forth until you've scanned all the sticks, and all the slots, one by one.

Memtest86+ - Advanced Memory Diagnostic Tool

BSOD Summary

Cheers,
Frederik.

HI thanks for replying, well after what you said I ran memtestX86 on USB, tested both RAM on the slots and to 7 passes and no errors. what should I do next??

Thanks

GTO656 said:

HI thanks for replying, well after what you said I ran memtestX86 on USB, tested both RAM on the slots and to 7 passes and no errors. what should I do next??

Thanks

Click to expand...

Let's do some Driver Verifier.

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "IRP Logging", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next" (​

"Special Pool" may be able to be used depending on amount of RAM and errors being seen. In situations with small amounts of RAM, DO NOT select it),​

- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and ​

locate the memory dump file. If present, ​

turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page. Then, zip up the memory dump file(s) and upload them with your next post. If no dump files were generated, post back for further suggestions.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Code:

Delete these registry keys to stop Driver Verifier from loading (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

​

Click to expand...

Best Regards,
Frederik.

Sorry for the late post, I've received another error too yesterday:

On Sat 14/07/2012 23:37:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071512-30326-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x423F9)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800020433F9, 0xFFFFF880009A99D8, 0xFFFFF880009A9230)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 14/07/2012 23:37:22 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF800020433F9, 0xFFFFF880009A99D8, 0xFFFFF880009A9230)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time

Hello,

Are you able to upload the dumps?

Also do the following-
i) Make your way to ATI Drivers - Downloads and download the latest driver for your card, save it to your desktop for instance
ii) Uninstall the Graphic driver you currently have and all its extensions (do not reboot yet)
iii) Download Driver Sweeper
iv) Get to safe mode (without network) and search for Driver Sweeper in your rb:
v) Select all the ATI components and analyse them
vi) Clean them, head into Windows without internet and install the driver you've downloaded previously

Drivers to be aware of

AsIO.sys
ASACPI.sys
athrx.sys
amdiox64.sys
amdxata.sys
ntk_PowerDVD_64.sys
000.fcl
speedfan.sys
Rt64win7.sys
AODDriver2.sys
cpuz135_x64.sys
AtihdW76.sys
aswFsBlk.SYS
aswMonFlt.sys
aswTdi.SYS
aswRdr.SYS
aswSP.SYS
aswSnx.SYS
atikmpag.sys
atikmdag.sys

Best Regards,
Frederik.