Yes and if you got a deadline it makes you nervous. Some will say you can go back to 11. Sure, I can even go back to 7 but that’s not ideal.
Same here, it’s not that I am blaiming the 12 update or something, it’s more of a discussion of how things will get better for the end user.
12.0.30 any time soon? 
The first was concluded that is a non supported OS-cubase version missmatch.
Some other was related to Slate. Slate does not pass the VST-SDK test tool.
You only need to point out one specific to show your point, not list up a lot of crashes I dont intend do check all of them.
I’ll write it again: everything has the latest version installed!!!
Hi,
I tried what Procdump generates, the result from ten starts:
6 x C:\Program Files\Steinberg\Cubase 12\Components\mediaservice.dll
1 x C:\Program Files\Steinberg\Cubase 12\VST3\VST Connect.vst3
2 x win32u.dll
1 x mswsock.dll
The MediaService always crashes in the same place, which is easy to fix (this is not a random error).
I am very curious when Steinberg will fix it.
Just choose any of those, if you say Slate plugins don’t count. How about you begin with Cubase crashing on exit?
Hi There,
What I found is that the update 12.020 changed something. Up until then I had no trouble. I hope that Steinburg will have fixed this issue with the next update. Of course, I’m not worried for myself, now.
At least one confirmed exit crash is confirmed to internal within cubase and occurs without any plugins at all.
Actually there are users which don’t have the problem whithout plugins, and others have it more frequently the more plugins are loaded into a project. Others have it only when certain plugins are loaded into the project and others don’t have it at all. And now?
I gave you a list of multiple threads, which all are related to issues with plugins which are NOT related to their GUI, not just this here. You said, just give me one. Well there are lots, everyday. Now if you are too lazy to look through them, thats not my problem. But then stop acting like the issues were not real.
I don’t have the time to continue this useless conversation with you, like on the sandboxing thread, where you clearly ignored what others were saying and tried to derail a FR, just because you don’t think its a thing. Lets stop here with this nonsense. If you think crashes of plugins are 99,9% related to their GUI, than thats good for you. Keep on closing your eyes and thinking that 
It is unavoidable crash/hang in 12.0.20. Cubase 12.0.20 performance issues - #119 by Tony_ST
But it is for sure not the last. So you dont have a single crash to support your ideas?
Yes the list of threads I repeatedly showed you already.
How about you prove, that 99,9% of crashes are caused by the GUI, like you said?
Curious to see that one. 
The problem is that many of us won’t continue believing in the same. If C11 is good enough, why we need C12, C13 and all future versions? For me the C11 is the sky. New features are not necessary. For last two-three years the vector of Steinberg is to gain popularity of mainstream genres and this is about two-three genres, not the serious values for which we had good 9.5 and 10.5 versions.
IMHO, of course 
Were you able to take a look at the crash files that I posted 21 days ago on May 14th? Seems that you respond to each person who posts the files, but I have not heard anything. I am now at the point where Cubase just continues to crash and it has become completely unusable. Is there ANY fixes coming for the constant freezing and crashes that occur on v12?
I’m new to this and seen many threads about this subject. I upgraded to 12.0.20. I then had the problems of crashing, so I sent the computer off for an upgrade to 32 Gb RAM and an SSD drive. It then worked excellently. However, I once accidentally opened Cubase 11 instead of 12 and since then Cubase 12 freezes on exit (project closes OK) and sometimes when starting. I have tried all the suggestions in the various forums. and uninstalled all previous Cubase versions and reinstalled Cubase 12. I have removed all the old versions preference files too. Here are two of the recent dump files. (I have excluded those ending’-freezedump’ as these are 0kb.
Cubase 12.0.20.263 64bit 2022.6.7 14.05.47.781.dmp (613.4 KB)
Cubase 12.0.20.263 64bit 2022.6.6 18.37.03.062.dmp (775.8 KB)
Both of those show the crash is related to Intel Graphics
Microsoft (R) Windows Debugger Version 10.0.25111.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\me\Downloads\Cubase 12.0.20.263 64bit 2022.6.6 18.37.03.062 (1).dmp]
User Mini Dump File: Only registers, stack and portions of memory are available
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Version 22000 MP (8 procs) Free x64
Product: WinNt, suite: SingleUserTS Personal
Edition build lab: 22000.1.amd64fre.co_release.210604-1628
Machine Name:
Debug session time: Mon Jun 6 12:37:03.000 2022 (UTC - 5:00)
System Uptime: not available
Process Uptime: 0 days 0:24:19.000
................................................
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(c04.2818): Access violation - code c0000005 (first/second chance not available)
For analysis of this file, run !analyze -v
[...]
CONTEXT: (.ecxr)
rax=000000002467fbc8 rbx=00000000003ea3a0 rcx=000000002467fbc8
rdx=000000001185fbc8 rsi=00000000ffffffce rdi=00007ffbda7191f0
rip=00007ffc0775d939 rsp=000000002467fb70 rbp=0000000000000000
r8=000000002467fbca r9=00000000003ea418 r10=ce709ee7125b9070
r11=0000000000000000 r12=000000002467fbc8 r13=ffffffffffffffff
r14=0000000000000000 r15=00007ffbda7191e8
iopl=0 nv up ei pl zr na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010246
ntdll!RtlpWaitOnCriticalSection+0x219:
00007ffc`0775d939 48894218 mov qword ptr [rdx+18h],rax ds:00000000`1185fbe0=????????????????
Resetting default scope
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ffc0775d939 (ntdll!RtlpWaitOnCriticalSection+0x0000000000000219)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 000000001185fbe0
Attempt to write to address 000000001185fbe0
PROCESS_NAME: Cubase12.exe
WRITE_ADDRESS: 000000001185fbe0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000001
EXCEPTION_PARAMETER2: 000000001185fbe0
STACK_TEXT:
00000000`2467fb70 00007ffc`0777aa6c : 00007ffc`078711f8 00000000`00000100 00000000`2467fd00 00007ffb`da7191e8 : ntdll!RtlpWaitOnCriticalSection+0x219
00000000`2467fc70 00007ffc`0777a8d2 : 00000000`00000000 00007ffc`063d7ad7 00000000`2467fd90 00000000`0a1a4e10 : ntdll!RtlpEnterCriticalSectionContended+0x18c
00000000`2467fcd0 00007ffb`d981dba4 : 00000000`0a1a56c0 00007ffc`077679e1 00000000`0a1a56b0 00000000`005f0000 : ntdll!RtlEnterCriticalSection+0x42
00000000`2467fd00 00000000`0a1a56c0 : 00007ffc`077679e1 00000000`0a1a56b0 00000000`005f0000 00000000`00611b78 : igd10iumd64+0x29dba4
00000000`2467fd08 00007ffc`077679e1 : 00000000`0a1a56b0 00000000`005f0000 00000000`00611b78 00007ffb`d981ddba : 0xa1a56c0
00000000`2467fd10 00000000`2467fd90 : 00000004`00000004 00000000`22edc520 00000000`2467fd58 00000000`2467fd58 : ntdll!RtlFreeHeap+0x51
00000000`2467fd50 00000004`00000004 : 00000000`22edc520 00000000`2467fd58 00000000`2467fd58 00000000`00000030 : 0x2467fd90
00000000`2467fd58 00000000`22edc520 : 00000000`2467fd58 00000000`2467fd58 00000000`00000030 00007ffb`d981dcd2 : 0x00000004`00000004
00000000`2467fd60 00000000`2467fd58 : 00000000`2467fd58 00000000`00000030 00007ffb`d981dcd2 00000000`258c2480 : 0x22edc520
00000000`2467fd68 00000000`2467fd58 : 00000000`00000030 00007ffb`d981dcd2 00000000`258c2480 00007ffc`00000000 : 0x2467fd58
00000000`2467fd70 00000000`00000030 : 00007ffb`d981dcd2 00000000`258c2480 00007ffc`00000000 00000000`00000005 : 0x2467fd58
00000000`2467fd78 00007ffb`d981dcd2 : 00000000`258c2480 00007ffc`00000000 00000000`00000005 00000000`00000005 : 0x30
00000000`2467fd80 00000000`258c2480 : 00007ffc`00000000 00000000`00000005 00000000`00000005 00000000`258c2480 : igd10iumd64+0x29dcd2
00000000`2467fd88 00007ffb`ffffffff : 00000000`00000005 00000000`00000005 00000000`258c2480 00007ffc`07794a0c : 0x258c2480
00000000`2467fd90 00000000`00000005 : 00000000`00000005 00000000`258c2480 00007ffc`07794a0c 00007ffc`00000000 : xmllite!_security_check_cookie
00000000`2467fd98 00000000`00000005 : 00000000`258c2480 00007ffc`07794a0c 00007ffc`00000000 00000000`258c2480 : 0x5
00000000`2467fda0 00000000`258c2480 : 00007ffc`07794a0c 00007ffc`00000000 00000000`258c2480 00000000`258c2480 : 0x5
00000000`2467fda8 00007ffc`07794a0c : 00007ffc`00000000 00000000`258c2480 00000000`258c2480 00000000`00000000 : 0x258c2480
00000000`2467fdb0 00007ffc`07781a33 : 00000000`0024a000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlpFlsDataCleanup+0xd8
00000000`2467fdf0 00007ffc`077448de : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`12425808 : ntdll!LdrShutdownThread+0x43
00000000`2467fef0 00007ffc`062754e9 : 00000000`12425808 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlExitUserThread+0x3e
00000000`2467ff30 00007ffc`0774485b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x19
00000000`2467ff60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x2b
SYMBOL_NAME: igd10iumd64+29dba4
MODULE_NAME: igd10iumd64
IMAGE_NAME: igd10iumd64.dll
STACK_COMMAND: ~32s; .ecxr ; kb
FAILURE_BUCKET_ID: INVALID_POINTER_WRITE_c0000005_igd10iumd64.dll!Unknown
OS_VERSION: 10.0.22000.1
BUILDLAB_STR: co_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
IMAGE_VERSION: 27.20.100.9664
FAILURE_ID_HASH: {4af8a78b-3515-cf5d-5e21-86f940c8082b}
Followup: MachineOwner
---------
You can test the new version 12.0.30, my short test experience: it doesn’t freeze anymore, although it does crash on loading (but this happens with version 11 too).
Thanks Steinberg
With my usual vsts, no crashes on exit or startup so far, and no freezes.
This update 12.0.30 seems to be working fine, fingers crossed!
Thank you @steinberg
@Martin.Jirsak
Hi there, just got this with 12.0.30:
Cubase 12.0.30.286 64bit 2022.6.11 12.17.00.360.dmp (1.1 MB)
I tried to open seventh heaven pro and cubase quit
This is the same dump as in the new topic I started here
Thank you so much Arthur Neeman for you workaround:
“Close project without closing Cubase, then open new empty project, close it and then close Cubase. It will quit without crash.”
My current projects are loaded with VST’s etc, so it’s hard to narrow it down to one in particular, but Cubase 12 now always hangs on quit, never did so with Cubase 11. New projects without plugins are ok; Cubase will close.
I agree Lucy63. It works. Just sent a crash report to Steinberg bout CB12. I think CB12 has a major problem internally Like type conversion mismatch or pointers overwriting memory etc. , that causers all this issues.
But all these workarounds take too much time, sadly. Since cubase 12 release I now do my recording in CB11 pro and all my work that relates to anything live in Ableton live 11 suite with I bought to survive.
Maybe we Cubase 12 pro buyers here should vote or create a name list to emphasize our demands.
My vote would go to:
Actually that was described on my first post: