@LausCassidy Bug check 1e means that a kernel-mode program caused the error, but it doesn't specify which one. Your dxdiag also lists a few in page errors, which are usually related to an issue with the hard drive/solid state drive or memory. So I'd suggest you look there first. For the drives:
- Hit Windows key-X
- Choose either “PowerShell (Administrator)” or “Windows Terminal (Administrator),” whichever option is offered
- Inside the window that appears, copy and paste "chkdsk /f /r c:" without quotes, and enter
- You'll be asked to allow a restart; say yes
- When the scan is done, use this guide to find the results
- Repeat for drive D: use "chkdsk /f /r d:" without quotes
You should be able to attach the report to a post as well. Running chkdsk will take some time, so you may want to leave it while you're doing something else.
For the RAM, the gold standard is MemTest86, testing each module separately and in at least two different slots on the motherboard.
https://www.memtest86.com/index.html
https://www.overclockersclub.com/guides/memtest86_memory_guide/
Since this is time-consuming, you can start with chkdsk and see what you get, and you can also use Microsoft's built-in memory diagnostics first:
https://docs.microsoft.com/en-us/previous-versions/technet-magazine/ff700221(v=msdn.10)?redirectedfrom=MSDN
I wouldn't consider a pass from this tool to be even close to definitive, but if it does flag an error, that's probably accurate.
Finally, I'd like to know what RAM you're using, by product number. If you don't have that handy, you can find it on the modules themselves.
