Abit Ab9 Pro - Q6600 oc problem

[Gtancx]

Dear all,

I have a little OC problem with my Q6600 on Abit Ab9 Pro, which no one on the Internet seems to know anything about [[at least during 24h+ research on the subject matter]].. I sincerely hope I will find an answer here.

Recently I switched from E6420 to Q6600 G0 with the goal of achieving about 3,5 ghz core speed and it seems that I've encountered an fsb wall at precisely 346 mhz.
No matter what I tweak in Bios my system greets me with a BSOD/freeze/restart during windows XP loading screen.
Here's the list of things I've done so far to no avail:
- tried different fsb freq's from 346 - 475 on all available multipliers [[6-9]] to look for fsb holes
- tweaked almost all available voltages from bios [[except for the mind blowing extremes]]
- tested different RAM speeds, latencies and ratios
- updated bios to v.23 Beta

The computer runs stable @ 3,06 ghz which is 340 fsb mhz with vcore of 1.38v with idle temps of 38 C and stress temps of no more than 60 C. [[I use Scythe Mine with Arctic Silver 5]].

What is interesting is that the systems starts up to 345 fsb and passes Orthos CPU test for more than acceptable periods, but as soon as I try the Large In Place FFT for RAM for a few seconds the computer restarts with no indication of what has happened.
Previous CPU [[E6420]] ran successfully @ 3,40 ghz [[fsb of 425 mhz x 8]]

I would be very grateful for you suggestions or explanation of what is happening!!

Best regards,
Greg

[GoNz0]

so your chip hit its max, its not like you can buy a chip that will overclock to a certain speed now is it ?

or are you one of those that insists that there chip will hit 3.5ghz

mine hit its wall at 2.96, simple as that, nothing else could be done to get round it.

[Gtancx]

Does Large FFT's still fail at stock?

nope.. In fact, it runs stable on my current fsb spec of 340 mhz = 3,06 ghz..

[Gtancx]

so your chip hit its max, its not like you can buy a chip that will overclock to a certain speed now is it ?

or are you one of those that insists that there chip will hit 3.5ghz

mine hit its wall at 2.96, simple as that, nothing else could be done to get round it.

Thanks for the reply!!

I considered that of course, but then again wouldn't that mean that I should be gradually getting more CPU errors on Orthos in the instability zone of fsb 341-345 mhz ??

If there's no relation then I'll gladly accept the sad fact..