Overclocking my Q6600 problems?

[wt123]

EDIT - Ignore me I was being daft!!! /facepalm

I have done a little more fishing and the Memory Frequencies on this board allow for the following...

1:1, 5:6, 4:5, 3:4, 2:3, 5:8, 3:5 and 1:2.

To help you understand, those are dividers of your FSB....

400 FSB 1:1, RAM = 400 (x2 for DDR = 800)
400 FSB 5:6, RAM = 480 (x2 for DDR = 960)
400 FSB 4:5, RAM = 500 (x2 for DDR = 1000)

...and so on. Now apparently not all of these dividers are always available. It depends on the FSB.

So you can see that every time you raise the FSB above 400, your memory is going to go with it, even on the lowest divider (which is running in sync) 1:1.

Given that your memory is only rated for 400 (x2 for DDR) then that could be an issue.

So, with that in mind, maybe we should go back to the 9x multi and see where that gets us...

CPU RATIO - 9x
FSB - 367
CPU Vcore - 1.52
CPU PLL - 1.55
Northbridge - 1.3
FSB Termination - 1.25
RAM - 1.9

Memory Frequency - DDR2-734 (1:1 to the FSB) if available

EDIT - with any luck that will get you running at 3.3ghz.

Sorry about late reply, just tried it and windows started and all, was all looking good, then started prime ran for like 10 seconds then crash and blue screen =[

EDIT: Forgot to mention could only put DDR2-735

 

[Diggsy]

Sorry about late reply, just tried it and windows started and all, was all looking good, then started prime ran for like 10 seconds then crash and blue screen =[

EDIT: Forgot to mention could only put DDR2-735

Thats a pity. Its sounding like you've hit the limits of your board/cpu.

The only other thing I could suggest to try is loosen the RAM timings and see if that helps, but I am not sure it will as at 367 the RAM is already running below spec.

It seems that your cpu needs a lot of voltage (either because of the board, or maybe even the cpu itself) to get any higher, and it's really not worth it.

If I were you I would clock it back to 3.2 and be happy.

Just try to get all the voltages as low as you can, but remaining stable.

Try the following, and reduce the vcore by 0.01 (or as close to this as possible) at a time, testing with Prime for stability. Once it crashes, raise it 0.01 and leave it at that.

CPU RATIO - 8x
FSB - 400
CPU Vcore - 1.5
CPU PLL - 1.5
Northbridge - 1.2 (might need a tiny bit more for stability, but you'll know right away)
FSB Termination - 1.2
RAM - 1.9