Game shuts off computer after about 10 mins of gameplay.
DxDiag.txt output_log.txt No crash reports in WotO Folder.
3 Times now, I have had my computer shut off completely after playing for roughly 10 minutes or so. I am not sure if this is an issue on my end or in the game itself but the crash is consistent. When it does shut off my computer, I have checked to see if my hardware was really hot and might have overheated, but this doesn't seem to be the case. I am currently on the second map of the campaign, and it has crashed at different times during this map (aka not a specific time/trigger.) I have not had this problem with any other games (SC2, WoW, BL2, CS:GO, etc.) When it crashes, it shuts down my entire computer, and does not automatically restart. If I had to guess, my suspicion if that something on my hardware is triggering some sort of failsafe, and shutting down to protect itself. I will continue to tinker with video settings and post here is anything changes.
PS
Thank you so much for this game, I have been craving DK for years!!!!!
Looking at your system specifications, it seems that you only have 4gb of RAM. While this does meet the minimal system requirements, it can cause slowdowns in some of the busier levels like campaign mission 10. WftO can not, however, simply shut down your system by itself, so it indeed is very likely a hardware failure.
If you checked your PC's temperature, which components in particular did you check? The PC simply shutting down without a further whimper sounds as if the CPU is overheating (especially seeing how it only does so after a while), but if the CPU temperature is within acceptable parameters, this naturally isn't very likely to be the issue. You should, however, check whether or not your PC's power supply unit may be overheating, which may happen if the GPU gets especially power-hungry for graphics-intensive games.
There's a lot of other potential causes for this issue, including outdated or malfunctioning drivers, hard drive failure, and whatnot. Sadly, given that WftO very likely is not the cause of the issue but simply triggers the symptoms, I'm unsure whether there's very much we can do to help you. At best, I would recommend to do a bit of testing with benchmark software, so as to see whether or not the shutdown is related to heavy resource usage, or whether it is a mechanical problem.