Blue Screen and How to Fix Them?

Before explain more, At Wikipedia , The Blue Screen Of Death (also known as BSoD or bluescreen or " Blue Screen of Doom "), kno...

Before explain more, At Wikipedia, The Blue Screen Of Death (also known as BSoD or bluescreen or "Blue Screen of Doom"), known officially as a Stop Error [1] or a bug check is the error screen displayed by the Microsoft Windows family of operating systems upon encountering a critical error, of a non-recoverable nature, that causes the system to "crash." The term is named after the color of the screen generated by the error. Many people who is using Windows Operating System has ever experienced the BSoD. So, to fixed that problem, I found many ways to fixed it's when searching in Google.


Stop 0x0000000A or IRQL_NOT_LESS_OR_EQUAL

Indicate a kernel-mode process or driver tried to access a memory location without permission. Stop error is usually caused by damage, or hardware / software that are not compatible.

Name of device drivers that are offered usually appear on the message or stop and can give important clues to solve the problem. If the error message invites us to use the devices or specific device categories, try to remove or replace the device in that category.

If the messages stop appearing at Startup, then the cause is most likely that there are no compatible devices, system service, virus scanner, or other backup programs.

STOP 0x0000001E or KMODE_EXCEPTOIN_NOT_HANDLED

In this case, the Windows XP kernel detected a processor instruction illegal or unknown due to failure to access the device driver or hardware. This message is also often offer the device or driver is needed.

If the error appears suddenly after installing a driver or service, try disabling or disposed of only a driver or service.

STOP 0x00000024 or NTFS_FILE_SYSTEM

This message is caused by problem drivers NTFS file system. Stop message type, 0x23, derived from FAT32 drivers. The most likely cause of failure in a disk or disk controller.

Possible solution is to check the connections to all hard drives in the system, and run Check Disk (chkdsk.exe). Press the Windows key + R, then type "chkdsk.exe" (without quotation marks).

STOP 0x0000002E or DATA_BUS_ERROR

Failure or lack of memory (including memory-adapter video adapter). This error might also caused by a corrupted or damaged motherboard.

STOP 0x0000003F or NO_MORE_SYSTEM_PTES

Error messages like this are rare, occurs when excess system PTEs (Page Table Entries). This is due, backup program or device out of control.

STOP 0x00000050 or PAGE_FAULT_IN_NONPAGED_AREA

Hard disk driver or system service requested data that does not exist in memory or incompatible software, especially for remote control and antivirus programs. If the error appears after installing a device driver or an application, try to get into Safe Mode to delete drivers or uninstall the program.

STOP 0x00000077 or KERNEL_STACK_INPAGE_ERROR

The system reads data from the kernel virtual memory (pagefile) and failed to find data on the memory address. However, this STOP error can also be caused various problems, including lack of memory, hard disk malfunctions, installation disk controller or cable that is incorrect, corrupted data, or it could be being infected with the virus.

STOP 0x00000079 or MISMATCHED_HAL

This message appears because of the discovery of mismatch between Windows XP Hardware Abstraction Layer (HAL) and system files of Windows XP. It usually occurs on ACPI machines, where the ACPI BIOS settings change unexpectedly.

To disable or re-enable ACPI features, re-install Windows XP after you make changes to the BIOS.

STOP 0x0000007A or KERNEL_DATA_INPAGE_ERROR

The cause of this error as the same STOP error 0x77-error: a page of kernel data was not found in the virtual memory (pagefile).

The cause may be disk or controller drivers are not compatible. It can also be derived from hardware problems, such as SCSI devices are not properly disconnected, the occurrence of bad blocks on the hard disk, or it conflicts with a BIOS or firmware on the disk controller. Try running Check Disk (chkdsk.exe)