Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 101, {18, 0, fffff80280d22180, 0}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
the above dump file means a secondary processor became hung up or stopped working. Just to go back to my last post for a second, did you manage to run this test:
'Run a stress test of the gpu using Furmark. Watch the temps in case it starts to overheat'.
FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
Please post any results.
Regarding the above dump file as the analysis was inconclusive you'll need to run the driver verifier.
In order to run the verifer you will also need a recovery disk/USB. This is just in case the verifier causes a blue screen loop on start up. If it does you can then use the recovery disk/usb to boot into the recovery console, enable safe mode and then turn the verifier off. Hopefully by that point the culprit will have been caught and written on the dump file.
Recovery drive
Creating a recovery drive - Windows Help -
Safe mode
4 Ways To Boot Into Safe Mode In Windows 10
Driver verifier
How do I fix a Blue Screen in Windows using Driver Verifier?
Post any new dump files. Any problems post back.