Windows 11 26H2 is set to introduce an essential tool aimed at solving a persistent problem for graphics card users: recurring graphics driver failures. The new feature seeks to put an end to the crashes that affect the experience of millions of players and professionals.
Microsoft develops an innovative feature called DirectX Dump Files, designed so that developers can actually understand the exact cause of GPU crashes as they occur. This initiative aims to significantly improve fault diagnosis.
The main focus is errors known as TDR, which stands for Timeout Detection and Recovery. This phenomenon manifests itself when the screen freezes, goes dark and returns with the warning that the driver has stopped responding and has been restarted, and the functionality covers hardware from AMD, NVIDIA and Intel.
Unraveling the mystery of graphics glitches with DirectX Dump Files
The concept behind the feature is similar to the dynamics of the system’s memory dump files, so-called *memory dumps*, which record the state of the machine in case of anomalies. However, in this case, the registry photographs the state of the video card in detail.
When a graphics crash occurs, whether due to a crash, image freeze or abrupt driver restart, the new functionality is activated to capture an accurate snapshot of the GPU’s execution at that moment.
The result of this capture is a file with the .dxdmp extension, containing detailed information about the component involved, the driver used, the operating system and the application that was affected by the incident.
Detailed information stored in .dxdmp files
The great advantage of this technology is the ability to consolidate, into a single file, information that is currently dispersed across multiple diagnostic tools. This eliminates the need for the developer to manually cross-reference records to identify the root of the failure.
The data dump process collects the state of the hardware, including register values, shader program counters, page fault addresses, and command buffers in use.
Along with this data, information from the DirectX layer and system kernel is included, covering D3D objects, pipeline states, graphics adapter details, and CPU call stacks. Developers can also attach up to 2 MB of application-specific data through new D3D12 APIs.
This technology was presented for the first time at GDC 2026 and its construction included the active participation of the three largest GPU manufacturers.
Microsoft described the feature as “a major advancement in debugging GPU crashes on Windows” when releasing the public preview on the DirectX development blog.
Understanding Different Levels of Data Capture
The system offers several collection methods, which establish a balance between the amount of data recorded and the impact on system performance. The choice of the ideal mode is made by the professional who develops the software.
- NO_OVERHEAD: Does not generate performance costs, being suitable for wide distribution and standard captures.
- MEDIUM_OVERHEAD: It has moderate performance cost and provides extra data for diagnosis.
- HIGH_OVERHEAD: It presents a high performance cost, ideal for in-depth investigations of drivers and the GPU itself.
On compatible hardware classified as Tier 2, cost-free mode is already enabled by default. In practice, this allows developers to receive useful diagnostics without having to modify any line of code.
However, the feature is only available as a preview, and there is an important caveat: so far, only AMD has a prepared driver, version 26.10.07.02 of the AgilitySDK Developer Preview. NVIDIA and Intel still need to make equivalent packages available for their devices.
The analysis of the generated files is carried out by PIX, Microsoft’s graphical debugging tool, which already supported the .dxdmp format in its preview version.
The official and broad launch of the technology is scheduled for the autumn period in the Northern Hemisphere, between September and November 2026, a window that coincides with the arrival of the new version of the Windows operating system.
The project was designed to serve two distinct fronts.
One of them is the collection of information about breakdowns directly from the end user’s computer, in a real-use environment.
The other front consists of supporting testing and development teams in investigating problems on the bench, before the game or program is made available to the public.
Failure history: the long fight against driver black screen
For the end consumer, the request for a definitive solution is not new. The failure that forces the driver to restart and causes the dreaded “black screen” is among the oldest complaints from those who use their PC for games or to work with heavy graphics, requiring a response for several generations of the operating system.
Microsoft had already been implementing improvements in this aspect; the WDDM 3.2 model, present in the 24H2 and 25H2 versions, brought specific advances in the treatment of these crashes. However, the technological layer capable of identifying the exact cause of the failure was missing, at which point the user remained without answers.
DirectX Dump Files are not an automatic fix for crashes, but they provide the investigative material that was missing. With standardized reporting across AMD, NVIDIA and Intel, Microsoft gives developers and hardware manufacturers the tools they need to turn a recurring complaint into an end-to-end trackable issue, directly impacting the end user experience.