Quote Originally Posted by Maxwell View Post
Ok. So did the whole "Restore Defaults" thing like Harley suggested, and checked Afterburner, and everything appeared to be at stock, including voltages. I tried the "test custom clocks" with settings at stock settings after restoring defaults, and it failed (it shouldn't). Then I decided to go a little loco...

I backed the memory clock down to 500, and the GPU clock down to 575 in CCC. This is from stock settings of 1000 and 725, respectively. Tested these custom clocks, and it passed. Put them on MW for about 45min, then emptied the cache. All went well.

Uninstalled the driver, swept, reinstalled the driver, to see if that changed something internal to the card. It didn't because when I tried the "test custom clocks" thing again with default settings, it failed again.

I'm now uninstalling completely again, and I'm going to switch the location of the two cards, and see if that can get something going...
Maxwell, hold your horses please. Something is really wrong here. Like it takes a rocket scientist to figure that out...... Where is Dr.Von Braun when you need him?

I strongly suggest you do the HDD swap with a fresh install of Win7. Remember you do not need to activate it for 30 days.

Damn, new thought leads to new question: Did you just recently install any new M$ updates? I just remembered SP1 for Win7 came out like 2 or 3 days ago. This could be your culprit. So do the HDD swap but do NOT update. Install CCC 10.10 without APP, just to see what happens. Install BOINC and crunch. You can use the BlackOps group account so it won't mess with your CPID. I will add Collatz, MW & DNETC to it.

If it works then you can install all the M$ updates dated before the first of the year and crunch some more. Then update CCC to 11.0 and test again. You need to find the point of failure. Just keep adding sets of updates until it BSODs. This will give you a target.