Fix Stop 0x00000077 or KERNEL STACK INPAGE ERROR

The following error message may be displayed on your Windows computer:

Stop 0x00000077



Cause of the Error

This error, also known as the Stop 0x77 error, is displayed when either:

  • The master boot record (MBR) of your system is infected with a boot sector virus, or
  • Paging file is unable to read a requested kernel data into memory.

To find the cause of the error it is essential to further interpret the error message. If, in the error code, both first and third parameters are zero, then the four parameters are defined in the following way:

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

In case either, the first or third parameter is not zero then the following will apply:

1 – Status code
2 – Status code of I/O
3 – Number of Page File
4 – Offset into Page File

In this case, the cause of the problem is determined by the second parameter that depicts the I/O status code. The following information listed in the value of the second parameter helps you determine the general cause of the error message:

0xC000000E (STATUS_NO_SUCH_DEVICE): The required drive is unavailable, indicating either one or all of the following are bad:

  • Hard drive
  • Disk controller
  • Disk array

0xC000009A (STATUS_INSUFFICIENT_RESOURCES): Non-paged resources are not available.

0xC000009C (STATUS_DEVICE_DATA_ERROR): There are bad blocks on the hard disk.

0xC000009D (STATUS_DEVICE_NOT_CONNECTED): Cable is bad or is not terminated, or the controller is unable to gain access to the hard disk.

0xC000016A (STATUS_DISK_OPERATION_FAILED): There are bad blocks on the hard disk.

0xC0000185 (STATUS_IO_DEVICE_ERROR): SCSI-based devices are not terminated properly or the cable is defective. Or, two devices are trying to gain access to the same IRQ.

Resolution Methods

You can use the following methods to resolve these errors.

Method 1: Scan and Remove Boot Sector Virus

To scan the MBR of your system, use a reliable Antivirus tool, such as STOPzilla Antivirus and scan the boot sector of your system. If there is an infection in the boot sector, your antivirus tool should clean it and resolve the problem.

Method 2:

If the error is not caused due to a boot sector virus, perform the following tasks.

First, open the Event Viewer on your Windows computer and then in the System log look for additional error messages that may help you determine the device that is causing the error.

If the first and second parameters are zero (0), it indicates that the stack signature could not be located in the kernel stack. This problem occurs due defective hardware.

Now, if the I/O status is C0000185 and the paging file exists on a SCSI hard disk, you must ensure that there is no problem with SCSI termination and cabling.

In case the I/O status code is 0xC000009C or 0xC000016A, it usually indicates that there are bad blocks on the disk due to which data could not be read. In this case, when you reboot your Windows PC, the Autochk must run automatically on the system to determine and mark the bad sector. In case the tool does not run automatically, you must manually run it to determine the bad sector(s) on the disk. In case you have NTFS partition on your hard disk, run the Chkdsk /f /r on the system partition. Also, you must reboot the system before the scanning process starts. If you are unable to start the PC, use the Command Prompt of your Windows computer to run the Chkdsk /r command.

Some of the other tasks that you can perform to repair the error are:

  • Ensure that RAM or memory of your computer is not defective.
  • Ensure that all adaptors are properly seated in their slots.
  • Ensure that the connectors of all adaptors connected to your system are clean.
  • Disable system caching from BIOS to see if doing this resolves the issue.
  • Check your motherboard for faults.