Stewart Kingsley

There is a miniDump file in Roaming\Cakewalk\Sonar\MiniDumps but its too big to attach (6.8Mb).

There is no Crash dump folder. It never got to that point.

As I said, there are no crash reports, it seems to crash before the crash report system starts. Unless there is a command line switch or something to turn it on before its turned on?

minidumps of what? The program crashes silently and does not provide any indication of what is happening.

Application Error: 1000 Faulting application name: Sonar.exe, version: 31.7.0.84, time stamp: 0x6871641a Faulting module name: Sonar.exe, version: 31.7.0.84, time stamp: 0x6871641a Exception code: 0xc0000005 Fault offset: 0x00000000006b552b Faulting process id: 0x31BC Faulting application start time: 0x1DBF35168B247FA Faulting application path: C:\Program Files\Cakewalk\Sonar\Sonar.exe Faulting module path: C:\Program Files\Cakewalk\Sonar\Sonar.exe Report Id: a134e34d-56ad-476b-a966-59ad360e7acb Faulting package full name: Faulting package-relative application ID: Windows Error reporting: 1001 Fault bucket , type 0 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: Sonar.exe P2: 31.7.0.84 P3: 6871641a P4: Sonar.exe P5: 31.7.0.84 P6: 6871641a P7: c0000005 P8: 00000000006b552b P9: P10: Attached files: These files may be available here: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_Sonar.exe_3492c9dae99c859efc9b94b8a72f4826cd7ba0c5_b265c456_818c837e-39a2-44d6-bb86-2657129023f7 Analysis symbol: Rechecking for solution: 0 Report Id: a134e34d-56ad-476b-a966-59ad360e7acb Report Status: 4 Hashed bucket: Cab Guid: 0 Windows Error reporting: 1001 Fault bucket 1595593941533195849, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: Sonar.exe P2: 31.7.0.84 P3: 6871641a P4: Sonar.exe P5: 31.7.0.84 P6: 6871641a P7: c0000005 P8: 00000000006b552b P9: P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.4c304880-a61e-49e3-bc46-140c1505ce27.tmp.WERInternalMetadata.xml These files may be available here: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Sonar.exe_3492c9dae99c859efc9b94b8a72f4826cd7ba0c5_b265c456_818c837e-39a2-44d6-bb86-2657129023f7 Analysis symbol: Rechecking for solution: 0 Report Id: a134e34d-56ad-476b-a966-59ad360e7acb Report Status: 268435456 Hashed bucket: 233ab6296666c9327624b03c6ad9fe49 Cab Guid: 0 WER.4c86810c-2ddc-491b-8f78-8d245810ee7a.tmp.WERInternalMetadata.xml

Latest version of Sonar still will not continue starting after showing the splash window. Is there a way to get some kind of diagnostics information that I can then post to show the issue I have?

Hi I have not used Cakewalk for some time as I now utilise Vb-Audio Matrix and Voicemeeter. Since I started using these now essential tools Cakewalk will not start properly. Upon opening Cakewalk the Splash opens, even the first time run dialog opens, but after that the program quietly ends. No error message, it just ends quietly. If I had some debug information to provide then i would be more than happy to provide it. But since it does not give any error messages I am at a loss to how to assist. Until then Cakewalk is unusable for me. Regards Stewart Kingsley

Mine was set 3, changing that to 2 has solved my latency issue and also the crackling problems. Good job!

I Found another thread with a similar problem with latency and someone posted the following... Noticed that I had mine set to 3, setting it to 2 and voila crackling had gone. To confirm the test I put it back to 3 again, and the crackling returned. So I recommend that you check the ThreadSchedulingModel setting and set it to 2.

Having the same issue, the crackling continues no matter what ASIO buffer size is used. Also the performance indicator shows there is no overloading of the PC. There are no problems in others DAWs or using standalone versions of the virtual instruments. Since this is something that has only recently become an issue, it can only really be a Cakewalk issue, potentially one that has been introduced recently to the code instead of something that has changed in the OS that affects just the Cakewalk DAW. Hopefully it will get resolved quickly before it becomes an issue that turns people away, especially with the new features.