PAGE_FAULT_IN_NONPAGED_AREA

[Mark Kennedy]

I had a registry problem earlier this week. It would not boot. In the
process of fixing that, now I get the following error:

Stop 0x00000050 PAGE_FAULT_IN_NONPAGED_AREA (0xFFFFAFF8, 0, 0x8053C7B1, 0).

I searched and found the suggestion that this may be a problem with RAM. I
put new ram in. No go.

Tried this and that. Restoring previous registry etc.

Finally resurrected an old HDD. Loaded XP, and it goes well on the same PC
with unchanged specs.

MMmm.

Any ideas?

Mark

 

[S.Sengupta]

Hello!
This could be caused by j audio drivers, incompatible video drivers, bad
or corrupt hard disk, and faulty RAM. The error may be triggered by an
event such as plugging in a USB device, but the problem is, the fault
may not lie with the device itself that was actually plugged in.Errors
hide the exact curlprit.
You may try the following things:-
1]go to Device manager and check for any faulty hardware.
2]Disable any services those are associated with hardwares by using
msconfig [start >Run >msconfig >ok]
3] update all the hardware drivers.
4] check event viewer for any error log
5[ If you use more than one RAM stick just insert one and take off the
other for a trial error.
All the best/
ssg/pronetwirks.org

 

[Mark Kennedy]

Many thanks
But I cannot get into the PC to test or do anything.
As soon as it boots I get the blue screen of death.
It is unlikely to be hardware as if I swap the HDD, away it goes (no
changes) The HDD tests ok when I put it in as the secondary HDD.

Any further help would be appreciated. I do not want to loose data in My
Docs.

Mark

Hello!
This could be caused by j audio drivers, incompatible video drivers, bad
or corrupt hard disk, and faulty RAM. The error may be triggered by an
event such as plugging in a USB device, but the problem is, the fault
may not lie with the device itself that was actually plugged in.Errors
hide the exact curlprit.
You may try the following things:-
1]go to Device manager and check for any faulty hardware.
2]Disable any services those are associated with hardwares by using
msconfig [start >Run >msconfig >ok]
3] update all the hardware drivers.
4] check event viewer for any error log
5[ If you use more than one RAM stick just insert one and take off the
other for a trial error.
All the best/
ssg/pronetwirks.org

I had a registry problem earlier this week. It would not boot. In the
process of fixing that, now I get the following error:

Stop 0x00000050 PAGE_FAULT_IN_NONPAGED_AREA (0xFFFFAFF8, 0, 0x8053C7B1, 0).

I searched and found the suggestion that this may be a problem with RAM. I
put new ram in. No go.

Tried this and that. Restoring previous registry etc.

Finally resurrected an old HDD. Loaded XP, and it goes well on the same PC
with unchanged specs.

MMmm.

Any ideas?

Mark

 

[Mark Kennedy]

If I reload XP will I loose the data from MY Docs. It says I will.

Can I safely copy it to some other place on the same HDD without loss?

Mark

 

[S.Sengupta]

Hi!
safest option is to go for "Repair XP".[You may Bakup your data in a CD].
How To:-
http://www.michaelstevenstech.com/XPrepairinstall.htm.
regards/
ssg

 

[Malke]

If I reload XP will I loose the data from MY Docs. It says I will.

Can I safely copy it to some other place on the same HDD without loss?

Mark

I don't know why you say it can't be hardware - you proved that it *was*
caused by hardware: your old hard drive. Yes, it's possible that a
drive won't boot but you can slave it and get data off it. That's what
I would do. Run a hard drive diagnostic on it if you want to be sure,
but I'd salvage my data first and then replace it.

Malke

 

[Mark Kennedy]

Many thanks
No I don't suspect hardware, though nothing is impossible. But all the
hardware works fine, but the system does not boot.
When I load XP on an old drive, all works fine. An the HDD I want it to work
on is just weeks old.

I did run a test on it overnight just in case the h'ware doubters were right
and I was wrong, but it had no errors.

Anyway, a shot while ago I gave up. Very annoyed but resolute, I bit the
bullet and reinstalled XP from the CD. So far all is ok.

I now suspect the registry, but the damage was too deep to fix, and I could
not get it to restore the old effectively.

Be nice to think that MS can come up with a better way to protect their
property rights and let us keep better back-ups of systems and thus maintain
ours. A bullet proof registry backup that is readily accessible from the
bootable CD would be nice.

I hope it continues

Mark

 

[Malke]

Many thanks
No I don't suspect hardware, though nothing is impossible. But all the
hardware works fine, but the system does not boot.
When I load XP on an old drive, all works fine. An the HDD I want it
to work on is just weeks old.

Just "weeks old" is no guarantee that the hard drive won't fail. In
fact, if hardware is going to fail, it usually does so within the first
few months (and if it doesn't fail early on, a hard drive can last
years).

I did run a test on it overnight just in case the h'ware doubters were
right and I was wrong, but it had no errors.

It's good you got your system up and running. Of course, diagnosing
someone's machine over Usenet isn't the most accurate way! See, when
you say "doesn't boot", this makes *me* think you aren't even getting
through the POST. From your last message, you may just have been unable
to get into Windows. Different situation entirely.

(snip)

Be nice to think that MS can come up with a better way to protect
their property rights and let us keep better back-ups of systems and
thus maintain ours. A bullet proof registry backup that is readily
accessible from the bootable CD would be nice.

Ah hah hah. There is no perfect software. There is no perfect hardware.
There is no "bullet-proof" situation. Buy and use some imaging software
like Norton Ghost or the program from Acronis and make images. Back up
your data regularly. Be prepared to restore images and data.

Cheers,

Malke

 

[Mark Kennedy]

Thanks.



No I could not boot, as I said. But I had an old HDD that I could boot from.
As I said I loaded XP onto that and put my new HDD in as a slave and used
that to test it. My point re HDD age is that in my experience, a new HDD
that is a few weeks old is less like to play up than one that is 10 yrs old.

Ah hah hah. There is no perfect software. There is no perfect hardware.

There is no "bullet-proof" situation. Buy and use some imaging software

like Norton Ghost or the program from Acronis and make images. Back up

your data regularly. Be prepared to restore images and data.

That is a lot of work and a lot of time and additional resources. You are
expecting a home user to have "corporate" type resources. Why can't MS fix
this?

No need to be defensive. I like XP and respect MSs right to protect itself.
But previous versions were easier to deal with registry and boot problems as
I have had. It has cost me many many hours and in the end had to reload XP
with the risk of loosing a lot of data (too much to back up with out
"corporate" type resources). There has to be a better way. If I can improve,
everyone tells me. That is how I learn. If we the users don't let MS know
where we are having problems, how will they know?

 

[Alex Nichol]

Many thanks
No I don't suspect hardware, though nothing is impossible. But all the
hardware works fine, but the system does not boot.
When I load XP on an old drive, all works fine. An the HDD I want it to work
on is just weeks old.

I did run a test on it overnight just in case the h'ware doubters were right
and I was wrong, but it had no errors.

It can arise from multiple cause,

Actual hardware defect - most often RAM, possibly say Video RAM

Program defect in a driver associated with hardware - especially video
drivers, which are highly complex

Program defect in the core code of the system; extremely unlikely by
now unless it has been damaged, in which case an SFC /SCANNOW should
fix things

Defect in some other program that has muscled in on the non-paged area
to make itself permanently resident. Third party things *ought* not to
do this IMO, but I am aware that some do. Some components of Norton
System Works are known to do so, So if you have any Norton product
installed I would uninstall it, see if the error goes, and see if it
comes back after reinstallation (if so, scream at Symantec).