PAGE FAULT IN NON-PAGED AREA blue screen

Hi guys,
can someone help me with this random blue screen. It's happening 4-5 times a week , fairly randomly, no particular activity sets it off.

Attached the data file here, about to do a deep ram check.

Cheers

Jamie

• DESKTOP-VDTSN2J-13_11_2015_204839_59.zip (403.8 KB, 1 views)

Hi jambon316,

Welcome to the 10blog.

I suggest you run MemTest86+ to test your memory.
The 0x50 are mainly read errors

Code:

PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced.  This cannot be protected by try-except, it must be protected by a Probe.  Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: ffffc0a0c40d8698, memory referenced.Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. Arg3: fffff8005ad368fb, If non-zero, the instruction address which referenced the bad memory     address. Arg4: 0000000000000002, (reserved)

Please uninstall everythingof AMD using Display Driver Uninstallerand install new drivers from AMD. Be sure to ONLY install the drivers using custom/advanced options.

Code:

*** WARNING: Unable to verify timestamp for atikmpag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys 2: kd> lmvm atikmpag start             end                 module name fffff800`b55a0000 fffff800`b5649000   atikmpag T (no symbols)                Loaded symbol image file: atikmpag.sys     Image path: SystemRootsystem32DRIVERSatikmpag.sys     Image name: atikmpag.sys     Timestamp:        Sat Aug 22 03:45:00 2015(55D7D41C)     CheckSum:         000A5C52     ImageSize:        000A9000     Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Diagnostic Test

 RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 blog

   Note

MemTest86+ needs to be run for at least 8 passesfor conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zeroerrors here. Even a single error will indicate RAM failure.

This was the warning displayed by the next to useless windows memory diagnostic tool, i'm going to run memtest too just so i have some tangible proof of the ram sticks being bad but this is pretty much a guarantee if it now isn't it? as this pc is on a remote site, my buddies house, i am pretty much thinking i've done all i can now, software should be ruled out at this point. is that right?

There is much more we can do, but I can't think of everything possible because that much is there we could try.

This message doesn't really say that the memory is bad, it could also be software causing this due to a bug.