q6600 restart on high overclock?

T

tissimo

Limp Gawd
Joined
Dec 8, 2007
Messages
318
Well, I've been messing with my system all weened trying to get the most I can out of it, and it doesn't want to go over 3.2ghz at all. It runs perfectly fine at 3.2ghz (8x400) 1.3v ~ 55c full load. But it wont go higher.

When I try to go higher about 3/4 of the time Itll just restart, instead of erroring out of Prime95. I'm not sure if I have a setting wrong or something. It seems odd that itll just restart rather then error in prime, no matter what I do.

For example, I had it running @ 3.4ghz (9x378) 1.36v and it ran prime for an hour fine full load ~60c (a little high i think?, but room temp is ~ 26-27 :( ) then out of no where it just restarted? no prime errors or anything.

Do you think i've just hit my limit?
 
If it will run a 400 FSB and you get a BSOD or something while stressing it out, you most likely need some more voltage before you can go higher. More voltage means more heat...better cooling needed.
 
i tried 3.3 1.36v last night, it lasted an hour in prime. So figured I'd try 3.4 again with more volts... ON EVERYTHING, haha.. 1.42 cpu, 1.4 chipset, 1.27 cpu vtt (i think), ran for another hour in prime95 with no errors. So tried to run 3dmark and after the frist test BSOD and restart.

I said f'it before I went to bed and gave 3.6 another shot with even more volts. 1.49v core, 1.45 chipset, 1.32 cpu vtt. It ran for ~ 30 minutes no errors, then BSOD and restart.

I think i've just hit my limit. 3.2 is good enough I suppose. :(
 
at 3.6 was ~ 62-63.. it was much cooler last night (cool front just came though, so room was ~ 74-75*f / ~23*c rather then the 26-27 it was earlier)
 
restarts are more indicative of memory/chipset problems than cpu hitting it's limit. Everytime I've pushed a CPU beyond it's overclock limit, I simply get prime errors or hard locks and am forced to reboot myself.

I've even done some suicide testing for my cpu at 4ghz, cpu-z verified (prime failure though lol)

edit: A thermalright ultra 90 will not push enough heat beyond 3.2ghz and high voltage, while a ultra 120 and ultra 90 may seem similar up to certain load temps, it is the higher load temps that the ultra 120 excel at. What reviews fail to mention or demonstrate with their testing is that a q6600 at lower speeds can push as much heat as their testing at 3.9ghz.
 
tissimo said:
Well, I've been messing with my system all weened trying to get the most I can out of it, and it doesn't want to go over 3.2ghz at all. It runs perfectly fine at 3.2ghz (8x400) 1.3v ~ 55c full load. But it wont go higher.

When I try to go higher about 3/4 of the time Itll just restart, instead of erroring out of Prime95. I'm not sure if I have a setting wrong or something. It seems odd that itll just restart rather then error in prime, no matter what I do.

For example, I had it running @ 3.4ghz (9x378) 1.36v and it ran prime for an hour fine full load ~60c (a little high i think?, but room temp is ~ 26-27 :( ) then out of no where it just restarted? no prime errors or anything.

Do you think i've just hit my limit?
Click to expand...

Do you have a B3 quad or the G0 quad???
 
Its a G0 , I got it from Club-it.

My temps arn't that high. It was only reaching 62-63*c after about 20 minutes in prime @ 3.6. Its a little higher then I would like though (would like to stay under 60). mid 50s at 3.2.

Maybe I'll take out 2 sticks of ram, I've read that there can be some issues with have 4 sticks. I'll mess around with more.
 
Slade said:
restarts are more indicative of memory/chipset problems than cpu hitting it's limit. Everytime I've pushed a CPU beyond it's overclock limit, I simply get prime errors or hard locks and am forced to reboot myself.
Click to expand...


This is very interesting, as beyond 2.92 I cannot get a stable clock. However, to reflect on your comment, most of the POST-stable clocks, for example, 3.8, 3.6. and 3.4, have failed to boot Vista 64, but have NOT locked. They are usually reboots at either the end of the black-screen boot sequence, right before the login prompt comes up, or right after I try to log into the OS.

If your restart assumption is correct, then I should leave the CPU where it's at, say 3.6 and focus on the RAM / CHIPSET? Hmm..
 
Yes, play around with the RAM and chipset voltages. I continue to be surprised about the amount of people who do not touch anything but the Vcore and then they will ask why things do not work...
 
if it was me I'd put the CPU at stock speed or under, re-run your testing and start to narrow down other possibilities
 
Justintoxicated said:
if it was me I'd put the CPU at stock speed or under, re-run your testing and start to narrow down other possibilities
Click to expand...

Its funny you mention that. My board will give "Bad CPU or impropely installed" POST error if I try everything at stock... Its kinda funny, actually..
 
Well, a little update. I gave 3.6 ghz another shot and BSOD & restarted in the same place as it did last time in 3d mark. So I was looking at my bios and tried disabled 2 more cpu features (execute bit disable or something, and virtualization technology) and tired 3.6ghz again. When through 3dmark fine with no errors. I got a 1407x score too :)

So currently messing with my settings to see if I can get this stable. So far been going an 45 minutes though prime and no errors. Though temps are a little bit higher then I want (~60-62*c, but my room is like 23-24*c and it usually isn't this cold. so probably will try a lower clock (3.4) and try to get that stable under 60*c).
 
You will want to re-enable execute bit disable as it has to do with Anti Virus software, or how the Operating system reacts to malicious code, or something like that..

You can leave virtualization techonolgy disbaled unless you use Vmware or something similar.

I still notice you have yet to say anything about your RAM Voltage, North bridge voltage or MCH Voltage. (Or any other voltage other than the Vcore) What are you setting these to? Also what about the RAM Timmings?
 
Blueagle87 said:
You will want to re-enable execute bit disable as it has to do with Anti Virus software, or how the Operating system reacts to malicious code, or something like that..

You can leave virtualization techonolgy disbaled unless you use Vmware or something similar.

I still notice you have yet to say anything about your RAM Voltage, North bridge voltage or MCH Voltage. (Or any other voltage other than the Vcore) What are you setting these to? Also what about the RAM Timmings?
Click to expand...

I will try it later to figure out which setting was giving me problems. I've tried several northbridge voltages. I'm currently running 2.2V ram voltage as called for by their specs. I was underclocking them most of the time and using 5-5-5-18 timings when they can run 800 mhz at 4-4-4-12. I've previously ran them at those settings and speeds without problems before.

I got it running 3.4 (426x8) @ 1.36v, 1.4v northbridge voltage, 1.27 cpu vtt, 2.2 ram volts, 4-4-4-12 timing. It Ran prime for an hour then I played an hour of crysis demo and no bsods or lockups. Load temps were ~ 57*c.

Maybe over the christmas break I'll try lapping my cpu and heatsink and try for 3.6 again.
 
You must log in or register to reply here.
Back
Top