This is great!

Hi bukhalmae145 and thanks.

Latest BIOS update (changes from previous mod in bold);

• CPU Type, Signature (CPUID), Stepping & µcode displayed on 'Overclock' page at the bottom
• Memory 'RTL-IOL Configuration' menu unlocked (read only)
• Advanced 'Power & Performance' Menu unlocked
• Advanced 'OverClocking Performance Menu' unlocked
• Advanced 'System Agent (SA) Configuration' menu unlocked
• Advanced 'PCH-IO Configuration' menu unlocked
• Speedshift enabled by default
• XTU Interface enabled (shows 'Memory' tuning option in Intel XTU)
• XTU 'Real Time Memory' timing unlocked in XTU (shows Secondary and Tertiary RAM timings - read only)
• PL4 limit increased to maximum 1023999
• iGPU enabled by default
• IRST Premium & OPTANE enabled by default
• RAID OROM & EFI modules updated to 17.8.3.4687
• VBIOS updated to 1062 (VBT 209)
• GOP updated to 1109 (VBT 228)
• 906EA µcode downgraded to 70
• 906EB µcode downgraded to 72
• 906EC µcode downgraded to 84
• 906ED µcode downgraded to AA

1E379114_mod6.zip

Zitat von chinobino im Beitrag #57

---

[quote=""|p121027]

---

@OneShot Vdroop disabled makes the CPU unstable for me even at stock speeds. Looks like you're getting some good results @ 4.9 GHz

Update for new BIOS v1.15 unlocked (changes from previous mod in bold);

• CPU Type, Signature (CPUID), Stepping & µcode displayed on 'Overclock' page at the bottom
• Memory 'RTL-IOL Configuration' menu unlocked (read only)
• Advanced 'Power & Performance' menu unlocked
• Advanced 'OverClocking Performance Menu' unlocked
• Advanced 'System Agent (SA) Configuration' menu unlocked
• Advanced 'PCH-IO Configuration' menu unlocked
• HPET unlocked
• Speedshift enabled by default
• XTU Interface enabled (shows 'Memory' tuning option in Intel XTU)
• XTU 'Real Time Memory' timing unlocked in XTU (shows Secondary and Tertiary RAM timings - read only)
• PL4 limit increased to maximum 1023999
• IRST Premium & OPTANE enabled by default & set to UEFI mode
• Restore AC Power Loss set to off by default
• VBIOS updated to 1062 (VBT 209)
• GOP updated to 1109 (VBT 228)
• RAID OROM updated to 17.8.3.4687
• EFI RAID module updated to 18.30.0.4887
• 906EA µcode downgraded to 70
• 906EB µcode downgraded to 72
• 906EC µcode downgraded to 84
• 906ED µcode downgraded to AA

1E379115_mod1.zip

Zitat von chinobino im Beitrag #65

---

Update for new BIOS v1.15 unlocked (changes from previous mod in bold);

---

@Oneshot You're welcome!

I haven't really had a chance to check performance but I expect it to be the same as v1.14 as only ME FW update was mentioned by EVGA.

Zitat von chinobino im Beitrag #67

---

@Oneshot You're welcome!

I haven't really had a chance to check performance but I expect it to be the same as v1.14 as only ME FW update was mentioned by EVGA.

---

@OneShot By default HPET is enabled in all EVGA stock BIOS but hidden.

If you check in device manager you can see that it is present with Hardware ID 'ACPI\VEN_PNP&DEV_0103' in device manager;



On my system HPET is enabled in the BIOS but useplatformclock is not set, which is the default value for Windows.

It means that HPET should be available if required by certain programs, as stated by Intel here all the way back in 2004;

Zitat

---

The timers are defined such that in the future, the OS may be able to assign specific timers to be used directly by specific applications.

---

@OneShot - You can test with timers BIOS HPET On/Off vs BIOS On/Off & BCDEdit useplatformclock set Yes/No, you will see a difference with BIOS HPET Off, even when you still see device in device manager
I posted an image of this kind of test and some info, below the "Change Log" area of the first post in this thread
[OFFER] Gigabyte Z390 M Gaming UPD + Completely Revised Blue Theme

Many users think it's still enabled once disabled in the BIOS now, this is only due to how Win10 still shows it in device manager. This is especially when someone like me has to mod/change the setting, while still leaving option hidden in BIOS
The BIOS setting does work, it's not placebo, it just does not disappear from Device manager now in win10, like it used to in XP/Win7.
I am not certain, have not tested, but you may be able to uninstall/remove it from device manager in Win10, once disabled in BIOS? (just guessing out loud )

Zitat von Lost_N_BIOS im Beitrag #70

---

I posted an image of this kind of test and some info, below the "Change Log" area of the first post in this thread
[OFFER] Gigabyte Z390 M Gaming UPD + Completely Revised Blue Theme
I am not certain, have not tested, but you may be able to uninstall/remove it from device manager in Win10, once disabled in BIOS? (just guessing out loud )

---

@Lost_N_BIOS Thanks for the info @OneShot

I just set 'bcdedit /set useplatformclock yes' and rebooted and my system became laggy and unresponsive with 100% CPU use.

I then set 'bcdedit /deletevalue useplatformclock' and uninstalled the HPET device, disabled HPET in the BIOS, shutdown the PC and removed all power.

When I rebooted the device came back in device manager and I can still set 'bcdedit /set useplatformclock yes'.

Zitat von OneShot im Beitrag #71

---

I think that there is no point in disabling it in the "device Manager" if you have not enabled it in windows forcibly via bcdedit

---

@OneShot - You're welcome! In regards to /set useplatformclock - it's enabled/yes by default in Win10, provided you have not ever ran BCDEdit previously to disable or delete it

@chinobino - Test this, disable in BIOS, reboot to windows >> BCDEdit /set useplatformclock No/False, then reboot and see if you can then uninstall from device manager, then reboot again and see it it comes back on rescan for missing devices.
That's what I meant, I was unsure and had not tested. I am not sure if this is = to what you did above or not? If outcome is the same, then my guess/idea about this = fail
It would be nice if it worked, since many coming from Win7 immediately check there and think it's still enabled even once disabled in the BIOS, since "before it would be gone from device manager once disabled in BIOS @ Win7"

But yeah, once disabled in BIOS, it does not matter, depending on what you're concerned with.
In my linked test, check the image close, timers looked better to me with /set useplatformclock YES + BIOS Disabled HPET vs /set useplatformclock NO + BIOS Disabled HPET

** Of note here, I do not game, make audio, video etc, so HPET does not affect me either way.
I only did the test and made that image/info so I could link users to that whom I sometimes hard disable HPET for in their BIOS without making it visible, so they'd see and know a way to check/confirm to themselves it was disabled vs their stock BIOS
I always say to myself, "If they need it disabled for some specific purpose, and it's really giving them issues, then they'll know right away it's disabled and not need visual confirmation"
But you know how the mind acts, without seeing a setting + device manager still having it, some may think what I send them is only meant as placebo as mentioned - not the case and I needed a way to show users who may feel this way.
So, summary, my BCDEdit + BIOS test is ONLY for this reason, setting things one way or another between the four mentioned possibilities here, may work differently for different usage/problem scenarios.
Some may have better luck with useplatformclock yes/No and BIOS disable/enable etc, my info is just meant as quick was to see immediately that it's disabled in the BIOS even if you cannot see the setting (in those kind of mod BIOS cases I mean).

Zitat von Lost_N_BIOS im Beitrag #73

---

@OneShot - You're welcome! In regards to /set useplatformclock - it's enabled/yes by default in Win10, provided you have not ever ran BCDEdit previously to disable or delete it

---

@OneShot - See, Yes, ^^ That's what I meant, and found in my quick testing too
Sorry, I don't game, so I am not sure what way is the best to set any of this in regards to that.

Test your games directly each way and see which works best for you, setup one scenario with each of the following -
BIOS Disable HPET and /set useplatformclock YES
BIOS Disable HPET /set useplatformclock NO

Then you could also do for completeness -
BIOS Enabled HPET and /set useplatformclock YES
BIOS Enabled HPET /set useplatformclock NO

Then you will know which is best for your games.

Yes, EVGA can only enable BIOS HPET, but Microsoft does the useplatformclock YES by default