F5F Stay Refreshed Power Users Overclocking i7 980x underclocking problem

i7 980x underclocking problem

i7 980x underclocking problem

A
ArceusHD
Member
154
09-27-2016, 09:28 PM
#1
I was adjusting my i7 980x for underclocking while mining bitcoin with my GPU, wanting to reduce CPU load. I changed the multiplier to 22 (2.9 GHz). After stopping, I checked the BIOS and adjusted it back to 26 (3.46 GHz), which is a bit higher than the base clock. But both the Windows Task Manager and CPU-Z still show 2.9 GHz. Initially, I thought it was just a display issue, so I tried running a benchmark in GTA V, which showed lower FPS than before. Then I ran cinebench, and instead of the expected 665, it came out as 602. Do you have any suggestions on how to return to the base clock? I also tried setting the multiplier back to 25, but that didn’t help. My motherboard is an LG 1366 Gigabyte Guerilla Killer.
A
ArceusHD
09-27-2016, 09:28 PM #1

I was adjusting my i7 980x for underclocking while mining bitcoin with my GPU, wanting to reduce CPU load. I changed the multiplier to 22 (2.9 GHz). After stopping, I checked the BIOS and adjusted it back to 26 (3.46 GHz), which is a bit higher than the base clock. But both the Windows Task Manager and CPU-Z still show 2.9 GHz. Initially, I thought it was just a display issue, so I tried running a benchmark in GTA V, which showed lower FPS than before. Then I ran cinebench, and instead of the expected 665, it came out as 602. Do you have any suggestions on how to return to the base clock? I also tried setting the multiplier back to 25, but that didn’t help. My motherboard is an LG 1366 Gigabyte Guerilla Killer.

T
truji8tarifa
Member
193
09-28-2016, 05:36 AM
#2
So recently I attempted to further reduce the CPU's clock speed to a multiplier of 20, yet it still reports 2,93 GHz. Do you know what might be causing this issue?
T
truji8tarifa
09-28-2016, 05:36 AM #2

So recently I attempted to further reduce the CPU's clock speed to a multiplier of 20, yet it still reports 2,93 GHz. Do you know what might be causing this issue?