Windows 10: BSOD 0x00000050 0x0000003b 0x0000000A

My computer has crashed for some time now and the things I have been doing so far is
Swap out my GTX 660 for my old GTX 460. No improvements.
Swap out my ram memory with a friend 8GB.No improvements.
Installed a clean version of Windows 10. It still crashes.
Been using Verifier and it has crashed about 5 times from going from login into desktop, in system logs and Minecraft.
No mini dump file has been created with Verifier on.
The last crash as I do got a mini dump from was like 4-5 minutes into a new Minecraft world.
Thanks in advance
Edit: since i created this post I had an other crash see separate mini dump file.

:)

 

Windows 10 64-bit Blue Screen of Death

Hi,

several BSOD happens when wake up the PC in a sleep mode, it does not happen everyday, bug check string, code and caused by driver as follows:

SYSTEM_SERVICE_EXCEPTION, 0x0000003b, ntoskrnl.exe.

PM KMODE_EXCEPTION_NOT_HANDLED 0x0000001e ndis.sys.

AM IRQL_NOT_LESS_OR_EQUAL 0x0000000a ntoskrnl.exe.

PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 FLTMGR.SYS.

PM SYSTEM_SERVICE_EXCEPTION 0x0000003b atikmdag.sys.

Here is the link for DMP and MSinfo

My PC dmp and info.zip

Computer specification:

OS: windows 10 64-bit

CPU: intel core i7-4770 3.40GHz

Ram: 16 GB

Video card: AMD ATI Radeon R9 390x

Motherboard: Gigabyte Z87-HD3

 

BSOD Windows 10 ntoskrnl..exe

Upgraded to windows 10 BSOD are haunting me cant seem to find the issue. Updated drivers, new graphics card, running SSD hard drive. What next?

PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 ntoskrnl.exe+142970 10.0.10586.589 (th2_release.160906-1759)

SYSTEM_SERVICE_EXCEPTION 0x0000003b FLTMGR.SYS 10.0.10586.0 (th2_release.151029-1700)

ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY 0x000000fc dxgmms2.sys 10.0.10586.545 (th2_release.160802-1857)

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x0000000000005fc7, 0x48d38afff3a267e8, 0x0000000000000000, 0xfffff80002aea7ce). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 00000000-0000-0000-0000-000000000000.

 

You don't have verifier setup correctly:

Code: STANDARD FLAGS: [X] (0x00000000) Automatic Checks [ ] (0x00000001) Special pool [ ] (0x00000002) Force IRQL checking [ ] (0x00000008) Pool tracking [ ] (0x00000010) I/O verification [ ] (0x00000020) Deadlock detection [ ] (0x00000080) DMA checking [ ] (0x00000100) Security checks [ ] (0x00000800) Miscellaneous checks [ ] (0x00020000) DDI compliance checking ADDITIONAL FLAGS: [ ] (0x00000004) Randomized low resources simulation [ ] (0x00000200) Force pending I/O requests [ ] (0x00000400) IRP logging [ ] (0x00002000) Invariant MDL checking for stack [ ] (0x00004000) Invariant MDL checking for driver [ ] (0x00008000) Power framework delay fuzzing [ ] (0x00040000) Systematic low resources simulation [ ] (0x00080000) DDI compliance checking (additional) [ ] (0x00200000) NDIS/WIFI verification [ ] (0x00800000) Kernel synchronization delay fuzzing [ ] (0x01000000) VM switch verification[/quote] Driver Verifier is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

Driver Verifier - Enable and Disable in Windows 10

Pay close attention to


PART TWO


and make sure the correct boxes are checked.


Warning:
It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

Always create a Restore Point prior to enabling Driver Verifier.

What we're looking for is a BSOD with a mini dump that will tell us what driver caused it.

As for the dumps:

07/02/16 12:54 PM Driver Verifier enabled but setup wrong. No useful info in dump.
07/02/16 11:11 PM Driver Verifier not enabled. no useful info in dump.
07/02/16 09:35 PM Driver Verifier not enabled, memory_corruption. No useful info in dump.
07/02/16 06:35 PM Driver Verifier not enabled, hardware. No useful info in dump.

Since you have already swapped out the RAM I don't see that as being the cause of this. Ditto for the video card.

Check the system temperatures using Speedfan and/or CPU-Z. If nothing out of whack there, try stress testing CPU and GPU.

Follow this tutorial to stress test your CPU:

Prime95 - Stress Test Your CPU - Windows 10 Forums

Follow this tutorials to stress test your GPU:

FurMark - GPU Stress Test - Windows 10 Forums

 

I had three more crashes this morning. After two 0x00000050 PAGE_FAULT_IN_NONPAGED_AREA crashes in a row I disabled page file to test it and got IRQL_NOT_LESS_OR_EQUAL 0x000000a. Verifier was on this time.
The link is to the three new mini dump files on my onedrive.
This afternoon I had an other crash 0x000000fc.
New mini dump

 

In the future, please load all files here, not Onedrive or anywhere else.
Always run the DM_Log_collector as that will include the drivers list and other files that may be of use.

I see 5 dump files from 07/03/16.

 

Dump from Sun Jul 3 06:50:05 indicates a problem with adgnetworkwfpdrv.sys. It's part of Adguard WFP network driver.
Note that Driver Verifier is not enabled in this dump.

Uninstall Addguard for Windows, see if that resolves the problem.

The dump from Sun Jul 3 11:14:31 does not have Driver Verifier enabled either. No useful data in it.
The dump from Sun Jul 3 05:28:50 does not have Driver Verifier enabled either. No useful data in it.
The dump from Sun Jul 3 06:22:16 does not have Driver Verifier enabled either. No useful data in it.
The dump from Sun Jul 3 06:22:16 does not have Driver Verifier enabled either. No useful data in it.

Driver Verifier was not enabled in any of these dumps.