When you are running Windows, you may receive one of the following error messages:
This article describes how to troubleshoot these error messages.
This issue can occur if a requested page of kernel data could not be read from the paging file into memory, or the master boot record is infected with a virus. To further determine the possible cause, you must properly interpret the error message. If both the first and third parameters are zero, then the four parameters are defined as:
- 0 (zero)
- Page Table Entry (PTE) value at time of error
- 0 (zero)
- Address of signature on kernel stack
If either the first or the third parameter is not a zero, then the following definitions apply:
- Status code
- I/O status code
- Page file number
- Offset into page file
If this is the case, the cause of this issue may be determined from the second parameter (the I/O status code) by using the following information that is listed in a "value of second parameter" followed by "general cause" format:
0xC000000E, or STATUS_NO_SUCH_DEVICE: the drive went unavailable, possibly a bad hard drive, disk array, and/or controller card.
0xC000009A, or STATUS_INSUFFICIENT_RESOURCES: lack of nonpaged
0xC000009C, or STATUS_DEVICE_DATA_ERROR: bad blocks on the hard disk.
0xC000009D, or STATUS_DEVICE_NOT_CONNECTED: bad cabling, non-termination, or the controller is not able to obtain access to the hard disk.
0xC000016A, or STATUS_DISK_OPERATION_FAILED: bad blocks on the hard disk.
0xC0000185, or STATUS_IO_DEVICE_ERROR: improper termination or defective cabling of SCSI-based devices, or two devices attempting to use the same IRQ.
To resolve this issue, use the appropriate method:
Boot sector virus
To determine if you have a boot sector virus, run a current virus-checking program, and if needed, disinfect your computer.
Not a boot sector virus
View the System Log in Event Viewer for additional error messages that help you determine the device that is causing the error.
Bad block. Stop 0x77 is caused by a bad block in a paging file, or a disk controller error, or in extremely rare cases it is caused when non-paged pool resources are unavailable.
If the first and second parameters are 0, then the stack signature was not found in the kernel stack. The cause of this issue is defective hardware. If the I/O status is C0000185 and the paging file is on a SCSI-based hard disk, you should verify the disk cabling and SCSI termination.
If the I/O status code is 0xC000009C or 0xC000016A, this normally indicates that the data could not be read from the disk due to a bad block.
If you can restart your computer after the error message, Autochk runs automatically and tries to map out the bad sector. If for some reason Autochk does not scan the hard disk for errors, manually start the disk scanner. If your computer is formatted with the NTFS file system, run Chkdsk /f /r on the system partition. You must restart your computer before the disk scan begins. If you cannot start your computer due to this issue, use the Command Console and run Chkdsk /r.
Defective or unreliable random access memory (RAM) is another common cause of this issue.
Verify that all the adapter cards in your computer are properly seated.
Ensure that all adapter card contacts are clean.
Disable system caching in the BIOS to see if this resolves the error.
If this does not resolve the issue, your computer mainboard may be damaged.