Page 1 of 1

impossible to work like that! SOLVED

Posted: Sun Mar 01, 2020 8:00 pm
by anteas38
cubase 10.5.12 have a serious problem seen multiple comments I am not the only one.
I am running W10, ssd, 16 gb mem, 8 core processor

I think we spend more time on the forum looking for solutions than working on our projects


Résumé du vidage
----------------
Fichier de vidage: Cubase 10.5.12.123 64bit 2020.3.1 19.49.14.273.dmp : C:\Users\******\Documents\Steinberg\CrashDumps\Cubase 10.5.12.123 64bit 2020.3.1 19.49.14.273.dmp
Dernier temps d'écriture: 01/03/2020 19:49:14
Nom du processus: Cubase10.5.exe : C:\Program Files\Steinberg\Cubase 10.5\Cubase10.5.exe
Architecture du processus: x64
Code d'exception: 0xC0000005
Informations sur l'exception: Le thread a tenté de lire à partir d'une adresse virtuelle ou d'écrire vers une adresse virtuelle pour laquelle il ne dispose pas d'un accès appropriés.
Informations sur le tas: Absent

Informations système
--------------------
Version du système: 10.0.18363
Version(s) CLR:

Modules
-------
Nom du module Chemin du module Version du module
------------- ---------------- -----------------
Cubase10.5.exe C:\Program Files\Steinberg\Cubase 10.5\Cubase10.5.exe 10.5.12.123
ntdll.dll C:\Windows\System32\ntdll.dll 10.0.18362.657
kernel32.dll C:\Windows\System32\kernel32.dll 10.0.18362.329
KERNELBASE.dll C:\Windows\System32\KERNELBASE.dll 10.0.18362.693
ucrtbase.dll C:\Windows\System32\ucrtbase.dll 10.0.18362.387
msvcp140.dll C:\Windows\System32\msvcp140.dll 14.24.28127.4
msvcrt.dll C:\Windows\System32\msvcrt.dll 7.0.18362.1
combase.dll C:\Windows\System32\combase.dll 10.0.18362.693
msvcp_win.dll C:\Windows\System32\msvcp_win.dll 10.0.18362.387
win32u.dll C:\Windows\System32\win32u.dll 10.0.18362.693
user32.dll C:\Windows\System32\user32.dll 10.0.18362.657
kernel.appcore.dll C:\Windows\System32\kernel.appcore.dll 10.0.18362.1
winmm.dll C:\Windows\System32\winmm.dll 10.0.18362.1
graphics2d.dll C:\Program Files\Steinberg\Cubase 10.5\graphics2d.dll 1.1.2.123
d2d1.dll C:\Windows\System32\d2d1.dll 10.0.18362.1
d3d11.dll C:\Windows\System32\d3d11.dll 10.0.18362.387
dxgi.dll C:\Windows\System32\dxgi.dll 10.0.18362.693
inputhost.dll C:\Windows\System32\inputhost.dll 10.0.18362.387
CoreMessaging.dll C:\Windows\System32\CoreMessaging.dll 10.0.18362.1
SYNSOACC.dll C:\Windows\System32\SYNSOACC.dll 1.22.1.0
nvwgf2umx.dll C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_33895c186dfc2a0d\nvwgf2umx.dll 26.21.14.4250
baios.dll C:\Program Files\Steinberg\Cubase 10.5\Components\baios.dll 2.5.2.96
mediaservice.dll C:\Program Files\Steinberg\Cubase 10.5\Components\mediaservice.dll 2.2.1.23
avrt.dll C:\Windows\System32\avrt.dll 10.0.18362.1
wdmaud.drv C:\Windows\System32\wdmaud.drv 10.0.18362.1
videoengine.dll C:\Program Files\Steinberg\Cubase 10.5\Components\videoengine.dll 3.0.1.9
exceptiondumper.dll C:\Program Files\Steinberg\Cubase 10.5\Components\exceptiondumper.dll 1.3.0.26
dbghelp.dll C:\Windows\System32\dbghelp.dll 10.0.18362.1
dbgcore.dll C:\Windows\System32\dbgcore.dll 10.0.18362.1
VSTPlugManager.dll C:\Program Files\Steinberg\Cubase 10.5\Components\VSTPlugManager.dll 3.1.60.28
vstconnect.dll C:\Program Files\Steinberg\Cubase 10.5\Components\vstconnect.dll 4.0.10.12
msiltcfg.dll C:\Windows\System32\msiltcfg.dll 5.0.18362.1
ysusb_asio64.dll C:\Program Files (x86)\Yamaha\Yamaha Steinberg USB Driver\ysusb_asio64.dll 1.10.4.0
nvoglv64.dll C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_33895c186dfc2a0d\nvoglv64.dll 26.21.14.4250
Cubase Plug-in Set.vst3 C:\Program Files\Steinberg\Cubase 10.5\VST3\Cubase Plug-in Set.vst3\Contents\x86_64-win\Cubase Plug-in Set.vst3 8.5.10.142
mshtml.dll C:\Windows\System32\mshtml.dll 11.0.18362.693
eLicenserCore.dll C:\Program Files\eLicenser\Tools\eLicenserCore.dll 2.0.1.97
jscript9.dll C:\Windows\System32\jscript9.dll 11.0.18362.657
play_VST_x64.dll C:\Program Files\Vstplugins\play_VST_x64.dll 6.1.7.0
WrapPersist64.dll C:\Program Files (x86)\Common Files\PACE\Proxy\WrapPersist64.dll 0.0.0.0
HALion Sonic SE.dll C:\Program Files\Common Files\Steinberg\Shared Components\HALion Sonic SE\HALion Sonic SE.dll 3.3.1.77
Padshop.vst3 C:\Program Files\Common Files\VST3\Steinberg\Padshop\Padshop.vst3 2.0.1.44
Retrologue.vst3 C:\Program Files\Common Files\VST3\Steinberg\Retrologue\Retrologue.vst3 2.2.20.211

Re: impossible to work like that!

Posted: Sun Mar 01, 2020 10:10 pm
by Martin.Jirsak
Hi,

Please describe when did it happened and attach the source DMP file.

Re: impossible to work like that!

Posted: Sun Mar 01, 2020 10:39 pm
by anteas38
all the contents of the dmp I posted all that I can add is in "dmp-2.png"

Re: impossible to work like that!

Posted: Sun Mar 01, 2020 11:12 pm
by anteas38
it happens at any time, when I edit anything or when I do mixdown

Re: impossible to work like that!

Posted: Mon Mar 02, 2020 12:14 am
by Martin.Jirsak
Hi,

As I said, I need the description (are you editing Audio or MIDI, what kind of editing is it exactly; what editor; what functions)? And I need the source DMP file to be able to resolve it.

Re: impossible to work like that!

Posted: Mon Mar 02, 2020 12:50 am
by anteas38
for example, I edited stock compressor just before crash, then I put play then it crashed, a new crash when rendering mixdown etc. These past few days I haven't edited midi, just vst instruments and audio recordings

Re: impossible to work like that!

Posted: Mon Mar 02, 2020 1:35 am
by anteas38
i don't understand how steinberg can post such an update and boast about their satisfaction on the official website how well it works :evil: :?:

Re: impossible to work like that!

Posted: Mon Mar 02, 2020 7:58 am
by Martin.Jirsak
Hi,

I don't understand how you can send PNG file instead of DMP file 3 times. Again, please, attach the DMP file, please.

And please, the DMP file should match the description. So if it crashes in other scenario than the one you described, write the steps what you did before it crashed, please.

Re: impossible to work like that!

Posted: Mon Mar 02, 2020 12:56 pm
by anteas38
I sent dmp 2 ( dmp-1 and dmp-3 ) times so that we see that the crashes are successive, the dmp-2 is the screen cpt from VS debuging tool

Re: impossible to work like that!

Posted: Mon Mar 02, 2020 1:06 pm
by Steinberg
The VS debugging only includes the list of modules, it is not resolved.
We need the original .dmp files to resolve them fully, please, no other way.
Screenshots and non-resolved dumps are not useful.

Re: impossible to work like that!

Posted: Wed Mar 04, 2020 9:35 pm
by drmq
Steinberg, when are you going to implement an automatic way to send dmp files when there is a crash just like everybody else does?

Re: impossible to work like that!

Posted: Wed Mar 04, 2020 10:56 pm
by anteas38
Today I installed the new yam usb driver but it's even worse. I'm going crazy, it's not possible

Re: impossible to work like that!

Posted: Thu Mar 05, 2020 12:53 am
by Martin.Jirsak
Hi,
anteas38 wrote:
Wed Mar 04, 2020 10:56 pm
Today I installed the new yam usb driver but it's even worse. I'm going crazy, it's not possible
Could you attach the DMP file, please?

Re: impossible to work like that!

Posted: Thu Mar 19, 2020 1:20 pm
by anteas38
Hello everyone, my problem seems to be solved.
I had to uninstall cubase, clean the registers, and delete all the files that remained after uninstalling, I reinstalled the cubase 10.5.12 again and there it seems that it works fine except for a few small imperfections which I will point out so that they will be corrected in the next update if possible.
If you have problems that make you crash the software then do like me.