The required data cannot be found in virtual memory or physical memory. This error is usually a memory error, bad disk block or virus erosion.

1, users are advised to check the system for viruses with the latest version of antivirus software.

2. Reinstall the correct operating system. And correctly install the driver of each device.

3. Use ScanDisk to check whether the hard disk is faulty. If yes, please send the bill. Fault part: hard disk

4. Send the order. Faulty parts: memory, motherboard

1, use the latest version of antivirus software for antivirus;

2. At the command prompt, run the "Chkdsk /f /r" command to check and repair the file error.

3. If it is not the latest system service package, please upgrade the latest system service package.

4. If the above operations are ineffective, it is recommended to repair, install or reinstall the system.

When running Windows, you may receive one of the following error messages:? 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:

1.0 (zero)

2. The value of the page table entry (PTE) when an error occurs.

3.0 (zero)

4. Address of signature on the kernel stack

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

1. status code

2. Input and output status codes

3. Page file number

4. 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.

solution

To solve this problem, please use the following appropriate methods:

Boot sector virus

To determine whether the boot sector is infected with virus, please run the latest virus checker and clean the computer virus if necessary.

Not a boot sector virus

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

Incorrect word group. "Stop 0x77" 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.