Vulkan Developer Driver 440.66.09 graphical issues with DXVK games (Linux)

After updating to Vulkan Developer Driver 440.66.09 I get flickering horizontal black bars across my screen in DXVK/Steam Play titles. The severity changes from game to game (and scene to scene within the same game). The previous version (440.66.08) works without issues.
Tried with the games “b” (severe issues especially during launch), “CubeWorld” (minor issues on the title screen) and “Dying Light” (many issues, especially when looking around).
A user on the phoronix forums also confirmed these issues with the new version.

System Details:
PROCESSOR: Intel Core i5-3350P @ 3.30GHz
Core Count: 4
Extensions: SSE 4.2 + AVX + RDRAND + FSGSBASE
Cache Size: 6144 KB
Microcode: 0x21
Scaling Driver: intel_pstate powersave

GRAPHICS: eVGA NVIDIA GeForce GTX 1050 Ti 4GB
Frequency: 1354/3504MHz
OpenGL: 4.6.0
Vulkan: 1.2.136
Display Driver: NVIDIA 440.66.09
Monitor: ZOWIE XL LCD
Screen: 1920x1080

MOTHERBOARD: MEDION MS-7797 v1.1
BIOS Version: M7797W08.209
Chipset: Intel Xeon E3-1200 v2/3rd
Audio: Realtek ALC887-VD
Network: Realtek RTL8111/8168/8411

MEMORY: 8GB

DISK: 1000GB Samsung SSD 860
File-System: ext4
Mount Options: errors=remount-ro relatime rw
Disk Scheduler: MQ-DEADLINE

OPERATING SYSTEM: Solus 4.1
Kernel: 5.5.11-151.current (x86_64)
Desktop: GNOME Shell 3.36.1
Display Server: X Server 1.20.7
Compiler: GCC 9.3.0 + Clang 9.0.1 + LLVM 9.0.1
Security: itlb_multihit: KVM: Mitigation of Split huge pages
+ l1tf: Mitigation of PTE Inversion; VMX: conditional cache flushes SMT disabled
+ mds: Mitigation of Clear buffers; SMT disabled
+ meltdown: Mitigation of PTI
+ spec_store_bypass: Mitigation of SSB disabled via prctl and seccomp
+ spectre_v1: Mitigation of usercopy/swapgs barriers and __user pointer sanitization
+ spectre_v2: Mitigation of Full generic retpoline IBPB: conditional IBRS_FW STIBP: disabled RSB filling
+ tsx_async_abort: Not affected

1 Like

Can confirm this for Fallout 76 at least. Reverting to 440.66.08 fixed all stutter issues for me.

1 Like

I can confirm that the new version 440.66.11 fixes this issue.