[BSOD] Page fault in non-paged area on boot, please help!

jimmychangas

Honorable
Jul 19, 2013
13
0
10,510
So I have this rig that I built myself back in March 2014, here are the specs:

Intel Core i7-4770 (non-k version)
ASRock Z87E-ITX
16GB Kingston HyperX 1600Mhz Low Profile RAM (2 sticks of 8GB)
Samsung 840 EVO 250GB SSD
Kingston HyperX 3K 120GB SSD
Western Digital Green 1TB 7200rpm HDD
Nvidia GeForce GTX 780 Ti
Windows 7 Ultimate 64-bit

Here's the set up: The Samsung SSD serves as the C drive, containing the OS. The other 2 drives are just for storage purposes.

The PC ran fine and superb from day one. I have a free version of Avast! antivirus installed just to monitor things out. It wasn't until a couple of days ago when I came back from work and proceeded to power on my PC as usual, and bam, this BSOD greeted me. To be specific, upon hitting the power button, the PC got past the BIOS, it also got past the "Starting Windows" screen, but right before it gets to the login screen this BSOD appears, and it's the "PAGE FAULT IN NON-PAGED AREA" type.

At the time I was utterly dismayed, because before this BSOD appeared I have had zero problems with this PC. Several hits of the reset button later only have I concluded that I have no chance of getting past the BSOD and hence no chance to boot normally into Windows. Attempts to boot into safe mode and loading the last known good configuration got me nowhere either; the BSOD just appears right before the login screen. I therefore popped in the Windows 7 installation disc and hoped that performing a System Restore would solve the problem. However, I was told that there weren't any restore points to restore from.

I therefore performed a clean reinstall of Windows. From there on, things seemed to have gotten back to normal, as I was able to boot normally into Windows, install the essential drivers and software, and play games. I even installed a new antivirus, which is BitDefender. I should note that I only reformatted the Samsung SSD; the other two drives were left untouched.

However, just two days after the clean reinstall, the BSOD returned (the same BSOD as mentioned above), to my horror. I had the PC restarted prior as I was configuring which software to run during boot in msconfig, and after I hit the "Restart" button, the PC never made it to the login screen after the reboot. This time however, I was able to launch startup repair and managed to perform a successful system restore, and I was able to boot to Windows after restoring. For the next 5 to 6 hours using the PC, it ran just fine without any issues or BSODs. It was only when I shut down or restart the PC the BSOD appears again, and for every instance of these BSODs I was able to rectify by performing System Restore, and boot normally to Windows after.

I've therefore done some Googling about the BSOD, and learnt that it is associated with RAM. But if this was to be a RAM problem, I would have gotten BSODs when I was using it midway. This BSOD only appears during boot up, and a System Restore is able to temporarily solve the problem. I'm just baffled. Any help would be greatly appreciated. Thanks in advance!
 
Hello... All my experience with BSOD is due to a Hardware communication, interrupting between the MB and Windows.
1) Make sure you have no un-happy hardware drivers in your "Device Manager"... No Yellow or Red icon indicators
2) Clean all card/stick edges with rubbing alcohol... And Re-insert cards.
3) Inspect and clean all DATA and Power connections... to your Hardware and MB.
4) Verify all devices CPU/GPU/MB temperatures are with in Normal operating temperatures.
5) Verify your Power Supply 12Vdc has enough current , To operate your Video Card and CPU, at the Performance setting you are using.

A quick fast test, would be try one stick of Ram at a time.

A quick fast test would be to Boot without your Graphics Card using the IGT of your CPU.
 

jimmychangas

Honorable
Jul 19, 2013
13
0
10,510


Alright I will try to perform these steps, thanks for your swift response.
 

jimmychangas

Honorable
Jul 19, 2013
13
0
10,510


I honestly didn't know that. That could be it. Let me try to uninstall these updates and I'll get back to you. Thanks for the swift response.
 
Hello... As I have always stated... " If it isn't broken Don't try and fix it! " Updates can take a smooth running machine into a Mess of problems. For example... only use the Hardware drivers from your Card/Hardware Maker, Microsoft hardware drivers updates have always cause problems with me.
 

jimmychangas

Honorable
Jul 19, 2013
13
0
10,510


duly noted, thanks!
 

oggmeista

Distinguished
Oct 11, 2008
18
0
18,510
People keep trying to directly associate this error with hardware, but from my experience thos probably is not the case....

I just had some malware/adware/virus issues for a second time in 2 months, and both times I got this error after running anti virus/malware/addware software and then using the system restore function...

The machine then BSOD 4-5 times with this same error, (although not always the exact same location) before eventually it stopped

Personally I believe this is probably more likely caused by an unexpected exception, probably in the windows registry, so don't automatically assume you have bad memory or PSU etc, replacing those may well just be a big waste of money.....