MIDInco Posted January 31 Share Posted January 31 (edited) Does anyone know how to deal with crashes caused by the error code C0000005 (Access Violation)? This error seems to be triggered by the function m7_ippsLn_32f_A21, which is part of Intel IPP (Integrated Performance Primitives). From my research, it appears to be an error related to memory access conflicts. Many users in this forum insist that "Sonar has no bugs." However, when working on large-scale orchestral compositions exceeding 100 tracks or producing complex bass music like Dubstep with intricate automation and effect chains, Cakewalk frequently hinders my workflow with numerous bugs. One of the most persistent issues I've been dealing with recently is this error caused by m7_ippsLn_32f_A21. The conditions for this error vary, but it occurs most frequently when automating Serum, a well-known synthesizer. (Though to be clear, it happens in many other situations as well.) It occurs consistently across both large and newly created projects, making it highly reproducible. And just to be clear, this error does not happen in any of the following DAWs that I own: Cubase, Studio One, Reaper, Bitwig Studio, or Ableton Live. Since this error involves an Intel library, I asked a programmer friend who owns a Gen14 Intel Core i7 14700K to install Cakewalk by BandLab and test my project file. The result? The exact same crash occurred under the exact same conditions. (My friend explained some technical details to me, but unfortunately, since I'm not a programmer, I couldn't retain most of it.) Additionally, I found a similar crash report related to this function on GitHub, where a Korean Cakewalk user described the same issue: https://github.com/surge-synthesizer/surge/issues/4838 That thread suggests a potential issue related to Unicode and OS compatibility, which I also suspect could be the case. Since I am also from Asia, this may be a common factor. I’m planning to buy a new PC soon and will try setting it up with an English version of Windows to see if it makes any difference. I have already contacted Cakewalk support and tried the following solutions: ・Deleting Cakewalk-related registry entries and reinstalling Cakewalk Sonar. ・Uninstalling and reinstalling the Visual C++ Redistributable. None of these have resolved the issue. Here are some possible solutions I’m currently considering: ・Switching my CPU from Ryzen to Intel. (Both Cakewalk support and my friend say this is unrelated, but I’m not ruling it out.) ・Memory shortage. (However, the dump file indicates over 10GB of free RAM, so this seems unlikely.) ・Setting up an environment with an English version of Windows. (Since Roland ended support for Sonar over a decade ago, continuous updates may have gradually broken compatibility.) If anyone has encountered this issue or has any suggestions, I would appreciate your input. Finally, for reference, here are the details of my environment: Sonar Version: 2024.12 (Build 004, 64-bit) Main PC ・OS: Windows 11 24H2 (Updated yesterday; no change in the error.) ・CPU: AMD Ryzen 9 7940HS (16 threads / 8 cores, Base Clock 4.00 GHz) ・RAM: DDR5 64GB ・GPU: Radeon 780M ・Storage: SSD 1TB + 2TB ・Audio Interface : RME Babyface Pro FS Sub PC ・OS: Windows 11 23H2 ・CPU: AMD Ryzen 9 3900X (24 threads / 12 cores) ・RAM: DDR4 64GB ・Storage: SSD 512GB + 2TB, HDD 8TB I use ChatGPT. Sorry, my bad English. Edited January 31 by xmirrorimage Link to comment Share on other sites More sharing options...
reginaldStjohn Posted January 31 Share Posted January 31 Have you sent a crash dump file to support? support@cakewalk.com. Link to comment Share on other sites More sharing options...
David Baay Posted February 1 Share Posted February 1 22 hours ago, MIDInco said: Many users in this forum insist that "Sonar has no bugs." I just Googled "has no bugs" site:discuss.cakewalk.com. I got two hits; one was yours and the other was "Please name one bit of complex software you own that has no bugs". On the old forum you get "As if Cubase has no bugs... LMFAO.." and "I swear this is probably the same cat dropping his Logic-has-no-bugs propaganda..." Regarding your issue, check the .txt file that was created along with the .dmp file for more info. If the crash is in the plugin I would send the dump to the plugin vendor first. If they find that the trigger is something non-standard that Sonar is doing, they can refer it to the Bakers themselves with details from their analysis. Link to comment Share on other sites More sharing options...
sjoens Posted February 1 Share Posted February 1 Try googling "rock solid". Many have contested whatever version of SONAR/CbB they use is just that, which I guess means it never crashes or exhibits any bugs. They ignore or never see the bugs the rest of us do because they aren't using those features or they have a clean system that doesn't interfere with their DAW... or they simply live in denial of what constitutes a bug. But more and more users have been reporting otherwise the past couple years. Some of whom used to claim "rock solid" have and some of those have even left the building. I've had nothing but crashes and bugs since X1 but I'm still here. Just the other day CbB crashed right after simply opening with no project loaded. I figure it's the price of using my laptop for EVERYTHING. A DAW specific system might not be so bug prone. 1 Link to comment Share on other sites More sharing options...
MIDInco Posted February 1 Author Share Posted February 1 (edited) 6 hours ago, reginaldStjohn said: Have you sent a crash dump file to support? support@cakewalk.com. There is no fool who would contact support without sending a dump file. I have already sent about three dump files. Edited February 1 by MIDInco Link to comment Share on other sites More sharing options...
MIDInco Posted February 1 Author Share Posted February 1 1 hour ago, David Baay said: I just Googled "has no bugs" site:discuss.cakewalk.com. I got two hits; one was yours and the other was "Please name one bit of complex software you own that has no bugs". On the old forum you get "As if Cubase has no bugs... LMFAO.." and "I swear this is probably the same cat dropping his Logic-has-no-bugs propaganda..." Regarding your issue, check the .txt file that was created along with the .dmp file for more info. If the crash is in the plugin I would send the dump to the plugin vendor first. If they find that the trigger is something non-standard that Sonar is doing, they can refer it to the Bakers themselves with details from their analysis. If it's the exact same sentence, it might be just me. There are many ways to phrase things and various sentences in the world. Isn't it a bit short-sighted to search for a single sentence and conclude, "You're the only one who said that"? Upon checking the dump file, I found that the function m7_ippsLn_32f_A21 is causing the error. Additionally, the dump file contains the entry "IsPluginCrash: 0", indicating that the likelihood of the error being caused by a third-party plugin is low. Link to comment Share on other sites More sharing options...
MIDInco Posted February 1 Author Share Posted February 1 41 minutes ago, sjoens said: Try googling "rock solid". Many have contested whatever version of SONAR/CbB they use is just that, which I guess means it never crashes or exhibits any bugs. They ignore or never see the bugs the rest of us do because they aren't using those features or they have a clean system that doesn't interfere with their DAW... or they simply live in denial of what constitutes a bug. But more and more users have been reporting otherwise the past couple years. Some of whom used to claim "rock solid" have and some of those have even left the building. I've had nothing but crashes and bugs since X1 but I'm still here. Just the other day CbB crashed right after simply opening with no project loaded. I figure it's the price of using my laptop for EVERYTHING. A DAW specific system might not be so bug prone. So there is a term called "rock solid." Unless the software is exceptionally well-made, I feel like being truly "rock solid" is almost impossible... I've been using Sonar since the X2 era. Sonar's MIDI editor is incredibly easy to use, and I can't imagine composing orchestral music with anything else. I once had similar thoughts as you and decided to buy a brand-new PC. I did a completely clean installation of Windows and set up an environment with only Sonar and VST plugins. In the end, I experienced the exact same crashes and ended up just wasting my time and money. Link to comment Share on other sites More sharing options...
sjoens Posted February 1 Share Posted February 1 There are custom made DAW specific systems out there but I've never tried one as they are typically 2x or 3x the cost. Link to comment Share on other sites More sharing options...
MIDInco Posted February 1 Author Share Posted February 1 15 minutes ago, sjoens said: There are custom made DAW specific systems out there but I've never tried one as they are typically 2x or 3x the cost. It's difficult to find overseas DAW workstations from Japan, but I took a quick look. https://www.scan.co.uk/3xs/configurator/3xs-az-audio-workstation-music-production-system In the case of this PC product, all the components inside are available for individual purchase, so if we really wanted to, we could build the same system ourselves. It doesn’t really feel like a dedicated DAW workstation... (I think my search method may have been flawed, so there might be genuine professional workstations out there if I look harder.) Link to comment Share on other sites More sharing options...
sjoens Posted February 1 Share Posted February 1 (edited) There are a few in the USA claiming to be such. studiocat.com PCAudioLabs.com The key to a good DAW system is using it ONLY for that, nothing else. Something the average hobbyist isn't likely to do. Edited February 1 by sjoens 1 Link to comment Share on other sites More sharing options...
pwalpwal Posted February 1 Share Posted February 1 10 hours ago, sjoens said: The key to a good DAW system is using it ONLY for that, nothing else. Something the average hobbyist isn't likely to do. tbf, it's totally possible to use a pc for daw plus other purposes, i certainly do, we don't all have a budget for two pcs /goodluck 2 Link to comment Share on other sites More sharing options...
David Baay Posted February 1 Share Posted February 1 3 hours ago, pwalpwal said: tbf, it's totally possible to use a pc for daw plus other purposes, i certainly do, we don't all have a budget for two pcs Me too, but it's more about the burden and inconvenience of maintaing separate machines than financial limitations. If the DAW were my primary income source, I might think about isolating it, but then more for stability (as in unchanging) and security of the ecosystem than for performance. In my experience, significant audio performance degradation doesn't usually manifest as slow death by a thousand cuts of all the incidental software installed on a machine; it's usually all good until some single entity completely trashes it, like a new or updated plugin, driver, O/S component, hardware or configuration change or a problematic update to the DAW app itself. The thousand cuts might shave 10% off the ultimate performance capability of the machine in terms of a low and stable DPC latency and fast RAM/disk response that are the foundations of good, low-latency DAW performance, but they're not going to make or break the servicability of the system. Link to comment Share on other sites More sharing options...
sjoens Posted February 1 Share Posted February 1 Me three. That's why I said what I said. Link to comment Share on other sites More sharing options...
pwalpwal Posted February 1 Share Posted February 1 I don't have any income source from the daw haha wish I did lol Link to comment Share on other sites More sharing options...
pwalpwal Posted February 1 Share Posted February 1 Also, paragraphs Link to comment Share on other sites More sharing options...
msmcleod Posted February 2 Share Posted February 2 On 2/1/2025 at 5:01 AM, sjoens said: The key to a good DAW system is using it ONLY for that, nothing else. Something the average hobbyist isn't likely to do. On 2/1/2025 at 3:21 PM, pwalpwal said: tbf, it's totally possible to use a pc for daw plus other purposes, i certainly do, we don't all have a budget for two pcs /goodluck There's the middle ground compromise that I use... stick in another drive and have a dual boot - same PC hardware, two installs of Windows. I've got one boot that is only for DAW use and another for more general use. 3 Link to comment Share on other sites More sharing options...
Noel Borthwick Posted February 6 Share Posted February 6 On 1/31/2025 at 9:02 PM, MIDInco said: Upon checking the dump file, I found that the function m7_ippsLn_32f_A21 is causing the error. Unless you have the symbols the function name will be meaningless. If you have a repeatable crash from a recent build of Sonar send me a link to the dump and I can check the cause of the crash. Sometimes dumps don’t give us the full picture… Link to comment Share on other sites More sharing options...
Matthew Simon Fletcher Posted February 6 Share Posted February 6 (edited) On 1/31/2025 at 1:07 AM, MIDInco said: The conditions for this error vary, but it occurs most frequently when automating Serum, a well-known synthesizer. (Though to be clear, it happens in many other situations as well.) I have recently had a crash whilst working on automation with Serum - but it's not been reproducible to the point that I've raised a case with Sonar/Xfer yet. I also can't recall it generating a plugin crash, so something else might have been going on in Sonar at the time. If you have a project that you believe has had the issue I'll happily try and test further. Edited February 6 by Matthew Simon Fletcher Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now