Blue screen error message
page_fault_in_nonpaged_area

hank, July 2008

The other answer from techangel.co.uk

The probable cause of it is Memory issues specifically with your RAMs. If you are mixing your RAMs with different types of brands/modules or filling all Memory banks full, try removing one Bank or the odd one(s) out.
Another related cause is overloading of the PCI BUS or IRQ sharing esp in an Athlon/VIA setup. Study all the IRQ's assignment of your machine and avoid sharing whenever possible. I have seen and personally experienced these errors myself and the problems goes away after avoiding IRQ sharing/conflicts.
Another interesting note Ive discovered if youre running WinXP, it is ideal to install the PCI devices by filling up the 1st PCI Slot in sequential order. This means if you have a SCSI Card, Sound Card and a Network Card, arrange them in the sequence of PCI Slot 1= SCSI Card, Slot 2= Sound Card, Slot 3 & 4= Blank and Slot 5 = Network Card.

Phil, July 2008

Found on techangel.co.uk:
I was helping a friend upgrade the RAM on his old HP Pavilion desktop. He had 64mb, and had upgraded to Win2K Pro, and it was very slow. I put a 128mb stick into the empty slot, restarted, and got the BSOD "Page Fault in Non Paged Area". I took out the RAM, restarted, set the min & max virtual RAM sizes to 0, shut down, reinserted RAM, and restarted. Windows rebuilt the page file (virtual memory) and resized it to 20mb. It will give you an "Insufficient Virtual Memory" error on startup, but if you keep clicking OK, it should allow you to restart the unit. Afterwards you can set the min & max page file size to 2x the total amount of RAM.

I've found several others and will post them shortly...

Phil, July 2008