Adds support for EVGA Z690 motherboards.

• EVGA Eleet X1 v1.0.12.0

Release Notes:

• Supports Z690 non-K CPU OC

 
As always, please leave your feedback and let us know if you run into any issues.

Any plans to add the ability to change SA/VDD2/VDDQ TX/VDD/VDDQ to this?

Rebooting to make any voltage change to the memory voltages is a PITA. 
 

Motherboard fan control would be nice. Just so I can ramp stuff up on the fly. 

Greetings!

I'm running mighty version 1.0.13 of this fine software! I just have one small issue, if it could be remedied, it would make me and I believe many others with me a happier people <3

Whenever I boot my PC, all of my LED settings are set to default/rainbowy stuff, I always have to click on my profile after restart and load it anew in order for my PC to shine in all of its glory as can be seen below.

Would You please be so kind and add a "load last loaded/saved profile on startup" 


 
Also +1 for the fand speed control, eventhough the one in BiOS/UEFi is already powerful a one in Eleet would make life a bliss! 

And another one, there's some bug in 1.0.13 that won't remember BCLK and DMi set to actual values [e.g. 100 MHz], but it keeps getting to 50 and than sometimes it reports something about cannot divide by zero and crashes and that the 50 is an invalid value.

Here, I'm attaching the exception log.
 

Message: Attempted to divide by zero.
StackTrace: at Z690Lib.Hardware.BCLK.Z690PEGclk.GetClk()
   at Z690Lib.ViewModels.Mains.PackageVM.updatePEGDMIclk()
   at Z690Lib.ViewModels.Mains.PackageVM.OnProfileLoaded()
   at Z690Lib.ViewModels.Mains.OverClockingViewModel.onProfileLoaded()
   at Prism.Events.EventBase.InternalPublish(Object[] arguments)
   at Z690Lib.ViewModels.MainViewModel.Load()
   at Prism.Commands.CompositeCommand.Execute(Object parameter)
   at MS.Internal.Commands.CommandHelpers.CriticalExecuteCommandSource(ICommandSource commandSource, Boolean userInitiated)
   at System.Windows.Controls.Primitives.ButtonBase.OnClick()
   at System.Windows.Controls.Button.OnClick()
   at System.Windows.Controls.Primitives.ButtonBase.OnMouseLeftButtonUp(MouseButtonEventArgs e)
   at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
   at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
   at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
   at System.Windows.UIElement.ReRaiseEventAs(DependencyObject sender, RoutedEventArgs args, RoutedEvent newEvent)
   at System.Windows.UIElement.OnMouseUpThunk(Object sender, MouseButtonEventArgs e)
   at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
   at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
   at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
   at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
   at System.Windows.UIElement.RaiseTrustedEvent(RoutedEventArgs args)
   at System.Windows.Input.InputManager.ProcessStagingArea()
   at System.Windows.Input.InputManager.ProcessInput(InputEventArgs input)
   at System.Windows.Input.InputProviderSite.ReportInput(InputReport inputReport)
   at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr hwnd, InputMode mode, Int32 timestamp, RawMouseActions actions, Int32 x, Int32 y, Int32 wheel)
   at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr hwnd, WindowMessage msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
   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)

uplink_svk
And another one, there's some bug in 1.0.13 that won't remember BCLK and DMi set to actual values [e.g. 100 MHz], but it keeps getting to 50 and than sometimes it reports something about cannot divide by zero and crashes and that the 50 is an invalid value.

Here, I'm attaching the exception log.
 

Message: Attempted to divide by zero.
StackTrace: at Z690Lib.Hardware.BCLK.Z690PEGclk.GetClk()
  at Z690Lib.ViewModels.Mains.PackageVM.updatePEGDMIclk()
  at Z690Lib.ViewModels.Mains.PackageVM.OnProfileLoaded()
  at Z690Lib.ViewModels.Mains.OverClockingViewModel.onProfileLoaded()
  at Prism.Events.EventBase.InternalPublish(Object[] arguments)
  at Z690Lib.ViewModels.MainViewModel.Load()
  at Prism.Commands.CompositeCommand.Execute(Object parameter)
  at MS.Internal.Commands.CommandHelpers.CriticalExecuteCommandSource(ICommandSource commandSource, Boolean userInitiated)
  at System.Windows.Controls.Primitives.ButtonBase.OnClick()
  at System.Windows.Controls.Button.OnClick()
  at System.Windows.Controls.Primitives.ButtonBase.OnMouseLeftButtonUp(MouseButtonEventArgs e)
  at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
  at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
  at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
  at System.Windows.UIElement.ReRaiseEventAs(DependencyObject sender, RoutedEventArgs args, RoutedEvent newEvent)
  at System.Windows.UIElement.OnMouseUpThunk(Object sender, MouseButtonEventArgs e)
  at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
  at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
  at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
  at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
  at System.Windows.UIElement.RaiseTrustedEvent(RoutedEventArgs args)
  at System.Windows.Input.InputManager.ProcessStagingArea()
  at System.Windows.Input.InputManager.ProcessInput(InputEventArgs input)
  at System.Windows.Input.InputProviderSite.ReportInput(InputReport inputReport)
  at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr hwnd, InputMode mode, Int32 timestamp, RawMouseActions actions, Int32 x, Int32 y, Int32 wheel)
  at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr hwnd, WindowMessage msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
  at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
  at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
  at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
  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)

I can attest to this, as I’ve been trying to troubleshoot why my 12900K won’t boost beyond 4.9/3.7 at stock settings using my Z690 Classified. Opening Elite X1 v1.0.13.0 was the latest step I took in having a look around at settings, and that’s when I discovered this bug.

ObscureEmpyreI can attest to this, as I’ve been trying to troubleshoot why my 12900K won’t boost beyond 4.9/3.7 at stock settings using my Z690 Classified. Opening Elite X1 v1.0.13.0 was the latest step I took in having a look around at settings, and that’s when I discovered this bug.

Yup, guys from EVGA, will You address these buggies anytime soon? I really like the SW, the Eleet, but inability to load the profile at startup and some bugs here and there are rendering it pretty cumbersome :(

For now, I'm just loading the profile each time when the PC starts, I set up the App so it would start maximized, but it's not that great You know :)

uplink_svk

ObscureEmpyreI can attest to this, as I’ve been trying to troubleshoot why my 12900K won’t boost beyond 4.9/3.7 at stock settings using my Z690 Classified. Opening Elite X1 v1.0.13.0 was the latest step I took in having a look around at settings, and that’s when I discovered this bug.

Yup, guys from EVGA, will You address these buggies anytime soon? I really like the SW, the Eleet, but inability to load the profile at startup and some bugs here and there are rendering it pretty cumbersome :(

For now, I'm just loading the profile each time when the PC starts, I set up the App so it would start maximized, but it's not that great You know :)

EVGATech_LeeM
From our MB team, they say that enabling XMP will disable C-State (also if you set a manual ratio) to improve stability.  If you don't need the OC, you can enable C-State with the XMP.
 
These configurations should work for default Turbo of 5.2GhZ (based on 12900):

1. C-State Enable + Enhanced C1 Enable
2. C-State Enable + Enhanced C1 Disable

https://forums.evga.com/FindPost/3566634
 

EVGATech_LeeM

Hey there sir Lee!

Thank You for Your fast reply!

Well, I was thinking more about the "startup bug", where I need to manually select the profile to load each time when PC starts.

Here, just like MSi AB does:


And second one is, when the Eleet loads up, it prompts error of wrong setting of BCLK and PEG/DMi. It doesn't matter whether I set them to 50 or 100, it always sets itself to some "random" value, either 50 or 100 and it always loads up differently.

Next time I boot my PC, I'll make You a screenshot.

Have you tried clearing out the ELEET X1 profile folder?  AppData -> Local -> EVGA Co., Ltd -> Delete any Eleet folder that has a ".exe_Url_" and then some random string of letters and numbers.  See if the same issues occur after doing this.