• BSOD booting from disk: "PAGE_FAULT_IN_NONPAGED_DATA"
    5 replies, posted
I keep getting this annoying error whenever I boot from my Win7 disk (usually to repair my obnoxious computer's system which loves to give me problems) The error is "PAGE_FAULT_IN_NONPAGED_DATA" Windows 7 64-bit, AMD Phenom (quadcore can't recalls the specs now very well), 4GB of RAM, and an ATI graphics card which I can't remember the number of now. Sorry I can't be more specific but all I find from it is related to some sort of issue with faulty hardware installation (which is strange, because I haven't installed any hardware lately?) Also; occasionally when it doesn't BSOD me trying to start up the disk, it won't go past the point where it gives the error and lets you choose between memory diagnostic and windows setup.
Try testing the RAM by removing one stick, and try to start and then put it back in, and take the other out. Otherwise, right down the error code should be something 0x00000* or that alike.
I removed one stick (the primary one :ohdear:) and it booted just fine, but before I turned it off I scheduled a memory test and put the stick back in so I could see if something's wrong with it. I'll likely post the results when it's done.
Update: (sorry to double-post!) But memtest seemed to have no issues and the computer booted up just fine :psyduck: I'm doing a chkdsk /f /c to see if there's anything on disk like [url=http://msdn.microsoft.com/en-us/library/ff559023%28v=vs.85%29.aspx]this[/url] suggested.
Did you use memtest86+ ([url]www.memtest.org[/url]) or did you use the garbage one on the Win 7 install CD? The Windows memtest is terrible and doesn't tell you anything. I've had it say completely bad memory was good before, it's awful. chkdsk is equally terrible, it only checks the file system, not the underlying disk. Run a program like HDD Scan: [url]http://hddscan.com/[/url] And check the surface of the entire drive for readability.
It really sounds like on stick is bad, and bohb is right.
Sorry, you need to Log In to post a reply to this thread.