Page fault in non paged area

  • Thread starter Thread starter the K
  • Start date Start date
T

the K

Windows xp is restarting as soon as it appears to be finished booting. The
error message is the title of my post. System Restore doesn't work in safe
mode, so that's out. Does anyone know how to resolve this problem?
 
Background information on Stop Error message
http://msdn2.microsoft.com/en-us/library/ms793437.aspx

0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
(Click to consult the online MSDN article.)
Requested data was not in memory. An invalid system memory address was
referenced. Defective memory (including main memory, L2 RAM cache, video
RAM) or incompatible software (including remote control and antivirus
software) might cause this Stop message, as may other hardware problems
(e.g., incorrect SCSI termination or a flawed PCI card).
Source: http://aumha.org/a/stop.htm

Remove the dust bunnies and test the RAM memory
http://www.elephantboycomputers.com/page2.html#Hardware_Tshoot

Check the hard drive for bad sectors by running chkdsk /f /r

Check the System log of Event Viewer for Error Reports.

Please post copies of all Error and Warning Reports appearing in the
System log in Event Viewer for the last boot. No Information Reports or
Duplicates please. Indicate which also appear in a previous boot.

You can access Event Viewer by selecting Start, Control Panel,
Administrative Tools, and Event Viewer.

A tip for posting copies of Error Reports! Run Event Viewer and double
click on the error you want to copy. In the window, which appears is a
button resembling two pages. Click the button and close Event
Viewer.Now start your message (email) and do a paste into the body of
the message. Make sure this is the first paste after exiting from
Event Viewer.

Are there any yellow question marks in Device Manager? Right click on
the My Computer icon on your Desktop and select Properties,
Hardware,Device Manager. If yes what is the Device Error code?

Try Start, Run, type "sigverif.exe" without quotes and hit OK. What
drivers are listed as unsigned? Disregard those which are not checked.

--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
 
the K said:
Windows xp is restarting as soon as it appears to be finished booting. The
error message is the title of my post. System Restore doesn't work in safe
mode, so that's out. Does anyone know how to resolve this problem?
Click to expand...


run a RAM test
 
in
Windows xp is restarting as soon as it appears to be finished booting. The
error message is the title of my post. System Restore doesn't work in safe
mode, so that's out. Does anyone know how to resolve this problem?
Click to expand...

Get memtest86 to check your memory.
 
I ran memtest86 and my memory is fine. I read that antivirus software can
cause this error, so I uninstalled it. However, this didn't solve the issue.
Any other ideas?
 
I am not clear what you mean when you refer to System Restore and safe
mode. What happens if you try?

Lots of suggestions still left to try.

Background information on Stop Error message
http://msdn2.microsoft.com/en-us/library/ms793437.aspx

0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
(Click to consult the online MSDN article.)
Requested data was not in memory. An invalid system memory address was
referenced. Defective memory (including main memory, L2 RAM cache, video
RAM) or incompatible software (including remote control and antivirus
software) might cause this Stop message, as may other hardware problems
(e.g., incorrect SCSI termination or a flawed PCI card).
Source: http://aumha.org/a/stop.htm

Remove the dust bunnies and test the RAM memory
http://www.elephantboycomputers.com/page2.html#Hardware_Tshoot

Check the hard drive for bad sectors by running chkdsk /f /r

Check the System log of Event Viewer for Error Reports.

Please post copies of all Error and Warning Reports appearing in the
System log in Event Viewer for the last boot. No Information Reports or
Duplicates please. Indicate which also appear in a previous boot.

You can access Event Viewer by selecting Start, Control Panel,
Administrative Tools, and Event Viewer.

A tip for posting copies of Error Reports! Run Event Viewer and double
click on the error you want to copy. In the window, which appears is a
button resembling two pages. Click the button and close Event
Viewer.Now start your message (email) and do a paste into the body of
the message. Make sure this is the first paste after exiting from
Event Viewer.

Are there any yellow question marks in Device Manager? Right click on
the My Computer icon on your Desktop and select Properties,
Hardware,Device Manager. If yes what is the Device Error code?

Try Start, Run, type "sigverif.exe" without quotes and hit OK. What
drivers are listed as unsigned? Disregard those which are not checked.

--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
 
Found the culprit. It was the file cfgwiz.exe, which is a Norton Systemworks
or Antivirus file. I disabled that through MSCONFIG.EXE and the computer
booted fine. Thanks a lot Vanguard, the solution you provided took me 10 min,
compared to the 2 hours I spent on the phone with Microsoft support to no
avail.
 
Actually, this is just a by product of a bigger problem. I've noticed that
whenever I attempt to open the C:\Windows\System32 folder in windows explorer
or perform the dir command in dos under C:\Windows\System32\Drivers, I get
the same error. What would cause a page fault when an attempt is made to open
these directories?
 
I don't get a blue screen . However, I get the message, "Windows has
encountered and error and will close the application...etc." It mentions that
the file kernel32.dll caused an error.
 
WangVS said:
the K;3784888 Wrote:
....


It's just disconcerting that this occurred after upgrading the res on
the two monitors. The only other change made to the system was
installing the trial version of Ultramon, a utility for working with
multiple monitors. Ultramon itself has not crashed afaik.

Oh yes, one more thing: I have ECC memory. That means Error
Correcting memory. I really don't think this is being caused by the
memory.
Click to expand...

Have you tried putting the res back to where it was and uninstalling
Ultramon?

If your BIOS set to use ECC memory? Was it installed in the same
timeframe as the above stuff? Do you actually NEED ECC RAM?

Have you tested memory? Memtest is a decent tester but there are many
others available.

I think I'd start with looking at RAM, after putting things back as
they were before you made the changes. Then report back here is no joy.

HTH,

Twayne`
 
WangVS said:
Some people have reported clearing up this problem by changing memory.
That's really distressing because the error reported is an internal OS /
app thing, not a true "fault." A page fault is a signal from the CPU to
the OS to let the OS know that a memory page presently not paged in must
be paged in for the current process to continue.
Click to expand...

A page fault is a hardware interrupt. The hardware doesn't generate such
an interrupt on a whim, it generates it because something in memory (I
would call them page tables) has a bit set saying that the corresponding
page in the address space is not resident.

"Non-paged memory" is simply storage where the system does not set the
"page invalid" bit. If something else comes along, and sets that bit,
then you will get your page fault when the page is referenced.

Admittedly, this would not be anything to do with an actual memory fault.
 
Back
Top