Jump to content

Recommended Posts

Posted (edited)

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 by Bass Guitar
Posted

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.

 

Posted

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.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...