Cubase 13.0.30 not scanning 3rd party VST3 plugins with new admin user account

rickpaul · May 27, 2024, 6:33am

This relates to the discussion posted in Cubase Pro 13.0.30 (Windows 10) crash in inference engine on startup and a troubleshooting step Waves support is insisting I do.

Specifically, they are requesting that I try a problem project that is crashing Cubase on the first start after a reboot using a newly created admin user account. While, from my perspective, this is just an information gathering step (I need this to work with my account, which also is an admin user account!), all the information I’ve supplied them to date has not yet led to a solution, so I am trying to carry out this step. However, when I try running Cubase 13 (or 12, for that matter) with the new admin user account, Cubase does not scan third party VST3 plugins, and thus I cannot actually try the problem project since Waves’ plugins are VST3 and do not get scanned.

I’ve already looked through various threads on this topic, including All 3rd Party VST 3 plugins today refuse to load? How to I force a VST3 rescan? with no luck in anything that helps get past the issue.

One thing I am finding is an event viewer entry that vstscannermaster.exe is crashing with an exception code of 0xc0000409. Here is the full event log information:

Log Name:      Application
Source:        Application Error
Date:          5/26/2024 10:25:57 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      RP-Studio
Description:
Faulting application name: vstscannermaster.exe, version: 4.2.10.5, time stamp: 0x653bc178
Faulting module name: vstscannermaster.exe, version: 4.2.10.5, time stamp: 0x653bc178
Exception code: 0xc0000409
Fault offset: 0x000000000014c895
Faulting process id: 0x42d4
Faulting application start time: 0x01daaff6597ff4c2
Faulting application path: C:\Program Files\Steinberg\Cubase 13\Components\vstscannermaster.exe
Faulting module path: C:\Program Files\Steinberg\Cubase 13\Components\vstscannermaster.exe
Report Id: dfdf42fb-a2eb-4b7d-ab0f-917f49677ab0
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2024-05-27T05:25:57.4197294Z" />
    <EventRecordID>43479</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>RP-Studio</Computer>
    <Security />
  </System>
  <EventData>
    <Data>vstscannermaster.exe</Data>
    <Data>4.2.10.5</Data>
    <Data>653bc178</Data>
    <Data>vstscannermaster.exe</Data>
    <Data>4.2.10.5</Data>
    <Data>653bc178</Data>
    <Data>c0000409</Data>
    <Data>000000000014c895</Data>
    <Data>42d4</Data>
    <Data>01daaff6597ff4c2</Data>
    <Data>C:\Program Files\Steinberg\Cubase 13\Components\vstscannermaster.exe</Data>
    <Data>C:\Program Files\Steinberg\Cubase 13\Components\vstscannermaster.exe</Data>
    <Data>dfdf42fb-a2eb-4b7d-ab0f-917f49677ab0</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

Any clues what might be going on and how to get past this? FWIW, my normal user account (also an admin user) has no problem with third party VST3 plugins in Cubase 13 (or 12, for that matter), so this is something specific to trying to run Cubase with the new admin user account. (This is also my second time trying this test after giving up the first time due to this issue, deleting the account, and starting over creating a new admin account.)

Martin.Jirsak · May 27, 2024, 7:31am

Hi,

Is this a DMP file? If yes, could you share the source DMP file, to be able to resolve it, please?

rickpaul · May 27, 2024, 3:13pm

No, there is no DMP file available. In particular, this is not a Cubase crash – Cubase still comes up, just without third party VST3 plugins – so there is nothing in CrashDumps. Checking more Event Viewer entries, it looks like Windows should have been producing a DMP file:

Log Name:      Application
Source:        Windows Error Reporting
Date:          5/26/2024 10:57:52 PM
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      RP-Studio
Description:
Fault bucket 2293722532587394555, type 5
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:
P1: vstscannermaster.exe
P2: 4.2.10.5
P3: 653bc178
P4: vstscannermaster.exe
P5: 4.2.10.5
P6: 653bc178
P7: 000000000014c895
P8: c0000409
P9: 0000000000000007
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2AED.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B3C.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B4D.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B5A.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B8A.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_vstscannermaster_2d9010846f423cd1dc36bba36618c9b1134c771_d830a785_31e578f3-7eeb-4df9-bef8-097104eb4c02

Analysis symbol: 
Rechecking for solution: 0
Report Id: 1553a6f6-4404-4b54-a6ca-40369c0d4060
Report Status: 268435456
Hashed bucket: e1389138e8b5a5a3dfd4f07da02e55fb
Cab Guid: 0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Windows Error Reporting" />
    <EventID Qualifiers="0">1001</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2024-05-27T05:57:52.3195298Z" />
    <EventRecordID>43491</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>RP-Studio</Computer>
    <Security />
  </System>
  <EventData>
    <Data>2293722532587394555</Data>
    <Data>5</Data>
    <Data>BEX64</Data>
    <Data>Not available</Data>
    <Data>0</Data>
    <Data>vstscannermaster.exe</Data>
    <Data>4.2.10.5</Data>
    <Data>653bc178</Data>
    <Data>vstscannermaster.exe</Data>
    <Data>4.2.10.5</Data>
    <Data>653bc178</Data>
    <Data>000000000014c895</Data>
    <Data>c0000409</Data>
    <Data>0000000000000007</Data>
    <Data>
    </Data>
    <Data>
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2AED.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B3C.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B4D.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B5A.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B8A.tmp.txt</Data>
    <Data>\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_vstscannermaster_2d9010846f423cd1dc36bba36618c9b1134c771_d830a785_31e578f3-7eeb-4df9-bef8-097104eb4c02</Data>
    <Data>
    </Data>
    <Data>0</Data>
    <Data>1553a6f6-4404-4b54-a6ca-40369c0d4060</Data>
    <Data>268435456</Data>
    <Data>e1389138e8b5a5a3dfd4f07da02e55fb</Data>
    <Data>0</Data>
  </EventData>
</Event>

However, there is nothing at the location. What I do find in a related directory is a WER report (pasting here in case it of any use, but I suspect it mostly has the same information as already given):

Version=1
EventType=BEX64
EventTime=133612630714312528
ReportType=2
Consent=1
UploadTime=133612630716270533
ReportStatus=268435456
ReportIdentifier=31e578f3-7eeb-4df9-bef8-097104eb4c02
IntegratorReportIdentifier=1553a6f6-4404-4b54-a6ca-40369c0d4060
Wow64Host=34404
NsAppName=vstscannermaster.exe
OriginalFilename=vstscannermaster.exe
AppSessionGuid=00002524-0002-00c5-bb2c-12cffaafda01
TargetAppId=W:00069498bd94e25309a54888e38d1f2ccf8f00000000!0000edd63ab32438ef79c2333ed906ae6f889122f16d!vstscannermaster.exe
TargetAppVer=2023//10//27:13:56:08!21d655!vstscannermaster.exe
BootId=4294967295
TargetAsId=2991
IsFatal=1
EtwNonCollectReason=1
Response.BucketId=e1389138e8b5a5a3dfd4f07da02e55fb
Response.BucketTable=5
Response.LegacyBucketId=2293722532587394555
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=vstscannermaster.exe
Sig[1].Name=Application Version
Sig[1].Value=4.2.10.5
Sig[2].Name=Application Timestamp
Sig[2].Value=653bc178
Sig[3].Name=Fault Module Name
Sig[3].Value=vstscannermaster.exe
Sig[4].Name=Fault Module Version
Sig[4].Value=4.2.10.5
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=653bc178
Sig[6].Name=Exception Offset
Sig[6].Value=000000000014c895
Sig[7].Name=Exception Code
Sig[7].Value=c0000409
Sig[8].Name=Exception Data
Sig[8].Value=0000000000000007
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.19045.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=1811
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=181110d1cc6ba86e93596ea1a2987c72
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=9731
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=9731c684b884879ae40ea8cfd793adb2
UI[2]=C:\Program Files\Steinberg\Cubase 13\Components\vstscannermaster.exe
LoadedModule[0]=C:\Program Files\Steinberg\Cubase 13\Components\vstscannermaster.exe
LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\WINDOWS\System32\KERNEL32.DLL
LoadedModule[3]=C:\WINDOWS\System32\KERNELBASE.dll
LoadedModule[4]=C:\WINDOWS\System32\ole32.dll
LoadedModule[5]=C:\WINDOWS\System32\ucrtbase.dll
LoadedModule[6]=C:\WINDOWS\System32\RPCRT4.dll
LoadedModule[7]=C:\WINDOWS\System32\combase.dll
LoadedModule[8]=C:\WINDOWS\System32\GDI32.dll
LoadedModule[9]=C:\WINDOWS\System32\win32u.dll
LoadedModule[10]=C:\WINDOWS\System32\gdi32full.dll
LoadedModule[11]=C:\WINDOWS\System32\msvcp_win.dll
LoadedModule[12]=C:\WINDOWS\System32\USER32.dll
LoadedModule[13]=C:\WINDOWS\System32\SHELL32.dll
LoadedModule[14]=C:\WINDOWS\System32\SHLWAPI.dll
LoadedModule[15]=C:\WINDOWS\System32\msvcrt.dll
LoadedModule[16]=C:\WINDOWS\System32\IMM32.DLL
LoadedModule[17]=C:\WINDOWS\SYSTEM32\kernel.appcore.dll
LoadedModule[18]=C:\WINDOWS\System32\bcryptPrimitives.dll
LoadedModule[19]=C:\WINDOWS\system32\uxtheme.dll
LoadedModule[20]=C:\WINDOWS\SYSTEM32\windows.storage.dll
LoadedModule[21]=C:\WINDOWS\SYSTEM32\Wldp.dll
LoadedModule[22]=C:\WINDOWS\System32\advapi32.dll
LoadedModule[23]=C:\WINDOWS\System32\sechost.dll
LoadedModule[24]=C:\WINDOWS\System32\bcrypt.dll
LoadedModule[25]=C:\WINDOWS\System32\OLEAUT32.dll
LoadedModule[26]=C:\WINDOWS\System32\SHCORE.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
OsInfo[0].Key=vermaj
OsInfo[0].Value=10
OsInfo[1].Key=vermin
OsInfo[1].Value=0
OsInfo[2].Key=verbld
OsInfo[2].Value=19045
OsInfo[3].Key=ubr
OsInfo[3].Value=4412
OsInfo[4].Key=versp
OsInfo[4].Value=0
OsInfo[5].Key=arch
OsInfo[5].Value=9
OsInfo[6].Key=lcid
OsInfo[6].Value=1033
OsInfo[7].Key=geoid
OsInfo[7].Value=244
OsInfo[8].Key=sku
OsInfo[8].Value=48
OsInfo[9].Key=domain
OsInfo[9].Value=0
OsInfo[10].Key=prodsuite
OsInfo[10].Value=256
OsInfo[11].Key=ntprodtype
OsInfo[11].Value=1
OsInfo[12].Key=platid
OsInfo[12].Value=10
OsInfo[13].Key=sr
OsInfo[13].Value=0
OsInfo[14].Key=tmsi
OsInfo[14].Value=222684858
OsInfo[15].Key=osinsty
OsInfo[15].Value=3
OsInfo[16].Key=iever
OsInfo[16].Value=11.3636.19041.0-11.0.1000
OsInfo[17].Key=portos
OsInfo[17].Value=0
OsInfo[18].Key=ram
OsInfo[18].Value=16296
OsInfo[19].Key=svolsz
OsInfo[19].Value=1861
OsInfo[20].Key=wimbt
OsInfo[20].Value=0
OsInfo[21].Key=blddt
OsInfo[21].Value=191206
OsInfo[22].Key=bldtm
OsInfo[22].Value=1406
OsInfo[23].Key=bldbrch
OsInfo[23].Value=vb_release
OsInfo[24].Key=bldchk
OsInfo[24].Value=0
OsInfo[25].Key=wpvermaj
OsInfo[25].Value=0
OsInfo[26].Key=wpvermin
OsInfo[26].Value=0
OsInfo[27].Key=wpbuildmaj
OsInfo[27].Value=0
OsInfo[28].Key=wpbuildmin
OsInfo[28].Value=0
OsInfo[29].Key=osver
OsInfo[29].Value=10.0.19041.4412.amd64fre.vb_release.191206-1406
OsInfo[30].Key=buildflightid
OsInfo[30].Value=169EB6B3-AF73-4A01-A70B-C4C31FB731A9.1
OsInfo[31].Key=edition
OsInfo[31].Value=Professional
OsInfo[32].Key=ring
OsInfo[32].Value=Retail
OsInfo[33].Key=expid
OsInfo[33].Value=RS:19B1B
OsInfo[34].Key=fconid
OsInfo[35].Key=containerid
OsInfo[36].Key=containertype
OsInfo[37].Key=edu
OsInfo[37].Value=0
FriendlyEventName=Stopped working
ConsentKey=BEX64
AppName=VST 3 Plug-In Scanner Master
AppPath=C:\Program Files\Steinberg\Cubase 13\Components\vstscannermaster.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=C16E211A388C8FFFFFBFB02383FA2E1E
MetadataHash=935834192

Because the information in the Event log was pointing to a temporary directory, I tried this morning to see if Windows was just cleaning it up after sending it to its own server by unplugging my Ethernet cable and putting Windows in airplane mode (to disable wireless communications), but still no DMP file shows up.

st10ss · May 28, 2024, 1:36am

What plugins you are talking about?

rickpaul · May 28, 2024, 2:42am

Any third party ones. The only ones that end up showing up in Cubase are Steinberg’s. It is assumedly due to vstscannermaster.exe crashing as noted above. (This is only when trying to start Cubase with the newly created admin account for Waves’ testing purposes. My normal account, which also has admin privileges, has all relevant VST3 plugins scanned and working.)

In case you were asking about the Waves plugins, it is specifically Clarity Vx DeReverb and Clarity Vx (in that sequence within a channel) that, upon first load of such a project after rebooting, crashes Cubase (12.0.70 or 13.0.30, which are the only versions I still have installed on my system).

Martin.Jirsak · May 28, 2024, 4:58am

Hi,

Have you tried any other but Waves plug-in, please?

rickpaul · May 28, 2024, 5:32am

As I indicated above, no third party VST3 plugins get scanned (and I have LOADS of VST3 plugins, from the likes of Waves, PSP Audioware, NI, Arturia, IK, and more). The only VST3 plugins that show up with this newly created admin account are from Steinberg.

I’m guessing this is because Steinberg’s VST3 plugins get scanned some way other than the way normal VST3 plugins are scanned, so the crash of vstscannermaster.exe does not affect them.

Martin.Jirsak · May 28, 2024, 6:46am

Hi,

We would need a DMP file to be able to have a look inside.

st10ss · May 28, 2024, 8:48am

TBH, the admin account will not have access to the data of the old account.
You need to install some plugins again, at least the plugins installed for one user only.

rickpaul · May 28, 2024, 8:38pm

Unfortunately, the VST3 scanning program isn’t capturing its own DMP like Cubase does, and, if Microsoft is capturing one, it is extremely transitory (like disappearing within less than a second – I was watching the directory where the event log indicated those should be put at one or two points while trying to “catch” one, but, if a DMP file was among the files that briefly appeared, it was gone as soon as it appeared, and was not located to another directory in the general area, nor did searching for DMP files in the related directories find anything).

That said, if you know of a way to capture a DMP file from a program that only runs for a split second (e.g. the equivalent of “stalking” the program name when it is not yet running, so that, as soon as it does, it is being monitored and a dump can be taken), please let me know. I’ve used the stock “procdump64 -e -h -t Cubase13” to capture DMP files from Cubase, but that is once they are already running and in a hung state.

The thing is, it isn’t finding any of the third party VST3 plugins, only Steinberg’s VST3 plugins (as evidenced by the Plug-in Manager list afterward). It does find the VST2 versions of plugins from the same developers who’d normally be in the VST3 plugins list. (Waves doesn’t have VST2 plugins anymore, so it’s not like I can even try those versions of their plugins to see if they also have the issue.) So it can’t just be an issue with some subset of plugins that are installed for one user only. (I generally take the defaults from any given plugin installation for whether it is one user or all users since I would normally only have one user account on my PC anyway, and switching accounts is a pain due to different desktop setups, application data, etc.)

Martin.Jirsak · May 28, 2024, 8:43pm

Hi,

Generate a DMP file and share it via Dropbox or a similar service, please.

Use the Microsoft ProcDump utility to generate a DMP file, please.

Please download ProcDump64 from Microsoft (~650kB) and extract the archive to a local folder on your hard disk.
Run Command Prompt (cmd) as administrator (right click and select “run as administrator”)
Navigate (in the Command Prompt) to the folder with the extracted procdump file.
For example:
cd C:\ Users \ \ Downloads \ Procdump
Note: the dmp file will be written into that folder.
Launch Cubase/Nuendo. You can work as usual. At any time, change to the command prompt and start procdump, to monitor Cubase/Nuendo for unexpected behaviour (see next step).
Launch procdump64 via Command Prompt:
Cubase 13:
procdump64 -e -h -t Cubase13

Nuendo 13:
procdump64 -e -h -t Nuendo13

The -h option will write a dmp file in case of an application hang. This might kick in too early sometimes, in case some action takes a little longer. Feel free to skip the “-h” option, if you are only up for fetching crashes.
The option -e will catch exceptions and the option -t terminations of the application.

Prodump is now monitoring the Cubase/Nuendo process and will write a crash log, in case Cubase/Nuendo crashes or hangs. Perform the action that causes Cubase/Nuendo to crash and send us the generated crash dmp.

ZIP and share the DMP file via Dropbox or a similar service, please.

rickpaul · May 28, 2024, 10:06pm

Okay, thanks. I didn’t think this would be applicable because Cubase was not itself crashing – only the VST3 scanner – but I just tried it right after Cubase started, and it did create a DMP file. It was too big to upload here, so I’ve zipped it and made it available at:

FWIW, here is what WinDBG sees from that (though assumedly the DMP file can provide more information – assuming, of course, it is capturing the crash of the scanner and not just some random moment in Cubase’s execution before it gets to the dialog box that mentions the missing plugins in the project):


************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : false
   AllowNugetExeUpdate : false
   NonInteractiveNuget : true
   AllowNugetMSCredentialProviderInstall : false
   AllowParallelInitializationOfLocalRepositories : true

   EnableRedirectToV8JsProvider : false

   -- Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.234 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 41

Microsoft (R) Windows Debugger Version 10.0.27553.1004 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [E:\Tracks\Test\Waves VxReverb test\Cubase13.exe_240528_145327.dmp]
Comment: '
*** procdump64  -e -h -t Cubase13
*** Hung window detected: 60916'
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 19045 MP (12 procs) Free x64
Product: WinNt, suite: SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Debug session time: Tue May 28 14:53:27.000 2024 (UTC - 7:00)
System Uptime: not available
Process Uptime: 0 days 0:00:07.000
................................................................
............................................
Loading unloaded module list
.................
For analysis of this file, run !analyze -v
win32u!NtDCompositionWaitForChannel+0x14:
00007fff`77353a04 c3              ret
0:000> !analyze -v
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3124

    Key  : Analysis.Elapsed.mSec
    Value: 9559

    Key  : Analysis.IO.Other.Mb
    Value: 3

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 10

    Key  : Analysis.Init.CPU.mSec
    Value: 296

    Key  : Analysis.Init.Elapsed.mSec
    Value: 5396

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 274

    Key  : Failure.Bucket
    Value: BREAKPOINT_80000003_win32u.dll!NtDCompositionWaitForChannel

    Key  : Failure.Hash
    Value: {d72ea3de-f0ea-9458-6bdb-2d4cd9aa41e8}

    Key  : Timeline.Process.Start.DeltaSec
    Value: 7

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1

    Key  : WER.Process.Version
    Value: 13.0.40.251


FILE_IN_CAB:  Cubase13.exe_240528_145327.dmp

COMMENT:  
*** procdump64  -e -h -t Cubase13
*** Hung window detected: 60916

NTGLOBALFLAG:  0

APPLICATION_VERIFIER_FLAGS:  0

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 0000000000000000
   ExceptionCode: 80000003 (Break instruction exception)
  ExceptionFlags: 00000000
NumberParameters: 0

FAULTING_THREAD:  00006100

PROCESS_NAME:  Cubase13.exe

ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION}  Breakpoint  A breakpoint has been reached.

EXCEPTION_CODE_STR:  80000003

STACK_TEXT:  
00000000`0014ec08 00007fff`737fa17e     : 0000b000`0000b000 00000000`02fb1540 00000000`02f50568 00000000`fffffff0 : win32u!NtDCompositionWaitForChannel+0x14
00000000`0014ec10 00000001`4472ae63     : 00000000`02fb1540 00000000`02f50568 00000000`003a7800 00007fff`783a0653 : dcomp!DirectComposition::KernelChannel::WaitForChannel+0xe
00000000`0014ec40 00000001`447249f7     : 00000000`00000000 00000000`0014eed0 00000000`02f504a0 00000000`00654ab0 : Cubase13+0x472ae63
00000000`0014ecd0 00000001`44722ef8     : 00000000`00000000 00000146`00000258 00000000`02f504e8 00000000`0014eed0 : Cubase13+0x47249f7
00000000`0014ed50 00000001`4258b73c     : 00000000`00654ab0 00000001`46f6fa30 00000001`46f6fa30 00000001`4419ef6f : Cubase13+0x4722ef8
00000000`0014ed80 00000001`441ae99c     : 00000000`02e799e0 00000000`0014eed0 00000001`46f6fa30 00000001`46f6fa30 : Cubase13+0x258b73c
00000000`0014edd0 00000001`441e4807     : 00000001`46f6fa30 00000000`11aa5bf0 00000000`00000002 00000001`00000076 : Cubase13+0x41ae99c
00000000`0014f6e0 00000001`441e3e7d     : 00000000`10958700 00000000`09cbc7f8 00000000`00000016 00000000`11bbc820 : Cubase13+0x41e4807
00000000`0014f780 00000001`441e370a     : 00000001`46f6fa30 00000000`0014fb60 00000000`00654ab0 00000000`00000000 : Cubase13+0x41e3e7d
00000000`0014f930 00000001`4258a1ee     : 00000000`00654c98 00000000`0014f708 00000000`0014f658 00000000`0014f878 : Cubase13+0x41e370a
00000000`0014fa60 00000001`434d3f39     : 00000000`11a2a670 00000000`0014faf8 00000000`00000196 00000001`45f39440 : Cubase13+0x258a1ee
00000000`0014fbf0 00000001`44372367     : 00000000`00000000 00000000`00000196 00000000`0014fbf0 00000001`45f39440 : Cubase13+0x34d3f39
00000000`0014fc20 00000001`4436f07e     : 00000000`00654ab0 00000000`00000000 00000000`0014fc18 00000000`0014fb68 : Cubase13+0x4372367
00000000`0014fc60 00000001`434d3d24     : 00000000`00654ab0 00000000`00654ab0 00000000`00654cf8 00000000`00654d30 : Cubase13+0x436f07e
00000000`0014fc90 00000001`44832b66     : 00000000`00000000 00000000`0014fcb8 00000000`0014fcf8 00000000`0014fcb8 : Cubase13+0x34d3d24
00000000`0014fef0 00007fff`77597344     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Cubase13+0x4832b66
00000000`0014ff30 00007fff`795026b1     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14
00000000`0014ff60 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21


STACK_COMMAND:  ~0s; .ecxr ; kb

SYMBOL_NAME:  win32u!NtDCompositionWaitForChannel+14

MODULE_NAME: win32u

IMAGE_NAME:  win32u.dll

FAILURE_BUCKET_ID:  BREAKPOINT_80000003_win32u.dll!NtDCompositionWaitForChannel

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

IMAGE_VERSION:  6.2.19041.4412

FAILURE_ID_HASH:  {d72ea3de-f0ea-9458-6bdb-2d4cd9aa41e8}

Followup:     MachineOwner
---------

Vicken · May 29, 2024, 1:11am

I have the same problem today and I thought it was related to 13.0.40 update, however, I can’t log in to my iLok account and there is a problem on their website and service, also my UA connect freezes and might be related to iLok as well!!
I use EW Opus with iLok and that software is working fine outside of Cubase.

rickpaul · May 29, 2024, 1:35am

While I did try the issue I was having with 13.0.40 today, just to see if it made a difference, it did not. The issue I am seeing in this area doesn’t happen with my normal account, just the new admin account I set up to try to run a test Waves was asking me to do. I’m pretty sure it relates to the program that scans for VST3 plugins crashing (I posted an event log entry for that above, and that was consistent every time I tried starting Cubase with that account).

I’m not having any issues with VST scanning on my normal account, but I don’t think any of my iLok-based plugins have had updates in the last few days (the latest one I’m aware of that did was a few updates to PSP Flare last week).

If you can’t scan iLok-based plugins due to the iLok server’s being down, I wonder if that means you have plugins registered in the iLok cloud, rather than on a hardware dongle or on your hard disk (or whatever iLok uses for the non-cloud, software-only registrations)? (Of course, if it’s working in non-Cubase areas that also depend on the iLok authorization, I’d expect those to have issues if the server to connect to the cloud authorizations is down, unless maybe they have some grace period to cover such scenarios.)

Martin.Jirsak · May 29, 2024, 7:11am

Hi,

Reported to Steinberg. Thank you.

Martin.Jirsak · May 30, 2024, 10:10am

Hi @rickpaul ,

Could you please attach the source vstscanner DMP file located here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_vstscannermaster_2d9010846f423cd1dc36bba36618c9b1134c771_d830a785_31e578f3-7eeb-4df9-bef8-097104eb4c02

rickpaul · May 30, 2024, 3:57pm

There is no DMP file there, only a single Report.wer file. I think that is the same one as I pasted above, but I’m uploading it here (in a ZIP file because the forum won’t allow me to upload a WER file), just in case…

Report.zip (2.4 KB)

I also saw your earlier note (now deleted? – I’m not seeing it here now) in an email notification mentioning something about the graphic card and asking for a system profile. If you still need that and in some specific format (or from some specific system utility), please let me know. But the snapshot (probably in my forum profile) is:

Windows 10 Pro (10.0.19045 Build 19045)
Intel i7-5820k CPU (3.30 GHz)
16 GB RAM
NVidia GeForce GT 640 graphics card
2 ASUS VA247 monitors
MOTU 828x audio interface running on Thunderbolt II
ASUS X-99 Deluxe motherboard (with the Thunderbolt II adapter)

It probably goes without saying that my main account, which does not have this problem, is using the same exact underlying system as the newly created admin account that has the problem.

Also, I tried Cakewalk by BandLab with the new admin account, and it scanned all my VST3 plugins, including the Waves ones I was intending to test with the new account. (But Cakewalk doesn’t get the crash that Cubase 12 and 13 get on the first load a similar project after a reboot.)

Martin.Jirsak · May 30, 2024, 4:18pm

Hi,

I see, wierd. Thank you.

ChantiGreene · September 11, 2024, 11:00pm

Remove everything in the VST3 folder but “Steinberg” folder and restart Cubase. Close Cubase and put everthing back… Worked for me

ollyonpiano · October 28, 2024, 11:00pm

Just wanted to say I had the exact same issue after creating a new admin user and ChantiGreene’s suggestion above fixed it, so thanks!