BSoD ONLY when Overclocking. Persistent issue.

DominicMendonsa

Honorable
Jul 9, 2012
15
0
10,510
I prayed I'd never have to come back here but lo, I once more need the help of my fellow TomsHardwarians. Assemble!

Windows 7 64-Bit
2x XFX HD 7870's DD's
Zambezi 6-Core @ 3.8GHz Stock
16GB of 1333GHz RAM Ballistix by CRUCIAL
Coolmax 1000B 1000W PSU
HP w2338h Wide LCD Monitor(23")
Crosshair V-Formula ROG Mobo
Most recent ATI driver (Mid of december or something like that... I think the 20th)(Just updated it)

>I started receving BSoD's immediately after I installed and played the BF4 Closed Beta back in September/August or w/e.
>I loaded up the game with my stuff overclocked and it crashed.
>I tried for a week to play BF4 but eventually gave up. I've yet to buy it and don't plan to at this point.
>Went through this whole fiasco of checking if it was the CPU/GPU causing the issues.
>DICE later confirmed something but I couldn't remember. No matter.
>Uninstalled BF4

>Tried playing BF3 again which at that point I hadn't played since roughly June and last I remembered, it ran fine when I was OC'ed and everything. I always played it OC'd. No problems ever before.
>Bluescreen
>Continue trying to play with OC but consistent BSOD's.
>Capable of playing with non-OC'd so I did that until October when I stopped playing again.
>Started up my Youtube channel in November and started making videos again.
>Every now and again, my display driver will stop working while I'm rendering a video. Typically when I'm trying to do something else like watch a youtube video or play a game. Makes sense since it's PURE rendering and I was probably just exhausting the GPU. I no longer do anything while rendering to let it handle it's stuff on it's own.

>Faster forward to now. (1/7/2013)
>I've recently re-installed Planetside 2 for the 6th time after my clan telling me they FINALLY optimized it to be playable on AMD.
>Planetside 2 delivered non-OC'd. 90FPS average
>Decided today to try and OC to see how it works forgetting that I've since had this issue.
>Bluescreen.
>Kinda irritated at this point.

How do I OC? Well, my standard OC'ing suit since I got these cards back in April was the following:

http://puu.sh/6cGFC.png

I'm a pansy OC'er so I just did it a little.
I increased the GPU Clock from 1000 to 1200
I increased the GPU MemCLock from 1200 to 1400
I increase the fan speed from Auto(45-50) to 70.
I used to increase the PCS to 5% but later learned that it didn't really make a difference for me so I just leave it at 0% now.

Both cards look like this and it's run just fine since I got the cards all the way til September. How do you know it's the OC'ing specifically? Because I've only BSoD when enabling these OC settings that I had prior been using for months with zero problem. I first noticed the pattern when I was trying the BF4 CBT. It wouldn't BSOD when not OC'ed though the game would freeze and it was because of gubbins optimzation for AMD processors that DICE admitted. It was happening for everyone. But when I tried to run it OC'd, it'd BSoD. I even tried doing it in small increments of only +50 to Clock, Mem Clock, and +10% on Fan Control. It'd BSoD on even those low settings.

So, since that day I haven't really touched my OC'ing utility in CCC. I occasionally try OC'ing forgetting about the issue only to be met with a BSoD and then I proceed not to touch it anymore. Well for whatever reason, I decided that today is the day I try to figure this out.

So where am I at right now?

Since the BF4 incident, I've Pansy-OC'd my ram to 1600GHz up from it's stock 1333. These sticks have a Turbo of 1866. I've also used CPU Overdrive in CCC to overclock my CPU from 3.8 to 3.9. Again with Pansy OC. It just makes me comfortable. Ever since, it's ran fine.

Whenever I enable my old OC settings, that I used to run just fine all the time until September of 2013, playing a decently demanding game will cause me to BSoD. I forgot that I was on OC'd settings when I was playing Hammerwatch today and noticed I wasn't crashing. Awesome. I'm glad I can play by 32 bit games while OC'd :D!... -.-

Before I came to these forums, I did a little crawling of my own because the BSoD is the standard 0xa0000001 or w/e which typically entails drivers issues. That persuaded me to update my drivers today, once again, they're the drivers that were released in mid-December. No dice. People also said it could be because of shitey voltage so I increased the voltage on each card to 5%. No dice and one last time at 20%. No dice.

I can literally overclock by no more than 50 on Clock and Mem Clock speed and still get a BSoD. It seems that if I'm overclocked in the slightest, my computer will fail. I've done memtest already and it came up clean. You can rule that out.

Here are my lazy guesses because I'm tired and don't care to think very hard at this moment in time:

-Driver issue(Duh).
-OC'ing Utility Issue
-Crossfire/Crossfire Bridging issue

Other than that, I have no clue. I'm completely baffled for an answer because even a mere and minuscule overclock(not like mine were minuscule enough) of 50 will cause it to crash. Because of how pathetic that is, that's why I'm more convinced that it's a utility/driver issue rather than an issue with the card... cuz that's ridiculous. The cards don't overheat nor does my CPU.

What do, TomsHardware? What do?

Please be very detailed with your suggestions or questions. As a frequent troubleshooter, I detest milling a lot of time on small responses. If you can, when you suggest things, suggest back up things dependant on the answers you're expecting from me.

Like if you were to ask me what 1+1 is as a start? Don't wait for me to respond, provide further steps dependent on if I'd give you the answer of 0 or the answer of 2. 0 meaning that I'm an idiot that can't do math or 2 meaning that we can keep going.

Make sense?

If you're going to suggest that I clean wipe my drivers or any other moderately lengthy series of tweaks, please provide links and detailed descriptions/walkthroughs on how to pursue them so I'll have to make one less trip to the forums and can get you the results faster. Im sorry if I seem pushy about thsi but I get mixed suggestions about what to use and how to use it from multiple forums so PLEASE provide as much as you can in a single post, hell, even multiple suggestions, so I can test the brunt of the standard tweaks and get back to you with MORE answers so you don't have to waste your time coming here as well.

Thanks, guys! :D
 
Well, not to sound like a jerk, but if you are a frequent troubleshooter, you should know that overclocking is luck of the draw. You might have just gotten the opposite of the silicon lottery.

My first thought is what are the temperatures of the card, and how good is the airflow? Since I cannot possibly list all of the possibilities, please forgive me for not answering your questions for you. I'm sorry if you have to waste your time reading over this, I just detest people who come looking for help whilst trying to make the people they want help from feel stupid.

If temperatures are fine I would pretty much be confident you just have a bad luck chip that is already pushed as far as it will go. However, have you tried running Memtest to test your RAM? If the RAM tests come back ok, I'm again leaning toward just a bad luck of the draw on the chip.

The last suggestion I would try if everything tests out fine would be to reset the motherboard. To do this, unplug your CPU, remove the side panel, locate the CMOS battery on the motherboard (looks like an oversized watch battery), remove it for about a minute, pop it back in and try again.

If all of that fails then I would be 99% sure you just have a bad chip.
 

DominicMendonsa

Honorable
Jul 9, 2012
15
0
10,510


You don't sound like a jerk. Not at all. But at the same time, I didn't come here to waste other peoples time with all the question asking. After years of doing troubleshooting I know the basics that will be requested of me both in terms of specs and already attempted methods. I never make a short "Help me" thread because there's a lot of ground to cover.

I already provided all the information thus far when it comes to specs. I also did mention that I did a memtest which was fine. And this isn't a recent overclock. These overclocking settings I posted have worked flawlessly for months in the past. One of the biggest questions when answering one is "When did you start noticing this happening?".

It literally first happened in a crash during the BF4 CBT. While I can understand Overclocking is a luck of the draw type of thing, there was already proof that this once worked before which is why I'm circling EVERYTHING else before it comes to the cards.

If it came slowly overtime, I'd jump to the cards more quickly. But this all started almost INSTANTLY after trying to BF4 CBT.

The way I handle issues is Software>patches>Registry>hardware... hardware, like you said with the Mobo, being the end-all-meets-all. Where I can understand where your're coming from that I sound like I'm trying to make people feel stupid(which I'm not), I've also had too much experience with troubleshooting forums and one thing helpers hate the most is having to ask the stupid questions. So as a courtesy to them, I provide AS much information as I can. Over years of troubleshooting, I've learned a lot of methods, some advanced and some not, that I perform and provide results or testimonies for in my "Request for help" posts so it's one less step that we have to go through and one less thing you need to be asking before because I've been on the answering end as well and I hate asking the same questions over and over again.

So, again, it's courtesy thing that I provide as much information as I can both for the helper and for my own sanity and I do it out of respect for the helpers time. And for the record, I don't feel like MY time is being wasted because I'm on the computer all day but I absolutely HATE wasting other peoples time. I hate it.