Consistent Crashes on a preset, only using 55% CPU/DSP, thoughts?

FINAL UPDATE: I rebuilt the preset and moved my Vocal chain to row 2 (instead of row 4) and it’s holding steady!! So Guitar is Row 1 → Row 3, and vocal chain is Row 2 only.

Tried emailing support but haven’t received a reply after 4 days, so I’m posting here for advice.

  • This preset worked for years without issues. The only recent change was adding Row 4 dedicated to vocal processing (XLR In 2 → Row 4 → Out 2). Rows 1–3 are guitar, and Row 4 is vocal.
  • Since adding Row 4, the unit crashes randomly after about 5–25 minutes (usually around 10 minutes). The crash timing is inconsistent and not tied to any specific action.
  • The preset typically runs around 70% CPU, but crashes still occur even when disabling other FX and reducing CPU to around 50%. I understand I’m pushing the DSP somewhat, but 50–70% CPU doesn’t seem excessive enough to cause instability, especially since crashes still occur at lower CPU levels.
  • I’ve narrowed the issue to something in Row 4, likely Pitch Correction, Mini Voicer, or their interaction. Removing other blocks does not consistently prevent the crash.
  • I’m using the OEM power supply, and I’ve attached a screenshot of the preset that consistently crashes.
  • What I sent to support: video, diagnostic log, link to this thread. They’re responding daily, but mostly asking me for stuff I’ve already provided. I’ll update this as necessary.

EDIT: See below for all troubleshooting steps I’ve taken. Key finding: Placing ANY plugin on Row 3 (even something simple like an EQ) eventually causes a crash).

Please let me know if any additional information would help.

Thank you,

Updates / Troubleshooting Steps I’ve Tried (summarized from my post below):

  1. Initial test: Tried adding a Ryobi fan for cooling → unit still crashed after ~5 minutes.
  2. Retest on rebuilt patch: Recreated an exact duplicate of the crashing preset and tested again with the fan → still crashed. This suggests the issue is not heat-related.
  3. Plugin isolation test #1: Removed Pitch Correction but kept Mini Voicer.
    • DSP dropped to ~45%. Patch remained stable for 40+ minutes.

    • Next step: swap them (add Pitch Correction, remove Mini Voicer) and retest.

  4. Plugin isolation test #2: With Pitch Correction active, the patch failed after ~5 minutes.
    • This suggests a possible issue with the Pitch Correction plugin.

    • Next tests planned:

      • Run Pitch Correction alone on a low-DSP patch.

      • If stable, add it to a different full patch with higher DSP load.

  5. Cross-patch test: Added Pitch Correction + Mini Voicer to the default “Brit 2203” preset (DSP ~62%).
    • Patch remained stable for 30 minutes.

    • This suggests PC and MV themselves are stable, and the problem may be a conflict with another plugin in the original preset.

    • Next step: reintroduce original plugins one-by-one and retest.

  6. New discovery: I’ve learned that it’s not Pitch Correction or Mini Voicer, instead it’s the use of Row 3 IN ANY WAY crashes. Placing ANY plugin on Row 3 (even something simple like an EQ) eventually causes a crash.

I guess my next step is to utilize splitters/mixers to rebuild my patch only using rows 1, 2, and 4. This is crazy.

are you fully updated, CorOS-wise? (4.0.1)

I know it’d be a lot of work, but if you could rebuild that preset from scratch it might determine whether that particular preset is corrupt or it’s an unavoidable incompatibility bug that would need to be addressed officially

Hey brotha, thanks for the reply.

I did update this morning, unfortunately it still crashes. I was on 4.0.0 (crashes), then updated to 4.0.1 (still crashes).

I already rebuilt it from scratch (long process!) and it still crashes. It must be something to do with either Pitch Correction, Mini Voicer, or their interaction.

I wonder if Pitch Correction/Mini Voicer occasionally spikes CPU and crashes it. It’s frustrating, because I finally have a “perfect” patch and it’s unstable :frowning:

EDIT: This is what I mean: Last crash took 9minutes 32 seconds. Rebooted, clicked on the patch and in FOUR seconds it crashed. It’s totally random.

Try copying network@neuraldsp.com when contacting support and be sure to check your spam folders. If support doesn’t reach out within 48 hrs, please DM your contact details and I will forward directly to support.

1 Like

Yeah, support is going to need to look at your diagnostic report for sure. Probably will even request a video. They usually respond very quickly so definitely take the Mod up on his order to escalate if you don’t hear from them soon.

I received a response via email about an hour ago. Recorded a video (uploaded to YouTube) and answered all their questions. I’ll keep everyone posted what the resolution is.

One thing I’m trying as we speak is putting a Ryobi fan on the exhaust grill to push some air inside it to keep it cool as possible. I suspect the unit’s thermal paste is inadequate (speculation), and not cooling as efficiently as possible, so when I push it over 50% DSP it’s overheating and failing to prevent damage. Total guess, but if this runs for 45 minutes then I’m on to something.

EDIT: Ryobi fan didn’t help, failed after about 5 minutes.

EDIT: Ryobi fan didn’t help on “remade” patch either (the patch where I recreated an exact duplicate of the crashing patch)

EDIT: Removed the “Pitch Correction” plugin (keeping the “Mini Voicer”), patch DSP to 45%, has been stable for 40+ minutes. I’m going to flip flop now, and add PC, and remove MV" and re-test.

EDIT: Patch failed after about 5 minutes. It sure seems to indicate that there’s some type of issue with the Pitch Correction plugin. This makes me sad :frowning: I will attempt to 1) put Pitch Correction on it’s own patch stand alone (low DSP), if that succeeds then I’ll add Pitch Correction to a different complete patch to push the DSP and see how it goes.

EDIT: I put Pitch Correction and Mini Voicer on the default “Brit 2203” patch (which pushed DSP to 62%), it’s been stable for 30 minutes. This implies that PC & MV are stable, and instead there’s a conflict with one of my other plugins on my original patch. I’ll now re-introduce my previous plugins one-by-one and retest. This is painstaking lol.

EDIT: I’M ON TO SOMETHING: It appears that putting ANY plugin in “Row 3” (even a basic EQ), it will eventually crash. I’m at a loss for how to fix it.

1 Like

Interesting; good experiment! I’ve never had anything fail from heat issues, I suspected that probably would be the case.

I have had corrupt presets though, and was advised to delete them which did solve the problems. I never attempted to rebuild them though- it’ll be good to hear what they think is occurring here. Because you were able to duplicate it I suspect it’ll be some sort of incompatibility between devices in that particular config. I assume you’ve tried moving things around too, just in case? Maybe swap cores?

thanks for keeping us posted!

Have you tried adding other devices to push up the CPU to see if it is the PV or CPU?

I think my setup is pretty simple for stereo.guutar but it is at 53 or 56%.

I narrowed it down to putting ANY plugin in “Row 3” (even a basic EQ), it will eventually crash. I’m at a loss for how to fix it.

I narrowed it down to putting ANY plugin in “Row 3” (even a basic EQ), it will eventually crash. I’m at a loss for how to fix it. Hoping support can chime in.

1 Like

Just curious, are you using the OEM power supply or ensuring you are providing 12v @ 2A minimally? I only ask as I don’t think I have ever seen any unit suffer from heat but I have seen odd behaviors due to inadequate power supplies being used. Thanks for providing the updates and tests as well!

1 Like

Good question, I should have mentioned it because I know that can be a critical variable.

Indeed, I am using the OEM PSU.

1 Like

Other than working with support, have you tried to backup and perform a factory reset, test and then restore etc?

I updated my original post below, holding steady for now.

1 Like