AMD Radeon™ GPU Detective (RGD) logo

Capture. Examine. Investigate. Now available as part of the AMD Radeon™ Developer Tool Suite.

AMD RGD UI image

Meet AMD Radeon™ GPU Detective (RGD), a powerful tool for developers to help with post-mortem analysis of GPU crashes.

Supports:

  • DirectX® 12
  • Vulkan®

Download the latest version - v1.5

Important: To use AMD RGD, please make sure you have the AMD Software: Adrenalin Edition™ 25.3.1 driver or newer installed.

Download AMD RGD (Windows®)View AMD RGD on GitHubRead the AMD RGD documentation

This release adds the following features:

  • Added support for AMD Radeon™ RX 9060 XT, AMD Radeon™ RX 9070 GRE, and AMD Radeon™ AI PRO R9700 graphics cards.
  • Added support for Hardware Crash Analysis on APUs with AMD Radeon™ 880M Graphics or AMD Radeon™ 890M Graphics.
  • For DirectX® 12 apps, you can augment the crash analysis output file with high-level information about in-flight shaders, including the source file name and the HLSL source code. This requires pointing the tool to the files that include the debug information that was generated by the DXC compiler, which can be done via AMD RDP or the AMD RGD command line.
  • In Vulkan®, nested command buffers are now reflected in the execution marker tree.
  • The crash analysis output file now contains metadata about the configuration of the capture session (was Hardware Crash Analysis enabled? What PDB search paths were used? and more).
  • For more information about enhancing AMD Radeon™ GPU Detective Output with DirectX® Debug Information, see this blog post.

Features

AMD Radeon™ GPU Detective allows you to easily and reliably capture AMD GPU crash dumps from your crashing DirectX® 12 and Vulkan® applications. A concise crash analysis report file will include detailed information that can help to narrow down the cause of the crash.

This command line tool makes the process simple with an intuitive and concise crash analysis summary and useful visualizations.

Gather your evidence

Capture AMD GPU crash dumps and generate crash analysis reports with ease.

AMD RGD ensures you can reproduce the crash with minimum impact on your runtime performance.

Examine your execution

Understand the exact events which led to your crash using the execution marker tree. This tree visualizes the GPU work that was in progress in the moments leading to the crash.

You can insert user markers with custom strings in your code which will be presented in the crash analysis file.

Terminal window
Command Buffer ID: 0x617 (Queue type: Direct)
=============================================
[>] "Frame 362 CL0"
├─[X] "Depth + Normal + Motion Vector PrePass"
├─[X] "Shadow Cascade Pass"
├─[X] "TLAS Build"
├─[X] "Classify tiles"
├─[X] "Trace shadows"
├─[X] ----------Barrier----------
├─[X] "Denoise shadows"
├─[X] "GltfPbrPass::DrawBatchList"
├─[X] "Skydome Proc"
├─[X] "GltfPbrPass::DrawBatchList"
├─[>] "DownSamplePS"
│  ├─[X] ----------Barrier----------
│  ├─[>] Draw(VertexCount=3, InstanceCount=1)
│  ├─[>] Draw(VertexCount=3, InstanceCount=1)
│  ├─[>] Draw(VertexCount=3, InstanceCount=1)
│  ├─[>] Draw(VertexCount=3, InstanceCount=1)
│  ├─[>] Draw(VertexCount=3, InstanceCount=1)
│  └─[>] ----------Barrier----------
├─[>] "Bloom"
│  ├─[>] "BlurPS"
│  │  ├─[>] ----------Barrier----------
│  │  ├─[>] Draw(VertexCount=3, InstanceCount=1)
│  │  ├─[>] Draw(VertexCount=3, InstanceCount=1)
│  │  └─[ ] ----------Barrier----------
│  ├─[ ] ----------Barrier----------
│  ├─[ ] Draw(VertexCount=3, InstanceCount=1)
│  ├─[ ] Draw(VertexCount=3, InstanceCount=1)
│  ├─[ ] "BlurPS"
│  ├─[ ] Draw(VertexCount=3, InstanceCount=1)
│  └─[ ] ----------Barrier----------
└─[ ] "Indirect draw simple"

Probe any page faults

If a page fault is a suspect, check out the page fault summary section to begin your investigation.

This view provides details that can help to shed light on the crash cause, including the offending virtual address, a detailed list of the resources that have ever resided in that virtual address, with information that can help you identify the resources in your code, and a resource timeline that shows the events associated with these resources. 

Timestamp            Event type        Resource type     Resource identifier     Resource size             Resource name
---------            ----------        -------------     -------------------     -------------             -------------
00:00:00.1145408     Create            Buffer            0xd9fb99b500000169      671088640 (640.00 MB)     VidMemBuffer
00:00:00.1154752     Bind              Buffer            0xd9fb99b500000169      671088640 (640.00 MB)     VidMemBuffer
00:00:00.1154752     Make Resident     Buffer            0xd9fb99b500000169      671088640 (640.00 MB)     VidMemBuffer
00:00:01.1202400     Evict             Buffer            0xd9fb99b500000169      671088640 (640.00 MB)     VidMemBuffer

Requirements

Driver

  • AMD Software: Adrenalin Edition™ (minimum version 25.3.1)

Supported GPUs

  • AMD Radeon™ RX 9000 Series Graphics
  • AMD Radeon™ RX 7000 Series Graphics
  • AMD Radeon™ RX 6000 Series Graphics
  • AMD Ryzen™ Processors with AMD Radeon™ Graphics based on AMD RDNA™ 3.5 architecture or better
  • AMD Radeon™ AI PRO R9700 Graphics

Supported graphics APIs

  • DirectX® 12
  • Vulkan®

Supported OSs

  • Windows® 10
  • Windows® 11

Version history

  • Added support for AMD Radeon™ RX 9060 XT, AMD Radeon™ RX 9070 GRE, and AMD Radeon™ AI PRO R9700 graphics cards.
  • Added support for Hardware Crash Analysis on APUs with AMD Radeon™ 880M Graphics or AMD Radeon™ 890M Graphics.
  • For DirectX® 12 apps, you can augment the crash analysis output file with high-level information about in-flight shaders, including the source file name and the HLSL source code. This requires pointing the tool to the files that include the debug information that was generated by the DXC compiler, which can be done via AMD RDP or the AMD RGD command line.
  • In Vulkan®, nested command buffers are now reflected in the execution marker tree.
  • The crash analysis output file now contains metadata about the configuration of the capture session (was Hardware Crash Analysis enabled? What PDB search paths were used? and more).
  • For more information about enhancing AMD Radeon™ GPU Detective Output with DirectX® Debug Information, see this blog post.

AMD Radeon™ Developer Tool Suite

Other tools

Related news and technical articles

Related videos