Computer crashes, BSOD, freezes

Drivers. Try re-installing the drivers - GPU drivers, especially.

Did you monitor CPU temps? Try replacing the thermal paste and re-seating the cooler a bit more carefully, in case the temps are abnormal.

As for failing CPU, depends on how much voltage you run it at, the temps, and how long you've been using it at that.

Temps are pretty good, so it really is difficult tell, at least within my knowledge. Try to run other kinds of stress tests - both GPU and CPU. Run AIDA64, Unigine, PCMark, and other stress tests as well. Keep an eye on the GPU as well, and did you OC the GPU?

Considering current information, it really looks like a dying part, because everything else looks pretty normal to me.

in general for bugchecks: you want to update the bios and motherboard drivers from the motherboard vendors website.


for bugchecks that do not produce a memory dump, you would suspect the storage system
(and update the bios and motherboard drivers) but sometimes you also have to update firmware of a solid state drive and make sure there is plenty of free space on the drive. run crystaldiskinfo.exe to read the smart data of the drive. You should also consider putting the drives data cable on a different port and controller if your system has two SATA controllers. Generally, the slower one directly supported by the cpu chipset will have fewer bugs in the driver.


with freesing/lockups they can happen when a graphic driver gets messed up. The most common cause of this is overclocking of the grahics driver and conflicts between the graphics drivers sound system and another sound controller in your system. very common for the motherboard sound driver to cause this. most motherboard vendors did a audio driver update after windows 10 shipped.


there are other causes of the lockups but these are the most common. if these attempt at a fix don't work then you have to google how to force a memory dump via keyboard, make the registry settings and attempt to force a memory dump while the system is locked up. Generally you would want to run verifier and set debug flags and change the memory dump to kernel so the debug data is not stripped out of the memory dump.

you would also have to put the memory dump on a server and post a link so it could be read with the windows debugger.

you would have to put the memory dump on a server like Microsoft onedrive, share the file for public access and post a link.

yes, certain mouse drivers can cause this problem under certain conditions. (usb mouse drivers can corrupt data on the usb bus, usb bus can be shared with the PCI/e bus which has your graphic card on it.)

your memory dumps show parameter 1 (the error code) to be 0xc0000005 which is generally a bad memory address being passed to a driver.

you have one error code 0xc000000e
which is A device which does not exist was specified.

since it was a kernel in page error it could mean that your drive is connecting and disconnecting over and over.
or has become unresponsive. normally you would check cable connections, update sata drivers or move the drive to a different sata port and controller. also check for firmware updates to the drive and make sure there is plenty of free space. if the drive firmware is behind in its garbage collection routines, you can boot into bios and leave it powered but unused. After 5 minutes, the firmware cleanup will run and try to clean up the drive.

note the timestamp string on the Logitech looks like a ok version.
the human interface drive has a bogus timestamp (in 1991)
current versions windows have some in process memory compression and tend to mess up the compression where the drive dates become corrupted. It also messes up the debugger and makes it hard to figure out problems

here is a problem: you last bios for this machine was in 2010, the specifications for USB were changed in 2012 and windows 10 will be using the new specs. The new specs require a BIOS update after about april of 2012 and your motherboard is out of support. basically windows 10 will run until it hits a bug in the USB or SATA then you will have to reboot. You might be able to disable your onboard USB ports and put in a cheap USB 3 or USB 2 card.
or go back to a older version of windows that you can get proper drivers for.
I guess you could go back to a PS/2 keyboard or reboot your machine every few hours and never let it sleep.

you bios info:
BIOS Version 2103
BIOS Release Date 06/18/2010
Product M4A785TD-V EVO
Version Rev X.0x


-------
you have a USB device that failed, looks like it was removed but its file handles were not closed so it never finished the remove.
InstancePath is "USB\VID_0000&PID_0002\5&33cee4ba&0&2"

some mice and keyboards have firmware updates that you have to apply.



first time I have seen this driver installed:
\SystemRoot\system32\drivers\tsusbhub.sys

I would also suspect this driver:
Asus ATK0110 ACPI Utility (l would look for a update)
\SystemRoot\system32\DRIVERS\ASACPI.sys Thu Nov 1 18:54:34 2012

depends on what the cause of the problem was. Sometimes usb problems leave drivers that are old, some of the old drivers respond to all events on the USB bus rather than just events for that driver. generally, these will just slow your system down and will not cause a bugcheck unless some timeout value is reached.
generally, I can see these by looking at a kernel memory dump, there are internal logs that track errors.
I have seen USB logs record 26 million event logs in 10 or 20 minutes.

you might be able to run usbview.exe and see if you have a problem with a usb subsystem. its source come with the windows device driver kit but people have made versions you can download. I use this one most of the time:
http://www.uwe-sieber.de/usbtreeview_e.html

most of the time, I just look at the kernel memory dump using the debugger and dump the various internal logs to look for a problem. I also look at the various file dates and BIOS dates.

also, if windows finds a bugcheck on your system it sends it to a Microsoft system for debugging and tries to push a fix back to your system or do additional debugging. you can find these special memory dump if you search your hard drive for files with a .dmp extension. for most machines, Microsoft might find the cause of the problem but be unable to install a fix (for various reasons, like special drivers required or BIOS update required) On my old machine the windows update would turn off sleep because of known bugs in the BIOS. My wifes asus machine has known bugs in the USB support chips and you just have to reboot the machine to fix the USB ports.

you might also check your BIOS to see if there is a setting for USB. sometimes you can tell the bios to use a old version and turn off the USB extensions. motherboard vendors often attempt to speed up their usb by making extensions before the final specification is made. When the spec comes out the vendor has to update the BIOS and provide new drivers.
I think the 2.2 spec came out in 2012. you might see if there is a setting in bios to only use legacy or 1.x spec for the USB.
Problem is that newer drivers might not test properly with the old spec and you might just hit a bunch of bugs.

see if you can remove the device software or disable it. it stops responding after a while. you might have to use this method if the usbview can not remove the device (or windows PNP just reinstalls it)
https://technet.microsoft.com/en-us/library/cc771484(v=ws.10).aspx