Build Environment
Windows 11, NVIDIA GeForce RTX 3060,
LeiaSR-Runtime 1.34.12+
DisplayXR 25.1.0.472
Steps to Reproduce
- Install FPS Monitor on top of DisplayXR and SR Runtime
- Try to run any displayXR application
- Check windows events
Expected Behavior
App starts normally
Actual Behavior
App crashes in vulkan_1.dll
Logs / Screenshots
Application event log error:
Faulting application name: cube_handle_d3d12_win.exe, version: 1.0.0.0, time stamp: 0x69c63992
Faulting module name: vulkan-1.dll, version: 1.3.280.0, time stamp: 0x65fafbea
Exception code: 0xc0000005
Fault offset: 0x000000000003c0fa
Faulting process id: 0xA31C
Faulting application start time: 0x1DCBDCD897199D9
Faulting application path: D:\Google\Downloads\TestApps-472\CubeHandleD3D12\cube_handle_d3d12_win.exe
Faulting module path: C:\WINDOWS\SYSTEM32\vulkan-1.dll
Report Id: 925e286c-eddf-4dd0-82d1-b8a8c425cae3
Faulting package full name:
Faulting package-relative application ID:
By disabling FPS Monitor in registry, apps work again.

C:\Program Files (x86)\FPS Monitor\tools\fpsmonvk64.json
Note:
This is probably not a bug in displayXR, but it might occur at customer installations.
Build Environment
Windows 11, NVIDIA GeForce RTX 3060,
LeiaSR-Runtime 1.34.12+
DisplayXR 25.1.0.472
Steps to Reproduce
Expected Behavior
App starts normally
Actual Behavior
App crashes in vulkan_1.dll
Logs / Screenshots
Application event log error:
Faulting application name: cube_handle_d3d12_win.exe, version: 1.0.0.0, time stamp: 0x69c63992
Faulting module name: vulkan-1.dll, version: 1.3.280.0, time stamp: 0x65fafbea
Exception code: 0xc0000005
Fault offset: 0x000000000003c0fa
Faulting process id: 0xA31C
Faulting application start time: 0x1DCBDCD897199D9
Faulting application path: D:\Google\Downloads\TestApps-472\CubeHandleD3D12\cube_handle_d3d12_win.exe
Faulting module path: C:\WINDOWS\SYSTEM32\vulkan-1.dll
Report Id: 925e286c-eddf-4dd0-82d1-b8a8c425cae3
Faulting package full name:
Faulting package-relative application ID:
By disabling FPS Monitor in registry, apps work again.

C:\Program Files (x86)\FPS Monitor\tools\fpsmonvk64.json
Note:
This is probably not a bug in displayXR, but it might occur at customer installations.