Search the Community

A new occurrence - I can't say if it happened in previous versions, cause it's the first time I've used it - is that the Hornet SW34EQ plugin gets completely scrambled every time I open a project that includes it. All the gain knobs jump to max, the input-output link button gets engaged, the input and output settings are reset to 0, the hiss level is reset to default, and the plugin is turned off from the frame - even if it appears active in FX bin. This is very similar to things happening in the past - Softube Tape and Embertone Sensual Saxophone fully resetting on Stop/Play commands, or Waves REQ6 and H-EQ bands jumping to max value, on pressing the same. Additionally, the double arrows that open the Synth Rack/Browser/Help windows are missing - that's something I've reported a long time ago, not fixed, the toast notifications still don't go away by themselves, and the order of these three windows still gets reset, on some projects. The Arranger track always missing on open, even though it's saved with it on, so on so forth. That's just a small part of the minor stuff. Another thing that I've noted recently is that now plugins crash when i turn on/off other plugins up the chain - for instance Waves dbx crashes when I turn on/off the PA Helios Bus, in the bin, five plugins upchain, or PSP Delay crashes when I turn on/off the Reason Rack . Many times turning on/off makes pop sounds, some times the ML Drums channels start making this huge whistling/hiss noise that covers everything - not good when you're wearing headphones, I can tell you that - and a bunch of plugins keep crashing the DAW - if I remove one, another one crashes - I've gotten to 6 separate plugins crashing the DAW, on one project, at different times. Other times, CW just crashed by itself - CW core. The code is c0000005 or c0000005d. I've got all the VC redists installed. Virtual instrument outputs stops or it gets desynced every time I reposition the playhead in the time line or change the loop selection. That's some of the not so minor stuff. Not the worst. The more serious problems are wave clips that I find moved in the timeline - the contents of the clip gets repositioned when I trim the clip edges, other times various slices appear in various positions in the lane, hidden underneath other clips, so on. There's dozens of types of problems, in this department. This is the serious stuff. These are all old, and have never been fixed.

Hi everyone, Long time, no post. Installed the new release, first action was a crash on open - not finding Softube Tape activation, for some reason the activation gets reset randomly, usually after a few hours, sometimes after minutes, no connection to CW - for which reason CW reported a crash with Waves dbx - code c0000005, which seems to be related to VC++, even though everything is installed and up to date. Reinstalled iLok, loaded up fine, Tape working, except the settings of all its instances in the project were reset to default, as if they were never set up at all. All Waves plugins get scanned at each start, otherwise the project loads without them, so, if it crashes 10 times a night, which is not at all uncommon, 10 times I need to wait about 2 minutes for the scan to complete. The toast notification for the scan never goes away after the scan is complete. In all of these respects, seems that nothing has changed. I haven't participated in the discussion about the new planned releases for CW, but, in my opinion, CW is not remotely in the same league as being ready for a commercial release - and I'm only scratching the surface of the introduction here. I must have about 50 captures of things going wrong in the last few months - meaning 50 different issues, not repetitions of the same. I meant to send them to the developers, but never got around to it. Just my two cents. Will continue to work with the new release.

That and girls. I've had many an access violation. Seriously, great overview of the issue. C0000005 is frustrating to deal with. And there have been times where the developers were able to point to the specific issue and contact the VST company. It's not silence like some believe.

I'm not battling anyone, nor am I blindly defending my preferred DAW. Just basic troubleshooting while trying to avoid a classic causation vs. correlation logical fallacy. Let me explain my reasoning, and feel free to correct any logical errors I may make in the process. Let's start at the beginning, by looking at what a c0000005 error is, and how it comes to be raised. This particular error code represents an access violation, which means the software has attempted to write to an address location that it does not have permission to write to. Usually, this is the result of an uninitialized pointer, a variable that contains a memory address but that hasn't been given a value. Because all variables initially default to zero, the pointer is pointing at address 0. Although 0 is a valid memory address, it's in a part of memory that's reserved for the operating system kernel and cannot be written to by user applications. The O/S protects itself by refusing the operation and raising an error so that the offending application can deal with it. How does a pointer get initialized? That's up to the programmer who wrote the code. That's why it's safe to assume that a c0000005 error is a bug in the code that raised it, and ultimately human error. I apologize if you knew all that already, but it's important to understand how this error happens and why. The key concept is in your statement that "...This is not the only plugin that has generated a c0000005...". The salient point is that it was the plugin that attempted to write to protected memory, not the DAW. The error was raised by the plugin, not the DAW. Granted, the plugin may have been referencing an invalid pointer that the DAW supplied it with, that's not impossible. However, any pointers passed to the plugin (e.g. input and output buffers) would be the same pointers the host passes to all plugins. If they were invalid, the DAW would crash every time you attempted to use any VST plugin. From a software developer's perspective, it is always the module's responsibility to validate arguments, and to never assume that the caller guarantees they are valid. Usually, that means the plugin will refuse the invalid pointer and notify the host that the call has failed, in which case the host would be tasked with processing the error. When this is the case, it won't be the plugin that was identified as the offending module in the dump, but rather the DAW. But if the stack dump shows a plugin's DLL as the failing module, then that's where the problem originated.

Sorry, I don't come here often so didn't see your reply until now. The battle of who is at fault when a certain plugin doesn't function with a certain DAW will rage on in perpetuity. The DAW developer will blame the plugin developer and the plugin developer will blame the DAW developer. It's been that way since both have coexisted. When the plugin functions just fine in all other DAWs is it the fault of the plugin or the DAW where it doesn't function? I know DAW loyalty always plays a part (it can't be the DAW's fault because it's my favorite DAW and so on). So to reiterate the part of my post you failed to quote: "This is not the only plugin that has generated a c0000005 crash in Cakewalk, while those plugins work without issue in the other four (now 5) DAWs I use". So you can turn a blind eye to the issue in order to protect your DAW but that serves no one including yourself. Oh and the "literal definition" of periodically is: pe·ri·od·i·cal·ly from time to time; occasionally.

I've got a project that is fairly complex with many plugins and sidechains that will open completely, then after about 3 seconds I get the hour glass and it exits to Windows. There is no error and setting the sensitivity in the initialization file doesn't appear to generate anything. I have projects that are far more complex than this one that open fine. I've tried loading in safe mode and it will stay open if I excluded everything but if I exclude them one at a time (or common groups like soft synths or FX) it will crash. Only loading with no FX and synths keeps it from exiting. If I'm quick, I can start it playing but it bails out after a second or two. I looked at the Event Viewer and see this: 2281215597166793434 4 APPCRASH Not available 0 Cakewalk.exe 28.11.0.21 6387726b StackHash_b4ee 0.0.0.0 00000000 c0000005 PCH_29_FROM_unknown+0x0000000000000000 \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8FF.tmp.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA29.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA39.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA37.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA57.tmp.txt \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Cakewalk.exe_49f901855dfc38b7a24d15255f7e2bb35cc8b_3a505869_d681d648-3951-4881-a327-ed0e0152210a 0 7c145382-c31f-4148-8404-24c905b17497 268435456 fe55d34db251ca1dcfa8817fcd3512da 0 Faulting application name: Cakewalk.exe, version: 28.11.0.21, time stamp: 0x6387726b Faulting module name: ntdll.dll, version: 10.0.19041.2788, time stamp: 0x2f715b17 Exception code: 0xc0000005 Fault offset: 0x000000000002faad Faulting process id: 0xfb4 Faulting application start time: 0x01d97af031f5e7cc Faulting application path: C:\Program Files\Cakewalk\Cakewalk Core\Cakewalk.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: 50850872-87b8-4f01-99e3-3670e499ee6d Faulting package full name: Faulting package-relative application ID: The C0000005 tells me someone is trying to access a memory location they aren't supposed to (that someone being Cakewalk or ntdll but it could be on behalf of a plugin.) Any suggestions how to investigate this further? I ran the deep hardware tests and they all pass. Terry Edit: I got it to open by opening two other projects with it at the same time. Well there's a usable solution! LOL. Resaving it and trying the new file didn't help.

If you look through the forum, you will see that the general purpose c0000005 crash error has come up quite a bit. It might be hard to find though, because it usually shows up as a picture posted by a user as opposed to text which can be searched.** I have seen it myself as well as others mentioning it. When I get it on my PC, I take it as a sign that I need to problem-solve the issue. Yup! Part of problen-solving the issue. **CORRECTION: I was wrong. This search produces 2 full pages of hits.

Yes that's obvious since it says" Obsession.dll-Crash Detected!" right in the image. I already sent the files to the developer before posting here but that's not what I asked. I asked if anyone else periodically experiences this issue. This is not the only plugin that has generated a c0000005 crash in Cakewalk, while those plugins work without issue in the other four DAWs I use. I'm looking to build a list of plugins that have or can generate the error so I can test them as well.

Anyone else get these errors periodically? Windows 10 Latest CWBL.

I looked at the dump file. The crash isn't in any Cakewalk code and its impossible to decipher from the stack. There are a lot of Sitala threads there but it's not clear if it was responsible. Very possible that some corruption caused the crash. The problem with errant plugins is it can be very hard to track down from the DAW level if crashes are random because they can corrupt memory. Details from your dump are below. Something (not Cakewalk) is basically trying to read from a bad memory address somewhere. Based on your description the most likely explanation one of the plugins possibly ran out of memory and had poor error handling leading to this crash. The bottom line is there is nothing any DAW can do to protect from cases like this. If you have consistent problems with particular plugins your best option is to work with the plugin vendor to fix it. ExceptionAddress: 00007ffb092812a8 (ntdll!RtlDispatchException+0x0000000000000048) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 00000000000000bc Attempt to read from address 00000000000000bc PROCESS_NAME: Cakewalk.exe READ_ADDRESS: 00000000000000bc ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s. EXCEPTION_CODE_STR: c0000005 EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 00000000000000bc FAULTING_THREAD: ffffffff STACK_TEXT: 00007ffb`092812a8 00007ffb`092812a8 ntdll!RtlDispatchException+0x48 STACK_COMMAND: ** Pseudo Context ** Pseudo ** Value: 3 ** ; kb SYMBOL_NAME: ntdll!RtlDispatchException+48 MODULE_NAME: ntdll IMAGE_NAME: ntdll.dll FAILURE_BUCKET_ID: BAD_DUMP_MISSING_MEMORY_NULL_CLASS_PTR_READ_c0000005_ntdll.dll!RtlDispatchException OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 IMAGE_VERSION: 10.0.19041.2130

Dear Cakewalk community, My cakewalk has started crashing when I play my project files. The music will play for approx. 2 seconds before crashing and exiting the software with no error message. Just to give some background: I was having issue with exporting WAVs of my project which was also crashing the software (exporting mp3 files seemed fine though). Anyway I think the exporting issue is fixed. I suspected this was due to workload or memory on the computer, so I went through my files and deleted unused files especially from my downloads folder. This was to free up space. All the VSTs that I use are also in a Cakewalk plug-ins folder. I have opened up crashlogs and it seems that Sitala VST is the issue. Here are some examples from the crashlog: EXCEPTION_RECORD: (.exr -1) ExceptionAddress: 00007ffa840e3973 (Sitala!VSTPluginMain+0x00000000003d6d33) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 00000000000000f4 Attempt to read from address 00000000000000f4 STACK_COMMAND: ~0s; .ecxr ; kb SYMBOL_NAME: Sitala+3d6d33 MODULE_NAME: Sitala IMAGE_NAME: Sitala.dll FAILURE_BUCKET_ID: NULL_CLASS_PTR_READ_c0000005_Sitala.dll!Unknown I have re-installed Sitala several times and it makes no difference. I was wondering if anyone has any advice on what to do? Other plug-ins I use are Surge, Molotok, TAL dub delay, and CamelCrusher. Interestingly my smaller project files seem to play ok even though these also involve Sitala, so maybe it is a performance issue? I never had issues before today/before I started exporting large projects as WAVs. Many thanks in advance, PS It has also just crashed when trying to freeze a track. The track used Sitala.

c0000005 is an access violation. An Access Violation is a type of Exception caused when an application Reads, Writes or Executes an invalid Memory Address. The Exception Code is 0xC0000005 https://docs.microsoft.com/en-us/shows/inside/c0000005 Probably best to find a newer synth for the intended use... TL/DR: That is a code bug... that synth is no longer supported, so hope for a fix is non-existent...

Hi all, I need this synth for my song but it's crashing Cakewalk every time I start up, even when I start as admin. The error is crash code: c0000005

Of course. The error is the standard memory violation: c0000005. Seen one ... Changing the Exception Severity just makes Cakewalk blow it off but TT EZD3 still crashed with the violation. The fault is in EZdrummer 3.vst3. D u m p F i l e : C : \ U s e r s \ t e r r y \ A p p D a t a \ R o a m i n g \ C a k e w a l k \ C a k e w a l k C o r e \ M i n i D u m p s \ P l u g i n s \ U n t i t l e d _ 0 5 0 3 2 0 2 2 _ 2 0 2 3 5 7 . d m p E x c e p t i o n C o d e : c 0 0 0 0 0 0 5 d F a u l t i n g M o d u l e : c : \ p r o g r a m f i l e s \ c o m m o n f i l e s \ V S T 3 \ E Z d r u m m e r 3 . v s t 3 A p p V e r s i o n : 2 8 . 0 2 . 0 . 0 3 9 U s e r : t e r r y S e r i a l : ************************************** P r o j e c t F i l e : D : \ C a k e w a l k s o n g s T B K \ U n t i t l e d I s P l u g i n C r a s h : 1 T o t a l P h y s M e m 1 6 7 1 4 5 1 2 K B A v a i l P h y s M e m 1 0 3 1 2 2 2 4 K B Side note: It works on my friends W8.1 machine running 2021.12. Go figure. I did a rollback to that version and it still crashed.

Don't know if it's directly related to the current version, but I haven't had it do it earlier (as far as I recall). The arpeggiator crashes the program if I close a project which uses it, then open another one which also uses it. Garbage collection? Not releasing memory? Don't know. Here's the Windows Even Log for it: Log Name: Application Source: Application Error Date: 03/27/2022 09:57:20 Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: Win10 Description: Faulting application name: Cakewalk.exe, version: 28.2.0.39, time stamp: 0x6228b87d Faulting module name: Arpeggiator.dll, version: 17.5.4.0, time stamp: 0x56df59d7 Exception code: 0xc0000005 Fault offset: 0x00000000000cb688 Faulting process id: 0x4e10 Faulting application start time: 0x01d841a36fea2471 Faulting application path: E:\Program Files\BandlabCakewalk\Cakewalk Core\Cakewalk.exe Faulting module path: C:\Program Files\Cakewalk\Shared MIDI Plugins\Arpeggiator.dll Report Id: 5081fc85-b178-4aa3-b2fc-34dc82707ad3 Faulting package full name: Faulting package-relative application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Version>0</Version> <Level>2</Level> <Task>100</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2022-03-27T06:57:20.9569408Z" /> <EventRecordID>29923</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>Application</Channel> <Computer>Win10</Computer> <Security /> </System> <EventData> <Data>Cakewalk.exe</Data> <Data>28.2.0.39</Data> <Data>6228b87d</Data> <Data>Arpeggiator.dll</Data> <Data>17.5.4.0</Data> <Data>56df59d7</Data> <Data>c0000005</Data> <Data>00000000000cb688</Data> <Data>4e10</Data> <Data>01d841a36fea2471</Data> <Data>E:\Program Files\BandlabCakewalk\Cakewalk Core\Cakewalk.exe</Data> <Data>C:\Program Files\Cakewalk\Shared MIDI Plugins\Arpeggiator.dll</Data> <Data>5081fc85-b178-4aa3-b2fc-34dc82707ad3</Data> <Data> </Data> <Data> </Data> </EventData> </Event>

I'm having a similar problem, specifically (copy/paste special, although it doesn't matter whether it's a new or existing track) and frequent c0000005 errors in general just entering notes in PRV. They have always been frequent and are more frequent (like multiple within a couple of hours) with this latest release. They are usually the error shown in the image below and can occur in either Cakewalk.exe or the kernel. My specs briefly: Win 10 Pro x64 i7 7820X octal @3.90Ghz 64GB memory Babyface Pro (ASIO/2048K buffer)

I updated the Ample Metal Ray, and it managed to crash both Cakewalk and Studio One 5. Reproducible with v3.5.0, VST2 & 3. The issue seems to occur while re-opening the Ample plugin GUI, after closing it while the riffer was playing. OK, so I tried it with my last resort test DAW, Reaper. Crashed that too, which is quite an achievement! Here is some data provided by AppCrashView for one of the Cakewalk crashes: Name=Application Name Value=Cakewalk.exe Name=Application Version Value=27.12.0.102 Name=Fault Module Name Value=Ample Metal R.dll Name=Fault Module Version Value=3.5.0.0 Name=Exception Code Value=c0000005 Uninstalled v3.5, and fell back to v3.3. That seems to have resolved the crashes. Let me know if I'm not the only one seeing this please!

Good to know. After evaluating the Rapture Pro demo, I'm quite pleased. Also, I was able to create a two-octave pitch bend with a Pro instrument. I simply changed the bend range in the bottom of the Pro Elements window(s) and it worked. Better than dumping a bunch of RPN CC's all over the Controller pane. I do notice that Rapture crashed a few times via fatal error c0000005, and I'm already running as Administrator. I'll have to look for that to happen again. Besides that, I've been enjoying Cakewalk Sound Center all this time, but I sure wish I'd purchased Rapture Pro long ago.

I got more Information on the error now: It only crashes if I try to play using Cakewalk TTS-1 (Error: c0000005) (It also mentions the TTS-1.ddl as a Problem.) Any Ideas?

Upgraded to 2021.09 build 120 64 bit and it seems to crash out a lot! The latest one, I was just playing my project and after a verse it went quiet. Source Cakewalk Application Summary Stopped working Date ‎14/‎09/‎2021 21:27 Status Report sent Description Faulting Application Path: C:\Program Files\Cakewalk\Cakewalk Core\Cakewalk.exe Problem signature Problem Event Name: APPCRASH Application Name: Cakewalk.exe Application Version: 27.9.0.120 Application Timestamp: 613a4746 Fault Module Name: ntdll.dll Fault Module Version: 10.0.19041.1110 Fault Module Timestamp: e7a22463 Exception Code: c0000005 Exception Offset: 000000000010bc11 OS Version: 10.0.19043.2.0.0.768.101 Locale ID: 2057 Additional Information 1: 108a Additional Information 2: 108af0384854619f77ac18936b5d5865 Additional Information 3: 4ed5 Additional Information 4: 4ed56071069a682f056ddf056cb95ab1 Extra information about the problem Bucket ID: 31f603d93f5fe9ef5cd2e38008f05603 (2076972517216507395) Previous crashes involved a Rapture session track, setting midi output to MS GS wavetable (failed as per) but then disappeared. Just playing on a loop. The crash file itself appears to be empty and inaccessible. My project is only basic, One AD2 track, 11 audio tracks with 9 muted. Having decided to try an instrument track today, it would appear that it has crashed out each time as there has been no changes saved. Any ideas? Report.wer @Noel Borthwick I have now found the dmp files (20 - 23MB) in "appdata/local/crashdumps"! I don't do any cloud based storage - bar Bandlab strangely enough, so I will have to think on it and see how bad it gets. No crashes in previous months, 3 since update, but I did update Libreoffice as well.

I installed Rapture Session (via the Cakewalk Command Center). I drag the synth into a new Track, and when I click the synth icon to open it, I encounter a c0000005 crash. This occurs in Sonar and Cakewalk by BandLab. I have tried these steps: Uninstalling both DAW's and removing the Cakewalk registry keys. Then I reinstalled both DAW's with Rapture Session as the only synth. Moving the Rapture VST3 from Program Files/Common Files/VST3 (why would it put that there?) to the actual DAW VST3 plugins folder. Has anyone had this happen? Can anyone provide guidance to help resolve? Thanks in advance. EDIT, 9:51PM: I modified one of the DAW shortcuts to "Run as administrator"...but I only did this for one of the DAW's. Now, on loading the Rapture synth via the track icon, it loads up fine with no crash. I honestly don't know what to make of this -- forcing only one DAW's shortcut to "Run as Administrator" and it works now in both of them. Even considering I moved the VST file out of Common Files.

Recently I got Addictive Drums 2. At first it worked fine. I put drums on a project with it. I save the project, next day I open the same project again and Cakewalk crashes. I try opening the project through the file system, and it works fine. Next time I open it, same problem, I get another crash. I get the same crash, an unhandled exception C0000005 which I have read can be a lot of things but is mainly related to memory access. I tried analyzing the dump file, but I don't really find the info helpful, it refers to TT1 for some reason. I also tried running Cakewalk as an admin. I tried starting a new project and adding addictive drums as new instrument, crashes right away. I also tried relocating the 32 bit and 64 bit because it might have an effect, still nothing. I tried reinstalling addictive drums I get a warning about compatibility mode if I move/remove the vst of addictive drums, but I don't use that I uploaded the dumpfile output from an analyzer, I would upload the file itself but it's too big for the forum https://pastebin.com/kpJY4CQF Any help appreciated :).

At some it would be good to collect together the various actions we try to get V-Vocal to work once it decides to go south. I'd love to hear other's tricks. And yes, we have beat the Melodyne option horse to death. This is about working around V-Vocals short comings. For me, I try one or more of the following in this order. 1. Disable all effects. Strangely this works enough times to give it a try. 2. Bounce the clip. Try bouncing by itself, then try bouncing with adjacent clips, then give up and move to option 3. 3. Bounce to stereo then open V-Vocal. If it fails, convert to stereo and back to mono (if that is where you started.) Then try 4. 4. Close the program and restart. It rarely works but sometimes .... 5. Reduce the size of the clip to as short as possible and still be able to make the changes I want. It could be as small as 1 second. This is one of those solutions that makes me think V-Vocal is running into some other chunk of memory Cakewalk is using. Hence the C0000005 (you ain't supposed to be in here.) 6. Copy the track/clip to a new project but I almost always have to close the other project where the crash occurs or the new project will crash too. Make the changes and copy it back into the original project. I often copy an instrument track with the clip to help identify the pitch changes I want, but I add that with no effects. Either way, editing in a new project almost always works. I'd say 95%+. 7. If I get the empty V-Vocal window, I bounce the clip which works and/or convert to stereo and back to mono. but I usually have to close the project and restart. If Cronus or Vpenc don't decide to crash, the wave is usually there. If it crashes, I will be forced to option 6. 8. If the volume of the clip is low enough, you might find notes where you don't get the initial yellow pitch line. The waveform is there but no yellow level/pitch line. Exit V-Vocal and raise the gain of the clip 6db (or more) until you get the yellow line across the complete note. Edit the clip, render and then reduce the gain by that same amount. I see this at the end of long notes where there isn't enough signal for V-Vocal to follow it as the note decays. The line will end before the note actually does. Most crashes are in Cronus and Vpenc. Once in awhile, Cakewalk will just close. I never see a VPSoloDec crash. The reliable option 6 is a bit of a pain but once you start doing it you get pretty quick and it's faster than trying the other options first. Just accept your destiny. To gmp, your suggestions are exactly what I see but pretty much head for option 6. Moving the clip in memory seems to make it work again.

Hello, first of all (isn't it?). 😉 "Works fine here" can come with a "when does it happen?", "have you tried bla bla?" after, etc. I assumed it was something commonly known, so I didn't attached any screenshot. My bad; but not a crime, isn't it? "Do you have any solution" is a typical question anyone asks when trying to find an answer. So... This problem is tending to happen in large projects. The small ones (really small ones, not too many tracks) "work fine here". The exception code is c0000005, an "unhandled exception". I'm attaching a screenshot. Thank you all in advance. Regards. Chino

@Štefan Gorej I’m curious if you insert this plugin in a new project, change its settings, save as a new project and open it does it also crash? You can’t restore VST3 plugin state into a VST2 plugin unless the plugin supports it. Waves support going from VST2 to VST3 but most other vendors do not. I looked at your dump file. Its definitely a crash solely in the plugin caused by it accessing a null location. So the stricter error handling is doing its job in pointing this out and stopping execution. While bugs like this may have sometimes gone undetected in the past in some cases they could corrupt the memory state leading to all kinds of instability in the app. So its critical that issues like this are fixed in the plugins to avoid destabilizing the entire project. According to the dump I don't see Cakewalk loading the project in the stack so perhaps the crash occurred after the project loaded. Was it still loading the project when it crashed? Sometimes its hard to see from the dump since the data doesn't always accurately report the rest of the state. --- Unhandled exception at 0x00007FFC38DF5D64 (Presswerk(x64).vst3) in 2021-02-25_05012021_191305.dmp: 0xC0000005: Access violation reading location 0x0000000000000000. Presswerk_x64_+3d5d64 00007ffc`38df5d64 8b11 mov edx,dword ptr [rcx] EXCEPTION_RECORD: (.exr -1) ExceptionAddress: 00007ffc38df5d64 (Presswerk_x64_+0x00000000003d5d64) ExceptionCode: c0000005 (Access violation) Attempt to read from address 0000000000000000 DEFAULT_BUCKET_ID: NULL_POINTER_READ PROCESS_NAME: Cakewalk.exe ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s. FOLLOWUP_IP: Presswerk_x64_+3d5d64 00007ffc`38df5d64 8b11 mov edx,dword ptr [rcx]