Gigabyte Aorus Master x670e System 7 & 8
Hello! I don't think I see this covered in the open and closed issues. I apologize if it has. Some Gigabyte motherboards have 8 total fans. Mine, Aorus Master x670e, has three on ITE IT8689E, three on ITE IT8792E, and two on an Embedded Controller. The 6 fan ports on the two ITE chips work with Fan Control 2.50. The two on the Embedded Controller do not.
Here is a screenshot of HWiNFO showing this controller with comments about it being an "archaic" controller that might be unstable. Does this mean that it is unlikely that Fan Control would/could be expanded to handle this controller? The fans can be controlled by the BIOS and by the Gigabyte Control Center software.
Also below is a screenshot of the controls that Fan Control found. The default names Fan Control gives vs. the BIOS are as follows (I renamed them). Fan Control seemed to reuse some names, but they are indeed different controls. System 1 = Fan # 2 System 2 = Fan # 3 System 3 = Fan # 4 System 4 = Fan # 3 System 5/Pump 1 = Fan # 1 System 5/Pump 2 = Fan # 2 CPU = Fan # 1
I'm assuming that either Fan # 5 or Fan # 6 control the CPU_OPT fan, but I don't have a fan plugged in there to check. That would still leave another control that doesn't seem to control anything: neither controls System 7/Pump 3 or System 8/Pump 4.
Gigabyte does weird stuff. We just added in the support for the 2nd ITE chip which isn't controlled like other chips already, but that EC stuff I haven't touched on that. Probably yet another proprietary protocol required. Are you aware of any third party program than can "control" these fans, and not just read them?
In any case, support is from here : https://github.com/LibreHardwareMonitor/LibreHardwareMonitor Not from Fancontrol itself. So any further discussion would have to be in that repo.
I have a Gigabyte x870 Aorus Elite WiFi7 ICE.
With Libre Hardware Monitor (LHM) v0.9.4, I can successfully control all the fans connected to the board. However, when using Fan Control 2.50, I am unable to control the CPU Fan and CPU Opt fans.
I attempted to resolve this by copying the relevant library files from LHM into the Fan Control installation folder, but this did not resolve the issue. I still lack control over the CPU and CPU Opt fans.
With Libre Hardware Monitor (LHM) v0.9.4, I can successfully control all the fans connected to the board. However, when using Fan Control 2.50, I am unable to control the CPU Fan and CPU Opt fans.
I attempted to resolve this by copying the relevant library files from LHM into the Fan Control installation folder, but this did not resolve the issue. I still lack control over the CPU and CPU Opt fans.
LHM v0.9.4 uses WinRing0 driver while the current master, which ships with FanControl, uses PawnIO. This is very incompatible.
I have a Gigabyte x870 Aorus Elite WiFi7 ICE.
With Libre Hardware Monitor (LHM) v0.9.4, I can successfully control all the fans connected to the board. However, when using Fan Control 2.50, I am unable to control the CPU Fan and CPU Opt fans.
I attempted to resolve this by copying the relevant library files from LHM into the Fan Control installation folder, but this did not resolve the issue. I still lack control over the CPU and CPU Opt fans.
I have X870 AORUS ELITE WIFI7 ICE too. But i can see what it not stable control. Now i can see that fan 3 can't control. After restart FanControl i can't control CPU fan. I can see hat it`s random.
[V250] 28.11.2025 20:45:58: Unhandled exception (Application.Current.DispatcherUnhandledException) : System.NullReferenceException: Object reference not set to an instance of an object.
at FanControl.Domain.FileLogger.Log(Exception exception, String context)
at FanControl.ViewModels.Utilities.ControlUtilities.AutomaticCalibration(ControlViewModel controlViewModel)
at FanControl.ViewModels.Utilities.ControlUtilities.EditFanCalibration(ControlViewModel controlViewModel, Boolean suggestAuto)
at FanControl.ViewModels.ControlViewModel.EditFanCalibrationDelegate(Boolean suggestAuto)
at FanControl.MVVM.AsyncCommand.Execute(Object parameter)
at FanControl.MVVM.AsyncCommand.Execute(Object parameter)
at System.Threading.Tasks.Task.<>c.<ThrowAsync>b__124_0(Object state)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
In any case, support is from here : https://github.com/LibreHardwareMonitor/LibreHardwareMonitor Not from Fancontrol itself. So any further discussion would have to be in that repo.
Ah! Thanks. I'll see about contacting them.
On the X870 AORUS ELITE WIFI7 BIOS Version F8, none of the Fans can be controlled using FanControl V250
All Fans are connected to the same ITE IT8696E IC
Using V249 it was at least possible to control the CPU Fan.
I confirm ITE IT8696E - work. Sensors ITE IT8696E - work. But i can see ITE IT87952E with fans too - it not work (What it?).
Just upgraded to Aorus Elite X870 (non-ICE), Fans connected to my NXZT hub that is then connected through USB to the motherboard are recognized, without sensors, but Fans connected to the motherboard are not recognized...
When I hit the "Assist" setup, It cleared the whole bunch of fans I had and exposed only my GPU fans.
This seems consistent with what others are reporting, this issue got more apparent with the newest release.
GCC(gigabyte control center) identifies all fans correctly
I confirm ITE IT8696E - work. Sensors ITE IT8696E - work. But i can see ITE IT87952E with fans too - it not work (What it?).
This looks like 0.9.4, which does not reflect any of current changes and the reported issues here. Please take a master build from here to get accurate data on most recent changes: https://github.com/LibreHardwareMonitor/LibreHardwareMonitor/actions I hope everyone else is using a recent build and not the release from end of 2024 to test.
I confirm ITE IT8696E - work. Sensors ITE IT8696E - work. But i can see ITE IT87952E with fans too - it not work (What it?).
This looks like 0.9.4, which does not reflect any of current changes and the reported issues here. Please take a master build from here to get accurate data on most recent changes: https://github.com/LibreHardwareMonitor/LibreHardwareMonitor/actions I hope everyone else is using a recent build and not the release from end of 2024 to test.
Last build work great also. And now all fans is corrects i hope.
I have a Gigabte X870E Extreme AI top and can't control all fans either, been following this thread and is the current workaround for now to use the latest nightly build of LibreHardware?
Latest release does use all the advancement that were made in LHM.
Latest release does use all the advancement that were made in LHM.
Shame, doesn't work for me despite the same ITE chip the other boards have.
Some users reported that the service used by the Gigabyte software will interfere.
Some users reported that the service used by the Gigabyte software will interfere.
What service? I don't have anything installed. I never install the motherboard bloatware.
Here is the latest LHM dll with debug log enabled. Take either the .net10 or 4.7 depending on your of FanControl, and swap it in. Then enable a control and try to change it's speed. It should generate a log file in your FanControl folder.
"PawnIo_IsaBridgeEc_DebugLog.txt"
Here is the latest LHM dll with debug log enabled. Take either the .net10 or 4.7 depending on your of FanControl, and swap it in. Then enable a control and try to change it's speed. It should generate a log file in your FanControl folder.
"PawnIo_IsaBridgeEc_DebugLog.txt"
I tried this earlier with the latest version off their github, unfortunately swapping in the LHM dll directly blows up.
[V250] 12/1/2025 6:06:13 PM: Open - System.Reflection.ReflectionTypeLoadException: Unable to load one or more of the requested types.
Could not load file or assembly 'RAMSPDToolkit-NDD, Version=1.4.2.0, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.
Could not load file or assembly 'RAMSPDToolkit-NDD, Version=1.4.2.0, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.
Could not load file or assembly 'DiskInfoToolkit, Version=1.0.9.0, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.
Could not load file or assembly 'DiskInfoToolkit, Version=1.0.9.0, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.
Could not load file or assembly 'DiskInfoToolkit, Version=1.0.9.0, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.
at System.Reflection.RuntimeModule.GetDefinedTypes()
at System.Reflection.RuntimeModule.GetTypes()
at FanControl.Domain.BackendProviders.LHM.LHMBackendProvider.DeactivateNvidiaML()
at FanControl.Domain.BackendProviders.LHM.LHMBackendProvider.Open()
System.IO.FileNotFoundException: Could not load file or assembly 'RAMSPDToolkit-NDD, Version=1.4.2.0, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.
File name: 'RAMSPDToolkit-NDD, Version=1.4.2.0, Culture=neutral, PublicKeyToken=null'
System.IO.FileNotFoundException: Could not load file or assembly 'RAMSPDToolkit-NDD, Version=1.4.2.0, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.
File name: 'RAMSPDToolkit-NDD, Version=1.4.2.0, Culture=neutral, PublicKeyToken=null'
System.IO.FileNotFoundException: Could not load file or assembly 'DiskInfoToolkit, Version=1.0.9.0, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.
File name: 'DiskInfoToolkit, Version=1.0.9.0, Culture=neutral, PublicKeyToken=null'
System.IO.FileNotFoundException: Could not load file or assembly 'DiskInfoToolkit, Version=1.0.9.0, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.
File name: 'DiskInfoToolkit, Version=1.0.9.0, Culture=neutral, PublicKeyToken=null'
System.IO.FileNotFoundException: Could not load file or assembly 'DiskInfoToolkit, Version=1.0.9.0, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.
File name: 'DiskInfoToolkit, Version=1.0.9.0, Culture=neutral, PublicKeyToken=null'
[V250] 12/1/2025 6:06:16 PM: Open - System.Reflection.ReflectionTypeLoadException: Unable to load one or more of the requested types.
Could not load file or assembly 'RAMSPDToolkit-NDD, Version=1.4.2.0, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.
Could not load file or assembly 'RAMSPDToolkit-NDD, Version=1.4.2.0, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.
Could not load file or assembly 'DiskInfoToolkit, Version=1.0.9.0, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.
Could not load file or assembly 'DiskInfoToolkit, Version=1.0.9.0, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.
Could not load file or assembly 'DiskInfoToolkit, Version=1.0.9.0, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.
at System.Reflection.RuntimeModule.GetDefinedTypes()
at System.Reflection.RuntimeModule.GetTypes()
at FanControl.Domain.BackendProviders.LHM.LHMBackendProvider.DeactivateNvidiaML()
at FanControl.Domain.BackendProviders.LHM.LHMBackendProvider.Open()
System.IO.FileNotFoundException: Could not load file or assembly 'RAMSPDToolkit-NDD, Version=1.4.2.0, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.
File name: 'RAMSPDToolkit-NDD, Version=1.4.2.0, Culture=neutral, PublicKeyToken=null'
System.IO.FileNotFoundException: Could not load file or assembly 'RAMSPDToolkit-NDD, Version=1.4.2.0, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.
File name: 'RAMSPDToolkit-NDD, Version=1.4.2.0, Culture=neutral, PublicKeyToken=null'
System.IO.FileNotFoundException: Could not load file or assembly 'DiskInfoToolkit, Version=1.0.9.0, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.
File name: 'DiskInfoToolkit, Version=1.0.9.0, Culture=neutral, PublicKeyToken=null'
System.IO.FileNotFoundException: Could not load file or assembly 'DiskInfoToolkit, Version=1.0.9.0, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.
File name: 'DiskInfoToolkit, Version=1.0.9.0, Culture=neutral, PublicKeyToken=null'
System.IO.FileNotFoundException: Could not load file or assembly 'DiskInfoToolkit, Version=1.0.9.0, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.
File name: 'DiskInfoToolkit, Version=1.0.9.0, Culture=neutral, PublicKeyToken=null'
[V250] 12/1/2025 6:06:17 PM: LibreHardwareMonitor could not initialize or has no sensors.
You will also need up to date dependencies. They seem to be missing from the .NET 10 folder in the zip.
Yeah there you go.
Yeah I had slurched the latest build after I posted that, shouldn't be trying things mid meeting. Anyways, fans that show up are controllable, for the most part. I'm missing 3 fans that aren't detected.
Fans 7 and onwards are completely missing in LHM as well as FanControl. I'm finding interfacing with gigabyte IO in general is an experience.
My question is, if they are not connected to ITE chip #1 or ITE chip #2, where the are hell are they plugged into? Why not plug every fan on 1 chip with enough available channels like every single other manufacturers lol
My question is, if they are not connected to ITE chip #1 or ITE chip #2, where the are hell are they plugged into? Why not plug every fan on 1 chip with enough available channels like every single other manufacturers lol
Beats the fudge out of me man I'm wondering the same thing. They definitely do things "interestingly" compared to the others. If the godlike wasn't such trash and ASUS didn't ruin it for, I wouldn't have splashed for this board. To be fair, it's not actually too bad. I'm enjoying it, but, interfacing with the IO and EC has been a PITA.
Here is the latest LHM dll with debug log enabled. Take either the .net10 or 4.7 depending on your of FanControl, and swap it in. Then enable a control and try to change it's speed. It should generate a log file in your FanControl folder.
I put it into the program folder and ran the first run wizard. Then I changed the speed of CPU Fan, Fan2 and Fan3. I was only able to change speeds of Fan3 (which didn't work previously, but I was able to control CPU once..?) but nothing more.
Here is the latest LHM dll with debug log enabled. Take either the .net10 or 4.7 depending on your of FanControl, and swap it in. Then enable a control and try to change it's speed. It should generate a log file in your FanControl folder.
"PawnIo_IsaBridgeEc_DebugLog.txt"
PawnIo_IsaBridgeEc_DebugLog.txt LibreHardwareMonitor.Report.txt I hope it will be helped.
@userosos in your case the ControllerEnableRegister is already set to "false", so technically "manual" mode is enabled.
