Page 1 of 1

Attempts to shut down-then shows: now safe to turn off comp.

Posted: Fri Feb 02, 2007 2:46 am
by peggen79
T60 Automatically attempts to shut down, and then shows message:
"It’s now safe to turn off your computer"

We have a bunch of T60s that were supposed to be shipped out to users by now but since they behaving like this we cannot do a thing until we solved this.

All of them are Type: 1951-45G and these machines are running with windows 2000
Professional image on and they have 1,5 GB RAM.
Since they are running w2k we wont get ANY support from Lenovo/IBM.
We are not currently allowed to upgrade these machines to Windows XP...

Since we started to have this problem we have set up a lab-environment and done nothing more with the machines than just log in on them.

They all attempt to shut down at different times of the day.

We have configured some of the lab-computers to using Windows updates, instead of our WSUS-server, but it makes no difference.

We have upgraded to the latest BIOS on all of them.

There is nothing written in the eventlogs at the time before they decides to shut down.

Is there anyone that has a clue, what can cause this, alternatively have any suggestions about things we can try to troubleshoot this.

Posted: Fri Feb 02, 2007 3:32 am
by skanky
in device manager, is the "computer" listed as "acpi uniprocessor PC" or whatever the w2k eqiuvalent is?

Posted: Fri Feb 02, 2007 3:44 am
by peggen79
It´s listed as "ACPI Multiprocessor PC"

We have also configured the power-settings, so that none of the computers will shut down/hibernate etc. because of idle-time...

Posted: Fri Feb 02, 2007 11:08 am
by vision33r
This is a known issue with Win2k and ACPI drivers. There's a patch from MS that address this issue.

XP resolved this as well.

Posted: Fri Feb 02, 2007 5:19 pm
by peggen79
Is there no-one who has the link to that patch?

I would be VERY thankful if anyone has it!

I have been searching microsoft kb-articles for hours, but I haven´t found nothing that helped us out yet. Just some regular microsoft troubleshooting pages that didn´t helped us with this problem.