Cubase 13 crashes when using izotope Nectar 4

Hey everyone,

cubase consistently crashes when using Nectar 4’s Assistant feature. Nectar 3 works.

Last time, I even got a BSOD saying “whea uncorrectable error”

These are my last cubase crash dumps. Any ideas?

Cubase 13.0.21 64bit2024.3.7 21.10.56.954.dmp (3,3 MB)

Cubase 13.0.21 64bit2024.3.7 21.10.56.965.dmp (1,5 MB)

Cubase 13.0.21 64bit2024.3.7 20.56.38.302.dmp (2,8 MB)

2 Likes

Hi @SiriusVI

Sorry to hear about the crashes you’re encountering when using Cubase.

These crashlogs don’t look good but my intuition is that there’s something wrong here that is besides Cubase. First BSOD is related to hardware, usually you can see it in the same screen as it often points to a component name and therefore the real culprit. For now, make sure all your hardware has up-to-date firmware and drivers.

Second, if Cubase is crashing when using Nectar 4 then we can highly presume that this is due to Nectar. I would suggest you send these DMP to iZotope, maybe they can make more sense of them that we can here.

Cheers,
Armand

1 Like

Hey, thx for your answer!

Can you point me into the right direction for my hardware troubleshooting?

Can you give me any specifics of what these crash logs say?

All my drivers and firmware are up to date.

I have an overclock running, and I could try resetting Bios to default. Could that be an issue?

I have since gotten nectar to work 2 times, but it still crashes cubase most of the time.

I already contacted Izotope and I am waiting for their reply.

No problems with Nectar 4 here … Windows 11 CB13

WHEA Unrecoverable error is indeed a hardware error (WHEA = Windows Hardware Error Architecture), but is also a pretty generic stop code, the dumps don’t provide enough info to see what the problem is: they look all different. The one in Cubase is a heap corruption, the others I can make a wild guess about memory corruption or dangling pointers.
The dump saved by Windows might provide some insight on the actual hardware involved, they are saved in C:\Windows\Minidump - you can check it out with WinDbg Preview (free on the Microsoft Store) or you can upload it to a service like Dropbox, WeTransfer, etc. and PM me the link, I’ll have a look.

OCing can be a problem, but not necessarily is.

1 Like