Stop Error Message: 0X0000007A(OXC03E10A8.........................

[Guest]

My computer has been working great with no problems until I received a Stop
Error Message. The message only occurs when the computer is unattended for
15 to 30 minutes. When I return and bring the computer out of the screen
saver, I have a blue screen and the following error message, to gain
control of the computer, I have to press the Start/Reset button on the
computer. Any help with solving this problem would be appreciated, I will
only type part of the message:

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 message, ............ restart the
computer.

Check to make sure any new HW & SW is properly
installed.......................

If the problem continues, disable or remove any newly installed HW or
SW........

Technical info:
STOP: 0x0000007A (0xc03E10A8, 0xC0000185, 0xf842a759, 0x1A5AD860)

NTFS.Sys - Address F842A759 Base at F83C9000, DataStamp 41107eea

Beginning dump of physical memory........

 

[Guest]

Thier is a hotfix from microsoft for that,its kb900485

 

[Guest]

Hi Andrew, thank you very much for responding to my question. Unfortunately
I do not understand the term 'hotfix' or how to implement this fix. Could
you elaborate on this or tell me where to find this info? Meanwhile I will
go to some of the Microsoft websites and search for this term, hopefully
this will give me the info.

Thank you again,

 

[Guest]

Andrew, I did the search and got the info on 'HotFix', the undate has been
installed and hopefully this will fix the problem. I noticed there are other
'Hotfixes' available and I will be keeping my eye on them in case I still
encounter any problems.

Thank you again,

 

[John John]

Hi Carroll,

Unfortunately, Andrew E. gave you incorrect information. You can read
the article that he point you to if you wish, it's here:
http://support.microsoft.com/kb/900485

That article refers to a Stop 0x7E in aec.sys. The hotfix provides a
replacement Aec.sys file.

Your error is a Stop 0x7E in NTFS.Sys. NOT the same thing at all as
what Andrew E. send you on a fools errand for! *DO* *NOT* bother with
the hotfix in the article, it will do *nothing* to help you!
Furthermore, if you call Microsoft asking for a hotfix they will ask you
why you need the hotfix. If you give them the description of your
problem and it doesn't match the problem addressed by the hotfix they
may charge you $$$ for a service call!

The hotfixes referred to in some of these Microsoft articles are fixes
that are available to address *specific* problems on some computers.
These hotfixes are not meant to be made available to the general public
because they have not been fully tested or because they may cause other
problems if applied to computers without the problem that the fix
addresses, that is why you have to call Microsoft to obtain hotfixes.

As for your 0x7A error in NTFS.Sys, I am sorry that I cannot provide
more accurate advice for your problem. You might want to sift through
these:
http://search.microsoft.com/results...=0&SearchBtn0=Search&FORM=QBME1&l=1&mkt=en-US

Errors in NTFS.sys can lead to loss of data or complete disk and file
system failure! Make a back up of your files while you can!

Good luck,

John

 

[Guest]

Thanks John for your excellent input, I have a question for you since it
sounds like you have lots of knowledge concerning this type of problem.
Since I posted this message, I disabled all power options and the screen
saver which was the Microsoft blank screen saver, not a third party screen
saver is there is such a thing. After disabling these features, I have not
encountered this problem again. Is it possible this type of problem could be
repaired by nothing more than shutting down the computer and rebooting? I
suspect this problem may not resurface and again, it may happen again, I
hope not.

 

[John John]

It could be that the problem was a one time only thing, Windows could
have made a bad disk read or made a bad write then tried to read from
it. It is quite possible that a simple reboot might have taken care of
the problem. It could be that a minor case of disk corruption caused
the error. It is difficult to know exactly what caused the error, this
is an excerpt from a Windows Resource Kit troubleshooting guide:

====================================================================
Stop 0x0000007A or KERNEL_DATA_INPAGE_ERROR

This Stop message, also known as Stop 0x7A, indicates that the requested
page of kernel data from the paging file could not be read into memory.

One of the following conditions usually causes a Stop 0x7A: a bad sector
in a paging file, a virus, a disk controller error, defective hardware,
or failing RAM. In rare cases, a Stop 0x7A occurs when nonpaged pool
resources run out.
====================================================================


The Windows 2000 Resource Kit offers further advice which may also apply
to Windows XP:

====================================================================
Resolving the Problem

Stop 0x7A 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.

Viruses. Check your computer for viruses, using any up-to-date,
commercial virus scanning software that examines the Master Boot Record
of the hard disk. Any Windows 2000 file system can be infected by viruses.

Bad block. 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, 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. For more
information about the Recovery Console, see "Troubleshooting Tools and
Strategies" in this book.

Failing RAM. Another common cause of this error message is failing RAM.
Run hardware diagnostics supplied by the system manufacturer, especially
the memory scanner. For details on these procedures, see the owner's
manual for your computer.

Also, check that all the adapter cards in the computer, including memory
modules, are properly seated. Use an ink eraser or an electrical contact
treatment, available at electronics supply stores, to ensure adapter
card contacts are clean. Be sure to wipe the cleaned contacts off,
removing all cleaning debris, before reinstalling the adapter card into
the computer. If compressed air is available, use it to clear out the
adapter card slot.

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 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 the 0x7A Stop message, refer
to the Microsoft Knowledge Base link, using the keywords winnt and
0x0000007A. For information about this resource, see "Additional
Resources" at the end of this chapter.
======================================================================

The one thing that is a bit unsettling about the error is seeing
NTFS.sys associated with it. I do not want to unduly alarm you but that
can sometimes be very bad news! I cannot stress enough that you should
make sure that your important files are properly backed up! After the
files are backed up it may be a good idea to run a chkdsk on the drive.
Be warned that running chkdsk may lead to loss of data, it is always
advisable to have a proper backup before running chkdsk. Not running
chkdsk may be a bad decision if disk corruption is suspected. If left
unchecked minor disk corruption may develop into a major corruption
problem that may lead to loss of data. Microsoft sums it up this way:

"For a mission-critical computer that is expected to be online 24 hours
a day, doing nothing (not running chkdsk) might be a necessary choice.
The drawback to this option is that relatively minor corruption can
become major corruption if you do not repair the volume as soon as
possible after you detect the corruption. Therefore, consider this
option only if keeping a system online is more important than the
integrity of the data stored on the corrupted volume. You must consider
all data on the corrupted volume at risk until you run Chkdsk."

John

 

[Guest]

I was able to run 'chkdsk c: /f/r & chkdsk d: /f/r on both of my HDs but the
report at the end of the test was breifly flashed on the display, not long
enough to read the report. Does that mean there was nothing found and the
drives are OK? I would think the report at the end of this test would be
available somewhere in a file but I have no idea what the file name would be.
I would also think the report would stay on the display/screen until the
user deleted it?

 

[John John]

Look in the Event Log for the chkdsk report.

John

 

[Ron Martell]

Thier is a hotfix from microsoft for that,its kb900485

Andrew, please take your incompetent blather and go away, far far
away. You are apparently totally incapable of comprehending the
questions being posted on these newsgroups and your wrong answers are
annoying at best and very often are in fact dangerous.

Why else would you post a reference to an article about STOP
0x0000007e as a solution for a problem involving STOP 0x0000007A?

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2008)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."

 

[Ron Martell]

My computer has been working great with no problems until I received a Stop
Error Message. The message only occurs when the computer is unattended for
15 to 30 minutes. When I return and bring the computer out of the screen
saver, I have a blue screen and the following error message, to gain
control of the computer, I have to press the Start/Reset button on the
computer. Any help with solving this problem would be appreciated, I will
only type part of the message:

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 message, ............ restart the
computer.

Check to make sure any new HW & SW is properly
installed.......................

If the problem continues, disable or remove any newly installed HW or
SW........

Technical info:
STOP: 0x0000007A (0xc03E10A8, 0xC0000185, 0xf842a759, 0x1A5AD860)

NTFS.Sys - Address F842A759 Base at F83C9000, DataStamp 41107eea

Beginning dump of physical memory........

The most likely cause of your problem is the hard drive. Go to the
hard drive manufacturer's web site and download their free diagnostic
test utility and run that to check out your hard drive for possible
problems.

Here is one Microsoft Knowledge Base article that might possibly be
relevant (boot drive connected as stand-alone slave):
http://support.microsoft.com?kbid=330100

Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2008)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."

 

[Guest]

Hi Ron,

Your diagnostics of the problem seems to be spot on the mark! I went to the
MS Knowledge Base article you suggested and it discribed the problem axactly.

Back in Feb I was having some serious problems with my computer coming out
of the standby mode. I reformatted the two hard drives on my computer and
reloaded all the SW. Seem to work OK until the lastest problem. But after
having the previous problem with 'Standby', I have not been using that
option but I was using the MS screen saver and the problem returned but
differently. I would not be surprised if the two problems are related to one
of the HDs coming out of some standby mode after the computer is put into a
screen saver or standby mode.

I don't understand the article completely such as the advice about the slave
dr vs the master dr. I still use the original 'C' dr (set to Master) for the
operating system and MS Office and the second dr 'D' as the slave dr with
some of the third praty programs I am using loading onto the 'D' dr. Is the
MS Knowledge Base article saying that the second dr should be a master dr.
If so, that doesn't seem right, I don't believe you can have two master drs
in one computer but I am not an expert on this either.

Can you restate the MS Knowledge Base article in manner that I can
understand, sorry for my lack of understanding but I am sure the verbiage in
the 'Resolution' (PATA vs SATA & ect) section has the answer imbedded
somewhere but I need to know exactly what I should do.

I think my situation is complicated by using two HDs. Not sure what I
should do about this but I would think this should not be a problem since I
have been doing this for many yrs on different computers.

Not sure what I should do at this time. For sure your suggestion of
contacting the manufacture of the second HD would be a good place to start.
They may sled some light on this problem since I expect the second HD is the
source of the problem.