All the most recent dumps show a Bugcheck: D1:
Code:
BugCheck D1, {0, d, 8, 0} Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+247
The dump from 10/28 at 8:17PM is similar but points to your Nvidia card/driver:
Code:
BugCheck D1, {ffffcc8cbc9767ba, 9, 0, fffff80eb56cadb4} *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : nvlddmkm.sys ( nvlddmkm+dadb4 )
You can try some of the older Nvidia drivers, see if they work any better for you. The latest ones are definitely buggy.
================================================================
Remove and install latest Nvidia drivers:
I suggest completely uninstalling the Nvidia display drivers using Display Driver Uninstaller (DDU) from WagnardMobile (near bottom of page) then get the latest driver for you Nvidia card here: NVIDIA Driver Downloads
Then do a custom install of only the NVidia graphics driver and the PhysX driver.
See if that gets rid of the problem.
================================================================.
If that doesn't help see what enabling Driver Verifier shows us:
===================================================
Driver Verifieris a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier'sverification 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 Verifierwill run very sluggishly due to the stress being applied to the drivers.
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 Verifierfor more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.
Alwayscreate a Restore Point prior to enabling Driver Verifier.
What we're looking for is a BSOD with a mini dump that will tell us what driver caused it.