page fault in non-paged area

[Barobi]

hi folks,

i have an acer laptop with xp home; suddenly, it keeps re-booting with the
BSOD that says at the top "page fault in non paged area". it disappears too
fast to read the rest - which lists a loong string of 0x00000050 .... etc.

it boots into safe mode ok, but i don't have a clue what to do in safe mode.
SP3 is up to date etc.

thanks for any pointers.

BC

 

[PA Bear [MS MVP]]

What anti-virus application or security suite is installed and is your
subscription current? What anti-spyware applications (other than Defender)?
What third-party firewall (if any)?

Has a(another) Norton or McAfee application ever been installed on the
computer (e.g., a free-trial version that came preinstalled when you bought
it)?
~~~~~~~~~~~~~~~~~~~~~~~~~~~
To see the STOP error, you'll need to change the way Windows reacts to a
BSOD.

Right-click on My Computer (on your desktop) | Properties | Advanced |
Startup and recovery | Settings | System Failure | Make sure the first 2
options here are checked but that "Automatically restart" is NOT checked |
OK your way out and reboot.

Alternately, look for the STOP error in Start | Settings | Control Panel |
Administrative Tools | Event Viewer | System.
~~~~~~~~~~~~~~~~~~~~~~~~~~~
<QP>
0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
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).
</QP>
Source: http://aumha.org/a/stop.htm

<QP>
The following actions might prevent an error like this from happening again:

1. Download and install updates...for your computer from Windows Update.
2. Scan your computer for computer viruses.
3. Check your hard disk for errors.
</QP>
Source: http://msdn.microsoft.com/en-us/library/ff559023(VS.85).aspx

 

[csnyder]

May be bad form - but I'll top post so everybody see this. On an ACER with
page fault in non-paged area the first line of attack is to REMOVE the e-lock
application. It may have worked when it was written but it conflicts with
both AVG and something Microsoft updated back in 2008 or 2009

What anti-virus application or security suite is installed and is your
subscription current? What anti-spyware applications (other than Defender)?
What third-party firewall (if any)?

Has a(another) Norton or McAfee application ever been installed on the
computer (e.g., a free-trial version that came preinstalled when you bought
it)?
~~~~~~~~~~~~~~~~~~~~~~~~~~~
To see the STOP error, you'll need to change the way Windows reacts to a
BSOD.

Right-click on My Computer (on your desktop) | Properties | Advanced |
Startup and recovery | Settings | System Failure | Make sure the first 2
options here are checked but that "Automatically restart" is NOT checked |
OK your way out and reboot.

Alternately, look for the STOP error in Start | Settings | Control Panel |
Administrative Tools | Event Viewer | System.
~~~~~~~~~~~~~~~~~~~~~~~~~~~
<QP>
0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
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).
</QP>
Source: http://aumha.org/a/stop.htm

<QP>
The following actions might prevent an error like this from happening again:

1. Download and install updates...for your computer from Windows Update.
2. Scan your computer for computer viruses.
3. Check your hard disk for errors.
</QP>
Source: http://msdn.microsoft.com/en-us/library/ff559023(VS.85).aspx



.

And for those who always look at the END for any solutions:
On an ACER with page fault in non-paged area the first line of attack is to
REMOVE the e-lock application. It may have worked when it was written but it
conflicts with both AVG and something Microsoft updated back in 2008 or 2009