Your UEFI/BIOS (version A0.08) dates from 2015. Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system. If you are able to install the update through Windows (without booting from an external drive), then go ahead and update it. WARNING - if the computer might shut down during this procedure, please don't do it, as this may physically damage the computer and prevent it from booting.
FYI - W8 and W10 communicate more with the UEFI/BIOS than previous versions of Windows, so it's important to ensure that the UEFI/BIOS is kept up to date (and the outdated UEFI/BIOS' may be the cause of some compatibility issues).
Although you appear to have a reasonable number of Windows Update hotfixes for this version of your OS, please double check for any new Windows Updates. It only takes one update to cause a problem, so it's essential that you have all of them. The actual number is not important. Rather it's important that you checked manually, installed any available updates, and didn't experience any errors when checking or updating.
This device is disabled in Device Manager. Did you deliberately disable it? If so, why did you disable it?
Cisco AnyConnect Secure Mobility Client Virtual Miniport Adapter for Windows x64 ROOT\NET\0000 This device is disabled.
If able, please re-enable it and then uninstall it.
If not able to uninstall it, then please re-enable it and update it to the latest, W10 compatible version.
Although you're not having this error, please try the troubleshooting from this article: http://www.carrona.org/VideoTDR.html
It'll help in isolating problems that might come from the video card.
Many, many Live Kernel Events in the WER section of the MSINFO32 report.
This is often a sign of a hardware problem, so please start with these free hardware diagnostics: http://www.carrona.org/hwdiag.html
Please start with the video tests (Furmark and Other video), but please run ALL of the tests
Let us know the results and we can move on from there.
If you'd like me to look at the Event Viewer errors, please do the following.
The Sysnative dump of it is in text format and isn't very easy to scan through (and I have vision problems)
Please do the following:
- open Event Viewer (run eventvwr.msc from the "Run" dialog)
- expand the Custom Views category (left click on the > next to the words "Custom Views")
- right click on the "Administrative Events" heading
- select "Save all Events in Custom View as..."
- save the file as Admin.evtx
- zip up the file (right click on it, select "Send to", select "Compressed (zipped) folder")
- upload it with your next post (if it's too big, then upload it to a free file-hosting service and post a link here).
FYI - If we're looking for Event ID 41 errors (unexplained shutdowns), there's more info on that here: http://support.microsoft.com/kb/2028504
While waiting for a reply, please monitor your temps with this free utility:
SpeedFan v. 4.5.1 and later (free from here: http://www.almico.com/sfdownload.php ) can log temperatures in a CSV file:
You may not need to log temps. If uncertain, please ask.
NOTE:You may want to turn logging off when we're done - as I don't know it's impact on performance or on the system.
To make it work (log the temps to a file) you have to do BOTH of the below:
1. Enable logging in general: Configure...Log...check "Enabled" then click on OK to save.
2. Enable logging for specific checks: Configure...Temperatures..left click on each sensor, then click on "Logged" at the bottom of the Window (for our purposes we want them all) then once you've selected "Logged" for all sensors, then click on OK to save.
The log will be located at C:\Program Files (x86)\SpeedFan
Naming: log files are named SFLogYYYYMMDD.csv, where YYYY is the year (four digits), MM is the month (2 digits, zero padded) and DD is the day (2 digits, zero padded). If a file already exists by that name, the file that already exists is renamed according to the following naming scheme: SFLogYYYYMMDD-CCCC.csv, where CCCC is a increasing number. The new file is then created with the standard file name scheme.
Notes: whenever you change the options related with logging, SpeedFan starts a new log file.