 In Windows XP, there's no such thing as an elegant crash. A dialog box appears suddenly, demanding your attention. A cryptic stop message, accompanied by a red exclamation point, interrupts your daily routine. Usually the application or operating system task you were performing comes to a screeching halt.
Thankfully the most common crashes—the kind that occurs when you were just trying to change your video resolution or copy a file—are not too detrimental. You can sometimes just reboot or close the dialog box and get back to work. In other instances a crash can signal a more serious problem with the operating system—one that might take hours to resolve or, worse, a long phone call to tech support.
Fortunately Microsoft has provided several new diagnostic features in WinXP. One of the most important: There's a way to send bug reports to Redmond, where technicians can track the issue and fix any problems that seem to be rather widespread. WinXP sometimes provides clues about what went wrong, including an error code or message that you can use to address the problem right away. Interestingly many of the errors in WinXP are brand new problems not found in previous 16-bit versions of the operating system, such as Windows 98. So, by following the tips and ideas below, you can fix problems in WinXP and restore your computer to good working order.
Most Serious Errors
Serious operating system errors are often the most frustrating to fix because they often involve a recurring system conflict. When you see a blue screen with a vague message about kernels and page faults, you might be tempted to just bring the computer back to the shop and start over. Fortunately even the most serious errors can be resolved by following some specific steps. No conflict occurs randomly just to spoil your day; they are usually the result of a program you have installed recently, a new hardware device you've attached to the computer, or some other traceable and logical cause. The good news is that once an error occurs, you can fix the problem, and it probably won't occur again. Every problem, at least on a computer, has a solution.
Error Message: "Stop: 0x00000077" or "KERNEL_STACK_INPAGE_ERROR"
Translation: This could be a boot sector virus or a corrupted WinXP paging file.
Solution: Reboot your computer. In some cases when Windows starts up and runs the Autochk program, any bad sectors will be remapped—problem solved. (Just keep an eye on your computer, though, to see if the error message reappears.) Otherwise, if Autochk does not fix the problem, your computer may have defective or poorly seated RAM modules. If you're comfortable opening the computer case, you can reseat the RAM modules so that they are firmly snapped into position (ground yourself properly beforehand). Also, double-check all the other PCI (Peripheral Component Interconnect) and AGP (Accelerated Graphics Port) cards to make sure they are seated properly. Run a virus-checking program such as Norton AntiVirus 2004 (www.symantec.com) to scan for a boot sector virus.
Error Message: "Stop: 0xA0" error message during hibernation
Translation: This problem can occur on a notebook if you use the Standby option (by selecting Start, Turn Off Computer, and Standby), which puts the computer to sleep. The CD-ROM driver conflicting with the hard drive driver usually causes the error.
Solution: Microsoft fixed this problem with the WinXP Service Pack 1, available at www.microsoft.com.
However, if you're not connected to the Internet and can't download the service pack (and the error keeps causing your notebook to crash), you can just avoid the problem by adjusting the battery-saving features on your computer to never hibernate. That way, even if you pause to answer the phone or fix dinner, your notebook will never hibernate and crash.
Error Message: "Stop: 0x0000000A" error message when you fast switch between users
Translation: This rare but troublesome error can occur if your multimedia keyboard uses the Netropa driver and you have enabled fast user switching. Typically, when you log off your computer (using Start and Log Off), all the programs you are running will shut down automatically. If you enable Fast User Switching in the User Accounts control panel, your programs will remain active. When you log off, the keyboard driver will cause a stop error.
Solution: You'll need to download and install a new keyboard driver, available at www.netropa.com/download/mmkbd/download.html
Error Message: "Stop: 0x0000007B" or "0x4,0,0,0"
Translation: The boot sector of your computer (the portion of memory that handles computer start ups) has become corrupted, causing an error on a blue startup screen.
Solution: Boot sector problems are difficult to troubleshoot because they occur before WinXP even loads. You won't be able to just run a program, edit a WinXP Registry file, or remove a device driver. The 0x0000007B error usually includes an error code such as 0x4,0,0,0 that can help a Microsoft tech support engineer troubleshoot the problem. However, you can perform a few diagnostic steps on your own.
First, try rebooting a second time to see whether the stop error reoccurs. Sometimes WinXP may run the Autochk program and correct a disk error automatically. Second, think about whether you have added any new hardware devices recently, such as a second hard drive or a SCSI (Small Computer System Interface) drive. Try removing that drive and restarting. Third, you can remove your primary hard drive and install it on another computer. Often a boot sector problem can be resolved by using a different computer because the second computer may be using a more recent BIOS (Basic Input/Output System; the software that controls the computer startup procedure). As a last resort, you can reformat the drive to correct a boot sector problem, which will require that you reload WinXP.
Error Message: "Stop: 0x9F"
Translation: This error occurs most commonly on notebooks that are frequently entering standby mode or resuming from hibernation. The problem has to do with the power management features on the notebook conflicting with a device driver.
Solution: The quickest solution is to remove the driver that is causing the problem, but finding the guilty party can be difficult. Conflicts occur with unsigned drivers that are not officially sanctioned by Microsoft to work with power management features (or with WinXP in general). You can use the Sigverif.exe tool to see which unsigned drivers might be causing problems. (Before you run this program, it's a good idea to close any open applications and make a backup of your most important data because the computer will enter a diagnostic-scanning mode.) |
The Sigverif.exe tool will help you find error-causing drivers.
|
Click Start and Run and type Sigverif.exe. Click the Advanced button. Select the option to Look For Other Files That Are Not Digitally Signed . . . and click OK. In the Look In This Folder field, type C:\Windows\system32\drivers (substitute C for the drive letter you use). Next, on the Logging tab, make sure the Save The File Signature Verification Results To A Log File option is checked and then click OK. Now click Start. Windows will save the Sigverif.txt file to C:\Windows, so open that file with Notepad to see a listing of all signed and unsigned driver listings.
Use the Device Manager to disable unsigned drivers you find, one by one, until the problem is fixed. Click Start, Control Panel, and System. Select the Hardware tab and click Device Manager. Look for the driver you want to disable. (You may need to use the Show Hidden Devices option under the View menu.) Right-click the driver and select Disable. You may be able to remove the program and any associated drivers by using the Add Or Remove Programs control panel.
Another trick: You can just look in the WINNT\SYSTEM32\Drivers folder for any drivers that may be causing the power management problems and rename the file, which means WinXP won't load that driver after you reboot.
Use the Sigverif.exe program to look for unsigned drivers that may be causing power management problems in WinXP.
Error Message: "Stop: 0xC2" or "Stop: 0x000000C2"
Translation: A device driver has caused a WinXP kernel error.
Solution: A device driver has caused a conflict with the kernel in WinXP, which is the heart of the operating system—the most important code that is used to run applications and manage memory. A device driver error is like a faulty part on an automobile: The best way to get the operating system running again is to remove the driver. Unlike the "Stop: 0x9F" error in WinXP, which unsigned drivers can cause, a signed or unsigned driver can cause the "Stop: 0xC2" error. The best method for resolving this problem is to think about any new programs you have installed recently or new hardware devices that you have attached and that have installed a driver automatically. Try uninstalling any new programs you've added recently (by using the Add Or Remove Programs control panel) and unplug any hardware devices. Reboot your computer.
Error Message: "0x000000D1" error when you turn your computer off
Translation: A USB (Universal Serial Bus)-related error related to the OHCI (Open Host Controller Interface) driver, which controls USB file size and memory allocations.
Solution: This error can occur when you transfer large files such as photo and videos over a USB connection to your computer. WinXP does not allocate enough resources for the large file transfers. To prevent this error from occurring, you'll need to download the WinXP Service Pack 1 at www.microsoft.com/windowsxp/pro/downloads/servicepacks/sp1/default.asp
Error Message: "0xc000026C" or "Stop: 0xc0000221 Unable to Load Device Driver" error occurs when you start WinXP
Translation: This error occurs during the WinXP startup process if a critical system driver is missing or damaged or if the file User32.dll is missing or damaged.
Solution: WinXP is not too forgiving if you happen to delete a .SYS file in your WINDOWS\System directory. One missing file and the operating system will fail during startup. There's only one solution: You'll need to run the Recovery Console and replace the missing or damaged file; otherwise, you'll have to reinstall WinXP altogether. Fortunately the error message contains the driver file name, so fixing the error is relatively easy.
To run the Recovery Console, first insert the WinXP disc in your CD-ROM drive and then reboot. Newer computers typically include a startup option to boot from the CD; otherwise, you'll need to enter your BIOS (usually by pressing the DELETE key) and change the boot sequence so that your computer boots from CD. Save the BIOS, and your computer will continue the startup process.
When you see the Welcome To Windows screen, press r to use the Recovery Console. In the instructions below, drivername is the name of the file listed in the error message. (After each command, press ENTER.)
Type in your login information. Then, at the command prompt, type:
cd windows\system32\drivers
Then, type:
ren drivername.sys drivername.bak
Finally, type:
copy cd-rom:\i386 drivername
The Recovery Console will reboot the computer. If the user32.dll file caused the problem, you need to type these commands into the Recovery Console instead and then reboot:
cd windows\system32
ren user32.dll user32.bak
expand cd-rom:\i386\user32.dl_ c:\windows\system32\user32.dll
If replacing the files still doesn't work, you'll need to do a repair install of WinXP, which is an option listed at the Welcome screen when you boot from the CD. Note that a repair install won't delete your documents and important files, but you will lose all your Windows settings, Internet favorites, and other operating-system-related files.
Error Message: "0x0000008E" error on a blue screen in WinXP
Translation: This rare (and random) error can occur when a program references an incorrect memory address, causing your computer to crash.
Solution: Microsoft has released a hotfix, which you can install and run to fix the problem. You'll need to call Microsoft technical support to obtain the hotfix, however. It's not available online (at least, not yet). If you only see the error occasionally, you might consider waiting for another service pack release for WinXP, although living with the error is probably counter-productive. For support options visit support.microsoft.com.
The good news is that if the tech support engineer determines that you do need the hotfix, you won't be charged for the call.
Error Message: "STOP: 0x0000001e"
Translation: You're using an older version of the Aspi32.sys CD-ROM driver.
Solution: You'll need to download the latest driver from Adaptec (www.adaptec.com). Go to the site, look for the Support area, and then click Downloads. Download the latest version and install the new driver.
Error Message: "WinXP could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM"
Translation: Your WinXP Registry is corrupted and requires restoration.
Solution: This is one of the most serious errors you're likely to encounter in WinXP, and the solution involves four specific steps. You'll need to copy new files from the WinXP setup disc, reinstall GUID (globally unique identifier) files, delete critical system files that are causing problems, and use the RestorePoint feature in WinXP. Although the fix may seem complicated, it's clear and straightforward.
You can access the complete solution at Microsoft's Knowledge Base; look up article number 307545.
However, because you will be replacing system files, there's always a possibility that your system could become even more unstable, that you could replace the wrong file and have to start over, or that one of your previous RestorePoint files is also corrupt. If you have a backup of your most important files and don't mind losing your WinXP settings (for example, Internet Favorites, desktop wallpapers, etc.), then a faster and easier solution—one that will eliminate any problems once and for all—is to reformat your hard drive and reinstall WinXP from scratch.
Error Message: "RUNDLL Error loading irprops.cpl" error when you start WinXP
Translation: A Bluetooth Authentication Agent DLL file is missing or you have uninstalled the Bluetooth Authentication Agent, but a Bluetooth-related entry still exists in the WinXP Registry. |
Cleaning a specific file from your Registry can help solve Bluetooth errors.
|
Solution: Bluetooth is the short-range wireless standard for connecting handheld devices and phones to your computer so you can transfer files back and forth. To solve the problem, remove the Bluetooth Authentication Agent using the Add Or Remove Programs control panel. Sometimes when you remove Bluetooth, the Registry entries still attempt to control authentication between the device and your computer. To remove the Registry entry, click Start and Run, type regedit, and click OK. Look for the following Registry entry: HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\WINDOWS\CURRENTVERSION\Run.
Right-click BluetoothAuthenticationAgent and click Delete. Close Registry Editor and restart your computer.
Use the WinXP Registry program as a last resort to troubleshooting the most arcane error messages.
Error Message: "8E Stop" error on a blue screen
Translation: When you transfer a file to a USB device, the Usbser.sys driver generates an error on a blue screen. Usually the file is shown with the error, although you may just see the stop error and not the name of the offending driver.
Solution: You'll need to call and request a hotfix for this problem. To contact Microsoft go to support.microsoft.com.
Most likely, because this is an operating system problem, you won't be charged for the tech support call. Another option: Try rebooting, copying the file to your USB device again, and seeing if the error reoccurs.
Error Message: "STOP: 0x00000073 (0x00000001, 0xc000017d, 0x00000002, 0xfc96fcc0) CONFIG_LIST_FAILED"
Translation: WinXP is unable to access a core system file.
Solution: One of the more common stop errors in WinXP, this problem occurs when you have run low on either disk space or system memory (or both). If you are running low on disk space, reboot your computer and delete files that you don't need anymore. You can do a search (Start and Search) to look for large files that you may have forgotten about, such as game files and large photos. Under Search, click All Files And Folders, click the What Size Is It? arrow, and then select Large (More Than 1 MB). Click Search and view the list by size by clicking the Size tab. Look through the largest files and delete the ones that are taking up unnecessary space.
If system memory ran low and caused the error, you can usually solve the problem just by rebooting and running fewer programs at the same time. Upgrading your RAM is only important if you tend to multitask several applications at the same time.
Error Message: "Stop: 0xc0000218 (0xe11a30e8, 0x00000000, 0x000000000, 0x00000000) UNKNOWN_HARD_ERROR" or "Stop: 0xc0000218 {Registry File Failure} The Registry cannot load the hive (file)."
Translation: This occurs due to a corrupted Registry, corrupted hard drive, a driver that is damaged and is attempting to load into system memory, or if the RAM on your computer is damaged and causing problems with the Registry.
Solution: There are several troubleshooting options available, each one intended to address one of the four possible causes. You should first try rebooting the computer and see if the Load Last Known Good Configuration option appears. Sometimes, by using this option, you can load a previous version of the Registry that is not corrupted. The next step involves using the WinXP Recovery Console program to rebuild the system Registry, a complicated process described online at Microsoft's Knowledge Base in article number 307654.
The other options are much more drastic: reformatting your hard drive completely and reinstalling WinXP and replacing the RAM on your computer. One of the problems with solving this error is that, if the problem is RAM-related, you could replace the hard drive and still experience problems (and vice versa). Our advice is to consult a computer repair technician or call Microsoft tech support engineers who can further diagnose the problem and suggest the best course of action.
Application Errors
Not every program runs perfectly on WinXP. However, application errors are generally easier to diagnose than an operating system error. The worst-case scenario is that you will have to remove the application and try something that works better in WinXP. Outdated applications such as CD-backup software and programs designed to run on the previous 16-bit versions of Windows can cause frequent error messages, usually when they access memory incorrectly. WinXP handles most applications errors gracefully, providing a message and shutting down the program. WinXP itself usually remains quite stable after an application error (which was not true in previous iterations of the operating system). The best rule of thumb is that, if the program is outdated, you can usually obtain an updated release by going to the company Web site and downloading and then installing the upgrade.
Error Message: "This Application Requires the Windows Installer to Run"
Translation: The application was loaded incorrectly on your computer, is located on a network drive that is not available, or needs to be reconfigured.
Solution: Usually, the best course of action is to reinstall the application from the source CD, making sure that you install to a local drive. If the application was installed originally to use a network drive, you'll need to make sure you have access to that drive. Click Start and My Network Places to see which network drives are available. (In an office environment, you might call the network administrator to see if a network drive is not accessible.) In some cases you can search for the actual program file and double-click the executable file to get the application to run. Click Start and Search and type the name of the program file (for example, Excel.exe). Then, when you find the program, double-click on it to see if the program will run.
Error Message: Ole32.dll may cause an error message in WinXP
Translation: An outdated version of MSN Messenger has caused a memory leak.
Solution: This error sometimes includes another message: "Msmsgs.exe has encountered a problem and needs to close. We are sorry for the inconvenience." The fix is to visit messenger.msn.com and download the latest version of the instant-messaging client.
Error Message: "CD Recording Software Will Cause Windows to Become Unstable" error when you start Windows
Translation: You are using an outdated version of Easy CD Creator (www.roxio.com).
Solution: You'll need to remove the Registry entries for Easy CD Creator. Contact Roxio technical support at www.roxio.com/en/support/index.jhtml. However, you may be able to resolve the problem by upgrading to the latest version of Easy Media Creator 7.
Error Message: Explorer.exe may generate an application error when you close a folder
Translation: Internet Explorer causes WinXP to freeze when you open or close folders.
Solution: You may not use IE for any other task than browsing the Web, but it's also useful for browsing your own files and folders. Unfortunately this random error was a problem with the Service Pack 1 release. No error message appears on-screen; your computer will just stop responding. The solution is to download a new file (Duser.dll) for WinXP that fixes the problem at www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=49E589AE-2F93-48DC-A39A-C9D98DADA7A5.
Another option: If you have Service Pack 1 installed, you can safely browse files by using the My Computer icon on your Desktop.
Error Message: "Install.exe is not a valid win32 application" or "Setup.exe is not a valid win32 application."
Translation: This error appears when you attempt to install a program designed to run on older versions of Windows on the new 64-bit version of the operating system.
Solution: You won't be able to install or run 16-bit applications on the new 64-bit version of WinXP. The solution is to obtain a 32-bit or 64-bit version of the program you are trying to install. In some cases you can obtain a 32-bit installer for the application and then still run the older application, even in 16-bit mode.
System Maintenance Errors |
Use the Disk Defragmenter as a part of your maintainance routine to help stop errors before they start.
|
File and system maintenance errors seem to fall into two categories: routine errors with a straightforward solution and more complex errors that may be a symptom of a more critical problem. In most cases a system maintenance error occurs because you have moved files and folders around so much and because you have installed so many programs that Windows is having difficulty keeping track of all the changes and additions. One routine maintenance task that may help prevent problems: run the Disk Defragmenter tool. Click Start, All Programs, Accessories, System Tools, and Disk Defragmenter. The program will perform a disk analysis and then suggest whether you should run defrag. Just follow the advice of the program to decide if your disk needs to be defragged or not. Run this utility about once per month, or more often if you are constantly adding and deleting files, folders, and programs.
Run the Disk Defragmenter program in WinXP to make sure the operating system doesn't become clogged trying to manage your files and programs.
Error Message: Unable to start programs with an .EXE extension
Translation: A virus has infected your computer.
Solution: Many of the most destructive viruses will cause EXE problems. You'll need to install and run a virus protection program, such as Symantec's Norton AntiVirus 2004 (www.symantec.com). Many of the most powerful antivirus programs also include virus-prevention tools that scan incoming email and can watch for boot sector viruses.
Error Message: "The Target can not handle this type of document" error appears when you try to copy a file in WinXP SP1
Translation: This is an operating system bug.
Solution: This error occurs when you right-click a file and use the Send To command to copy a file that is not housed in the My Documents folder to some other location, such as a network drive. The solution is to use the Send To command from the Desktop. The bug is also quite innocuous: although you will see the error, the file actually copies over correctly. Microsoft will address the bug in the next service pack update.
Error Message: "Delayed Write Failed" error when you manage files in WinXP
Translation: You have selected the Enable Write Caching On The Disk option in your computer's BIOS or you have used a 40-wire cable to connect a UDMA (Ultra-Direct Memory Access) hard drive to your IDE (Integrated Drive Electronics) controller instead of an 80-wire, 40-pin cable.
Solution: You should replace the 40-wire UDMA cable with the 80-wire, 40-pin cable (or bring the computer to a service shop to perform the replacement). If that doesn't solve the problem, you should enter the BIOS (usually by pressing the DELETE key as the computer starts up) and disable the write-caching option. Using the BIOS on your computer incorrectly can cause new (and harder to diagnose) problems, so you should consult the manual that came with your computer or call for technical support before enabling or disabling any other features. Make sure that if you do use the BIOS and disable disk caching that you save your changes in the BIOS.
Error Message: "Bad Command Structure" error message occurs when you extract files from a compressed folder
Translation: You've discovered another minor bug in WinXP when you try to extract a compressed file but only if you type in a directory that does not exist on your computer.
Solution: WinXP has built-in file compression capabilities. This error occurs when you right-click on a compressed file (with a .ZIP extension) and decide to extract the file. WinXP presents a dialog box where you can type in the directory for the extracted file. If you type in an invalid destination, you'll receive an error that WinXP was unable to create the directory. Microsoft will undoubtedly address this problem in the next WinXP service pack.
Memory Errors
Memory errors occur when your computer runs low on disk space, you open too many applications at once, or when the RAM in your computer becomes corrupted. Fortunately most memory problems can be resolved quite easily, just by freeing more space on your hard drive, adding a memory module or two, or closing out of applications. Some memory errors can be resolved once and for all by just rebooting your computer and waiting for the Autochk program to run, which fixes common hard drive problems. And if the virtual memory paging file (which provides more memory when your RAM runs low) is overloaded, you can usually just reboot or adjust the size of the paging file. Problem solved!
Of course, other memory problems, such as a corrupted hard drive or corrupted RAM, are more difficult to diagnose. In those cases you may need to experiment with a variety of troubleshooting techniques, such as removing RAM modules one by one until you find the culprit. In some rare cases, you may need to reformat the hard drive and start fresh with a new WinXP installation.
Error Message: The StgCreateDocFile() function causes an "STG_E_FILEALREADYEXISTS" error in WinXP
Translation: A memory leak has occurred that's related to a core operating system file.
Solution: This is a known bug that occurs when a program uses the StgCreateDocFile core operating system function in WinXP. It's actually a code flaw that will cause the memory leak, leading to additional error messages until the computer becomes unstable and you have to reboot. The solution is to obtain the WinXP Service Pack 1, available at www.microsoft.com.
Error Message: "Your system is low on virtual memory. Windows is increasing the size of your virtual memory paging file. During this process memory requested for some applications may be denied."
Translation: You are running too many applications at the same time, or there is a conflict with Symantec's Norton Internet Security program. |
Windows XP lets you specify how much space Virtual Memory uses.
|
Solution: If you see this large balloon message in the lower-right corner of your screen, it's a good idea to reboot the computer to free system resources. In some cases, you can just close some applications to free more memory, although it may just be a matter of time before the computer starts running too slow. If you are not running more than just a couple of applications, WinXP may be conflicting with Norton's Personal Firewall program, especially if you have configured that program to start automatically by using the Registry as opposed to using the WinXP Startup Group folder.
For more information about this Symantec error (including how to configure the Personal Firewall correctly for WinXP), visit the company's support site at www.symantec.com/techsupport and type the following ID: 2000040412261536.
Error Message: "System has recovered from a serious error DRIVER_IRQL_NOT_LESS_OR_EQUAL"
Translation: You have corrupted RAM installed, the wrong memory modules installed for your computer, or the Windows paging file is corrupted.
Solution: This error can occur just after you install new RAM chips, so the easiest solution is to remove the new RAM (after properly grounding yourself, either by using a grounding strap or touching the power supply). If you're not sure if the RAM modules you installed work with your computer, you can visit Microsoft's Knowledge Base and look up article number 65416.
If you know that the RAM should work (for example, if the modules came with the computer and have always worked), then you might try increasing the paging file size. First, click Start, go to My Computer, right-click, and select Properties. Click the Advanced button and, under the Performance tab, click Settings. Click the Advanced tab and, under the Virtual Memory area, click Change. Click the No Paging File option and click OK for each open dialog box. Now restart your computer. Open Properties again for My Computer and go back to the Virtual Memory area. Click Change and select the System Managed Size option. Click OK to close each dialog box again and restart.
Adjust the paging file size to prevent virtual memory errors from occurring.
Error Message: "System restart has been paused: Continue with system restart. Delete restoration data and proceed to system boot menu."
Translation: During hibernation, the computer accessed memory incorrectly.
Solution: This error occurs on notebooks occasionally after returning from hibernation, the sleep mode in WinXP. There's no option for returning to the Desktop, so you may lose your work. Use the option to Delete Restoration Data And Proceed To System Boot Menu, which will cause WinXP to reboot. Microsoft will fix this problem in a future WinXP update. For now you can set the power management features on your notebook to use standby mode but not hibernate, but only if the error occurs frequently.
Error Message: "STOP: 0x00000074 (0x00000003, 0x00000002, 0x80087000) BAD_SYSTEM_CONFIG_INFO" or "The following file is corrupted: toside.sys"
Translation: One of the RAM modules on your computer is corrupted or won't work with your computer correctly.
Solution: If you recently upgraded your RAM, try removing the new chips you installed. (Make sure you have properly grounded yourself, either with a grounding strap or by touching the power supply.) If you are using the RAM that came with your computer, try removing one module at a time and rebooting each time to see if the error reappears. If the error doesn't occur, replace the RAM module that is causing the error. 
(NOTE: The "toside.sys" error only appears if you try to boot from the WinXP installation CD as a way to correct the problem. WinXP won't boot normally or from a CD if a RAM module is corrupted.)
by John Brandon
Most Hilarious Error Message
Error Message: "Stop: c0000218 {Registry File Failure} The Registry cannot load the hive (file): \SystemRoot\System32\Config\SOFTWARE or its log or alternate"
Translation: You are attempting to install Windows XP on a corrupted or outdated hard drive. Solution: This message may cause a few chuckles when you consider that Microsoft uses the word "hive" in reference to the core operating system files. It's funny, considering that WinXP can seem like a beehive of files at times (especially if you start exploring the Registry). It's hilarious, when you start thinking about how there may be a few "Star Trek" fans at Microsoft. In the series, the Borg "hive" is the central core of the alien race. And, incidentally, the solution to this problem is not as earth-shattering as you might think: If you are attempting to install Windows on a corrupted or outdated hard drive, it's an error message that's quite helpful. Even if you could install WinXP, crashes would undoubtedly occur. Better to just use a new hard drive or reformat the drive entirely.
Most Obvious Error Message
Error Message: "Another copy of this application is already running"
Translation: The application you are trying to start is already running. Solution: You can just switch over to the application you are trying to start instead. This error can also appear if you have upgraded from Windows 98 to Windows XP, which makes it much less obvious and more difficult to fix. You'll need to rename some files and reinstall some WinXP files, but for most of us, the error only appears when you don't notice that the program is already running.
Most Annoying Error Message
Error Message: "System Has Recovered from a Serious Error" message after every restart
Translation: Windows XP error reporting sometimes gets stuck in memory and won't refresh, so the error will appear each time you restart. Solution: This is an annoying error message because, even if you fix the problem, WinXP will still prompt you to send the error to Microsoft after every reboot. It's one of those errors that some of us just live with, even to the point where we expect to get the error after a reboot and just click Don't Send each time. However, you can correct the problem. Click Start and My Computer, and then right-click and select Properties. Select the Advanced tab and click Settings in the Performance area. In the Virtual Memory area, click Change. Under Paging File Size For Selected Drive, click No Paging File and click set. You'll see two warnings; just click Yes on both of them and then select the System Managed Size option. Close out of all the dialog boxes and reboot.
Most Frustrating Error Message
Error Message: "Computer Configuration\Windows Settings\Local Policies\Security Options\Shutdown: Clear virtual memory pagefile."
Translation: The secpol.msc and sceregvl.inf localization files are corrupt.
Solution: For anyone who uses foreign language localizations of WinXP, you know that errors can occur that are difficult to understand and troubleshoot, especially if the translations are wrong. For example, when the French location files cause security problems and virtual memory paging file errors, the message "Arret: Creer un fichier d' échange de memoire virtuelle" will appear. If you know French, you know that the error is meaningless. Worse, there is no fix for the error because Microsoft is still addressing the problem. So: frustrating, translated incorrectly, and not fixable!
Most Common Error Message
Error Message: "Missing shortcut"
Translation: You have tried to start a program using a shortcut that is no longer valid.
Solution: This common error occurs because Windows XP doesn't automatically change shortcuts if you move a program file to a new location (for example, if you decide to run a card game program from the root of your C: drive instead of the Program Files folder). The solution: Right-click the shortcut. Click in the Target field and change the path to the correct EXE application. As an option, you can let WinXP attempt to find the missing application. This can take some time, so it's usually easier to just click the Browse button (in the Missing Shortcut dialog box) and look in your Programs Files folder for the correct application.
Most Difficult To Fix Error Message
Error Message: "Error 1402. Could not open key."
Translation: Microsoft Office 2000 causes this error when you try to run the application suite on Windows XP. Solution: There is a complicated fix to this error message, which involves some detailed editing in the system Registry (not for the uninitiated). One of the problems with editing the Registry, though, is that you can do more harm than good if you enable or disable just one simple option by mistake. Also, you'll need to know how to search for a specific Registry key (HKEY_LOCAL_MACHINE on Local Machine in this case). More importantly, beacuse Office 2000 is several versions older than the latest release, you may experience additional errors while running Word, Excel, and other programs—such as unexpected crashes and a constant reminder to register the software. The best solution is to call Microsoft tech support and discuss various options, such upgrading to Office 2003 or updating the Windows Registry with help from the engineer.
Most Confusing Error Message
Error Message: "Load needed DLLs for Kernel"
Translation: Important Windows XP program files are missing or damaged. Solution: This error is confusing for several reasons. First, many users may not understand that the kernel is the main program file in WinXP, the heart of the operating system. Second, the term "load needed DLLs" is just ambiguous enough that you might not know how serious the error really is. Unfortunately, this problem cannot be corrected by just rebuilding the system Registry or restoring files from the WinXP installation CD. You'll need to perform an "in-place install" of the operating system, which will destroy most of your settings such as Internet Favorites and all of your applications. The good news: An in-place install will usually not overwrite files in your My Documents folder and will keep other files located in other directories (as long as they are not operating-system-related). To perform an in-place upgrade, you'll need to boot from the WinXP CD, which might require that you enter the BIOS (Basic Input/Output System) of your computer and enable the Boot From CD option. Then, when the install starts up, select the Install WinXP option and follow the remaining instructions.
Most Unusual Error Message
Error Message: "Fatal System Error: 0x000000a0 (0x00000002,0x00070124,0x00000000,0x00000000)"
Translation: If you happen to own a Microsoft Sidewinder Game Pad Pro (not the joystick model), you may experience a unique problem. If you just happen to be running WinXP (as opposed to any other operating system) and you decide to unplug the USB (Universal Serial Bus) cable while WinXP is starting up, you will see the fatal system error and a blue screen, preventing you from accessing your Desktop.
Solution: Microsoft is working on a fix for this error, but at press time it is still unresolved. Fortunately, the workaround is rather simple. Just make sure you don't unplug the Sidewinder cable when the system is starting.
|
|
Email This
Print This
In Windows XP, there's no such thing as an elegant crash. A dialog box appears suddenly, demanding your attention. A cryptic stop message, accompanied by a red exclamation point, interrupts your daily routine. Usually the application or operating system task you were performing comes to a screeching halt. 
