PC Mover Move applications, files and settings from one PC to another. Handles Windows upgrades too, even XP 32-bit to Windows 7 64-bit!
RadarSync Ensures you have the latest drivers and software updates to make your PC run better and safer.
Partition Commander Now it's easy for anyone to safely partition their hard drive! You can reclaim waste disk space, organize files, even add new OSes.
KERNEL_STACK_INPAGE_ERROR
STOP: 0x00000077
Description
Windows could not read a file from the disk. It may indicate the hard disk has bad sectors, hardware (disk, controller, memory) issues, a virus infection or a bug in a device driver.
This is a fatal Windows error, typically called a Stop message, Bug Check, or more commonly the Blue Screen of Death (BSoD). The system is in a forced reboot state. Any unsaved work is likely lost.
Sample Screen
A problem has been detected and Windows has been shut down to prevent damage to your computer.
KERNEL_STACK_INPAGE_ERROR
If this is the first time you've seen this Stop error screen, restart your computer. If this screen appears again, follow these steps:
Check to make sure any new hardware or software is properly installed. If this is a new installation, ask your hardware or software manufacturer for any Windows updates you might need.
If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadowing. If you need to use Safe Mode to remove or disable components, restart your computer, press F8 to select Advanced Startup Options, and then select Safe Mode.
Technical Information:
*** STOP: 0x00000077
Beginning dump of physical memory
Physical memory dump complete.
Contact your system administrator or technical support group for further
assistance.
Text may appear differently depending on where the error occurs.
Additional technical information (hex values) specific to a machine are not shown.
You may have a defective memory. This is even more likely if it only occurs when the system is cold or hot, but not all the time. Use a memory tester to confirm if it is defective or if you have spare memory, try replacement.
Windows 7 and Vista include a Memory Test program when booting from the Windows Installation DVD. Step-by-step instructions with screen shots are available at Using System Restore on 7/Vista/2008 as part of System Recovery.
Several software products that also provide memory and video diagnostics includes Fix-It Utilities Professional and SystemSuite Professional. Other diagnostic products include Eurosoft's PC Check and Iolo's System Mechanic.
Additional Memory Solutions:
Confirm all the memory is of the same type and speed. Many motherboards only work correctly when the memory is installed with matched sets and matched speeds.
If you added or changed your memory just before this problem occurred, try reverting to the prior memory configuration to confirm it's the source of the problem.
Check that the memory is fully seated in the sockets. Memory sockets often have side latches that need to be upright to indicate the memory is correctly locked in place.
Confirm the memory resides in the correct slots on the motherboard. You'll need to refer to the motherboard manual to confirm this. There is little consistency, even within a single vendor. Some systems require that memory is installed as matched pairs, but not always adjacent to each other!
It's also possible the memory problem is on the video card, as they often contain additional memory. The video card should be tested and/or try a different video card to see if the problem goes away.
FaultWire Staff Posted: 5-Oct-2008
Remove Viruses and Malware
8
Using an Anti-Virus product with the latest pattern files, scan the system for viruses and malware. Often this is called a deep-scan where it looks at every file in the system.
Several software products that handle the detection and removal of Viruses and Malware include Avanquest's Fix-It Utilities Professional and SystemSuite Professional. Other commonly available Anti-virus products are available from Computer Associates, F-Secure, Kaspersky Labs, McAfee, Sophos, Symantec, Trend Micro and others.
FaultWire Staff Posted: 5-Oct-2008
Check Hard Disk and Cables
7
If you had changed, added or removed hard drives, or changed or removed drive cabling, likely something is wrong. Recheck that the drives are properly installed and the cabling has not changed. Switching cables to different motherboard connectors or changing the master/slave drive jumpers (on old ATA drives) can cause this problem. In some systems, the cables were not plugged into the drive or motherboard securely and may have worked loose. Reseat all drive connectors.
It's also possible a hard drive is failing. Use a system diagnostic to validate the drive or swap to another hard disk.
Install the latest Windows software updates. Don't forget to check for non-critical updates too!
To manually get updates, open Internet Explorer (you can't use a non-Microsoft browser for updates).
For IE 8 and later: Click on Safety, then Windows Update. Follow the instructions.
For IE 7 and older: Click on Tools, then Windows Update. Follow the instructions.
FaultWire Staff Posted: 5-Oct-2008
Get the Latest Drivers
6
Check if you are using the latest hardware drivers, especially the chipset and video drivers. Older drivers are a common contributor to BSoD issues.
You can use a product like Driver Genius or Radar Sync to verify you have the latest drivers and help keep all your drivers up-to-date. If you're comfortable with driver installations, you can individually find and install current drivers.
The requested page of kernel data from the paging file could not be read into memory.
After the Stop code will be 4 hex values: {Parameter 1, Parameter 2, Parameter 3, Parameter 4}. If Parameter 1 has a value of 0, 1, or 2:
Parameter 1 specifies how the page was retrieved:
0x00000000
The page of kernel data was retrieved from page cache.
0x00000001
The page was retrieved from a disk drive.
0x00000003
The page was retrieved from a disk drive and the storage stack returned SUCCESS, but Status.Information is not equal to PAGE_SIZE.
Parameter 2 specifies the value that appears in the stack where the signature should be.
Parameter 3 is set to 0.
Parameter 4 specifies address of the signature on the kernel stack.
If Parameter 1 is a value 3 or above:
Parameter 1 specifies the status code.
Parameter 2 specifies the I/O status code. Common codes include:
0xC000009A
A driver error occurred.
0xC000009C
Bad sectors on the disk drive.
0xC000009D
The controller does not see the hard drive due to a bad drive or cabling problem.
0xC000016A
There are bad sectors on the disk drive.
0xC0000185
The SCSI devices have improper termination, bad cabling, or devices are not configured properly causing two devices to use the same IRQ (Interrupt Request).
While BSoD fatal stop errors are identified by Microsoft Windows, they are often caused by
non-Microsoft applications, drivers and hardware issues.
Research this Issue
Getting search results...
Notes
While we believe this information up to date and accurate, FAQware is not responsible for any inaccuracies. If you find something that is out of date or inaccurate, please let us know at
so we can correct it.