hey, I'm working on a friend of a friends computer and during boot i get the error "PAGE_FAULT_IN_NONPAGED_AREA". BSOD ftw!!!! I've read ones that say that it would be a hardware issue. I haven't found any problems with the hardware. So what would be a quick fix to do (if there is one) on it such as from the command prompt. It's for his business and he's in desperate need of help right now but I'm a little lost on this subject.
He doesn't have anything backed up and it has information on it and I can't get into it but in safe mode and I still cannot access files that he needs (aka make a backup of his accounting information and back that up itself).
Any help or suggestions would be GREATLY appreciated.
Want to enjoy fewer advertisements and more features? Click here to become a Hardware Analysis registered user.
It's a memory problem. Usually associated with OC'ing, or failing hardware.
This Stop message occurs when requested data is not found in memory. The system generates a fault, which normally indicates that the system looks for data in the paging file. In this circumstance, however, the missing data is identified as being located within an area of memory that cannot be paged out to disk. The system faults, but cannot find, the data and is unable to recover. Faulty hardware, a buggy system service, antivirus software, and a corrupted NTFS volume can all generate this type of error.
This Stop message usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, either main memory, L2 RAM cache, or video RAM). If hardware has been added to the system recently, remove it to see if the error recurs. If existing hardware has failed, remove or replace the faulty component. Run hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owners manual for your computer. Another cause of this Stop message is the installation of a buggy system service. Disable the service and determine if this resolves the error. If so, contact the manufacturer of the system service about a possible update. If the error occurs during system startup, restart your computer, and press F8 at the character-mode menu that displays the operating system choices. At the resulting Windows 2000 Advanced Options menu, choose the Last Known Good Configuration option. This option is most effective when only one driver or service is added at a time. Antivirus software can also trigger this Stop message. Disable the program and determine if this resolves the error. If it does, contact the manufacturer of the program about a possible update. A corrupted NTFS volume can also generate this Stop message. Run Chkdsk /f /r to detect and repair disk errors. Restart the system before the disk scan begins on a system partition. If the hard disk is SCSI, check for problems between the SCSI controller and the disk. Finally, check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver causing the error. Disabling memory caching of the BIOS might also resolve it. For more troubleshooting information about this Stop message, refer to the Microsoft Knowledge Base at http://support.microsoft.com/support.
Ok, I've seen that explanation yes. Thus I used a program to check the integrity of my memory (which is what I came to believe the program was used for) and it was called memtest86 I believe. When that process was completed, it came back as everything passing with 100%. So would that error message come up from a different problem other than memory?
Can you provide the actual stop code, this may help in isolating where the issue lies.
In many cases the NONPAGED AREA portion of this error indicates that a peripheral device that utilizes DMA or RESERVED MEMORY space, or the drivers or memory mappings are causing conflicts or there may be a failing piece of HW.
Given that you get this every time, and you've actually been able to run memtest, and can get into safe mode would seem to indicate one of two most likely culprits.
1. Bad Video Card Memory. Under safe mode VGA setting most of the GPU Memory is not addressed or accessed. Swap out the GPU for another like unit.
2. Bad Driver configuration or update. As you can get into SAFE Mode using the core system basic drivers, there may be an issue with a recent driver or system update.
Ad Astra Per Aspera
(A rough road leads to the Stars)
We all know what we know, and everyone else knows we are wrong.
System Specifications in BIO