lHolyDiverl

Results 11 comments of 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...

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...

> 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](https://github.com/irusanov/ZenTimings/files/8686575/ZenStates-Core.dll.zip) New...

> 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...

> Yeah, sorry. I did that at work, but the source was outdated. [ZenStates-Core.zip](https://github.com/irusanov/ZenTimings/files/8689394/ZenStates-Core.zip) No chanegs with this revision: `Index was out of range. Must be non-negative and less than...

> 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...

> 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](https://github.com/irusanov/ZenTimings/files/8689746/ZenStates-2.0-20220513.zip) to [ZenTimings_v1.2.6.619-debug.zip](https://github.com/irusanov/ZenTimings/files/8689729/ZenTimings_v1.2.6.619-debug.zip) leads to: ```Index was out of range. Must...

> Last try for now, added some more checks in the code > [ZenTimings_v1.2.6.619-debug.zip](https://github.com/irusanov/ZenTimings/files/8691162/ZenTimings_v1.2.6.619-debug.zip) Result is the same: ```Index was out of range. Must be non-negative and less than the...

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...

Got it. Here it is: I believe it is the last one before error occurs.