Links: Volcanoes

Tips for recovering from the 'Blue Screen of Death'
Tips for recovering from the 'Blue Screen of Death'. The STOP: 0x00000### error is the actual error The message below it, usually_strung_together_with_underscores, is the translated error. The rest of the business just tells what was running at the time, but the upper-left most driver or exe is usually the culprit or the victim. The rest of the info isn't too much use to Joe Average. 0x0000000A IRQL_NOT_LESS_OR_EQUAL An attempt was made to access pageable memory at a process internal request level (IRQL) that was too high. A process can only access objects that have priorities (IRQL) of equal or lower priority than its own. This is usually caused by a device driver using improper addresses. 0x00000019 BAD_POOL_HEADER Invalid Pool Header. There are many reasons that this would appear. Debugging the system would reveal the cause. 0x0000001E KMODE_EXCEPTION_NOT_HANDLED This is a very common bug check. Usually the exception address (the second parameter) pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. 0x00000024 NTFS_FILE_SYSTEM All file system bug checks have encoded in their first ULONG the source file and the line within the source file that generated the bug check. The high 16-bits identifies the file, while the lower 16-bits identifies the source line in the file where the bug check occurred. 0x00000051 REGISTRY_ERROR Something has gone terribly wrong with the Registry. It could indicate the Registry received an I/O error while attempting to read one of its files as a result of a hardware problem or file system corruption. 0x00000077 KERNEL_STACK_INPAGE_ERROR The requested page of kernel data could not be read in. Caused by a bad block in paging file or disk controller error. If the error is a result of a paging error, upon system restart, AUTOCHK will attempt to map out the bad block. The second parameter identifies the cause of the error: