Computer BSODing randomly; PAGE_FAULT_IN_NONPAGED_AREA

[Randomrocket]

Hey guys, my computer started BSODing a while ago when I got home from school for xmas break. I thought something had gotten jostled around in the car or something and it happened only twice, with about a week in between so after the second time, I opened up the case, dusted it out and made sure stuff was plugged in properly. Then about a few days later it BSOD'd a third time. This time, the PC failed to load past the windows logo before BSODing again. It wouldn't boot up. I thought I was screwed because my back up hard drives are at the school for winter break along with my repair disc and stuff. After running CHKDSK, it booted up.

My PC has four hard drives, two 2TBs for my personal data, and two 750 GBs for the OS and programs. both sets of hard drives are set up in raid1 configurations for redundancy. I'm wondering if the raid setup is bad making it harder for Windows 7 to run. I know it's slower for read/write, but I'm a bit paranoid about losing my the videos I have created and stuff.

I'm posting the log here from this computer and I'm scared to turn it off again. I remember one of the BSODs being a PAGE_FAULT_IN_NONPAGED_AREA or something and I think that is a hardware error. Please look through the logs for me and let me know what is killing my machine before it BSODs again and I lose all of my data.

Thank you so much,

Silas

 

[Arc]

Hi Randomrocket.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If memtest86+ does not show any error, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions.
______________________________________________________________________________________

BugCheck 50, {fffff900c2bdb000, 0, fffff960000c5f23, 0}


Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!draw_clrt_nf_ntb_o_to_temp_start+7b )

Followup: MachineOwner
------------------------------------------------------------------------------------
BugCheck 3B, {c0000005, fffff8801121d007, fffff8800a54e080, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

 

[Randomrocket]

Okay, thank you. I will test the RAM when I get home again.

Thank you

 

[Randomrocket]

Okay, I am in a bit of crap with my machine now. I ran the memtest and it didn't find any errors for 8 passes. So then I figured that it might be because Windows 7 doesn't like to be run in a raid 1 set up. I have 4 hard drives, two 750Gbs for the OS and two 2Tbs for my stuff. So I decided to break the raid that was on the 750s so my OS would no longer be in raid. I used the Windows repair disc and removed the mirror and tried booting up again. Only now, I have two copies of Windows 7 on each disc. I want to format one of the drives to use it for stuff but for some reason it lists the C: drive as the system and the J: drive as the crash dump, and boot and stuff. So I can't wipe either of them. I would like a way to move the boot and stuff to the C drive and then format my J but I can't seem to find a way.

This brings me to my next problem. My PC is BSODing on boot now. It was working fine last night after I broke the raid but now it doesn't seem to like me. The Windows repair disc finds both installations of windows but when I try running bootrec, scanos doesn't find any installations. it's weird. I can't repair anything for some reason.

Any ideas or suggestions?

 

[Arc]

If you want to change the storage controller mode on which windows is originally installed, you need to do a clean install. Otherwise windows will not boot.

 

[Randomrocket]

So a new install is my only option? I'm fine with it, but it's just gonna be a pain reinstalling everything and would rather see if I can fix what I already have.

 

[Randomrocket]

I am unable to reinstall Windows. When I load up my windows 7 disc, it gives an error message that says something along the lines of memory could not be referenced and to restart to try again. Sometimes it'll even bsod at this point due to memory_management. Is ram the actual problem? Why didn't memtest find anything?

 

[Arc]

At least it is determined that the issue is with either the RAM (strange that memtest did not detect it), or HDD or motherboard.

You have a chance to minimize the alternatives. Get a pair of known good RAM compatible to your board. SWAP your existing RAM with those and see how it goes. Is it still the same?

Also run a Short Test using Seatools for DOS. Does it pass?

If doth the answers are positive, the culprit is the motherboard.