A user-mode process such as a game cannot by itself hang the whole system (OK one way would be to run an intensive thread in Realtime priority but nobody would really do that).
So this indicates a driver/hardware problem.
What I would do:
- Check the Event Viewer, specifically System and Application event logs. Check if anything suspicious is logged prior to the system hanging.
- Advanced debugging troubleshooting:
** Run "verifier" from the command line, "Custom settings", enable "Deadlock detection" for some or all drivers. From this point if a deadlock happens, causing the hanging, the system will bluescreen instead, producing a dump file. Analysing this crash dump will point to the problematic driver in question.
Quoting the Windows Internals book: "The first step to troubleshooting hung systems is to enable deadlock detection on suspect drivers, then unsigned drivers, and then all drivers, until you get a crash that pinpoints the driver causing the deadlock."
** There is a way to force-crash the system with a key press when it hangs:
https://msdn.microsoft.com/en-us/library...45499.aspx Once crashed, it will produce a crashdump which will need to be analysed.
If you succeed with any of these, upload the dump file and I can have a look.