5820K on an MSI X99A SLI Plus Mobo

yeah dude i will when im happy with my overclock settings, to get going i would start by setting 44 multi, 100blk, leave ram at 2133mhz, leave cache at 3000mhz, set vccin to 1.95, vcore to 1.3 and cache to 1.15 run a custom prime95 tourture test put 448 in each box then set ram to how much ram in MB you want it to use, then let it run for 2 hours - if it fails in the first 20mins raise the vccin abit to 1.97 and retest, if it passes and you're happy with 2hour stable at those voltages move on to the vcore using 1344 custom sets, im pretty sure 1.95 will get you about 1hour stable if not longer. then do the same for vcore,imc etc etc... no easy solution im afriad it all depends on how much time you want to put in to your overclock. start of at a base, then test test and retest.
 
Last edited:
vonex said:
yeah dude i will when im happy with my overclock settings, to get going i would start by setting 44 multi, 100blk, leave ram at 2133mhz, leave cache at 3000mhz, set vccin to 1.95, vcore to 1.3 and cache to 1.15 run a custom prime95 tourture test put 448 in each box then set ram to how much ram in MB you want it to use, then let it run for 2 hours - if it fails in the first 20mins raise the vccin abit to 1.97 and retest, if it passes and you're happy with 2hour stable at those voltages move on to the vcore using 1344 custom sets, im pretty sure 1.95 will get you about 1hour stable if not longer. then do the same for vcore,imc etc etc... no easy solution im afriad it all depends on how much time you want to put in to your overclock. start of at a base, then test test and retest.
Click to expand...

Good to know! :)
 
I've got 4.5GHz stable @ 1.265v - I say stable, I'm gonna stress it overnight but thus far with a few hours of stressing and multiple benches it's not missed a beat :)
 
Howling said:
I've got 4.5GHz stable @ 1.265v - I say stable, I'm gonna stress it overnight but thus far with a few hours of stressing and multiple benches it's not missed a beat :)
Click to expand...

Any other extra settings you tweaked? Are you able to provide screenies, please? :)
 
Sure. Screenie from the 8hr aida thread over in the CPU section;
1h4fqQr.png

I used Intel XTU and simply changed the multiplier to 45x on each core and the core voltage to 1.265v -- left everything else at default. I like things simple I guess.
Using MSI X99A Gaming 7 board btw.
 
my psu has died... just ordered a 1000w superflower platinum so will continue when its arrives.

RIP corsair tx850w v2 2012 - 2015
 
vonex said:
my psu has died... just ordered a 1000w superflower platinum so will continue when its arrives.

RIP corsair tx850w v2 2012 - 2015
Click to expand...

Warranty rma? 5 years warranty? corsair are quite good they might even give you a step up at similar wattage. My AX 750 died and got the new AX 760 instead.
 
remy87 said:
Warranty rma? 5 years warranty? corsair are quite good they might even give you a step up at similar wattage. My AX 750 died and got the new AX 760 instead.
Click to expand...

yeah i'll RMA it with corsair and sell the replacment on MM, i bought the superflower 1000w platinum and its coming tomorrow THANKS TO OCUK for giving me saturday shipping for £9.99
 
Just to hijack this thread a little -- something I've not seen before is the cache clock, is that something I should be overclocking as well or just leaving that one? O.o
 
Really not having much luck with mine. I got 4GHz mostly stable - using Prime 27.9 I got 12 hours before an error so I'm sure a minor voltage bump would take care of that.

However 4.2GHz and above are proving difficult, Prime will just lock the whole thing up and make it reboot within about 2 or 3 seconds of starting.

For 4GHz I only needed 1.15v which I thought wasn't too bad. Then to move on I tried 1.3v with 100 bclk and 44 multiplier and when I realised that wasn't stable I dropped to 42 but still see the same. I've upped the vccin voltage to 1.95 but that made no difference at all. I've also tried the 125 strap and 33/34 multiplier which booted up fine but gave me the same results. Temps don't appear to be too bad but then I don't get a chance to check what they are as it reboots almost instantly. What am I missing here?

Specs are:
i7 5820K
MSI X99A SLI Plus
EVGA 850w Superflower G2 PSU
GeForce GTX 970
Corsair H100i GTX
Crucial M4 128GB SSD and Samsung 2TB HD

Edit: After that I managed to get it Prime stable for about 20 minutes at 4.2GHz. I previously tried the CPU voltage set to offset mode with a 0.2v offset to give me around 1.3v. I set the VDroop Control back to its default Auto (was on 50%) before and changed the CPU volts to adaptive/offset mode with a 0.15v offset which gave me 1.28v roughly under load in Windows. It lasted about 20 minutes before BSOD'ing on me so I'm sure more volts may help, but needing 1.3+v for 4.2GHz is a pretty crappy chip from what I've read unless there's some other options I can try :(
 
Last edited:
Beginning to think that myself. I think I'm beginning to regret my X99 decision - would rather have better clocked quad core than a lower clocked hex core. Might try to offload this kit as it's annoying me now.
 
It seems it isn't the motherboard at fault. I have an Asus X99-A to test with and under Prime 95 (version 27.9 without the AVX stuff) load it will still blue screen after an hour or so, even with voltage up at 1.27v. After reading of so many people only needing 1.1-1.15v for 4.2GHz I think I'm ready to just give up with overclocking this thing and go back to my 2600K.

Just my luck to get not just a 5820K that's below average, but WAY below average.
 
just abit of an update, my x99a mpower has been causing me a lot of problems, pci-e jumping from 3 to 1.1, low cpu usage, low gpu usage, stuttering and a slight delay on general windows tasks, just replaced it with an asus x99-s, everything is running fine now and im running prime @ 4.4ghz 1.292v, 4ghz cache 1.27v, 2666mhz 15 15 15 35 350 1t 1.28v, the msi board would not boot with cache above 3500mhz so in away im happy its faulty.

turns out my PSU is not faulty and it was actually the motherboard causing hte problem.
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom