ZenTimings
ZenTimings copied to clipboard
irusanov
1.2.5 (nor previous versions) load past "initializing" splash screen. AGESA 1.2.0.0+
CPU Ry5 3600 Mobo AsRock B550M SL BIOS 1.9, (AGESA 1.2.0.0) 2.0, 2.1 (AGESA 1.2.0.2) OS Win 10 Pro x64 21H1 RAM OLOy WarHawks DDR4-3600 2x8GB (b-die)
Same issue as some others, only the update prompt on first run and "initializing" splash screen on subsequent runs are shown, program exits before ever making it to the GUI. :( Previous versions back to 1.2.2 more or less the same (1.2.2 hangs on "initializing" for longer)
Thanks for reporting. Will have to compile a debug version that outputs everything in a file, so we can see where it stops first.
Attached version has trace enabled for the dll. It will be logged to trace.log
ZenTimings_v1.2.5-trace-debug.zip
Wow, hi Ivan!
First of all I just want to say I think it's so cool you took the time to compile this and send it to me for testing.
Unfortunately I can't help you now, because the program ran fine upon start and then I tried the normal release of ZenTimings 1.2.5 and that, too, ran fine.
Since my original issue, for different reasons, I reinstalled the latest AMD chipset driver and did a clean reinstall of my graphics drivers. Probably the former fixed it. Do you still want the log output?
Pete
On Thu, Jul 8, 2021 at 3:41 PM Ivan Rusanov @.***> wrote:
Attached version has trace enabled for the dll. It will be logged to trace.log
ZenTimings_v1.2.5-trace-debug.zip https://github.com/irusanov/ZenTimings/files/6786857/ZenTimings_v1.2.5-trace-debug.zip
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/irusanov/ZenTimings/issues/24#issuecomment-876696022, or unsubscribe https://github.com/notifications/unsubscribe-auth/AT6I5FRPFKZYCW6XTL54NKLTWX5PBANCNFSM47OWFQFA .
Just want to add, that before when it was crashing out, I believe I tried reinstalling chipset drivers and it had no effect. This time, though, there was a newer version on AMD's site. Updated chipset driver may solve?
Who knows. Haven't installed chipset drivers from a long time on my machine, but sometimes OS updates cause issues, drivers probably too.
I tried running Zen Timing for the first time and also had the CPU not supported error. I ran this debug version and here is the trace log:
Entering Cpu
Mutex Global\Access_PCI created
Check Ols Status
OK
Entering CPUID 0x1
OK
Entering CPUID 0x80000001
OK
Entering CPUID 0x8000001E
OK
Entering CCD and CCX config
OK
GetPatchLevel
GetSVI2Info
PowerTable
Could not get DRAM base address.
OK
My system is a Dell G3 3590 with an i7-9750H cpu. Let me know if there is any other information I can share to help troubleshoot. I also tried the 1.2.3 version and it never started.
Thanks! DeadEnd
I tried running Zen Timing for the first time and also had the CPU not supported error. I ran this debug version and here is the trace log:
Entering Cpu Mutex Global\Access_PCI created Check Ols Status OK Entering CPUID 0x1 OK Entering CPUID 0x80000001 OK Entering CPUID 0x8000001E OK Entering CCD and CCX config OK GetPatchLevel GetSVI2Info PowerTable Could not get DRAM base address. OKMy system is a Dell G3 3590 with an i7-9750H cpu. Let me know if there is any other information I can share to help troubleshoot. I also tried the 1.2.3 version and it never started.
Thanks! DeadEnd
Its a program for ryzen cpus not intel stuff.
Hi, I have the same problem with the launch of Zentimings v1.2.5, like #24 Lufusol.
Configuration: Win 10 Pro x64 21H1 Ryzen 5 3600 MSI X570 Gaming Plus AGESA 1.2.0.0. Hyperx Predator RGB [HX432C16PB3AK2/16] 2x8GB
Launch log:
Entering Cpu
Mutex Global\Access_PCI created
Check Ols Status
OK
Entering CPUID 0x1
OK
Entering CPUID 0x80000001
OK
Entering CPUID 0x8000001E
OK
Entering CCD and CCX config
Could not read CCD fuse!
OK
GetPatchLevel
GetSVI2Info
PowerTable
Could not get DRAM base address.
OK
Hello,
Looks like same problem is present for ASUS G713RM laptop with AMD Ryzen 7 6800H running on Windows 11:
Log:
Entering Cpu Mutex Global\Access_PCI created Check Ols Status OK Entering CPUID 0x1 OK Entering CPUID 0x80000001 OK Entering CPUID 0x8000001E OK Entering CCD and CCX config OK GetPatchLevel GetSVI2Info PowerTable Could not get DRAM base address. OK
Thank you for your work.
The 6800H is not (fully) supported in 1.2.5. If you feel adventurous, attached is a debug version of 1.2.6 which is not really finished yet, but might work on Rembrandt. Unfortunately I don't have a Rembrandt or Renoir.
ZenTimings_v1.2.6.615-debug.zip
For 1.2.6 version result is the same:
CPU model is not supported. Please run a debug report and send to the developer.
It would be nice to have an option to lunch debug version with traces enabled e.g. by adding parameter to the shortcut like:
"PATH\ZenTimings.exe" -trace
Or any other way to easy enabling of trace option for cases when ZenTimings couldn't lunch GUI properly without compiling separate version.
The plan is to add automatic debug/trace log in case of a crash. The message you get is not really correct. If the model is not supported, how are you supposed to run a debug report :D Have no idea why it says the CPU is not supported, maybe the CPUID is wrong. Can you share a cpuz screen and probably some report from hwinfo?
I have recompiled the DLL, extract it from the archive and replace in ZenTimings folder. Should have the detection fixed. Hopefully the rest works then.
I have recompiled the DLL, extract it from the archive and replace in ZenTimings folder. Should have the detection fixed. Hopefully the rest works then.
New message appears:
Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
The plan is to add automatic debug/trace log in case of a crash. The message you get is not really correct. If the model is not supported, how are you supposed to run a debug report :D
Yep, but at least I know that my CPU should qualifeid for it :)
Have no idea why it says the CPU is not supported, maybe the CPUID is wrong. Can you share a cpuz screen and probably some report from hwinfo?
Here is CPU-Z:
And HWinfo report: HWinfo_CPU.LOG
Yeah, sorry. I did that at work, but the source was outdated. ZenStates-Core.zip
No chanegs with this revision:
Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index
It seems the CPUID is not a problem anymore, but something else fails. I don't have a proper debug logging in the app. I have disabled some things in this build and turned off some of the advanced settings (in settings.xml)
ZenTimings_v1.2.6.619-debug.zip
Here's a build of the new ZenStates which only loads the DLL and has no UI elements yet. If that loads then the DLL is at least half-workling.
Thanks for the testing, if none of the above has any positive effect I will have to implement that debug report functionality and then try again.
It seems the CPUID is not a problem anymore, but something else fails. I don't have a proper debug logging in the app. I have disabled some things in this build and turned off some of the advanced settings (in settings.xml)
No changes here.
CPU model is not supported. Please run a debug report and send to the developer.
Here's a build of the new ZenStates which only loads the DLL and has no UI elements yet. If that loads then the DLL is at least half-workling.
Looks like it works:
Thanks for the testing
No problem. You are welcome.
It seems the CPUID is not a problem anymore, but something else fails. I don't have a proper debug logging in the app. I have disabled some things in this build and turned off some of the advanced settings (in settings.xml) ZenTimings_v1.2.6.619-debug.zip
No changes here.
CPU model is not supported. Please run a debug report and send to the developer.
Can you copy the ZenStates-Core.dll from the ZenStates zip and replace in the ZenTimings directory?
Can you copy the ZenStates-Core.dll from the ZenStates zip and replace in the ZenTimings directory?
Coping ZenStates-Core.dll from ZenStates-2.0-20220513.zip to ZenTimings_v1.2.6.619-debug.zip leads to:
Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index
Thanks for trying, something is not initialized correctly in the app and I'm not handling the error correctly. The DLL seems to be working.
Last try for now, added some more checks in the code ZenTimings_v1.2.6.619-debug.zip
Last try for now, added some more checks in the code ZenTimings_v1.2.6.619-debug.zip
Result is the same:
Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index
@lHolyDiverl Sorry to bother you again, but do you remember what is the last message displayed in the loading screen?
Hi @irusanov,
@lHolyDiverl Sorry to bother you again, but do you remember what is the last message displayed in the loading screen?
Same as here:
Last try for now, added some more checks in the code ZenTimings_v1.2.6.619-debug.zip
Result is the same:
Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index
Or maybe you are reffering to some other version?
I mean, does the loading screen show at all and if it does, what is the last message that is displayed when the error occurs? The loading is probably still there, but is hidden under the error and you should be able to see it if you move the dialog.
Alright, that would probably help in tackling where it fails. Thanks! I believe it is a DDR5 specific error where the app can't get modules/channels info. It is probably related to channels detection, since a single DDR5 stick is now a dual-channel on-die, so 2 sticks make for a "quad-channel".
If you're willing to test, I might temporary disable that part when I get back home from work and see how it goes.
Btw, you might want to try the DRAM Calculator, which has timings only and no other complications, so it might start without an error.
PS: I think the problem is that it detects 2 DIMM modules (or 1 if your laptop has just one DIMM) and twice the channels and that's where it fails. For example, let's assume you have just one DIMM installed, respectively dual-channel memory. The apps detects one dimm and expects single-channel configuration, but it finds 2 channels. Then tries to set the info of the second channel to the non-existing 2nd DIMM, because the logic is not aware of DDR5. Hence the index-out-of-range error.
Okay lets try dissabled option.
By the way DRAM Calculator is working and even show timings:
P.S. I believe my laptop should have 2 DIMM modules installed. Didn't opened it yet to check.