Nvidia-bug-report-dxdiag-hang.md

# dxdiag hangs indefinitely with /dontskip on driver 616.56 and 616.92 (RTX 5060 Ti) — breaks Call of Duty launch

## Summary

On an RTX 5060 Ti, `dxdiag.exe` invoked with the `/dontskip` flag hangs

indefinitely and never produces its output file. This happens on driver

versions **616.92** and **616.56**, and does **not** happen on **610.88**.

The hang is reproducible outside of any game. It breaks Call of Duty: Modern

Warfare II, whose Activision bootstrapper calls `dxdiag` with exactly those

flags during startup and waits for it to return — so the game sits forever on

the RICOCHET anti-cheat splash screen.

—

## System

| | |

|—|—|

| GPU | NVIDIA GeForce RTX 5060 Ti (8 GB) |

| CPU | AMD Ryzen 7 9700X |

| iGPU | AMD Radeon Graphics (integrated) |

| Motherboard | Gigabyte B650M AORUS ELITE AX ICE, BIOS F42b (2026-04-19) |

| RAM | 32 GB DDR5 (single module, running at 4800 MT/s) |

| PSU | Corsair CX750 |

| OS | Windows 11, build 26200.9457 |

| Secure Boot | Enabled |

—

## Reproduction

Run from an elevated PowerShell prompt:

```powershell

Remove-Item “$env:TEMP\test.txt” -Force -ErrorAction SilentlyContinue

dxdiag /dontskip /whql:off /t “$env:TEMP\test.txt”

Start-Sleep -Seconds 45

Test-Path “$env:TEMP\test.txt”

Get-Process dxdiag -ErrorAction SilentlyContinue | Select-Object Name, CPU

```

### Results by driver version

| Driver | `/dontskip` present | Output file created | dxdiag exits |

|—|—|—|—|

| 616.92 | yes | **no** | **no** |

| 616.56 | yes | **no** | **no** |

| 610.88 | yes | yes | yes |

| 616.92 | no | yes | yes |

| 616.56 | no | yes | yes |

On the affected versions, the process accumulates CPU time and then stalls at

a consistent point — measured at 42.78 s, 43.73 s, 43.32 s and 43.39 s of CPU

across four separate runs. The consistency suggests a deterministic block

rather than a race condition.

Without `/dontskip`, `dxdiag` completes in a few seconds on every driver

version tested.

—

## Symptom in Call of Duty: Modern Warfare II

The Activision bootstrapper launches `dxdiag` during game startup. Captured

command lines:

```

dxdiag.exe /dontskip /whql:off /t

“C:\Users\\AppData\Local\Temp\Activision\bootstrapper\\dxdiag_onboot.txt”

dxdiag.exe /dontskip /whql:off /t

“C:\Users\\AppData\Local\Temp\Activision\Call of Duty MWII\\dxdiag_onboot.txt”

```

`cod22-cod.exe` then sits at a fixed **1012 MB** working set with slowly

increasing CPU and never advances past the RICOCHET splash screen. The

process reports `Responding = True` — it is waiting, not crashed. No

application error is written to the Windows event log.

Reverting to driver 610.88 resolves the game launch immediately.

—

## Possibly relevant

The `dxdiag` GUI, run without arguments on the affected drivers, displays:

> "DxDiag has detected that there may have been a problem accessing Media

> Foundation the last time this program was used. Would you like to bypass

> Media Foundation this time?"

Since `/dontskip` explicitly prevents that bypass, the hang may be in the

Media Foundation enumeration path. On 610.88 the same prompt does not lead to

a hang, so this looks like a driver-side interaction rather than an OS

component fault — see “ruled out” below.

—

## Ruled out

Each of the following was tested and did not resolve the hang on 616.56 or

616.92:

- **Clean driver install** with the “perform clean installation” option

- **DISM /Online /Cleanup-Image /RestoreHealth** — completed successfully

- **sfc /scannow** — found no integrity violations

- **Disabling the integrated AMD Radeon GPU** via `Disable-PnpDevice`

- **Closing all overlay software** — NVIDIA App, NVIDIA Overlay, Discord,

TeamViewer, Gigabyte Control Center

- **Stopping third-party kernel-mode services** — EasyTuneEngineService

(AMDRyzenMasterDriverV31), GigabyteUpdateService

- **Clearing shader caches** — game shadercache, NVIDIA DXCache and GLCache

- **Verifying the RICOCHET kernel driver** — `atvi-randgrid_sr` starts

successfully via `sc.exe start` and reports RUNNING; the driver itself is

not the blocker

- **Closing OneDrive**, which syncs the game’s Documents folder

—

## Notes

CUDA remains functional on 610.88 (`torch.cuda.is_available()` returns

`True`, CUDA 13.0), so the rollback carries no cost for compute workloads on

this machine.

Driver 616.92 was installed automatically by Windows Update, signed by

“Microsoft Windows Hardware Compatibility Publisher”, rather than through the

NVIDIA installer. Whether the WHQL-distributed package differs from the

NVIDIA-distributed one is not something I can verify.

—

## Ask

NVIDIA_bug_report_dxdiag_hang.pdf (7.6 KB)

Confirmation of whether this is reproducible on other RTX 50-series cards,

and whether the Media Foundation enumeration path changed between 610.88 and

616.56.

Hello,

Welcome to the NVIDIA Developer forums.

I have an RTX 5080/Gigabyte X870E Pro Ice/AMD 9800X3D, so pretty close, and CoD installed, driver version 616.92. I tried to reproduce, but neither running CoD, nor trying diverse dxdiag command lines caused a hang for me. Everything working nicely.

I also recommend you visit the GeForce forums. They target more the consumer side of things and might have better answers as to what might be going wrong on your system.

Best regards.

Hi, thanks for taking the time to test this.

Could you confirm whether you ran the exact command below? Without /dontskip, dxdiag completes normally on my system too, on every driver version:

dxdiag /dontskip /whql:off /t “%TEMP%\test.txt”

On my machine this hangs on 616.56 and 616.92 after a clean install (DDU), stalling at a consistent point across four runs (42.78 s, 43.73 s, 43.32 s and 43.39 s of CPU time), and completes normally on 610.88.

Two other differences that may matter:

  • The RTX 5080 uses the GB203 die, while my RTX 5060 Ti uses GB206, so the issue may be specific to that GPU variant.
  • On the affected drivers, running dxdiag without arguments shows the prompt about a possible problem accessing Media Foundation. Since /dontskip prevents that bypass, the hang may be in the Media Foundation enumeration path. If your dxdiag never shows that prompt, your system may simply not hit this path.

I’ll also post the report on the GeForce forums as you suggested and link back here.

Best regards,
Gabriel