The program stopped working on R7 5700X

SnikS1337 commented 10 months ago

Hello! I used the program without problems, but at one point it stopped running. I've already tried everything, I don't know what to do next. I am attaching the log file . I tried everything you wrote. I even reinstalled .NET. The thing is that I hadn’t touched anything before, and the program simply stopped running. LogFile.txt

mann1x commented 10 months ago

Hi! I don't see anything wrong in the logfile.

What is exactly the behavior on screen? Are you running an AntiVirus?

Try to run it with the command line switches:

-LogTrace=1 -inpoutdlldisable=1

If it starts send me both LogFile and LogTrace.

SnikS1337 commented 10 months ago

Hi again. I don’t have a single antivirus, not even Windows antivirus.

When I start it, the download reaches halfway and hangs there for maybe half an hour, then the program closes. This didn't happen before.

I tried to run it with your command lines, same story. It just loads halfway and freezes

upd. it started up and seemed to work fine. It worked for 1 minute and froze. upd1. It works fine but freezes for half a minute. Then it works fine again, then freezes again. Unstable dumpcppc.txt

9qPEWJU8KX Not responding LogFile.txt

mann1x commented 10 months ago

Are you maybe running Hydra as well? Asking because when it starts the power plan is 1usmus.

Maybe it's not the latest b29 beta?

https://mega.nz/file/pm4GASTT#t_op3o1woHhKIOCC7YcszxpwX7EhQFN327yEU5glNl4

mann1x commented 10 months ago

If you still have issues try to enable in Settings the Diagnostic log.

If you started it with the command line switches you should have at least one LogTrace.txt, check it. Otherwise it didn't work, you need to try to start again with command line switches.

SnikS1337 commented 10 months ago

Hydra? Idk what is that. Poweplan is automatically switch to yours when program is open.

latest b29 beta still doesnt open. I use "start C:\Users\Administrator\Desktop\CpuDOC1\CPUDoc.exe -LogTrace=1 -inpoutdlldisable=1" in cmd. Maybe its wrong?

upd. beta is open after 3 minutes from cmd. But the computer starts to lag a lot when the program freezes. I type the text, and in 1 frame after 5 seconds it just starts to be written.

Here the LogTrace -

mann1x commented 10 months ago

Odd..

The command line was partially enabled:

2023-11-21 01:02:28.9806|INFO|1|cmdargs LogTrace=-1 2023-11-21 01:02:28.9806|INFO|1|cmdargs.inpoutdlldisable=1 AppSettings.inpoutdlldisable=False inpoutdlldisable=True vgc=False

Not sure why LogTrace is not enabled. Since you can boot try to enable in settings diagnostic logs, exit the program and restart

SnikS1337 commented 10 months ago

LogTrace.txt

mann1x commented 10 months ago

It seems something else is blocking the access to the CPU for monitoring. If it's that it should work if you set disable inpoutx64.dll in settings, check it out.

SnikS1337 commented 10 months ago

LogTrace.txt

upd 3:41. After 20 minutes, i open the program and its still working fine. And not lagging

mann1x commented 10 months ago

Something else is accessing the CPU, probably checking the PowerTable via the SMU. At the same time CPUDoc stopped working you must have installed something that interferes. Most likely a monitoring software or something related to the hardware, like a tool to control fans or similar.

SnikS1337 commented 10 months ago

That's the thing, I didn't install anything. I just started the PC at one point and saw that the program did not open. Before this, I didn’t install anything, I used my PC as usual

mann1x commented 10 months ago

Something has changed, maybe a silent update in background. There are no apps/services from Microsoft accessing and keeping busy the CPU SMU or the PCI bus; must be a 3rd party.

There's also the remote possibility the CPU is defective but I'd exclude it. Some BIOS options could mess with the SMU access but I guess you'd have told me if you changed something there recently.

Except this, there are very few other reasons that can explain why the CPU SMU can be accessed but it gets stuck during PowerTable refresh.

You could have been infected but I don't think I have ever heard about any virus hogging the PCI bus or even less the Zen SMU; I'd exclude this too.

Than there are the AVs which are just blocking or "throttling" the DLL but you don't have any.

Last explanation is another 3rd party app or tool which is monitoring the CPU and you don't know. Make a review of everything which is installed/running as app or service.

SnikS1337 commented 10 months ago

I honestly don't know, I haven't installed anything. Maybe RyzenMaster began to interfere? But I had it before. I even rolled back the backup, still nothing changed, but now it’s fixed. Everything is as always, everything is the same)

mann1x commented 10 months ago

You can try uninstalling RM but it's unlikely that's the issue. It does interfere of course but only if you use it. Unless it's running in background, not an issue. Better to close CPUDoc before using it.

Not sure how well you know the drivers you are supposed to have installed, you can check with Autoruns:

https://learn.microsoft.com/en-gb/sysinternals/downloads/autoruns

But beware doing any change you are not 100% sure about, it could render your system unbootable.

SnikS1337 commented 10 months ago

RM is not running. I rarely run it. I launched it when I bought a new processor and installed PBO. Then I found your program, it worked well. After that, I did not open RM.

The drivers are empty. At least everything I know. I check with my antivirus every week or two. Two antivirus programs, but they are portable.

I think we can close the discussion. The program is working well now. Aren't there some functions that work there, but I think they are not that important. Yes?

upd: I also have monitoring from Afterburner on my second monitor. The CPU temperature is turned on there. But again, this never bothered me. I've been using Afterburner for over 5 years.

mann1x commented 10 months ago

Definitely not AB, I ran it as well with CPU monitoring since ever.

I'd try to find out what is blocking the access to the SMU. It's not supposed to happen. Does ZenTimings works as expected if you open and close it like 20 times?

The functions you are going to lose are all those related to specific Zen support. So view/change of PBO limits and everything specific to AMD which I'll add later. It's quite a lot but nothing critical or mandatory to make it work. If you don't want/need those features it's even better to avoid loading the dll.

SnikS1337 commented 10 months ago

I didn’t quite understand about 20 times. Like restarting the application 20 times with xiounput enabled?

Could it be affected by the fact that I have AutoOC + Curve Optimizer in RM? It was there before... but suddenly...

mann1x commented 10 months ago

Just open and close it, if it can't access the powertable you'll get an error popup before it opens, missing details about the voltages. Do it 20 times and check if it fails and how many times.

The AutoOC + Curve should just changes BIOS settings. I think there's a way to keep it running but you should see it in the system tray if that was the case.

mann1x commented 10 months ago

If you can, please send me again the logs with diagnostics enabled and the DLL enabled. I don't see some details I was expecting.

Before sending the logs change the settings and close CpuDoc. Then open it, let it run one minute and close it. Send me the logs.

Then disable the DLL and also disable the diagnostic logs.

SnikS1337 commented 10 months ago

LogTrace inpout OFF.txt LogTrace inpout ON.txt

mann1x commented 10 months ago

I'd need also the corresponding LogInfo, there are different things inside, sorry!

SnikS1337 commented 10 months ago

oh sorry. LogInfo its a LogFile.... or what? LogFile.txt

mann1x commented 10 months ago

Thanks, the LogInfo is the standard logfile. If you enable Diagnostic Logs in settings more information will be logged there and additionally some other stuff, which could hinder readability in the main logfile, to the LogTrace.

Your problems are very likely due to the BIOS version or setting.

Seems you have disabled the CPPC Preferred Cores, there are no CPPC tags found for the cores. Can you confirm?

2023-11-21 15:58:46.9695|INFO|1|CPPC: C0:100 C1:100 C2:100 C3:100 C4:100 C5:100 C6:100 C7:100

The CPU is properly initialized but access to the PowerTable is blocked:

FO|1|Zen PM Table dump: Offset 0000 000: 0,00000000 Offset 0001 004: 0,00000000 Offset 0002 008: 0,00000000 Offset 0003 00C: 0,00000000 Offset 0004 010: 0,00000000 Offset 0005 014: 0,00000000 Offset 0006 018: 0,00000000

This issue is often caused by different methods to offset or override CPU vcore/vsoc or other changes of some options (like disabling LCLK DPM)

You should try reverting to defaults the BIOS and check if it works again. If so, review the BIOS settings, building up a new profile from scratch until you find which option is messing up.

SnikS1337 commented 10 months ago

photo_1_2023-11-27_07-33-25 photo_2_2023-11-27_07-33-25 photo_3_2023-11-27_07-33-25 photo_4_2023-11-27_07-33-25 photo_5_2023-11-27_07-33-25

SnikS1337 commented 10 months ago

LCLK DPM ALL AUTO

mann1x commented 10 months ago

Puzzling... Which model and bios version for the motherboard? Does HWInfo and Ryzen Master both display the CPPC tags for the cores and TDC/EDC values? First time I see it not working and it's not the AV or a BIOS setting.

SnikS1337 commented 10 months ago

gcSbJBhSoD Sorry for RU lang. I cant find in hwinfo CPPC tags.. asrock x370, last bios ver.

mann1x commented 10 months ago

Ah, didn't thought about the board chipset. I have seen similar issues with x370/x470. Not sure if it's a chipset limitation or bad integration of the AGESA in the BIOS.

Check that in HWInfo Settings -> General / UI -> "Snapshot CPU pooling" is enabled.

You should see "Core Performance Order (CPPC)" if the CPPC tags are readable, in the CPU section of the Summary:

Check also if in the sensors do you see the TDC/EDC levels:

SnikS1337 commented 10 months ago

ZGliZ0Gatv sensors are working too...

mann1x commented 10 months ago

In the summary the CPPC ordering is linear, while the Windows scheduler core ordering seems correct. The BIOS probably has a messed up ACPI table for CPPC. Not nice but also not a big deal, what's important is that Windows is using the right ordering.

Can you post the sensors screenshot of HWInfo including TDC/EDC with snapshot pooling? That should be using the same method as I use to gather the values. Those in summary are read differently.

Not sure why it can't read the PowerTable, the address didn't change with that SMU version as I know of. Also with SMU 56.76 on AGESA 1.2.0.A didn't change, I'm running it on mine.

Can you send me the ZenTimings Tools->Debug->Save As... output?

SnikS1337 commented 10 months ago

Debug_Report_28351389.757159.txt V3fMVuX4Kf QzPYS7XvmQ

mann1x commented 10 months ago

Unfortunately, no idea how to fix it. I can only guess there's something peculiar using the x370 chipset and we don't know how to handle it. Martin with HWInfo has a lot more technical documentation but he can't share it.

Just for curiosity, did you try ZenTimings in the past with this BIOS? Did it work?

Thanks for all the info.

SnikS1337 commented 10 months ago

I updated the BIOS back in 2022. Thanks for the help, I'll sit and twirl. At least I already know the reason

mann1x commented 10 months ago

Thanks! I'll close the issue.

mann1x / CPUDoc

The program stopped working on R7 5700X #10