First OC attemp - looking ok?

GirMoose

GirMoose

GirMoose

Associate
Joined
26 Aug 2008
Posts
80
First OC attempt - looking ok?

Hey folks,

I decided that my computer had gone non-overclocked for too long, so started reading and fiddling with it today.

I have a q6600 g0 and a p5q-e with 8gb (4x2gb) of corsair ram (6400c4dhx). I set the bios up to be 333 fsb speedstep off etc. and all seems to have gone well enough to begin with, but I am a bit unsure of one thing. I set the cpu voltage at 1.3000 in the bios, but in cpuz it registers at 1.224. This just seems like its a long way off. And if it is normal, does that mean that I can basically pump the voltage in the bios up higher than the recommended amounts, as long as cpu-z shows it below the 1.3600 that i (rightly or wrongly) think is the max I should aim for?

And one more thing, the temps - They seem a bit high in general. I dunno exactly what to expect (using a sunbeam core contact cooler i think its called). As you can see from RealTemp, it doesn't go up too much from the lowest temps shown (idle), so maybe its just either a hot chip or i suck at mounting the heat sink (this is my 3rd go at it). I assume though that if it was a bad mounting, the temps would skyrocket under prime95 large ffts. Case is a Akasa Eclipse and I replaced the case fans with those new Akasa Apache fans.



added the pic as a thumbnail link, so as not to stretch the forums width with a huge pic.

-GiR
 
Last edited:
I have the same processor with the same GHz setup. Your temperatures seem fine to me (says its above 50 at load on the pic?) which seems perfectly acceptable to me. Your temperatures are very similar to mine, I have speedstep enabled to keep temeperatures and power consumption down while my cpu is idle.

As for the voltage, to get 3GHz with my q6600 G0 I left it at stock voltage (1.325V) with FSB 333. I think a 20% voltage increase from (As long as you can keep cpu stays cool) is acceptable. That voltage diference your seeing happens to me too, I think its called vdroop or vdrop? something like that. Seems to happen to many people.

What speed are you aiming for?

(off topic- I love that dock thingy you have in the background and the big clock, what program is that?)
 
Last edited:
I don't really have a target in mind yet, was just interested to see what I could do. I thought that 1.2500 was the default for some reason for voltage, so I guess I actually set it to undervolt and oc'd it to 3GHz, so thats not so bad for now! I'll do some more in the morning when I get back from work (damn night shifts).

If I go to 355 for a 3.2GHz it blue screens upon the prime95 test, so I guess I'm at the limit for the voltage there, but I have some decent headroom with it.

I'll post an update in the morning if I manage to get anything better :)


-offtopic- The dock is Rocketdock with the Stacks Docklet and some icons i found on deviant art (think they were called Balloons or something similar). The big clock is Rainmeter with 10-ft HUD settings. -/offtopic-
 
Last edited:
Ok, put it up to 3.4ghz now, upped the vcore to 1.36 (is 1.336 in cpu-z) as you can see below in the bios settings. I also set the ram timings to 6-6-6-18 incase it was causing problems as im using 4 ram slots and i have heard tell that sometimes that can cause the ram to need to run slower to avoid problems.

With these settings, my temps peak out at about 65 degrees on the hotter cores and around 58-60 on the cooler ones.

However, it fails large ftt in prime95 almost instantly on the 2nd core.

Is there something I'm missing / doing wrong here? Also - cpu-z keeps showing my multiplier dropping to 6, however I have set speedstep to disabled and then manually set the multiplier to 9. Any ideas why this is happening?

Pics below:

img0041ssl.jpg

img0040hnj.jpg

img0040akg.jpg


Apologies if they are too big :/

-GiR
 
Well at 1.4000 in the bios I get 1.392 under load in cpu-z.

This seems potentially stable @ 3.4Ghz, none of the cores have failed right away, temps are at 68, 67, 61, 60 after 8 mins of prime95 large ftt.

I was hoping to get to 3.6 once it did 3.2 so easily, but if I put it up to 3.6, I get bluescreens before even getting into windows @ 1.4vcore. It is possible that is ram related though, but not really sure if I can easily tell.
 
I'm using 4 sticks of corsair ram - I'll grab a screenie of the cpu-z page for it, probably easier - its running at the settings in the bios pics above, so 6-6-6-18 at 2.08v (but i hear my board overvolts ram or something).

cpuzram.jpg


-GiR
 
Well, I took two of the sticks out, still bluescreen loading windows. Tried with the increased NB too, that also didn't change anything. I guess I'll have to be happy with the 1Ghz overclock and properly stress test it :)
 
I would say FSB hole, but the P5Q series apparently don't have these so that can't be the problem.


I get a BSOD when loading windows when trying to go in a 3.6Ghz (360 FSB) and I'm thinking it's RAM related, it was the first time I had to run the RAM below 1000Mhz, so I'm thinking it could be going to slow.

Try OCing your RAM a bit to see if that gives a bit more stability.
 
The problem with that is I cannot find an option to manually set the divider between them. I can only select from like 2 or 4 pre-set amounts, based on my fsb, and they are quite large jumps,. like from 800 to 1000+ in one go. I'll give it a try in the morning when I get back home though :) No harm in trying!

If anyone else has any suggestions too, feel free to throw them my way!
 
You must log in or register to reply here.
Back
Top Bottom