This crash is slightly different. It's its cousin stop error 0x117 which is also "VIDEO_TDR_TIMEOUT_DETECTED".
Unfortunately, the code itself is very difficult to diagnose. This, directly from the mindump:
Code:
VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
[COLOR=Red][B](This code can never be used for real bugcheck).[/B][/COLOR]
Arguments:
Arg1: fffffa8005b1b4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800ffdaf9c, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.
It could only be helpful to install the latest DirectX for June 2010:
DirectX End-User Runtimes (June 2010) download from Guru3D.com Failing that to be helpful, I would use CPU-Z to find out the exact RAM modules in use. Then visit the manufacturer's site for proper timings, voltage and frequency.
Once this info in known, then set the system bios manually using it. When booted to Windows, you can check CPU-Z's memory tab to see if it is correct, according to manufacturer.
Otherwise, it may be heat related. Try using Rivatuner to slightly downclock the memory/gpu and raise fan speed to max while playing a video game, as a test. Another good test would be to open the case and blow a large room fan inside while playing a game.
If no crashes under these circumstances, the 0x116 and 0x117 are being caused by heat.
If crashes while fan is blowing, then not a heat problem and we could probably look past that being an issue.
Edit: I looked up your video card and noticed it is overclocked out of the box. I would bet that downclocking as a test is not going to produce errors. It is high chances the factory overclock is not so well,
in your particular system/environment. Try eliminating heat and too much mHz on the gpu as a cause.