New
#31
The dumps are showing a memory corruption during a wrapped shell execute. This can only mean two things. There is a problem with memory or third party software has an errant filter installed. Seeing the over-temperature throttling that occurred earlier in the month would be a clue but that's where the syslog ended (7/7). The applog showed no symptoms of heat related problems after that date. You could be having memory faults but those normally show up with a system BSOD and other signs in the dump. That leaves third-party software. Many are known to be incompatible with certain Windows functions and others that are just so poorly written they crash the system. There's also many that don't interact well with each other simply because they install filters (drivers) that interfere with each other or Windows. We see this a lot with multiple AV suites and Torrent software.
Follow this tutorial and perform a Clean Startup/Boot. Uncheck ALL the non-Microsoft items except the two that are highlighted in the image below. We, here at WSF, know that MSC does not cause conflicts so if the problem continues, the culprit can easily be determined by allowing one startup process at a time and testing the system. Continue the test making sure each User account is used. After that, check ONE more item to allow it's startup and repeat the system test for each user. Many of us are wagering on the outcome but this is the only way to prove it to you.