Hey everyone...

I got bored last night so I decided to mess around with my computer a lil bit. I got the latest version of Cheepoman bios and stuck it onto my computer: installed fine. Went into the bios and messed around with the settings some. Tried setting it to 138/138. Worked fine and I got into Win2000. After a lil while, my comp just rebooted, so I figured I had set it to high and I put it down to 133/133, where it ran stable.

Now, I'm getting this BSOD:

Page Fault in non-paged area in NAVAP.sys

I've been searching around for an answer for this. Microsoft said it could be faulty RAM and I saw one or two other reasons after I searched on google.

When I get home today, I'll probably try using one RAM stick at a time. My bios still reads it as 512 meg. (Have two sticks of 2100 DDR at 256 each) Additionaly, I'll probably put the latest bios from the ECS site back on.

Anyone ever have this problem before, or know a remedy?

Thanks for any suggestions!
-Tom S.

I'm sure I'm not alone in thinking that the first line there says it all, Banshee If everyone was 100% honest, I wonder how many threads here (and support calls I have to field) would begin with that statement?

Have you tried resetting the BI/OS? That'll get rid of all those settings you changed when you “Went into the bios and messed around with the settings some”.

I actually traced the problem to it being a heat issue. I had the side of my case on at that time. Took it off... been working ever since. (Although, I can't run WinMX anymore without my computer rebooting now... weird)

-Tom S.

I could be "Way out in left field", but isn't the file "NAVAP.SYS" the Norton Anti-Virus Auto Protect file? If so, a re-install of Norton Anti-Virus will probably repair the problem.

I have been getting BSOD page fault in non paged area, IRQ not less than equal and PFN file list corrupt.
I have identified the errors as being caused by a 256 stick of "replaced under warranty" Crucial DDR 2100 ram. RAM checks out as O.K! Running on just 256 of another brand I am getting no further errors. Hope this helps

That file does sound like the Norton. Personally, I haven't used any kind of virus protection software for more than 3 years and haven't had any problems since I stop using them. Actually I get more peformance I believe not using that software. Its always running in the background :-p

Casanova
Happy Gaming

I'm trying to build a computer. 1st attempt. I can't get WinXP to load because of the same BSOD error. I've read that it could be the placement of my graphics card. I'll try reseating the mem and the PCI to see if any of that'll fix it.

Athlon XP 1800
ASUS A7V8X-X
PC2100 256 MB
80 Gb Harddrive

This error is usually caused by memory problems of some kind-try using just one stick or swapping to different slots.

NAVAP.SYS is a Norton file, but the memory errors are probably occurring in the area in which the NAV data is loaded.

check your ram with this ----> http://www.goldmemory.cz

Maybe were on to something here.

Most people seem to agree that its a memory problem. I actually heard Crucial DDR 2100 ram mentioned. That is the same ram that I use. Perhaps its something with this spacific type of memory. Anybody else using Crucial memory have this problem?

To be more spacific on my system -
Its a game server running on Windows 2003 Server Enterprise
Dual Processor Athlon MP 2000+ (Asus A7V266-D Motherboard)
2 GB all Crucial DDR 2100 Registered ECC (3 chips - 1gb, 512mb, 512mb) (supposed to be the best stuff, pfft)
PNY Geforce 3
Linksys internal Network card
Western digital 40gb
Maxtor 80gb
Memorex internal burner

Maybe if we can find common ground on our systems then we can see if its a conflict or simply just the memory.

I have noticed on ALOT of boards that about 95% of the people haveing this error are all running pc2100 ddr (same goes for me) I am Thinking The type not brand is the problem . Although Some brands arent all that great anyway



MSI kt3 v
512mb PC2100
AMD Athlon 2200+
Radeon 9000 64mb

Hey, I have had similar issues with my system yet my memory is pc133, though I've yet to try the removal of my two 256 memory modules. My problem is this, after removing various peices of hardware or softwares, how long do i wait untill I can say that the problem is fixed? Is there a way to "prompt" the error to occur?


XP Professional
512 mb sd ram
1.1 gig AMD Athlon

Hi

As a hardware engineer for over 5 years now Ive encountered this problem only with WinXP. The reason behind this is due to one of two main causes.

Windows XP and most NT/2000 kernal OS by MS come complete with a variety of hardware safety measures designed to keep a business PC in top shape by stopping problems before they occour. Unlike Win98/ME/95 the NT kernal has a BSOD (Blue screen of death) message system that is meant to give the admin all the info needed (as if).

Now as I said there are two main causes of the following messages

Page Fault Found In A Non Paged Area BSOD's
Memory Dump BSOD's
IRC BSOD's

Now the first thing to do is make sure that EPROM CACHE is disabled in the BIOS, When this is enabled windows gets confused and will promptly display the BSODs randomly, if however this doesnt work or as in most boards you dont have an EPROM cache then its likely to be the RAM at fault

Now heres a quick test we run at work. First off power up the PC with the side panel on but unscrewed. Use normally until you recieve the BSOD. as soon as this appears turn pc off immediatly and see how close you can move your hand towards the ram before you feel any heat coming off of it. The closer you get the better! If you can feel heat from the ram more than 3cm away then its a heat problem.

Now if this is fine its your ram stick, check theres no dust on the ram that could be linking pins together and the like and ensure all sticks are properly inserted into the board. Also make sure you fill the slots up in order as in slot1, slot2, slot3 !NOT! slot3,slot1,slot2 etc etc. If again this fails then in my experience its about 90% sure your ram stick has gone up the shoot.

I must also add this is most common on DDR sticks, both PC2100 and PC2700. Ive heard of PC133 doing the same but only when the RAM gets aged. If youd like any more info just e-mail me at Mike@Vapournet.com


Best Of Luck
Mike

Hi ... I am facing the same problem with "Page fault in non-paged area"! and something BLUESCREEN saying the my win32.sys are having error ... and then I force to restart! lost some of my unsaved works

my system was running fine in the last 10 months or so!

my AMD Xp 1800+
1GRAM DDR400 ...KingstonRam
ASUS A7N8X deluex motherboard
Ti4600 A250 Ultra graphic card with 128RAM
40GB of Segate HD with 7200RPM

so... now I don't know what to do ... cause I tried to format my XP professional version.. and reinstall .. but the installation also freeze on me! but lucky I am able to install it back on. but the "BLUESCREEN" with "Page fault in non-paged area" still show UP!

what happen... can anyone tell me what is going on!
I tried to download latest Xp updates already! is it my BIOS for motherboard need to upgrade!?

Hi Guys,

I have started having this same error happen to me just yesterday - but it is since I installed an Adaptec 29160N SCSI card in the XP machine(at least I thought it was due to this card, although having read most of the replys I am now not so sure).
But the strange thing is the error I get is not linked to a DLL, SYS, or any other file.
Also when I start up in Safe Mode the computer runs fine(if this was an error caused by faulty/overheated RAM surely I shouldn't even be able to start at all?)

Any thoughts?

Michael,

Just wanted to say thanks for your advice here...

I've been struggling with these BSOD's on my PC for about a month, and have completely resintalled XP 3 or 4 times.

I ran GoldMemory and as a result found one of my 2 sticks of DDR Ram was a bit poorly to ay the least (6 pages of errors inthe first 15 seconds!). I removed the faulty stick, and my PC now runs like a dream again!

Thanks again for geat advice

Ok, so i've had the same problem. I just got HALO the other day, and it worked fine for a few days. But, after a few hours of play time, i'd get the bsod PAGE_FAULT_IN_NON_PAGED_AREA or BAD_POOL_CALLER. Heat apparently may be an issue, or a bad ram card. I have a 512mb of pc2100. Any clues as to what a bad pool caller is?

WinXPPro
512mb pc2100
Radeon 9000 pro
60g

Well,

I have an asus A7N8X Deluxe PCB 2.0,
2x512 MB PC 3200 RAM
Athlon XP 2800+.

I have the same problem, BSOD.

Reading the posts here the Page Fault in non-paged area happen only when there are 2 banks of memory that the motherboard dislike.

My memory is configured in single channel mode, it cannot be used in twin mode (not compatible) and I think that if I pull out a bank of mem from the mobo the problem will disappear...

Ah I got also a 29160 scsi controller, but i don't think it's it the problem...

Anyone have solved this issue?

Hello everyone,

I thought I would shed some light on this whole memory issue. It is a memory issue by the way. Anytime Windows says there is a PAGE or DATA error then it is a memory issue.

Windows reports if there is any error in the transfer of data to or from the 1)Harddrive, 2) Memory or 3) SCSI or IDE controller. Primarily errors such as these can occur if Windows cannot write to the swapfile. This condition would present a typical hard drive timeout error for Windows and thus throw a flag or BSOD and kill all processes to prevent damage to the hardware or from overwriting files on the hard drive. This is a standard memory error protection feature in XP.

I figured out that my BSOD KERNEL INPAGE DATA error was due to my Promise PDC 20276 RAID setup on my IDE controller. But it was a faulty harddrive that was ultimately causing the error.

To troubleshoot I used a removeable hardrive setup on IDE1 in the same computer with the exact same setup as my RAID with WIndows XP and never noticed any problems wiith the memory or video card. The computer ran for days without crashing no matter what I threw at it. As a result I logically narrowed the problem down to my RAID hard drives on my Promise IDE RAID controller. I hear some people are running SCSI RAID from previous posts. It could be your hard drives are going bad. I would check them. I use the Western Digital diagnostics and found multiple unrecoverable errors on one of my drives. I am sending it in and getting a new one.

Check your harddrives, memory and video. These are the primary causes of such errors. And remember - a hard drive is treated as memory just like your DDR RAM is in Linux and XP.

I've been getting these since I built my wifes machine - XP2800, Gigabyte GA7N-400pro2, 60Gb WD hdd, 512 Mb pc3200 RAM. The errors occur at any time, often while doing something non-intensive like playing mp3's in Media Player. I have run memtest86 for 8 hours with no faults, and tested the hard drive with Western Digital's utility with no problems found. CPU temp is about 47c, so shouldn't be a temperature issue. Windowa XP pro has been reinstalled (after complete reformat ) to no avail. I've tried a different stick of RAM, and swapping memory slots, but no luck there. I'm starting to think the fault must be on the motherboard or the CPU itself, although I don't see why this wouldn't show up during memtest. Any help would be welcome !

I had the same problem:

but since i've clocked my mems from 400 to 333 it's all disappeared...

I think it's because the memory I have are not what my a7n deluxe 2.0 like.


Kind Regards