Vanilla P5K 0603 + G0 stepping - Reversed speedstep problem ??

I have had to update my Standard P5K bios to 0603 to support the G0 stepping chips but since doing so Im having problems.


When I run prime after about 20 seconds the multiplier will switch from x9 to x6 lowering my clock, its like speedstep in reverse and btw speedstep is disabled in my bios.


For example...

Here is my rig ready to run prime95.

http://img222.imageshack.us/img222/6...ppedem0.th.jpg


Now, here it is running after a few seconds.

http://img208.imageshack.us/img208/9...owediy6.th.jpg


This happens no matter what speed Im running.

Its fine with my E2160 chip it just happens with my Q6600 G0 :(


Any ideas anyone ?

is the bios really necessary to run ya GO, eg my Striker needs 1202 or higher to support the 1333FSB CPU's though it booted fab on my friends new rig with 1201 bios and it runs fine then I see no need to update a bios to me if it all runs fine... maybe you can try a lower version of the bios....

I believe so, unless someone can enlighten me.

the release notes for 0603 says it adds temp reading support for G0 steppings.

motherboard cannot supply enough current.

Quote:

---

Originally Posted by cadaveca

motherboard cannot supply enough current.

---

Could you expand a bit more on this please ?

Is the board faulty ? Why is it fine with other non G0 cpu's ?



Thanks

Asus sent me a new beta bios 0701 but it had the same problem.


Ive found the cause of the problem since though.

When the core temps go over 50 deg ithe cpu is throttling, Its should throttle at 100 DEG not 50 :(

Im going to go back to Asus...

HI devious, try lower clocks, same temps will not cause throttle. Vcore is dipping more than .1v, this can trigger TM2 throttle, once EIST is turned off.

G0's clock well partially because they can handle more current(less leakage, it seems, in this case). This is the same for the "Super B" early edition Conroes.

I can get this same behavoir with G0 and B3 quads, mainly because of the high current draw. Never had it happen with a Core2Duo. Something seems to happen when the FSB is pushed up that causes the throttle, as the same is not true when current draw is high AND FSB are low, although I suppose that at stock current draw is going to be pretty low.

I know for sure that the limit on each board before this happens is different...currently p35 boards go higher before this happens, and hence my correlation wit hFSB, however my views on this issue are not ocmpletely accurate as I'm just a basement bencher/gamer, not a "IT professional" like the top guys.

Quote:

---

Originally Posted by cadaveca

HI devious, try lower clocks, same temps will not cause throttle. Vcore is dipping more than .1v, this can trigger TM2 throttle, once EIST is turned off.

G0's clock well partially because they can handle more current(less leakage, it seems, in this case). This is the same for the "Super B" early edition Conroes.

I can get this same behavoir with G0 and B3 quads, mainly because of the high current draw. Never had it happen with a Core2Duo. Something seems to happen when the FSB is pushed up that causes the throttle, as the same is not true when current draw is high AND FSB are low, although I suppose that at stock current draw is going to be pretty low.

I know for sure that the limit on each board before this happens is different...currently p35 boards go higher before this happens, and hence my correlation wit hFSB, however my views on this issue are not ocmpletely accurate as I'm just a basement bencher/gamer, not a "IT professional" like the top guys.

---

Hi cadaveca,


I dont fully understand your post, I have tried lower clocks and since my last post I have found the problem is still there under 50 DEG.

I have done the pencil mod on this motherboard so my vcore actually goes up 0.01 under prime rather than dip. Could this be the problem ?

this is caused by cpu, not board, altohugh drop of a board will affect when it happens. I assumed it was current....


So, like, i got these quads. 3.0ghz, 1.18v, no problem. Both of them. Both 1.25v VID.

So, i start increasing clocks....failures @ 3.3ghz, 1.25v, so i go up to 1.325v.

Reboot into windows...it freezes.

:stick:


scratch my head a little bit, dig out the multimeter... set by real cpu volts, 1.299v. it gets into windows.(@ 367x9)

run prime...crashes after 4 hrs.

up voltage to 1.325....real by DMM, 1.321v...cannot load windows.


Pull out RD600... 1.3125v...windows boots.


run prime, throttles. lower voltage to 1.297v, boots.

run prime, throttles after 55minutes.

1.286, throttles after 2 hrs.

1.275, not stable.


So, i drop speed back down to stock, up votls to 1.35, boots into windows, runs prime fine, no throttles.

UP voltage to 1.55v, boots into windows, runs prime, hits 80c(stock cooler), no throttle.


up to 3ghz, 1.325 volts, no ,boot.

Lower to 1.299v, boots, stable.


1.3122v, throttles.


Take it ofr what you will...i dunno.:shrug:

sussed it,

disabled CPU TM function in bios = no more throttle :)

under cpu options, correct?:stick: no such luck here... you'll jsut find you can only go a bit further , or that throttle doesn't happen as soon, maybe, at least that's what happened here. Disabling TM function(as i mentioned in other post) is only a partial fix for me.

Seems fine upto 3.6Ghz, but my board is way to flaky and cannot prime for much more than 2 hours, no throttle though.

Time for a new board i think.