Thinkpads Forum

Hi, got me a odd problem with my 600E (2645-4AU).
Many months ago I fitted a Pentium 3 450, some PC100 low density RAM, did all the messing about with the hex editor in the bios and not a single error or complaint until now all has worked 100% flawlesly.

However I now hit a error 102 when rebooting, this does not happen from a cold boot (switch on at post, at least it says it does not, but if you run the test in the BIOS on the system board you will hit error 102), but the thing that happens all the time is the CPU is now shown by PowerLeap Control Panal to have a FSB of between 40-50Mhz randomly making the speed varie between 200-250Mhz whats worse it cant seem to count either when I calculate the speed based on the FSB and multiplier that it gives me the answer is different to what the app says for example

PowerLeap says :
CPU Speed = 238 or 225 or something odd
FSB = 47.33
Multi=4.5

The real answer is 212Mhz. something, again the answers/figures are random.

IBMs error code listings say 102 is the sytem timer can this be repaired without buying a whole new system board?

Why now...just when I was going to buy a P3 850,DVD/CDRW combow and some more RAM!!!

I don't have any experience running PowerLeap, or with the 102 error, but something you've said about the reduction of the FSB strikes a note with me...

Are you running Windows 2000? I have seen Win2K throttle back the FSB to 51Mhz on one of my 600X systems. It seems to be controlled by the various Power Option settings. My speed measurements have been taking with the MobileMeter and CPU-Z utilities.

It runs Windows 2000 (Also 98, Fedora 5, Knoppix) mostly but this has never happened before, the P3 CPU it has is not a SpeedStep MMC at least I think its not

Anyhow that would not account for the error in the BIOS and the error on POST appearing

Is it possible that your CMOS battery is going? I don't know how easy it would be to replace just the clock timer chip, but it would certainly be alot easier to replace (or test the strength of) the CMOS battery first -- if only to confirm that the problem is not caused by it.

Phil.

I set the Windows 2K Power Management to Min. and lo and behold the PowerLeap app reports 100Mhz FSB and 450Mhz (correct answeres) on the CPU, also VERY strangly the 102 error has disappeared and I cannot get it to come back on after a warm reset (start Windows then restart) I'm wondering if something could be left behind when Windows was shutting down causing the timer to think its gone because it still thinks the FSB is 47Mhz or something odd when it was expecting a normal answer?

That would make a little bit more sense since I never got the 102 error from a cold start (switch on then POST)

The more important question here of course is who has had there grubby paws on MY THINKPAD!!!!!

Dr_Frankenmiga wrote:I set the Windows 2K Power Management to Min. and lo and behold the PowerLeap app reports 100Mhz FSB and 450Mhz (correct answeres) on the CPU...

That much I have seen before on my Win2K 500Mhz 600X. Both MobileMeter and CPU-Z reports about 251-254Mhz when Windows Power Option has been set to maximum battery setting (or others that aren't Maximum Performance; not sure of the exact wording since I don't have that system available at the moment).

Dr_Frankenmiga wrote:... also VERY strangly the 102 error has disappeared and I cannot get it to come back on after a warm reset (start Windows then restart)

Can't answer/comment on the remainder of your post as I've never encountered that error before.