Friday, August 18th 2023

AMD Releases Radeon GPU Detective (RGD) 1.0

We are happy to announce the release of Radeon GPU Detective (RGD) v1.0 - a tool for post-mortem analysis of GPU crashes. The tool allows developers to retrieve and analyze AMD GPU crash dumps and produce information that can help narrow down the search for a crash's root cause. Such information includes page fault details, resource details and execution markers reflecting the GPU work that was in progress at the moments leading to the crash.

This first version of the tool supports analysis of GPU crashes on Windows ("TDRs") in Direct3D 12 applications and requires a RX 6000 series (RDNA 2) or RX 7000 series (RDNA 3) card, in addition to the latest public AMD Radeon Adrenalin Software.
The tool lets developers set the driver into Crash Analysis mode using the Radeon Developer Panel (RDP) before reproducing the crash. Upon crash, an analysis file is generated with details that can help shed light on the crash's cause:
  • Execution marker information indicating which render passes and draw calls were in progress during the crash. Custom markers can be added by the app developer using the AGS (AMD GPU Services) library.
  • If the crash was determined to be caused by a page fault:
    • offending virtual address.
    • Details about any resource (such as heaps, textures, and buffers) that resided in the offending virtual address, including resource names given by the developer.
    • Timeline of memory events (such as Create, Destroy and Evict) filtered only for the relevant resources.
    • The crash analysis file is generated in text format by default. The tool can also be configured to generate the analysis file in JSON format to support automated processing.
RGD is part of the Radeon Developer Tool Suite (RDTS) which is available for download here.

Please note that RGD v1.0 requires the latest Adrenalin drivers (minimum version 23.7.2). The latest Adrenalin drivers can be downloaded from here.

The code for the RGD command line tool is open source and can be found on the Radeon GPU Detective repository.
Source: GPUOpen
Add your own comment

14 Comments on AMD Releases Radeon GPU Detective (RGD) 1.0

#1
ixi
AMD 100 points. Nvidia 0 points. Yaaawnn.

Would be cool and I hope that they will add vulkan and dx11. Can't wait to see nvidia clone of this for money :D.


Grabs popcorn.
Posted on Reply
#2
KrazyT
The tool's name is funny !
Hope it would work as decribed, and be useful ...
Posted on Reply
#3
Shihab
ixiAMD 100 points. Nvidia 0 points. Yaaawnn.

Would be cool and I hope that they will add vulkan and dx11. Can't wait to see nvidia clone of this for money :D.


Grabs popcorn.
docs.nvidia.com/nsight-graphics/

Nvidia has many faults, skimping on development tools isn't one of them...
KrazyTThe tool's name is funny !
Kinda sad it didn't turn out to be an [official] counterpart to Inspector...
Posted on Reply
#4
Unregistered
I am wondering if there exists a software to diagnose system's performance, to check where the game is limited.
#5
AsRock
TPU addict
Sounds interesting, although i would like to know who is "WE".

You mean this TPU's tool ?.
Posted on Reply
#6
Shihab
AsRockSounds interesting, although i would like to know who is "WE".

You mean this TPU's tool ?.
The "Press Release" tag on the front page should be mirrored on the forum view as well...
Posted on Reply
#7
lemonadesoda
This utility should not be needed. Is AMD not embarassed that they *need* this utility to fix their drivers?
Posted on Reply
#8
redeye
all my crash are from undervolting my 7900xtx, i stopped reporting them after the first 5.
Posted on Reply
#9
Mysteoa
lemonadesodaThis utility should not be needed. Is AMD not embarassed that they *need* this utility to fix their drivers?
Did you actually go and read what the tool is about? If you didn't, here is a sniped
Radeon GPU Detective (RGD) is a tool for post-mortem analysis of GPU crashes. The tool allows developers to capture and analyze AMD GPU crash dumps and produce information that can help narrow down the search for a crash’s root cause.
This is primarily aimed at developers that are testing their products and trying to resolve crashes. It could also be helpful, if a user can also provide that information to the developers.
Posted on Reply
#10
Steevo
lemonadesodaThis utility should not be needed. Is AMD not embarassed that they *need* this utility to fix their drivers?
To think that a company should be embarrassed for bettering their products is what is truly embarrassing.
Posted on Reply
#11
lemonadesoda
SteevoTo think that a company should be embarrassed for bettering their products is what is truly embarrassing.
I’m old school. A product should come to market when it’s ready. I don’t condone selling broken or unready products requiring time and effort for the end user to fix. Even worse: obligation to use paid for services to solve said unready or faulty product.

I would be embarrassed to sell a product or service that didn’t deliver on its promises.
Posted on Reply
#12
GoldenX
lemonadesodaI’m old school. A product should come to market when it’s ready. I don’t condone selling broken or unready products requiring time and effort for the end user to fix. Even worse: obligation to use paid for services to solve said unready or faulty product.

I would be embarrassed to sell a product or service that didn’t deliver on its promises.
Think of it this way. At least AMD and NVIDIA offer the tools to debug the cause.
Good luck with Intel or the lame Android SoCs.
Posted on Reply
#13
mechtech
I wonder if this will capture non-crashes, such as fan settings reverting to default?
lemonadesodaI’m old school. A product should come to market when it’s ready. I don’t condone selling broken or unready products requiring time and effort for the end user to fix. Even worse: obligation to use paid for services to solve said unready or faulty product.

I would be embarrassed to sell a product or service that didn’t deliver on its promises.
Have you seen games the past 5 years?? Seems a big chunk of them are in"early access" for years......................
Posted on Reply
#14
R-T-B
lemonadesodaI’m old school. A product should come to market when it’s ready. I don’t condone selling broken or unready products requiring time and effort for the end user to fix. Even worse: obligation to use paid for services to solve said unready or faulty product.

I would be embarrassed to sell a product or service that didn’t deliver on its promises.
Yeah, this would help devs acomplish that dude.
Posted on Reply
Add your own comment
Nov 18th, 2024 00:24 EST change timezone

New Forum Posts

Popular Reviews

Controversial News Posts