Windows 10 might have killed my ThinkPad

[Idle]

It's only a might — I wasn't watching what went on.

Since early last year I've been running the various builds of W10 via the fast ring on a more-or-less redundant R500 ("upgraded" if you can call it that, from Win 8.1.)

Today it was installing the latest build (14342) — had completed the regular updates, downloaded the new build and the install had got to the first reboot.

I was working outside, went in to enter password and found the machine stuck at the logo screen: "Press the blue Thinkvantage button etc.)

That's now as far as the device gets — removing the battery, unplugging power and holding the power button down didn't help.

This suggests a BIOS problem, which may involve screwdriver work.

My question is: Does anyone know how to kill the CMOS on a R500?

I'm not panicking over it, there's nothing of importance on the machine, but it would be interesting to know what happened.

TIA

Idle

[MrMaguire]

I doubt Windows 10 killed your hardware, but you never know.

I would start by reseating the RAM.

[Idle]

Thanks for the reply — I'll try that.
However, there's no error beep.

[TPFanatic]

It's totally hung? If something got messed up the Thinkpad might do an extended memory test behind the scenes at the loading screen. Pressing Esc at the logo should bring up additional information, and at that screen pressing spacebar should cancel the test.

Unless it's frozen there and nothing does anything....

[Idle]

Yep, totally hung.

Now, if I can just remember what I did with the copy of the service manual... (Never get old...)

[RealBlackStuff]

Click on the HMM link at the top of this page to get your manual.

[josh5k]

It's darn near impossible for Windows 10 to have 'killed' your Thinkpad. At the end of the update/setup process, all the OS does is a request for reboot along with a temp change in boot request if there are further steps needed upon first boot.

I'd suggest basic hardware troubleshooting such as removing power sources including battery and then retrying and perhaps if needed remove CMOS battery to reset the BIOS settings. Beyond that resetting memory and CPU Fan connection has helped me on a couple of older machines.

[axur-delmeria]

Remove the hard drive and see if the machine turns on properly.

[Idle]

Remove the hard drive and see if the machine turns on properly.

Sorry to take so long replying, I've been suffering the effects of advancing age — I suppose, at 92, I'm entitled to (but I wish I wasn't...).

Have tried cleaning RAM modules & sockets, removing HD (and re-inserting same) — no result. Neither does starting the machine with no RAM, which should have a noisy aftermath.

I think the "press the blue button" etc. message appears at the entry point of BIOS — if it halts there, there may be either a firmware problem or a hardware one (you pays your money and you takes your choice...)

Looks like I may have to write the thing off.

[Idle]

Fixed it!

Took my courage in both hands, pulled the thing to bits and found what looked like a dry joint,

Hit it with a well-tinned iron and

[MrMaguire]

Excellent! Where was the dry solder joint?

[Idle]

Excellent! Where was the dry solder joint?

In the BIOS area (where I first thought) — must have been connected to it, although I didn't spend time tracing it through.
Took a while with a strong glass to find it — fortunately I knew what I was looking for.
I was a bit scared doing the job, my hands are really too shaky for fine work nowadays (never get old, it isn't much fun.)
Luckily, I got away with it.

[axur-delmeria]

That's indeed excellent news. Glad that you got it running again.

[Dodge DeBoulet]

Remove the hard drive and see if the machine turns on properly.

Sorry to take so long replying, I've been suffering the effects of advancing age — I suppose, at 92, I'm entitled to (but I wish I wasn't...).

Well, see, you're 92 in Aussie years, mate. That's only 66 in US years, and 59 in European!

Good job on finding the fix