AMD’s latest Radeon Adrenalin driver release, version 26.6.3, arrived as a hotfix aimed squarely at resolving a nagging installation failure that had been plaguing Windows 10 users for weeks. The patch, rolled out earlier this week, succeeded in allowing clean installs where previous attempts ended with cryptic error codes or system lockups. But the fix has brought a new headache to light: a subset of gamers is reporting that Smart Access Memory (SAM) remains stubbornly disabled post-update, even after performing a complete driver wipe using tools like DDU (Display Driver Uninstaller) or AMD’s own cleanup utility.

The dual nature of this release—one problem solved, another exposed—highlights the fragility of AMD’s driver ecosystem, particularly for users who rely on the full feature set of Radeon Software to squeeze every frame out of their Ryzen + Radeon gaming rigs. As the community awaits official acknowledgment from AMD, affected users are comparing notes on performance deficits and band-aid fixes.

The Fix: Windows 10 Can Now Inhale the Adrenalin Package

For weeks leading up to the 26.6.3 hotfix, AMD’s support channels were flooded with complaints from Windows 10 users unable to install any recent driver revision. The installer would throw up errors like “General Error – 1603” or “AMD software installer detected an incompatible build,” often leaving the system in a limbo state with a partially installed driver that caused screen flickering or defaulted to Microsoft’s basic display adapter. This left gamers unable to update to newer versions that included optimizations for recent releases such as Black Myth: Wukong or Hogwarts Legacy.

The 26.6.3 hotfix directly targeted this installation logic. According to the patch notes—though sparse—the installer now correctly identifies Windows 10 build revisions and avoids a conflict with certain legacy components that were triggering the failure. Feedback from the AMD subreddit and official community forums indicates that the fix works for the majority of previously locked-out users. “Finally, I can actually use my RX 7800 XT on Win10 again after two months of being stuck on 23.Q4 drivers,” one user posted. However, that same wave of relief was quickly overshadowed when many noticed that a key Radeon feature wasn’t playing along.

Smart Access Memory Goes AWOL

Smart Access Memory, AMD’s implementation of the PCIe Resizable BAR technology, allows the CPU to access the entire GPU frame buffer at once rather than in 256MB chunks. On compatible systems—typically a Ryzen 3000 series or newer CPU paired with a Radeon RX 6000 series or later GPU—enabling SAM can yield measurable performance uplifts, often 5–15% in memory-hungry scenarios at 1440p and 4K. It’s one of the headline features AMD uses to differentiate its “all-AMD” advantage from Intel/NVIDIA combos.

But after the 26.6.3 installation, users with previously functioning SAM setups began reporting that the toggle in Radeon Software’s “Performance > Tuning” tab had vanished, replaced by a grayed-out “Not Available” status. This occurred even when the motherboard BIOS had Resizable BAR and Above 4G Decoding enabled—the two prerequisites for SAM.

“My BIOS is set correctly, CPU is a 5800X3D, GPU is a 7900 XTX, and SAM was working fine on the old driver. After DDU and a clean install of 26.6.3, SAM is just gone,” read a detailed post on the AMDHelp subreddit. The user noted that GPU-Z confirmed Resizable BAR was enabled at the hardware level, but the driver refused to recognize it. This suggests the breakage lies within the Radeon Software layer, not in the BIOS or hardware initialization.

Performance Penalty: When SAM Switches Off

The real-world consequences for affected gamers aren’t trivial. Without SAM, the GPU’s memory access pattern reverts to a more restrictive method that can bottleneck data-hungry titles. Benchmarks posted by the community show drops of 8–12 frames per second in Cyberpunk 2077 at 1440p Ultra settings with an RX 7900 GRE, compared to identical settings with SAM enabled on an earlier driver. In Escape from Tarkov, a game notorious for its CPU-memory dependency, some users reported stutters and lower 1% lows that made the experience choppier.

A YouTube creator going by “GearSeekers” demonstrated the disparity in a before-and-after video using HWINFO and CapFrameX. With SAM off (26.6.3), Horizon Forbidden West averaged 89 FPS; with SAM on (rolling back to 26.5.1), the same benchmark run averaged 97 FPS—a nearly 9% gain. While not game-breaking, it’s enough to drop below a desired VRR window or force a settings reduction.

Community Workarounds: A Fragmented Experience

As is customary in the PC builder community, users have been swapping notes on temporary fixes. The most consistent solution: roll back to the previous driver version where SAM worked. For Windows 10 users, that often means Adrenalin 26.5.1 or a legacy 24.Q4 branch. However, this negates the installation fix and any newer game optimizations.

Some have reported that a specific installation order brings SAM back:
- Disable Windows automatic driver updates via Group Policy or DDU option.
- Boot into Safe Mode and clean the system with DDU.
- Reboot, enter BIOS, disable Resizable BAR and Above 4G Decoding, save and exit.
- Boot into Windows normally, run the 26.6.3 installer with Factory Reset checked.
- After installation, reboot, re-enter BIOS, re-enable the two settings.
- Boot back into Windows and check Radeon Software.

This convoluted dance works for about 60% of those who try it, according to an informal poll on the Linus Tech Tips forum. But it’s hardly an acceptable solution for a mainstream audience.

Others have pointed to a conflict with the AMD Chipset Driver. If the system is running an outdated chipset driver, the Radeon installer might not properly detect SAM capability. AMD’s official recommendation—buried in a support document—is to always install the latest chipset driver before the graphics driver. That proves true in some cases: users who updated their B550/X570 chipset drivers from AMD’s website reclaimed SAM after a reboot. Yet this didn’t help everyone, indicating multiple root causes.

AMD’s Silence Speaks Volumes

At the time of writing, AMD has not publicly acknowledged the SAM regression. The 26.6.3 hotfix release notes make no mention of Smart Access Memory; they solely describe the Windows 10 installation fix. Attempts to elicit a response on X (formerly Twitter) from AMD’s support account have gone unanswered. This radio silence is fueling frustration, especially among enthusiasts who expected a quick follow-up hotfix.

Veteran hardware observers note that driver install packages are chaotic assemblies of shader compilers, display controllers, and hardware abstraction layers. Breaking one component while fixing another is not unusual, but the silence suggests either that the issue is difficult to reproduce in AMD’s labs or that it has yet to bubble up to the priority list. With AMD’s engineering resources likely split between RDNA 4 launches and enterprise ROCm tasks, a small SAM glitch on a beta hotfix might not be deemed critical.

The Larger Picture: Windows 10 vs. Windows 11

A curious observation from the community is that the SAM issue seems to be disproportionately affecting Windows 10 systems. Windows 11 users who applied the 26.6.3 hotfix (primarily to align with their GPU’s support schedule) are reporting fewer incidents of SAM vanishing. This hints at a possible oversight in the driver’s Windows 10-specific code path, which might have received less testing.

With Windows 10’s end-of-support looming in October 2025, AMD might be shifting validation resources away from the older OS. Yet Windows 10 still commands a substantial install base, especially among gamers who prize its leaner overhead and lack of arbitrary TPM/hardware requirements. Leaving those users in the lurch with a broken marquee feature is not a good look, especially when competing NVIDIA drivers show no such degradation on the same OS.

How to Check if SAM is Affecting You

If you’ve just updated to 26.6.3 and are experiencing unexpectedly lower frame rates, here’s a quick checklist:
1. Open Radeon Software and navigate to Performance > Tuning. Look for “Smart Access Memory” under “GPU Tuning.” If it says “Not Available,” proceed.
2. Verify BIOS settings: Ensure Resizable BAR and Above 4G Decoding are enabled. On some motherboards, you may also need to disable CSM and enable UEFI boot.
3. Confirm hardware support: Your CPU must be a Ryzen 3000 series or newer (excluding APUs older than 4000G) and your GPU a Radeon RX 5000 series or newer. RX 5000 series actually support Resizable BAR but were unofficially SAM-enabled later; check the specific model.
4. Use GPU-Z: The Advanced tab’s “Resizable BAR” should show “Yes” if enabled at the hardware level. If it says “No” despite BIOS setting, you have a lower-level conflict.
5. Update chipset drivers: Download the latest AMD Chipset Software directly from amd.com/support. Install, reboot, then recheck Radeon Software.
6. Try the DDU + BIOS toggle method described above as a last resort.

Looking Forward: A Hotfix for the Hotfix?

The PC gaming community has grown accustomed to a cadence of driver firefighting: a major release introduces problems, a hotfix patches the most urgent ones, and a subsequent stable build consolidates everything. If history is any guide, AMD will likely issue a 26.6.4 or 26.7.1 driver within weeks that quietly restores SAM functionality alongside the Windows 10 install fix. But until then, affected users are trapped between a functional SAM and a broken installer, or a working installer and a broken SAM.

For now, the recommendation from seasoned tech veterans is clear: if you’re on Windows 10 and SAM is critical to your gaming experience—and you weren’t bitten by the installation bug—stay on your current driver. If you need the installation fix desperately, be prepared to lose SAM and possibly tinker with the BIOS or accept lower performance. Bookmark AMD’s official driver release notes page and watch for a sequel hotfix that explicitly lists SAM as an addressed issue. In the meanwhile, the community remains the best source of real-time workarounds, underscoring the vital role forums and Reddit play in patching the gaps left by official support.

The 26.6.3 hotfix is a microcosm of the broader struggle between rapid innovation and reliable driver quality. As AMD pushes more advanced features like HYPR-RX and Fluid Motion Frames into its software stack, the complexity of maintaining a monolithic driver that works across two generations of Windows OS, multiple GPU architectures, and endless hardware combinations only grows. Each bug fix risks waking another bug, and it’s the enthusiast who often bears the cost. For now, the SAM saga is a reminder that even a resolved installation bug can cast a shadow—one that only AMD can fully dispel.