Below are the list of BSOD Error messages with details. For more detailed information and solution search on
BSODS ERROR MESSAGES
1.
STOP: 0×0000000A IRQL_NOT_LESS_OR_EQUAL
This Stop error, which can be caused by either software or hardware, indicates that a kernel-mode process or driver attempted to access a memory location it did not have permission to access or a memory location that exists at a kernel interrupt request level (IRQL) that was too high. A kernel-mode process can access other only processes that have an IRQL that’s equal to or lower than its own.
Problem with Hardware on the PC
Check Event Log
Check YOUR RAM
Remove and check any of the following devices
* SCSI devices
* IDE devices
* Network adapter
* Internal modem
* Sound card
* Extra hard disks (you have to have at least one to complete the installation)
* CD drive or DVD drive (if you are installing from the local hard disk)
# Upgrade the computer BIOS if that is applicable.
Repair Windows
Reinstall windows
For More Info ..
http://support.microsoft.com/?kbid=314063
2.
STOP: 0×0000001E - KMODE_EXCEPTION_NOT_HANDLED
This Stop error indicates that indicates that the Windows XP kernel detected an illegal or unknown processor instruction. The problems that cause this Stop error can be either software or hardware related and result from invalid memory and access violations, which are intercepted by Windows’ default error handler if error-handling routines are not present in the code itself.
* Hardware failure (memory, processor, or motherboard).
* Anti-virus software that is running on your computer.
* Drivers installed by third-party software.
Disable any antiviurs running on your computer
STOP: 0×0000000a
STOP: 0×0000001e
STOP: 0×00000050
4.
STOP: 0×00000050 - PAGE_FAULT_IN_NONPAGED_AREA
This Stop error indicates that requested data was not in memory. The system generates an exception error when using a reference to an invalid system memory address. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause this Stop error.
STOP: 0×0000000a
STOP: 0×0000001e
STOP: 0×00000050
Same as above
5.
STOP: 0×0000007B - INACCESSIBLE_BOOT_DEVICE
This Stop error indicates that Windows XP has lost access to the system partition or boot volume during the startup process. Installing incorrect device drivers when installing or upgrading storage adapter hardware typically causes this Stop error. This error could also indicate a possible virus infection.
Troubleshooting Stop 0×0000007B or “0×4,0,0,0″ Error
Boot Sector Viruses
STOP: 0×0000007B (parameter1, parameter2, parameter3, parameter4)
INACCESSIBLE_BOOT_DEVICE
Setup has encountered a fatal error that prevents it from continuing.
Use the Last Known Good Configuration feature.
Use the Repair option with Windows XP Setup. F
Restore a registry backup or System restore
6.
STOP: 0×0000007F - UNEXPECTED_KERNEL_MODE_TRAP
This Stop error indicates a hardware problem resulting from mismatched memory, defective memory, a malfunctioning CPU, or a fan failure that’s causing overheating.
General causes of “STOP 0×0000007F” errors
Your computer has hardware or software problems (hardware failure is the most common cause).
Check RAM
To determine an approximate cause, examine the parameters at the top of the STOP screen:
**STOP 0×0000007F (0×000000XX, 0×00000000, 0×00000000, 0×00000000)
UNEXPECTED_KERNEL_MODE_TRAP
7.
STOP: 0×0000009F DRIVER_POWER_STATE_FAILURE
This Stop error indicates that a driver is in an inconsistent or invalid power state. This Stop error typically occurs during events that involve power state transitions, such as shutting down, or moving in or out of standby or hibernate mode.
* Shutting down
* Suspending or resuming from Standby mode
* Suspending or resuming from hibernation
Check Devise manager for Any driver conflict
Roll Back Windows
8.
STOP: 0×000000D DRIVER_IRQL_NOT_LESS_OR_EQUAL
This Stop error indicates that the system attempted to access pageable memory using a kernel process IRQL that was too high. The most typical cause is a bad device driver (one that uses improper addresses). It can also be caused by faulty or mismatched RAM or a damaged pagefile.
Error Message with RAM Problems or Damaged Virtual Memory Manager
System has recovered from a serious error
DRIVER_IRQL_NOT_LESS_OR_EQUAL
Check RAM
# If you change your RAM, test to determine if the issue is resolved. If the issue is resolved, do not complete the remaining steps. If the issue is not resolved, go to step 2.
# Click Start, right-click My Computer, and then click Properties.
# Click the Advanced tab.
# Under Performance, click Settings.
# Click the Advanced tab.
# Under Virtual Memory, click Change.
# Click No paging file. Click OK, click OK, and then click OK.
# Restart your computer.
# Click Start, right-click My Computer, and then click Properties.
# Click the Advanced tab.
# Under Performance, click Settings.
# Click the Advanced tab.
# Under Virtual Memory, click Change.
# Click System managed sized. Click OK, click OK, and then click OK.
# Restart your computer.
9.
STOP: 0×000000EA - THREAD_STUCK_IN_DEVICE_DRIVER
This Stop error indicates that a device driver problem is causing the system to pause indefinitely. Typically, this problem is caused by a display driver waiting for the video hardware to enter an idle state. This might indicate a hardware problem with the video adapter or a faulty video driver.
Error message: STOP 0×000000EA THREAD_STUCK_IN_DEVICE_DRIVER
This issue occurs if the graphics adapter is caught in an infinite loop while it waits for the video hardware to become idle. This can indicate that there is a problem with the video hardware, or that the graphics adapter cannot program the hardware correctly.
Method 2: Install the latest driver for your video adapter
To detect and to install the latest driver for your video adapter in Windows XP, visit the following Microsoft Web site:
http://windowsupdate.microsoft.com
Method 4: Replace your video card
Method 2: Adjust the Hardware Acceleration
1. Click Start, click Control Panel, and then double-click Display.
2. On the Settings tab, click Advanced, and then click the Troubleshoot tab.
3. Move the Hardware Acceleration slider to None, and then click to clear the Enable write combining check box.
4. Click OK, and then click OK.
10.
STOP: 0×00000024 - NTFS_FILE_SYSTEM
This Stop error indicates that a problem occurred within Ntfs.sys, the driver file that allows the system to read and write to drives formatted with the NTFS file system. (A similar Stop message, 0×00000023, exists for the file allocation table [FAT16 or FAT32)] file systems.)
Troubleshooting Stop 0×24 or NTFS_FILE_SYSTEM Error Messages
This issue can occur if a problem occurred within the Ntfs.sys file. The Ntfs.sys file is the driver file that enables your computer to read and write to NTFS partitions. Damage in the NTFS file system, damaged portions of your hard disk, or damaged SCSI or IDE drivers can also cause this issue.
# Try disabling any virus scanning programs, backup programs, or disk defragmenter tools that constantly monitor your computer, and if possible, run hardware diagnostics tools supplied by your computer manufacturer.
# Run chkdsk /r to detect and resolve any file system structural damage.
FAT or FAT32 File System
If your system partition is using the FAT or FAT32 file system, disconnect or turn off any data disks that contain NTFS volumes. This allows you to start back into the operating system to perform troubleshooting steps. If you can determine which NTFS volume is causing the boot problem, use the following steps:
1. Make sure the drive that contains the corrupted NTFS volume is disconnected, and then start Windows by using Safe mode.
2. Rename the %SystemRoot%\System32\Drivers\Ntfs.sys file to Ntfs.old, and then shut down the computer (this action prevents the Ntfs.sys driver from loading).
3. Reconnect the drive that contains the corrupted NTFS volume.
4. Restart the computer, and then run the following command on the corrupted NTFS volume:
chkdsk driveletter: /f
NOTE: The Chkdsk tool has built-in support for NTFS and does not require the Ntfs.sys driver to make repairs.
5. After you use the Chkdsk tool to repair the corrupted NTFS volume, rename %SystemRoot%\System32\Drivers\Ntfs.old to Ntfs.sys, and then shut down and restart the computer.
The computer should be operational again, and you can try to determine what caused the original problem.
11.
STOP: 0xC0000218 - UNKNOWN_HARD_ERROR
This Stop error indicates that a necessary registry hive file could not be loaded. The file may be corrupt or missing. The registry file may have been corrupted due to hard disk corruption or some other hardware problem. A driver may have corrupted the registry data while loading into memory or the memory where the registry is loading may have a parity error.
How to Troubleshoot a Stop 0xC0000218 Error Message
Stop: 0xc0000218 {Registry File Failure}
The registry cannot load the hive (file):
\SystemRoot\System32\Config\SYSTEM or its log or alternate.
It is corrupt, absent, or not writable.
A Stop 0xc0000218 error message means that a necessary registry hive file could not be loaded. This error message can occur if the file is corrupt or missing. To resolve this issue, you can reinstall the operating system and restore the registry files from a backup. The registry files may have been corrupted because of hard disk corruption or some other hardware problem.
This error message can also occur if the driver has corrupted the registry data while loading into memory, or the memory where the registry is loading has a parity error. In the latter case, turn off the external cache and check the memory chips.
# Start your computer by running the Recovery Console, run the chkdsk /p command on the drive, and then restart your computer. Test to determine whether the issue is resolved. If the issue is resolved, do not complete the remaining steps. If the issue is not resolved, go to step 2.
# When Windows loads, press SPACE BAR when the “Load Last Known Good” message appears.
12.
STOP: 0xC0000221 - STATUS_IMAGE_CHECKSUM_MISMATCH
This Stop message indicates driver, system file, or disk corruption problems (such as a damaged paging file). Faulty memory hardware can also cause this Stop message to appear.
“STOP: C0000221 unknown hard error” or “STOP: C0000221 STATUS_IMAGE_CHECKSUM_MISMATCH” error message occurs
STOP: 0xC0000221 unknown hard error
C:\Winnt\System32\Ntdll.dll (or another specific file or driver)
STOP: 0xC0000221 STATUS_IMAGE_CHECKSUM_MISMATCH
Path\File_name
Reinstall or Repair windows Xp
* All driver files (except those that are loaded by the system loader to start. the computer)
* All dynamic-link libraries (DLLs), including User, Graphics Device Interface (GDI), Shell, Kernel, Ntdll, Crtdll, and others.
