I asked this in one of my other threads but as that was regarding a different issue, most of you might not have read it. So here's hoping someone has some pointers as I'm not one for messing about too much in the BIOS.

I'm now using the ASUS TUF Gaming Z690-Plus WiFi D4 and Intel Core i5-12400 

The UEFI/BIOS is a rabbit warren of settings, so if anyone has any tips on what I should change from default, please chip in (pardon the pun!).

General as well as specific MSFS tips welcome. I've found that enabling XMP causes CTDs in MSFS every time so I've had to leave that alone.

Not sure if I can give you any tips as I don't have your board, building in a Z690 Apex at the moment.

Does your board have AIOC? In the past, auto overclocking was frowned upon, but things have changed. Even legendary overclocker and YouTuber de8auer says that overclocking this platform is a bit of a waste of time and AIOC is probably the best option.

With AIOC you run stress tests first so the algorithm knows what your CPU and cooling can do and then it sets the overclock for you. It even monitors over time.

The nice thing is, you can then manually tweak voltage down if you like, set temp limits, voltage limits and optimism levels.

If your board doesn't have AIOC, then yes it will be manual overclocking required. But don't expect miracles, Intel CPU's these day's are pushed closer to the limits out of the box, so signifcant overclocks are a thing of the past.

For tips on overclocking your CPU and board manually, Google for articles and look on YouTube for videos.

My advice, after overclocking for quite a few years, is KEEP IT SIMPLE. Don't get bogged down with a myriad of settings changes. Change the minimum required.

51 minutes ago, martin-w said:

Does your board have AIOC?

The TUF Gaming board doesn't support AIOC.

 

54 minutes ago, martin-w said:

de8auer says that overclocking this platform is a bit of a waste of time

Interestingly, he's overclocked the i5-12400 (non-K) CPU that I have.  However, Intel have warned against doing it as it risks damage to the chip.

I will give that ASUS video a watch but I've never been one for overclocking, so I may just leave well alone.

But what I am interested in is all the various other tweaks in the BIOS, most of which go way over my head and may therefore be best left alone too. However, I'm curious what useful (and safer) settings may be hidden away in that labyrinth of settings. I'm trying to tackle the XMP issue which is causing CTDs (only in MSFS) in another thread, but anything's up for discussion in this thread (as long as it's related to this mobo!😁 ). This PC came with an ASUS Prime 450M but either the BIOS was simpler or I just never got that deep into it before swapping it for my ill-fated MSI board which prompted me to buy the 3rd mobo this PC has had since I bought it in mid-2020!

14 hours ago, 109Sqn said:

I will give that ASUS video a watch but I've never been one for overclocking, so I may just leave well alone.

 

I do apologise, I should pay more attention, I misunderstood and thought it was OC BIOS settings that you were after. 

 

14 hours ago, 109Sqn said:

But what I am interested in is all the various other tweaks in the BIOS, most of which go way over my head and may therefore be best left alone too

 

You shouldn't really need to touch any of them. If I'm not overclocking then its just set XMP and leave it at that. Everything else to optimised defaults. If you have any issues then yes, a tweak or two might be required.

I notice you have a thread regarding XMP, so I'll comment there.  

5 hours ago, martin-w said:

I do apologise, I should pay more attention

No problem!

 

5 hours ago, martin-w said:

You shouldn't really need to touch any of them. If I'm not overclocking then its just set XMP and leave it at that

The less I have to do to get the best results, the better. Less to regret later! The BIOS is a great toll if you know exactly what each element does, but even though I've years of experience building my own PCs, 99% of BIOS settings go over my head. I liken it to medicine - the public say "bruise", the medical profession says "haematoma". Something simple can sound far more complicated once tech speak is used.