@amd_comeback - That doesn’t matter, been using that for a year now I think. I don’t use AMIBCP anyway, but it doesn’t work for these kind of usual menu edits anyway (when it “would/should” work, before Gigabyte redid the layout outside of the norm for AMI)
Some (read very few) can be made visible with AMIBCP, but only in already visble menus. Most don’t even work that way anymore for their new BIOS, you just have to unsuppress in setup module (something AMIBCP can’t do, and doesn’t touch aside from textual edits)
For the Acer, this is wrong thread. I don’t know anything about that, I haven’t had time to get into that thread yes. General answer would be "No’, not for OEM BIOS like that, anything more specific or direct will have to wait until I can look at the BIOS (And I hate Insyde BIOS, so I doubt I can help)
@petterkkk - Make an exact list (in full, in a single post) and make it specific to what you want, leave nothing to me, this means leave no choices to me and don’t tell me to “also do other settings there/related etc”
Be exact, list each item you want changed by it’s exact name, and what you want it set to.
EZ RAID only works once two or more drives are connected, if you want to run single mode RAID, set RAID (Intel RST blah blah) at the SATA Page instead of AHCI, or connect a second drive for a minute to enable RAID at the EZ Mode page, then you can remove later.
Hmm, sounds confusing now that I re-read what you said. Obviously you have RAID working, you have two SSD’s in RAID 0, so I’m lost now how you think RAID isn’t working??
PCIE can only RAID with PCIE, at least I think that’s what the manual said when I looked last time (you can’t even RAID 2 PCIE NVME’s if they are not both PCIE type too, ie if one PCIE SATA NVME and one PCIE PCIE NVME = can’t RAID)
@Lost_N_BIOS Ok, here comes.
* HPET disable (off is using my last bios you made as base)
* TCO Disable (if not default off)
* Watchdogs disable, they are randomly placed atleast in AMIBCP. (Intel ICC, ASF, acpi?/rc-acpi?, debug)
* Use the last bios you made for me as base (which has HPET disabled)
* Enable Audio DSP under HDA Sound Settings (sound)
* Enable post/pre-processing options for the DSP (sound)
* Disable WakeonVoice(WoV) (sound)
* Set the preferred WoV to Intel. (sound)
* Enable HDA-Link as Non-UAA (sound)
* Enable I2S mode (sound)
* Select Realtek codec from list below I2s option (sound)
* Enable DMIC 0 and 2 (sound)
* Enable SWND #2 (sound)
* Disable HyperThreading (CPU)
* Set amount of cores to 6, not "all" (CPU)
* Enable C6RAM (CPU)
* Disable C-states, all of them
* Disable ASPM for all but keep it at auto for DMI
* Set default monitor/screen and card to PEG and PCIE slot 1 (theres two options, one for PEG, another for PCIE)
* Disable internal GPU (I can do it aswell though)
* Disable AMT/ASF but keep ASF tables visible (another option)
* Enable network stack (but dont enable any other options)
* Enable PCI Latency Optimization & MSI (and MSI-X if it exist)
* Set RST raid interrupt type to MSIX
* Disable Optane support for RST
* Enable raid on cpu-option (keep, its already enabled)
* Set RST PCie remapping to auto
* Enable Cpu wakeup timer if not already enabled
* Disable Intel Speedshift & Speedstep (or I can do it)
* Set memory allocation for internal gpu to minimal (sometimes 0, sometimes 32mb etc)
And thats it. Skip the ones I can do myself to spare your time for more fun stuff to do:)
First two already done, please see notes below and redo this list
* Watchdogs disable, they are randomly placed atleast in AMIBCP. (Intel ICC, ASF, acpi?/rc-acpi?, debug) << This is not exact, please correct
* Use the last bios you made for me as base (which has HPET disabled) << Of course 
* Enable Audio DSP under HDA Sound Settings (sound)
* Enable post/pre-processing options for the DSP (sound) << Not exact, please correct
* Disable WakeonVoice(WoV) (sound)
* Set the preferred WoV to Intel. (sound) << Pointless, you asked to disable above, so no time will be wasted here
* Enable HDA-Link as Non-UAA (sound)
* Enable I2S mode (sound)
* Select Realtek codec from list below I2s option (sound)
* Enable DMIC 0 and 2 (sound)
* Enable SWND #2 (sound)
* Disable HyperThreading (CPU)
* Set amount of cores to 6, not “all” (CPU) << Pointless, no time wasted here
* Enable C6RAM (CPU)
* Disable C-states, all of them << This you can do via BIOS bug #1 or #2 (One setting disabled all at once)
* Disable ASPM for all but keep it at auto for DMI
* Set default monitor/screen and card to PEG and PCIE slot 1 (theres two options, one for PEG, another for PCIE)
* Disable internal GPU (I can do it aswell though) << Yes, you can do this directly in stock BIOS, this should not be in this list
* Disable AMT/ASF but keep ASF tables visible (another option) << Not exact, please correct… If you think Disable ASF makes something go away, then it can’t be disabled. Additinally, if you can already see this, to be concerned with something going away, then remove from this list I don’t need to edit you can do in BIOS
* Enable network stack (but dont enable any other options) << This directly visible in stock BIOS I think, if not, for sure via Bug #1 or #2 (may need UEFI mode enabled or disabled first)
* Enable PCI Latency Optimization & MSI (and MSI-X if it exist)
* Set RST raid interrupt type to MSIX
* Disable Optane support for RST
* Enable raid on cpu-option (keep, its already enabled) << Then remove from list
* Set RST PCie remapping to auto
* Enable Cpu wakeup timer if not already enabled << Not exact, please correct
* Disable Intel Speedshift & Speedstep (or I can do it) << Yes, both directly visible to user in stock BIOS, either as-is or via bug #1-2
* Set memory allocation for internal gpu to minimal (sometimes 0, sometimes 32mb etc) << Null once Internal GPU disabled, so does not need to be here
About the Timers, it changed in Windows 10 1809.
My guess its a little bit slower then prev. versions and it isnt just an overlay.
It could be linked to some security patches they added to the kernel since Windows 10 1809, Hypervisior.
I wouldnt bother with it, just use HPET Disabled or Enabled in BIOS.
I recommend, testing HPET On/Off then tests with Mousetester, after that you go for useplatformtick yes. Same Test with HPET, but this time with useplatformtick enabled.
And i recommend to test these steps with Timerres ( lowest ),too.
My feeling is Mousetester is more Static with HPET ( BIOS ) Disabled & useplatformtick ( BCDEDIT ) Enabled & Timerres ( Lowest ).
And Ingame it feels little bit faster with HPET Disabled (BIOS).
Yes, I disable in BIOS + Leave useplatformclock enabled for best result (see my test image on previous page @st1cky ) That gives best/lowest freq
Thanks for reply about platformtick, I’ve never heard anyone mention this, hopefully he can figure out on his own about that.
With useplatformclock Enabled and(+) HPET Disabled in BIOS, you will get the PM/ACPI Timer (QPC Bypass of the 10 Mhz) but it will decrease the overall performance, like fps. ( Some People wanted to test it, but lower Freq. doesnt mean the Timer is better, this Timer is normally disabled. )
He can test it, i would only change HPET in BIOS not OS Side. 
So if we disable HPET inside BIOS, HPET is disabled.
But when we use the command for OS LEVEL HPET Timer > useplatformclock it will use the ACPI Timer instead, because HPET is disabled in BIOS.
So these Switches are basically,
Windows 10 Default:
USEPLATFORMCLOCK = Disabled ( Forces usage of the platforms’s clock source as the system’s performance counter. It will use HPET or ACPI Timer depends on the BIOS HPET Switch)
USEPLATFORMTICK = Disabled ( Uses the OS Platformtick )
Everything related to Platform is Windows ( OS Level )
DISABLEDYNAMICTICK = NO ( Internet Says, its a Feature related for Power Saving specially on Laptops. )
Recommendet Settings are ->
bcdedit /set disabledynamictick true
bcdedit /set useplatformclock false
bcdedit /set useplatformtick false/true -> it varies between OS Builds, needs sometesting with 3rd Party Tools.
I dont know why HPET inside BIOS still affects the OS, because normally Win10 doesnt use HPET at all. It got replaced with QPC=QueryPerformanceCounter.
So testing HPET (BIOS) separately, is advisable.
@st1cky - Thanks for the further info! I still/only ever see QPC, no matter what. I never see HPET, see image on post #28, I tested useplatformclock Yes/No w BIOS HPET enabled + BIOS HPET Disable w/ useplatformclock Yes/No.
Basically, your first sentence is what I said to do, ie do nothing in OS (so useplatformclock Yes by default) + Disable HPET in BIOS = lowest freq 3.xx shows in CPU-z timers in this manner (QPC)
But, then your last comments say opposite of this (useplatformclock = False)…
So, you can see why I’m always confused about this 
I guess it doesn’t help that this setting or how it affects things do no matter to me, so I’m not familiar with what it does/affects etc
Its actually pretty easy to understand, i try again xD
So Default Windows use QPC as Timer. The QueryPerformanceCounter is more precise because it use the Base(STOCK) CPU Frequency as Time and not the actually switching CPU Frequencys.
Windows 10 - didnt changed the Timer they just modified something ( since Windows 10 Build 1809 ) , maybe they wanted everyone to has the same QPF (QueryPerformanceFrequency).
Looks like QPF is locked, could be because of Security.
Since Microsoft didnt gave us any Statement about the Timer, its hard to know and the circle who is working on that specific thing is very small. My Guess they have no clue.
We just need to understand here how the switches are working, how the diff. Timer works Internally is much more complicated.
Basic.
Platform = OS Level
QPC/F Downwards Windows 10 1809 - QPF is LACPI Freq.
QPC/F Upwards Windows 10 1809 - QPF is 10 Mhz.
TSC & TSC Invariant is linked to all ACPI P-, C-. and T-states.
useplatformclock yes - Forces Windows to use HighPrecisionEventTimer(HPET) if not available LAPIC | useplatformclock no - Forces Windows to dont use HighPrecisionEventTimer(HPET), ( I think setting it to no has no effect, since Windows 10 dont use HPET as default ).
There are 2 Variables to keep in mind. The BIOS Setting for HPET is important here.
BIOS: HPET ON = HPET Support granted for OS.
BIOS: HPET OFF = HPET Support denied for OS. ( Windows 10 here, cant use the HPET Timer so it will use the (L)ACPI Timer. )
useplatformtick yes - Forces Windows to use the Platformtick | useplatformtick no - Forces Windows to dont use the Platformtick. ( I think setting it to no has no effect, since Windows 10 dont use PlatformTick as default ).
Using LAPIC Timer for Windows 10 will lower the QPF. But what i saw is decreased Performance in FPS. Maybe playing around with the following Settings on OS Level, can change the behaviour for the LAPIC Timer.
2
3
4
5
6
7
uselegacyapicmode [ yes | no ]
Used to force legacy APIC mode, even if the processors and chipset support extended APIC mode.
x2apicpolicy [ enable | disable ]
Enables or disables the use of extended APIC mode, if supported. The system defaults to using extended APIC mode if it is available.
Update:
disabledynamictick [ yes | no ]
Dynamic Ticks are a feature that lets windows stop the system timer when nothing is happening in order to conserve power. This is nice for portable and battery systems but can be a problem for desktops, especially since the tickless mode has been known to cause strange issues on some systems; especially when gaming or engaged in other media related tasks. Source: https://updatecontroller.wordpress.com/2016/08/08/disabling-dynamic-ticks/
That is how i think it is working, if im wrong. Someone can correct me :)
@st1cky - Thanks for in-depth explanation!
My simple test contradict some of what you mention, that is why I was confused, and still am I suppose
https://i.imgur.com/htT6gNp.png
My Testing on Win10 (Latest) -
HPET Enabled in BIOS
useplatformclock YES >> QPC = 24
useplatformclock NO >> QPC = 10
HPET disabled in BIOS
useplatformclock YES >> QPC = 3.58 (@4.1GHZ CPU)
useplatformclock NO >> QPC = 10
ACPI - Always Same/Same no matter what
UsePlatformTick + disabledynamictick - I never seen anyone mention ever until this thread, nor had I heard of it until this thread.
Seems like everyone that cares about HPET in general should forget they heard of it as well, based on what you mention.
Except unless maybe it helps those guys with audio issues more than HPET fiddling does by itself.
For me none of this matters, and only reason I am looking at any of this, was for a way to show end user HPET Disabled in BIOS = True
All the other stuff you guys discuss I don’t know or need to know about in general. Just so you know where I come from in this kind of discussion, so you know my reasoning for quick simple test etc.
@Lost_N_BIOS
Everything seems correct, Windows 10 use QPC as Default.
Check Screenshot. 
ACPI and (L)APIC can be very confusing and i need more to check out and read into it. But i was reading, that if HPET is locked then LAPIC will be used. So i think its the LAPIC Timer. ( I can be wrong )
Yes ACPI doesnt change since Windows 10 use QPC as Timer. So its probl. a combination like this HPET → QPC(F) or LAPIC/TSC/TSC-V/… → QPC(F).
Whats confussing,too. Im always reading HPET uses 10Mhz-14Mhz. ( 24 Mhz could be something else,too. But its 100% related to the HPET switch. )
There is a lot of wrong Information spread around, i will look more into it. And correct my self if i found something.
Ok, new list:
* Disable ACPI Autoconfiguration
* Disable S3 Suspend
* Disable hibernate
* Disable TCO Timer
* Enable PCI Latency Optimization and MSI, should be same place. (and MSI-X if it exist as option of intterrupts)
* Serial Intterrupts = Quiet, not "realtime" or whatever it may say
* Enable DSP for sound chip in Audo options, enable I2S-mode to link Intel->Realtek codec, and codec to Realtek. This is correct, not mistake. Believe me, this is how Dell does things on their XPS 13 9343 too.
* Enable C6RAM (CPU)
* Set edRAM to HW-mode
* Enable GNA Device
* Enable DMIC 0 and 2 under advanced audio settings.
* Enable SWND #2, same menu as above
* Disable WakeonVoice(WoV) (sound)
* Disable HyperThreading (CPU) - i dont want it nor do I have it.
* Use base of last one again, with HPET hard-disabled as usual.
* Disable TCO Timer
* If there is possible, set timer to use TSc timer (nearest BIOS) - Dont know if you edit in HEX or if possible at all.
* Set default monitor/screen and card to PEG and PCIE slot 1 (theres two options, one for PEG, another for PCIE iirc)
* Security device = dGPU (not viisible by bugs OR by default - only on off)
* ENable the "already pressed OPROM key" option that exist in all Ami bioses. Dont know where.
* All OPROM Video settings leave default but please enable the OPROM (not in RST menu) but in PEP Mitigation list (I dont understand what is on or off - enable to disable or disable to enable?) so I can press ctrl+i to enter raid setup (atleast in CSM - never worked forme).
* I have seen option to enable IRSTe(nterprise) in AMIBCP before. Enabling it broke raid completely. What about swapping out OPROM with latest IRSTe instead? I dont have optane nor VROC and want the most robust, since irstEnterprise supports Linux.
I currently do not know what/how the intel ME affects computer and thus the menus there I have no clue. I did not,get to reflash Intel Me after last bios though. Maybe not an issue at all. Do what you usually do, or leave as is.
A
Thanks, much appreciated.
-------------------
I work at Barco where we do alot of clock and timer setups. One project we included a 24Mhz high precision event timer from Intel. TSc is by far fastest.
I noticed on my ASUS BIOS, when HyperThreading is Visible, its enabled even without supported.
And in Windows, it says HyperThreading Enabled, you know why this happens? My CPU Doesnt support it. ( Only for Support or is there something else hidding in the background? )
The other settings you mentioned i tested already, had no gain, except for the Audio Settings didnt tested it.
But i noticed Soundcards and Sound overall, affects hitreg.
Makes sense then, since on Win10 I get 3.xxGhz with >> HPET disabled in BIOS + useplatformclock YES >> QPC = 3.58 (@4.1GHZ CPU)
@petterkkk - On ME FW, you can update it in BIOS as you flash, or with FW update tool within windows/DOS. If you don’t know about Intel ME FW, then I suggest it doesn’t matter to you, leave as is, or ask me to update to latest version in BIOS update
Gigabyte does not lock any of this down, so you can make it whatever you want, ideally as-is or latest version is best.
On RAID, you must setup RAID array with whatever option you want set in advance, plus you need to use other drivers.
I don’t think you can easily switch between the two types, you have to decide before you build the array, or backup and mirror current array back onto a new rebuilt array with other option, then test and compare.
This >> * All OPROM Video settings leave default but please enable the OPROM (not in RST menu) but in PEP Mitigation list (I dont understand what is on or off - enable to disable or disable to enable?) so I can press ctrl+i to enter raid setup (atleast in CSM - never worked forme)
Makes no sense to me, you must be exact. You can’t say leave all video oprom settings at default, but then tell me to change something without telling me the exact thing you want changed (AND this (Video setings) has nothing to do with Intel RST RAID)?? So as you can see, all very confusing, and not exact like I requested.
Additionally, sounds like you do not even know what any of this does, why are you changing it??
To enter RAID, you must NOT use EZ Raid to build the array. Set RST in BIOS, reboot to Intel Control+I and build the array.
CSM on or off may matter here, if your BIOS only has one rom for UEFI (CSM Disabled) or Legacy (CSM enabled), and you have used incorrect choice at RST/RSTe.
BIOS May only have one or the other RST/RSTe and one/both may only be one type (legacy/UEFI), so you’d have to confirm what you want and then make choice based on what is possible.
I checked your BIOS, the one I updated for you, and it has the following RST Roms
17.8.0.4507 - UEFI
17.8.0.4507 - oRom (Legacy)
So you cannot use RSTe, unless you have me replace both of those with RSTe, or only UEFI with RSte (And then only use CSM disabled)
Yes, I can swap in RSTe, if your chipset supports that, check the EFI RST download page and see, if it does let me know and I can switch, but you will need to rebuild array probably, unless it just broke it before because you enabled an option in BIOS edit for a non-present rom module (since no RSTe in default BIOS)
Additionally >>
* Enable DMIC 0 and 2 under advanced audio settings.
* Enable SWND #2, same menu as above <<< Not exact, unless you mean Enable SWND 0 and 2? If that is what you meant, please say this on your re-write of this list.
This, makes no sense to me, or not exact
* If there is possible, set timer to use TSc timer (nearest BIOS) - Dont know if you edit in HEX or if possible at all. <<< Tell me exactly what you want set, it does not matter how I edit it, you give me the setting you want out of shown available options and I apply it 
This, not exact >>
Enable PCI Latency Optimization and MSI, should be same place. (and MSI-X if it exist as option of intterrupts) << it’s either there, or not, and if so you see it and tell me what you want set exactly, for any and all settings one by one.
Makes no sense, please tell me exact setting and what exactly you want set. Additionally, for ALL of these, please give me exact location where you are looking at them (Example >> Advanced >> PCH >> xxx Submenu >> Setting xxx)
Security device = dGPU (not viisible by bugs OR by default - only on off)
ENable the "already pressed OPROM key" option that exist in all Ami bioses. Dont know where. << Not a setting, never heard of what you mean, if you see in AMIBCP give exact location I will set. If this is the exact wording/spelling, then it’s not a BIOS setting (I searched "pressed" nothing resembles this)
So, sorry to add to the mess, but I need this all to be 100% exact to what you want set, using the exact names shown in BIOS and their locations you are looking at them in AMIBCP
This is because some are dupes and some are in hidden/debug areas, since you have a huge list I need to know EXACTLY what you are looking at when you want me to change something.
So, please redo the list, with my above comments in mind and then I can work on it again for you.
Hi @Lost_N_BIOS
Is it possible to edit default IOL Offsets for these UEFIs? Other boards let you manipulate these values but the Master does not. I believe Gigabyte has these defaulted to 21 if I’m not mistaken. Also, RTL values seemed to be bugged in all versions. The board doesn’t respect the values manually set at all. Wonder if there’s a way to manually set them via bios modding.
Thanks as always. I’ll be sending a PM to donate for all the help you’ve provided. Def been more of a help than Gigabyte.
@whosalty - Do you mean IoLatR0D0 << If so, yes, these can be made visible if not already? (x3 or 4) If you can’t see them now, try looking using bug 1 or 2 from what I mentioned in post #9
RTL, this is not something I can “fix” if it’s an actual setting function issue, I only know about menu manipulation not actual functionality/editing of the setting action/processes.
Do you simply mean what you set is not applied? If yes, I suppose a value could be manually set via BIOS mod, but then if that works each time you want to change you’d have to redo the mod.
RTL is tied to other settings, maybe you are setting it first and then changing something else making it auto-default to the next area where it would fit in with the other setting you changed (I think tFAW and the one tied to it are also somewhat tied to certain ranges of RTL, like a strap range)
Try setting it last and see if it sticks for you.
I will look into both of these on my M Gaming, and see if I can see the setting, if not how to make visible (if edit needed, or if you can access via bug), and I will check out RTlL’s too. What are you checking applied value in windows with, aida64?
Awesome, look forward to the PM and I appreciate it
No, Manually setting RTLs doesn’t work at all on this board. Been a constant complain in threads dedicated to the board on the net. One way to manipulate them is to have access to Iol offsets which this board doesn’t give you access to. IoLat settings are already visible on this board however thanks for looking into it. Hopefully Gigabyte fixes the issue one day but I doubt it as these boards have been out for quite sometime now.
Thanks, I’ll have to look into this on my board and see what I notice. If you can access IOL offsets, which you say affect the RTL and these are already visible, how do these interact with RTL and does changing IOL actually change RTL too?
If yes, you may need to set certain IOL to get whatever RTL you want manually? Like I said, I’ll have to check this out, I’ve not been keeping up on any complaints like this, so it’s first I’ve seen this discussed (I believe you, just wasn’t aware)
Yes, that is quite odd if there is a lot of complaints and they haven’t fixed yet 
BTW, not sure if I directly answered previously, but yes, if there is some default value set I can probably change that to something else for you if you want (kind iffy sometimes if “Auto” is default for a numeric entry, usually pulled from SPD/XMP, but I will check)
What are you using to look at live/current IoL’s in windows? I checked with AIDA64 and it only shows RTL’s, or is in the one right under that tIOL (I/O Latency)?
If IOL is that, I see 4T on mine in AIDA64 and in BIOS at JEDEC CHA/CHB column too, so I assume this is it. Well, if this is it, then changes here are not applied either?
* Edit - I changed 4 to 5, still shows 4 in AIDA64 and yes, I see same with RTL’s too still digging around and testing…
Maybe disable Round Trip Latency Training in Memory Training area will help? * Edit << Hard disabled this, didn’t make any diff. Next test, hard set value change to RTL (I assume this will work, but that would need done every time you want to change, will let you know result tomorrow - out of time right now )
* Edit @whosalty - Tested hard changed RTL in all possible areas, for a single digit increase, no effect.
So, to me this says they have messed something up and RTL is not configured/connected correctly to whatever it’s supposed to be connected with the actual setting programming to make the changes apply. So this is why any change fails to apply
Only thing left to test here is edited SPD+XMP, but I may not be able to write to any DDR4 I have, I’ll have to check on all the DDR4 I have and see if any are unprotected. But, even if so, I don’t have paid version of Taiphoon and to me it’s not worth spending $26 on this program
OK, I got the legacy one to boot up with ctrl+i - the problem I did not have enough SATA hdds as it only supports that. SO i created a new raid0 array with 2 hdds, and have a uefi setup created raid0 between two pcie ssds.
So I only want you to do ALL of the other stuff i mentioned, ditch the IRST-E. Leave as is.
but all other is important to me.
i can donate after u do it.
@petterkkk - PCIE NVME should be supported as well (maybe only in EZ RAID Mode though, I’m not sure, haven’t tested). But yes, to get into either RAID management areas you need to have at least two disks connected.
I was hoping to see new refined and corrected list from you, still some stuff from post #54 I need exact changes info and setting locations for the stuff you mentioned.
And thanks, yes, anything you donate my way would be greatly appreciated! Send me a PM once you are ready and I will give you details