Thread replies: 7
Thread images: 2
Thread images: 2
Anonymous
OC past threshould. Windows or CPU at fault? 2017-03-15 12:57:59 Post No. 59414044
[Report] Image search: [Google]
OC past threshould. Windows or CPU at fault? 2017-03-15 12:57:59 Post No. 59414044
[Report] Image search: [Google]
File: Capture.jpg (25KB, 361x199px) Image search:
[Google]
25KB, 361x199px
OC past threshould. Windows or CPU at fault?
Anonymous
2017-03-15 12:57:59
Post No. 59414044
[Report]
Can you help a brother out? I have had a 2500k for a while but only recently decided to OC it (yeah)
I've gotten from 3.3GHz to 4.1GHz stable no problem. The problem is past that. I set everything I can find in the BIOS to 42, I gave it more than enough vcore (1.3V at this point just to make sure that's not what's causing the problem) and I disabled every power saving feature ever in the BIOS.
I can boot fine and everything, but Windows doesn't detect the OC past 4.1GHz as you can see on the screenshot. That's under 100% load. (it's set to high performance btw)
The max. multiplier is 42 but it doesn't go past 4.1GHz regardless.
>>
"More than enough vcore"
>1.3v
If you want to go higher you'll need to give it more vcore.
>>
>>59414044
its the turbo boost multiplier, it will only go at that speed with one core under load.
>>
File: IMG_0641.png (1MB, 750x1334px) Image search:
[Google]
1MB, 750x1334px
Set Voltage maximum then benchmark again.
>>
>>59415431
kill yourself, itoddler.
>>
>>59415028
>>59415064
>>59415431
Ignore these trolls. Check the following settings:
>EIST and speedstep is enabled in BIOS
>turbo boost is enabled
>"sync all cores" in BIOS (when settings the multiplier)
>use fixed/manual/override voltage
If none of those work, update your BIOS and motherboard drivers.
>>
>>59415028
no, I got 4.1GHz stable on 1.17V there's literally no reason to need this much more voltage for 100MHz more
>>59415512
I got it working by accident. My last resort was to disable all but one core and see if that somehow made it better and lo and behold it actually recognized my 4.2GHz OC.
The problem was after that I enabled all cores again but it somehow didn't propagate anymore. Windows couldn't detect more than one core.
At this point I knew nothing else but to reset the entire BIOS and now it works flawlessly again. The OC works even with various energy saving features still enabled. I guess something about the BIOS must've been off so that it didn't propagate certain settings.
Thread posts: 7
Thread images: 2
Thread images: 2