• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 990
  • Last Modified:

Vista & PAGE_FAULT_IN_NONPAGED_AREA

Good evening/good morning/good afternoon experts.

I have a friends laptop (Gateway MX8734) running Windows Vista HP 32bit and I am trying to resolve a "PAGE_FAULT_IN_NONPAGED_AREA" BSOD that is happening from every angle. Her story is she was working on some things on the couch and her son being annoying popped the DVD drive in and out a few times putting the disc in and taking it out and a few minutes later the laptop started running "weird" and things weren't working so she restarted the computer and since that point it will not successfully load Windows without a PAGE_FAULT BSOD. There is no file or driver listed just PAGE_FAULT_IN_NONPAGED_AREA, the normal BSOD text and a stop error starting with 0X00000050.

When the laptop is started it goes right to a black & white "Windows Error Recovery" screen with two options; (1) Launch Startup Repair (recommended) and (2) Start Windows Normally. Both of those result in making it to the Windows loading screen with the moving green bars and then results in the PAGE_FAULT BSOD. If I press F8 to get to the other start-up options every option will cause the PAGE_FAULT BSOD around the same time. Also, if I try inserting and booting off of the Vista DVD that came with the laptop, a Vista Business DVD of mine, or a retail Windows 7 Professional DVD of mine they will all result in the PAGE_FAULT BSOD as well. Same with the Windows Vista Recovery DVD from Microsoft.

I've spent quite a bit of time reading up on the PAGE_FAULT BSOD and usually it sounds like a software issue but some appear to be bad RAM or hard drives. I have tested all the memory with Memtest86+ and tested the hard drive with GRC SpinRite and both result in no issues at all. I also tried running the system with one stick of RAM and then the other; and then in different slots but all still result in the same BSOD.

I am at a loss here and I don't know what to try next. I have never seen a system refuse to boot off of the different versions of media like this and refuse to start up into some sort of safe or recovery mode. Any suggestions on how to troubleshoot further would be greatly appreciated. I will only be up for about an hour yet this evening. This thing has done me in for the night.
0
J-Reese
Asked:
J-Reese
  • 7
  • 5
  • 2
3 Solutions
 
J-ReeseAuthor Commented:
Well I might have figured out something else in a last ditch effort for tonight.

I have a spare 2.5" SATA drive in a USB enclosure here so I took it out and put it in the laptop and tried the same Vista disc that came with the system and it booted right up and was ready to do the install. Same with my retail Windows 7 disc. So thinking the other way around I thought I would stick the Gateway hard drive in my now empty USB enclosure and run a checkdisk from my Windows 7 desktop but about 10 seconds after plugging in the USB enclosure with the Gateway hard drive in it; Windows 7 detects it and starts to install the drivers for it and then throws the same exact PAGE_FAULT_IN_NONPAGED_AREA BSOD but on there it actually listed "NTFS.SYS" as the problem. So now if I try to plug in the USB enclosure with the Gateway hard drive in it or leave it in when I start up my Windows 7 system it just blue screens like the laptop.

I am assuming that the NTFS.SYS file is in relation to the file system on the Gateway hard drive. Could it be that the NTFS file system driver somehow got corrupted on the Gateway hard drive? If so how can I try to correct it - or better yet how in the heck can I get to it since Windows wants to blue screen every time it tries to access the file on the drive?
0
 
John GriffithCommented:
NTFS.sys is a Microsoft driver - for the NTFS file system.  Usually when seen in a BSOD, the bugcheck is 0x24 and indicates a potential problem with the hard drive.
I would suggest bypassing the Vista OS install & upgrade - just wipe the entire HDD to be used for Windows 7 with KillDisk, then insert the Windows 7 DVD and install Windows 7.  No need to have Vista lurking around for the W7 install.  After KillDisk, you're looking at 45-60 minutes to desktop.
KillDisk --> http://www.killdisk.com/downloadfree.htm
Burn bootable KillDisk CD-R with ImgBurn --> http://www.imgburn.com/index.php?act=download
Allow Windows Updates in - check for them yourself as well - www.update.microsoft.com
Regards. . .
jcgriff2
 
 
0
 
nobusCommented:
if you have a BSOD -  why don't you post the minidulmp for analysis here ?
0
Fill in the form and get your FREE NFR key NOW!

Veeam is happy to provide a FREE NFR server license to certified engineers, trainers, and bloggers.  It allows for the non‑production use of Veeam Agent for Microsoft Windows. This license is valid for five workstations and two servers.

 
J-ReeseAuthor Commented:
@jcgriff2: I am not looking to upgrade the system to Windows 7. Using the Windows 7 disc was a mere attempt at trying to see if the laptop would boot off of anything. I am trying to fix the system so it works again for my friend - hopefully without the need to reload the entire system. Also, there is data on the drive that needs to be backed up so I don't really care to format it until I can get access to it some way on some system without it throwing a BSOD.

@nobus: Well I can get a dump file from my Windows 7 system from when I plug in the Gateway drive via the USB enclosure but I can't get to the Gateway drive without Windows blue screening so I can't actually get the dump file off of the hard drive by any means for the system it is actually crashing on.

I will see if I can look at the dump file on my Windows 7 system that is created when I plug in the Gateway drive via the USB enclosure but I am not 100% sure that it is the same thing that is causing the BSOD on the Gateway laptop - although I am pretty sure. I would like to get the original dump file off of the laptop I just don't know how to get to it.
0
 
nobusCommented:
you can get to it much easier than that : boot from a live kNoppix cd, it let's you even copy to usb !
ftp://ftp.kernel.org/pub/dist/knoppix/KNOPPIX_V6.0.1CD-2009-02-08-EN.iso
0
 
J-ReeseAuthor Commented:
Well the good news is Knoppix worked like a charm and I can access the files very easily however; the bad news is for some reason there is no recent memory dump on the system. There is one on it but it is from back in September of 2008.

However, I took a look at the memory dump that my Windows 7 system produced when I plugged in the Gateway hard drive via the USB enclosure and it is attached below.

I'm not really that good with dump files but I do see some references to NTFS.SYS and I am not sure what to do next. Is there anything I can do in Knoppix to try and correct the file if it is corrupt or what would my next step be?
WinVistaBugcheckAnalysis.txt
0
 
John GriffithCommented:
I don't like the references to ntfs.sys, either - run chkdsk /r
The problem that I did not do a very good job explaining (apologies) is that once you inserted that Windows 7 disc and booted - the system may very well not allow the return to Vista without wiping the hard drive.  
Back up the needed data, then wipe the drive as I mentioned w/ KillDisk.  When formatted, insert the Vista DVD and re-install, then copy files over.  I have seen stranger things happen in Windows.  You may just find the HDD to be fine.  Booting with the DVD should not have given the same BSOD error as booting from the HDD.
0
 
nobusCommented:
well - at the end it says that it occured during a memmove ...which points to RAM
0
 
J-ReeseAuthor Commented:
@nobus: I ran Memtest86+ again today and left it go all day with 22 passes (I only did 5 passes before) and it appears to be fine. Also, in regards to the "memmove" references that is also preceded by "Ntfs!..." every time so I am still thinking that it is something to do with the NTFS.SYS driver.

@jcgriff2: How am I to run chkdsk when I can't get anywhere to have access to chkdsk either on the laptop itself or when trying to connect it as an external drive to a working system? It blue screens on everything. And I'm sorry but I do not believe that just by booting the system with a Windows 7 disc it turns the computer into an unusable system. That would be asinine.

To me it appears that it is something with the file system they way everything blue screens. On a normal boot Windows starts to load for a fraction of a second, tries to look at the file system and immediately throws a BSOD. Booting with an OS disc starts the process but as soon as it goes to launch the actual setup portion it looks at the file system on the drive to see what is on there and it throws a BSOD. Putting the drive in the USB enclosure and plugging it into my Windows 7 box it detects it and installs the driver for it but when it tries to look at the file system to see what is on there it throws a BSOD.
0
 
J-ReeseAuthor Commented:
Still bothered by the NTFS.SYS file I decided to test something and I figured out the problem - a corrupted NTFS.SYS file I believe.

I booted back up with Knoppix, made a backup of the current NTFS.SYS, copied a different NTFS.SYS from the recovery partition and put it in the necessary location then restarted the system and BAM! It actually booted and launched "Startup Repair". After going through a series of "repairs" it finally gave me a login screen and it appears to be functioning normally. I am running a chkdsk now and I will check the Event Viewer and a few other things tomorrow to see the final results.


0
 
nobusCommented:
did you ever try a system restore, when booted from the cd ? Here a guide :
http://www.bleepingcomputer.com/tutorials/tutorial148.html
0
 
J-ReeseAuthor Commented:
I couldn't boot from any media before without a BSOD... For some reason I always feel like I am repeating myself when I come here.

For future reference copying NFTS.SYS from the recovery partition and replacing the current NTFS.SYS in C:\Windows\System32\Drivers\ solved the problem and allowed me to get the system started again. After that running a chkdsk on the drive didn't find any errors but after normal maintenance and updating of the software the system appears to be running normally again.
0
 
nobusCommented:
j-Reese, what was the solution ?   just curious...
0
 
J-ReeseAuthor Commented:
Have you read my last two posts? I pretty much explained it twice.....
0

Featured Post

Configuration Guide and Best Practices

Read the guide to learn how to orchestrate Data ONTAP, create application-consistent backups and enable fast recovery from NetApp storage snapshots. Version 9.5 also contains performance and scalability enhancements to meet the needs of the largest enterprise environments.

  • 7
  • 5
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now