I have never had a problem with Hallion. It only started after the last update. There is a problem with this update. I hope the next version will fix these bugs.
I will try to follow your advice.
Thanks for the tip Erik8.
1 Like
Hi Jerris, offcourse i understand that you do not want problems with your software, and when you get crashes, you have a bad day. 
Now, when your share this here with us, then we all have a little bit a bad day, when we see Cubase crashing.
It is good to see that you had no problem before this crash, but offcourse, you want to use Cubase without any crash.
Now, every software can crash at this level, just like a video editor can crash because of the many editings you can do.
So, what i advice is for you, and any other Windows User, to check some thing in the system where Cubase is running, to be sure there are no other problems.
Offcourse i can not see that from here, and if you check that, and there is no error code or red dot related to this to the health of your OS.
Only to be sure, because if the Cubase crash is caused by another proces in your memory, then Steinberg can not find the solution in there own software.
So, log in with your account and get a Request ticket via Support to send this dump file, and if you want to know about something you see in your diagnose, just put it here, so we can see if there is no other software that can create this conflict in your memory.
Hi Jerris, since march this year i use Cubase 13 pro and start on this forum.
About crashes with Cubase 13 and HALion:
I was working on many projects, and sometimes when 1 exit after saving my project, Cubase Crashed, but after that crash, that sometimes occurs, not while i am programming, but when i EXIT after saving, i did not lost any data, Cubase start in the save mode after the crash and everything is working fine.
My system is 100% healthy, and this crash was VST crash.
Not many, but when i was working long on a project, this VST crash in HALion Sonic, was a fact, in HALion 7 i have not seen a CRASH yet.
Now i was thinking, about this:
In the crash i was talking about the name of the module was HALion Sonic.vst3.
The crash was in the APP Cubase 13
Now, what is the differents if you use a stand alone?
When you use HALion as a stand alone, you have to save your presets, or you lose your work.
In Cubase you do not have to save setting from instruments that you can change via your instrument.
Because if you save a project, and open your project, instrument change in the setting in HALion are in the Cubase project saved.
So if you see in your error message in Windows:
The name of the APP, that is Cubase.
And the Name of the Module, because in this case HALion Sonic is not working in the memory as a stand alone.
Offcourse i advice you when you are using cubase to save your work every minute. (try to get avoid the nervs you can get from crashes 
)
The way in this load order is that if Cubase13.exe is the FRAME in the memory, HALion Sonic.vst3 is working as a module that is loaded in the frame in memory from this executable cubase13.exe.
This order in your memory, has to do with how your processor and memory handle all data.
The drivers are loaded into the Kernel.
Because here was a crash when i EXIT a project in HALion Sonic.vst3 as module, a dll file is a module to for a computer.
The extension .sys files are the drivers that are loaded as the module in NT KERNEL.
That is how it works under the hood…
The code c0000005 (HEX) means that while exit the program did not return a 0 (that is for C script developers)
So that means at that moment when i exit an “read/write to the memory error” occured.
As if the module stopped communication with the drivers to the hardware (RAM = hardware)
and 1+1 is still 2 
I just made a Windows diagnose in my Cubase 13 pro system and if you see this, then you can exclude your system is the cause of a crash.
If any other software can give conflicts besides cubase while Cubase crash, you can exclude it if you know what program’s are installed with drivers.
2 Likes
Hi Jerris, i hope your system and DAW is doing fine.
I got some support from Steinberg, and it turns out that some steps show some corrupt system files via:
C:\Windows\System32\cmd.exe
open as administrator
typ:
SFC /SCANNOW
(c) Microsoft Corporation. Alle rechten voorbehouden.
C:\Windows\System32>SFC /SCANNOW
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.
C:\Windows\System32>SFC /SCANNOW
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.
C:\Windows\System32>
So this was my system repair today, 9-8-2024, even my diagnose was 100% healthy.
So maby you can do something to with this information Steinberg gave me today:
You should try to repair Visual C++ Runtimes:
Press the Windows Key + R, enter appwiz.cpl and then press Enter.
Locate Microsoft Visual C++ Redistributable (2015-2022) (x64) (x86) Packages in the list of installed applications.
Select this entry and then click Uninstall/Repair and it will show options to Repair, Uninstall or Cancel.
Click on Repair and allow the process to complete. You’ll be asked to restart your PC"
After that was Oké i did a scan with SFC /SCANNOW
They gave me this link to.
Good luck.
How to set up a DAW in Windows.
1 Like
Hi dimdvp, can you describe what settings you have done before you got this error message?
Every crash, you can send dump files via a ticket, and maby you got some instruction via the support to?
If everything is working oké, but only this crash occurse by exit, then i ask you if you have looked in your UEFI or BIOS.
Some settings there must be disabled, can you give information about that?
Thanks.
This happens randomly, then an error on Cubase, then Halion, just an update from Halion 6 to Halion 7 - Windows 10.
The same thing happens on a clean system with Windows 11 on a new disk.
I updated all the drivers, tried to increase MMCSS threads to Max, although on the Steinberg website it was required only up to Cubase 10. I also tried to disable SMT in the Bios - this reduced the number of cores from 32 to 16. But Reaper and Studio1 WORK without any SMT settings and disconnections…
Hi dimdvp, did you get a ticket and send your dumpfiles to the Steinberg support as a registered member?
Before you go on, i can explain some words.
HALion 6 to 7 is an upgrade from a VST instrument.
Not an update, try to see the differends, then you can better describe the problem on forums.
Just a vew letters, looks like the same, but an upgrade is a new version from the software, and updates are changes in the version that not change, just like by all other software, as Windows 10 to 11 UPGRADES often cause more errors.
So can you tell me more about both systems, and how your setting where configured?
Because, if you can do that in your system, and you have all your settings configured in the UEFI and your system only for REALTIME AUDIO.
If you have your system running when Cubase is installed, and all your setting are just Steinberg advice here…
the License.
So you wrote that you update (it is an version upgrade) from HALion 6 to 7, so how about the situation is now, that you have both an upgrade for HALion 6 and upgrade that to HALion 7.
So you have the license then to install HALion 7 without HALion 6, as far i follow your post, and you have many crashes that must be solved, so step for step.
If you do as above, understand that if you do not know where to look, start with that Windows Diagnose and in cmd.exe as administrator (the folder system32) you can scan your system with the command SFC /SCANNOW.
So i can help you to gather information in your system with differents methodes, and you can show what hardware you have on your motherboard.
Yes, I need help with the correct system setup, Bios.
On the main Windows 10 disk with a lot of plug-ins installed, Cubase 13.0.41 was updated from the 12th version and Halion7 was installed on top of or next to Halion6, or I deleted the 6th due to incomprehensible errors.
On the new SSD, clean system, Windows 11, clean installation. Only Cubase13, Halion7, Groove Agent, Padshop, Backbone, Overloud TH-U
My new system:
- Ryzen 9 7950X 16-Core Processor 4.50 GHz
/newest Chipset driver AMD Chipset Driver V6.06.11.2153 2024/07/04 - Asus ROG CROSSHAIR X670E HERO BIOS 2204
newest Bios 2024/08/05 - 32Gb*2 Kingston Fury Beast AMD XMP/Expo default 4800
- Asus GeForce 1070 /newest driver Studio driver 560.70 July 16, 2024
- RME AIO /newest driver 4.48
- Windows 11 Pro 23H2 OS Build 22631.3958
Windows Feature Experience Pack 1000.22700.1026.0
1Tb ssd Samsung 980 Pro Windows10 -System, many 3rd party plugins
1Tb ssd Samsung 980 Pro Windows11 -Newest Clean System - Only Cubase13, Halion7, Groove Agent, Padshop, Backbone, Overloud TH-U
2Tb ssd Samsung 980 Pro - Libriaries Steinberg, XLN, Nexus and others
4Tb ssd Kingston Fury Renegade - Libriaries, Samples, Toontrack, Kontakt
Hi dimdvp.
It seams that you build a wunderfull graphical game computer, but that is suddenly become your problem.
It is not that you have a bad system, no.
The problem is all this speed technology from the hardware can give errors in Cubase because that cause CRASH of a MODULE in Cubase.
Now if you use HALion stand alone, then HALion is not loaded in the memory as a MODULE, but as a program with a PID (Proces Identification) in Windows.
Imagen that when you use Cubase the instruments are load into RAM in the FRAME in the memory where Cubase is loaded and running.
WORK MEMORY you see in your Asus GeForce 1070
Now, if you want to build a realtime advanced audio work station with a program like Cubase, you are better off without this Video Card, but, that is not what you want.
So what are the options?
All setting in the VIDEO CARD setting must be all set, just like you see in the BIOS, for ONLY REALTIME AUDIO when Cubase runs.
If you go into your BIOS/UEFI, you can read this
the parts:
Tweaking Windows
Tweaking Cubase/Nuendo
Tweaking the computer
So that one for the computer let you read what settings you must disable in the Eufi/Bios.
For your videocard:
So if you can manage the settings from your videocard, CUBASE can not handle good in a GAMING environment and you must downgrade settings, if the videocard gives to much then Cubase can crash.
That is because the VID RAM is work memory to.
Hardware profiles:
If you need differend settings for your computer, to use CUBASE and you want to use the same computer as a gaming computer, then you can try to look if you can save your settings in a HARDWARE profile, you can load before you choose what you want to do with your computer.
So you see, there is a lot to be done, your computer is fast enough.
So, i hope you can do some look over your settings, and check if your errors are coming back or not.
1 Like
My previous system is Core i7-950, 24 GB DDR3 RAM, Asus Geforce 1070. Photoshop, Adobe Premier and Cubase worked stably. But it is impossible to make an arrangement…It has become impossible to work on a project on modern Nexus, Diva and other synthesizers. Yes, GTA 5 games worked, for example.
The video card is not modern, not 4070)
The video card was purchased in 2018.
Progress does not stand still (and Cubase does!!!).
Many users are asking to improve stability and performance, which is what we see…
Programmers and designers Steinberg create problems: they remove Loopmash, Beat calculator and other synthesizers that are in the projects …
The design of the program and fonts are not changing for the better (Cubase12 is the best design), people appear on the forum about this!
I updated the system, due to modern progress, to make everything work: sample libraries loaded quickly, everything was processed quickly, synthesizers worked without brakes, why am I updating?)))
5 times more powerful!
Reaper WORKS, Studio1 WORKS, FL Studio WORKS, Ableton WORKS
Cubase- SUCKS, sorry. But my favourite DAW
I`ll try to find in the BIOS and make settings in VIDEO CARD for ONLY REALTIME AUDIO when Cubase runs…thank you
1 Like
I see that you use a lot software, and the most are running stable.
Asume that combine can give some troubles.
So, you are rigth if you have to do with crashes, but that is the issue, a system like Cubase needs to run on a computer without limitations as energy saving settings with sleep when idle, or the hardrive is shut off after, let’s say 10 minutes, you can manage that in Windows self.
So, if i give you some advice, i hope that you understand that CUBASE is like a system itself.
The computer and all process needs to run at one tempo without any speed reductions for a better performance in Windows, all for this realtime Audio.
So that is written here, and in the world of computers, the architecture of processors is now GEN3.
So all this turbo boost settings are funest for Cubase, even without all this other programs, that still can run stable.
But, the drivers and the way how that works under the hood, is for many people offcourse advanced, and then it is a mess.
Please keep me informed about your situation. And if you had some succes, on one or both computers, we can handle that as two differend systems, Windows 10 and 11 are not so different, but still different.
1 Like
Yes, I tried the Demo versions Studio1, FL Studio, Ableton on Windows 10.
Now Im looking on Studio1 if I cant to make good my favourite Cubase(