Asus P5B Vcore problem?
 

Hey,

i run behind the hardware - stuff for 2 gen ;-) but that's because of 3 kids and noooo time ;).

My problem: I have a free Asus P5B mobo, a free E2140 CPU,... In short: almost everything for free ;-) to try some serious OC'ing.

After raising the FSB to 340 and raising the Vcore a little (1.3125v) to improve stability, i see in monitoring soft. from asus and in CPU-ID that the Vcore is still at default.

I have the latest bios installed.

I OC the 2140 (stock 1.6 Ghz) to 2.8'ish Ghz, but it won't run stable after 15 min. of Seti@home.

Graphics: 8600GT, 256 mb DDR3, 32sp.

Is this a sign to let someone experienced in Vmodding to handle the mobo? Or is there something i missed in the bios?

think I've had the same combo once, anyway clocking through the bios should do it but P5B seem to undervolt a bit so you might want to try some extra volts. I've used up to 1.6V on air if I remember it correctly.

EDIT: if you really want to push this board to the limit you need some voltmodding, found pictures from my elderly board with MCH, DRAM and VCORE mods. Also, check the heatsinks, the cooling paste below might need some extra care. Furthermore I believe you also have to take into account at which frequencies you're booting. For instance when you boot at 333MHz the chipset might stop clocking around 380MHz and it may seem you're hitting a solid wall here. Now when the boot at 400MHz the chipset will be internally strapped to different latencies, you can't alter those in the BIOS it is done automatically, but it works and you have now probable up to 470Mhz overclocking. There are few FSB frequencies you need to take into account, I can't remember all of them but there sure are some pretty good articles concerning first generation Conroe mainboards. In Windows you can alter the MCH strap by using Memset software if I remember it correctly. You can use SetFSB to alter the FSB in windows, or was it Clockgen? hmm...

i'll give it a try upping the vcore. Also probably a memory problem, due to the "free" nature of the parts, the memory is 667Mhz, very unfriendly to oc'ing... hint hint: someone with extra DDR2 Ram's surplus ;)

voltage did the trick, now memory bottleneck :(

try the higher memory volts, increase timings and see if you can have the RAM 1/1 with the FSB.

yup - yup - yup - crappy ram, comes out of an Acer Aspire M1600 desktop