BSOD PAGE_FAULT_IN_NONPAGED_AREA - RAID0 Drives

GodMac · 19 Mar 2015 at 11:31

I get the error on my sons PC that is an AMD 8-core with dual SSD 120Gb in RAID0 config. Its been working fine and suddly started doing it in boot up 10 seconds into Win 7 x64 starting.

I've tried the auto repair with windows but because the OCZ 120Gb drives are in RAID0 config I need to load the RAID drivers to recognise the windows OS. The drivers start to load and then BSOD with the same message. I can't get to the memory dump until the system can access the OS, but it BSOD's before the OS is accessible. Therefore I can't see if its a driver that is causing the problem.

I've tried the load the OS in safe mode but again 10 seconds into boot up of the Win 7 start up (pulsing windows on the black back ground) the BSOD happens again.

I've swapped memory over and changed slots, same thing happens.

Is there any way to get to the OS so I can get to the windows\minidump directory? Or is there a recent driver release from Microsoft that is screwing systems up with the same error?

Thanks in advance!

ED209 · 19 Mar 2015 at 12:00

I think this error relates to memory

take out all the sticks and re seat them all.

if this doesn't work run memtest or try with just 1 stick of ram in as it maybe a faulty module

Emlyn_Dewar · 19 Mar 2015 at 12:01

Unsure of any Microsoft update of late that could cause it, but you should see the RAID if you boot into a Linux distro liveCD?

GodMac · 19 Mar 2015 at 12:52

I did swap the memory around and put one stick back in at a time but I've not done a memtest. I'll take the memory out of my system and put that into my sons to see if that runs any different. I've also got a copy of knoppix I can boot the system up with to see if I can acess the dump file. Thanks.

GodMac · 20 Mar 2015 at 10:29

OK, so the problem is sorted, this is what I did so others can use the process:

Firstly to eliminate the memory fault I took the two DDR3 sticks out of my system and put them in place of those in the suspect system. Same problem occured on boot up so was not a memory hardware problem.

1, Downloaded a copy of Hiren's Boot CD (its a little old but still works great)
2, Booted the system from a USB live version of the Hiren's BCD I'd created from the ISO with Rufus
3, Booted into HBCD and ran Mini Windows XP. As this is a Linux based system it loads the drivers so my two SSD drives that are in RAID0 can be accessed as one C Drive.
4, Nativigated to C:\Windows\Minidump to access the BSOD memory dump. However, there was nothing there! Which was strange.
5, Did a google search to identify why the memory dump was not there and noticed a post where the same thing had happened with someone else which pointed at a failed Microsoft patch update
6, Using CHKDSK in the menu I check and repaired a file corruption
7, From HBCD Menu went into CCleaner and did a system clean and a registry repair. 14 errors in registry were repaired
8, Came out of everything and rebooted the system as normal
9, system booted passed the original BSOD point but got to the User account screen and BSOD again.
10, Rebooted the system and pressed F8 to get to the advanced boot screen options. Chose Safe Mode without network drivers.
11, System started up OK. So I was now more confident it was not a hardware issue.
12, Did a Google search for any issues relating to BSOD from Microsoft patch updates in March 2015.
13, Noted one patch that was released (KB3033929) that caused a Reboot Loop on a Windows 7 systems. Identified that the patch was not relevant to my system so uninstalled it.

http://krebsonsecurity.com/2015/03/ms-update-3033929-causing-reboot-loop/

14, Rebooted the system as normal and all when through absolutely fine.

I suggest if you have this patch installed. Check whether you need it and uninstall if you don't. Hope this helps.