BSOD ntoskrnl.exe

A new BSOD, ran the collector directly after it happened. It will be a while before the dump file is uploaded.

There were missing folders and files in the latest beta log collector.
Please re-run the beta log collector and post a new zip into the thread.
Also open file explorer > this PC > C: > in the right upper corner search for C:\windows\memory.dmp > zip > post a one drive or drop box share link into the thread

Re ran the log collector. The memory dump is being uploaded. Will post the link when it is finished.

When available please post a memory.dmp with all BSOD:

Crash dump found at C:\Windows\MEMORY.DMP
Creation date: 07/22/2018 02:57:15
Size on disk: 1195 MB

Here is the link to the memory dump.
Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

See post #12.
Had you used Windows driver verifier?

Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

Enable and Disable Driver Verifier in Windows 10 | Windows 10 Tutorials

zbook said:

See post #12.
Had you used Windows driver verifier?

Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

Enable and Disable Driver Verifier in Windows 10 | Windows 10 Tutorials

I did the first time it was recommended. I did not induce a BSOD that night with about 6 hours of continuous use. Should I keep driver verifier on until I get a BSOD?

1) make sure that you make a brand new restore point
2) and make sure that you have a backup image (Macrium, Aoemi, Acronis, Paragon, EaseUS, etc)
3) Use this link for the the custom settings:
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community
4) Use this link for the methods to turn off or recover from using Windows driver verifier:
Enable and Disable Driver Verifier in Windows 10 | Windows 10 Tutorials
5) Use the tool for 48 hours to find BSOD
6) After the last BSOD use the tool for an additional 36 hours and then that will complete the troubleshooting with this tool.
7) The computer and boot may become sluggish while using the tool. It there are problems using the computer then communicate that into the thread and the settings can be modified.
8) After each BSOD allow the % counter to rise to 100% before rebooting so that there is sufficient time to create the dump file
9) Use verifier/reset or verifier /bootmode resetonbootfail or system restore to turn off or recover from using the tool and always use the verifier reset first and advance to the other commands only if the prior command fails. System restore often leads to a loss of the dump file and little progress is made in the troubleshooting.
10) After each BSOD post at the same time: a) beta zip and b) c:\windows\memory.dmp zip

Followed driver verifier instructions exactly. Did a fresh system restore point and enabled driver verifier exactly as prescribed, checking only the non-microsoft drivers. Complete bricked system. Won't boot to windows (hangs on the spinning circle). Tried to reset verifier (received the message "no settings were changed"). Tried to system restore. Gives error 0x800700003. Tried to clean install from recovery drive and USB, gives error 0x80070003. I'm going to pull the SSD and completely wipe it and start again. Hopefully this gives some more troubleshooting data.

Had you made a Macrium backup image?
Macrium has a boot rescue which can be tried however it is not likely to turn off Windows driver verifier.
There are troubleshooting steps using command prompt.
What happened with the command: verifier /bootmode resetonbootfail?
Clean install is the most efficient method.