DxDiag Explained: How the DirectX Diagnostic Tool Works in Windows
QUICK ANSWER DxDiag, short for DirectX Diagnostic Tool, is a built-in Windows utility that collects information about Windows, DirectX, graphics adapters, di...
QUICK ANSWER
DxDiag, short for DirectX Diagnostic Tool, is a built-in Windows utility that collects information about Windows, DirectX, graphics adapters, displays, sound devices, input devices and their drivers. Open it by pressing Windows + R, entering dxdiag, and selecting OK.
DxDiag helps identify hardware, driver and DirectX compatibility information, but it does not repair problems, benchmark performance or prove that hardware is healthy. Use its findings to decide whether Windows, a driver, an application or the hardware requires further investigation.
What is DxDiag?
DxDiag (dxdiag.exe) is a Microsoft diagnostic utility included with Windows. Its primary purpose is to collect information that can help diagnose DirectX-related video and sound problems.
DirectX is a collection of Windows components and application programming interfaces used by games and multimedia applications to communicate with graphics, audio and input hardware. DxDiag provides a readable summary of this environment.
It can report information such as:
- Windows version and build
- Computer manufacturer and model
- BIOS or UEFI information
- Processor and installed memory
- Installed DirectX version
- Graphics adapters and connected displays
- Display resolution and refresh rate
- Graphics memory figures reported by Windows
- DirectX feature levels supported by the graphics driver
- Graphics and audio driver names, versions and dates
- Windows Display Driver Model information
- Sound playback and recording devices
- DirectInput devices
- Diagnostic notes and reported problems
DxDiag normally runs without administrator rights. Administrative permission may be required for any corrective action performed afterward, such as changing protected settings, installing drivers or rolling back a driver.
When should you use DxDiag?
DxDiag is useful when:
- A game will not start or reports a DirectX error.
- A game or multimedia application crashes, freezes or displays graphical corruption.
- Windows shows an unexpected graphics adapter.
- Sound is missing, distorted or using the wrong device.
- You need to identify a graphics or audio driver version.
- Software support requests a DxDiag report.
- You want to check the DirectX version installed in Windows.
- You need to compare a computer’s capabilities with an application’s requirements.
- A problem appeared after a Windows, graphics or audio driver update.
- A system has both integrated and dedicated graphics adapters.
What DxDiag cannot do
DxDiag is an information-gathering tool. It does not:
- Repair DirectX, Windows or drivers
- Update drivers
- Measure gaming performance or frame rates
- Stress-test the GPU, CPU or memory
- Monitor temperatures, power consumption or fan speeds
- Confirm that hardware is physically healthy
- Guarantee that a game or application will run
- Replace Event Viewer, Reliability Monitor, Device Manager or vendor-specific diagnostic tools
A clean DxDiag report means that the tool did not identify an obvious problem in the information it checked. It does not rule out intermittent failures, overheating, defective hardware, application bugs or problems that appear only under load.
How DxDiag works
When DxDiag starts, Windows gathers information from the operating system, DirectX components, installed drivers and detected devices. It then organizes the results into tabs.
The available tabs can vary depending on the Windows version and installed hardware. Systems with multiple graphics adapters or audio devices may display additional tabs.
DxDiag primarily reads and reports system information. Simply opening the tool does not change drivers, DirectX settings or hardware configuration.
The first time it runs, DxDiag may ask whether it should check if drivers are digitally signed. Microsoft recommends allowing this check. A signed driver has a verifiable publisher signature, but the signature alone does not guarantee that the driver is current, error-free or suitable for every application.
How to open DxDiag
Method 1: Use the Run dialog
- Press
Windows + R. - Enter:
dxdiag
- Select OK or press
Enter. - Wait for the progress indicator to finish collecting information.
Method 2: Use Windows Search
- Open Start or Windows Search.
- Enter
dxdiag. - Select dxdiag or DirectX Diagnostic Tool.
Method 3: Use Command Prompt or PowerShell
Open Command Prompt, PowerShell or Windows Terminal and run:
dxdiag
You do not normally need to open the terminal as an administrator.
Understanding the DxDiag tabs
System tab
The System tab provides an overview of the computer and Windows installation.
| Field | What it means |
|---|---|
| Current Date/Time | System date and time when DxDiag was run |
| Computer Name | Windows device name |
| Operating System | Windows edition, build and architecture |
| Language | Windows language and regional setting |
| System Manufacturer | PC or motherboard manufacturer reported by firmware |
| System Model | Manufacturer’s model identifier |
| BIOS | BIOS or UEFI version information |
| Processor | Detected CPU model and logical processor information |
| Memory | Installed system memory |
| Page File | Current paging-file usage information |
| DirectX Version | Highest DirectX runtime version reported by Windows |
Important DirectX version limitation
The DirectX Version field does not by itself confirm that a graphics card supports every feature of that DirectX generation.
For example, Windows may report DirectX 12 while the installed GPU supports only certain Direct3D feature levels. Application compatibility depends on several factors:
- Windows version
- Graphics hardware
- Graphics driver
- DirectX feature level required by the application
- Other application-specific hardware requirements
Check both DirectX Version on the System tab and Feature Levels on the appropriate Display or Render tab.
Display and Render tabs
These tabs describe graphics adapters, displays and graphics drivers. A computer may show several tabs when it has integrated graphics, a dedicated GPU, multiple displays or special rendering devices.
Common fields include:
| Field | What it tells you |
|---|---|
| Name | Graphics adapter detected by Windows |
| Manufacturer | GPU or adapter manufacturer |
| Chip Type | Graphics chipset information reported by the driver |
| Display Memory | Memory figure available for display-related use |
| Dedicated Memory | Memory assigned specifically to the graphics adapter |
| Shared Memory | System memory that Windows may make available to graphics |
| Current Display Mode | Active resolution, colour format and refresh rate |
| Monitor | Detected monitor name or generic monitor description |
| HDR | HDR capability or status where reported |
| Driver Name | Graphics driver files in use |
| Driver Version | Installed graphics driver version |
| Driver Date | Date embedded in or reported for the driver package |
| WHQL Logo’d | Whether applicable signature testing information is reported |
| Direct3D DDI | Driver interface level used for Direct3D |
| Feature Levels | Direct3D hardware feature levels exposed by the driver |
| Driver Model | Windows Display Driver Model version |
| Notes | Problems identified by DxDiag |
DirectX version versus feature levels
These values answer different questions:
- DirectX Version describes the DirectX runtime available in Windows.
- Feature Levels describe the Direct3D capabilities made available by the particular graphics hardware and driver.
If a game requires a specific feature level, such as 12_0, seeing “DirectX 12” on the System tab is not enough. The required value must appear in the Feature Levels list for the GPU that will run the application.
Feature-level names are technical compatibility indicators, not performance ratings. Two GPUs supporting the same feature level may deliver very different performance.
Dedicated and shared graphics memory
Do not add every displayed memory value and assume the result is physical video RAM.
- Dedicated memory is memory reserved for or physically present on the graphics adapter, depending on the hardware design.
- Shared memory is system RAM that Windows may allow the GPU to use.
- Display Memory may be a calculated total rather than the amount of physical memory installed on the graphics card.
For an exact hardware specification, compare the results with the PC or graphics-card manufacturer’s official documentation.
Sound tabs
Each Sound tab represents an audio playback or recording device detected by Windows. Multiple tabs are normal when a PC has speakers, HDMI or DisplayPort audio, Bluetooth audio, a headset, a USB audio device or virtual audio software.
Useful fields include:
- Device name
- Hardware identifier
- Default-device status
- Driver provider
- Driver file
- Driver version and date
- Driver signature status
- Diagnostic notes
An HDMI or DisplayPort sound device is commonly associated with the graphics adapter because those connections can carry audio as well as video.
DxDiag can confirm which audio devices and drivers Windows detects, but it does not test speaker wiring, microphone quality, volume settings or physical device failure.
Input tab
The Input tab lists devices and components associated with DirectInput and other input paths. Depending on the system, it may include:
- Keyboard
- Mouse
- Game controllers
- Joysticks
- Steering wheels
- USB input devices
- Human Interface Devices
- Related driver components
A listed device is not necessarily the device currently selected inside a game. Controller mappings, application settings and support for newer input APIs may require separate investigation.
What to check first in DxDiag
For efficient troubleshooting, examine these areas:
- Notes: Look for a reported problem at the bottom of each relevant tab.
- Correct device: Confirm that Windows detects the expected graphics or audio hardware.
- Driver version and date: Compare them with the PC or component manufacturer’s supported driver.
- Feature Levels: Verify that the required Direct3D feature level is present.
- Current Display Mode: Confirm the expected resolution and refresh rate.
- Multiple adapters: Check every Display or Render tab on hybrid-graphics systems.
- Sound devices: Confirm that the intended playback or recording device appears.
- Operating-system build: Confirm that Windows is current and supported.
Do not treat an old-looking driver date as proof that the driver is obsolete. Driver dates can reflect the package’s metadata and should be assessed together with the complete driver version.
How to save a DxDiag report
A support technician or software vendor may request the complete report.
- Open DxDiag.
- Wait until information collection finishes.
- Select Save All Information.
- Choose a secure location.
- Enter a suitable filename, such as
DxDiag.txt. - Select Save.
- Review the file before sharing it.
The saved text report normally contains more detail than is visible on the first screen, making it useful for remote support and issue escalation.
Privacy warning before sharing
A DxDiag report is not a password dump, but it can contain information you may not want to publish openly, including:
- Computer name
- Windows version and build
- Hardware manufacturer and model
- Device names and identifiers
- Driver versions and file paths
- Connected peripherals
- Display and audio configuration
Review the complete report before sending it. Share it only with a trusted support channel and remove information that is unnecessary for the case. Avoid posting an unreviewed report on a public forum.
Do not edit technical fields requested by legitimate support unless you clearly tell the recipient what was removed. Missing hardware or driver information can make diagnosis more difficult.
How to use DxDiag results to troubleshoot problems
Graphics problems or game crashes
- Open the appropriate Display or Render tab.
- Check Notes for reported problems.
- Confirm that the expected GPU appears.
- Check whether the application’s required feature level is listed.
- Record the complete driver version.
- Install available Windows updates.
- If necessary, obtain a compatible driver from Windows Update, the PC manufacturer or the GPU manufacturer.
- Restart Windows and run DxDiag again.
- Test the affected application.
On laptops and manufacturer-customized systems, the PC manufacturer may provide a validated graphics driver designed for that device. Check its support guidance before replacing it with a generic driver.
Missing or distorted sound
- Review every Sound tab.
- Confirm that the expected playback or recording device is detected.
- Check the driver provider, version and Notes section.
- Verify the selected output device in Settings > System > Sound.
- Reconnect USB, HDMI, DisplayPort or Bluetooth devices as applicable.
- Install Windows and supported driver updates.
- Restart and test again.
A clean Sound tab does not confirm that the correct output device, volume level or application audio setting is selected.
DirectX errors
If an application reports that DirectX is missing or unsupported:
- Check the DirectX version on the System tab.
- Check Feature Levels on the GPU’s Display or Render tab.
- Compare both with the application’s official requirements.
- Install applicable Windows updates.
- Update the graphics driver from an approved source.
- Repair or reinstall the affected application if its own runtime components are damaged.
- Contact the software vendor if the hardware and software meet its published requirements.
On current Windows versions, DirectX components are serviced primarily through Windows Update. Do not download unofficial “DirectX repair” utilities or DLL files from third-party websites.
Updating Windows, DirectX and drivers safely
Update Windows
In Windows 11:
- Open Settings.
- Select Windows Update.
- Select Check for updates.
- Install applicable updates.
- Restart if requested.
Microsoft states that Windows 10 and Windows 11 already include their latest supported DirectX version, with updates delivered through Windows Update. Hardware limitations can still prevent support for particular DirectX features.
Support notice: Free Windows 10 software updates and security fixes ended on October 14, 2025, except where an applicable extended-support option is in use. For normal ongoing support and security updates, use a supported Windows release.
Update a graphics or audio driver
Use these sources in order of suitability:
- Windows Update
- Optional driver updates offered through Windows Update
- The PC manufacturer’s support site
- The hardware manufacturer’s official site, when appropriate
Avoid driver-download aggregators and unofficial update utilities. They may supply incorrect, modified or unwanted software.
Administrator permission is generally required to install, uninstall or roll back device drivers. In managed environments, follow organizational change-control and driver-deployment policies.
Common DxDiag problems
DxDiag takes a long time to open
Allow the initial scan to finish. Delays can occur while Windows queries devices and drivers.
If it never completes:
- Disconnect nonessential external audio, display or input devices.
- Restart Windows.
- Install pending Windows updates.
- Check Device Manager for devices with warning symbols.
- Try DxDiag again.
- Investigate recently installed or malfunctioning drivers if the problem continues.
A graphics card is missing
Possible causes include:
- The device is disabled in Device Manager or firmware.
- The driver is missing or damaged.
- The computer uses hybrid graphics and reports adapters separately.
- The hardware is disconnected or has failed.
- A remote or virtual session is presenting a virtual display adapter.
Check all Display and Render tabs, Device Manager, the computer manufacturer’s firmware settings and the official driver package.
DirectX shows a newer version than a game supports
A newer DirectX runtime does not automatically make an older game incompatible. Windows can support multiple DirectX-related interfaces and application components.
Older games may still require legacy runtime components installed by the game’s official installer. Use only Microsoft or the software publisher’s official installation method.
DxDiag reports no problems, but the application still fails
The problem may exist outside DxDiag’s scope, including:
- Corrupted application files
- Unsupported application settings
- Insufficient GPU performance or memory
- Overheating
- Unstable overclocking
- Hardware failure under load
- Security software interference
- Missing application-specific components
- A game or application defect
Use the application’s logs, Event Viewer, Reliability Monitor, hardware diagnostics and vendor support procedures for further investigation.
Benefits of DxDiag
DxDiag provides several practical benefits:
- It is built into Windows and requires no third-party download.
- It quickly creates a consistent hardware and driver inventory.
- It helps distinguish the installed DirectX runtime from GPU feature support.
- It identifies multiple graphics and audio devices.
- It records exact driver versions for comparison or escalation.
- It produces a portable text report for remote troubleshooting.
- It does not perform a stress test or make configuration changes simply by running.
- It is useful to beginners while still providing valuable technical detail for support teams.
Limitations and alternatives
Use another Windows tool when DxDiag does not provide the required information.
| Requirement | More suitable tool |
|---|---|
| Manage, update or roll back drivers | Device Manager or Windows Update |
| View detailed hardware inventory | System Information (msinfo32) |
| Review application and driver errors | Event Viewer |
| Check crash and reliability history | Reliability Monitor |
| Observe CPU, memory, disk or GPU activity | Task Manager or Performance Monitor |
| Test memory | Windows Memory Diagnostic or manufacturer diagnostics |
| Monitor temperature and fan data | Manufacturer-supported hardware utility |
| Repair protected Windows system files | Supported Windows servicing tools |
| Benchmark graphics performance | A reputable benchmark supported by the hardware or application vendor |
DxDiag is most effective as the first diagnostic snapshot, followed by a more specialized tool based on what the report reveals.
FAQ
Frequently asked questions
Is DxDiag safe to run?
Yes. DxDiag is a built-in Microsoft utility that primarily reads and displays diagnostic information. Opening it does not update drivers or alter DirectX settings.
Does DxDiag require administrator rights?
Normally, no. A standard user can generally open the tool and save a report. Installing, uninstalling or rolling back drivers afterward may require administrator permission.
Does DxDiag repair DirectX problems?
No. It reports system, device and driver information. Use Windows Update, supported driver packages, application repair options or other troubleshooting tools to correct identified problems.
Why does DxDiag show DirectX 12 when my game says the GPU is unsupported?
The DirectX 12 entry describes the runtime available in Windows. The game may require a Direct3D feature level or hardware capability that the GPU or its current driver does not expose. Check the Feature Levels field on the relevant graphics tab.
Can DxDiag tell me how much VRAM my graphics card has?
It reports dedicated, shared and total display-memory figures supplied by Windows and the driver. These values require careful interpretation, especially with integrated graphics. Confirm physical VRAM against the manufacturer’s specifications.
Why are there multiple Display or Sound tabs?
Windows creates separate tabs for detected adapters or devices. Multiple tabs are common on hybrid-graphics laptops and systems using HDMI audio, Bluetooth devices, USB audio or several monitors.
Is a digitally signed driver always the best driver?
No. A valid signature helps verify the publisher and driver integrity, but it does not prove that the driver is current, compatible with every application or free from defects.
Is a DxDiag report safe to post publicly?
Review it first. The report can contain the computer name, device details, driver versions and connected hardware. Prefer sharing it privately with a trusted support provider and remove unnecessary identifying information.
Can DxDiag test whether a graphics card is failing?
No. It may expose driver or device-detection problems, but it does not stress-test the GPU or prove that the hardware is healthy. Use manufacturer diagnostics and appropriate hardware testing when failure is suspected.
FINAL RECOMMENDATION / CONCLUSION
Use DxDiag as the first step when diagnosing DirectX, graphics, sound or game-compatibility problems in Windows. Check the Notes sections, device names, driver versions and Direct3D feature levels, then save a report if technical support needs a complete snapshot.
Treat the results as diagnostic evidence rather than a repair or hardware-health verdict. Apply updates through Windows Update or official manufacturer sources, avoid third-party driver and DLL download sites, and review every DxDiag report before sharing it.
#DxDiag #DirectX #Windows11 #Windows10 #WindowsDiagnostics #GraphicsCard #GPU #GraphicsDriver #AudioDriver #DirectX12 #FeatureLevels #GamingSupport #DriverTroubleshooting #DisplayProblems #SoundProblems #ITSupport #WindowsTools #TechnicalSupport #SystemInformation #Knowledgebase
SOURCES
Was this guide useful?
Your answer helps us keep BISONKB accurate and practical.