Overclock.net banner

ASUS ZenStates

136K views 245 replies 68 participants last post by  pipes  
#1 · (Edited)
ZenStates 0.7.6747

- Created a new method for storing settings, hopefully works better. Also has the advantage of being human readable XML (should be located under C:\ProgramData\ASUS ZenStates).
- Removed Performance Enhancer and replaced it with PPT/TDC/EDC control. They're inactive right now since I'm not able to reset back to default values at the moment.
- Again attempts to install/start the service at launch so you don't have to manage it yourself
- Added more details to the Event Log messages from AsusZsSrv for easier debugging
- Any settings are now only applied when the tray icon is initialized
- Added a "-min" switch for the software which is used for auto-starting. This means that by default when launching the application manually, the main window will be visible.
- The "Save" button now only appears when settings are not saved

http://www.mediafire.com/file/6robkt74vc9wgdf/ASUS ZenStates 0.7.6747.zip

Image
 
#4 ·
Do you have a link to a post or something to elaborate on what Eternal XFR is? My gut feeling would be something along the lines of XFR still working with a custom overclock.. Or is it under wraps?
 
#10 ·
Is it "External" or "Eternal" XFR? :D

Anyway, an XFR that is working with OC would be awesome .. 4GHz on 1 or 2 Cores isn't a big deal for any Ryzen. :)

As written, Eternal XFR. More info after the Ryzen 2/C7H embargo is up.


What the app really needs is a "reset all values to default" option.

Reset to whatever the BIOS settings are? That's doable.
 
#5 ·
Custom XFR sounds great!

I did use zen states for a period when I was getting to grips with pstate/manual ratio & C-states. Worked well.

However I found from my testing that performance was slightly less than when overclocking with the BIOS. I have seen others say the opposite though.

Great software and I'd be interested in testing the custom XFR if it will work with the Crosshair VI
 
#9 ·
Is it "External" or "Eternal" XFR? :D

Anyway, an XFR that is working with OC would be awesome .. 4GHz on 1 or 2 Cores isn't a big deal for any Ryzen. :)
 
#14 ·
Elmor,

Remember it does this:

http://www.overclock.net/forum/attachment.php?attachmentid=153689&thumb=1

When trying to start it for the first time (after passing UAC) on my system. If I start it a second time, it's fine. I mentioned it some time back, you said you knew what it was.

Would love to see a way to start when Windows does BUT not apply the settings when it starts (basically start and stay resident), I know that's counter-intuitive, but I'd like to have it ready so I can apply a PState OC as needed, and then a way to "deactivate the OC/return to defaults" as well. Might also be neat to have an import/export for settings, and maybe even a couple 3 "profile slots" for a few different PState Settings. Edit: If going back to defaults isn't possible without a reboot, would have a profile that more or less just had your default PState Settings set and being able to activate/load it be a workaround for that issue?

Thanks for still working on this Elmor, a lot of us love it!
 

Attachments

#15 ·

Attachments

#18 ·
Summit is OK too, no difference in functionality. Performance Enhancer works on Summit as well, but the result is not as great. For example 1800X will stay at 4.1G single-threaded and 3.7G multi-threaded.


Alright Elmor, I'll be testing this. Running a 2600x with C6H Bios 6101 currently. I assume PE settings activates the same one as the BIOS? Can it be turned on and off without a reboot? What do Core C6 State and Package C6 State do, I've always been curious of that?

All settings apply on the fly. Core/Package C6 allow very low power C-states. I believe Package C6 is the same as Global C-states Control under AMD CBS.
 
#25 ·
The only way I'm aware of would be to directly set it on the controller, which I don't want to do.


I installed it yesterday on my 1700, OC @3.7GHz at the moment.

Works as good as 0.2.2. :)

One question, what does PE Level 3 do? Can't see any difference?

It unlocks the TDP/TDC limits of the CPU, but on Summit Ridge it doesn't have much of an impact.


Hey Elmor,

First I want to thank you for updating this tool, I've been using the 0.2.2 version for a couple of months because my BIOS lacks of P-STATE support (Asus X370-F Gaming) and it's really useful.

I've tested your beta and it works just fine for most of the options (didn't test Perf. Enhancer), except Performance Bias.

I ran a couple of comparative tests between 0.2.2 (with Performance Bias BIOS option) & 0.3, here are some CineBench15 results (R7 1700@3.9Ghz):

ZenStates 0.3 (Performance Bias: Disabled)
1708 1722 1726
ZenStates 0.3 (Performance Bias: CB15)
1730 1731 1732
ZenStates 0.2.2 (Performance Bias: Auto - BIOS)
1711 1722 1728
ZenStates 0.2.2 (Performance Bias: CB15 - BIOS)
1764 1780 1787

So there's probably something wrong going on here, maybe some swapped bias options? CB15 bias (0.3 version) clearly doesn't have the same impact on score as BIOS's CB15 bias.

In my BIOS (4009), I have the following dropdown for Performance Bias:
- Auto
- None
- CB15
- AIDA / Geekbench
- CB11.15

Thanks if you can look into that issue, because it's really useful to be able to switch Performance Bias on the fly!

Keep up the good work.

Thanks, seems the settings are not applying like they should.


@elmor, just had a very interesting issue using 0.3

my graphics card was acting out every time I applied my OC, my screen would start blinking, and would turn black, I would get a ton of "error initializing graphics driver" prompts in windows. was happening even after re-installing the graphics drivers (after wiping with DDU of course).

went back to 0.2.2, the problem went away.

curious.

Did you uncheck the P0 TSC workaround checkbox?
 
#22 ·
I installed it yesterday on my 1700, OC @3.7GHz at the moment.

Works as good as 0.2.2. :)

One question, what does PE Level 3 do? Can't see any difference?
 
#23 · (Edited)
Hey Elmor,

First I want to thank you for updating this tool, I've been using the 0.2.2 version for a couple of months because my BIOS lacks of P-STATE support (Asus X370-F Gaming) and it's really useful.

I've tested your beta and it works just fine for most of the options (didn't test Perf. Enhancer), except Performance Bias.

I ran a couple of comparative tests between 0.2.2 (with Performance Bias BIOS option) & 0.3, here are some CineBench15 results (R7 1700@3.9Ghz):

ZenStates 0.3 (Performance Bias: Disabled)
1708 1722 1726
ZenStates 0.3 (Performance Bias: CB15)
1730 1731 1732
ZenStates 0.2.2 (Performance Bias: Auto - BIOS)
1711 1722 1728
ZenStates 0.2.2 (Performance Bias: CB15 - BIOS)
1764 1780 1787

So there's probably something wrong going on here, maybe some swapped bias options? CB15 bias (0.3 version) clearly doesn't have the same impact on score as BIOS's CB15 bias.

In my BIOS (4009), I have the following dropdown for Performance Bias:
- Auto
- None
- CB15
- AIDA / Geekbench
- CB11.15

Thanks if you can look into that issue, because it's really useful to be able to switch Performance Bias on the fly!

Keep up the good work.
 
#24 ·
@elmor, just had a very interesting issue using 0.3

my graphics card was acting out every time I applied my OC, my screen would start blinking, and would turn black, I would get a ton of "error initializing graphics driver" prompts in windows. was happening even after re-installing the graphics drivers (after wiping with DDU of course).

went back to 0.2.2, the problem went away.

curious.
 
#27 ·
I had this same issue trying to apply OC's with Zenstates. Also, Elmor, would it be possible to add the other PE levels into ZenStates, not just PE3? PE3 is the one I have the most stability issues with (windows won't boot if I use it from the bios) and PE4 pushes too much voltage. I tend to run with PE2, but PE1/PE2 aren't available in ZenStates.
 
#33 ·
@elmor once again a BIG THANKS for this.
 
#39 ·
Similar issues on my side: weird screen flicker and loops to startup screen. This does only happen if I switch to Performance Bias for Cinebench 15. With "Disabled" (and PB in the BIOS at "Auto") ZenStates 0.3.6691 works smoothly like 0.2.2 over the last year.

Running a R7 1800X with 6101 BIOS...and love to see ZenStates 1.0 coming!
 
#40 ·
@elmor Just some feedback and a bit of a question when you get a chance. I actually never used zenstates with my 1700X however I recently got a 2700X and using it on my C6H board. Any once again a BIG THANK you for this. Works like a charm.

Hopeing you can explain this to me. Once I stated using ZS with my 2700 on manual overclocking in HWinfo my CPU Core VOltage SVI2 TFN stays locked..however now my VCORE from the ITE IT8665E thing now works. My vcore will actually drop down to about .6 volts and my temps are reflecting that...so is my Vcore the correct voltage now? See pic. Also Cpu-Z and Aida are all reflecting this Vcore changing from idle to max. No I ran these individually so no conflicts to verify as I know using multiple programs like this can cause sensor errors.
 

Attachments

#41 ·
Update on my issues, managed to finally install and now SOMETIMES the settings are set.
But the settings are NOT SAVED despite clicking "Start with system" and "apply at start".


Full list of issues:

On reboot, program asks for admin rights on start (seems like its stuck in an installation loop despite saying it installed properly?) - .2.2 doesn't do this.
On Reboot and on program close-restart, all settings are set back to default. Including the "cheeked" settings.
Performance Bias sometimes doesn't do anything(seems random, if the P0 states work, bias does work, and if p0 states work, bias doesnt work).
When setting a custom Core voltage, it keeps saying that the number is "value was either too large or too small for a uint64". Despite changing just one number. (Example, 2.2 worked fine with V1.22000 - New version says "value is either too large or to small" if I change the selectable 1.22500V to 1.22000V) Infact, changing ANY setting by hand, yields the error, even if I write a number that is in the list.
 
#42 ·
feature request: simple intelligent throttling

thank you very much for ZenStates!

i also have to confirm the flickering problem on prime x370-pro.

as feature request for gamer and video renderer it would be really nice to get intelligent throttling. i mean a simple task if P0 reachs temp XX fall back to P1 until temperature -XX. another missing ryzen feature is the well known avx offset, but i think thats more complex to realize. So i hope you could integrate the throttling feature - it's annoying to switch between gaming (max single thread) and renderer (max multi thread) profiles.
 
#43 · (Edited)
Firstly, thanks for this very useful util.
Secondly, I want to report a problem with P0 voltage, I had to set it to 1.10625 in order to achieve 1.25 V in HWiNFO (SVI2 TFN).

/EDIT
My apologies, it was due to a forgotten multiplier setting in the BIOS. I experienced the flickering problem once I booted back though, but after a reset it's currently fine. Will report if happens again.