access database repair center
microsoft access repair
HomeRecovery ReportTypical SymptomsFAQTestimonialsContact

Q228753 Troubleshooting 'Stop 0x00000077' or 'KERNEL_STACK_INPAGE_ERROR'.

Symptoms

Whilst running Windows you get either of the following errors:

”Stop 0x00000077”

“KERNEL_STACK_INPAGE_ERROR “

Cause

These errors emerge if the master boot record is infected with a virus, or, a requested page with kernel data can’t be read. Understanding the cause of this error requires analysis of the error message itself:

If the first and third parameters are ‘0’, then the four parameters are defined as:

1. 0
2. Page Table Entry (PTE) value at time of error
3. 0
4. Address of kernel stack signature

If first or the third parameters are not ‘0’ then the following applies:

1. Status code
2. I/O status code
3. Page file number
4. Offset into page file

If the above applies, then the cause can be tracked by looking at the second parameter, the I/O status code, using the following information listed in a "value of second parameter" followed with "general cause" format:

0xC000000E, or STATUS_NO_SUCH_DEVICE: the drive became unavailable, hard drive is bad, disk array, and/or controller card.

0xC000009A, or STATUS_INSUFFICIENT_RESOURCES: lack of non-paged pool resources.

0xC000009C, or STATUS_DEVICE_DATA_ERROR: there are 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.

Resolution

To resolve this problem, you will need to use one of the methods listed above.

 
Home | Links | Blog | Sitemap | Privacy Policy