• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Crossfire BSOD

|TheRock|

|TheRock|

Junior Member
Hi, looking for help; been searching for a few days now on a solution but have come up with nothing. I am running Crossfire with two HD 7970's, on is a XFX Double D (non-GHz version) and the other is a HIS (non-GHz) version. I can run windows and all applications with crossfire enabled until I try to run a 3D game; I have attempted to play many games, as well as run 3Dmark, but as soon as the application starts, I get this BSOD everytime:

2470.jpg


Here is my full rig specs:
-4770k OC'd to 4.6 GHz
-ASRock extreme6 z87 mobo
-Corsair H100i
-16 GB Corsair Vengeance 1600MHz
-XFX Pro850w PSU
-60 GB SSD for OS
-1TB 7200RPM WD Black
-2x HD 7970 Crossfire (specific cards above)
-Win 7 64 bit Ultimate

Here are the things I have tried:
1) Tried multiple AMD drivers (13.6 beta2, 13.8 beta, 13.10 beta, and finally a stable 13.4). Same issue on all driver versions. Was a clean install each time (manually deleted residual files in System32 and SysWOW64 folder).
2)Tried each card seperately; both work correctly by themselves.
3)Reversed order of Xfire configuration.
4)Changed xfire cable from first slot to second slot.
5)Turned ULPS (ultra-low power state) off in registry.
6)Expanded atikmdag.sys
7)Disabled AMD HD Audio.

(I think that's all I've tried, but it's hard to keep track at this point)
 
Last edited:
What anti virus/internet security are you using? have you tested the ram sticks with memtest?
 
I have installed the molex connector into that port; if nothing else works, perhaps I'll try and reseat it as it was very difficult to install with the PSU in the way. I'll try the new 13.9 driver this afternoon, when I get back from work, although I don't believe that would be the issue as I have tried multiple drivers, now.
 
|TheRock| said:
I have installed the molex connector into that port; if nothing else works, perhaps I'll try and reseat it as it was very difficult to install with the PSU in the way. I'll try the new 13.9 driver this afternoon, when I get back from work, although I don't believe that would be the issue as I have tried multiple drivers, now.
Click to expand...

The newest WHQL drivers appears to have fixed some issues with BSOD's. I am thinking it's something driver/software related. Especially since each card works without issue on their own.
 
|TheRock| said:
I have installed the molex connector into that port; if nothing else works, perhaps I'll try and reseat it as it was very difficult to install with the PSU in the way. I'll try the new 13.9 driver this afternoon, when I get back from work, although I don't believe that would be the issue as I have tried multiple drivers, now.
Click to expand...

The newest WHQL drivers appears to have fixed some issues with BSOD's. I am thinking it's something driver/software related. Especially since each card works without issue on their own.
 
Ok, so I've done the following without success:
1)Ran 2 passes of memtest86 with 0 errors
2)Made sure that the molex pci-express power connector to the motherboard was seated properly
3)Installed 13.9 stable
4)Found that there was more than one instance of enableulps in registry and disabled all of them
5)Saw a registry entry of enablecrossfireautolink above enableulps; I enabled all instances of this

No success so far... I'm thinking of doing a clean install of windows, but am looking for other suggestions before I do that.

EDIT: I've noticed that after I restart my computer that some of the instances of enablecrossfireautolink disable themselves but most remain enabled; anyone know what this means?
 
Last edited:
Have you tried running each card by itself? I know you have them both in there. But take #2 out, game a bit with #1. Then take #1 out, and put #2 in. I am wondering if one of them actually has a hardware issue. And enabling cross fire just enables that card and then you get the BSOD.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top