BSOD


BSOD

BSOD Error Messages

The Blue Screen of Death is the error code created by windows on a critical system which can cause system to be unstable. It can be caused by any physical faults to Hard Disk, Ram or Display card. These errors are generated on Windows NT based operating systems when the kernel or the driver running in kernel mode.. It causes systems to crash or shutdown.

We suggest running check disk to repair windows internal driver and other files.

Below are some of the Blue Screen Error causes & Fix

 

1) BSOD ERROR: STOP: 0×0000000A | Error – IRQL_NOT_LESS_OR_EQUAL

Check Event Log.

Check your RAM.

Solution:

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 Computer BIOS if possible.
  • Repair or Reinstall Windows.

 

2) BSOD Error: STOP: 0x00000050 | PAGE_FAULT_IN_NONPAGED_AREA

This Stop Error explains that requested data was not in memory. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause this Stop error.

Solution:

  • Hardware failure (memory, processor, or motherboard).
  • Anti-virus software that is running on your computer.
  • Drivers installed by third-party software.
  • Disable any antivirus running on your computer.
  • STOP: 0x0000000a | STOP: 0x0000001e | STOP: 0x00000050
  • Solutions to recently resolved computer problems

 

3) BSOD Error – STOP: 0x0000001E | KMODE_EXCEPTION_NOT_HANDLED

This Stop error indicates that indicates that the Windows XP kernel detected an illegal or unknown processor instruction. The problem can be software or hardware related.

Solution:

  • Hardware failure (memory, processor, or motherboard).
  • Anti-virus software that is running on your computer.
  • Drivers installed by third-party software.
  • Disable any antivirus running on our computer.
  • STOP: 0x0000000a | STOP: 0x0000001e | STOP: 0x00000050.

 

4) BSOD Error – STOP: 0x0000007B | INACCESSIBLE_BOOT_DEVICE | “0X4,0,0,0” Error

Boot Sector Viruses: STOP: 0x0000007B (parameter1, parameter2, parameter3, parameter4)

Causes

This error explains that Windows XP has lost access to the system partition or Boot Volume during start up. Installing or upgrading hardware drivers proabably caused this Stop Error. Setup has encountered a fatal error that prevents it from continuing. This could also be caused by a Virus on PC.

Solution:

  • Use the Last Known Good Configuration feature.
  • Use the Repair option with Windows XP Setup.
  • Restore a registry backup or System Restore.

 

5) BSOD STOP Error: 0x0000007F | UNEXPECTED_KERNEL_MODE_TRAP

Causes:

This Stop Error shows a problem with Hardware caused by mismatched memory, a malfunctioning CPU, failure with Fan causing overheating. Computer may have hardware or a Software problem.

Solution:

  • Check Ram, Check Fan
  • Check Error Logs

 

6) BSOD Error – STOP: 0x0000009F | DRIVER_POWER_STATE_FAILURE

This error indicates a malfunction of a driver. This error generally occurs while shutting down or moving out or standby or Hibernate Mode.

While Shutting down, Suspending or resuming from Standby mode, Suspending or resuming from hibernation

Solution:

  • Check Devise Manager for any driver conflict.
  • Update drivers.
  • Roll Back Windows.

7. BSOD STOP Error: 0x000000D1 | DRIVER_IRQL_NOT_LESS_OR_EQUAL – System has recovered from a serious error

This Stop error indicates that the system attempted to access page able memory using a kernel process IRQL that was too high.

The major cause is bad devise driver or by a faulty or mismatched RAM or damaged page file.

Damaged Virtual Memory Manager or RAM problems

Solution:

  • Check RAM
  • Check Virtual RAM
  • 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.
  • Enable Page File again
  • 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, and then click OK.
  • Restart your computer.

9) BSOD Error – STOP: 0x000000EA | THREAD STUCK IN DEVICE DRIVER

Causes:

This Error is caused by a devise driver causing the system to pause indefinitely. A hardware problem with the video Adapter or a faulty video driver. This can indicate that there is a problem with the video hardware, or that the graphics adapter cannot Program the hardware correctly.

Solution:

  •  Update your Video Adapter or install the latest Drivers for Windows XP.
  • Replace your Video Card
  • Adjust the Hardware Acceleration
  • Click Start >> click Control Panel >> and then double-click Display.
  • On the Settings tab >> click Advanced >> then click the Troubleshoot tab.
  • Move the Hardware Acceleration slider to none >> and then click to clear the Enable write combining check box.
  • Click OK

 

10) BSOD Error – STOP: 0x00000024 | Stop 0x24 or NTFS_FILE_SYSTEM

Causes:

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, 0x00000023, exists for the file allocation table [FAT16 or FAT32] file systems.) 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.

Solution:

  • Run Disk Defragmenter
  • Run
  • Try disabling any virus scanning programs,
  • CHKDSK /R to detect and resolve any file system structural damage.

 

11) 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:

  • Make sure the drive that contains the corrupted NTFS volume is disconnected, and then start Windows by using Safe mode.
  • 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).
  • Reconnect the drive that contains the corrupted NTFS volume.
  • 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.

12. BSOD Error – STOP : 0xC0000218 | UNKNOWN_HARD_ERROR – Stop: 0xc0000218 (Registry File Failure)

This error is caused when a registry hive file could not be loaded. The may be missing or corrupt. It may be caused by hard disk failure or some other hardware problem.

Solution:

  • Start your computer by running the Recovery Console, run the chkdsk /p command on the drive, and then restart your computer.
  • When Windows loads, press SPACE BAR when the “Load Last Known Good” message appears.

 

13) BSOD Error – STOP: 0xC0000221 | STATUS_IMAGE_CHECKSUM_MISMATCH – unknown hard error” or “STRP:C0000221 STATUS IMAGE CHECKSUM MISMATCH”

BSOD ERROR – C:\Winnt\System32\NTDLL (or another specific file or driver)

Solution:

  • Reinstall or Repair Windows XP