5ghz is still an extreme overclock for an i9 11900k if you don’t know what you are doing and it starts to sound like your PC store overclocker might not know what they are doing.
There are a lot of things that can throw an overclock off.
Not all CPU’s are golden sample winners of the silicon lottery and they just won’t hit 5ghz all cores without stupid vol
No all cooling solutions are up to the task and even a great cooler poorly mounted will cause issues.
Fill every dimm slot with DDR? That adds stress to memory controller and more often than not reduced your potential overclock.
Not all motherboards are made equal, some handle Overclocking very well, some very poorly.
Finally your PSU, it’s quality and whether all the power connectors are plugged in properly.
So, there are a whole bunch of variables that will throw an OC away.
Overclocking can be fun, it’s not terribly hard and there are always a lot of places to find information about how to do it and how to test that your overclock is stable.
I have no idea what your supplier did, but it sounds like it’s a far from stable OC and I’m not even sure there is a good reason to OC an 11900k either. It should be more than capable just at stock clocks and letting it boost up the cores it needs when it needs to.
What is your cooling? You cook your cpu with this settings! No wonder that the system crash.
Note: MSFS use AVX instructions. This is uncommon in games and must be in mind when setting up the OC.
If you are not knowing what OC does, disable it, regardless to what some supplier say. You wont sit yourself in an topfuel dragster without having an idea what this machine does with you when you lower your feet.
Reset anything to the defaults. Turn HT off. Watch youtube about OC until you get starting to get an idea off what it is. Then start to OC slow and mild by yourself. Step by step, not head through the wall.
Note again, your OC must be AVX stable! If you have f.e an 5,0Ghz OC with an AVX offset off -3 your PC will run with 4.7Ghz in MSFS. Pointless.
BTW: OC is no problem with MSFS at all. Here runs my trusty old 8600k@4,9Ghz allcore, no AVX offset with 1.245V (could probably get another 0.02V lower but its ok) and goes never above 67 degrees Celsius (watercooled). Rock solid! So what?
I have had oc’s running on my cpu and gpu since release and haven’t even had a handful of CTD’s since release.
I haven’t touched the voltage on the gpu or cpu left them alone.
With the my I9-9900K I found if I go over 4.9ghz I do start seeing crashes.
The limit for my RTX 2070 is a + 220 mhz core clock increase any higher the sim will crash, I have the memory clock boosted by 1000mhz but can more than double that, but wasn’t seeing any more improvements so kept it at 1000mhz.
The power limit on gpu is set to 114% and voltage is left alone.
I just use afterburner and let it run its tests to find a stable oc, then i adjust it slightly myself after.
Most of the issue’s with oc’s is people try pushing the oc’s to far.
Try to keep your oc as simple as possible at first. Reset your bios settings to default (press f5 in bios) Start with an all core clock of 4.9 ghz and use static core voltage. Set your ram profile to your ram speed (should be profile 1) set core voltage to 1.3. This should be more then enough. Don’t change anything else, just leave it all to auto. You might want to check out llc (load line calibration) and look online to find a suitable setting for your motherboard when overclockingm usally a average setting is fine. (Like when the options are 1-8 use 4.)
Save and go to windows. Download cinebench and run an multicore benchmark and watch your temps ans voltages using hwmonitor or something similair. Watch closely how the vcore is behaving. It will go higher then set voltage in bios in some occasions( like 1.345 or something like that). Your temps shouldn go to high with these voltages though.
If temps are good and voltages don’t go crazy, like towards 1.4 you can let the benchmark run for a few loops. When everything is stable for like 20 mins or so you should be good.
Now try setting your oc to 5ghz and see what you get. You should be able to get 5ghz easy with a 1.3 static vcore with a appropiate llc.
After evertyhing is stable you can try to achieve same results using an adaptive vcore and a negative offset value to match your static vcore used before.
Motherboards these days can go crazy with some cpu’s and give way to high voltages. Also there’s alot of settings in the bios wich will only make things harder. Also each manufacturer gives different names or meanings to their settings. This is why an manual overclock with these cpu’s is often given better results because default settings will try to up the vcore tp high and make your cpu downclock when it reaches a certain temperature.
At least this is the problem i had with my i9 10900k and gigabyte vision D motherboard. Running default settings will get my cpu up to 100c in no time and cpu will go down to 4.9 and still be around 90c under load. Now i’m using a all core 5ghz oc with 1.3 volts (up to 1.35 under load) and tamps won’t go over 80c (liquid cooling)
Let us know when it happens again. 5.1GHz isa bit much. This has te bery well stresstested to confirm it is stable. Hope you have a good cpu cooler for that?
I ran MSFS on an I9-9900K OC to 5Ghz with no problems. The issue is the DBX that pops up, randomly, “It appears you are overclocking you GPU and MSFS will shut down” I paraphrased and will post an image of the actual DBX the next time it comes up but this is BS!!!
I have a EVGA Kingpin Hybrid RTX 2080Ti with the LN2 BIOS and can push it to 2145 on the Clock and 8300 on the Mem all under 70 c. Why does MSFS care what I am running. My system is nowhere near over heating and the sim is running fine right up to the DBX and it locks up. Checking the OK button the Sim will shut down. NO CTD here. The last time it came up I had to use Task Manager to Kill MSFS. It takes 20 to 30 minutes to setup a flight, taxi and Takeoff in the PMDG 737 only to have MS butt in and tell me I am OC’g my GPU. WTF!
it does’nt.. it is a hint about a possible reason in a case where the impl catched a problem, thus simple a text.
I have a 2080TI with default factory OC and never seen that popup.
So far I remember, does the ln2 bios of that 2000$ card ( year 2019 ) increase the powerlimit extremly ( 250 → 520W or so ). Also the temp-limit are disabled. And also if we assume the watercooling system can handle 500W, exists other components on the system, like the PSU.
And let us remember… a high OC of a 2080TI is already 1800 / 7000 ( whats similar to the factory default of that card ). So, I not wonder about any kind of problems with that OC… the CPU OC I ignore for now.
In that topic we spoke about some possible reasons why some users get that popup , where OC is number one, but also others. Also the possible missleading error-text is mentioned.
FWIW I have mine OC’d by +800mhz on the memory and (I think off the top of my head) 170mhz on the clock speed. Anything more than that causes that crash, but only in MSFS.
That is pushing my already manufacturer OC’d card to it’s very limits so I’m totally ok with it, there has to be a limit somewhere.
Artifacts are often the first thing to show up on the screen when pushing OC too hard and I have not seen that in MSFS. If it is a driver issue it should suggest a particular driver version. Just seems to me this DBX is too vague to be of any real value in diagnosing the issue. Sounds more like a “Catch all” statement. All I know is I can push my GPU a lot harder than this in XP with no issues.
