Cubase 15.0.10 - DAW Freeze ! Please Help me

Good Morning,
This problem is making me crazy.
-When I play a cubase project for more than 2 hours the system freezes completely and i need to force power off pressing the power button;
-Sometimes ( Randomly) , The system freezes when I’m doing some operation ( like create an instrument track and load an instrument plugin:

NO CRASH DUMP ARE CREATED ! NO ERRORS IN MY EVENT VIEWER ,ONLY STOCK PLUGINS ARE USED FOR THE TEST

System Setup :
Windows Version:25H2 (26200.7623)
Cubase Version : 15.0.10;
Demo Project : Austin Hull - Cubase 15 ( form bar 3 to 71 in loop mode);
Yamaha Steiberg USB Driver : 2.19;
Hardware : Steinberg UR28M;
Processor:Intel Core i9-13900HK;
RAM:32 GB;
SSD 1 ( OS + Cubase ):Lexar SSD NQ7A1 1TB
SSD 2: Sound Library and Cubase Project Files : Transcend TS1TMTS425S
Graphic Card:Intel Iris Xe Graphics;
GPU Driver Version :32.0.101.7084;
Monitor : LG FHD
Audio Buffer : 2048 Samples;
ASIO GUARD : OFF;

The problem occurs with the system described above and with :

  • Other Audio Buffer Sizes;
  • Other Yamaha Steinberg Driver Version;
  • With Asio Guard OFF and the Asio Guard ON
  • With wi fi enabled and wi fi disbaled;
  • USB Cable from motherboard to sound card is new !!!;
  • Power Energy is optimized with usb suspended mode turned off;

If I open the project, Go in Mixconsole3 , open the GUI of this 4 plugins ( see attahced image) , The system wil freeze in a period of time that is random : Always after 2h but it can happens after 15 minutes too.

THE ONLY WAY TO AVOID FREEZING IS TO DISABLE THE GPU FROM THE DEVICE MANAGER BUT AS YOU KNOW , THEN I CAN’T USE THE GUI OF THE PLUGINS !!

Please Help Me !!!

Thanks

The way you describe it, it sounds more like an issue with the GPU or its driver.

Have you maybe tried another version of the graphics card driver? Or maybe could try a separate graphics card.

I once had problems with third-party plugins that would reliably crash with openGl errors on my onboard AMD graphics, regardless of driver version, which stopped immediately when I bought the cheapest graphics adapter I could find.

Hi! thanks for your reply.
I have tried another version of the graphic card driver and it happens the same.
I can assure that I have stressed the GPU using the utility “FurMark” for 24 hours without any freezing

The PC is a Mini PC made by GEEKOM , model Mini IT13 and I can’t add an external graphic card. It could be beautiful to test with another USB GRAPHIC CARD but I think that they don’t exist.

I have done another test :

Opening a project in repeat mode
Open MixConsole 3 and dont open plugin GUI : The system freezes the same.

For me the problem is related to Cubase and Intel GPU.

Attached you can find a photo of the pc in Freeze state

Updates : The freeze occurs when running Cubase in Safe Mode ( 3rd parties plugin deactivated)

I agree with @fese that it seems to be a GPU or CPU issue rather than Cubase.

You say it is a mini PC? I tried one of those a few years back with Cubase after having success using one for day to day computing, but Cubase didn’t like it at all.

I’m not sure if it could be the lack of ventilation on these little boxes, and Cubase is pretty CPU intensive, even when idling, so could be an overheating issue?

Sounds like you have done the right thing running in safe mode with no external plugins, so unfortunately I think you have to look at the computer being the issue.

Do you have any crash dumps (freeze dumps) that you can upload here?

My Geekom is running without any issues, so far. It’s an AMD based system.

1 Like

Hi @JuergenP ! as I wrote above, It’s not a crash : It’s a freeze . No crash dumps are generated

Hi @manassas77 , I think is not a ventilation prolbem . The previous laptop was smaller than this mini pc and I ran cubase for 11 years….

Hi @st10ss , above you can find my setup , but i post it here again :

System Setup :
Windows Version:25H2 (26200.7623)
Cubase Version : 15.0.10;
Demo Project : Austin Hull - Cubase 15 ( form bar 3 to 71 in loop mode);
Yamaha Steiberg USB Driver : 2.19;
Hardware : Steinberg UR28M;
Processor:Intel Core i9-13900HK;
RAM:32 GB;
SSD 1 ( OS + Cubase ):Lexar SSD NQ7A1 1TB
SSD 2: Sound Library and Cubase Project Files : Transcend TS1TMTS425S
Graphic Card:Intel Iris Xe Graphics;
GPU Driver Version :32.0.101.7084;
Monitor : LG FHD
Audio Buffer : 2048 Samples;
ASIO GUARD : OFF;

In the same time. I’m dealing with Intel Support Community…

Could you try with 1024 Audio buffer 48kHz sample rate and ASIO GUARD normal just for a check?

You can generate freeze dumps when it happens. Open the task manager click on the Cubase process and then right click to get the context menu.

This screenshot is from Windows 10, but there it is the same in Windows 11

2 Likes

Hi @JuergenP ,

I can’t generate anything because when the system freezes , I can’t use mouse and keyboard

Hi @Puli , the test is going… I started the test at 13.27. Here yu can look at the temperature now

Have a look at this thread in the Microsoft community. It describes how to get a dump on a frozen system.

It requires changes to the registry, so be very careful, but you should be able to get a dump.

Here is another document that has a lot more descriptions on what to check. One point is to look at the settings for the pagefile and increase it in case it is too small.

https://windowsreport.com/windows-11-keeps-freezing/

@Puli : with the setting you suggested to me, The systems freezes always after 2h and 30 minutes

Hi Alessio, does restarting the graphics driver temporarily help clear the freeze? You can do this pressing CTRL + Win + Shift + B (your screen may flicker and beep once)

2 Likes

Hi @lethian : No, it doesnt work… The only way to take the control is to press the power button and restart the mini pc

Sorry to interfere…

Hey @JuergenP , it looks like the easiest way to generate a dump file, right ?

When I tried recently with ProcDump64 I could not manage to make it as the window shut down as soon as it opened…

I would alway try the minidump from the task manager first. It is usually working very well.

In case you want to get more infos you can run procdump, you should follow the instructions from @Martin.Jirsak to get a full dump.