DS4Windows is causing repeated kernel crashes (BSOD) on my machine. The crashes occur while DS4Windows is running in the background after use — not necessarily during active controller input. The system has crashed multiple times since installing DS4Windows on this machine, with dumps dated April, May, and June 2026.
Environment
OS: Windows 11 (Kernel 26100, 24 logical processors)
DS4Windows version: 3.5
ViGEmBus version: 1.21.442.0 (latest)
Hardware: PCSpecialist Ionico Ii 16
Hyper-V active (required for Windows Subsystem for Android and WSL)
Bugcheck details:
Stop code: WDF_VIOLATION (0x10D)
Arg1: 0000000000000004 (NULL parameter passed to function requiring non-NULL)
Arg2: 0000000000000000
Arg3: fffff80437acb226 (caller address)
Arg4: ffffcf01c5893cb0
Failure bucket: 0x10D_4_ViGEmBus!unknown_function
Stack trace:
nt!KeBugCheckEx
Wdf01000!FxVerifierBugCheckWorker+0x24
Wdf01000!FxVerifierNullBugCheck+0x44
Wdf01000!imp_WdfObjectGetTypedContextWorker+0xb9
ViGEmBus+0xb226
The crash is occurring in WdfObjectGetTypedContextWorker which is receiving a NULL object. This appears to be
triggered after a controller session ends — DS4Windows is left running in the system tray with no controller connected, and at some point the driver faults.
This did not occur on my previous machine using DS4Windows over several years. The new machine has Hyper-V enabled and a different hardware configuration (Intel Wi-Fi 6, USB4). It is unclear whether the Hyper-V virtual device layer is involved in the interaction.
Kernel dumps are available if required.
DS4Windows is causing repeated kernel crashes (BSOD) on my machine. The crashes occur while DS4Windows is running in the background after use — not necessarily during active controller input. The system has crashed multiple times since installing DS4Windows on this machine, with dumps dated April, May, and June 2026.
Environment
OS: Windows 11 (Kernel 26100, 24 logical processors)
DS4Windows version: 3.5
ViGEmBus version: 1.21.442.0 (latest)
Hardware: PCSpecialist Ionico Ii 16
Hyper-V active (required for Windows Subsystem for Android and WSL)
Bugcheck details:
Stop code: WDF_VIOLATION (0x10D)
Arg1: 0000000000000004 (NULL parameter passed to function requiring non-NULL)
Arg2: 0000000000000000
Arg3: fffff80437acb226 (caller address)
Arg4: ffffcf01c5893cb0
Failure bucket: 0x10D_4_ViGEmBus!unknown_function
Stack trace:
nt!KeBugCheckEx
Wdf01000!FxVerifierBugCheckWorker+0x24
Wdf01000!FxVerifierNullBugCheck+0x44
Wdf01000!imp_WdfObjectGetTypedContextWorker+0xb9
ViGEmBus+0xb226
The crash is occurring in WdfObjectGetTypedContextWorker which is receiving a NULL object. This appears to be
triggered after a controller session ends — DS4Windows is left running in the system tray with no controller connected, and at some point the driver faults.
This did not occur on my previous machine using DS4Windows over several years. The new machine has Hyper-V enabled and a different hardware configuration (Intel Wi-Fi 6, USB4). It is unclear whether the Hyper-V virtual device layer is involved in the interaction.
Kernel dumps are available if required.