Thanks for the dump. Unfortunately it didn't help.
I want you to run memtest86+ v 5.01 as follows:
===================================================
Follow this tutorial:
MemTest86+ - Test RAM - Windows 10 Forums
MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:
- RAM will accept and keep random patterns of data sent to it
- There are no errors when different parts of memory try to interact
- There are no conflicts between memory addresses
Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.
Warning
MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.
If you are asked to run
MemTest86+ by a Ten Forums member
make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.
Note
MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.
Running 8 passes of
MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run
MemTest86+ just before you go to bed and leave it overnight.
Take a picture when done and post in the forum please.
If that doesn't indicate a memory problem then give
Driver Verifier a try.
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 may run very sluggishly due to the stress being applied to the drivers.
Directions here:
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 so you have a way to recover if it goes haywire. Seldom does but it can happen.
What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun the Beta log collector and upload the resulting zip file.
Here is some additional info on Driver Verifier posted by @
axe0 today in another thread:
Random weekly BSODs even after reset, CRITICAL_PROCESS_DIED