The KERNEL_DATA_INPAGE_ERROR bug check has a value of 0x0000007A.
This bug check indicates that the requested page of kernel data from
the paging file could not be read into memory.
Parameters
The four parameters that are listed in the message can have three
possible meanings. If the first parameter is 1 or 2, or 3 and the third
parameter is 0, the parameters have the following definitions.
Parameter
Description
1
The lock type that was held (1, 2, or 3)
2
The error status (usually an I/O status code)
3
If Lock Type is 1: the current process
If Lock Type is 2 or 3: 0
4
The virtual address that could not be paged into memory
If the first parameter is 3 (and the third parameter is nonzero) or 4, the parameters have the following definitions.
Parameter
Description
1
The lock type that was held (3 or 4)
2
The error status (typically an I/O status code)
3
The address of the InPageSupport structure
4
The faulting address
Otherwise, the parameters have the following definitions.
Parameter
Description
1
The address of the page table entry (PTE)
2
The error status (usually an I/O status code)
3
The PTE contents
4
The faulting address
Cause
Frequently, you can determine the cause of the
KERNEL_DATA_INPAGE_ERROR bug check from the error status (Parameter 2).
Some common status codes include the following:
These status codes are the most common ones that have specific
causes. For more information about other possible status codes that can
be returned, see the Ntstatus.h file in the Microsoft Windows Driver Kit (WDK).
Another common cause of this error message is defective hardware or failing RAM.
A virus infection can also cause this bug check.
Resolving the Problem
Resolving a bad block problem: An I/O status code of
0xC000009C or 0xC000016A typically indicates that the data could not be
read from the disk because of a bad block (sector). If you can restart
the computer after the error, Autochk runs automatically and attempts
to map the bad sector to prevent it from being used anymore.
If Autochk does not scan the hard disk for errors, you can manually start the disk scanner. Run Chkdsk /f /r
on the system partition. You must restart the computer before the disk
scan begins. If you cannot start the computer because of the error, use
the Recovery Console and run Chkdsk /r.
Warning If your system partition is
formatted with the FAT file system, the long file names that the
Windows operating system uses might be damaged if you use Scandisk or
another MS-DOS-based hard disk tool to verify the integrity of your
hard disk from MS-DOS. Always use the version of Chkdsk that matches
your version of Windows.
Resolving a defective hardware problem: If the I/O status is C0000185 and the paging file is on an SCSI disk, check the disk cabling and SCSI termination for problems.
Resolving a failing RAM problem: Run the hardware
diagnostics that the system manufacturer supplies, especially the
memory scanner. For more information about these procedures, see the
owner's manual for your computer.
Check that all the adapter cards in the computer are properly
seated. Use an ink eraser or an electrical contact treatment, available
at electronics supply stores, to ensure adapter card contacts are clean.
Check the System Log in Event Viewer for additional error messages
that might help identify the device that is causing the error. You can
also disable memory caching of the BIOS to try to resolve this error.
Make sure that the latest Windows Service Pack is installed.
If the preceding steps do not resolve the error, take the system
motherboard to a repair facility for diagnostic testing. A crack, a
scratched trace, or a defective component on the motherboard can cause
this error.
Resolving a virus infection: Check your computer for
viruses by using any up-to-date, commercial virus scanning software
that examines the Master Boot Record of the hard disk. All Windows file
systems can be infected by viruses.
SOURCE: Lost of Hibernation
his Stop message indicates that the requested page of kernel data from the paging file could not be read into memory. This Stop message is usually caused by a bad block (sector) in a paging file, a virus, a disk controller error, or failing RAM. In rare cases, it is caused when nonpaged pool resources run out. It is also caused by defective hardware.
User Action:
If the I/O status is C0000185 and the paging file is on a SCSI disk, the disk cabling and SCSI termination should be checked for problems. Check your computer for viruses, using any up-to-date, commercial virus scanning software that examines the Master Boot Record of the hard disk. An I/O status code of 0xC000009C or 0xC000016A normally indicates the data cannot be read from the disk due to a bad block (sector). If you can restart the system after the error, Autochk runs automatically and attempts to map out the bad sector. If Autochk does not scan the hard disk for errors, manually launch the disk scanner. Run Chkdsk /f /r on the system partition. Restart the system before the disk scan begins. If you cannot start the system due to the error, use the Recovery Console and run Chkdsk /r . Caution: If your system partition is formatted with the FAT file system, the long file names used by Windows 2000 can be damaged if Scandisk or another MS-DOSbased hard disk tool is used to verify the integrity of your hard disk from an MS-DOS prompt. (An MS-DOS prompt is typically derived from an MS-DOS startup disk or from starting MS-DOS on a multiboot system.) Always use the Windows 2000 version of Chkdsk on Windows 2000 disks. Another common cause of this Stop message is failing RAM. Run hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on these procedures, see the owners manual for your computer. Check that all network adapters in the computer are properly seated. Use an ink eraser or an electrical contact treatment, available at electronics supply stores, to ensure network adapter contacts are clean. Check the System Log in Event Viewer for additional error messages that might help pinpoint the device causing the error. Disabling memory caching of the BIOS might also resolve it. Finally, if all the above steps fail to resolve the error, take the system motherboard to a repair facility for diagnostic testing. A crack, a scratched trace, or a defective component on the motherboard can also cause this error. For more troubleshooting information about this Stop message, refer to the Microsoft Knowledge Base at http://support.microsoft.com/support.
2,707 views
Usually answered in minutes!
×