Gigabyte Z690 Gaming X Ddr4 Drivers

0 views

Skip to first unread message

Ina Dottery

unread,

Aug 3, 2024, 6:12:47 PM8/3/24

to lingscofinleb

Hello, i've been recently messing with a Z690 motherboard and an Intel Alder Lake CPU

Managed to get Windows 7 installed, but it was tricky, decided to try an updated Windows 7 ISO with drivers (USB3, NVMe... etc) slipstreamed and tried out, found out Intel USB3 got updated enough that current driver infs lacked the IDs for the new chipsets and didn't recorgnize it, so i had to install using from another PC with modern Intel AHCI, then carry the drive over the system after the first stage of setup. I ended forcing one of the AMD USB3 drivers with success on the system.

I feel scared about how the scheduler works with a heterogenous CPU using SMT clusters. My Ryzen 5 3500u (which is not like that by any means) goes crazy high power in embarassingly parallel games like Football Manager or script-heavy mods such as Europa Barbarorum II for Medieval II Total War.

I did experience that during heavy ST workloads like Cinebench R20 single thread test, the process seems to hop across cores regardless if is a P-Core, Hyperthread of a P-Core or an E-Core, also noticied that Windows 7 sees the ADL CPU as a dual socket system

Hello! I have a gigabyte z690 elite ddr4 and get a bsod a5 after installing win7 on the first launch. I tried different builds, everyone has the same. p.s. CSM is enabled and XHCI is disabled.
What else can I try?

I don't know much right now and I may be extremely incorrect but if you're getting ACPI compliance BSODs, there is some kernel parameter or setting you boot with to not use ACPI. The fact that you got this already means 7 does not recognize the type of ACPI used in modern motherboards now, so we will have to wait for a modded ACPI.sys for this to work natively. As of now, you can disable ACPI on bootup. I think it was some key you hold in the boot menu of Win7.

If you can get the default CPU Affinity for explorer.exe to be on only the P-cores, this will have the effect of having all user-launched programs on the P-cores, and some of the "system" or "background" processes will be able to use the E-cores (or user can set specific programs to use E-cores through task manager). Not quite sure exactly how you could get this done, but perhaps making a task scheduler to kill and immediately re-start explorer with P-core-only affinity would work although it might look bad as the taskbar appears and disappears.