Wednesday, July 10, 2013
Extreme Overclocking results from Corsair blog
Extreme Overclocking results from Corsair blog
Extreme Overclocking Results - Success and Failures
Overclocking on liquid nitrogen and pushing hardware into the danger zone can be very frustrating but can also be rewarding. We recently released an overclocking video that showed you how I prepare my motherboards to run on liquid nitrogen. I recently took the same setup from the video but with a different CPU, and tried to set the 3DMark03 world record with it.
After a weekend of testing I was able to secure third place in the benchmark with a score of 229,115 3DMarks. I knew I could push the CPU higher, so I made up my mind to try and take the world record poisition. After several more days of testing I was able to get the CPU clocked to 6.68GHz and get a run of 231,239 3DMarks. This was good enough for second place, and only a few thousand points behind first place.
I knew that I could easily get first place if I could just get a few more runs in with slightly higher CPU speed. Unfortunately, like I said earlier, pushing hardware to its absolute limits can be frustrating. After a five hour overclocking session, countless blue screens and crashes, the CPU finally had enough and no longer wanted to run 3DMark03. I tested the CPU one more time but it lost two of the memory channels so I was only able to run in single channel. I decided to run 3DMark05 this time, so I changed out the graphics cards to four 5870s. Again the CPU ran at 6.68GHz and I was able to get a result of 59,626 3DMarks. This was good enough for 6th place on HWBot.org.
Unfortunately I was unable to break the world record in 3DMark03, but with extreme overclocking that is the way it goes sometimes. I was still able to take a solid 2nd place, beating the previous 2nd place score by 2000 points. More details on the scores can be seen on HWBot.org 3DMark03 and 3DMark05.
This article was originally posted at http://www.corsair.com/blog/extreme-overclocking-results-success-and-failures/. Credits go to them