Techmeme is a great site, not only because it lists todays stories, but it lists all the popular stories circulating blogdom. Today I came accross this article on people having trouble with random shutdowns on their Macbooks.
Do a google search for “macbook random shutdown” and you’ll find many people with similar problems reporting on various forums. At present, this issue has not been picked up by the mainstream PC news media. However, one should also note that only a fraction of those with problems are suffering this particular fault. A large number of other reasons must be ruled out before a MacBook owner should become convinced their machine is one which suffers this problem. Bad RAM, poorly seated RAM, improperly installed hard drive, corrupted OS, corrupted plists, bad batteries, bad chargers, corrupted PMU, and corrupted NVRAM all need to be ruled out first!
My own MacBook suffered the random sudden shutdown malady and eventually required complete replacement after a logic board replacement did not solve the issue. Some of the MacBooks appear to have a hardware problem which surfaces after a period of use. Many reported their problems starting after a month of ownership. Coincidentally, that also coincided with the release of 10.4.7, but most likely that is not at the root of the sudden, random, shutdown problems.
The article goes on to list troubleshooting techniques and things to try, definitely work looking at if you are having similar troubles.
If it appears that Win XP is not shutting down, give it some time. Some users report a minute or longer for shutdown to visibly start. Generally, this is a consequence of software that is running when shutdown is attempted; it also may have something to do with particular hardware. If you experience 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. In Control Panel | Administrative Tools | Services, stop the Nvidia Driver Helper service. (You can also get this by launching SERVICES.MSC from a Run box.) Many other newsgroup participants quickly confirmed that this solved this extremely slow shutdown problem for them.
Another possible solution: In Win XP Professional, the Group Policy Editor has a security option to clear the pagefile at system shutdown. The same setting also forces the hibernation file to be wiped at shutdown. These processes take long enough that users may think that shutdown has hung. Since someone actually has to have set this policy, the problem will be pretty rare, but is worth mentioning. To change the setting, click Start | Run, type GPEDIT.MSC, click OK. Drill down to Computer Configuration | Windows Settings | Security Settings | Local Policies | Security Options. In the right pane, find Shutdown: Clear virtual memory pagefile.
During shutdown or reboot, Win XP may hang (stop responding) at the saving your settings screen. During such a hang, there is no response to Ctrl+Alt+Del; the mouse may or may not work. The problem may be intermittent.
This is a known bug in Windows XP, for which Microsoft has a supported fix. Because this patch is scheduled for further quality assurance testing in the future, Microsoft only recommends that you install it if you have a serious problem; otherwise, they recommend waiting for Service Pack 1, which will include the more permanent version of the fix. To learn how to get this patch, see Windows XP Stops Responding (Hangs) During Windows Shutdown.
NOTE: The article says the patch may only be obtained by contacting Microsoft. However, it is now available on the Windows Update site under Recommended Updates for Win XP Professional, titled Restarting Windows XP.
As a workaround, you may resolve this problem by dismantling the Windows XP logon Welcome screen. In the Control Panel, click User Accounts, then click Change the way users log on or off. Uncheck the box that says Use the Welcome screen. This removes the initial logon screen with individual icons for each user and, instead, pops up the classic logon prompt that requires each user to type a user name and password.
The majority of Win XP shutdown problems reported thus far have been that it reboots when shutdown is attempted. This may be a global symptom emerging from several distinct causes, because, by default, XP executes an automatic restart in the event of a system failure. Therefore, more or less anything compromising the operating system during the shutdown process could force this reboot.
Disabling the restart on system failure feature may permit the exact cause to be isolated: Right-click on My Computer, click Properties, click the Advanced tab. Under Startup & Recovery, click Settings. Under System Failure, uncheck the box in front of System reboot.
Here are some things that have produced this reboot-instead-of-shutdown symptom:
By now, the Roxio/Adeptec Easy CD / Direct CD software is well documented as being the major cause of this undesirable shutdown behavior. SOLUTION: Roxio has released new drivers here to solve this problem in both the Platinum and Basic editions of Easy CD Creator 5. As expected, at least half of the Win XP shutdown problems went away with the release of these patches.
One warning about this patch: Be sure to read the directions! Roxio Easy CD Creator Platinum 5.0 can be a real hassle to get working under Win XP, and there is the risk of your computer not booting if you blindly go ahead and install it without first consulting the Roxio Web site. It should also be mentioned that Roxio’s Take Two backup program (normally part of Easy CD Creator 5 Platinum) is uninstalled when the Roxio patch is applied.
Direct CD. Many Easy CD users (but not all) found that installing Easy CD 5.0 does not cause the shutdown problem, provided they do not install the Direct CD component.
UDFRINST. Several people solved this reboot-on-shutdown problem by deleting the UDFRINST file. This file is part of the Roxio CD-RW software for systems not using Direct CD.
CDRALW2K.SYS. file (version 220.127.116.118) has been identified as the Roxio file causing a shutdown problems and error conditions. When the file is deleted or renamed, the problems went away. (Of course, you lose your CD functionality that way, too.)
Whether or not APM is enabled makes a difference but the effect could go two ways. Some users report that XP reboots on shutdown if APM is enabled, but shuts Windows down just fine if APM is disabled. Other users report exactly the opposite behavior. The issue seems related to the computers specific hardware or BIOS so, as with all NT operating systems, stick to the Hardware Compatibility List where possible. Meaning, update your bios.
Y-SB3 Logitech Internet Keyboard can also cause this problem. If you use it as a simple generic keyboard, there’s no problem; but, if you install the Key Commander software that drives the special Internet functions, Win XP will restart instead of shut down. Unfortunately, Logitech has decided that they will not be updating this driver for this keyboard.
Logitech MouseWare 8.6. Windows reboots when shutdown is attempted. The software caused a BSOD with KBDCLASS.SYS. Removing the software solved the BSOD the problem.
When you try to shut down your computer, you may receive an error message similar to the following:
DEVLDR not responding.
If you click End Now , your computer stops responding.
This error may occur if you have the Creative Labs SoundBlaster Live installed on your computer.
Click here for the article
This article refers to resources that you can use to troubleshoot shutdown problems in Windows XP. After you follow the steps in each article in a section, determine if you have resolved the problem by either shutting down or restarting your computer. If you still cannot shut down or restart your computer, continue to the next section in order. Try to shut down or restart your computer at the end of each section.
Click here for the article.