Kontakt 7 crashing in Cubase 13

rdalcroft · 2024-02-29T17:42:24+00:00

There was an error rendering this rich post.

rdalcroft

Happens straight after loading an instrument.

Also happens if i try to open more that one track with Kontakt 7 on it?

I have tried using the Nvidia GPU and also my Intel IGPU, thinking it may be a driver issue?

But it cant be as It happens on 2 different GPU's

Tried to upload the crash dump from cubase, but its not allowed to be attached here.

Find more posts tagged with

Accepted answers

rdalcroft

To fix this.

In Kontakt (standalone) go in the file - Options - Engine

Change Multiprocessor to disabled, restart,

then open Kontakt up again, change it back to 16 cores. Now close.

Open in Cubase, and No more D3d11 crashing, even when opening up multiple instanceses.

All comments

rdalcroft

To fix this.

In Kontakt (standalone) go in the file - Options - Engine

Change Multiprocessor to disabled, restart,

then open Kontakt up again, change it back to 16 cores. Now close.

Open in Cubase, and No more D3d11 crashing, even when opening up multiple instanceses.

PoorFellow

Thank you very much for sharing ! 🙂

rdalcroft

I spoke too soon.

There is definatly an issue with Kontakt 7 vst in both Cubase 13 and Ableton 11 and 12. Issue is with d3d11.dll.

The multicore thing only worked once in cubase. Ableton it crashes everytime.

I am not sure what it is referencing the d3d11.dll for. Could it be a driver issue? or something else.

Like I said already, it happens on both my Nvidia GPU and Intel IGPU, so thats 2 different drivers from different GPU manufacturers.

This seems to be a Kontakt issue, maybe windows 11. As it seems to be plagued with alsorts of issues relating to MPO, and its whole GPU WDM backend.

Here is a copy of the Dump file txt:

This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(5bd8.5004): Access violation - code c0000005 (first/second chance not available)
For analysis of this file, run !analyze -v
ntdll!NtGetContextThread+0x14:
00007ffb`29671284 c3              ret
0:098> !analyze -v
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

*** WARNING: Check Image - Checksum mismatch - Dump: 0x26c79b, File: 0x263c67 - C:\ProgramData\Dbg\sym\d3d11.dll\ECCA1C89257000\d3d11.dll
*** WARNING: Unable to verify timestamp for Kontakt 7.vst3plugin

KEY_VALUES_STRING: 1

    Key  : AV.Fault
    Value: Write

    Key  : Analysis.CPU.mSec
    Value: 156

    Key  : Analysis.Elapsed.mSec
    Value: 1349

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

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

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

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

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

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

    Key  : Failure.Bucket
    Value: INVALID_POINTER_WRITE_c0000005_d3d11.dll!CContext::TID3D11DeviceContext_RSSetState__1

    Key  : Failure.Hash
    Value: {46ee21a1-294d-b007-18ef-0c3e6b64d6bd}

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

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Version
    Value: 10.0.22621.1

    Key  : WER.Process.Version
    Value: 1.0.0.1


FILE_IN_CAB:  Live_12.0b29_2024-02-19_5094b92fa5_2024_03_01__01_46_08.dmp

CONTEXT:  (.ecxr)
rax=00007ffb22d52830 rbx=000000003ec82c20 rcx=0000000054699648
rdx=00000000552135d8 rsi=0000000000000000 rdi=0000000000000001
rip=00007ffb22d52830 rsp=000000004c86f878 rbp=000000004c86f980
 r8=000000005469a448  r9=00000000ffffffff r10=000000005581ea40
r11=0000000054699648 r12=00000000587395f0 r13=0000000000000000
r14=0000000058739638 r15=000000004c4f93a0
iopl=0         nv up ei pl nz na pe nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
d3d11!CContext::TID3D11DeviceContext_RSSetState_<1>:
00007ffb`22d52830 e9cbd7ffbf      jmp     00007ffa`e2d50000
Resetting default scope

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 00007ffb22d52830 (d3d11!CContext::TID3D11DeviceContext_RSSetState_<1>)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: ffffffffffffffc8
Attempt to write to address ffffffffffffffc8

PROCESS_NAME:  Ableton Live 12 Beta.exe

WRITE_ADDRESS:  ffffffffffffffc8 

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:  ffffffffffffffc8

STACK_TEXT:  
00000000`4c86f878 00007ffa`62408ba4     : 00000000`3ec82c20 00000000`00000000 00000000`00000000 00000000`00000000 : d3d11!CContext::TID3D11DeviceContext_RSSetState_<1>
00000000`4c86f880 00000000`3ec82c20     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`587394b0 : Kontakt_7+0x3018ba4
00000000`4c86f888 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`587394b0 00000000`58739490 : 0x3ec82c20


SYMBOL_NAME:  d3d11!CContext::TID3D11DeviceContext_RSSetState_<1>+0

MODULE_NAME: d3d11

IMAGE_NAME:  d3d11.dll

STACK_COMMAND:  ~98s; .ecxr ; kb

FAILURE_BUCKET_ID:  INVALID_POINTER_WRITE_c0000005_d3d11.dll!CContext::TID3D11DeviceContext_RSSetState__1_

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

IMAGE_VERSION:  10.0.22621.3139

FAILURE_ID_HASH:  {46ee21a1-294d-b007-18ef-0c3e6b64d6bd}

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

0:098> lmvm d3d11
Browse full module list
start             end                 module name
00007ffb`22c50000 00007ffb`22ea7000   d3d11    # (pdb symbols)          C:\ProgramData\Dbg\sym\d3d11.pdb\D7AC99B801BA80F273905541FB223F661\d3d11.pdb
    Loaded symbol image file: d3d11.dll
    Mapped memory image file: C:\ProgramData\Dbg\sym\d3d11.dll\ECCA1C89257000\d3d11.dll
    Image path: C:\Windows\System32\d3d11.dll
    Image name: d3d11.dll
    Browse all global symbols  functions  data
    Image was built with /Brepro flag.
    Timestamp:        ECCA1C89 (This is a reproducible build file hash, not a timestamp)
    CheckSum:         0026C79B
    ImageSize:        00257000
    File version:     10.0.22621.3139
    Product version:  10.0.22621.3139
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        2.0 Dll
    File date:        00000000.00000000
    Translations:     0409.04b0
    Information from resource tables:
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     D3D11.dll
        OriginalFilename: D3D11.dll
        ProductVersion:   10.0.22621.3233
        FileVersion:      10.0.22621.3233 (WinBuild.160101.0800)
        FileDescription:  Direct3D 11 Runtime
        LegalCopyright:   © Microsoft Corporation. All rights reserved.
0:098> .exr -1
ExceptionAddress: 00007ffb22d52830 (d3d11!CContext::TID3D11DeviceContext_RSSetState_<1>)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: ffffffffffffffc8
Attempt to write to address ffffffffffffffc8

rdalcroft

After some further testing, I believe, Nvidia's Geforce (or the New Nvidia App) overlay could be causing this crashing and throwing up the d3d11.dll error.

If i deactivate the Overlay in the Nvidia app, then these crashes seem not to happen.

Maybe worth, getting in touch with Nvidia about this. As before in the older release of geforce experience, this was never an issue with having the overlay enabled all the time.

(all thought the overlay is not physically open on screen, the overlay is always running, whether you see it or not. If you have geforce experience, or the Nvidia app installed, and you have ticked the box for the Nvidia overlay, then that overlay is present always in windows, running in the background). Was never an issue before, until their new Nvidia App. (1 week ago).

I have also submitted my finding over on the Nvidia forums.

rdalcroft

Update:

Even after disabling the Nvidia overlay.

This is still happening; I am at a loss here? Both Ableton and Cubase, I can't use more than 1 track with Kontakt, if I do, it will crash the whole DAW.

I cant even submit a crash report from Kontakt, because it doesn't think its crashed, I only get dump files from the DAW's as technically the DAW crashed. Although, Kontakt caused it.

Standalone there are no such crashes.

andrewfez

Man that sucks. I was gonna upgrade to the full Kontakt 7 to take advantage of the sale. But maybe I'll hold off until Native fixes the issue.

PoorFellow

https://community.native-instruments.com/discussion/comment/137434#Comment_137434

Quote one of your previous posts : "To fix this. , In Kontakt (standalone) go in the file - Options - Engine , Change Multiprocessor to disabled, restart, then open Kontakt up again, change it back to 16 cores. Now close."

Makes me want to ask : did you try to "Change Multiprocessor to disabled" permanently ?

rdalcroft

Hello

Thanks for asking.

Yes, I have tried:

I have it disabled for the VST.

I have also tried it with it disabled in the standalone app too, but I do not see how that could affect the kontakt.vst

Hopefully Native Instruments will see this and other comments that others are having, and maybe come up with a fix.

It seems, there are people who are having issues on both mac and windows, in different scenarios, different DAW's but all relating to Kontakt 7.

rdalcroft

https://community.native-instruments.com/discussion/comment/137598#Comment_137598

I would not hold off on your upgrade, as I do not think this is affecting most people.

If it does, it will be fixed pretty quick, as NI are pretty good at fixes and updates.

andrewfez

@rdalcroft

I'm on Windows 11 also, though when I built this computer, I didn't add a graphics card.

Idk - right now I'm working out of town during the week, so only have 2 days on the weekend to write some tunes. Basically if something does go wrong, and it takes me several days to resolve it, that could easily be several weeks of not composing.

The front end on just downloading the free Kontakt was a bit glitchy. Took several attempts to dl and even when a task was complete, it wouldn't say so on the main NI window.

But thanks for the reply! Hope your issue gets fixed!

andrewfez

Actually - changed my mind - I want my harp to work - so I'm gonna take the plunge....

reffahcs

https://community.native-instruments.com/discussion/comment/137647#Comment_137647

I just tested my Windows 10 setup and had no issues running the latest Kontakt 7 in Ableton Live 11. Running an NVIDIA GPU and AMD CPU.

andrewfez

@reffahcs

I was able to install it okay without it affecting my current project I'm working on. Now I finally have the harp - sort of. Spitfire reworked their library into an all inclusive symphonic package recently, meaning the harp is not a standalone library I can see in NA, so now I can't see the harp in the rack (the fancy graphics that is). I just have to shuffle through the files to load what I need. Good enough to work.

rdalcroft

https://community.native-instruments.com/discussion/comment/137768#Comment_137768

I do realise this does not affect everyone. Note you are on (Windows 10). I am on Windows 11.

Did you load Multiple tracks with Kontact on. I can use one track fine. It's usually on the 2nd or third instance where it will crash the DAW.

Thanks for the Input though.

rdalcroft

https://community.native-instruments.com/discussion/comment/137801#Comment_137801

So glad it worked for you.

Quick links

Unanswered questions