What does BSOD 0x400000AD (VIDEO_DRIVER_DEBUG_REPORT_REQUEST) mean?

 
Previous Next
WINDOWS_NT_RC_STRING HARDWARE_PROFILE_UNDOCKED_STRING

VIDEO_DRIVER_DEBUG_REPORT_REQUEST

Video driver debug report request for VIDEO_DRIVER_DEBUG_REPORT_REQUEST

VIDEO_DRIVER_DEBUG_REPORT_REQUEST is bug check code 0x400000AD. This code is documented by Microsoft as a non-fatal minidump created by the video port on behalf of the video driver during runtime. It is diagnostic evidence for the display stack and should not be interpreted as a normal fatal blue-screen failure.

How to read it in a dump

  • Microsoft documents this value as 0x000000AD and explicitly describes the capture as non-fatal.
  • The display miniport driver, video port, adapter, and workload context are the important evidence.
  • TDR, device reset, and graphics-driver logging can be related, but the dump must be inspected.

What to check

  • Preserve the minidump and collect GPU driver version and display-event logs.
  • Correlate with graphics workload, driver update, monitor changes, and TDR events.
  • Use WinDbg and graphics symbols to identify the driver path that requested the report.

References

Dump evidence

Preserve the complete dump, the four bug-check parameters, the exact Windows build, loaded-module list, and the event timeline immediately before the stop. AllStat summarizes the condition as “this result”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.

Analysis order

  • Run WinDbg !analyze -v, then inspect the documented meaning of each parameter instead of relying only on the probably-caused-by line.
  • find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with video / driver / debug / report / request.
  • keep third-party filter, security, storage, graphics, and virtualization drivers in the module inventory; removing evidence before dump analysis can obscure the responsible path.

Do not repeatedly reboot a machine affected by this result before collecting the dump and event logs. Recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.

Looking for a different code? Search another status or error code.