[GUIDE] - How to Read a DxDiag

Publication Date: 2025-04-02T16:22:15+01:00

For now placing this guide in the EA Community Discussion Subforum as there currently is no Community Resources section.

In this guide, I’ll cover the main sections of a DxDiag, focusing on the most important details for troubleshooting, along with tips to keep in mind.

Before the switch from AHQ to the new EA Forums, a similar thread existed, but unfortunately, it didn’t carry over. However, I found an archived version of the old thread here: [Internet Archive] - (AHQ Community Resources) How to read a DXDiag 

The original thread, created in 2014, was maintained until the forum change. In this updated version, I’ve expanded the coverage while omitting outdated info (e.g., SLI/Crossfire, Service Packs).

This guide assumes basic knowledge of Windows, software, and hardware. It serves as an introduction to troubleshooting with a DxDiag, though keep in mind that it may not always provide a clear solution.
This guide is based on a DxDiag from Windows 10 (DxDiag Version: 10.00.19041.5438 64bit Unicode) and may differ on Windows 11.

The guide follows the same order as the sections within a DxDiag.

If you notice any missing or incorrect information, or have suggestions for improvements, feel free to leave a comment, and I’ll review it when I can.

Table of Contents

Excluded Sections

>> Click here to go back to the Table of Contents <<

There are several sections in the DxDiag report that will not be covered in this guide. These sections are either outdated, legacy features, or not directly relevant to most troubleshooting scenarios. The table below outlines these sections and the reasons they are excluded:

Figure 1 (Overview of DxDiag Sections and Their Relevance for Troubleshooting)

System Information

>> Click here to go back to the Table of Contents <<

Figure 2 (DxDiag - System Information)

This section provides various details about your computer that can be useful for troubleshooting.
Key information includes:

• Operating System: Specifies the OS and its version.
• System Model: Information about the motherboard and overall system.
• BIOS: Displays the BIOS version.
• Processor: Details about the CPU.
• Memory: The total installed RAM.
• Page File: More on this below.
• Windows Directory: The location where Windows is installed.
• DirectX Version: The highest version of DirectX supported.
• DPI Settings: Details about screen scaling.

These entries are often the most relevant when diagnosing issues.
To troubleshoot effectively:

1. Compare System Specs with Game Requirements: Check the system specifications against the minimum and recommended specs for the game you're troubleshooting. If the system falls short of these specs, it could explain the issues being experienced.
2. BIOS Version: Ensure that the BIOS is up to date for your specific motherboard model. BIOS updates are typically released only when necessary, such as for system stability improvements, addressing hardware compatibility, or fixing issues like incorrect voltage delivery.
3. Page File: A correctly configured page file is critical, especially for systems with limited RAM. The page file acts as virtual memory, storing inactive data from RAM onto your storage device (e.g., HDD or SSD) to free up more RAM. Proper configuration is especially important if your system has a small amount of physical RAM. For guidance on the appropriate page file size, refer to this article: [Learn.Microsoft] - How to determine the appropriate page file size for 64-bit versions of Windows.
4. DirectX Version: The version of DirectX is crucial for gaming performance. Newer games may require DirectX 12 instead of DirectX 11. For example, Apex Legends has begun phasing out DirectX 11 in favor of DirectX 12. However, the version of DirectX is just one factor—some games require specific DirectX feature levels, which we will cover in the Display Devices section.
5. DPI Settings: DPI settings control how your screen content scales. A setting other than 96 DPI (100%)  can cause text to appear misaligned or even prevent some games from launching properly. For more information on DPI scaling, refer to [Learn.Microsoft] - DPI and device-independent pixels.

DxDiag Notes

>> Click here to go back to the Table of Contents <<

Figure 3 (DxDiag - DxDiag Notes)

One of the key features of DxDiag is its ability to flag issues such as unsigned drivers. These flags indicate that the drivers may be unstable, potentially due to being in beta or corrupted. Here’s an example of how such issues might appear in the DxDiag report:

  DirectX Files Tab: No problems found. 
      Display Tab 1: The file ialmrnt5.dll is not digitally signed, which means that it has not been tested by Microsoft's Windows Hardware Quality Labs (WHQL).  You may be able to get a WHQL logo'd driver from the hardware manufacturer. 
        Sound Tab 1: The file RtkHDAud.sys is not digitally signed, which means that it has not been tested by Microsoft's Windows Hardware Quality Labs (WHQL).  You may be able to get a WHQL logo'd driver from the hardware manufacturer. 
          Music Tab: No problems found. 
          Input Tab: No problems found. 
        Network Tab: No problems found. 

Source: https://forum.multitheftauto.com/topic/60173-mta-crash-dxdiag-included/

In addition to identifying unsigned drivers, DxDiag can also detect other types of issues. Below are a few examples of how this may appear:

I am not aware of an exhaustive list of all items that will be caught under the DxDiag Notes section, though any problems detected under this section will typically be detailed enough to guide you through further troubleshooting steps.

Display Devices

>> Click here to go back to the Table of Contents <<

Figure 4 (DxDiag - Display Devices)

This section provides details about the monitors connected to your system and the associated display settings.
Key information includes:

• Monitor Name
• Monitor Model
• Current Mode: The current resolution and refresh rate being supplied by the GPU to the monitor.
• Native Mode: The native resolution and refresh rate that the monitor supports.
• Driver Version: The version number of the GPU driver being used.
• Driver Date/Size: The release date and file size of the installed driver.
• WHQL Logo'd: Indicates whether the driver has passed WHQL testing.
• Display Memory: The total memory available for the display, including both dedicated and 
• shared memory.
• Dedicated Memory: The VRAM (Video RAM) physically available on the GPU itself.
• Shared Memory: The portion of system RAM allocated for use by the GPU.
• Output Type: The type of display connection in use (e.g., HDMI, DisplayPort).
• DDI Version: The DirectX Device Interface version supported by the GPU.
• Feature Levels: The DirectX feature levels supported by the GPU. This is important as some games may require specific feature levels to run properly.

If you have multiple monitors, then there will be a separate entry with all the corresponding information.

Key Checks

• Current Mode vs. Native Mode: Ensure the monitor is running at its native resolution and refresh rate. For example, if a 1440p monitor is running at 1080p, it may be due to the user forgetting to change their resolution. Similarly, check if the refresh rate is lower than what the monitor supports natively.
• Driver Version: It's important to check that the GPU driver is up to date. You can verify the driver version and check the Driver Date for the release date. Staying on the latest stable driver version is recommended, but it's important to be cautious of any issues with the most recent updates.
  • Note: Nvidia driver versions are usually shortened to the last 5 digits of the version with 2 decimal points. (This: 32.0.15.7242 Becomes: 572.42) This means that if you want to look up a Nvidia driver, you should look it up in that format.

Looking up a GPU Driver and checking if it needs updating

First off we’ll need to check the card to see if it’s from Nvidia, AMD or Intel. This can be found under the Manufacturer section for each entry under Display Devices.

Once you've figured it out, navigate to the corresponding section below.

Nvidia

1. Go to this site: https://www.nvidia.com/en-us/drivers/
2. Under Manual Driver Search, fill in the required specifications according to the information that is present in the DxDiag
3. Press “Find

Figure 5 (Nvidia Driver Search - Part 1)

4. Compare the Game Ready Driver version with the driver version present in the DxDiag, if it’s newer, then the driver should be updated

Figure 6 (Nvidia Driver Search - Part 2)

AMD

1. Go to this site: https://www.amd.com/en/support/download/drivers.html
2. Fill in the specifications from the DxDiag inside of the "Search or Browse Drivers and Support by Product” section
3. Press "Submit”

Figure 7 (AMD Driver Search - Part 1)

4. Select the correct Operating System
5. Compare the driver version with the driver version present in the DxDiag, if it’s newer, then the driver should be updated

Figure 8 (AMD Driver Search - Part 2 )

Intel

(You might not be able to find the corrrect Intel drivers via the steps below, you can find all Intel Graphics Drivers on this page:  [Intel] - Driver Search (Graphics) but do keep in mind that it also includes drivers for integrated chipsets)

1. Go to this site: [Intel] - Intel® Arc™ & Iris® Xe Graphics - Windows*
2. Compare the driver version with the driver version present in the DxDiag, if it’s newer, then the driver should be updated

Figure 9 (Intel Driver Search)

Sound Devices

>> Click here to go back to the Table of Contents <<

Figure 10 (DxDiag - Sound Devices)

The Sound Devices section lists all the devices used for audio playback, including headsets, speakers, or any other audio output devices.

This list corresponds to the devices found in Windows Settings > System > Sound > Sound Control Panel > Playback. It will also display Virtual Playback Devices. If you use software that creates virtual audio devices (e.g., Voicemod, Virtual Cable), these will appear in the list as well.

Each sound device contains several pieces of detailed information, but the following key details are most relevant:

• Description (The name of the sound device)
• Driver Name 
• Driver Version 
• Date and Size (The release date and file size of the driver)
• WHQL Logo’d (Indicates whether the driver has passed WHQL Testing and is certified by Microsoft)
• Default Sound Playback (Shows whether the device is set as the default audio output for Windows)

One of the key things to check here is whether your driver is up to date. Outdated drivers can mess with your audio, so keeping them current is a good way to avoid problems and make sure everything’s running smoothly.

If you're not hearing sound from the device you want, check the Default Sound Playback setting. If it says "Yes," that device should be the one Windows uses for audio. If it’s not working right, you can change it here, or sometimes in the settings of the app you’re using to play audio.

Sound Capture Devices

>> Click here to go back to the Table of Contents <<

Figure 11 (DxDiag - Sound Capture Devices)

The Sound Capture Devices section lists all devices used for capturing audio, such as microphones.

This list corresponds to the devices found in Windows Settings > System > Sound > Sound Control Panel > Recording. It will also include Virtual Microphones. If you use software that creates virtual audio devices (e.g., Voicemod, Virtual Cable), these virtual microphones will also appear in the list.

For each sound capture device, the following key details are provided:

• Description (The name of the sound capture device)
• Driver Name 
• Driver Version 
• Date and Size (The release date and file size of the driver)
• Default Voice Capture (Indicates whether the device is set as the default audio input device for Windows)

It’s important to check that the driver for the sound capture device is up to date, as outdated drivers can lead to performance issues or limited functionality.

Additionally, verify that the Default Voice Capture is set to ‘yes’ for the correct device. This ensures that Windows will use the intended device for audio input. However, some applications may allow you to select a specific microphone within the app itself, overriding the default Windows setting. If audio capture isn't working as expected, this could be the cause.

Video Capturing Devices

>> Click here to go back to the Table of Contents <<

Figure 12 (DxDiag - Video Capture Devices)

The Video Capture Devices section lists any device used for capturing video, including webcams and capture cards.
Key information to focus on includes:

• FriendlyName (The name of the Video Capture Device)
• Manufacturer 
• DriverVersion
• DriverDateEnglish
• Service (The service used to interact with the Video Capture Device)

When reviewing this section, it's crucial to check if the driver is up to date. Outdated drivers can lead to issues with video capture functionality.

USB Devices

>> Click here to go back to the Table of Contents <<

Figure 13 (DxDiag - USB Devices)

The USB Devices section provides a hierarchical view of all USB devices connected to the system, similar to what you’d see in Device Manager.

For each USB device, the following information is displayed:

• Vendor/Product ID (These IDs can be used to identify the USB device, which can be looked up in the USB ID Database - [the sz development] 
• Matching Device ID (This ID is used by the Plug and Play (PnP) manager to locate a driver package that matches the device. For more information, refer to [Learn.Microsoft] - Device Identification Strings 
• Service (The service used by Windows to interface with the device)
• Driver (This includes the driver file name, the date and time of the driver, and the file size of the driver)

(Some will also include a “Location:” tag, this will not be covered in this guide)

This list can be valuable for troubleshooting, especially when identifying hardware-related issues. In some cases, anti-cheat systems may flag Removable Storage devices, preventing the game from booting up. This is why it may be good to check this list if you are aware of certain USB Hardware causing issues within a game

PS/2 Devices

>> Click here to go back to the Table of Contents <<

Figure 14 (DxDiag - PS/2 Devices)

Note: This is considered legacy technology. While it’s generally not relevant for most users today, it may still be important in certain troubleshooting scenarios, which is why it is included here.

In some cases, PS/2 Devices may appear in a DxDiag report even when no PS/2 device is physically connected. This could be due to hardware or software quirks during the DxDiag capture process, so don’t assume that a device listed in this section is actually connected. If you do need to troubleshoot PS/2 devices, make sure to confirm that the user has a device actually connected via the PS/2 port.

PS/2 devices typically refer to input devices like keyboards and mice connected via the PS/2 port, as shown below:

Figure 15 (PS/2 Ports) Sourced From Wikipedia: https://en.wikipedia.org/wiki/PS/2_port

While PS/2 used to be more common, USB has largely replaced it for these devices. As such, PS/2 should be considered legacy technology. If a user is still relying on PS/2 devices, it’s generally recommended to switch to USB unless they have a specific reason for using PS/2.

Here are some important considerations:

• PS/2 devices are not hot-pluggable: These devices need to be connected before booting up the computer. They will not work if plugged in after the system has already started.
• Potential instability: PS/2 communication with Windows can sometimes cause generic instability, particularly if there are compatibility issues.
• BIOS/UEFI support: Not all BIOS or UEFI firmware versions support PS/2 devices. It’s important to verify that the system’s firmware can recognize PS/2 if troubleshooting these devices.

Given these limitations, if PS/2 devices are malfunctioning, it’s often better to recommend switching to USB devices to avoid dealing with potential hardware or compatibility issues.

Disk & DVD/CD-ROM Drives

>> Click here to go back to the Table of Contents <<

Figure 16 (DxDiag - Disk & DVD/CD-ROM Drives)

In addition to providing details on your system’s storage, the DxDiag tool will also display information about your DVD/CD-ROM drives and their associated drivers.

For each drive, the following information is provided:

• Free Space
• Total Space
• File System
• Model

The most critical piece of information to focus on is the Free Space of the drive where Windows is installed. If this drive doesn’t have enough available space, it can significantly impact system performance and lead to instability. To maintain optimal performance, I would recommended to keep at least 15-20% of free space on the drive where Windows is installed.

Additionally, it's worth checking the model of the drive used for both your Windows installation and game storage. If you notice that the storage device is outdated and has exceeded its typical life expectancy or its read/write capacity, this could lead to performance degradation or potential failure
For a more thorough analysis of your drives, you might consider using [Crystalmark] - CrystalDiskInfo. This tool provides detailed health information about your storage devices, helping you identify potential issues like failing drives before they cause significant problems.

System Devices

>> Click here to go back to the Table of Contents <<

Figure 17 (DxDiag - System Devices)

This section lists all devices connected to the motherboard.
These devices can include:

• Controllers  (e.g., Audio Controller, SATA Controller, Ethernet Controller)
• PCIe Devices  (e.g., GPU, Wi-Fi Card, Ethernet Card, Sound Card, USB Card, etc.)
• And many other hardware components (Note: A full list of every possible device type would be too extensive for this guide.) 

Each entry will include the following information:

• Name: The device's name or description.
• Device ID: A unique identifier that can help you locate more details about the device, especially if the name proves insufficient.
• Driver: Details about the device's driver, including its location, version, release date, and size.

Locating Information Using the Device ID

The Device ID is a key piece of information. If the device name doesn’t provide enough detail, you can use the Device ID to look it up.
To search the Device ID:

1. Copy the Device ID (e.g., `PCI\VEN_10DE&DEV_24C9&SUBSYS_88AE1043&REV_A1\4&8BD6E8D&0&0008`).
2. Identify the Vendor ID and Device ID:
   • Vendor ID: `VEN_10DE`
   • Device ID: `DEV_24C9`
3. Visit the following website and search with the PCI type:
   • [DeviceHunt] - Search by PCI 

A repository of all PCI ID’s can also be found here for those interested: https://pci-ids.ucw.cz/ 

Diagnostics

>> Click here to go back to the Table of Contents <<

Figure 18 (DxDiag - Diagnostics)

The Diagnostics section in the DxDiag lists the 10 most recent application errors reported through Windows Error Reporting (WER). To view older WER entries, you'll need to check the Event Viewer.

Important: An entry in this list does not necessarily indicate a direct cause for the issue you're troubleshooting. Especially with unrelated applications, the error might have occurred at a different time or may not be relevant at all.

Each WER entry includes the following data:

• Fault bucket: A unique identifier generated by Windows based on the error's context.
• Fault bucket Type: A type differentiator (more information here).
• Event Name: The type of crash (I have yet to find a exhaustive list of event names).
• Response: Not covered in this guide.
• Cab ID: Not covered in this guide.
• Problem Signature: More details below.

The Problem Signature section contains various columns (denoted as "P" + numbers 1-10) that provide specifics about the crash. Though there’s no official mapping standard for these columns, here's a breakdown of what you might encounter:

• AppName: The application's EXE filename (e.g., "Explorer.exe").
• AppVer: The version number of the application or assembly.
• AppStamp: The timestamp of the executable.
• AsmAndModName: The name of the assembly/module if it’s part of a multi-module assembly.
• AsmVer: The version of the faulting managed assembly.
• ModStamp: The timestamp of the faulting module.
• MethodDef: The token for the faulting method.
• Offset: The IL offset for the faulting instruction.
• ExceptionType: The name of the exception type, with "Exception" removed (e.g., "System.AccessViolation").

Sourced from: [Learn.Microsoft] - Windows Error Reporting and CLR Integration

Note: The specific information in WER entries may vary depending on how the application integrates with WER.

Not all WER data will be visible in the DxDiag. For more comprehensive details, including crash dump files, check the Event Viewer or the full WER report.
I may create a more in-depth guide on Event Viewer and WER in the future for more in-depth troubleshooting.