Well, last post - final thoughts, from me, on this matter
So, besides my new stable OC profiles, all_core x 49, all_core x 47 with reduced VCore, I've finalized my per_core OC, as well: x49 x49 x 50 x 50. 5100 MHz, even on one core is out of the question for me: I boot all right, I run Outlook 2016 and my browser but as soon as some load is given, like a full scan with Defender, it crashes. No problem, I was not expecting it to work anyway. When it comes to my per_core I've just raised the lowest core from x48 to x49. I might try to set the rest of the 3 cores at x50, actually I did, but I am facing a crash in Excel 2016, trying to sort a big file, more than 65000 rows. Perhaps though this is a problem of a recent Excel update. Most probably, that it is!
This microcode update, and the rest of them as well, have really helped me and improved my system.@d0mini
, you could create a new thread but, personally, I would wait for more people to present concrete results (with screenshots and all)
When it come to per_core? Here's my personal and subjective opinion
, in a spoiler as it is off-topic.Warning: Spoiler! (Click to show)
I had three i7-4790K CPUs. I purchased the first one. Two months later I replaced it via Intel's Protection Plan, because it could not stabilize at 4800 MHz, no-matter-what. The second one could do 4800 but it could not pass that limit -- and it needed around 1.4V for it... A year later I made use of Intel's Warranty and got my third chip, the one I'm still having. It was (is) the best overall, it requires less V, but it could not pass 4800, on all four cores (until this microcode update).
So, I started playing and using per_core. Intel uses it,so why not? I stabilized x48 x49 x49 x50, before the update, like this: I set one active core at x50, in the BIOS, and run the x264 for like 30 minutes. I already knew that my chip can complete 10 loops (x264) at x48 with 1.380V, override VCore in the BIOS. So... I set 1.4V adaptive in the BIOS, and called it a day! I am sure that "1000 serious overclockers" would laugh at me, at my method. For around two and a half years now, 5 - 6 months per year, winter time mostly, I am using this per_core profile! I do not recall if I have ever crashed... Perhaps once, I think? Something like that. Not more. I am not a demanding user, and this a Home computer. I do whatever I want to do, and it just works. Without any issue, ever! Perhaps it's worth mentioning that , under this profile, I have plenty of times installed the Insider builds Microsoft is developing, for Windows 10. I participate in that. No problem, ever. So, I have the right to call it "stable for me".
If one cannot reach further, per_core is the only way.