Just a little heads-up to anyone who's stress testing while benchmarking, I've come to notice the following...
If your driver crashes MAKE SURE to RESTART windows before continuing the benchmark. This is important!
GPU ERROR/STABILITY ISSUE#
Valley benchmark and/or games will specifically black out and the system will return to the desktop. Task Manager should be opened and the processes closed.
Reduce the GPU clock frequency or increase the core voltage in small increments.
MEMORY ERROR/STABILITY ISSUE#
The benchmark will continue to run, however you may notice an increase in on-screen visual artifacts. I have also noticed that if the memory clock is unstable, the benchmark will unexpectedly run at unusually low FPS and maintain poor performance until the system is restarted.
Reduce the memory clock or reduce the core clock and retry the benchmark.
THE SYSTEM BECOMES UNRESPONSIVE OR CRASHES#
You've taken it too far - ya numpty!
GPU ERRORS - Warped model geometry, spiked artifacts, white dots and/or coloured splotches or flickering. Games/software will crash to desktop.
MEM ERRORS - Texture/model loading errors, discoloured or incorrectly rendered maps, poor performance, full screen colour crashes and on-screen artifacts that resemble brightly coloured triangles.
If both parts are unstable then you may experience the infamous looping sound crash. Reset your computer.
Remember that lower temperatures reduce the amount of voltage leak experienced at higher temperatures and therefore higher clocks can be achieved at lower core temps.Edited by GreenNeon - 3/21/13 at 2:40pm