• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

Need help with GA-X48-DS5!

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

totalz

New Member
Joined
Apr 24, 2009
I know this mobo is old, but I just installed a new one to replace my old 965P-DS3P. All the other things are exactly the same, Intel DC-E6300 (266*10.5), GTX2700, 1G*2 Supertalent + 2GB*2 Transcend...

I was able to get 412*9, CPU voltage = 1.375V, with E6300 & P965, default voltage for others. That's not much OC(!?), but I didn't want to go over the VCore... And of course, with programs like cpu-z, I know I can give it a bit more juice :chair:

Anyway, since I've been using the OCed E6300 for more than a year, I thought I could just go with the same settings and try everything else 1st then come back latter for further OC... but I end up with lockup/hang even in bios! I don't think it's caused by MCH latch!? Could it be fixed by the CPU clock skew control?

It does seem fine to run with 348*10.5, 2.4(C strap) ram:fsb ratio, 1.4 CPU voltage though, 1.376 Vcore in cpu-z 100% load! :fight:
 
There is no 2.40 system memory multiplier available for the C / 200 MCH strap, only for the B / 333 MCH strap. Assuming you have DDR2-800 RAM, change to the 2.00 memory multiplier on either the B / 333 or D / 400 strap, for an effective 696 MHz DRAM frequency at a FSB of 348 MHz.
 
There is no 2.40 system memory multiplier available for the C / 200 MCH strap, only for the B / 333 MCH strap. Assuming you have DDR2-800 RAM, change to the 2.00 memory multiplier on either the B / 333 or D / 400 strap, for an effective 696 MHz DRAM frequency at a FSB of 348 MHz.

thanks for reply,

yes, u're right, 2.4 is on B strap!

However, when I tried 2.0D with 9x412, it still lockups in bios! But I haven't tried with 2.0B though, would be strange if it works with B strap, cause D is more loose! And it's hell with this kind of lockup, I have to clear cmos every time!
 
Last edited:
Back