I have win 2k pro sr-3 which will not shutdown. If shutdown,or standby is selected the computer reboots. This also happens in safe mode with all possible services stopped. System is AMD 1300 on Asus A7M266 motherboard. It used to work and I can't remember when exactly the problem started. Soft off power button works and is the only way to shutdown. Any ideas?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Win 2k pro will not shutdown 1
- Thread starter Coljep
- Start date
-
1
- #2
netwalker1
Programmer
Enable the APM support from the Power Option in The contorl Pannel ..
And check the status ..
Mohamed Farid
Know Me No Pain , No Me Know Pain !!!
And check the status ..
Mohamed Farid
Know Me No Pain , No Me Know Pain !!!
- Thread starter
- #3
- Thread starter
- #6
Tried repair - no change.
Tried reinstall over old installation. Same reboot except now get Blue screen with DRIVER_POWER_STATE_FAILURE Error.
MS Technet suggests proceedure to find offending driver, but I think a complete new installation will be quicker.
Has anyone any experience with GoBack or is Ghost images a better strategy for the future?
Cheers!
Tried reinstall over old installation. Same reboot except now get Blue screen with DRIVER_POWER_STATE_FAILURE Error.
MS Technet suggests proceedure to find offending driver, but I think a complete new installation will be quicker.
Has anyone any experience with GoBack or is Ghost images a better strategy for the future?
Cheers!
I have some experiences that might be of use to you, Coljep. It seems that the situation may be mitigated by going to shutdown via logoff. I have also found it rewarding to startup and then shutdown from the login dialog box a couple of times and then startup propoerly, logon and do some work (yawn). This particularly seems to stop the problem for a while but I do not yet know how permanently the effect is, YET.
![[lipstick2]](/data/assets/smilies/lipstick2.gif "[lipstick2] [lipstick2]")
A BIT OF LATERAL THINKING
Windows and MS-DOS both provide ways of signalling whether a machine should be shutdown or restarted (warm start). I think it works by one of 2 values being placed in a register prior to shutdown. One value results in SHUTDOWN, the other in RESTART. My recent experience with Win2K certainly suggests that power supply/hardware is not the cause of my problem. I suggest that Win2K is using the restart value when it should be using the shutdown value. My little performance with startup/immediate shutdown was based on a hunch (desperate hope?) that I might persuade Win2K to return to using the correct value so that the problem would then go away. Well, it hasn't returned yet and I have done about 20 shutdowns in the last 2 days so I'm beginning to feel ever so slightly cautiously optimistic.
![[lipstick]](/data/assets/smilies/lipstick.gif "[lipstick] [lipstick]")
Windows and MS-DOS both provide ways of signalling whether a machine should be shutdown or restarted (warm start). I think it works by one of 2 values being placed in a register prior to shutdown. One value results in SHUTDOWN, the other in RESTART. My recent experience with Win2K certainly suggests that power supply/hardware is not the cause of my problem. I suggest that Win2K is using the restart value when it should be using the shutdown value. My little performance with startup/immediate shutdown was based on a hunch (desperate hope?) that I might persuade Win2K to return to using the correct value so that the problem would then go away. Well, it hasn't returned yet and I have done about 20 shutdowns in the last 2 days so I'm beginning to feel ever so slightly cautiously optimistic.
- Thread starter
- #9
Sorry it's taken so long to sort this but I havn't had much time recently and the computer has been OK apart from the shutdown problem. The problem has been traced to having my Netgear ME102 wireless access point plugged into the USB port! It only needs to be connected to change config but having it connected causes the wierd shutdown/reboot behavoir. Upgrading to the latest firmware and software made NO difference but unplugging when not reconfiguring cured all.
- Status