Atimpag.sys - BSOD

[marc69]

Hi guys,

My rig is as follows:

I5 2500k @ 4.5ghz
Asrock Z68 extreme 4
8 GB Gskill Ripjawx
2x ATI 6870s (not overclocked)
XFX 750w PSU

I keep getting this annoying blue screen of death which seems to be completely random. I'd been playing BF3 for a good 2 or 3 hours and then out of the blue (excuse the pun) the BSOD occurs.

I have no idea what to do, I've been googling around for endless amounts of time and I've still not reached a conclusion.

The temps on the cards never exceeds 70c
CPU - Around 60 / 65

Few logs:

On Sat 05/11/2011 20:13:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110511-21684-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x780C)
Bugcheck code: 0x116 (0xFFFFFA800CF9E4E0, 0xFFFFF8800419080C, 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 05/11/2011 20:13:00 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl!TdrResetFromTimeout+0x214)
Bugcheck code: 0x116 (0xFFFFFA800CF9E4E0, 0xFFFFF8800419080C, 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.

No idea what to do now really.

RMA the cards maybe?

Cheers,

Marc