Cant seem to reach old OC on new new motherboard

Deception · 27 May 2010 at 20:44

Hi there!

As the title goes, I recently purchased an Asus P5Q Pro (originally had GA-P35C-DS3R). Now i keyed in my old settings in the BIOS which i had previously to reach 3.2ghz on my q6600. The thing is, i get an BSOD everytime i attempt to load windows.

I guess it might be due to all the new options in the AI tweaker that arent there in the gigabyte version.

At the moment, ive had to lower RAM speed down to 962 from 1068(previously worked on old mobo)

Any help or people with same board and cpu will be appreciated!

*Edit* As for settings i just keyed in CPU Ration(9), FSB Freq (355) and DRAM Volt 2.1 Everything else was left to auto apart from obviously speedstep.

JonJ678 · 27 May 2010 at 21:02

Shocking. Stable settings tend to change when you update a bios, it was a very long shot indeed to believe that settings stable on the Gigabyte would work without alteration on the Asus.

You've also changed chipset, meaning there's a fair chance windows has got its knickers in a twist and will refuse to behave until its reinstalled.

Finally, leaving everything on auto is not a good call. And the P5Q range overvolted ram by 0.08V on the earlier bios versions, its quite possible its still doing so.

Changing to stock then more reading is highly recommended at this point.

Deception · 27 May 2010 at 21:15

JonJ678 said:
Shocking. Stable settings tend to change when you update a bios, it was a very long shot indeed to believe that settings stable on the Gigabyte would work without alteration on the Asus.

You've also changed chipset, meaning there's a fair chance windows has got its knickers in a twist and will refuse to behave until its reinstalled.

Finally, leaving everything on auto is not a good call. And the P5Q range overvolted ram by 0.08V on the earlier bios versions, its quite possible its still doing so.

Changing to stock then more reading is highly recommended at this point.

Yea, like you said it was worth a try haha. Ive also reinstall windows too ( didnt fancy taking that chance too

). I will go have a looksy!

alex24 · 27 May 2010 at 21:21

Hi mate, I actually made the same transition from a P35C-DS3R to the P5Q Pro. They're very different boards, so you'll need to start clocking from the beginning again.

Since that was my board, I know the BIOS is on a relatively new (if not newest) version, so RAM voltage should be OK, though I always had mine under volted a tiny bit just in case.

You'll need to start clocking from stock upwards I'm afraid, though you can probably take fairly large steps up to 3GHz as most Q6600's won't have any issues with that, and shouldn't need much, if any, extra juice.

As for the motherboard voltages, I had almost all on one notch above the lowest bar the obvious (CPU, DRAM), not on Auto, as I found that on auto under overclocking, they all were over volted too much and sometimes actually caused stability issues. I'd recommend you do the same, I was running a Q6600 at 3.4 in that before without much of a problem.

Oh, and run the RAM underclocked or at stock to begin, then clock it once the CPU is stable.

Big.Wayne · 27 May 2010 at 22:43

Hello Deception,

I don't see what the problem is? . . . should be quite easy to get that chip running at 3.0GHz/3.2GHz? . . . would you be prepared to reset BIOS and start again? . . . . is your board running the latest BIOS? and do you have DDR2-1066 memory?

First step for 3.0GHz:

Reset BIOS to stock, save & exit and back into BIOS
Change FSB to 333MHz
Change Memory Frequency to [DDR2-1000]
[Optional] Change Memory voltage to Manufacturers recommended value
Save & exit

That should get you 3.0GHz with the memory running at DDR2-1000 [2:3] . . leave the CPU multi and all other volts on [Auto] and temp for stability, noting load temps and load vCore as seen in CPU-z

Next step 3.2GHz

Enter BIOS
Change FSB to 356MHz
Save & exit

That should get you 3.2GHz with the memory running at DDR2-1068 [2:3], if that doesn't work I think it may be the board not given the processor enough voltage and you will have to re-enter BIOS and manually select a higher value! . . . . also if you can 3.2GHz working nice and stable using mostly[Auto] voltages you will be in a better position to begin *tinkering* with manually adjusting things! :cool:

Deception · 27 May 2010 at 23:09

Thanks for the tips Wayne!

I guess the main thing was compared to BIOS ive been used to and then seeing the AI Tweaker menu and not knowing what half the extra options do, it was abit overwhelming haha.. Most of them supposedly increase DRAM overclocking ability, yet when i enable.. I dont even get into windows, so they all went on disabled.

Not actually my bios though, just trying to show and example of what i meant.. I guess i like simple things

alex24 · 27 May 2010 at 23:50

I'd set the RAM latencies to auto first, it should take the info from the SPD (from the RAM chips) so it can definitely run OK. I.e. all those clock numbers in the screenshot above. I usually set the first lot to what you RAM reads after that. I.e. if you have RAM that reads 5-5-5-15, set the first four to that. There are a lot of pages on the net already about how to clock with this board that helped me too, though I don't have the links to hand. Google will help too, but for the most part it should be easy enough, as Big Wayne has tried to show above.

Big.Wayne · 28 May 2010 at 00:04

Deception, did you reset the BIOS and follow the instructions above? . . . don't worry man as I know that BIOS back-to-Front!

Most of that stuff in the screenie you posted should be on [Auto], especially Ai Transaction Booster at this early stage! :cool:

Deception · 28 May 2010 at 08:22

Big.Wayne said:
Deception, did you reset the BIOS and follow the instructions above? . . . don't worry man as I know that BIOS back-to-Front!

Most of that stuff in the screenie you posted should be on [Auto], especially Ai Transaction Booster at this early stage!

Yep, i followed then all!

Currently sitting at 3.3 (375x9). setting fsb to 380 hits a wall and BSOD during prime test. That screenshot wasnt actually of my BIOS, it was one i fount on the net to show the extra options im unaware off (everything in mine is still set to auto apart from those 3 bottom options which are set to disabled for now, also manual voltage on CPU and DRAM) RAM is currently set to 999 also.. Nice ironic number in my situation!

alex24 · 28 May 2010 at 13:07

Cool, well now you just need to up the CPU voltage a notch and see what FSB is bootable and go from there. Good luck, 3.3 is a good OC to start from to fine tune.

Deception · 28 May 2010 at 13:37

alexhull24 said:
Cool, well now you just need to up the CPU voltage a notch and see what FSB is bootable and go from there. Good luck, 3.3 is a good OC to start from to fine tune.

Yea, it is. I just need to find voltages of NB currently and the other options that are auto, so that i dont accidentally underclock. Hmm, now to find a multimeter as programs ive been using dont report NB voltage (Everest, HWMonitor)

alex24 · 28 May 2010 at 13:46

Setting it in the BIOS should suffice, there's no chance of undervolting the NB, just increase it from the minimum value if you think that upping the CPU voltage isn't helping anymore, or leave it on auto until the CPU is clocked, then you may be able to optimise the voltage afterwards if you have no problems. I assume that's what you meant?

Deception · 28 May 2010 at 13:49

In a way, I meant with it being set to auto in the bios, i wondered what it had been "auto" increased to currently. Then i can then start increasing from there and not accidentally put it under. My CPU voltage is currently on 1.28. Like you said, i could try increasing CPU voltage abit more, and leave rest at auto.. 3.4 is just such a round number and only a small increase in FSB (375 to 380)