My benchmarks were in competition, and I ended up in 28th position in the Asia amateur qualifier competition of the overclocking World Series. I could see how this has become a competitive electronic sport. But it was also becoming more fun as I started to battle with the system for stable performance.Ī small change I made in one place had an effect on another side of the performance, and it was getting to be much more of a game to keep pushing the benchmark number higher while preventing the machine from crashing. The blue screens were becoming more frequent and the adjustments I was making were becoming finer and more exotic.

Then I adjusted the amount of cache memory used by the processor and got a higher score: 2,717 - a 27 percent increase from my starting point. That had the effect of pushing the chip to 4.44GHz and resulted in a benchmark of 2,683. Martyn WilliamsĪ blue screen of death experienced while overclocking a PCīased on advice from an overclocking expert, I next focused on the clock frequency and took it up to 101MHz. Something wasn't performing well, so I rolled back to 44x and set my sights on other adjustments. Things started going wrong at 45x when I experienced a blue screen. At 43x I managed 2,608, and at 44x it was at 2,651 - a 24 percent increase from the starting point. I kept increasing the multiplier and the benchmark kept rising. That's a 20 percent boost in performance with nothing more than a few clicks. With this initial adjustment, it all seemed stable enough, so I ran the benchmark again: 2,577. I had also adjusted the voltage being applied to the chip core so that it could handle the extra power, but I needed to be careful that I didn't apply too much and overheat the chip. A few clicks of the mouse had the multiplier at 42x and the chip running at 4.2GHz.

Intel xtu overclock