e6600 not overclocking well

quantumisation

quantumisation

quantumisation

Associate
Joined
24 Feb 2007
Posts
275
i need help with this - im running fsb of 320 just now if i goto 325 my pc still powers up but i lose the video signal. I have pci set to 33.3 and pci-e to 101. Ive tried raising the voltage from 1.28 to 1.38 incrementing it and its the same every time. Surely i can get this processor above 3ghz atleast? im not looking to go mad and get over 3.6, 3.0ghz stable will do fine

I ran orthos and it froze after about 2 minutes too which is just fantastic. Before you think its voltage related ive tried it on default and increments up to 1.35, and its not overheating, stays around 45c.

Now i might just be doing something stupid cause i havent overclocked before but any advise would be useful about now, this system apparently should have brilliant overclocking ability but i cant seem to get anything out of it. Even the memory wont run at its correct level (4-4-4-15) and runs at 5-6-5-15, if i change that it blue screens when loading too.

full system spec is:

e6600 core2duo currently @ 2.8ghz 320FSB (although orthos is freezing so that might go down..)
p5b deluxe motherboard
8800 GTX 768mb graphics card
corsair 620w PSU
2x 1gb OCZ PC6400memory currently at 800mhz with 5-6-5-15 or something high like that
2x seagate baracuda 7200.10 320gb drives in raid 0
1x seagate caviar aaks 500gb hdd
1x western digital 250gb hdd
standard sony dvdrw
tuniq120 cooler - used thermal paste supplied with this
lian-li pc7 plus case with intake/exhaust 120mm
floppy drive with media card reader
 
p5b deluxe motherboard
Click to expand...

This one has been mentioned a few times. The P5B mobos in some instances become a tad twitchy once you start to push beyond the 320FSB range. Quite a few folk managed to get them working again by skipping stright to 400Mhz and adjusting the Multi of the chip.
 
hmm..does this have something to do with the NBCC strap (ive heard of it but dont really understand it well). If your saying i might have a duff motherboard then i might RMA it cause its only been 1 1/2 weeks although id rather not be without a computer while overclockers test it. Im not even sure if they would accept it as 'faulty' for that reason, my guess is no
 
ok i tried some things suggested in that page, im afraid its made things even more confusing for me.

i set the fsb to 401 and the vcore to 1.4 from auto, i get a video signal this time so i went into the bios and it reported the cpu freqency as 3ghz?? now i double checked the fsb and it still reads 401, i checked the multiplier and it still reads 9. I wasnt number 1 in maths but 401x9 != 3000. I thought ok this is weird ill exit and restart - back to no video signal again so i just reset it all.

I put BIOS revision 1004 on before starting any of this so i hope thats not causing any problem. The guy in that other thread didnt quite have the same problem as me btw.

If i am destined to not have an overclocking system so be it, the computer still does the job but it really does seem like a pity that i cant get the massive performance boost just by raising the fsb to 333 like others seem to do
 
Last edited:
Set your FSB to 401
Set your Multi to 8
Set your Vcore(cpu) to 1.4v
Set your Vdimm(memory) to 2.1-2.2v

This should give you 3.2ghz. If it boots fine you know your motherboard has some fsb 'holes' to be sure where the hole begins and ends you are just going to have to experiment.
 
I had problems with My P5B when i bought it, couldn't get the FSB past the 320 range. I was gutted and worried that i bought something crap.
Did a bit of searching around the internet though and found something that helped me. What i had to do was have the latest BIOS on a USB Drive/stick etc, Went into BIOS, installed the new BIOS. Turned off the system, and did a full BIOS Reset by changing the jumper settings etc. Powered back on, went into BIOS, and reinstall the latest BIOS again. Powered off, Reset the BIOS again by using the jumpers etc. When i booted up next time i was able to set my FSB to 325+ and get it to boot successfully . I've now got my E6300 running at around 505x7 Stable. Cant remember my vCore settings etc, as i'm in work at the moment, but it seems to be stable enough (note that I've not fully tested it yet, I've got around 2Hours stable on Orthos, just need to do more tests, and get around to lapping my core to knock some heat off, run at around 68C full Load on TAT)
 
ive already put the latest bios on 1004 and reset using the jumpers. I did it from windows using the asus update software available on their website..would this make any difference? im gonna try some more stuff tonight i guess, trying random fsb settings rather than slowly incrementing

i tried the settings above btw and = same

i also thought id try lowering the multiplier to 8 and running 325mhz and still get the same issue. As soon as i got above 320 it cuts out even though its a lower overall speed. I can do 320 x9 and it will boot but not 325 x8
 
Last edited:
Lol I am shocked I missed this, sorry man but it didn't even occur to me. I had EXACTLY the same problem with the system when I got to about the 2.8Ghz range on my E6600 P5B setup. In the end it turned out to be memory.

Going in to the memory options and selecting the speed below whatever it was currently working at allowed me to push the FSB up to 344 (3.1Ghz). I've decided to hold there for now but I am running it stable on a Vcore of 1.26v so chances are I can go higher when and if I am ready.
 
thanks for the suggestion but its still the same i think - i wasnt sure what you meant so i lowered the memory timings and lowered the speed on the setting just below the FSB from whatever it was to 650 (its rated at 800) and still it just powers off - powers on with no video and fans overspin.

Is it really just a case of try changing random settings till something works? i didnt wanna mess with voltages etc much but maybe i have to do that to get the e6600 above 2.89?
 
hi m8, have you left any of the voltages on auto?..if you have,try putting the voltages in manually.
try setting your v core to 1.45 as there is a 0.5 v drop with that board(same as mine :D )look in cpuz at vcore and see for youself
in the cpu section disable all options except first 1 (so you can set multi) and keep scrolling down so you see all the options ;)
if you need all my settings ,post back and il go in my bios and write them down for ya
hope this helps ...my spec is very similar to yours
6600,8800GTX,P5BDeluxeWiFi,2Gb 10th Anni,2xraptors(Raid0),2x sata dvdrw,razor AC-1,custom H2O
ps try pci freq at 96 instead of 100
 
ok thanks ill give it a try. Im wondering though would voltage affect things if its happening even when i lower the multiplier? e.g as i have above i cant goto 325 on x9 or x8, even though x8 would make the overall frequency much lower than x9. I have most of the voltages set to auto for things like northbridge/southbridge etc i guess i could put numbers in and try that
 
wow i cant believe it was this simple but it was the memory voltage, i changed it from auto to 1.9 and it worked. Im 100% sure ive tried this before but its the the only thing that makes the difference, none of the cpu options being disabled affected post. I have NO idea why this didnt work before because im sure i tried 1.9 and 2

Ok now that ive told you about my noob mistake its time for a noob question - why did i have to increase the memory voltage to increase the fsb if the memory is set to auto or set to 667 when its rated at 800?
 
answer to your Q...mem voltage on auto will be 1.8v(i think)which is the default v.
normally if it says 2.1v on you mem, that is what it needs to run at the memorys default settings(8oo/444412?).so i think 1.9 is abit to low m8 and i think you will hit some more problems the higher you go,just set it to 2.0v if you do
mboards(this 1 ) likes been told what volts to use and not guess :D
the mem freq will move up with the fsb,in bios when you select fsb freq use the + and - keys and watch your memory change as well as it keeps in sync

c ya
 
Last edited:
yea im planning on increasing the voltage to the memory when i was gonna overclock it too, but i didnt think it would affect my fsb overclock. previously i had the fsb set to 325 and memory 650 and it wasnt working so it was 1:1 and running lower than before.

1 other even stranger thing is, i also set the cpu to 1.35v as well just to make sure it would be stable and begin testing from that point using orthos. PC probe (asus temp utility) reports the CPU at 32c after 5 min of testing (it stopped after 5 min so ill obviously need to increase voltage or something). The weird thing is before when i had voltages lower using auto it was reporting temps or like 50c. I thought it might just be buggy software so i went into the BIOS again just now and hardware monitor reports 28c.

Dunno if im missing something there or not. When it was set to auto im 100% sure it was running the voltage lower than i am just now
 
You must log in or register to reply here.
Back
Top Bottom