protonscr

Starfield Creation Kit Crashes when adding Linked Ref or Dialogue animation.

vkd3dopen
HansKristian-Work/vkd3d-proton#3136 · opened 2026-06-30 by Blayer98 · updated 2026-07-02 · 3 comments · github
BBlayer98 2026-06-30 github

https://github.com/ValveSoftware/Proton/issues/7884

If you attempt to add/edit a Linked Ref to any object in a Cell, and select OK, the CK appears to crash with an access violation exception.

The same crash also happens when adding/editing a dialogue animation, by going to a quest's scene, selecting the Animation in the flowchart UI, and then selecting Animation, then selecting the button listed below Dialogue Animation, and then selecting any animation in the list and clicking ok, causes yet another crash.

Image Image Image

All of these occur on Linux, and I noticed a ton of VDK3D-Proton errors in my logs.

Software information

Starfield: Creation Kit
zram-generator.conf updated to use more zram.

System information

  • System: Steam Deck 512GB OLED
  • GPU + Driver: AMD AMD Custom GPU 0932 (radeonsi, vangogh, LLVM 20.1.8, DRM 3.64, 6.16.12-valve24.1-1-neptune-616-gf807228f1b69)
  • Driver version: 4.6 (Compatibility Profile) Mesa 25.3.0 (git-59b552c765)
  • Proton version: Experimental-11.0-20260622b
  • Wine version: 11.0
  • VKD3D-Proton version: 3.1.0, build bee300e4caccbe2.

Log files

This zip file contains both the proton log and .dmp file generated by the CK when adding a dialogue animation.
https://github.com/user-attachments/files/29516942/steam-2722710.zip

This zip file contain the .dmp file and proton log after the CK crashed when adding a Linked Ref.

Archive.zip

I’m trying to figure out what exactly is causing the crashes, whether it’s wine-mono, vkd3d-proton, or something else, but I’m not good enough with coding to be able to figure this out all on my own. :(

BBlayer98 2026-07-01 github

I posted this on the main Proton issue page, but I'll post it here too in case it might be useful, these are both the proton log, and also the analysed minidump file I was able to do.

steam-2722710.zip

=== CRASH SUMMARY ===
Crash Reason  : EXCEPTION_ACCESS_VIOLATION_READ
Crash Address : 0xffffffff96e06d88
Crashing Thread: 5
Crashing Module: CreationKit.exe
OS            : Windows NT
CPU           : amd64
Uptime        : not available
Stack Quality : LOW (1331/1544 frames from stack scanning) - majority of frames found by stack scanning, results may be inaccurate
==================================================
Operating system: Windows NT
                  10.0.19045 
CPU: amd64
     family 23 model 145 stepping 0
     8 CPUs

GPU: UNKNOWN

Crash reason:  EXCEPTION_ACCESS_VIOLATION_READ
Crash address: 0xffffffff96e06d88
Process uptime: not available

Thread 5 (crashed)
 0  CreationKit.exe + 0x1daf92c
    rax = 0xffffffff96e06d80   rdx = 0x0000000000000000
    rcx = 0x0000000000000000   rbx = 0x0000000000000000
    rsi = 0x0000000000109db0   rdi = 0x0000000000109dc0
    rbp = 0x0000000000109e01   rsp = 0x0000000000109c90
     r8 = 0x0000000000000150    r9 = 0x0000000000000000
    r10 = 0x0000000000000008   r11 = 0x0000000000000202
    r12 = 0xffffffffffffffff   r13 = 0x00000001744fc1c0
    r14 = 0x0000000000109d98   r15 = 0x0000000000109ea0
    rip = 0x0000000141daf92c
    Found by: given as instruction pointer in context

Thread 0
 0  ntdll.dll + 0xea94
    rax = 0x00006fffffedd8b0   rdx = 0x0000000000000000
    rcx = 0x0000000000103790   rbx = 0x0000000000000000
    rsi = 0x0000000000000001   rdi = 0x0000000758edbae0
    rbp = 0x0000000000108890   rsp = 0x0000000000108848
     r8 = 0x0000000000104b70    r9 = 0x00006fffffedd8b0
    r10 = 0x0000000000000000   r11 = 0x0000000000000246
    r12 = 0x0000000000108d10   r13 = 0x0000000000000000
    r14 = 0x000000007ffc0000   r15 = 0x0000000000000000
    rip = 0x00006ffffff3ea94
    Found by: given as instruction pointer in context
 1  kernelbase.dll + 0x7238f
    rax = 0x00006fffffedd8b0   rdx = 0x0000000000000000
    rcx = 0x0000000000103790   rbx = 0x0000000000000000
    rsi = 0x0000000000000001   rdi = 0x0000000758edbae0
    rbp = 0x0000000000108890   rsp = 0x0000000000108850
     r8 = 0x0000000000104b70    r9 = 0x00006fffffedd8b0
    r10 = 0x0000000000000000   r11 = 0x0000000000000246
    r12 = 0x0000000000108d10   r13 = 0x0000000000000000
    r14 = 0x000000007ffc0000   r15 = 0x0000000000000000
    rip = 0x00006fffffc6238f
    Found by: simulating a return from leaf function
 2  ntdll.dll + 0xeb54  [confidence: LOW - stack scanning ⚠]
    rbp = 0x0000000000108890   rsp = 0x0000000000108858
    rip = 0x00006ffffff3eb54
    Found by: stack scanning
 3  kernelbase.dll + 0x581c9  [confidence: LOW - stack scanning ⚠]
    rbp = 0x0000000000108890   rsp = 0x0000000000108860
    rip = 0x00006fffffc481c9
    Found by: stack scanning
 4  CreationKit.exe + 0x4e268cf  [confidence: LOW - stack scanning ⚠]
    rbp = 0x0000000000108890   rsp = 0x0000000000108870
    rip = 0x0000000144e268cf
    Found by: stack scanning
 5  CreationKit.exe + 0x17c5b288  [confidence: LOW - stack scanning ⚠]
    rbp = 0x0000000000108890   rsp = 0x0000000000108880
    rip = 0x0000000157c5b288
    Found by: stack scanning
HHansKristian-Work maintainer 2026-07-02 github

I don't see any evidence that this is vkd3d-proton's fault.

BBlayer98 2026-07-02 github

I don't see any evidence that this is vkd3d-proton's fault.

I see, there are a ton of vkd3d-proton warnings gs about E_NOINTERFACE, I was wondering why that was. I also don’t know what is causing the issue now if it’s not wine-mono, not vkd3d-proton… I’m completely stumped now and these two crashes Don’t occur on Windows, but I don’t have a Windows system anymore…

Upstream links

DLLs