Unstable Overclock problem

[mayheamk]

Hi
My overclock setting have recently become unstable causing applications to freeze. I have captured pictures of my bios setting and in hope of getting some help regarding readjusting them. Thanks so much.









My space:
Intel i7 950
EVGA X58 FTW3
EVGA GeForce GTX 580
6GB DDr3 1600: http://www.newegg.com/Product/Product.aspx?Item=N82E16820145289
Crucial Real SSD C300
850W PSU AXcrossair
Cooler master V8

 

[smarteyeball]

Recently become unstable - how recent? And is it triggering any crash dumps, or is it always a freeze?

Do you recall updating any drivers around the time it started (video/sound etc)

How long have they been at those settings and stable and what makes you think it's the OC to blame?


Normally you'd bump up the vcore a notch or three if it was CPU degradation. Ram dosen't need to have the voltage upped.

Yet none of those settings look 'degradation' causing :huh: (nothing obvious anyway)

The RAM is undervolted, and the vcore is reasonably 'low'.


Start with a memory test with memtest86+ - 6-8 passes. Either eliminate/confirm if it's a memory issue.

Depending on that outcome, we can start looking at other angles.

 

[mayheamk]

I have recently updated my sound drivers, other than that just the usual video card update every month. I set my vcore to 2.9 while i changed ICH Vcore and VTT to auto.

 

[mayheamk]

I just set everything back to default and the system still crashed and that shows me that the problem isnt the overclock. what happend is when i open a video game application after few second-minutes the screen goes black i would have sound for 1-2 second and nothing more. Could this be a ram issue maybe? or motherboard? i find it unlikely to be the video card seeing as how i recently got a same new video card from warranty..

Here is also what i get when i come back to windows.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 116
BCP1: FFFFFA800A5B9010
BCP2: FFFFF8801014A1A4
BCP3: FFFFFFFFC000009A
BCP4: 0000000000000004
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\081012-15506-01.dmp
C:\Windows\Temp\WER-28704-0.sysdata.xml

 

[smarteyeball]

I have recently updated my sound drivers, other than that just the usual video card update every month.

Two potential culprits right there.

I set my vcore to 2.9

I hope that's a typo or a mistake.

A cpu voltage/vcore of 2.9V will kill a chip. 1.45v is the max you want to use. If it's not a mistake and that's your actual vcore - go into the BIOS RIGHT NOW and change it. Even if you put it on AUTO for the time being.

Maybe the 2.9 is your clock speed?

I just set everything back to default and the system still crashed and that shows me that the problem isnt the overclock.

No, I'd say it's most likely software/drivers at this stage.

Could this be a ram issue maybe? or motherboard? i find it unlikely to be the video card seeing as how i recently got a same new video card from warranty..

Ram, perhaps. There's always a possibility of a module going bad. (although I doubt it's the case). I doubt it's your mobo at this stage.

To rule Ram out though, you could always run Memtest overnight.

what happend is when i open a video game application after few second-minutes the screen goes black i would have sound for 1-2 second and nothing more.

BCCode: 116

Tbh, that symptom and that error code points to the GPU or drivers. The screen blacking out sounds like the video driver has stopped responding.

x116 codes are usually TDR issues(Timeout Detection Recovery).

Are you running the 301.42 drivers?

(I've found them to be stable, but I have a different gen of card)




For testing purposes I would roll back to a previous 'known to work' set.

Also, I'd probably roll back the sound drivers too.



If the problem goes away with the older, known to be working drivers - then update either the sound or video drivers one at a time. If you re-introduce the problem, you'll know which ones the culprit.

If the problem doesn't go away by rolling back the drivers - then it's time to consider other angles like faulty components.