Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
HIP-RT runs on both AMD and NVIDIA GPUs, but AMD hardware-accelerated ray tracing starts with the RDNA 2 architecture. RDNA 1 cards can execute HIP-RT workloads without AMD’s hardware ray-tracing acceleration. For the currently documented AMD software stack, use AMD Software: Adrenalin Edition 23.30 or newer on Windows and ROCm 5.7 on Linux, then verify that your exact GPU SKU appears in the HIP SDK matrix for the release you selected. Windows support is limited to validated Windows 11 x86-64 configurations and does not implement every HIP runtime API function.
What is HIP-RT and what does compatibility mean?
HIP-RT is AMD GPUOpen’s ray-tracing library for applications written with HIP. It provides ray-tracing functionality while allowing a codebase to target AMD and NVIDIA devices through the HIP ecosystem. “Compatible” can mean three different things: the code can run at all, the GPU can use hardware ray-tracing units, and the exact operating-system, driver and software combination is officially supported.
Those distinctions matter when choosing a card. An RDNA 1 GPU may execute HIP-RT through non-accelerated paths, while an RDNA 2, RDNA 3 or RDNA 4 GPU can use AMD hardware ray-tracing acceleration when the application and software stack support it. A GPU can also be architecturally capable yet absent from a particular Windows HIP SDK release table; AMD treats an unlisted SKU as unsupported for that release.
HIP-RT release 3.0.9ba63f3, identified by GPUOpen in 2025, includes RDNA 4 ray-tracing work such as compressed BVH8 and triangle packets. These features do not make every older card equivalent: architecture, exact SKU, driver, operating system and library build still determine the result.
#1 Best Overall
- Powered by Radeon RX 9070 XT
- WINDFORCE Cooling System
- Hawk Fan
- Server-grade Thermal Conductive Gel
- RGB Lighting
Which AMD GPUs support HIP-RT hardware acceleration?
AMD states that hardware-accelerated ray tracing works only on RDNA 2 architecture GPUs or newer. Therefore, RDNA 2, RDNA 3 and RDNA 4 Radeon products are the relevant AMD generations for accelerated HIP-RT; RDNA 1 remains a software-execution option without that hardware acceleration.
Architecture-level support
| AMD architecture | HIP-RT execution | Hardware ray tracing | Practical implication |
|---|---|---|---|
| RDNA 1 | Can run HIP-RT workloads through non-accelerated paths | No | Expect substantially different performance and confirm that the application supports the fallback path. |
| RDNA 2 | Supported when the exact GPU and software release are validated | Yes | First AMD generation with hardware ray-tracing acceleration. |
| RDNA 3 | Supported for listed SKUs in the applicable HIP SDK matrix | Yes | Check the release-specific Windows table and matching driver. |
| RDNA 4 | Supported for listed SKUs in the applicable HIP SDK matrix | Yes | HIP-RT 3.0.9ba63f3 documents RDNA 4 ray-tracing features. |
The architecture rule is necessary but not sufficient. AMD’s Windows documentation is SKU-specific, so a card that uses a supported architecture can still be outside the official list for a given HIP SDK package.
Which exact AMD GPUs are in the current Windows HIP SDK table?
The current Windows table names specific Radeon, Radeon PRO and Ryzen AI products. AMD warns that an unlisted GPU is not officially supported and that prebuilt libraries compiled for an unsupported device can produce runtime errors.
| Product or family named by AMD | Architecture or target information | What the table establishes |
|---|---|---|
| Radeon RX 9070 XT | RDNA 4; LLVM target gfx1201 | Runtime and HIP SDK support are listed. |
| Radeon RX 9070 | RDNA 4 | Listed as a supported Radeon SKU. |
| Radeon RX 9060 XT | RDNA 4 | Listed as a supported Radeon SKU. |
| Radeon RX 7900 XTX and RX 7900 XT | RDNA 3 | Listed as supported Radeon SKUs. |
| Radeon RX 7800 XT | RDNA 3 | Listed as a supported Radeon SKU. |
| Radeon RX 7700 XT | RDNA 3 | Listed as a supported Radeon SKU. |
| Radeon RX 7650 GRE | RDNA 3 | Listed as a supported Radeon SKU. |
| Selected Radeon PRO W-series models | RDNA generation varies by model | Only the models present in the release table are official; the complete model list is release-specific. |
| Selected Ryzen AI Max and AI 300-series APUs | Integrated GPU | Only the named APU SKUs in the table are official; a product family name alone is not enough. |
The table is not a universal promise for every board partner, mobile variant or similarly named product. Before installing, match the exact model string reported by your system with the table for your HIP SDK release. If it is missing, treat the configuration as unsupported even when its architecture appears suitable.
Does HIP-RT work on RDNA 1 or RDNA 2?
RDNA 1 can run HIP-RT without AMD hardware ray-tracing acceleration. RDNA 2 is the minimum AMD generation for hardware-accelerated ray tracing, so it is the practical starting point for workloads that depend on acceleration rather than mere functional execution.
What RDNA 1 users should expect
- The application may launch and produce correct results through a software or non-accelerated path.
- Performance characteristics will not represent an accelerated ray-tracing implementation.
- Support can depend on whether the application permits the fallback path; check its own requirements before assuming that execution is useful.
Why RDNA 2 or newer is safer
- RDNA 2 introduces AMD’s hardware ray-tracing capability.
- RDNA 3 and RDNA 4 continue the accelerated path but remain subject to SKU and release validation.
- Newer HIP-RT releases can add architecture-specific optimizations, so pair the GPU with the release’s documented compiler target and driver.
What driver and ROCm versions does HIP-RT require?
GPUOpen identifies AMD Software: Adrenalin Edition 23.30 or later for Windows and ROCm 5.7 for Linux as the stated baseline requirements. These are minimums from the cited requirements, not a guarantee that every newer driver works with every older HIP-RT binary; keep the HIP-RT, HIP SDK or ROCm release and driver within the same compatibility documentation.
| Platform | Stated software baseline | Important qualification |
|---|---|---|
| Windows | AMD Software: Adrenalin Edition 23.30 or later | Use a validated Windows 11 x86-64 configuration and confirm the exact GPU in the release-specific HIP SDK table. |
| Linux | ROCm 5.7 | HIP is delivered through the ROCm Core SDK; package and kernel support must match the selected ROCm release. |
AMD’s documentation changes as HIP SDK and ROCm releases add or remove devices. Select the software version first, then check the GPU, operating system, kernel or Windows build and driver in that version’s matrix. Do not infer support from a table belonging to a different release.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11How is HIP installed on Linux?
On Linux, HIP is included in the ROCm Core SDK. Package-manager installations normally place ROCm at /opt/rocm. If you install it elsewhere, set HIP_PATH to the alternate HIP directory so build systems and tools can find the runtime and headers.
- Install a ROCm release that meets the HIP-RT requirement and supports your exact GPU and Linux distribution.
- Confirm that the ROCm directory is available at
/opt/rocm, or setHIP_PATHwhen using a non-default location. - Run
/opt/rocm/bin/hipconfig --full. This prints the HIP installation, compiler and platform details needed to spot a missing or mismatched component. - Check that the reported device target matches the architecture expected by your application and that the installed driver can access the GPU.
- Build or launch the HIP-RT application against the same ROCm installation you verified; avoid mixing headers, libraries and tools from separate ROCm versions.
If hipconfig is missing, the package is usually incomplete, the installation path is different, or the shell is pointing at another ROCm tree. Correct HIP_PATH and your executable search path before troubleshooting the application itself.
How is HIP SDK support handled on Windows?
AMD distributes the HIP runtime through the ROCm Core SDK on Windows as well as Linux, but Windows support is narrower. The current system-requirements documentation validates Windows 11 x86-64 configurations, and the HIP FAQ cautions that not all HIP runtime API functions are implemented on Windows.
- Install a Windows 11 x86-64 build that is covered by the HIP SDK release documentation.
- Install AMD Software: Adrenalin Edition 23.30 or a later driver that the selected release supports.
- Check the Windows HIP SDK table for the exact GPU model, not merely its family or architecture.
- Install the matching HIP SDK and compile with the targets listed for that release.
- Test the application’s Windows code paths, especially any feature that calls less-common HIP runtime APIs; Linux behavior does not prove that the same API is implemented on Windows.
An unlisted GPU may still be detected by the operating system, but that does not make it an officially supported HIP SDK device. AMD specifically warns that unsupported prebuilt libraries can fail at runtime, so rebuilding for an officially listed target is not a substitute for missing hardware or release support.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →What host CPU and platform requirements apply?
ROCm requires a host CPU that supports PCIe atomics. AMD gives modern processors after first-generation Zen and Intel Haswell as examples of CPUs with the required capability. The CPU requirement is independent of the GPU’s ray-tracing architecture: a supported graphics card can still fail to initialize if the host platform lacks PCIe atomic operations.
- Verify the processor generation and motherboard platform before diagnosing a GPU installation.
- Use a current BIOS and chipset configuration when the platform vendor documents PCIe atomic support as a firmware option.
- Remember that an APU listed in the Windows table still has to meet the operating-system and SDK requirements; integrated graphics do not bypass them.
How should I check a GPU before buying or deploying it?
Use a release-first checklist rather than relying on a generic “ROCm compatible” label. The first three checks are documented compatibility requirements; VRAM, performance, price and availability require separate application and market evaluation.
Rank #2
- Axial-tech fans now feature a smaller fan hub that facilitates longer blades and a barrier ring that increases downward air pressure
- Phase-change GPU thermal pad helps ensure optimal heat transfer, lowering GPU temperatures for enhanced performance and reliability
- 2.5-slot design allows for greater build compatibility while maintaining cooling performance
- Dual-ball fan bearings last up to twice as long as standard conventional sleeve bearings designs
- 0dB technology lets you enjoy light gaming in relative silence
- Choose the HIP-RT, HIP SDK or ROCm release. Compatibility tables are version-specific.
- Identify the exact GPU SKU. Record the complete model, including mobile, workstation or APU designation.
- Confirm architecture and ray-tracing capability. RDNA 2 or newer is required for AMD hardware acceleration; RDNA 1 is non-accelerated.
- Match the operating system. For the current Windows documentation, use validated Windows 11 x86-64; on Linux, confirm the distribution and kernel support for the selected ROCm release.
- Match the driver baseline. Use Adrenalin 23.30 or later on Windows or ROCm 5.7 on Linux, while following the release’s newer matrix when applicable.
- Verify the host CPU. PCIe atomic support is required by ROCm.
- Check application resources. VRAM capacity and workload performance are separate from official API compatibility.
What problems are most common, and how do I fix them?
The GPU is not in the Windows table
Treat it as unsupported for that HIP SDK release. Recheck the exact SKU and release, then use a listed model or a software version whose official matrix includes the device.
HIP tools cannot be found on Linux
Run the tool from the actual installation directory, commonly /opt/rocm/bin/hipconfig --full. If ROCm was installed elsewhere, set HIP_PATH and update the shell’s executable path.
The application reports a runtime error with a prebuilt library
Confirm that the library was built for the GPU target and that the device is officially supported. AMD notes that prebuilt libraries for unsupported GPUs can cause runtime errors; use a matching, supported build rather than forcing an unrelated target.
Windows works for one API call but fails for another
Check whether the failing call is among the HIP runtime functions implemented by the Windows SDK. AMD’s FAQ explicitly says that not all HIP runtime API functions are supported on Windows, so test the application’s Windows feature set independently from Linux.
Initialization fails despite a compatible GPU
Check the host CPU for PCIe atomic support, then verify the driver, SDK and operating-system versions as a set. A supported GPU alone does not satisfy the ROCm platform requirements.
Which GPU is the sensible choice for a new HIP-RT system?
For AMD hardware ray tracing, start with an officially listed RDNA 2-or-newer SKU in the HIP SDK release you intend to deploy. Among the current table entries, the Radeon RX 9070 XT is explicitly listed as RDNA 4 with LLVM target gfx1201 and Runtime plus HIP SDK support, but selection should still account for the application’s VRAM and performance needs. The compatibility sources do not establish street price, stock, board-partner quality or comparative benchmarks, so those decisions require separate current checks.
Recommended Free Tools
If your deployment must run on Windows, prioritize a model in the exact Windows table and test all required HIP runtime APIs. If Linux is acceptable, ROCm provides the common HIP delivery mechanism, but the GPU, distribution, kernel, CPU and ROCm release still need to align.
Frequently Asked Questions
Can HIP-RT run on an NVIDIA GPU?
Yes. HIP-RT is designed to run on AMD and NVIDIA GPUs through the HIP ecosystem. The AMD-specific RDNA 2 rule applies to AMD hardware ray-tracing acceleration, not to NVIDIA hardware requirements.
Do I need a discrete graphics card for HIP-RT?
Not necessarily. AMD’s Windows table includes selected Ryzen AI Max and AI 300-series APUs, but only the exact APU SKUs named for the release are official. Integrated graphics still share system resources and must meet the same SDK and operating-system checks.
Will a newer AMD driver always work with an older HIP-RT build?
Not automatically. A newer driver may be usable, but HIP-RT, HIP SDK or ROCm compatibility is release-specific. Keep the runtime, compiler, prebuilt libraries and driver within one documented compatibility set and retest after upgrades.
Free tools Windows power users keep installed
One-click scans. No signup required.
Why does a supported GPU still show poor ray-tracing performance?
Official support confirms that the software can target the device; it does not specify a performance level. Workload structure, VRAM pressure, scene size, compiler target and whether the application actually selects hardware traversal all affect speed.
Can I use Windows if my application also targets Linux?
Yes, but feature parity is not guaranteed. AMD supports HIP on both systems while warning that some HIP runtime API functions are not implemented on Windows, so maintain a Windows-specific test pass for every API and code path you depend on.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
