Overclock just won't happen....

Soldato
Joined
22 Oct 2006
Posts
5,913
Hi people.

I've got a e6600, 2gb Ballistix 5300 and a Asus P5N-E

I can't get any clock out of it, sometimes it will boot into windows and then just locks up

I've upped the vcore to 1.44 to try it. And couldn't even get 1200fsb stable...

I've set my RAM to 677mhz at 3-3-3-15 @ 2.27v and that is stable all day and night at stock CPU settings.

I have tried unlinked mode the lot.

At stock its fine.

At the moment I'm even running the CPU @ 2.4 with 3.31V

Anything over stock and its a no go zone.

Warren
 
but it runns 100% stable at that so i'd prefer to leave it. As i'm running unlinked it isn't affecting it.

2.27 is the closest to 2.2 that it will allow.
 
When you say 1200fsb do you mean actual, quad pumped or memory frequency?

If its CPU using 1200 fsb (divide by 4(quad pumped) = 300fsb x 9 (multi) = 2.7ghz). Yes? IF so I would be VERY surprised your 6600 couldn't do that even on stock vcore.

Try this :

Disable speedstep/C1E etc
Disable all

Set your multiplier to 9x
Set your FSB to 1400 (3.150ghz)
Set your cpu vcore to 1.45v

Run your memory unlinked.
Set your memory to 800
Set your memory timngs to 5-5-5-15 (leave the rest on auto)
Set vdimm to 2.2v or as near as possible.

If it boots and is stable you have 2 choices - increase the FSB until it becomes unstable or temps become a problem OR lower the vcore a little until it becomes unstable.

I take it you have tried going slow (overclocking one thing at a time) finding each components limit?
 
i'll try all that 2moz


i'm just going all night to try to do this, its doing my head in.

I want 3.2 thats it.

and webbo that was right at 2.7ghz
 
My E6600 was exactly the same although i thought it was my motherboard.

The trick is to have paitence and doing it very slowly, i tried getting 3GHz (9x 333 fsb) on the 2nd day i had it and it just wasnt happening even with 1.5 Vcore. I also tried finding the most FSB i could get by lowering the multiplier and keep it on stock so to increase the FSB.

I then every day upped it by 5Mhz with RAM linked and on a multiplyer of 2 and got to 3.1GHz on stock volts i then upped it a tad and im completly orthos 24 hours stable at 3.2GHz on 1.375Vcore. So maybe going extremly slowly and letting it settle in so to speak might help, well it did with me. Just have paitence and take your time.
 
try at offset clocks m8, instead of 1200 try 1204/1208/1212, its one of the things about the board doesnt seem to like the 00.
 
if i get a clean boot into windows i then get:

STOP: 0x0000009C (0x00000004, 0x00000000, 0xb2000000, 0x00020151)
"MACHINE_CHECK_EXCEPTION"

after about 2secs
 
Okey just been checking something and anyone know why this is orthos everest and windows show the right clock, cystalCPUID and CPUZ show the wrong ones?

 
Back
Top Bottom