Blue Screen 0x0000007A

[Guest]

Hello,
I am getting this error on an HP Pavilion ze5730us laptop running XP Home
SP2. The computer runs fine for about 15 minutes and then the error shuts it
down. It seems to run longer when running on battery power.
I did a Google search and checked the Mircrosoft Stop error page. The
problem is that they do not list the error codes after the first set for my
problem. I would appreciate anyone letting me know what is causing the
problem. No hardware or software has been added to the computer for several
weeks. A virus scan runs clean. Spyware and malware scans are clean. Here is
the complete error message:

Stop 0x0000007A or KERNEL_DATA_INPAGE_ERROR
a problem has been detected and windows has been shut down to prevent damage
to your computer.

kernel_data_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 manufactuers
for any window 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 compute,
press F8 to select advanced startup options, and then select safe mode.

technical information

***STOP: 0x0000007a(oxco3eac70,oxc000000e,0xfab1c130,0x096f b860)
***atapi.sys-address fac1c130

Microsoft and Bob Eshelman's page do not list any of the codes after the
first.

Thanks, Jerry

 

[David Candy]

#define STATUS_NO_SUCH_DEVICE ((NTSTATUS)0xC000000EL) is param 2.
This is your status code. ATAPI is hard drive/CDRom and similar driver.
a.. Disks or storage controllers that are failing, defective, or improperly configured.
b.. Storage-related drivers or programs (tape management software, for example) that are not fully compatible with Windows XP Professional.
are possible causes.

Memory tester
http://oca.microsoft.com/en/windiag.asp

Driver Development Tools: Windows DDK

Bug Check 0x7A: KERNEL_DATA_INPAGE_ERROR
The KERNEL_DATA_INPAGE_ERROR bug check has a value of 0x0000007A. This indicates that the requested page of kernel data from the paging file could not be read into memory.

Parameters
The four parameters listed in the message can have two possible meanings. If the first parameter is one, two, or three, the following definitions should be used:

Parameter Description
1 Lock type that was held (1, 2, or 3)
2 Error status (usually an I/O status code)
3 If Lock Type is 1 or 2: current process
If Lock Type is 3: virtual address

4 Virtual address that could not be paged into memory


Otherwise, use the following definitions:

Parameter Description
1 Page Table Entry (PTE) address
2 Error status (usually an I/O status code)
3 Virtual address
4 Virtual address that could not be paged into memory


Cause
Frequently, the cause of this error can be determined from the error status (Parameter 2). Some common status codes are:

a.. 0xC000009A, or STATUS_INSUFFICIENT_RESOURCES, is caused by lack of nonpaged pool resources. • 0xC000009C, or STATUS_DEVICE_DATA_ERROR, is typically due to bad blocks (sectors) on the hard disk.
b.. 0xC000009D, or STATUS_DEVICE_NOT_CONNECTED, indicates defective or loose cabling, termination, or the controller not seeing the hard disk.
c.. 0xC000016A, or STATUS_DISK_OPERATION_FAILED, is also caused by bad blocks (sectors) on the hard disk.
d.. 0xC0000185, or STATUS_IO_DEVICE_ERROR, is caused by improper termination or defective cabling on SCSI devices, or two devices attempting to use the same IRQ.
These codes are the most common ones for which specific causes have been determined. For information about other possible status codes that can be returned, see the file ntstatus.h in the Windows DDK.

Another common cause of this error message is defective hardware or failing RAM.

This bug check can also be caused by a virus infection.

Resolving the Problem
Resolving a bad block problem: An I/O status code of 0xC000009C or 0xC000016A normally indicates that the data could not 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 the bad sector to prevent it’s further use.

If Autochk does not scan the hard disk for errors, you can manually launch the disk scanner. Run Chkdsk /f /r on the system partition. You must 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.

Warning If your system partition is formatted with the FAT file system, the long filenames used by Windows can be damaged if Scandisk or another MS-DOS-based hard disk tool is used to verify the integrity of your hard disk from MS-DOS. Always use the version of Chkdsk that matches your Windows version.

Resolving a defective hardware problem: If the I/O status is C0000185 and the paging file is on an SCSI disk, the disk cabling and SCSI termination should be checked for problems.

Resolving a failing RAM problem: Run the hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on 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 pinpoint the device that is causing the error. Disabling memory caching of the BIOS might also resolve this error.

Make sure that the latest Windows Service Pack is installed.

If the preceding 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 cause this error.

Resolving a virus infection: You should check your computer for viruses 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.

See Also
Bug Check 0x77 (KERNEL_STACK_INPAGE_ERROR)

Send feedback on this topic. / Built on Thursday, February 13, 2003
See Also
Bug Check 0x77 (KERNEL_STACK_INPAGE_ERROR)

 

[Ron Martell]

Hello,
I am getting this error on an HP Pavilion ze5730us laptop running XP Home
SP2. The computer runs fine for about 15 minutes and then the error shuts it
down. It seems to run longer when running on battery power.
I did a Google search and checked the Mircrosoft Stop error page. The
problem is that they do not list the error codes after the first set for my
problem. I would appreciate anyone letting me know what is causing the
problem. No hardware or software has been added to the computer for several
weeks. A virus scan runs clean. Spyware and malware scans are clean. Here is
the complete error message:

Stop 0x0000007A or KERNEL_DATA_INPAGE_ERROR
a problem has been detected and windows has been shut down to prevent damage
to your computer.

kernel_data_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 manufactuers
for any window 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 compute,
press F8 to select advanced startup options, and then select safe mode.

technical information

***STOP: 0x0000007a(oxco3eac70,oxc000000e,0xfab1c130,0x096f b860)
***atapi.sys-address fac1c130

Microsoft and Bob Eshelman's page do not list any of the codes after the
first.

Thanks, Jerry

I suspect that your problem is being caused by overheating.

The reasons for this are:
1. It is a laptop, which are highly susceptible to overheating.
2. The problem occurs at a relatively constant time interval after
startup (you said 15 minutes) which is consistent with components
overheating.
3. The problem take longer to appear when the laptop is running on
batteries. This makes sense because laptops operate in "low gear"
(reduced CPU speed) when running on battery so as to prolong the
battery life. The reduced electrical consumption means that less heat
is being produced and therefore the heat does not build up as quickly.

Possible causes include:
1. Failure of the CPU cooling fan.
2. Accumulation of dust inside the computer, providing heat-retaining
insulation on the chips and other components.
3. Blockage of the air circulation ducts because of work done inside
the computer and components not properly put back into place.

It will probably require the "hands on" attention of a factory
authorized service shop for that brand of laptop because of the
proprietary nature of the parts used. Continuing to use the laptop
under these circumstances could result in permanent damage to the CPU,
motherboard, and/or other hardware components.

Good luck


Ron Martell Duncan B.C. Canada
--
Microsoft MVP
On-Line Help Computer Service
http://onlinehelp.bc.ca

In memory of a dear friend Alex Nichol MVP
http://aumha.org/alex.htm