Can you post the latest dump?
Since it’s a large file (5Go), here’s the file analyzed with WinDbg.
Cubase-Dump-Analyzed.xml (9.6 KB)
This latest dump shows baios as what is throwing the error.
Are you on an AMD processor? If so, this may be relevant
Edit: Actually, re-read that and it’s only for AMD if you’re running macOS.
But, the issue still appears to be that plugin.
Pete
Microsoft
I’m on Windows 11 and intel core. The baios.dll is present in these locations:
C:\Program Files\Steinberg\HALion Sonic\components
C:\Program Files\Steinberg\Groove Agent SE\components
C:\Program Files\Steinberg\Cubase 12\Components
you can tell if it’s the interface driver by switching to the dgeneric aiso driver and the quitting..
In the end, I’m thinking the problem is coming from Windows 11, because the same setup works perfectly fine on another machine running Windows 10 with the same RME fireface. The one causing me so many issues is a new PC with Windows 11 — I didn’t realize it was that unstable.
Between two PCs, there’s a lot more that’s different than just the OS. Windows 11 itself is not unstable.
We DO have some very recent hang-on-initialize and hang-on-close issues with MIDI. But in any dump, those would show up as including midisrv. Every one I’ve seen so far is due to a handful of devices like the Midisport/midiman USB MIDI interfaces.
Pete
Microsoft
I was saying that because with this new PC I’ve had a lot of crashes and issues in a short period of time. The most recent one was two days ago. I turned on the computer and it crashed during startup, it rebooted and crashed again. I used ChatGPT to help me find a solution to the problem — I had to roll back some Realtek audio and Intel drivers updates that had been installed by night, and I also disabled automatic updates just to prevent windows from reinstalling thoses drivers updates..After that experience, I thought that with a system that hasn’t fully matured yet, it would be very difficult to identify the cause of the problems I’m experiencing with Cubase.
FWIW, ChatGPT has been steering people wrong here for a while. Everyone turns to it, but it’s almost always wrong, and leads folks to massive OS changes.
And, again, the dump analysis you have above does not say anything about drivers or hardware. It points to a plugin problem, not a Windows problem.
baios!GetPluginFactory+0x9f1c
When cubase is hanging on close, go into Task Manager, right-click Cubase, and choose to create a memory dump. Share that actual dump here (not the text from analyze -v, please).
Pete
Microsoft
2 Likes
Thank you Psychlist1972, The file is 4,97 Go i can’t attach it here. How can i do?
Just upload to whatever sharing service you might normally use (dropbox, onedrive, etc)
Unless you have it turned off, or are using a local account, OneDrive is built into Windows and has a certain amount of free capacity. I don’t recall the starting amount.
Pete
Microsoft
Here’s the dump file.
The latest tests I recently carried out also indicate that when I work with 128 samples or less, the problem occurs. I didn’t experience any issues with a setting of 256 samples.
I looked at it earlier today.
Basically it’s the same failure in Fireface ASIO after a baios getpluginfactory event.
2 Likes
Thank you KT66 for taking the time.
I downloaded the file in 40 mn 
i don’t know witch internet provider you have 
Hello,
BAIOS is a Cubase engine component. It’s often indicated in a dump when Cubase is waiting on something that relates to the engine (plugins, routing, audio drivers, devices, etc.)
Seeing the dumps (the 5GB and the one in .xml format), Cubase is calling -likely closing- a plugin; then a breakpoint is reached, once in ucrtbase/kernel (free_base/freeheap) and once in fireface_asio_64 (with the kernel likely waiting for it to be released).
I have no means of actually resolve a 5GB dump right now, meaning I see encrypted symbols as well and this is, err, educated speculation.
In both cases, the kernel seems to be waiting for Cubase, which in turn waits for a component to do its thing and release it.
In both dumps the unloaded module list contains only Trilian.dll and WrapPersist64.dll.
Trilian is the VST2 version, the latter library is PACE/iLok. I’d make sure to run updated versions, and possibly Trilian VST3 instead of VST2.
However, it’s unusual to see this plugin in a dump. You can test if the it actually has anything to do with the hang by simply moving it out of the VST folder and retest.
IEEE1349a, on the other hand, has been having system-specific (hardware/chipset) sync issues since Haswell. If you have an IEEE1349b chipset for your FireWire interface all should be good, but I’d temporarily exclude the interface to test the hang issue in the same vein as with the plugin.
I don’t know if there are any differences concerning FireWire compatibility between Win 10 and 11. FW has been in general a bumpy road for a while, unfortunately.
3 Likes
I have business-class gigabit symmetrical fiber running right to the house. But that particular location is slow.
Trace shows there are quite a few hops between here and there. Maybe someone tripped on the cable going across the Atlantic 
No worries, though. Looks like others have it.
Pete
Microsoft
1 Like
Thank you very much Fabio_B for your analysis and for your help. I deleted the trillian Vst2 version, nothing has change so far..,
Thanx KT66, Rme states that the fireface 800 driver is windows 11 compatible, the firewire pcie card is on texas instruments chipset..with that said many times i got the warning message:
« TMFXCal|back: TotalMixFX.exe - Application error
The instruction at 0x00000000000000 uses the memory address 0x00000000000000 The state of memory cannot be written. »
Maybe Psychlist1972 will point at elements that explain the reason of this problem..At least am more convinced the problem is not related to cubase..
Thank you.
Matthias Carstens (of RME) is aware of this error and says it is transient… the user should just click OK to proceed, so this is likely not related to your specific problem.
Ultimately, you’re using a Fireface 800 which is getting pretty old, firewire itself is fading in the rearview mirror as @Fabio_B has indicated and you’re running it on very new hardware with an up to date operating system. It is possible you’re just running into an incompatibility somewhere.
Someone upthread suggested testing your machine with another interface. I realise that’s not easy for everyone to do, but it would give you an indication of where the problem really lies.
Sorry I can’t be of more help.