...Go to Start and type in sysdm.cpl and press Enter
Click on the Advanced tab
Click on the Startup and Recovery Settings button
Ensure that Automatically restart is unchecked
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump << where your .dmp files can be
found later.
Click OK twice to exit the dialogs, then reboot for the changes to take effect.
Then……Please read the first post in this sticky thread here Link RemovedGo to Start and type in sysdm.cpl and press Enter
Click on the Advanced tab
Click on the Startup and Recovery Settings button
Ensure that Automatically restart is unchecked
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump << where your .dmp files can be
found later.
Click OK twice to exit the dialogs, then reboot for the changes to take effect.
Hello and welcome to the forum.
Perhaps, if it's crashing, it may be generating a blue screen with associated dump files which might help diagnose the issue.
First make sure your machine is configured properly to facilitate the collection of .dmp files.
Then……Please read the first post in this sticky thread here Link Removed
Do your best to accumulate the data required.
Run the SF Diagnostic tool (download and right click the executable and choose run as administrator)
Download and run CPUz. Use the Windows snipping tool to gather images from all tabs including all slots populated with memory under the SPD tab.Likewise RAMMon. Export the html report, put everything into a desktop folder that you've created for this purpose, zip it up and attach it to your next post (right click it and choose send to, compressed (zipped) folder.
Additionally scan it with https://www.malwarebytes.org/mwb-download/
AND
Consider using some compressed air to free the heat sink and cooling fans from dust and debris
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {1c, 2, 0, fffff88001436cea}
*** WARNING: Unable to verify timestamp for RTL8192su.sys
*** ERROR: Module load completed but symbols could not be loaded for RTL8192su.sys
Probably caused by : RTL8192su.sys ( RTL8192su+f9ac )
Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {1c, 2, 0, fffff88001436cea}
*** WARNING: Unable to verify timestamp for RTL8192su.sys
*** ERROR: Module load completed but symbols could not be loaded for RTL8192su.sys
Probably caused by : RTL8192su.sys ( RTL8192su+f9ac )
Followup: MachineOwner