Resizable BAR and Smart Access Memory Explained: Requirements, BIOS, GPU Memory Access, and Performance Limits

A PCI Express device exposes memory and other resources to the system through Base Address Registers, or BARs. For a discrete GPU, part of that mechanism lets the CPU address regions of graphics memory through the PCIe device. Resizable BAR is an optional PCIe capability that allows the platform and device to negotiate a larger BAR size instead of relying only on a small fixed mapping window.

For graphics workloads, vendors describe the practical benefit as giving the CPU a larger view of GPU memory so transfers do not have to be broken into the same small mapped chunks. That does not make VRAM become system RAM, increase the physical amount of VRAM, or remove PCIe bandwidth and latency limits. It changes the addressable mapping available through the PCIe path.

AMD Smart Access Memory, usually shortened to SAM, uses the PCIe Resizable BAR capability in supported AMD platform and Radeon configurations. AMD describes it as allowing a Ryzen processor fuller access to Radeon graphics memory. It is not a separate memory technology, connector, bus, or extra pool of VRAM.

The names therefore overlap but are not interchangeable product labels. “Resizable BAR” describes the underlying PCIe capability used across multiple vendors, while “Smart Access Memory” is AMD branding for supported configurations built around that capability. Firmware menus may also use names such as Re-Size BAR or Smart Access Memory, so verify the exact system documentation rather than assuming the wording alone proves support.

A working Resizable BAR configuration depends on the complete chain: the CPU/platform, motherboard and UEFI firmware, graphics card, any required GPU firmware, and graphics driver must support the intended configuration. NVIDIA’s original GeForce RTX 30 desktop enablement, for example, required a compatible CPU and motherboard, suitable motherboard firmware, a supported GPU VBIOS where applicable, and a compatible driver. Intel likewise directs Arc users to motherboard or system support when firmware does not expose Resizable BAR.

Do not turn an old vendor compatibility table into a universal 2026 product list. Support has expanded over time and exact OEM systems can differ from retail motherboards. Check the current support material for the exact CPU or system, motherboard model and firmware revision, graphics card model, and installed driver before changing firmware settings.

Current Intel guidance for supported Arc configurations documents UEFI boot, disabled CSM or Legacy Mode, Above 4G Decoding, and Re-Size BAR Support as relevant firmware settings. ASUS similarly documents CSM, Above 4G Decoding, and Re-Size BAR on supported boards. Those examples establish common dependencies; they do not prove that every motherboard uses the same labels, menu path, default state, or sequence.

Changing CSM or boot mode can affect whether an existing operating-system installation or older expansion device remains bootable. Treat firmware changes as platform changes, not harmless performance toggles. Read the exact motherboard or system instructions first, preserve settings that matter, and do not flash a motherboard BIOS or GPU VBIOS merely because a generic guide says Resizable BAR exists.

AMD’s current Ryzen-and-Radeon desktop material states that Smart Access Memory compatibility extends to Radeon RX 5000 Series GPUs or later, Ryzen 3000 Series CPUs or later with listed exclusions, and AMD 500 Series motherboards or later with current vendor BIOS support; OEM support is also required. Other AMD pages still carry older footnotes describing the earlier Radeon RX 6000 and Ryzen/500-series launch-era requirement set.

That difference is a useful warning against copying one historical requirement list forever. Use AMD’s current product/platform documentation for the hardware being checked, and treat OEM laptops or desktops as exact-system compatibility questions. A matching AMD CPU and GPU brand combination by itself does not certify that SAM is enabled.

Do not assume that seeing a firmware toggle means the operating system and graphics stack are using the feature. NVIDIA documents a direct check in NVIDIA Control Panel under System Information, where supported GeForce configurations report whether Resizable BAR is enabled. Intel documents Intel Driver & Support Assistant as a way to confirm Resizable BAR state on supported Arc systems.

For AMD systems, use the current AMD software/system documentation for the exact platform rather than inferring SAM state from a BIOS label alone. If software reports the feature unavailable, work backward through exact motherboard firmware support, boot mode and documented prerequisites, GPU support or firmware requirements, and driver support. Avoid random BIOS toggling because a missing prerequisite can sit elsewhere in the chain.

A larger CPU-visible GPU-memory mapping can reduce an address-window limitation, but whether that matters depends on the application, engine, asset-transfer behavior, driver, GPU, CPU, resolution, and other system conditions. NVIDIA explicitly documented that its own testing found game-to-game variation and even regressions, which is why its GeForce implementation used game profiles rather than assuming the feature should improve every title.

Core Tech Tips therefore does not attach a universal FPS percentage to Resizable BAR or Smart Access Memory. Vendor benchmark claims can illustrate that vendors observed gains in selected configurations, but they are not independent measurements and cannot establish what another PC will gain. Evaluate performance with controlled before/after testing on the same system if the size of the effect matters to your decision.

Use a fixed sequence: 1) identify the exact CPU or OEM system, motherboard model and firmware revision, GPU model, and driver; 2) confirm current vendor support for that combination; 3) read the exact motherboard or system procedure and note boot-mode consequences; 4) check whether the GPU needs model-specific firmware; 5) change only the documented prerequisites; 6) boot normally and verify the active state in supported software; and 7) if performance matters, test the same workload under controlled conditions instead of assuming an automatic gain.

This keeps three questions separate: whether the PCIe capability exists, whether the complete platform actually enables it, and whether a particular workload benefits. Resizable BAR can be a useful platform feature, but it is neither a substitute for general GPU compatibility nor a universal performance switch.