- 2012/01/24: Error code 0x80AA001D after switching to the pipeline view
- This is caused by a recently-discovered bug in PIX concerning shader model 6.6. We will release an update soon.
- You can work around this issue by compiling with -O1 (or higher) instead of -Od.
In general we recommend using the latest available driver for your GPU. In the future, we will update this page with any exceptions to this guidance.
Issue: errors collecting GPU counters on NVIDIA driver 471.11
Fix: None available as yet.
Problem: On NVIDIA, the driver may crash when collecting counters such as “Wave Distribution” or “PCIe Bandwidth”.
- In GPU Captures, you may see a “WinPixEngineHost.exe has stopped working” dialog from Windows, followed by a “The PIX engine has terminated” dialog from PIX itself.
Currently, there is no workaround. NVIDIA has been informed of the problem, and we expect a fix soon.
Issue: errors collecting GPU timing data on NVIDIA
Fix: Update to NVIDIA driver 466.11 or newer.
Problem: On NVIDIA, some users may hit problems collecting timing data. 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.
If you must use an older driver, 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.
Issue: application hangs while running under GPU Capture
Workaround: avoid connecting/disconnecting via remote desktop.
Problem: the only known issue here happens if you are running your application under GPU Capture on a device, and you connect and/or disconnect to that device via remote desktop.
Issue: crash on AMD while collecting High Frequency Counters
Problem: On AMD, collecting High Frequency Counters will fail and/or crash after collecting Debug Layer Warnings in PIX. AMD are working on a fix.
Cannot capture application on a system using only Microsoft Basic Display GPU
Workaround: This can be fixed by installing a device driver for the GPU hardware present on your system.
Problem: PIX will fail to capture an application on a system that has defaulted to the ‘Microsoft Basic Display Adapter’ as the only supported GPU.