Overclocking my Q6600 on Asus pk5-premium

jubei

jubei

jubei

Soldato
Joined
3 Apr 2003
Posts
2,928
Hi guys,

After reading the stickies i decided to have a shot at my first overclock with my new rig. I used a thread that i saw linked on mainpage that recommended just going bios and setting dampener to enable, vcore to 1.35, fsb to 400 and multi to 8 which i have done.

I have now been running prime for a good 15-20 mins and the temps on coretemp are ranging from 42-49 and the odd 50 on the #3. Cant really remember my idle times, stupid i know but it was kind of a rebooting my computer and decided 'what the hell' and went in and changed the settings.

Are these temps okay? also i saw someone recommend checking 'round off checking' in advanced tab on prime but mine is greyed out. i am runnign the small FFT test just on whatever defaults came with the program.

CPU-Z shows:

core voltage: 1.32
spec: Q6600 @ 2.4
core speed: 3200+-
multi: x 8.0
bus: 400
rated fsb: 1600+-

CoreTemp shows:
vid: 1.2500
freq: 3199.88(399.99x8)

How does this look? is it normal or am i not stressing this enough?

Also i am more than happy with a 3.2 clock but after reading the guide i am none the wiser on how to optimise it, to ensure i getting the best speed i can out of that clock speed, should it be more fsb with lower multi or the other way around. also didnt see any info on making sure my memory is running the best it can.

Any help appreciated, also if people think i cld get to 3.4 on these voltages and would be safe to do so i might give that a shot at least then i am gaining a gig on top of the default.

Cheers all :)
 
cheers man, i originally was worried i had not put the hsf on right, had a nightmare putting the tuniq on as did it once mobo already mounted n also with a bit too much of the thermal grease i think. Also computer hangs now and then in UT3 when my mate was just playing it. Will be running fine then lock up for like 5 seconds n then carry on again.

But i donwloaded core temp and temps looked okay so decided to try the clock. Wonder if GFX card is the one playing up.

Anyhow what would you do about moving forward with this clock? do i keep fsb where it is and increase multiplier, or do i keep multi where it is and increase fsb? I have 4 1 gig sticks of geil memory 6400 that apparently does 4 4 4 4 12 timings or some such.

Just stopped prime95, max temps i saw were 52, test ran for 56 minutes with 0 errors 0 warnings.
 
Last edited:
Increase you FSB in small increments. (You can change the multi to x9) Post back your results/ findings

You are using 4x1 modules a small voltage increase to the NB will also be helpful. (4x1 adds more strain to NB memory controller vs 2x1 modules)
 
Last edited:
Are a whole load of threads recently on clocking P5K - E / E-Wifi / Premium boards these all follow a very similar procedure so would suggest that you have a quick browse on those threads for ideas on setting etc.. also Quad Core Database is a thread with loads of info on different clock speeds and settings would have a look at that..

maybe an idea I do a quick start clocking guide for the P5K- XX Asus boards as seems to be a popular topic right now? and am pretty familiar with a couple of variations of them :)
 
Hmm i just upped my multiplier to 9 and kept fsb at 400 and looks like i am runnign at 3.6? no idea if i am or not really tho.

Does prime actually test all cores with stress or just one? i have it running at the moment but on task manager cpu usage only seems ot have 2 cores really being used. Have set prime to realtime.

My fan is only kinda halfway turned up on my tuniq to spare me the noise but currently the temps on coretemp with prime running are 51-58C.

I couldnt find this speedstep setting on my bios, went through all the screens. Have not altered the northbridge voltage nor the ram voltage, i stuck the vcore to 1.35 just for the sake of it because people kept posting that it was important to do that but i have no idea if i actually needed to.

Anyhow how can i properly test this to ensure that my chip is not going to fry? Also i tend to leave my computer on 24/7, gets shutdown a couple of times throughout the day but generally is always on, is that safe to do with an overclocked system? Can i just batter it like a normal system or need to be more careful?
 
pic of my clock i think? Am i meant to include something different? Sorry for all the likely stupid questions, i am stuck somewhere between curiosity/excitement and fear of destroying my new computer :)

overclockzd7.jpg
 
Last edited:
jubei said:
pic of my clock i think? Am i meant to include something different? Sorry for all the likely stupid questions, i am stuck somewhere between curiosity/excitement and fear of destroying my new computer :)
Click to expand...

Hi jubei Nice over clock and extremely good temps congrats No such thing as a stupid question, we are all here to help each other;). And you wont destory your computer either.

In prime did you enable round off checking in the advanced Tab , and set the torture test for small ffts out of interest before you ran prime?

Are you able to post another pic with prime running to show the temps under load as you have halted prime in the shot above.
 
Last edited:
jubei said:
Does prime actually test all cores with stress or just one? i have it running at the moment but on task manager cpu usage only seems ot have 2 cores really being used
Click to expand...
I think you are using an old version, the latest version runs on all cores simutaniously, I have emailed you the latest version to your ntlworld.com address as I cant find a direct linky. . .
 
CyZMyAssBaby said:
Hi jubei Nice over clock and extremely good temps congrats No such thing as a stupid question, we are all here to help each other;). And you wont destory your computer either.

In prime did you enable round off checking in the advanced Tab , and set the torture test for small ffts out of interest before you ran prime?
Click to expand...

I cant mate, that round of checking is greyed out even when i have no test running. I literally clicked on the options tab, clicked torture test and small FFT and this is it running. Still running at the moment will update the picture.
 
Hmm i just upped my multiplier to 9 and kept fsb at 400 and looks like i am runnign at 3.6? no idea if i am or not really tho.
Click to expand...

Yup - 3.6ghz.

Does prime actually test all cores with stress or just one? i have it running at the moment but on task manager cpu usage only seems ot have 2 cores really being used. Have set prime to realtime.
Click to expand...

All four cores should be showing 100% usage. Ensure you have the latest edition of prime95 25.5.

My fan is only kinda halfway turned up on my tuniq to spare me the noise but currently the temps on coretemp with prime running are 51-58C.
Click to expand...
Increase it to full speed. There are few 'normal' programs that will load all your cores at 100% for any length of time so you wont need to run the fan at that speed normally. Having said that 51-58c is nothing to worry about.

I couldnt find this speedstep setting on my bios, went through all the screens. Have not altered the northbridge voltage nor the ram voltage, i stuck the vcore to 1.35 just for the sake of it because people kept posting that it was important to do that but i have no idea if i actually needed to.
Click to expand...

What you need to do is find your VID - this is the true stock vcore of your chip and work from there. Stating vcore without vid is a little misleading as some vids are 1.2 upto 1.35 so this needs to be taken into account when assessing how much extra vcore is required at any given overclock when comparing chip to chip.


Anyhow how can i properly test this to ensure that my chip is not going to fry? Also i tend to leave my computer on 24/7, gets shutdown a couple of times throughout the day but generally is always on, is that safe to do with an overclocked system? Can i just batter it like a normal system or need to be more careful?
Click to expand...

The new chips have an auto shutdown feature should your cpu get too hot and before it shutsdown it will throttle back so to reduce the temp. Aslong as your temps don't exceed 75c (which imo is a safe 24/7 load temp) then I wouldn't lose any sleep over it. It certainly won't fry unless you put silly vcore (1.7+) through it for extended periods.
 
Big.Wayne said:
I think you are using an old version, the latest version runs on all cores simutaniously, I have emailed you the latest version to your ntlworld.com address as I cant find a direct linky. . .
Click to expand...

Thats an old email address mate sorry, i will update my details appreciate you sending it.
 
Woah nightmare then, updated email address but couldnt remember my password for it to get the verification. Luckily iphone has the mail on it, i still dont know my password lol :)

Thanks for the link, appreciate the help fellas will start running that, fingers crossed.
 
Okay running the new prime and looks more realistic lol. Thread 1 and 2 stopped after the first little test and said fatal hardware error consult stress.txt. Cant actually find a stress.txt file though. Temps went up to 63C.

Any tips on where to go from here?

Vid is 1.25 according to my core temp.
 
enable round off checking in the advanced Tab this will execute the stress text file , and set the torture test for small ffts

increment/ up 1 notch on the Vcore (V+) and re prime
 
I just tried to re-primewhilst waiting on a response and got a BSOD with a memory dump :|

Have dropped the multi back down to 8 to try the prime as now i have the new version i cant just assume its stable i guess :)

Should i up fan to full on HSF even though i wouldnt run it at full normally? Am i not in a better position to see what it can handle at its current speed instead?

Hmm core temp will no longer load, said something about a driver failed to load and not all info be available. Now it keeps making my vista focus on something i cannot see and make beeping noises.

Its making more and more error windows, gonna rebooot.
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom