Finally OC'ed, Temps Fine, But Unstable

[VashTheStampede]

After being told my T-bird was locked and I needed to do the pencil trick or conductive pen trick or buy trace tape, I went into the BIOS last night and was just tinkering around. No results were produced until I started messing with Clock By Slight Adjust.

I've got it cranked to 113 now, and that's as far as I can go before Windows 2000 splash screen doesn't load or it BSODs me before Windows starts loading. Temps are great at the moment, 32 C for the CPU, 30 C for the case.

It POSTs fine, but it's Windows that seems to have the problem with accepting a higher FSB clock speed. 100MHz speed increase is good, but, as Tim Taylor would say, More Power! So some help from some more experienced OC'ers would be appreciated in diagnosing and solving my problem. Thanks.

~Vash~

[KaHNZa]

Did you do anything with the voltage?

[Yodums]

You need to adjust your voltage I'd bet.

Or check the database for your chip whether it is a good ocing chip or not.

I don't think your temperatures would be that low as orbs are very poor cooling and they push like 20cfm and their design aint good enough for AMD.

Yodums

[VashTheStampede]

Originally posted by Yodums
You need to adjust your voltage I'd bet.

Or check the database for your chip whether it is a good ocing chip or not.

I don't think your temperatures would be that low as orbs are very poor cooling and they push like 20cfm and their design aint good enough for AMD.

Yodums

Well with a little AS2 and some assistance from a "cheat cooling" program, Vcool, the temps are that low.

I just got through adjusting the voltage, to 18.00, just like before, it would post if I pushed the Clock By Slight Adjust beyond 113, but still crash at Windows 2000 splash screen or right before it, at the Verifying DMI Pool. Also noticing with pushing it past 113, the monitor would turn flukey. Saving BIOS changes and rebooting would leave the monitor there with a black screen, and eventually go into energy saving mode due to a lack of a video signal. A cold boot fixed that, but this is ONLY experienced when pushing the FSB beyond 113.

The chip is a good OC'er, people posting 1.2-1.4GHz and one at 1.8GHz with stock HSF (Kind of hard to believe).

~Vash~