Hey,
I have just upgraded my processor from an i5 9600kf to an i7 9700k but while doing a Cinebench benchmark I noticed the clocks wouldn't go above 3.78 GHz under full load.
It will clock way higher on lower loads, while writing this it's around 4.55 GHz while being minimally utilized but the clocks drop really fast whenever there's a significant load for the processor. (I know this in itself is normal behavior but I wouldn't expect the frequency to drop this much) I think this is strange because my i5 would hit 4.29 GHz consistently when under full load. There's plenty of room in terms of thermals I had around a maximum of 50 degrees Celsius on one of the cores.
The only conclusion I could think of would be my really cheap motherboard that doesn't support overclocking but I'm not sure if that's supposed to be affecting my turbo clocks.
Or is 3.78GHz a normal frequency for a stock i7 9700k while under full load?
The motherboard in question is a Gigabyte H310m S2H
Can someone give me a proper conclusion as to why this is happening and a potential solution to the problem?
Thanks,
Sam
I have just upgraded my processor from an i5 9600kf to an i7 9700k but while doing a Cinebench benchmark I noticed the clocks wouldn't go above 3.78 GHz under full load.
It will clock way higher on lower loads, while writing this it's around 4.55 GHz while being minimally utilized but the clocks drop really fast whenever there's a significant load for the processor. (I know this in itself is normal behavior but I wouldn't expect the frequency to drop this much) I think this is strange because my i5 would hit 4.29 GHz consistently when under full load. There's plenty of room in terms of thermals I had around a maximum of 50 degrees Celsius on one of the cores.
The only conclusion I could think of would be my really cheap motherboard that doesn't support overclocking but I'm not sure if that's supposed to be affecting my turbo clocks.
Or is 3.78GHz a normal frequency for a stock i7 9700k while under full load?
The motherboard in question is a Gigabyte H310m S2H
Can someone give me a proper conclusion as to why this is happening and a potential solution to the problem?
Thanks,
Sam