{"id":4261,"date":"2019-03-13T11:10:42","date_gmt":"2019-03-13T18:10:42","guid":{"rendered":"http:\/\/devblogs.microsoft.com\/pix\/?page_id=4261"},"modified":"2025-10-21T11:40:50","modified_gmt":"2025-10-21T18:40:50","slug":"known-issues","status":"publish","type":"page","link":"https:\/\/devblogs.microsoft.com\/pix\/known-issues\/","title":{"rendered":"Known Issues"},"content":{"rendered":"

If you are hitting a problem that isn’t listed below, then please contact us via the “Send Feedback’ button in the top-right corner of the PIX UI, or chat with us on the #pix channel on the DirectX Discord.<\/a><\/p>\n

 <\/p>\n

PIX Issues<\/h2>\n

Issue: while starting analysis, PIX hits an error saying “D3D12EnableExperimentalFeatures failed during analysis”<\/h3>\n

Status:<\/strong> Fixed, please download and install PIX 2509.25 or later from the downloads<\/a> page.<\/p>\n

Explanation: <\/strong>Windows 11 update KB5065789, initially releasing as a preview in late Sept 2025, updates the system32 copy of D3D12Core.dll to be roughly the same as DirectX Agility SDK 616.1. That new Agility SDK introduced a breaking change to the D3D12EnableExperimentalFeatures() API: it is no longer valid to call that API in a non-preview Agility SDK. Unfortunately PIX builds prior to 2509.25 unconditionally try to turn on some experimental features, so they hit errors after KB5065789 is installed. This is fixed in PIX 2509.25 and later.<\/p>\n

<\/h3>\n

Issue: app crashes when trying to launch it for PIX GPU Capture<\/h3>\n

Status:<\/strong> Fixed in PIX 2408.05 or later.<\/p>\n

Explanation:\u00a0<\/strong>The MSVC team introduced a breaking change<\/a> to the MSVC libraries related to std::mutex’s destructor. If you are seeing crashes at capture time in this area then this issue is likely to be the cause.<\/p>\n

 <\/p>\n

Issue: playback output (e.g. backbuffer contents) doesn’t match capture-time output<\/h3>\n

Status:<\/strong> Active \u26a0\ufe0f (has workaround for a lot of cases)<\/p>\n

Explanation:\u00a0<\/strong>This is commonly caused by ExecuteIndirect non-determinism. By default, PIX will snap a copy of your capture-time ExecuteIndirect argument buffers and use those to perform your ExecuteIndirects at replay time. This works for older applications, but in recent years it has started causing problems for applications that generate their argument buffers non-deterministically (e.g. during a GPU culling pass). It’s particularly problematic if the argument buffers are generated at the same time as other types of buffers and the application expects the buffers to be consistent with each other: at replay time, PIX will use the capture-time copy of the argument buffer but the replay-time copy of the other buffer, and bad things may happen.<\/p>\n

Workaround:<\/strong> Click Home->Settings in PIX, check the “Use replay-time ExecuteIndirect argument buffers (experimental)” box, and reopen your capture file.<\/p>\n

If you continue to hit problems after the setting this checkbox, then please contact us and we will be eager to investigate.<\/p>\n

 <\/p>\n

Issue: Race Condition when your application uses dbghelp.dll<\/h3>\n

Status:<\/strong> Active \u26a0\ufe0f<\/p>\n

Problem<\/strong>: Your application may hang\/crash if uses dbghelp.dll and is running under PIX GPU Capture. dbghelp.dll is not thread-safe, and so if both PIX and your application are trying to use it on different threads, sporadic errors or crashes can happen inside dbghelp.dll.<\/p>\n

Workaround<\/strong>: The only workaround is to avoid using dbghelp.dll altogether when PIX is attached<\/p>\n

 <\/p>\n

Issue: PIX doesn’t work on my HoloLens<\/h3>\n

Status:<\/strong> Active \u26a0\ufe0f (known cause has workaround)<\/p>\n

Workaround:\u00a0<\/strong>Please use PIX version 2308.30 with your HoloLens.<\/p>\n

 <\/p>\n

Driver Issues<\/h2>\n

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.<\/p>\n

 <\/p>\n

Issue: PIX fails to create D3D12 device on Qualcomm GPUs running some drivers<\/h3>\n

Status:<\/strong> Active \u26a0\ufe0f<\/p>\n

Workaround:<\/strong> create C:\\data\\test\\bin directory on the affected device<\/p>\n

 <\/p>\n

Issue: errors collecting timing data on Intel<\/h3>\n

Status:<\/strong> Active \u26a0\ufe0f (has workaround, Intel working on fix)<\/p>\n

Affected devices:<\/strong> Intel Lunar Lake GPUs running recent drivers with Hardware Scheduling enabled<\/p>\n

Problem<\/strong>: While collecting timing data in PIX, you may hit errors such as “Timing Data Error”, “ETW history buffer submissions weren’t received in chronological order<\/span>” or similar errors.<\/p>\n

Workaround:\u00a0<\/b>Disable Hardware-accelerated GPU scheduling in the Settings app on your PC, restart your PC, and launch PIX again.<\/p>\n

 <\/p>\n

Issue: errors collecting timing data on NVIDIA<\/h3>\n

Status:<\/strong> Active \u26a0\ufe0f (has workaround, NVIDIA working on fix)<\/p>\n

Affected devices:<\/strong> NVIDIA GPUs running recent drivers with Hardware Scheduling enabled<\/p>\n

Problem<\/strong>: While collecting timing data in PIX, you may hit errors such as “Timing Data Error”, “Not enough ETW passes were completed” or similar errors.<\/p>\n

Workaround:\u00a0<\/b>Disable Hardware-accelerated GPU scheduling in the Settings app on your PC, restart your PC, and launch PIX again.<\/p>\n

 <\/p>\n

Issue: error starting analysis on AMD (“PIX was unable to create a D3D12 device”)<\/h3>\n

Status:<\/strong> Active \u26a0\ufe0f (has workaround, AMD are working on a fix)<\/p>\n

Problem:<\/strong> There are at least two known causes for this issue:<\/p>\n

    \n
  1. If you have two AMD GPUs in your PC, both enabled, and you start analysis on the secondary GPU.\n