This problem may occur if the requested kernel data page cannot be read into memory from the page file, or the master boot record is infected with a virus. To further determine the possible cause, you must correctly interpret the error message. If both the first and third parameters are zero, then the four parameters are defined as:

0 (zero)

The value of the page table entry (PTE) at the time of error.

0 (zero)

Address of the signature on the kernel stack

If one of the first or third parameters is not zero, the following definitions apply:

Status code

I/O status code

Page file number

Page file offset

If this is the case, you can determine the cause of the problem from the second parameter (I/O status code) using the following information, which is listed in the format of "Value of Second Parameter" followed by "Common Causes":

0xC000000E or STATUS_NO_SUCH_DEVICE: The drive is unavailable, and the hard disk, disk array and/or controller card may be damaged.

0xC000009A or status _ assured _ resources: Non-paged buffer pool is out of resources.

0xC000009C or STATUS_DEVICE_DATA_ERROR: There are incorrect blocks on the hard disk.

0xC000009D or STATUS_DEVICE_NOT_CONNECTED: The cable is damaged, and there is no terminal or the controller cannot access the hard disk.

0xC0000 16A or STATUS_DISK_OPERATION_FAILED: There are incorrect blocks on the hard disk.

0xC0000 185 or STATUS_IO_DEVICE_ERROR: The wrong terminal or cable of SCSI-based device is damaged, or two devices try to use the same IRQ.