1.2.5 (nor previous versions) load past "initializing" splash screen. AGESA 1.2.0.0+

[irusanov]

1.2.5 (nor previous versions) load past "initializing" splash screen. AGESA 1.2.0.0+

[lHolyDiverl]

Got it.

Here it is:

I believe it is the last one before error occurs.

[irusanov]

Yes, it only reads common timings. I just need to fix the channel detection and ZenTimings will start, too. We can try with disabled first to verify, then will try to fix the initialization.

[irusanov]

Thanks for reporting. Will have to compile a debug version that outputs everything in a file, so we can see where it stops first.

[lufusol]

I'll be happy to pilot that and send you the log(s)

[irusanov]

Attached version has trace enabled for the dll.
It will be logged to trace.log

ZenTimings_v1.2.5-trace-debug.zip

[lufusol]

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 <#24 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AT6I5FRPFKZYCW6XTL54NKLTWX5PBANCNFSM47OWFQFA> .

[lufusol]

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?

[irusanov]

Who knows. Haven't installed chipset drivers from a long time on my machine, but sometimes OS updates cause issues, drivers probably too.

[DeadEnded]

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

[Battler624]

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

Its a program for ryzen cpus not intel stuff.

[Famebloody]

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

[lHolyDiverl]

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.

[irusanov]

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

[lHolyDiverl]

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.

[irusanov]

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?

[irusanov]

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.

ZenStates-Core.dll.zip

[lHolyDiverl]

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.

ZenStates-Core.dll.zip

New message appears:

Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index

[irusanov]

Yeah, sorry. I did that at work, but the source was outdated.
ZenStates-Core.zip

[lHolyDiverl]

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

[lHolyDiverl]

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

[irusanov]

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.

ZenStates-2.0-20220513.zip

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.

[lHolyDiverl]

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.

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.

ZenStates-2.0-20220513.zip

Looks like it works:

Thanks for the testing

No problem. You are welcome.

[irusanov]

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?

[lHolyDiverl]

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

[irusanov]

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

[lHolyDiverl]

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

[irusanov]

@lHolyDiverl Sorry to bother you again, but do you remember what is the last message displayed in the loading screen?

[lHolyDiverl]

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?

[irusanov]

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.

[irusanov]

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.

[lHolyDiverl]

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.

[irusanov]

Attached are 2 debug versions of the app. "1" has the channels info disabled and "2" has the whole memory modules info disabled.

Let me know if any of these launch successfully.

ZenTimings_v1.2.6.622-debug-1.zip
ZenTimings_v1.2.6.622-debug-2.zip

PS: If it works, I'll be glad if you can attach a debug report.

[lHolyDiverl]

Attached are 2 debug versions of the app. "1" has the channels info disabled and "2" has the whole memory modules info disabled.

Let me know if any of these launch successfully.

ZenTimings_v1.2.6.622-debug-1.zip ZenTimings_v1.2.6.622-debug-2.zip

PS: If it works, I'll be glad if you can attach a debug report.

First one ZenTimings_v1.2.6.622-debug-1.zip is working from the box.

Here is debug report for you:
Debug_Report_27545461.1494226.txt

[irusanov]

@lHolyDiverl Thank you very much! I have the base now to get the full support.

[lHolyDiverl]

@irusanov You are welcome. Happy to help :)

[lHolyDiverl]

Oh and one small addition.

When ZenTimings_v1.2.6.622-debug-1.zip starts it hang for a while on:

With following warning:

Could not get power table.
Skipping.

Than there
is a system exception for Memory controller:

An exception of type was thrown "System.Exception".

This is a test build but still maybe there are some other hidden issues since some power data table is present in debug report.

Here is application screenshot:

[irusanov]

The power data in the debug log seems to be gibberish, I will have a new build at the end of the day which would hopefully fix this problem.

[irusanov]

Hopefully this one works a little better.
ZenTimings_v1.2.6.623-debug.zip

[lHolyDiverl]

Both versions ZenTimings_v1.2.6.622-debug-1.zip and ZenTimings_v1.2.6.623-debug.zip are running fine when NOT in advanced\debug mode except 623 see the amount of available RAM and stick to choose at the bottom:

If debug mode is lunched both versions ZenTimings_v1.2.6.622-debug-1.zip and ZenTimings_v1.2.6.623-debug.zip are stuck at

With warning:

Could not get power table.
Skipping.

and exception for Memory controller:

An exception of type was thrown "System.Exception".

Screenshots for advanced mode to compare:

And some debug report from ZenTimings_v1.2.6.623-debug.zip:
Debug_Report_v1.2.6.623.txt

[irusanov]

Well, it's a progress. Not sure why the power table does not work.
We might need to use my debug tool and sniff what HwInfo app sends, if the HwInfo works with your laptop.
Let me know if you're up to it.

[lHolyDiverl]

HWinfo works fine:

Let's try and see what happend.

[irusanov]

SMUDebugTool_v1.3.3_20220518.zip

Here's the debug tool.

Close all other applications, unzip the tool and run the exe. You should see something like this, if it starts correctly.

Select SMU tab, then with the RSMU selected from the dropdown, click on "Send" to test for correct response. Command ID = 1 is a test command, result should be the value in Arguments field + 1.

Now click "Reset". For each item in the Mailbox dropdown, click "Monitor" - it will open a new window. Leave them open.

Launch HWinfo with monitoring enabled (as in the screenshot). After a while, close hwinfo and make a screenshot of the windows, like so.

Please don't enter random commands and arguments and click Send - this could be dangerous. Scan button usually works, but it might also lock the system, requiring a hard reset, so it's also not advisable. PMTable button is safe, but it will probably display incorrect values in the table (like in the debug report).

Thanks for the cooperation, hopefully this will help!

[irusanov]

ZenStates-Core.dll.zip
I also have another DLL to try with ZenTimings.

[lHolyDiverl]

ZenStates-Core.dll.zip I also have another DLL to try with ZenTimings.

Same result with this DLL as it was with original ZenTimings_v1.2.6.623-debug.zip for both Advanced Mode turned off and on

[lHolyDiverl]

I tried SMUDebugTool_v1.3.3_20220518.zip:

SMU tab:

Argument 0:

Argument 1:

Monitor part

I have basic configuration for HwInfo and run it as (After starting monitor):

Results are:

P.S. I had Chrome running in background at this run. I believe it shoudn't affect the results.
SMUDebugTool abnormally terminated couple of times and this run was pretty "stable"

[irusanov]

Thanks. Can you do the same Monitor, but with the other Mailbox opened as a SMU Monitor window?
It should be called MP1 in the Mailbox dropdown.

PS: Another request. Can you scroll to the very top of the SMU Monitor windows before taking the screenshots?

[lHolyDiverl]

Missed MP1 after some app termination.

Here is Monitor for MP1:

[irusanov]

@lHolyDiverl
Unfortunately, I don't know what else to change.
Could you run the RSMU Monitor again, open hwinfo, when it (hwinfo) opens completely, close it.
Scroll the SMU Monitor all the way up, so first lines are visible and make a screenshot. You can also resize the Monitor window to max height possible.

Thank you in advance!

[lHolyDiverl]

@lHolyDiverl Unfortunately, I don't know what else to change. Could you run the RSMU Monitor again, open hwinfo, when it (hwinfo) opens completely, close it. Scroll the SMU Monitor all the way up, so first lines are visible and make a screenshot. You can also resize the Monitor window to max height possible.

Thank you in advance!

@irusanov
Here is what I've got:

[irusanov]

@lHolyDiverl I still don't get it why it doesn't work :/

Here's a test dll with the address hardcoded (assuming it is shown on the screenshot):
ZenStates-Core-test-rembrandt.zip

[lHolyDiverl]

@irusanov

Result are pretty the same.

ZenTimings_v1.2.6.623-debug.zip with ZenStates-Core-test-rembrandt.zip provide following result:

With warning:

Could not get power table.
Skipping.

And exception:

An exception of type was thrown "System.Exception".

When <AdvancedMode>false</AdvancedMode>

And screenshot of the app:

Maybe you would need another configuration for testing to determine what is wrong.

[irusanov]

The error you get is because AMD seems to have removed the command to get memory controller config :/

One more build, but I expect similar results, although a different last error.
ZenTimings_v1.2.6.633-debug.zip

If that doesn't work, then I give up for now. Won't be able to fix it unless I have access to such a system. At least it shows main timings and as a last resort I can turn off AdvancedMode for Rembrandt until I figure out what's wrong.
I can probably fix the VSOC based on your previous debug reports, but the rest - I have no idea :(

[lHolyDiverl]

ZenTimings_v1.2.6.633-debug.zip running fine with Advanced Mode turned off:

And same for Advanced Mode turned on:

Could not get power table.
Skipping.

With warining:

Exception of type 'System.Exception' was thrown.

With app window:

As for Rembrandt you can also add a warning message that "Advanced Mode for Rembrandt is not available yet" or somethin like it and maybe dissable Advanced Mode option in settings.

People could also modified settings.xml but it will be their own choice.

Good luck in your "battle" against Rembrandt :)