Crash with dmp file

Cubase
,
1

hscr
hscr567×706 105 KB

There is a chance that this crash occurs because of this driver setting.
If when you disable this option there is still a crash when closing Cubase 13 which causes this crash in HALion, it could be a write error to the memory perhaps when closing after using a media player.
when I had the media player on, and I started HALion, the media player stopped and went gray.
Presumably, when starting up in HALion, the drivers were briefly closed and connected by loading the drivers into the kernel.
therefore I suspect this setting as the cause of the crash as 99% possible. that one percent is for when things turn out differently… :wink:

2

Hi,

Make sure, you have the latest Cubase, HALion and MediaBay installed, please.

1 Like
3

Thanks Martin, the Cubase, HALion and MediaBay are installed.
I can explain a bit, then i start using Cubase 13, sometimes a crash occurs in Cubase and Halion vst files.
Now, the crash it self has no effect on my work, because the vew time this crash occurs, i used audio files, and opent the media player while listing wav files before import, and at that moments, after exit the file, then i allready saved my work, this crash is a fact.

now i read a while ago that reference coul’d be the reason, but this crash not every time.
So what i did was remember what i did in Cubase before a crash comes, but after the save start, everything is working, so i think it can be a driver problem, because of the windows error code.

Now this Windows error code c0000005, has in Windows selfnothing to do with Cubase, but with a memory indication.
In older version, from Windows servers this was an error when memory (RAM) fail.
But the crash occurs in a vst file.

So, i write this, and i hope you, or other people here, this isue was spoken before by some in this forum, can help the developers, because this crash is not a big disaster for my work, but for people that want to use a crash free system, or want to go live, without crash, for de software updates in the future, sometimes this happends.

I do not concider it as something as fatal.
So, thanks for your comment, and i check updates every week.

4

Hi,

On the screenshot, I can see 13.0.21. This is not the latest Cubase version.

1 Like
5

In that picture i use a saved old message.
So what you see in that picture, the message about the crash, was made earlyer.
So that is why you see the older version number in this crash message.
But, i have version 13.0.41.256 installed at this moment.
Excuse for the misunderstanding.

6

c054
c0541626×875 207 KB

Cubase 13.0.41 64bit2024.7.23 18.07.45.773.dmp (889,9 KB)

7

c054b
c054b1088×592 199 KB

Maby good to know, that this was after installing cubase 13 a message.

8

Update:
c054c
I changed this setting in my windows driver settings.
about that results, i write it down here later.
Thanks all.

10

Hi,

Reported to Steinberg. Thank you.

1 Like
11

Thanks to you to Martin.
So for the rest everything is working fine, i noticed a vew things, but that is something that can be handled.

Today, an instrument was not giving any reactions via the buttons in the interface in HALion.
So what i did was load the instument again, and did an undo, and the buttons did work as before.
So, maby that is the connection to the VST files, that can be solved with a reload and an undo, if any of the users noticed the same sometimes.
If anything change here, i inform it in this post later.
Have a nice day. :+1:

12

Hi, today i had this exit crash again, when i working longer on a project, this sometimes happends.
Since it happends sometimes, now I can exclude certain actions as the cause.
Furthermore, I can save my file before I close the project.
If I close the project and there is no crash, Cubase remains loaded until I close Cubase.
Because of this HALion vst crash, Cubase crashes and closing Cubase is no longer necessary.
I don’t know if HALion crashes when I use HALion as a stand alone for so long, but I would have to test that, or maybe Steinberg can test that.
Otherwise it works fine.

13

Hi Martin, i think yesterday, via Steinberg Support with a ticket, the problem with the crash is solved here, because Oscar let me know what settings coul’d be causing the crash.

First i can tell that my hardware and how it is build was not the problem.
Steinberg Support asked me to send a ms32 info file with the input from my system, and i send them the dump files and the log (*.json)

After making a screenshot here from the crashes in Windows, they coul’d help me properly, and i had some corrupt system files, even after a system diagnose was 100% healthy.

Via cmd.exe SFC /SCANNOW a few system files were corrupt and repaired.
And they gave me a link to THIS WEBSITE and i changed settings in the UEFI to, important that under:

Tweaking the computer

  • Disable Hyper-Threading (Intel)/Simultaneous Multi-Threading (AMD) in the UEFI BIOS if your CPU supports it and if your BIOS allows you to modify this setting.
  • Disable advanced power-saving and dynamic performance options for your CPU if applicable. This usually needs to be done in the UEFI BIOS of your computer and includes ‘Enhanced Intel SpeedStep (EIST)’, ‘AMD Cool ‘n’ Quiet’, ‘Intel Turbo Boost’, and ‘AMD Turbo CORE’.
  • Disable C-States in the UEFI BIOS if this is accessible. C-States allow your CPU to sleep when idle, which may interfere with real-time applications such as audio. This option is often called ‘Disable CPU Idle State for Power Saving’.

So, i had only this crash when i used Cubase for a few ours and made many changes in the VST instruments.

Thanks for your support here, i think this had solved the problem.
If not, i always can get another ticket agian.
Have a nice day. :pray: