Page fault in non paged area

[Guest]

Hi all

I recently upgraded a PC to a new mobo, processor and
PC3200 RAM. New install of Windows XP on a SATA drive.

Ever since, at intervals varying from every boot of
Windows to once a week, I get a bluescreen with either a
nonspecific error or Page fault in non paged area.

Suspecting this to be the RAM module at fault, I did some
research and found out that my mobo (an Asus A7N8X-E
deluxe) is very particular about which PC3200 modules it
uses, and mine wasn't on the list. Consequently I sent
mine back for a refund and used a 512mb stick of PC 2700
that has been used in another system for a year without
issues. The mobo apparently isn't fussy about PC2700
modules.

However I am still getting the blue screens with the
known good memory. So the question is - what else can
cause this error?

TIA

 

[johy99]

Hi,

Please try this: R

Right click my computer>properties>advanced>performance>setting
button>advanced tab>Virtual memory>change>select your C drive>under paging
file size for selected drive choose custom size>set the initial size to the
total size of your ram (for example 512 MB)> and the maximum size to 1.5
times this eg 768 MB>click set>okay>apply>Okay to close>apply>okay>restart
computer.

Thanks

 

[Bob Day]

Hi all

I recently upgraded a PC to a new mobo, processor and
PC3200 RAM. New install of Windows XP on a SATA drive.

Ever since, at intervals varying from every boot of
Windows to once a week, I get a bluescreen with either a
nonspecific error or Page fault in non paged area.

Suspecting this to be the RAM module at fault, I did some
research and found out that my mobo (an Asus A7N8X-E
deluxe) is very particular about which PC3200 modules it
uses, and mine wasn't on the list. Consequently I sent
mine back for a refund and used a 512mb stick of PC 2700
that has been used in another system for a year without
issues. The mobo apparently isn't fussy about PC2700
modules.

However I am still getting the blue screens with the
known good memory. So the question is - what else can
cause this error?

It still sounds like it might be an intermittent memory problem.
You might try going into the bios and changing to less
aggressive memory settings. You also could try downloading
Memtest86+ from http://www.memtest.org and running it
overnight. It might not find a problem -- if there is a problem
with the memory, it might be too intermittent -- but if it does
find a problem, then you'll know what it was.

-- Bob Day
http://bobday.vze.com

 

[Guest]

-----Original Message-----


It still sounds like it might be an intermittent memory problem.
You might try going into the bios and changing to less
aggressive memory settings. You also could try downloading
Memtest86+ from http://www.memtest.org and running it
overnight. It might not find a problem -- if there is a problem
with the memory, it might be too intermittent -- but if it does
find a problem, then you'll know what it was.

-- Bob Day
http://bobday.vze.com

The situation, which has been steadily deteriorating over
the last few weeks, has got exponentially worse today -
now it bombs out every time at the black Windows loading
screen. A bluescreen flashes for an instant but I can't
read anything before it reboots.

Both sticks of memory have tested fine; I've tested the
first, new one thoroughly before, and the other has been
in use for a year without a sniff of a problem on that
PC. I am starting to suspect that it is a major fault
with the motherboard - or possibly a power supply issue -
although I use a fairly decent Antec 450W PSU that's only
a year old. I'm getting 3.29v on the 3.3v line and 4.97v
on the 5v line - is this enough to knock out a sensitive
mobo?

I'm now trying a reinstall of Windows on an EIDE drive
and leaving SATA out of the equation to see what
happens...

 

[Bob Day]

The situation, which has been steadily deteriorating over
the last few weeks, has got exponentially worse today -
now it bombs out every time at the black Windows loading
screen. A bluescreen flashes for an instant but I can't
read anything before it reboots.

Both sticks of memory have tested fine; I've tested the
first, new one thoroughly before, and the other has been
in use for a year without a sniff of a problem on that
PC. I am starting to suspect that it is a major fault
with the motherboard - or possibly a power supply issue -
although I use a fairly decent Antec 450W PSU that's only
a year old. I'm getting 3.29v on the 3.3v line and 4.97v
on the 5v line - is this enough to knock out a sensitive
mobo?

No. Those readings are fine. CPU overheating maybe?
To check temperatures, download the free Home Edition
of Everest from http://www.lavalys.com/products.php?lang=en
Run it, expand "Computer", and click on "Sensor". Also you
check for voltage fluctuations on that same display -- it updates
automatically every few seconds.

You can also use Everest to check the SMART readings of
your hard drive: Expand "Storage" and click on "SMART".
The "Worst" value of all the parameters not marked "Always
passing" should be well above the "Threshold" (except for
the "Spin Retry Count", whose worst value may be just a
little over the threshold).

-- Bob Day
http://bobday.vze.com

 

[Alex Nichol]

Ever since, at intervals varying from every boot of
Windows to once a week, I get a bluescreen with either a
nonspecific error or Page fault in non paged area.

However I am still getting the blue screens with the
known good memory. So the question is - what else can
cause this error?

That area of RAM is used for critical code, that is so important that it
must never be paged out. It is code that is supposed to be free of such
errors, but there are some third party installations try to get in on
the act. In particular if you have installed any Symantec/Norton
software try uninstalling that