"STOP” ERROR MESSAGES AT SHUTDOWN
Some users have gotten an error message similar to the following when attempting either to shutdown or restart Win XP:
STOP 0000009F, DRIVER_POWER_STATE_FAILURE
STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
TechNet and the Microsoft Knowledge Base have numerous articles discussing this type of error condition; for example, these. As a review of these articles will show, these are commonly device driver problems, but may also be caused by troublesome software (such as the notorious CrashGuard), or a problem in a system service. MSKB article Q262575 discusses a shutdown problem of this type, known to exist in Windows 2000 due to a resource (IRQ) conflict, if you have PACE Interlok anti-piracy software installed. This problem may occur in Windows XP as well.
Microsoft advises the following as one approach to these problems: Restart the computer. Press F8 during the restart and select “Last Known Good Configuration.” If you catch the problem when it first occurs (meaning you likely have installed only one or two drivers or new service), this will return you to a previous working condition. (Would System Restore accomplish the same thing? I don’t know, and don’t have a broken system to test it on.)
Microsoft reported similarly that these STOP code error message occur when Windows XP is trying to shut down devices. He says that he has seen this twice: once with Logitech Quickcam installed (with an unsupported driver), and once with a USB DSL modem that would hang if it wasn’t disconnected before shutdown.
STOP 0000009F, DRIVER_POWER_STATE_FAILURE
STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
TechNet and the Microsoft Knowledge Base have numerous articles discussing this type of error condition; for example, these. As a review of these articles will show, these are commonly device driver problems, but may also be caused by troublesome software (such as the notorious CrashGuard), or a problem in a system service. MSKB article Q262575 discusses a shutdown problem of this type, known to exist in Windows 2000 due to a resource (IRQ) conflict, if you have PACE Interlok anti-piracy software installed. This problem may occur in Windows XP as well.
Microsoft advises the following as one approach to these problems: Restart the computer. Press F8 during the restart and select “Last Known Good Configuration.” If you catch the problem when it first occurs (meaning you likely have installed only one or two drivers or new service), this will return you to a previous working condition. (Would System Restore accomplish the same thing? I don’t know, and don’t have a broken system to test it on.)
Microsoft reported similarly that these STOP code error message occur when Windows XP is trying to shut down devices. He says that he has seen this twice: once with Logitech Quickcam installed (with an unsupported driver), and once with a USB DSL modem that would hang if it wasn’t disconnected before shutdown.
SHUTDOWN WORKS, BUT IT’S REAL SLOW.
If it appears that Win XP is not shutting down, give it some time. Some users have reported a minute or longer for shutdown to visibly start. Thus far, it appears that this is a consequence of software that is running when shutdown is attempted, and it also may have something to do with particular hardware. If you are experiencing this problem, be sure to close all running programs before attempting shutdown and see if this solves your problem. If so, then you can determine, by trial and error, which program(s) are involved.
One specific solution for this was provided by Microsoft support. ” In Control Panel | Administrative Tools | Services. (You can also get this by launching SERVICES.MSC from a Run box. This utility is also built into the Computer Management console.) Stop the Nvidia Driver Helper service. Many other friends quickly confirmed that this solved this “extremely slow shutdown” problem for them.
If it appears that Win XP is not shutting down, give it some time. Some users have reported a minute or longer for shutdown to visibly start. Thus far, it appears that this is a consequence of software that is running when shutdown is attempted, and it also may have something to do with particular hardware. If you are experiencing this problem, be sure to close all running programs before attempting shutdown and see if this solves your problem. If so, then you can determine, by trial and error, which program(s) are involved.
One specific solution for this was provided by Microsoft support. ” In Control Panel | Administrative Tools | Services. (You can also get this by launching SERVICES.MSC from a Run box. This utility is also built into the Computer Management console.) Stop the Nvidia Driver Helper service. Many other friends quickly confirmed that this solved this “extremely slow shutdown” problem for them.
POWERDOWN ISSUES.
“Powerdown issues” are quite distinctive from “shutdown issues.” I define a shutdown problem as one wherein Windows doesn’t make it at least to the “OK to shut off your computer” screen. If Windows gets that far, or farther, then it has shut down correctly. However, the computer may not powerdown correctly after that. This is a different problem, and I encourage that people reporting these issues to make a very clear distinction in their labeling.
When Windows XP won’t powerdown automatically, the APM/NT Legacy Power Node may not be enabled. To enable this, right-click on the My Computer icon, click Properties | Hardware | Device Manager | View. Check the box labeled “Show Hidden Devices.” If it’s available on your computer, there will be a red X on the APM/NT Legacy Node. Try enabling it and see if this resolves the powerdown problem.
This should resolve the powerdown issue in most cases. However, other factors can sometimes interfere with correct powerdown functioning. In that case, consider the following tips:
· If you are changing the default power settings in the BIOS, it can lead to a powerdown problem. Restoring all BIOS power settings to default will likely fix it.
OTHER KNOWN ISSUES & HINTS.
· BIOS UPGRADE.
As with every new operating system that comes along - especially one that is as much of a “step up” as Windows XP is from Windows 9x - the recommendation is made to be sure your BIOS is updated. Many people have reported that this has solved their shutdown problems (and had other advantages) with Win XP, just as it has in earlier versions of Windows.
“Powerdown issues” are quite distinctive from “shutdown issues.” I define a shutdown problem as one wherein Windows doesn’t make it at least to the “OK to shut off your computer” screen. If Windows gets that far, or farther, then it has shut down correctly. However, the computer may not powerdown correctly after that. This is a different problem, and I encourage that people reporting these issues to make a very clear distinction in their labeling.
When Windows XP won’t powerdown automatically, the APM/NT Legacy Power Node may not be enabled. To enable this, right-click on the My Computer icon, click Properties | Hardware | Device Manager | View. Check the box labeled “Show Hidden Devices.” If it’s available on your computer, there will be a red X on the APM/NT Legacy Node. Try enabling it and see if this resolves the powerdown problem.
This should resolve the powerdown issue in most cases. However, other factors can sometimes interfere with correct powerdown functioning. In that case, consider the following tips:
· If you are changing the default power settings in the BIOS, it can lead to a powerdown problem. Restoring all BIOS power settings to default will likely fix it.
OTHER KNOWN ISSUES & HINTS.
· BIOS UPGRADE.
As with every new operating system that comes along - especially one that is as much of a “step up” as Windows XP is from Windows 9x - the recommendation is made to be sure your BIOS is updated. Many people have reported that this has solved their shutdown problems (and had other advantages) with Win XP, just as it has in earlier versions of Windows.
No comments:
Post a Comment