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.

Zitat von Lost_N_BIOS im Beitrag #46

---

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.

---

@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.

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.

Zitat von petterkkk im Beitrag #52

---

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.

---

Zitat von st1cky im Beitrag #51

---

@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.

:)

---

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