Page Fault in Nonpaged Area BSOD (Among a few others)

Hi there!

Have you ran the MemTest86+ as Dave asked? If so post us the results. Make sure you run it 7 to 8 passes.

Try this free stress test: Free Software - GIMPS

Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.

Run SFC /SCANNOW Command - System File Checker

Glad your system is running stable.

Let us know if you have anymore crashes or questions.

It is very common for any memory test to pass a few times and then show errors, it's just the way electronics are, if you are still having issues I recommend to run memtest86+ again. Run it overnight for a full 7 passes.
I searched your laptop for similar issues and RAM problems came up, repeatedly.

Have you done any of the suggestions from this previous post?

Dave76 said:

Did you Run CHKDSK with the /r option?
Download and run Seatools on your HDD.
How to use SeaTools for Windows
Short Drive Self Test and Long Drive Self Test.
Post the results here.

Disconnect any external devices, you should have only the power cord connected.
Let us know what devices you had connected previously.

Run memtest86+,again, for a minimum of 7 full passes with all RAM cards installed, best to run overnight.
Stop the test if you get any errors.
RAM - Test with Memtest86+

Sys Event Log:
In reference to the Stop message 0x0000000A crash

Code:

Event[31761]:
  Log Name: System
  Source: Application Popup
  Date: 2012-07-25T14:59:47.000
  Event ID: 26
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: NickWilson-PC
  Description: 
Application popup: Windows - Application Error : The instruction at 0xff141197 referenced memory at 0xfda0bdb8. The memory could not be read.
Click on OK to terminate the program

These must be previous to un-installing LogMeIn, the driver is not listed now.
Event[31619]:
  Log Name: System
  Source: Service Control Manager
  Date: 2012-07-25T13:48:42.184
  Event ID: 7000
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: NickWilson-PC
  Description: 
The LogMeIn Hamachi Tunneling Engine service failed to start due to the following error: 
The service did not respond to the start or control request in a timely fashion.


Event[31618]:
  Log Name: System
  Source: Service Control Manager
  Date: 2012-07-25T13:48:42.184
  Event ID: 7009
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: NickWilson-PC
  Description: 
A timeout was reached (30000 milliseconds) while waiting for the LogMeIn Hamachi Tunneling Engine service to connect.

Driver issues:

Code:

GEARAspiWDM.sys Mon May 18 2009 - iTunes driver

This driver is still loaded in your system.
You are having driver related crashes, un-install iTunes for testing.
If this is found to be the cause, and I've seen it be the cause before, you can get a different app for music.

Code:

SABI.sys     Thu May 28 2009 - Samsung kernel driver

Did you update all drivers from the Samsung site?

Code:

WinRing0x64.sys Sat Jul 26 2008 - many different programs that center around the using of the WinRing libraries, found in Real Temp directory.

Are you using RealTemp to monitor the CPU temps?

Did you get CheckDisk to complete?
Run CHKDSK with the /r option to correct these.
How to Run Disk Check in Windows 7

Your last crashes.

Code:

STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Usual causes:  Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus,  Device driver, NTFS corruption, BIOS
Invalid system memory was referenced.
Arg3: fffff800035cedfa, If non-zero, the instruction address which referenced the bad memory address.
FAILURE_BUCKET_ID:  X64_0x50_nt!ObReferenceObjectByHandleWithTag+22a
------------------------------------------------------------------------------------------------------------------------------
STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Usual causes:  Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
Arg1: fffff880034fca58, memory referenced
Arg3: 0000000000000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation
IMAGE_NAME:  iaStor.sys
FAILURE_BUCKET_ID:  X64_0xA_iaStor+2cdf9
------------------------------------------------------------------------------------------------------------------------------
STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Usual causes:  Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus,  Device driver, NTFS corruption, BIOS
Invalid system memory was referenced.
Arg3: fffff80003588dfa, If non-zero, the instruction address which referenced the bad memory address.
FAILURE_BUCKET_ID:  X64_0x50_nt!ObReferenceObjectByHandleWithTag+22a
------------------------------------------------------------------------------------------------------------------------------
STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
Usual causes:  Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
Probably caused by : intelppm.sys ( intelppm+2c53 )
This dmp file was corrupt, this usually points to RAM errors.
------------------------------------------------------------------------------------------------------------------------------
STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL 
Usual causes:  Device driver
Arg1: fffffa9003bf5660, memory referenced
FAILURE_BUCKET_ID:  X64_0xD1_paeusbaudiodsp_x64+2dd6
------------------------------------------------------------------------------------------------------------------------------

These crashes are indicating the tests and suggestions from my previous post needs to be implemented.

Let us know what you decide to do.