Page fault in non-paged area?

  • Thread starter Thread starter Matt
  • Start date Start date
M

Matt

I've gotten that BSOD message twice now, while attempting
to install quake 3. The only thing I can think of is that
it could be caused by the fact that I have an unformated
(read: raw) partition on my computer, but that really
shouldn't affect anything. I'm going to try formatting it
and then installing quake 3 again. Anyone else who's
experienced this error, any help would be appreciated.
 
Upon formatting the raw partition, and then attempting to
install quake 3 again, I got the error "PFN list
corrupt"(or possibly failure). I don't really understand
what's going on, I've downloaded all of the recommended
updates from windowsupdate, I have all the latest and
proper drivers for everything on my computer, so I can't
imagine what would be causing these problems.
 
Matt said:
I've gotten that BSOD message twice now, while attempting
to install quake 3. The only thing I can think of is that
it could be caused by the fact that I have an unformated
(read: raw) partition on my computer, but that really
shouldn't affect anything. I'm going to try formatting it
and then installing quake 3 again.
Click to expand...


The non-paged area is a section of RAM that is used by code so important
that it may never be dropped out into the pagefile by virtual memory
management. So it is mainly core system code. This is very unlikely to
have errors such as indicated by this message, so it usually indicates
hardware trouble - bad RAM or corruption of the code on the hard disk.
But there are a few third party things that push themselves into this
area - I understand some aspects of Norton SystemWorks do so, so if you
have installed anything of that sort, I would uninstall it and see if
the trouble goes away.

If not, have the XP CD in the drive, do a Start - Run and run
SFC /SCANNOW
to refresh system files; if that does not do it get the RAM checked
 
from the said:
The non-paged area is a section of RAM that is used by code so important
that it may never be dropped out into the pagefile by virtual memory
management. So it is mainly core system code. This is very unlikely to
have errors such as indicated by this message, so it usually indicates
hardware trouble - bad RAM or corruption of the code on the hard disk.
But there are a few third party things that push themselves into this
area - I understand some aspects of Norton SystemWorks do so, so if you
have installed anything of that sort, I would uninstall it and see if
the trouble goes away.
Click to expand...

Bad video drivers used to cause this sometimes (but I haven't seen it
for a while, with the latest Detonator / Catalyst driver sets).
Otherwise I agree with you - Systemworks, and anything else in the
'startup' folder(s).
 
Back
Top