So you never saw the MadExcept prompt show up to report a crash?

I see that you are running in Admin mode. Except for programming remote buttons, that's not needed. Perhaps you run everything as admin, but if you're doing anything special, please try just running with regular privileges.

Please ...

You forgot to include the "bugreport.txt" file, it should be in your root CMC directory.

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

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

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

My System32:
image.png


And my SysWoW64:
image.png


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

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

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

Well, CMC itself doesn't really have an original folder name. It just lives where you unzip it. I normally put it in CMC, but I notice that you like to name it for the version. That's fine and all, but can lead to problems with CCC.

Now, CCC.exe lives in a folder named CCC, which is inside of that ...

It looks to me like you may have renamed the directory after install, is that right? The path looks weird.

CCC is very sensitive to directory name changes, and/or moving the directory after setup.

No, I don't there is.

Now, I don't have v5, so I haven't been able to test this myself.

But Binnerup is on record saying they were removing this capability from v5. For that reason, I will be sticking with my legacy v4 version for as long as it works.