Overclocking
Even though the Strikers performance was great with its stock overclock, I couldn’t leave things alone, I had see what it is capable of overclock wise. To do this I split the overclocking up and test the GPU clock speed and the memory clock speed, then once I know what they can do I put them together and see if the card is capable of running them together. Starting with the GPU I started by running the Striker through at its stock speed, with the boost that gave us a clock speed of 1150MHz. I quickly bumped that up to 1250MHz and then finally 1300 where I maxed out what GPU Tweak would let me do without actually running into a hardware limitation.
On the memory side things were similar. I overclocked the Striker up to 6608 where I maxed out what GPU Tweak would let me do without having any crashes or artifacts. It wasn’t until I attempted to run both overclocks together that I had any trouble with crashing. After toying with it, dropping the GPU clock speed down slightly took care of the problem, but honestly I wouldn’t even bother with trying to overclock the memory. The FPS of the GPU overclock alone was higher than with both combined.
GPU Clock Speed Overclocking |
|||
GPU Clock Speed |
Pass/Fail |
FPS Result |
Notes |
1150MHz |
Pass |
42.2 |
|
1250MHz |
Pass |
44.82 |
|
1300MHz |
Pass |
46.39 |
Maxed out GPU tweak |
Memory Clock Offset Overclocking |
|||
Memory Clock Speed |
Pass/Fail |
FPS Result |
Notes |
6200MHz |
Pass |
42.30 |
|
6300MHz |
Pass |
42.39 |
|
6400MHz |
Pass |
42.42 |
|
6500MHZ |
Pass |
42.50 |
|
6608MHz |
Pass |
42.52 |
Maxed out GPU tweak |
GPU and Memory Overclocks Together |
|||
GPU Clock Speed |
Memory Clock Speed |
FPS Result |
Notes |
1300MHz |
6608MHz |
N/A |
Driver Crashed |
1300MHz |
6500MHz |
N/A |
Driver Crashed |
1250MHz |
6608MHz |
45.32 |