These projects crash on W11 SOLVED .

[Bass Guitar]

Going back a year ago and I was using new Sonar and my computer was on W10. There were these projects that always crashed. There's about 200 of them and they are pure midi projects, no audio,  There are no effects other than Loud Max and the You Lean meter on the Master.  Just a few standard instruments. Ones I have used on hundreds of projects. 

Last march I wiped the machine and installed W11. I've only been using Platinum since then giving up on Sonar because of this. 

I was on a vacation and took my laptop. I was starting to work on these projects again but Platinum is old and stupid so I just bought a membership and installed Sonar.  

The projects all opened without issue.  They still do on the laptop. 

I just returned home so I installed Sonar and all the add on's using the CPC to my W11 computer. So a fresh install of New Sonar. The same exact projects still crash. 

They will crash on loading. If I use safe mode this reveals there are what appears to be orphaned Pro Channel modules. See screenshot for example. They will all be labeled as Unknown. Sometimes Sonar says there's an issue with Addictive drums??  Then just now I get a quick flash of a crash stating it was You Lean loudness meter?? 

I don't always get a Mini dump to looks at, Mabey on half of them. 

The crash dumps.

2 say windowscodecs  google says The windowscodecs.dll file error often indicates an issue with corrupted system files, outdated drivers, or conflicts with a specific third-party application, particularly one that handles image or video files. The issue can cause application crashes (e.g., photo viewers, creative software) or general system instability. 

  7 say   ucrtbase    Google says The ucrtbase.dll error is a generic crash report that indicates an issue within the Universal C Runtime Base library, a core Windows component. The DLL file itself is usually not the direct cause but rather the module that reports an underlying problem in the application, a third-party driver, or a corrupted system file. 

1 says VCruntime140 which is another C++  

Then there one says ntdll which google say's When a crash report indicates ntdll.dll as the faulting module, it is important to understand that ntdll.dll is rarely the actual cause; it is the Windows NT Layer DLL that reports the exception, meaning the actual issue lies in a different application, driver, or system component that made an invalid call. 

So what the heck is wrong with my W11 computer, And it did exactly the same thing under W10 a year ago?  

Are not all the C++ runtimes installed with Sonar? 

The Laptop is a piece of junk i5 1 core 2.30 Ghz  12 GB RAM.  It has graphic issues with Sonar but hasn't crashed. 

My main computer is 3th Gen Intel(R) Core i5-13400F (2.50 GHz) 10 cores 64GB RAM 

As a note one thing comes to mind is these projects are from around 2019- 2023. They used mostly VST 2 versions of plug ins. Now I don't even install the VST 2 if there's VST 3. Only for a few things.  So what happens is Sonar reports them as missing even though they are there as VST 3's. I just have to replace them.  Can having missing plug ins cause Sonar to crash? But then the Laptop is set up exactly the same? 

I've included a few files that crashes on my W11 computer.  

Could a few of you please test these and see if they open for you. 

 

 

 

 

Hey Baby.cwp Am I blue.cwp Memphis.cwp

Edited 4 hours ago by Bass Guitar
Mark as Solved

[Base 57]

First one opened. I replaced the plugs I don't have and it played fine. When I closed it, it crashed. Now it crashes when I try to open it. Second one, instant crash. Not going to bother with the third.

 

[57Gregy]

All of them opened for me on Win 10 box. Got the 'missing plug-ins' message. I don't have them.
Didn't try to play them, but they opened.

[Base 57]

Out of curiosity, I opened Hey Baby in Safe Mode. Works fine now.

FWIW, I am still on W10 also.

[Bristol_Jonesey]

Opened the first one without issue on my Win 11laptop apart from the missing plugin warnings.

It let me play it and close it.

[Bass Guitar]

Thank you @Base 57  @Bristol_Jonesey &. @57Gregy  for testing those. 
 

If all 3 of you had no problems then that would then confirm that it’s this particular computer. 
But Base57 is experiencing what I am seeing. 
 

Sometimes I can get as far as the project opens but when I hit the space bar or click on anything it crashes. 
 

So they are on the edge. 
 

Could you guys check the Pro Channels and see if the EQ is there. in particular Base57 and Hey Baby in Safe Mode. 
 

If I open in safe mode it always shows all the active pro channel modules as labeled “Unknown “. 
And after it opens when I open the pro channels there is no EQ, it is all blank. That’s not possible. 
 

These projects are not mission critical they are just backing track projects that have all been finished and exported. But I was hoping to back them up as midi files which I still can do by using safe mode. 
It’s just that it makes me not really trusting Sonar with future projects. 
 

I submitted a ticket to the AI with these projects attached. 
I tried to submit a few mini dumps but it kept saying the connection was taking too long?? 
I will wait for an actual person to respond. 
I will also try re installing the C++ stuff if I can find it again. 
 

Thanks once again I appreciate your help. 

Edited yesterday at 03:37 PM by Bass Guitar

[Bass Guitar]

No word from Support. but what I did was the following. 

First I opened the folder and set up so it shows the date Modified. This reveals when the file was last updated and saved. 

I then spent around 3 hours opening each one and making notes. 

I had the crash dump folder open to one side so I could run Windbg as they happened. 

What was revealed is that only projects dated between April to Aug 2023 all crash. The rest don't.  

WinDbg blames just about everything, Lots of Wincodecs, UCRT Base , then it blames You Lean meter and Addictive drums, Ample P bass and so on. I think that is false information. Because all of these projects when opened in safe mode will have the "Untitled EQ etc.  

 

So now I'm trying to figure out exactly what was happening to Cakewalk at that time that corrupted any projects I worked on during that period. This would be the spring we were told Cakewalk was going to be discontinued and all that BS. So I was using Cakewalk. My next move is to find out somehow which version that was,  and dig back on the forum here for any clues. I will look for issues with the Pro channel at that time.

I think for sure there was an update in early September, I remember that well because that was when they added the hyper active log in system. But all files saved after then are fine. 

At least it is only about 35 projects that are bonked, Not 130. 

Oh, and I can still open these on my Laptop and the Pro Channel is not screwed up??? At least so far I've tried about a dozen. THAT is the big mystery. 

 

Edited 23 hours ago by Bass Guitar

[Bass Guitar]

I think I might have found the reason why all the projects that I worked on in the Spring of 2023 are corrupted. 
 

I went back to page 37 of the Cakewalk forum and I noticed a post by me chatting about the news of Sonar and Next. In the post I mentioned how I had just bought 3 new SSD drives and upgraded my computer. 
I remember clearly that I used the Samsung Magician to clone my C drive! 
I also mentioned having a bunch of gigs coming up. 
Put 2 and 2 together and that would have me working on a few backing tracks and that that state of Cakewalk was buggered by the cloning process. A few ones and zeros were wrong somewhere in the Cakewalk code. 
The dates line up perfectly as the next update was in late August or early September. The update repaired Cakewalk. 

And it’s just something in the pro channel code that got corrupted. 
 

That computer was replaced by a brand new build on Nov 15 that year. 
 

Anyways this forum is a great resource for tracking your own personal history! 
 

[57Gregy]

If you have the patience!