In general we recommend using the latest available driver for your GPU.
Issues with GPU timing data
February 2021: Some users may hit problems collecting GPU timing data on Windows version 2004 or later. Examples of these problems include:
- In GPU Captures, you may hit errors while collecting timing data (example error message: “PIX encountered an error while collecting timing data”).
- In Timing Captures, your capture may not include GPU events even if you have “GPU timings” turned on.
These are caused by known issue that will be fixed in a future NVIDIA driver.
Until then, in most cases the issue can be resolved by disabling the “In-Game Overlay” in the “GeForce Experience” app, or by uninstalling “GeForce Experience”. On Pascal or earlier hardware, the problem may be resolved by disabling GPU plugins (uncheck Home -> Settings -> Enable GPU Plugins).
If these workarounds don’t work for you then please contact us through the “Send Feedback” button in PIX.
High Frequency Counters
We are working with each IHV to resolve these issues. Stay tuned for updates in future PIX releases.
- Collecting High Frequency Counters will fail and/or crash after collecting Debug Layer Warnings in PIX.
- No known issues
- No known issues
Cannot capture application on a system using only Microsoft Basic Display GPU
PIX will fail to capture an application on a system that has defaulted to the ‘Microsoft Basic Display Adapter’ as the only supported GPU. This can be fixed by installing a device driver for the GPU hardware present on your system.
HLSL variables in DXIL debugger
This issue was resolved in PIX-2003.26.
Due to a change in DXCompiler’s debug information, PIX does not report HLSL variables for any DXIL shader compiled with versions of DXCompiler that were built from github source as of November 13th, 2019. This includes DXIL shaders built by PIX 1911.27 as part of Shader Edit and Continue. The only reasonable workaround is to compile the shaders with an older version of DXCompiler. A fix for PIX will be forthcoming. This is the specific DXCompiler commit that introduced the newer debug information: https://github.com/microsoft/DirectXShaderCompiler/commit/f4965b71dd878c42c219ec00d31c406c483fd045