Yeah, sorry to hear about your issues. It especially sucks when you spend that kind of money on those cards. Like I said though there should be new drivers out shortly and they will most likely be focusing on the newer cards as a priority.
your system spec does not include much info but I would have a look at your power supply I am seeing many posts here of people trying to run these cards with power supply's not ample to run them you need about 40 Amps on a single +12 volt rail for a quad core system with a big video card and lots of ram but people are trying to do it with 18 amps then wonder why their system crashes
sorry i read all the way back to the original post i see you have ample power supply lol i was looking in your system specs at the bottom
are you actually using NOD32 i seen someone else had major issue with NOD32 and an ATI card same issue as you it turned out to be NOD memory leakage just some food for thought
How many times I have seen issues like this dissapear when adapted drivers came out. It's like SP's in Windows. Can't do a thing until SP.
Thought I'd post back here. I have a thread running at overclock.net, but I think everyone has ran out of advice, including myself.
The thing that I have established is that I'm definitely looking at driver corruption, or a modification that happens in the drivers when performing certain windows tasks. One could call it driver degredation, one that my card doesn't take kindly to.
How did I establish this?
Well, the issue was that the card works perfectly after a fresh driver installation, and starts locking up upon entering 3D, after I perform a seemingly random task in windows, like installing a program.
The way I was able to pinpoint the source more detailed is by the way I uninstalled the ATI drivers.
I first used advice that said, let the WDDM drivers sweep possibly conflicting files after an express uninstall of the ATI drivers. So I did, but this doesn't remove leftover ATI related files in practice. So after this procedure I reinstalled the catalyst drivers, and the problem persists. Meaning that the corrupted file wasn't removed and still present in the reinstallation.
If I express uninstall the ATI drivers, followed up by a driver sweep, and then a reinstall of the ATI drivers, the card works perfectly again. This means one of the files that I delete with driver sweeper causes the crashes. These are about 20 files, so I would have to make my card crash 1-20 times before isolating this file.
From what I've seen, these are all .dll files. So first off, to me this means that there's no workaround. I've tried the new 9.12 beta drivers today, and its the same. So its either an inevitable RMA somewhere in the future, or I'll have to make the card crash a lot of times to isolate the conflicting file.
I made logs in GPU-Z and recorded both gpus before a crash. Theres nothing out of the ordinary. there's not even really a load, or raised temps, or even Amps. Its just nothing. The card just locks up when entering 3D, like its triggering a fail safe without reason.
Though, I do have to mention that all this is with the A.I. setting to enabled. I can use the card with this setting disabled, but that kind of takes away the purpose of a dual-gpu solution.
have you tried a custom install and choose to only install the ATI driver I always choose not to install the CCC and I disable the AMD External Event Utility after installation
I have installed without CCC and HDMI sound drivers, and even shut down AMD External Event Utility and ULPS, but never in sequence.
So you think its possible that the AMD External Event Utility is capable of destroying drivers? Or does it just cause issues on its own? The crashes start for one, with 100% certainty, after the installation of software. Does that correlate with that service?
Quote
.
