Sometimes XP crashes and displays one of these famous BSOD, The Blue Screen Of Death (blue screen of death)

who are in fact the "Stop errors." Here is a description and meaning of stop errors that are encountered at the blue screen. Stop 0 0000000A or 0 * 0000000A or IRQL_NOT_LESS_OR_EQUAL A process or device attempting to access a memory address without permission. This error is typically caused by software or hardware incompatibility. The device name appears often in the message, which is a great help to correct this error. If so, try removing the device. If the message appears during boot, you can suspect an incompatible device, service system, a virus scanner or backup operation. Stop 0 0000001E or 0 * 0000001E or KMODE_EXCEPTION_NOT_HANDLED The Windows kernel has detected an illegal instruction process or unknown, a common result of invalid memory access caused by a driver or a device installed incorrectly. The message often identifies the device in question. If this error appears immediately after the installation of a device, try to disable or remove this device. Stop 0 00000024 or 0 * 00000024 or NTFS_FILE_SYSTEM This message indicates a problem with the NTFS driver. A similar message exists for FAT32: 0 00000023. The most common cause is a hard drive or controller curtain. Check all physical connections to all hard drives, and run the utility Chkdsk.exe. Stop 0 0000002E or 0 * 0000002E or DATA_BUS_ERROR The most common cause of this error is a defective RAM (including video memory). This error may also be due to a damaged hard drive or a defective motherboard. Stop 0 0000003F or 0 * 0000003F or NO_MORE_SYSTEM_PTES This error message may occur fairly often when the system uses the table entries page (PTE Page Table Entries). The cause may be a backup or a wild buggy driver. It is sometimes possible to resolve the problem by modifying the registry, see article Q256004 in the Microsoft Knowledge Base (KB Knowledge Base) Microsoft. Stop 0 00000050 or 0 * 00000050 or PAGE_FAULT_IN_NONPAGED_AREA A device driver or system service requested data missing from memory. The cause may be either a faulty memory or incompatible software, especially anti-virus or a remote control. If this problem appears immediately after the installation of a device or application, try to launch the Safe Mode and delete the driver or uninstall the application. Stop 0 00000077 or 0 * 00000077 or KERNEL_STACK_INPAGE_ERROR

The system tried to read data in kernel virtual memory (pagefile) and did not find the specified address. This error can have several causes, including a faulty memory, a malfunctioning disk drive, controller or a misconfigured cable, corrupted data or a virus. Stop 0 00000079 or 0 * 00000079 or MISMATCHED_HAL This error identifies a disagreement between the hardware abstraction layer from Windows XP (HAL, Hardware Abstraction Layer) and the file system of XP. This error occurs most often on ACPI computers when configuring ACPI BIOS that has changed unexpectedly. To deactivate and reactivate the ACPI functions, reinstall Windows after the change in the Bios. For more details, see article Q237556 in the Microsoft Knowledge Base (KB Knowledge Base) Microsoft. Stop 0 0000007a or 0 * 0000007a or KERNEL_DATA_INPAGE_ERROR This error is due to the same cause as the 0 0000007a: a page of kernel data that was not found in the virtual memory (pagefile). This could be due to a hard disk (or driver) conflicts or hardware problems such as lack of closure on a SCSI chain, bad sectors on a hard drive, or conflict with the bios or a third party disk controller. Chkdsk.exe launch, and if the manufacturer of disk tools disk maintenance, launch them to control the physical hard drives. Stop 0 0000007b or 0 * 0000007b or INACCESSIBLE_BOOT_DEVICE This error means that Windows XP is unable to locate the system partition or boot volume during the launching session. This problem can happen after repartitioning a disk, add a disk or an upgrade disk controller. In this case, the boot.ini file entries no longer point at the correct partitions. If the error occurs after updating the drive controller, verify that the new hardware is configured correctly. Then start the system from the Windows XP CD, enter the Recovery Console(1), then use the command Bootcfg.exe, search for Windows installations that present aisnsi automatically repair the boot.ini file. Stop 0 0000007F or 0 * 0000007F or UNEXPECTED_KERNEL_MODE_TRAP The most common cause: hardware problem. When this message appears, there is probably a faulty memory card, a memory module missing, a malfunctioning CPU, or a power problem or fan causing overheating. This error occurs especially when the processor has accelerated beyond its default speed (overclocking). The parameter immediately following the error code stop is explained in article Q137539 in the Microsoft Knowledge Base (KB Knowledge Base) Microsoft. Stop 0 0000009F or 0 * 0000009F or DRIVER_POWER_STATE_FAILURE The power of a driver is in an unstable state, after a shutdown or standby (single or deep). This error is not limited to device drivers. It may also occur due to a driver filter system file, for example an anti-virus. The name of this driver often appears in the Stop message. To solve the problem, try uninstalling the product (device or software) that uses the driver in question. For more ideas, see article Q266169 in the Knowledge Base (KB Knowledge Base)

Microsoft. Stop 0 000000C2 or 0 * 000000C2 or BAD_POOL_CALLER This error occurs when a process or a kernel mode driver attempts to use an illegal memory address. It is often due to a bug in driver or software. It may sometimes occur due to a hardware problem. Article Q265879 in the Microsoft Knowledge Base (KB Knowledge Base) Microsoft gives way to overcome this error. Stop 0 000000d1or 0 * 000000d1 or DRIVER_IRQL_NOT_LESS_OR_EQUAL This error is most common. It occurs when a driver tries to access a memory address is nonexistent. To remedy this, check the recent installations of hardware, driver, and the latest antivirus and disk utilities and backup. Stop 0 000000D8 or 0 * 000000D8 or DRIVER_USED_EXCESSIVE_PTES If a poorly written driver requires too much memory "kernel" (protected memory), we can see this message due to "out of PTE (Page Table Entries). To remedy this problem, see the error 0 0000003F in this article. Stop 0 000000EA or 0 * 000000EA or THREAD_STUCK_IN_DEVICE_DRIVER This error appears after installing a new graphics card or updating a graphics card driver that is badly written. Replace the graphics card or install another card driver should resolve the problem. Stop 0 000000ED or 0 * 000000ED or UNMOUNTABLE_BOOT_VOLUME It was impossible to access the boot device. If this message appears when updating a system to Windows XP, check the compatibility of disk drivers. Otherwise, check that the cable discs are good and properly connected. If ATA66 or ATA100 drivers are used, ensure that cables have many connectors 80 (not 40). For the rest, see the error 0 0000007b. In some cases, a simple reboot (restart) will suffice. Stop 0 000000F2 or 0 * 000000F2 or HARDWARE_INTERRUPT_STORM The core (kernel) of Windows XP has detected a storm IRQ, because a device that has failed to reset the IRQ assigned to him. This error is obviously due to a badly written driver or a bug in the "firmware" (internal to the device). Difficult to find fault, although the file name is displayed, because it must find what device driver uses this file. Once done, you must go into the Device Manager to see what other device is associated. It is best then to remove all devices connected to the IRQ, then place them one by one (restarting each time ...) until the fault is detected. Stop 0xC000021A or 0 * C000021A or STATUS_SYSTEM_PROCESS_TERMINATED Be careful, this error indicates a serious security flaw. A subsystem user as Winlogon (winlogon.exe in the process) or the Client Server Runtime Subsystem (csrss.exe) is compromised. The most common cause is a badly written third-party program, it must then uninstall the program. This error can also occur after the partial restoration of a backup, causing a malfunction in the system files. Finally, improper modifications permits have been deleted in the user account permissions required to access system files and directories.

Stop 0xC0000221 or 0 * C0000221 or STATUS_IMAGE_CHECKSUM_MISMATCH Possible causes: problems of file corruption or disk (including the virtual memory file, pagefile) or hardware defficient. In general, we find the name of wrongdoing in the statement of "stop message". The solution is to restore the file using the Recovery Console(1). Another way is to reboot by pressing the F8 key, then select "Restart with last known good configuration". __________________