************ Official 39XX Overclocking Thread ************

So long, fair well.

I have decided to go back to my 2500K + Z68 setup.

I have reached a point where I just don't get any pleasure out of this setup. I guess I have learned that the extremes are not for me, and would prefer to keep to a good, yet modest setup.

Less heat, less noise, less hassle, less expense. I just never had any issues with my last setup, and while my most recent issue is likely not related to mobo/cpu/memory, I have had enough.
 
eyetrip said:
So long, fair well.

I have decided to go back to my 2500K + Z68 setup.

I have reached a point where I just don't get any pleasure out of this setup. I guess I have learned that the extremes are not for me, and would prefer to keep to a good, yet modest setup.

Less heat, less noise, less hassle, less expense. I just never had any issues with my last setup, and while my most recent issue is likely not related to mobo/cpu/memory, I have had enough.
Click to expand...

:(

I'm having fun with my rig at the moment by actually using it. But will go back and tinker some more soon i'm sure :P just can't take any more of the 30minute IBT tests between settings lol
 
Last edited:
Glad your'e enjoying.

My problem is, things HAVE TO work how I want them... when they don't, it just gets in my head and causes me stress.

I know it's silly, but I can't help it.

My original plan was to just get 3770K when they came out. May still do that, but likely just sticking with 2500K for now.

And going back to single GPU. So will either stick with the Asus 7950, or just get whatever is the single most powerful card out right now.
 
eyetrip said:
Glad your'e enjoying.

My problem is, things HAVE TO work how I want them... when they don't, it just gets in my head and causes me stress.

I know it's silly, but I can't help it.

My original plan was to just get 3770K when they came out. May still do that, but likely just sticking with 2500K for now.

And going back to single GPU. So will either stick with the Asus 7950, or just get whatever is the single most powerful card out right now.
Click to expand...

I understand, i was getting stressed out at not being able to get 4.6GHz how i want it, had to settle for 4.5GHz instead.

Get the 690, you know you want too :P
 
Ah, joy...

Got everything swapped back, but decided to keep the phanteks for the 2500K.

At stock, getting temps at 54 to 61 :(

Guess will be opening up again in no time!
 
Sorry to hear that you've abandoned, eyetrip, but I bet you'll be dissatisfied with the 2500k now. I've knocked back to 4.2 for the fan noise in the warmer days and I still can't get enough of this thing, it's sweet.

I have to say that the doubts about the robustness of the C2 stepping have persuaded me to stay well within voltage and temp spec. I don't want to break it :)
 
Yeah it is a golf!!!

Who needs sleep, clock while your alive, Sleep mode when the board is dead!!! lol

This is a known problem mate but you can get a stable 4.7 I am sure.
 
Last edited:
Is the sleep mode bug just a quirk of the RIVE? I maybe leaning back to the extreme over the formula, not a big user of sleep anyway.
 
JeffyB said:
Is the sleep mode bug just a quirk of the RIVE? I maybe leaning back to the extreme over the formula, not a big user of sleep anyway.
Click to expand...

I think Asus in general to be honest. Asus P6T Deluxe had it as well anjd i bet my Sabertooth does at higher overclocks.

eyetrip said:
Man, I must have some serious mental issues....

I just put it all back in this morning...

Something wrong with me!
Click to expand...

You're a nutjob :p
 
Odd never experienced that with my p6t deluxe v2 and i clocked that to 4.6 with a 920 d0. Not a deal breaker anyway.
 
Just going to keep clocks modest for now.

4.4GHz at 1.3V, with memory at 2133 @ 11-11-11-1t with 1.475V.

Keeping to 4.4 for now to test how things go once pll resets after sleep.
 
Hush you!

:D

I will up it again some time.

I will make a note of nagging Asus people to get it fixed.

I know it can be fixed in BIOS, as someone posted a custom bios with it fixed. I would use it, but the BIOS was not the most stable on my system, despite being derived from 1305.
 
Taking my time seeing if there is a combination of things which sets off this pll issue, and have discovered there is.

I disabled pretty much anything with an auto and gave it a value, tried resuming and pll did not drop.

So now I got to try re-enabling one thing at a time to find out what it is.

First thing I tried was going back to offset, from fixed 1.3V, and pll still kept after resume

Not going to let it stress me though.
 
A lot of patient testing (being sure not to let myself get aggrevated over anything :) ), truns out it is somehow memory related. So I owe 8Pack and couple of other people apology.

It seems to be when the memory is clocked to 2133.

Oddly though, I was sure I had tested this memory with even just one stick at 1333mhz and experienced the same issue.

Oh well, perhaps some future update will fix this, as I know it can be addressed ina BIOs update. Just means am restricted to 1866MHz on memory for now.
 
Last edited:
eyetrip said:
A lot of patient testing (being sure not to let myself get aggrevated over anything :) ), truns out it is somehow memory related. So I owe 8Pack and couple of other people apology.

It seems to be when the memory is clocked to 2133.

Oddly though, I was sure I had tested this memory with even just one stick and experienced the same issue.

Oh well, perhaps some future update will fix this, as I know it can be addressed ina BIOs update. Just means am restricted to 1866MHz on memory for now.
Click to expand...

How very peculiar! Yeah it has to be a BIOS issue surely. Glad you've found the reason though :)
 
So am I

That itch is now firmly scratched!!!

Now got to set my OC up again though. Going to aim for 4.6GHz this time with memory at the above 1866MHz. Fairly modest, but as long as it's stable, I will be happy.

Though I just realised I didn't test for the same behaviour with hyperthreading off.
 
You must log in or register to reply here.
Back
Top Bottom