BSOD when enabling CrossFire in CCC

michaelgears · 20 Mar 2011

I have 2 Radeon 5870 cards running in CrossFire. I have to temporarily disable CrossFire when I run ONLY one modded game S.T.A.L.K.E.R: Call of Pripyat Complete Mod, vanilla runs with crossfire without any issues.

After I finish playing this game I go back to Catalyst Control Centre and re-enable crossfire and on 2 occasions my computer showed BSOD and rebooted.

I have Catalyst Control Centre 11.4 preview edition, this is unsigned driver meaning not certified by Microsoft.

I have not tried to disable/re-enable crossfire while using older drivers because there was no need for that.

This is how it happens, I open CCC select Performance | AMD CrossFire Configuration | check crossfire and click apply. Then screen goes black and fan revs up for a few seconds then it shows a portion of my desktop which appears to be cut up into little pieces and finally it causes my computer to reboot. Most of the time when I re-enable CrossFire it acts the same way except that it does not crash.

I never experience any issues while running the game, no lock ups, no BSODs (knock on wood). I will attach .DMP file.

Thanks,

mgorman87 · 20 Mar 2011

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800c215010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800498f408, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.

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


FAULTING_IP: 
atikmpag+7408
fffff880`0498f408 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`06ad29c8 fffff880`04145000 : 00000000`00000116 fffffa80`0c215010 fffff880`0498f408 00000000`00000000 : nt!KeBugCheckEx
fffff880`06ad29d0 fffff880`04144d0a : fffff880`0498f408 fffffa80`0c215010 fffffa80`0a5a5c50 fffffa80`0eb8f010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`06ad2a10 fffff880`0400ff07 : fffffa80`0c215010 00000000`00000000 fffffa80`0a5a5c50 fffffa80`0eb8f010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`06ad2a40 fffff880`04039b75 : 00000000`ffffffff 00000000`00060c0a 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`06ad2b20 fffff880`040382bb : 00000000`00000102 00000000`00000000 00000000`00060c0a 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`06ad2b50 fffff880`0400b2c6 : ffffffff`ff676980 fffffa80`0eb8f010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`06ad2bf0 fffff880`04037e7a : 00000000`00000000 fffffa80`0a5a5c50 00000000`00000080 fffffa80`0eb8f010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`06ad2d00 fffff800`02f39cce : fffff880`071c5690 fffffa80`0eb90b60 fffffa80`09d41b30 fffff800`02c94157 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`06ad2d40 fffff800`02c8dfe6 : fffff800`02e0ee80 fffffa80`0eb90b60 fffff800`02e1ccc0 fffff880`01239cb0 : nt!PspSystemThreadStartup+0x5a
fffff880`06ad2d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+7408
fffff880`0498f408 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+7408

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d69cc2e

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

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

This BSOD shows a video card error. Try removing all traces of your video card drivers using the program from the link below and then reinstall the newest drivers

http://www.guru3d.com/category/driversweeper/

Also, if your doing any overclocking on the cards, stop. And check to make sure they aren't overheating (check for dust and proper ventilation)

michaelgears · 20 Mar 2011

I am not overclocking the cards. During gameplay temperature fluctuates between 85 and 89 degrees. The cards are very close together, there is only enough space to insert a piece of paper. But I have Alienware Aurora system they probably knew what they were doing when they designed this case. Remember that BSOD only occurred twice and ONLY when I tried to re-enable CrossFire. During gameplay I experience no issues.

mgorman87 · 20 Mar 2011

I only see one BSOD in the file you uploaded.You can try what I suggested anyway. It's not going to hurt anything. Also, can you update your system specs.

http://sites.amd.com/us/game/downloa...n_win7-64.aspx

Try using the public drivers. Maybe the unreleased 11.4 are causing the issue

mgorman87 · 21 Mar 2011

STOP 0x116: VIDEO_TDR_ERROR troubleshooting