PAGE_FAULT_IN_NONPAGED_AREA

Shady

Limit Breaker
Adventurer
Joined
Aug 5, 2004
Messages
537
Location
NYC
Linkshell
The Outsiders
Recently I'm getting this blue screen error message Page_Fault.. I did a quick google search and come up with the possible explanations: faulty RAM, faulty Kaspersky protection, or unknown general hardware failure. I ran a CHDISK, and everything is operating as it should, so I don't believe it's the RAM or a missing/corrupt DLL file. Does anyone have any clue what I could do to fix this before I re-install windows? I'd rather not go through that hassle. Thanks,

-Shady
 
Have you tried removing the harddrive and booting it from a working tower? That should let you know if it's a problem with the hardware or the contents of the harddrive.
 
Thing is my computer works.. for a time before I get the blue screen. Like right now, it's been on for a solid 30 minutes, it might go for another couple hours before I get the blue screen. Doesn't that rule a faulty hard drive out of the picture? It doesn't go straight to blue screen. The error is almost at random it seems..
 
That doesn't necessarily rule out a faulty harddrive. If you haven't already I'd start backing up anything on your harddrive that you cannot afford to lose.
You're probably going to have to reformat, but before you wipe everything you might want to try swapping out your RAM and checking to see if the same problem occurs when you stick the hdd in another tower. The other thing it might be is the NTFS file system getting corrupted. I think there are a handful of programs floating around that can help with that but you'd have to go digging to find them.

Once you get this thing all squared away you might want to look into grabbing some disk imaging software. It's absurdly useful for recovering everything. I suggest you find yourself a copy of Hiren's Boot Disk as it has quite a few disk imaging programs on it along with a bunch of other tools which may or may not help you identify where your current problem is.
 
this seems to be an issue lately with many people. im not getting bsod. but, my system has been rebooting for no apparent reason. not only that, but its not all time time either. most of the time mine would reboot within a minute or two of being on my desktop. i searched around, had seen people get advice of using a program called "whocrashed". it basically tells you which program is causing the crash. that is, if it is software that is causing it.
 
Interesting.. here's what it says:

Crash dumps are enabled and no valid crash dumps have been found on your computer. In case your computer does experience sudden reboots it is likely these are caused by malfunctioning hardware, power failure or a thermal issue. To troubleshoot a thermal issue, check the temperature using your BIOS setup program, check for dust in CPU and motherboard fans and if your computer is portable make sure it's located on a hard surface. Otherwise it's suggested you contact the support department of the manufacturer of your system or test your system with a memory test utility for further investigation.

-- Maybe it's just dusty in there.. gonna clean it out, will update in a couple days after extensive dusting --
 
if that is the case, sounds like it may just be a hardware issue?
have you run a memory scanner?
 
Thing is my computer works.. for a time before I get the blue screen. Like right now, it's been on for a solid 30 minutes, it might go for another couple hours before I get the blue screen. Doesn't that rule a faulty hard drive out of the picture? It doesn't go straight to blue screen. The error is almost at random it seems..

if that is the case, sounds like it may just be a hardware issue?
have you run a memory scanner?

Yup I'd check that, it rings like a memory problem to my hear. I'd try swapping the RAM (if you have access to extra RAM of course) just to see if it continues to do bsods. If there is no bsod, I'd try each stick individually to isolate the faulty one and replace it. Still, do yourself a favor and make a backup just in case lol. Don't forget to unplug your computer and to ground yourself before you start playing with your components :).
 
before going into the computer, run a memory test. if it comes up with faults, then i would go about what trib is saying. also, if it doesnt come back with errors when you run the mem test, then you may also want to isolate the computer from all of the extra periphs, IE printers, etc
 
Back
Top