Sonar 6.2.1 crash - MSVCR80.dll

Is there already a solution for this problem? (I've read a few other people had this problem, too).
When I open both Artist Drummer (DXi or VSTi, doesn't matter) and EZDrummer, Sonar crashes with this message:

I can load Artist Drummer or EZDrummer alone, but when I open both, it crashes. I have the latest XP patches from MS.

(I've read a few other people had this problem, too

I've seen the same error here after installing some software.. 6.2.1 (which worked/works fine) couldn't do anything (even not to record an audio track)..something with that MSVCR80 has changed and I wasn't sure which program did it.

There's a growing number of these WinSxS error reports. I'm sure we would love to see someone from Cakewalk sheding some light on why Sonar gets corrupted because of changes there (the Windows WinSxs folder)..it's something about sharing of dll files (maybe..i'm really not an expert..) but at the same time keeping different versions of these for different programs..anyways, Sonar gets totally corrupted when those VC files change.

I had to re-install..it helped (applying the 6.2.1 patch again) even WITHOUT cleaning everything first..yeah, sometimes I check how this stuff work without cleaning first and/or uninstalling..got nothing to lose.


Edit: I see the second post now.. I have to add that here it had nothing to do with plugins..Sonar simply didn't work at all (couldn't record) when that error was nagging about msvcr80.dll and the WinSxS.

ORIGINAL: mrbungle

Honest_Al, so what do you suggest, should I reinstall SONAR without uninstalling it? (Just install it over?)

I am not shure if it helps but maybe you could try to reinstall the 6.2.1 update (I think it is that one that adds the latest VC files).

DFUsion and SH are right on it..
each CW patch also extracts (your temp folder) and installs these VC files (the "vcredist_x86.exe" file - you can download it from MS..look for Visual C++ libraries or Visual C++ 2005 Redistributable Package)

It's sad to see Windows XP (and Sonar) acting like that (in 2007..and SP2 installed)... XP is runs here flawlessly, never a blue screen (for years) , no problems with DLL files
or "registry conflicts" or whatever.. It seems to run very smooth and handle 99.9% of the "oops..different versions installed" very well.. so as you see I wonder why such things still happen (the WinSxS and MSVC dll problems) -

I understand there are different versions and updates from MS (and Sonar still runs inside the Windows environment;) but it seems that no other programs had any problems with different versions of the visual C files..
isn't it weird that Sonar is "sensitive" like this?
could CW implement a check (as you launch Sonar) to verify it got all the right components installed? (and even leave a copy in its own folder of the vcredist file..then installing it automatically and re-launch Sonar automatically)

i too have seen these errors. much more in sonar 6 than 5.

ORIGINAL: Duojet

i too have seen these errors. much more in sonar 6 than 5.

Same here - random crashes like this one very frequently. I seem to notice them when I'm doing extensive clip editing/copying/moving. The only reason I'm still using Sonar is that at least when it crases it gives me the option to save the work in progress before it dies a horrible painful death. We should get V7 for free.

I've had it happen with magneto (steinberg) --and a few times a high whistling for a moment an the audio drops out, Hmmm.

I see this every day... Since i get use to it, it's not the problem anymore.. I won't load that VST so i will go to my sound module again. I will use hardware devices so Sonar won't crash

I never seen this on Sonar5

MSVCR80.DLL is part of the Microsoft Visual C++ runtime library, and as such is distributed with many applications other than SONAR. It's possible that installation of another application resulted in an older version of the library being copied. This is not an ActiveX library, so it's possible to have multiple copies on disk and which one gets loaded could depend on the order in which you started up various applications.

Run a search on your disk and find every instance of MSVCR80.DLL. Determine which one is newest and copy it into c:\windows\system32, then delete the duplicates. This way you have one instance of the library on disk and (hopefully) it's up-to-date.

Afterthought:
This DLL is part of a suite of libraries and support files, and you could also have issues if one of its dependencies was missing or out-of-date. It might be better to delete any found instances and then re-install using the redistribution package described by Honest_Al. This will make sure the whole set gets installed.

I'm experiencing the same exception message concerning the MSVCR80.dll. I've narrowed the problem down to the soft synth East West Quantum Leap Symphonic Orchestra Silver Edition. It seems that I can add any number of soft synths up until the moment I add EWQLSO Silver Ed. After that, I cannot add any soft synth without getting the exception message, at least not via the Insert > Soft Synths menu option. If I don't answer yes/no on the message it seems that I can still work with the current CWP-file,but the soft synth that I added doesn't seem to be associated with any audio track. Furthermore, it seems that I still can add soft synths by right-clicking in the FX-bins in the console, regardless of EWQLSO being previously loaded.

This leads me to believe that there is something wrong with the "Insert Soft Synth Options" dialog and that, for some reason, this way of adding soft synths differs from adding them to the FX-bin. The only difference that I could find in the manual is that there is no automatic connection to a corresponding MIDI-track when adding synths to the FX-bin (you'll have to connect it manually instead) but this doesn't account for the exception message since it still comes up when I un-check the option Create These Tracks: > MIDI Source. I've tried to un-check all the options in the "Insert Soft Synth Options" dialog, but nothing seems to steer clear of the exception message. Thus, there is something else being done in the background when adding a soft synth in this way compared to adding it to the FX-bin. I sure wonder what that is.

So, one work-around is to add soft synths to the FX-bins instead. However, I'm kind of a perfectionist, so I wasn't really satisfied with this. Synths belong in the synth rack, period :) Luckily, I've found another work-around: In the project where I first encountered this exception, I have three synths in my synth rack; the third being EWQLSO Silver Ed. Before adding the fourth synth, I disconnect EWQLSO by pressing the corresponding "power"-button in the synth rack. I then add the fourth synth (via the Insert > Soft Synths menu), which seem to be working fine. Then, I connect EWQLSO again via the "power"-button. It seems that I have to repeat this step every time I add another soft synth after EWQLSO has been added. But at least it works, and the result is a consolidated one compared to adding synths to the FX-bins.

I've tried to reinstall the Sonar update 6.2.1, and during this installation a redistributable is installed (don't know if it is the one mentioned above though), but the result is the same. I had two MSVCR80.dll-files in my system; one of them was the newest one (8.0.50727.762) and the other was older (8.0.50727.42). I removed the older one and replaced with the newer, but alas the result is the same.

I'm happy with the work-around for the time being. At least I can still make music. :) Sure hope Sonar programmers take a look at this problem though, and I hope the work-arounds are of any help for you guys.

I'm wondering if it's a conflict with Protools M-Powered 7.4 since it also uses the runtime library?

It's probably a conflict with something. For me, I think it's Amplitube v1.0
Since I stopped using Amplitube with RealGuitar, I haven't got that error.

bump ... anyone else still getting such errors? here it's only sometimes but you can never know when it will hit you again (when working with some synths)

Most likely the side by side configuration on your computer is corrupt. Its unlikely to be a SONAR error but you can submit a problem report with a minidump attached (Very important!) and we can look at the exact crash location. Perhaps that might indicate a possible solution. I hope other applications are not manually putting files there since the files there are supposed to be only managed by the Microsoft redistributables installer. Those files are the Visual C++ runtimes and are required by many applications besides SONAR.

This hit me Sunday morning, in a project that had opened OK the night before. No software had been installed or updated in the interim, no Windows configuration changes.

I verified that MSVCR80.DLL was up to rev, rebooted with minimal config, the project still crashed.

I'd made a backup of the project the night before, but because I'd edited some clips after the backup I decided to try just restoring the CWP file. SONAR opened the backup CWP without any problem.

So I now have two nearly-identical CWP files, one that always opens OK and one that consistently crashes with
"Faulting application sonarpdr.exe, version 16.0.1.188, faulting module msvcr80.dll, version 8.0.50727.762, fault address 0x00017471." followed by "Faulting application sonarpdr.exe, version 16.0.1.188, faulting module ntdll.dll, version 5.1.2600.2180, fault address 0x00043345.".

Both projects have the same plugins, same MIDI tracks, same audio tracks. The only things that were modified after the backup were two audio clips (edited with Adobe Audition) and some volume envelope adjustments.

My tentative conclusion is that the error is caused by a corrupt CWP file.

Will do.