BSOD page_fault_in_nonpaged_area Win7 and Win8

[Dave76]

If you get any more crashes, try the steps below.
You've had good help previously, just a few things that should be followed up on.

Since this is looking like a hardware issue, can you fill in your System Specs?
You can use this app to find them: Speccy Free System information Utility
Then enter them in the 'My System Specs' drop box at the lower left of any of your posts.

Previously mentioned that you ran memtest86+ for a couple of hours, how many passes did it make?
Need a minimum of 7 full passes to test your RAM. It runs different tests with each pass.
Your symptoms seem like a hardware issue so you should run memtest86+ again.
This may take several hours to complete so best to run overnight, you can stop the test if you get any errors, one is too many.
The crash you had, reported by x BlueRobot in post #41, indicates memory_corruption, testing the RAM is where you should start.

If you had problems with your graphics card when you ran Driver Verifier, then there might be an issue with your graphics card driver or the graphics card itself.
Driver Verifier stresses drivers, trying to make faulty or bad drivers fail so they will be identified and you can fix the problem.
Run a graphics test to check your graphics card.

Have checked for an update on the OCZ Agility 3 SSD firmware?
This SSD is known to have some issues, and a few firmware updates to solve them.

 

[cdog27]

Morning Dave,

i3 530 @ 4.0GHZ
16GB Kingston HyperX Grey
1GB 460GTX
Gigabyte H55M-UD2H
OCZ Agility 3 SSD 120GB

memtest86+ made 2 passes, was running for a couple hours. What I'll do is leave it running when I go to work (just about to leave), which should mean it runs for 9+ hours by the time I'm home this evening. Will that be sufficient?

I believe there is a newer version of the Agility 3 firmware, but don't you have to format the drive to update? I couldn't do it with this install of Windows 8 still in place, could I?

Thanks for your help.

EDIT - Used a tool OCZ provide which allowed me to boot from USB into a modified Linux environment, update the Agility SSD driver (to 2.25) and reboot. So SSD firmware is now up to date. I've left memtest86+ running (I'm at work now), and will post the results when I get home.

If you get any more crashes, try the steps below.
You've had good help previously, just a few things that should be followed up on.

Since this is looking like a hardware issue, can you fill in your System Specs?
You can use this app to find them: Speccy Free System information Utility
Then enter them in the 'My System Specs' drop box at the lower left of any of your posts.

Previously mentioned that you ran memtest86+ for a couple of hours, how many passes did it make?
Need a minimum of 7 full passes to test your RAM. It runs different tests with each pass.
Your symptoms seem like a hardware issue so you should run memtest86+ again.
This may take several hours to complete so best to run overnight, you can stop the test if you get any errors, one is too many.
The crash you had, reported by x BlueRobot in post #41, indicates memory_corruption, testing the RAM is where you should start.

If you had problems with your graphics card when you ran Driver Verifier, then there might be an issue with your graphics card driver or the graphics card itself.
Driver Verifier stresses drivers, trying to make faulty or bad drivers fail so they will be identified and you can fix the problem.
Run a graphics test to check your graphics card.

Have checked for an update on the OCZ Agility 3 SSD firmware?
This SSD is known to have some issues, and a few firmware updates to solve them.

 

[Dave76]

Good work on the SSD firmware update and the specs, can you enter the specs in the 'System Specs' dropbox in the lower left of any of your posts, that way we don't have to search through the thread to find them.

With 16GB RAM it may take longer than 9 hours, just let it run until it starts pass #8, then you can stop it.
Let us know the memtest86+ results.

 

[cdog27]

Good work on the SSD firmware update and the specs, can you enter the specs in the 'System Specs' dropbox in the lower left of any of your posts, that way we don't have to search through the thread to find them.

With 16GB RAM it may take longer than 9 hours, just let it run until it starts pass #8, then you can stop it.
Let us know the memtest86+ results.

Specs entered into 'System Specs'.

I'll see what pass number it has reached when I get in from work. Will it produce an error log I can share on here? Or should I just make a note of everything and anything?

 

[Dave76]

You can take a picture, but the fact that it passes or has errors is all that's really needed.
Just note the number of errors.

 

[cdog27]

OK will do. If it has errors, what are the next steps? Run memtest86+ on a module by module basis to identify the faulty stick? I have 4x4GB.

 

[Dave76]

If you get any errors you can stop the test.

Normally you would run memtest86+ one card at a time, you can test two cards to save some time.
If you get an error, remove one card and test again.

 

[cdog27]

If you get any errors you can stop the test.

Normally you would run memtest86+ one card at a time, you can test two cards to save some time.
If you get an error, remove one card and test again.

8hours 32minutes of testing so far; only 4 passes complete!!! No errors as of yet.

 

[cdog27]

16hours of Memtest86+, no errors (see attached).

 

[Dave76]

Good news on the RAM.
16GB RAM is nice to have until you need to test it.

Use Real Temp , to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.

If you want to stress test the system you can run OCCT.
OCCT stability checking tool
Run the CPU:OCCT test for at least 30 minutes, be sure to monitor your CPU and GPU temps.
Set the time before you start, leave the 1 minute pre and 5 minute post idle time, this gives a good reference point.
When its done, pass or fail, it will make some graphs. Post these here as they are useful for analyses.

If you get any more crashes, post the full report files.

 

[cdog27]

Good news on the RAM.
16GB RAM is nice to have until you need to test it.

Use Real Temp , to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.

If you want to stress test the system you can run OCCT.
OCCT stability checking tool
Run the CPU:OCCT test for at least 30 minutes, be sure to monitor your CPU and GPU temps.
Set the time before you start, leave the 1 minute pre and 5 minute post idle time, this gives a good reference point.
When its done, pass or fail, it will make some graphs. Post these here as they are useful for analyses.

If you get any more crashes, post the full report files.

Ran CPU:OCCT for 30 minutes. No errors.

Max temp:
Core1 - 68C
Core 2 - 63C

A bunch of graphs attached, let me know if you need more.

 

[Dave76]

Post all of the graphs.

The ones you posted look good.

 

[cdog27]

Post all of the graphs.

The ones you posted look good.

attached

 

[x BlueRobot]

There seems to be no errors reported so everything seems fine to me, any BSODs recently?

 

[cdog27]

No, none in the last couple days.

I think going forward ill just keep an eye on it and post any new BSODs in this thread if they happen. It is very random, so will have to wait and see.

Thank you both for all your help, much appreciated.

 

[x BlueRobot]

No, none in the last couple days.

I think going forward ill just keep an eye on it and post any new BSODs in this thread if they happen. It is very random, so will have to wait and see.

Thank you both for all your help, much appreciated.

Your welcome, and just keep the thread open for about a week and then report back your results

 

[Dave76]

There are a few voltage fluctuations, other than that the graphs look ok.

Is there a reason you're running your OC with locked in CPU frequency and voltage?
This causes a lot of stress on your CPU, most people are OC'ing with EIST enabled and Balanced Power plan.

This let's your system idle and gives full power when needed.
You choice, just a recommendation.

Let us know if you have any more crashes.

 

[cdog27]

Thought everything was going fine...Just had a new, never-seen-before BSOD.

Was joining a server on COD Black Ops 2 and got a KMODE_EXCEPTION_NOT_HANDLED error. Files attached.

 

[x BlueRobot]

[COLOR="red"]KMODE_EXCEPTION_NOT_HANDLED (1e)[/COLOR]


BugCheck 1E, {ffffffffc0000096, fffff80397f9e879, 0, 0}

Probably caused by : [COLOR="Red"]ntkrnlmp.exe[/COLOR] ( nt! ?? ::FNODOBFM::`string'+18f76 )

[B]Usual causes:[/B]  Device driver, [COLOR="red"]hardware[/COLOR], System service, compatibility, Remote control programs, memory, BIOS

There are a few voltage fluctuations, other than that the graphs look ok.

Is there a reason you're running your OC with locked in CPU frequency and voltage?
This causes a lot of stress on your CPU, most people are OC'ing with EIST enabled and Balanced Power plan.

This let's your system idle and gives full power when needed.
You choice, just a recommendation.

Let us know if you have any more crashes.

Have you followed Dave's suggestion? As he said, you are putting a lot of stress on your CPU, and this may be causing the system to become unstable.

Processor Version             Intel(R) Core(TM) i3 CPU
  Processor Voltage             8ah - 1.0V
  External Clock                200MHz
  [COLOR="Red"]Max Speed                     4000MHz
  Current Speed                 4000MHz[/COLOR]

 

[Dave76]

At this point the crashes are likely coming from your OC, 4.0GHz is pretty high for your CPU and motherboard.
The OCCT graphs are showing fluctuating 12v and 5v power at your motherboard. This may be caused by the PSU or the motherboard.
If you want to check into the cause of these crashes you will need to set BIOS to defaults until the cause is found.
Once the cause is found you can OC again.

Latest crash:

STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
Usual causes:  Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
This is a very common bug check, not much info in the dump the help.
PROCESS_NAME:  t6mp.exe
FAILURE_BUCKET_ID:  0x1E_c0000096_nt!_??_::FNODOBFM::_string_

From your System Event Logs:

Event[3076]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-PnP
  Date: 2012-11-18T17:59:54.346
  Event ID: 219
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: C-PC
  Description: 
The driver \Driver\WudfRd failed to load for the device ROOT\WPD\0000.

WudfRd driver is a Windows Driver Foundation - User-mode Driver Framework Reflector

Event[3080]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Processor-Power
  Date: 2012-11-18T17:59:54.377
  Event ID: 55
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: C-PC
  Description: 
Processor 3 in group 0 exposes the following power management capabilities:

Idle state type: ACPI Idle (C) States (1 state(s))

Performance state type: ACPI Performance (P) / Throttle (T) States
Nominal Frequency (MHz): 4400
Maximum performance percentage: 100
Minimum performance percentage: 100
Minimum throttle percentage: 13

Is your CPU running at 4.4 GHz?

Your App Event Logs are showing a large amount of games and Steam App crashes.