• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

"Page Fault in non paged area", won't boot, halp!

Skypix7

Senior member
Hi, I'm stuck with my home-grown system which has been stable and solid for more than two years:

my rig: Asus P4PE, 2GB DDR (1 GB x 2), Pentium 4 3.06, tons of hard drive space. Turned it on today like I always do, no new hardware, no new software installs recently, and got this message:

Address BFEFD335 base at BFEED000
stop: 0x000000x50 (0yE1AA7030, 0x00000000, 0xBFEFD335, )x00000001)
Page Fault in non-paged area
Address: BFEFD335 base at BFEED000
date stamp 3EDD1027-PQV21.sys

I've done everything I could think of to get the sytem to boot: pulled the memory sticks, board won't post, just long beeps. pulled one stick, won't get past bios. ditto the other stick. moved both sticks to 2 and 3 slots (in 1 and 2 now), won't post.

I can't get it to boot in last known config, or in any safe mode or command prompt mode.

I think it might be the memory, but thought I'd check the wizards here before I take it into the shop, or just get a new board and upgrade, which I may do anyway.

Thanks for any help...I don't have a local shop where I can get memory checked, or I'd do that next. Might it be anything else?

Jim
 
Sigh I hate to say it but I'm having the same issue here.

Although mine is a bit different I was moving computer today and go to boot up computer seemed to boot but monitor not working played arond with it and finnally booted up. I'm getting a Windows can not start error because of a corprupted system file. So I go to recpvery console to try and repair it or even install new xp but won't let me because I'm getting the same error you are.

Like you I suspect it's the ram but being as I have no DDR 2 computers anywhere else in the house I'm a bit out of luck on what I can do to see if it's the ram.

I'm out of ideas so if anybody has a fix to this for me and Sky I'd love to hear it.
 
Well it appears it's not the ram on my computer. Tried it in diff computer (didn't think ddr2 would work in old comp) and it works fine.

So I guess that means I need a motherboard and the ram slots have gone bad?
 
Well tried an old IDE harddrive and my comp bots up fine Sky. I'd try and figure out if it's the HD because it could be that going bad too before you run out and purchase some new ram.
 
thanks Naeeldar:

Wow, I hope it's not the HD, I've got lots of stuff on there I didn't back up. I've got the mem in for a check at the shop, when I get it back I'll take the next step. I've got four hard drives, but if it's not booting, it's got to be the C: drive, I would think.

It's a pretty new drive too, less than 2 years old.

Glad you got your problem solved, now it's my turn.
 
Skypix,

Your problem is a Norton issue (pqv21.sys). Read this thread ALL THE WAY TO THE END and find out how you can get back to normal, hopefully:

http://www.experts-exchange.com/Hardware/Q_21214156.html

By the way, Naeeldar, not to dismiss your issues, but posting your own separate issue in someone else's thread just mucks it up. Please feel free to post your own thread topic, where it will get undivided attention.


 
thanks Slikkster, I read it...although I don't have anything from Norton on my system, nonetheless, that .sys file is in there. I'll download the other things on my laptop and see if I can get in there, because I have yet to get it to boot past the first Windows screen.

Also, doesn't bother me that about Naeldar's posts, I felt that he was just trying to help by sharing his experience for me, and he did get me off thinking it was memory, which it shouldn't be as it's Samsung, top quality, and I've never had a single hiccup out of it.

Thanks again
Jim
 
Problem solved, thanks much to Slikkster! Following those links, I found out about a program called BartPE, which creates a bootable Windows GUI right from the disk, then you can go in and access whatever files or utilities you need to troubleshoot your problem. Fantastic!

I found out I do not in fact have a memory problem or a motherboard problem, but a stupid Norton file, as Slikkster pointed out, pqv21.sys, was the culprit.

What it was doing there is beyond me. Maybe I installed a trial of Ghost or something once, and the remove function didn't get that driver. Good old Norton screws up again, how has this company managed to stay in business all these years? I have never had a Norton program installed that didn't screw up my system somehow, sooner or later (usually sooner).

What I don't understand is why did this particular problem take so long to manifest? The only thing I can think of is I am low in my C: drive clear space, about 500 MB is all I have in it now, and I run Photoshop among other heavy crunchers and maybe the system starts looking elsewhere when it's running out of space. Time for a reformat and Windows XP.

Meanwhile, hats off to BartPE, it's a great utility for troubleshooting or just removing crap files that make your computer act like it's dead in the water.
 
Back
Top