App crash when opening

[p64imp]

Hi,

I'm installing the client on a new system and it flashes and closes. Event viewer shows this issue. How can i get around this? ntdll.dll is a protected system dll that is constantly in use, so replacing it is not a great idea. Seems a update to this system resource broke CMC from opening?

Faulting application name: CMC.exe, version: 7.0.2023.1031, time stamp: 0x65415fc2
Faulting module name: ntdll.dll, version: 10.0.26100.3323, time stamp: 0x22ecef5b
Exception code: 0xc0000005
Fault offset: 0x00083cad
Faulting process id: 0x8C84
Faulting application start time: 0x1DB9826132A91F3
Faulting application path: C:\ChameleonMediaCenter2\CMC.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 5d27e0f7-bcdc-42c4-b389-eac4cbf46c08
Faulting package full name:
Faulting package-relative application ID:

Event viewer logs

[Pauven]

No, there should not be any reason to mess with ntdll.dll.

I need you to run CMC in debug mode. Since you can't start it, I'll need you to edit the CMC.cfg file manually.

Find the DebugLoggin=False line, and change it to True, and save the change.

Then try to run CMC again.

Send me the new files that were created in the Logs directory.

[p64imp]

files attached. ran off a brand new install. Please let me know what the issue is?

Thanks!

[p64imp]

These logs may be a bit more useful. I copied the instance that runs no issue on another pc, i opened ccc.exe and updated the user/password. i checked the log and noted the connection is successful. And yet, the app still crashes...

how come?

[Pauven]

Oh, wow, you have the brand new Ryzen AI MAX+ 395, very nice!

Looks like it is dying right before it shows the form. I'll have to investigate further to see if I can find a reason why.

UPDATE: So I looked at my code, and it literally is dying between the form creation (which completes perfectly) and the form showing (which never starts).

Both of those procedures are wrapped in error handling, yet no errors are being logged. This is very odd.

I'll have to think about this some more. Just throwing out ideas - perhaps it's related to your APU? That CPU/GPU is very brand spanking new, and there could be a BIOS or driver bug that is triggered by CMC. Don't get me wrong, I'm not trying to pass the buck or play the blame game, but since this is a new issue only occurring on this PC, chances are it is hardware related in some fashion.

In the mean time, can you make sure your BIOS/firmware/drivers are all up to date. Primarily stuff related to CPU and GPU, not much else matters.

UPDATE 2: Exception code 0xc0000005 is an Access Violation error, which means the code is trying to access something that doesn't exist. The offset isn't 0 - if it was that would mean a variable didn't get initialized, so that's good. NTDLL.dll is the Windows Native API, basically it's how CMC talks to Windows to do basic Windows stuff (i.e. like show something on your screen). Taken all together, it seems we're trying to access something via the Windows API that isn't there, and since it occurs at the exact moment CMC is trying to show the screen, which would be via NTDLL.dll, that seems more than coincidental.

So definitely make sure BIOS/firmware/drivers are up to date. If that doesn't help, I'll have to send you a special version with an exception logger so we can figure out more.

[p64imp]

wow, thanks for the incredible research!

I'm a software developer myself so i'm tracking all you said.

The system is fully up to date. I use Armory crate regularly to make sure i'm 100% current, and i last updated about 5 days ago. There's no pending updates found.

And ty, it's a pretty amazing little device! And HARD to come by right now too! I'm really hoping to get CMC running as i'm dedicating this device as a little movie monitor while i'm working Frees up my personal laptop to focus on emails coming in etc.

I did compare dll's and if it helps, and interestingly found the only diff is the file size. the version stamp on both is identical. see attached image.
OLD = my workhorse PC where CMC runs fine. NEW is my 395 where cmc is hitting the issue.

[Pauven]

I think you may have accidentally compared the System32 ntdll.dll vs. the SysWoW64 ntdll.dll

My System32:

image.png (40.29 KiB) Viewed 2891 times

And my SysWoW64:

image.png (37.37 KiB) Viewed 2891 times

While our date stamps are ever so slightly different, it seems you're running a good version the best that I can tell.

I think the next step is for me to provide you with a MadExcept enabled version so we can log that exception. If MadExcept sounds like a familiar name, it's because it's written by Mathas Rauen, aka Madshi, of MadVR fame. It's a cool little plugin that will allow us to capture a ton of data at the time of a critical failure like this. The downside is that it does seem to cause problems on its own, so I can't ship with this enabled for everyone.

I'll post here when its ready.

[Pauven]

A note on using this MadExcept version: MadExcept will report all issues with a pop-up (can be quite annoying), for even the smallest things. For example, my CCC was busy doing a full export, and so I got a socket not available error, something CMC normally handles silently. But with MadExept, I get this:

image.png (31.83 KiB) Viewed 2889 times

Essentially, you'll need to hit Continue Application. Our goal is to replicate the total crash to desktop.

After a crash happens (or anytime you see that popup), a new file named bugreport.txt will be created in the CMC folder. That's what I'll need.

[Pauven]

Alright, a few more notes on this version.

This is v7.1 Beta 1, which has some bug fixes compared to the v7.0 you are currently running. Nothing major, and nothing I would expect would solve this problem, but it is possible the newer version alone fixes things. Because it is newer, you'll need to update CCC (and CME if you use it) along with it.

This was also compiled with the latest 12.3 version of my IDE, while the v7.0 you are running was compiled years ago, I believe on 12.0 or perhaps 12.1. v12.3 has literally been out about a week, it is extremely new. Sometimes new IDE revisions introduce brand new issues, and sometimes they resolves issues. As a developer yourself, you know. 12.3 is supposed to have enhancements for the very latest processors, so I'm hoping the solution for your AI MAX+ 395 could be as simple as me using this new compiler.

This special build was compiled with MadExcept enabled, and in Debug compile mode. That means it is over 3x larger and runs slower, but it is more likely to give helpful info if and when something crashes. I don't recommend this build for anyone not currently troubleshooting CMC issues.

CMC v7.1 Beta 1 Debug with MadExcept

[p64imp]

Executed, and same issue sadly. Logs attached.