The most important bit of information in the event description is the error code listed. Based on that, you can start troubleshooting this in the right direction.
Most of the problems leading to this event indicate faulty hardware, bugs in device drivers or incompatible hardware.
A troubleshooting approach from a newsgroup post: "Boot from CD to start the Recovery Console, then read setuplog.txt, and setupapi.log, to see what happens when it boots.
Another newsgroup posts suggests that this error requires the debugger to look at the parameters of the error. Usually this is some hardware driver failure. Running 'verifier' may identify it. Article ME244617
- How to Use Driver Verifier to Troubleshoot Device Drivers in Windows 2000 may help."
Error code 0000000a
= "IRQL_NOT_LESS_OR_EQUAL" - The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS. For additional details see the link to Error code 0x0000000a
Error code 00000020
= "KERNEL_APC_PENDING_DURING_EXIT" - May indicate a bug in a device driver. For additional details see the link to Error code 0x00000020
Error code 00000050
= "PAGE_FAULT_IN_NONPAGED_AREA" - See the link to Error code 00000050
for information about what may cause this.
Error code 0000009c
= "MACHINE_CHECK_EXCEPTION" - This indicates that a fatal machine check exception has occurred. See also ME162363
and Error code 0x0000009c
Error code 000000ce
= "DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS" - This indicates that a driver failed to cancel pending operations before unloading. If the driver responsible for the error can be identified, its name is printed on the blue screen.
Error code 000000ea
= "THREAD_STUCK_IN_DEVICE_DRIVER" - A device driver is spinning in an infinite loop, most likely waiting for hardware to become idle. This usually indicates problem with the hardware itself, or with the device driver programming the hardware incorrectly. In many cases this is the result of a bad video card or a bad display driver.
Error code 1000007f
= "UNEXPECTED_KERNEL_MODE_TRAP_M" - The first parameter displayed on the blue screen specifies the trap number. Trap number 0x00000000, or Divide by Zero Error, may indicate memory corruption. Other hardware problems, or software failures can cause this error. See EV100084
-Interpreting a Bug Check Code - for more explanations about various trap numbers.
Error code 1000008e
= "KERNEL_MODE_EXCEPTION_NOT_HANDLED_M" - Most of newsgroup comments about this error point to faulty hardware or drivers. The hardware varies from modems, video cards, USB device to memory or sound cards. Sometimes it proves to be hardware that it is not compatible with Windows XP. ME310740
gives an example of this error occuring when and old Audigy sound card driver is installed.
Error code 000000be
= "ATTEMPTED_WRITE_TO_READONLY_MEMORY" - This is issued if a driver attempts to write to a read-only memory segment. If the driver responsible for the error can be identified, its name is printed on the blue screen. A faulty device driver would typically be the cause of that. Also, potential file corruption.
Error code 100000ea
= "THREAD_STUCK_IN_DEVICE_DRIVER_M" - This indicates that a thread in a device driver is endlessly spinning. See the information for Error code 000000ea
Error code 0000007F
= "UNEXPECTED_KERNEL_MODE_TRAP" - From a newsgroup post: "According to ME104292
, there are two known causes for this error:
- corrupt system files, especially file system files
- mismatched memory or motherboard problem
This error generally occurs during boot, with no parameters specified except the first one. Suggested troubleshooting is to run repair to check for corrupt files, then low-level hardware diagnostics (including diagnosing RAM and the motherboard)." See also the link to Error code 0x0000007F
Error code 0x10000050
= Some information about this type of error can be found via the Error code 0x10000050
Error code 0x0000004e
= PFN_LIST_CORRUPT - While this error points to a corrupt memory structure, some forum posts reported this as happening when Panda Antivirus was conflicting with another antivirus program.