Warning: The steps contained in this article may involve changing the basic input/output system (BIOS) or complementary metal oxide semiconductor (CMOS) settings, or may require physical changes to the computer hardware. Incorrectly changing the computer's BIOS may cause serious problems. Microsoft cannot guarantee that it can solve the problems caused by changing the BIOS. Changing the BIOS settings is at your own risk. If you need help with these steps, please contact the hardware manufacturer. Please note that changes to the computer hardware or BIOS may invalidate your warranty. If you don't want to replace the computer hardware, you can send the computer to the maintenance center.

symptom

When running Windows XP, you may receive the following error message:

Stop 0x00000077

Kernel stack page error

This article introduces how to troubleshoot these error messages.

cause

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:

Page table entry (PTE) 0 (zero) value 0 (zero) address 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 use the information listed below from the second parameter (I/O

Status code) to determine the cause of the problem. This information is listed in the format of "Second Parameter Value" followed by "Common Causes":

0xC000009A or

Status _ assurance _ 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, there are no terminals or the controller cannot access the hard disk.

0xC0000 16A or

STATUS_DISK_OPERATION_FAILED: There are bad 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.

solution

To solve this problem, please use the following appropriate methods: There is a virus in the boot sector. To determine whether the boot sector is infected with virus, please run the latest virus checker and clean the computer virus if necessary. There is no virus in the boot sector.

Check the system log in Event Viewer for other error information to help determine the device that caused this error.

Incorrect word group. "Stop0x77" error may be caused by wrong block in paging file or disk controller error; This error can also be caused when non-paged buffer pool resources are unavailable, but this is very rare.

If both the first and second parameters are 0, the stack signature cannot be found in the kernel stack. Damaged hardware can cause this problem. If the I/O status is C0000 185 and the paging file is located on a SCSI-based hard disk, you should check the disk cable and SCSI terminal.

If the I/O status code is 0xC000009C or 0xC0000 16A, it usually means that the data cannot be read from the disk due to the wrong block.

If this error message appears, you can restart your computer, and Autochk will automatically run and try to separate the bad sectors. If for some reason Autochk doesn't scan the hard disk for errors, please start ScanDisk manually. If the computer is formatted with NTFS file system, please run Chkdsk /f/r on the system partition. You must restart your computer before starting ScanDisk. If you can't start the computer because of this problem, please use the command console and run Chkdsk /r r r.

Damaged or unreliable random access memory (RAM) is another common cause of this problem.

Please check that all adapter cards in the computer are inserted correctly.

Ensure that all contacts of the adapter card are clean.

Disable the system cache in the BIOS to see if it can solve the problem.

If this does not solve the problem, your computer motherboard may have been damaged.

The above is the official answer to this question provided by Microsoft.

To put it simply, you should check whether there is anything wrong with your hardware, especially your memory, and then check whether your boot partition has viruses. If all the above have been tried, enter the PE system and use the command prompt (Start → Run → "cmd").

Type chkdsk c:/f/r "c "and your system drive letter. Choose to run the check after the next restart, or you can check all other partitions by the way.

However, I suggest you try to enter safe mode first. If there are any problems in the system, most of them can be solved by entering the safe mode.