Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: BSOD when enabling CrossFire in CCC

20 Mar 2011   #1

Windows 7 Ultimate 64-Bit
BSOD when enabling CrossFire in CCC

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.


My System SpecsSystem Spec

20 Mar 2011   #2

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64bit

*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Attempt to reset the display driver and recover from timeout failed.
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:

fffff880`0498f408 4883ec28        sub     rsp,28h






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

fffff880`0498f408 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+7408

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys


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

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)
My System SpecsSystem Spec
20 Mar 2011   #3

Windows 7 Ultimate 64-Bit

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.
My System SpecsSystem Spec

20 Mar 2011   #4

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64bit

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.

Try using the public drivers. Maybe the unreleased 11.4 are causing the issue
My System SpecsSystem Spec
21 Mar 2011   #5

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64bit

My System SpecsSystem Spec

 BSOD when enabling CrossFire in CCC

Thread Tools

Similar help and support threads for2: BSOD when enabling CrossFire in CCC
Thread Forum
[BSOD] Enabling Crossfire on Catalyst newer than 10.11 BSOD Help and Support
BSOD error 0x000007e when enabling SLI BSOD Help and Support
Crossfire BSOD BSOD Help and Support
HD 6870 Crossfire BSOD BSOD Help and Support
Crossfire 5770 bsod BSOD Help and Support
BSOD after Enabling LMCompatibilityLevel value in Registry BSOD Help and Support
[BSOD] Crossfire on Windows7 x32 BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 07:50 PM.
Twitter Facebook Google+

Windows 7 Forums

Seven Forums Android App Seven Forums IOS App

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33