Got an Windows XP tip to share? Or a software tip? Post it here.
Regular Contributor
Regular Contributor
Posts: 558
Joined: Fri Jul 22, 2005 10:40 pm
Location: Accra Ghana


Post by thedon57 » Sun Sep 25, 2005 9:19 am

This Is A Read, Copy And Paste, Hope Members Find It Helpful


Here is a list of the most common STOP error codes, with suggested troubleshooting actions and external resourses for additional information.


A kernel-mode process or driver attempted to access a memory location without authorization. This STOP error is typically caused by faulty or incompatible hardware or software. The name of the offending device driver often appears in the STOP error and can provide an important clue to solving the problem.
If the error message points to a specific device or category of devices, try removing or replacing devices in that category. If this STOP error appears during Setup, suspect an incompatible driver, system service, virus scanner, or backup program.


The Window XP kernal detected an illegal or unknown processor instruction, often the result of invadid memory and access violations caused by faulty drivers or hardware devices. The error message often identifies the offending driver or device. If the error occurred immediately after installing a driver or service, try disabling or removing the new addition.


A problem occurred within the NTFS file-system driver. A similar STOP error, 0x23, exists for FAT32 drives. The most likely cause is a hardware failure in a disk or disk controller.
Check all physical connections to all hard disks in the system and run the Check Disk utility (Chkdsk.exe).
Errors in disk media and in file system can cause a wide range of Windows problems, ranging from an inability to open or save files to blue-screen errors and widespread data corruption.
Microsoft Windows XP is capable of recovering automatically from many disk errors, especially on drives formatted with NTFS.

To perform a thorough inspection for errors, you can manually run the Windows XP Check Disk utility, Chkdsk.exe. Two versions of this utility are available-a graphical version that performs basic disk-checking functions, and a command-line version that provides a much more extensive set of customisation options.

To check for errors on a local disk, follow these steps:
1 Open My Computer, right-click the icon belonging to the drive you want to check, and then choose Properties from the shortcut menu.

2 On the Tools tab, click the Check Now button.

3 In the Check Disk dialog box, select from the following options.

(a) Automatically Fix File System Errors. Select this option if you want Windows to automatically repair any file system errors. If this option is not selected. Check Disk reports any errors it finds but does not change them.

(b) Scan For And Attempt Recovery Of Bad Sectors. Select this option to perform an exhaustive check of the entire disk, locate bad sectors, and recover readable information stored in defective locations.
Note: that selecting this option automatically repairs file system errors as well, even if previous option is cleared.


Failed or defective physical memory (Including memory used in video adapters) is the most common cause of this STOP error. This error may also be the result of a corrupted hard disk or a damaged motherboard.


Your system ram out of page table entries (PTEs). The cause of this relatively uncommon error may be an out-of-control backup program or a buggy device driver. Knowledge Base article 256004, "How to Troubleshoot 'STOP 0x0000003F' and 'STOP 0x000000D8' Error Message in Windows 20000," (, describes modifications to the Window registry that might resolve the problem.


A hardware driveror system service requested data that was not in memory, causing an exception error.
The cause may be defective physical memory or incompatible software, especially remote control and antivirus programs. If the error occurs immediately after installing a device driver or application, try to use Safe Mode to remove the driver or uninstall the program.


The system attempted to read kernal data from virtual memory (the page file) and failed to find the data at the specified memory address. This STOP error can be caused by a variety of problems, including defective memory, a malfunctioning hard disk, an improperly configured disk controller or cable, corrupted data, or virus infection.

STOPx 0x00000079 or MISMATCHED_HAL

No this message has nothing to do with Hal, the paranoid computer in the classic film 2001: A Space Odyssey. Instead this message identifies a mismatch between the Windows XP hardware abstraction layer (HAL) and the Windows XP system files. This error most often occurs on ACPI machines, when ACPI BIOS settings are changed unexpectedly. To disable or reenable ACPI features, reinstall Windows XP after making changes in the BIOS. For more details, read Knowledge Base article 237556, " How to Troubleshoot Windows 2000 Hardware Abstraction Layer Issues" (


This STOP error has the same underlying cause as 0x77 errors: A page of kernal data was not found in virtual memory (the page file). This might be due to incompatible disk or controller drivers or hardware problems, such as an improperly terminated SCSI device, bad blocks on the hard disk, or a conflict with the BIOS or other firmware on a disk controller.
Run the Windows XP Check Disk utitity. If the disk manufacturer has a more comprehensive disk utility, use it to do a thorough check of each physical hard disk on the system.


Windows XP was unable to locate the system partition or boot volume during the startup process. This problem may occur after repartitioning disks, adding new disks, or upgrading a disk controller and its drivers. In that case, entries in the Boot.ini file no longer point to the correct partitions. If the error occurs after upgrading the disk controller, verify that the new hardware is cofigured properly. Then start your system with the Windows XP CD, log onto the Recovery Console, and use the Bootcfg command to scan for available Windows installations and repair the Boot.ini file automatically.


Hardware failure is the most common cause of this error. You are most likely to see this STOP error if you have defective memory chips, mismatched memory modules, a malfunctioning CPU, or a failure in your fan or power-supply that causes overheating. This error is especially likely to occur on systems where the CPU has been tweaked to run past its rated speed, a process known as "overclocking." The first parameter immediately after this STOP error number identifies the specific cause of the error, as explained in Knowledge Base article 137539, "General Causes of STOP 0x0000007F Errors."


A driveris currently in an inconsistent or invalid power state after shutting down, suspending to Standby or Hibernate mode, or resumming from either of those modes. This error is not limited to hardware drivers. It can also be caused by file-system filter drivers, such as those installed by antivirus programs, backup utilities and remote control programs. The name of the offending driver file often appears in the STOP error. As a troubleshooting technique, try uninstalling unsigned hardware drivers or software that uses the named driver. Knowledge Base article 266169, "How to Troubleshoot Problems with Standby Mode, Hibernate Mode, and Shutting Down Your Computer in Windows 2000," (, provides additional suggestions for resolving this type of error.


A kernal-mode process or driver attempted to perform an illegal memory allocation. The problem can often be traced to a bug in a driver or software, It is also occasionally caused by a failure in a hardware device.
You can find detailed debugging instructions for this error in Knowledge Base article 265879, "How to Debug 'Stop 0xC2' or 'Stop 0x000000C2' Error Messages."


This is one of the most common STOP errors. The error typically occurs when a driver tries to access an improper memory address. Check for unsigned drivers, and be especially suspicious of recently installed or updated antivirus programs, disk utilities and backup programs, which may install a faulty file-system filter driver.


If a poorly written driver causes your computer to request large amounts of kernal memory, you may run out of page table entries (PTEs) and see this error message. The underlying cause of the error and troubleshooting suggestions are identical to those found in the STOP 0x3F message.


You may see this error message after you install a new video adapter or an updated (and poorly written) video driver that causes the system to pause indefinitely while waiting for the video hardware. To resolve the problem, replace the video adapter or a different video driver.


Windows XP was unable to gain access to the volume containing boot files.
If you see this STOP message while attempting to upgrade a system to Windows XP, verify that you have compatible drivers for the disk controller and check the drive cabling to make sure it is configured properly. If you're using ATA-66 or ATA-100 drivers, make sure you have an 80-connector cable, not a standard 40-connector IDE cable. See the troubleshooting suggestions for STOP 0x7B errors as well. In some cases, this error will spontaneously correct itself after you restasrt your system.


This hardware-related STOP error can be extremely frustrating to experience and even more vexing to troubleshoot. The Windows XP kernal detects an interrupt storm when a device fails to release an interrupt request (IRQ). This failure is usually caused by a poorly written device driver or a bug in firmware. To isolate the problem, try to determine which device is associated with the file name listed in the driver information section of the STOP message. Then use Device Manager or System Information tool to identify other devices using the same IRQ, as described in " Viewing and Changing Resource Assignments,"

Viewing and Changing Resource Assignments

If you've worked with MS-DOS and early versions of Windows, you've probably struggled with device conflicts, most often when two or more pieces of hardware lay claim to the same IRQ. On modern computers with an ACPI BIOS and Windows XP, those sorts of conflicts are mercifuuly rare. In the original design of the IBM Personnal Computer, IRQs were in short supply, with a total of 15 available, many of those reserved by system devices, such as communications ports, keyboards, and disk controllers. With older Windows versions, problems could occur when adding a new device such as a sound card or network adapter. If the new device was hardwired to a specific IRQ that was already in use, or if there wereno free IRQs, the device simply would not work.

Remove all the devices identified as using that IRQ and add them back, one at a time, until the problem recurs.


This message indicates a serious security problem with Windows XP -a user-mode sub-system, such as Winlogon or Client Server Runtime Subsystem (Csrss.exe), is compromised. The most common cause of this program is a third-party program, and the solution is usually to remove that program. This error can also occur if a backup set has been partially restored, causing a mismatch in system files, or if system permissions have been incorrectly modified so that the System account no longer has permission to access system files and folders.


File or disk corruption problems (including a damaged page file) and faulty hardware are the most common causes of this type of STOP error. The message usually includes the name of the damaged file at the end of the symbolic error name or on a line by itself; you might be able to restore the file from the Windows XP CD using Recovery Console. Restoring the Last Known Good Configuration might also help to resolve this problem.

Taken from Microsoft Second Edition. Microsoft Windows XP INSIDE OUT

written by Ed Bott Award-winning computer journalist.

Carl Siechert, Windows documentation expert

Craig Stinson, Contributing Editor, PC Magazine.
Last edited by thedon57 on Wed Nov 09, 2005 9:11 am, edited 1 time in total.