Sweet thanks for the heads up

cool 

Any news on elite x1 support for z390 dark?

EDIT: Added the mentioned error from exception.log to bottom. 
 
Are there particular steps one should take or avoid when installing Eleet X1? I cannot get it to work on either my z590 FTW or z590 DARK board with fresh and fully patched Win10 installs. 
 
Errors:

• If I just run the Eleet X1 binary as normal, I get the error about ring0 not being open.
• If I run the binary as administrator to get the elevated token, I get an Exception.log created with the text at the bottom of this post. 

What I have tried:

• Ensured bios settings were at default and on latest bios versions
• Fresh reinstall of Win10
• Tried both Eleet X1 1.0.5 and 1.0.6
• Have tried deleting the Eleet X1 profile folder and rebooting
• No third party security software / agents have been installed at this time
• Tried disabling most of the default Win10 Exploit Guard settings as a test
• I reviewed the Win10 event logs and found no related errors in App / System / Win Defender. 
• Praised the sun
• Clicked my heels 3 times and said "there's no OC'er like Kingpin"

 

Message: The given key was not present in the dictionary.
StackTrace: at System.ThrowHelper.ThrowKeyNotFoundException()
   at Z590Lib.Hardware.Memory.RocketMemory..ctor()
   at Z590Lib.Models.ELeetXCtrl.hardwareAdded(IHardware hardware)
   at Z590Lib.Hardware.Computer.Add(IGroup group)
   at Z590Lib.Hardware.Computer.Open()
   at Z590Lib.Models.ELeetXCtrl.<InitializeAsync>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Z590Lib.Z590LibModule.<OnInitialized>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   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 haven't experienced the same issue, Z590 Dark user here. I run Eleet X1 in administrator mode and comparability mode for Windows 7, seems to work fine on both Windows 7 and Windows 10 build 21354.

Thanks for the update.

Z590 dark with 10900kf.
I tried 1.0.7 the program just auto closes like unleash rgb does. But 1.0.6 worked, and on default bios settings, eleet x1 says current limit throttling right under the core ratio sliders.
Core voltage setting worked, but core ratio wouldn't apply if it was set higher than 51.

So I went back to bios oc, but some voltages would always be 50 millivolts higher than the values I entered, vdimm, vccio, and another one I can't think of right now.

Vcore voltage does something else. I set 1.35v or anything else really, and tried any ratio higher than 51, the in bios stress tests would ALWAYS have voltage at 1.45v or slightly higher. And in windows the voltage under load would droop about 60 millivolts no matter the vdroop setting applied.

Ratio set at 53 all core in bios, but running a benchmark in windows always dropped cpu down to 5.1ghz, and when cpu load finished it would come back up to 5.3ghz.

I can't figure this z590 board out it seems. Maybe I shouldn't have gone with it to use with two generations of cpu's.

I've given up on using Eleet X1 and am just doing everything in the BIOS.  Something always seems to happen where it can no longer run.  Now I'm stuck on the Ring 0 not open error and don't want to spend more time trying to fix it.  

MoonOverMcNally
Z590 dark with 10900kf.
Ratio set at 53 all core in bios, but running a benchmark in windows always dropped cpu down to 5.1ghz, and when cpu load finished it would come back up to 5.3ghz.

Is your AVX offset set to 2?  Or are you thermal throttling?  

fragility_V1

kalsim
Mine is the same way. Voltages are always a bit higher than what I set.

Isn't this due to Vdroop?  Voltage set is a target, and depending on vdroop would try to adjust voltage to keep closer to that target.

Does it for the DRAM voltage, too.

Yea not been using per core, and for llc I've tried auto, default, -25% and they all act the same. If in windows the vcore is what I set in bios at idles, then under load all droop 60 mv. I hooked up my multimeter to confirm as well. I'm going to try again today with an older bios version.

Can the precision software control RGB color of EK fans connected to the RGB headers of the motherboard on the 590 Dark?