Very excited to see the new Update , but had a message from support saying build doesn’t include a fix for my ongoing bug which actually crashes Cubase without warning. Or sometimes after you quit Cubase crashes.
It’s a major bug talking your DAW out and Steinburg are fully aware of it. I had been told its fixed in the next build!
I would’ve thought this would be a priority given that I’ve supplied multiple bug reports it’s clearly a major problem.
I have a very reproducible crash in Hal 7 with Cubase 13, which drives me nuts. I’m running out of trial time, and seriously considering UVI Falcon (both have pros and cons, but Hal wins). Fortunately, it reproduces in Halion Standalone, Cubase isn’t even in the picture, in 4 clicks after starting the program. Unfortunately, it doesn’t reproduce on my notebook… 
How did you go about reporting the issue? I spent ungodly amount of time narrowing down the repro: HighDpi on/off, different NVIDIA screen resolutions and W11 display scaling. What did you have to do to be heard by the Steinberg support? Do they actually fix anything? It would be a bummer. I came to like it very much for sound design.
It’s difficult, but I have sent in so many crash logs , Steinberg have found the problem, I was told is was going to being included on the next build, which it hasn’t so I’m hoping for a midterm weak FingersX
For me HALion 7 Which only use for my own sample creation Not third party libraries, is simply the most powerful and easy to use software sampler I’ve ever come across nothing comes close
Hi cnyll,
if it crashes reproducible in Cubase 13 then there should be log files. Please have a look in “Documents/Steinberg/Crash logs”
and upload the files here.
Thanks Gerrit
We have found and fixed the problems from the crash-logs that contained valuable information. And they’re included in this version.
Unfortunately there are cases, were one fixed problem will not cure the complete mess and take you only one step further before it crashes again. This seems to be the case here.
So if you have newer crash-logs, please provide them.
thanks and best regards
Gerrit
Ok great , I’ll keep posting my crash log ,
Thx
Andy
this happen with the new build 7.1 just checking you have seen this bug report - Request #622875
Nuendo 13-2024-06-19-123257.ips (445.5 KB)
Hi Andy,
the Nuendo Crash-log above is an old one. It’s from June and refers to HALion 7.0. Do you have any which are more up to date?
best regards
Gerrit
I do have a more recent crash log but I don’t think it’s related to HALion
I will upload the next one here , if and when Thx
Archive.zip (97.4 KB)
Hi Andy,
you are right. This one is not HALion releated and you send it to Martin Jirsak already.
best regards
Gerrit
To stop this his happening I am now zipping the logs and naming them after his right away
Hi Gerrit, I’m sorry it took me a while to systematically verify different combinations of screen resolution and windows image scaling. The crash reproduces 100% in standalone Halion 7.1, but unfortunately on my desktop machine only. It has a 8K monitor with the resolution of 7680×4320, connected to a discrete NVIDIA RTX 3070 Ti (the latest studio driver). On the notebook, I have a 4K panel with the native resolution 3840×2400 and a dual on-chip Intel Xe + Discrete notebook RTX 3050 device. On the notebook, I’m unable to crash Halion 7.1 at will. On the desktop with the 8K monitor, there is a clear pattern.
When I set the display resolution to the recommended maximum value 7680×4320 and the scaling factor in Windows to any of the values 100%, 125%, 150%, 175%, 200%, Halion works as expected when I either click on the “Add FX” toolbar button or the “insert effect” dropdown in the Mixer. Any scaling factor above, 225% to 350% (i.e., huge windows and fonts), immediately crashes Halion with the same messages as it does inside Cubase. The scaling percentages are all standard, from the Windows Display control window.
However, when I decrease the monitor resolution to one half, down to 3840×2160, there is no crash at any display scaling.
I’m attaching a layout file “crashset.halpreset” from %Documents%\Steinberg\HALion 7\Sub Presets\Editor\Screensets which I made the default temporarily so that it was convenient to work on the repro; I just removed all extra windows. It’s only for convenience and is not essential. I’m dragging the preset from Windows Explorer onto the preset name window, go down the tree to open the only layer’s bus, click the “FX” button, and Halion crashes under the above conditions. The preset can also be anything, I’m attaching exactly the one that I used for the repro. Pictures show how the expected result looks, and show what causes the crash. I can add FX to the bus with the bus’ context menu, but still am feeling like I’m negotiating a minefield. 200% is too small for this monitor; I prefer 225% when the monitor is busy, or 250% otherwise.
I’ll be happy to provide any additional information that you think would be useful!
pictures.zip (308.0 KB)
CrashDumpsLabelled.zip (1.0 MB)
Afteruntouchable.vstpreset (9.6 KB)
crashset.zip (3.4 KB)
(I’m zipping the pictures because they are posted too huge otherwise, and the single crashset.halpreset file because .halpreset files are not allowed on the Halion forum. 
)
Thank you for your help, and I hope the problem could be resolved soon!
Hi cnyll,
Its now in our Defect-Tracking-System and listed as Bug-ID “HALLY-10852”.
I hope we can provide a fix for it soon.
Thanks for your report and please accept my apologies for any inconvenience caused.
Gerrit Junge
HI Gerrit , I don’t think these are HALion 7.1 crashes but could I double check
Archive 2.zip (59.2 KB)
You’re right, both crashlogs refer to Nuendo itself. I’ve forwarded the crashlogs to the sequencer-team
best regards
Gerrit
Thank you 
I am disappointed with version 7.1.0. after the update, Halion often crushed and suggested writing the project under a different name. This is very inconvenient. I hope to receive a new version with corrections.
Hi Jerris, If you are in Windows, send Steinberg via a request about your system and send the dmp file of the crash, time and date is important.
Check in your OS to for that crash.
C:\Users\Accountname\Documents\Steinberg\CrashDumps
Extension .dmp
And a LOG FILE:
C:\Users\Accountname\AppData\Local\Steinberg\usagelogger
Extension .json
Yeah, that is the info.
In Windows, to check some more, you can do several things to check if there are more crashes.
I can give you some advice:
Make a new folder on your desktop.
Give this folder the name:
.{ED7BA470-8E54-465E-825C-99712043E01C}
Then you create a configuration map with all tasks.
You can make a system diagnose to:
As administrator:
C:\Windows\System32\perfmon.exe
C:\Windows\SysWOW64\perfmon.exe (64bit)
