This crash of CB 15 Pro latest update happened while doing several Swam Trumpet Improv takes The was NO Crash Dump file
Hi,
This doesn’t look like Cubase message.
Isn’t there a DMP file stored in the Documents/Steinberg/Crash dumps/ folder?
I checked after it happened and there was no DMP file
It isn’t, it’s generated by Windows. It implies Cubase crashed with an un-handled error and it reverts to Windows to post a failure message.
It might be worth checking the Windows event log to see what messages are generated when this happens. Also, before clicking on the Close Program button, open the task manager, right click on the Cubase task and select the option on the dropdown menu to generate a dump. Post the dump here or a link and we’ll have a look.
Always include your full specs when reporting a crash.
Full - specs - from CPU, graphics, etc.. it may help identify issues.
I would also list the soundcard, drivers, sampling rate etc…
It’s a failure within Cubase (invalid pointer) but there’s nothing in the call stack to say what was going on at the time. Is there a specific action you’re taking when this occurs? Does it always happen in the same circumstances?
ebt 2250 32 gig ram intel ultra cpu the highest 1818 focusrite internal graphics intel card. 20+ TB My computer should handle it all..
heavy new score editing is where it all happens.
That is FAR from a full computer setup ![]()
You need to add windows version, ideally CPU type..
And a Dell PC of this level is probably not going to have an internal graphics card, I doubt that. Check your full system info.
And do mention if you use a dual screen setup or not.
The ebt 2250 certainly comes with the internal motherboard graphics card by Intel I don’t know where you’re getting your Research from my present system is very souped up. I do use Windows 11 I have one 32 inch curved monitor by Dell.
I don’t know what genre you use but that new score editor is extremely important for my orchestrations and that’s where the issue lies, it has been going on since cubase 14 Pro
Hi again Alan, let me try help you out again.
The issue is not with your setup being “cheap”, it clearly isn’t, it’s a great setup.
If like me you spent months and months looking around the internet for clues to why Cubase would crash like it can do, you would KNOW that it can be from a bunch of reasons, and know there are LOTS of potential things to try.
One possible avenue could be the graphics chipset, which is why I asked to confirm what graphics your setup has, Intel UHD probably, with the second monitor on HDMI.
I’ve seen several people with issues with 2nd monitors.
Let me offer you one easy test : with Cubase OFF, remove your second monitor, then launch Cubase, test all you want to test without the second screen, see if that makes a difference. If it does, you know you can suspect your graphics chipset !
I hope my modest contribution may bring you some help and relief.
Slightly off topic but why not use Dorico for the scoring and then bring it into Cubase for better virtual instrumentation and mixing ![]()
I have already done your suggestion and do have several monitors. I still think it’s a software issue but I do appreciate your objective response
Alan Russell
My library is SWAM and I like to hear my library when using Dorico 6 I need to be inspired as a composer at both software ends but I know the purpose of the software Dorico What I would like to see is future versions of Cubase professional work seamlessly with Dorico’s programming having better control from the new score editor since software version 14 Pro
Thanks.
@Martin.Jirsak Martin, it may be worth forwarding this dump to the Cubase team. The failure doesn’t appear to be caused by any external code.
All of my DMP files goes to Martin
I always send my DMP files to the team
