Q6600 -first overclock

TrevP

TrevP

TrevP

Associate
Joined
31 Dec 2008
Posts
13
New build:
Q6600, GA-EP43-S3L, Patriot PC6400 viper extreme (4,4,4,12), 9800GT.

Ran last night for an hour @3.2GHz (400x8) on stock cooler with stock vcore of 1.275v. No problems. RAM is at standard 800MHz. Will get a better aircooler today. Not happy with coretemp readings because CPU speed is shown incorrect so how can I trust the temp readings? They are the same as speedfan and HWMonitor though.

Going to lap the cooler to the CPU. Anyone overclocked this RAM? Will I need to add cooling to the motherboard at 400+fsb? Where do I find the chipset temp?
 
The speed is showing as lower in CPU-z prob because speedstep is still enabled, disable speedstep, EIST, C1E etc in bios and that will force it to remain at rated value. BTW Speedstep is a power saving feature where it declocks itself when not needing to run at full spec. So yes you can trust the temp readings.
Hacent OC'd that RAM but I gather patriot is good make so you should be ok, re cooling so long as you've got a decent case with good airflow I'd imagine you'll be ok
 
Just to say I got one for XMas (with a new mobo as well :-) ). Only really played around yesterday though.

Got mine up to 3.6 with 1.46 vcore. Apparently I have vdroop (!) on my new motherboard and the actual vcore reported by CPU-Z under load is 1.39-40. So not too shabby I think.

Core Temp is showing temps at around 30 idle and 63 max after about 3 hours of Prime "torture test". I'm using an Antec 900 and the top fan isn't on for some reason so I'm hoping for a bit of a drop in temps once I sort that one out.

Got to say the difference form the old e4300 is very obvious. Everything just opens, shuts and just works that bit faster in Windows. I've only tried Medierval 2 Total War as far as games go. But I can now run it on full detail with units set to huge (1680 X 1050), so I guess the old CPU was holding things back.
 
95thrifles said:
The speed is showing as lower in CPU-z prob because speedstep is still enabled, disable speedstep, EIST, C1E etc in bios and that will force it to remain at rated value. Hacent OC'd that RAM but I gather patriot is good make so you should be ok, re cooling so long as you've got a decent case with good airflow I'd imagine you'll be ok
Click to expand...

Ahh, nice little tidbit thanks.


Ben M said:
3.2@ 1.275, nice chip =]
Click to expand...
Yes thats what I thought. :D
 
Hit a problem. Put on a better HSF today and idle is around 30, with prime95 hovering around 52. Everything is fine unless I restart, when I get BSOD's. Let it cool for a bit and everthings fine again until I restart. Tried upping vcore from 1.275 to 1.2875 but no change there. ??
 
Up the vcore? Also check what CPU-Z is saying the vcore is as opposed to what you set in the bios, especially under load. Probably quite a bit less than you set, you might need to compensate.
 
Thanks. I've reset the vcore to [AUTO] CPUZ reports vcore @ 1.280 - 1.312v, so does that mean the mobo adjusts vcore on the fly if set to auto?

I also noted the memory in CPUZ was reported having timing of 5,5,5,15. When I looked at the SPD readings in CPUZ it says JEDEC @400MHz =5,5,5,15 at 1.8v and EPP @400MHz is 4,4,4,12 at 2.1v does that mean I should set the RAM voltage to 2.1v?
 
No you get your vid from coretemp (sorry I was very drunk when I got in last night, not sure really why I came on here and posted? lol), thats its recomended speed to run at stock, you could leave vcore on auto if its working fine at the moment but as you OC more youll need to set it manually
It is a good idea to manually set your RAM or DIMM voltage as it maybe labelled, set it to manufaturers recomended
 
Thanks for your help. This is where I'm at:
Q6600 @3.28 (410x8) stock voltage. Patriot PC2-6400 @820 2.1v, Akasa Evo blue cooler (ugh I know). Running prime95 with cores all below 50.

There's probably more to come yet, I'll have to get methodical.
 
Well, if that's achieved with vcore set at AUTO that's pretty good I think. But as 95th says if you want to push it further you're going to have to up the voltage.

The bit about vcore reporting a different vcore to the one set is due to vdroop (!) - I think. Basically, you board isn't passing the juice on properly. When you OC the chip and push it the voltage drops drastically. I used OCCT (you can download it her in the OC'ing section) and it shows graphs of the vcore as you put it through tests. Mine dropped from the 1.32 I'd set in the BIOS (to get 3.4) to 1.25-6 at which point the test failed. I've got my Q6600 at 3.6 stable now, but I've had to put the vcore up to 1.44, which CPU-Z sees as 1.38.

The only other thing I changed was the CPU PLL to be "set" at 1.6. Don't ask me what it is, I just read to do that here in a thread about my mobo.

I haven't touched anything else.
 
You must log in or register to reply here.
Back
Top Bottom