Above 4G Decoding Explained: When to Enable It for GPUs, PCIe Cards, and NAS

Quick Answer

Enable Above 4G Decoding on a modern 64-bit system when several PCIe devices, a large-VRAM GPU, an HBA, or expansion cards cause resource-allocation or missing-device problems. It is commonly required for Resizable BAR, but the two settings are not the same. If the system is stable and has few PCIe devices, changing it may provide no benefit.

Above 4G Decoding is a low-level PCIe resource allocation option in the motherboard BIOS. It often appears when troubleshooting NAS boxes, mini PCs, workstations, multi-GPU systems, routers, HBA / SATA expansion cards, and local AI machines.

In simple terms, it allows a 64-bit system to assign PCIe devices’ MMIO address space above the 4GB physical address range.

That sounds low-level, but the problem is very real: when a motherboard has a GPU, NVMe drive, NIC, SATA expansion card, capture card, HBA, and other PCIe devices, forcing all of them to compete for address space below 4GB can cause resource allocation failures, missing devices, or even boot freezes.

Why is there a 4GB boundary?

The 4GB boundary is a historical legacy of the 32-bit era.

A 32-bit address space can address at most:

1

2^32 bytes = 4GB

Modern computers have 64-bit CPUs and operating systems, and memory sizes of 16GB, 32GB, 64GB, or more are common. But during POST and PCIe device initialization, motherboards still need to account for old compatibility assumptions. Many PCIe device resource mappings are initially arranged below the 4GB address boundary.

The problem is that the space below 4GB is not only for RAM. The system must reserve part of it for hardware devices.

That is where MMIO comes in.

What is MMIO?

MMIO means Memory-Mapped I/O.

The CPU cannot directly touch the internal registers or memory windows of PCIe devices as if they were normal RAM. Instead, part of the device’s registers, buffers, or VRAM window is mapped into the system address space. When the CPU reads or writes that address range, it is effectively communicating with the PCIe device.

Roughly:

• A device needs an address range.
• The motherboard assigns a physical system address range to it.
• When the CPU accesses that address range, it actually accesses the PCIe device.

This mapped region is not ordinary RAM. It is an address window occupied by hardware.

In old default configurations, many devices’ MMIO regions are constrained below 4GB, often around the 3GB to 4GB area. This usually works with few devices, but becomes crowded as more devices are installed.

What is BAR?

Every PCIe device uses BAR to tell the motherboard how much address space it needs.

BAR means Base Address Register. Its job is to say:

1

I need a block of MMIO space. Please assign me an address range.

GPUs, NVMe drives, SATA controllers, NICs, HBAs, and USB expansion cards may all need BAR space. More devices means more address windows. GPUs may need especially large mappings.

If the available MMIO space below 4GB is insufficient, the motherboard may fail to allocate resources to later devices.

What happens if Above 4G Decoding is disabled?

When Above 4G Decoding is disabled, the motherboard tends to pack PCIe resources below the 4GB boundary. With only a few devices, you may not notice anything. With many devices, problems can appear.

Common setups include:

• A discrete GPU.
• One or more NVMe SSDs.
• A JMB585 / ASM1166 SATA expansion card.
• A 2.5G / 10G NIC.
• A Wi-Fi / Bluetooth module.
• Extra HBAs, capture cards, or USB expansion cards.

All of these devices request BAR / MMIO address space from the motherboard. If the below-4GB region is full, the motherboard may show:

• A PCIe card is not recognized.
• The device does not appear in BIOS.
• Linux / Windows reports missing devices or resource errors.
• Boot freezes during POST.
• Black screen or blinking cursor.
• Each card works alone, but the system fails when multiple cards are installed together.

In JMB585 SATA expansion card scenarios, users often see the motherboard hang before BIOS, or the expansion card disappear after adding NVMe or NIC devices. Besides Option ROM, CSM, and PCIe Gen speed, PCIe address-space allocation is also worth checking.

What changes when Above 4G Decoding is enabled?

Enable:

1

Above 4G Decoding = Enabled

This tells the motherboard that PCIe devices supporting 64-bit addressing may have their MMIO resources allocated above 4GB.

Then PCIe devices no longer need to fight for the small below-4GB region. The motherboard can place some BAR / MMIO mappings at higher addresses, reducing resource conflicts.

For modern 64-bit systems, this is usually a reasonable setting, especially on:

• Multi-disk NAS machines.
• Multi-NIC routers.
• Mini PCs with SATA / HBA expansion cards.
• Multi-GPU workstations.
• AI inference or training machines.
• Desktop systems with GPU, NVMe, capture cards, and expansion cards.

Its goal is not to improve normal application performance. Its goal is to make hardware resource allocation less cramped.

Relationship with JMB585 / SATA expansion cards

A JMB585-style SATA expansion card may not need huge MMIO space by itself. The problem is often not how much this card needs alone, but how all PCIe devices in the system compete for address space together.

For example, a mini PC may include:

• An NVMe system disk.
• An onboard NIC.
• A Wi-Fi module.
• A JMB585 five-port SATA expansion card.
• Possibly a discrete GPU or other controller.

If BIOS resource allocation is conservative, JMB585 may be one of the last devices initialized. Earlier devices have already consumed much of the below-4GB space. When JMB585 asks for BAR space, the motherboard may fail or enter an abnormal state.

Enabling Above 4G Decoding lets the motherboard place some device resources above 4GB, reducing the chance of conflict.

It cannot repair a bad card or solve every PCIe link-training problem, but it is well worth trying when issues appear only after several devices are installed.

Relationship with Resizable BAR / SAM

Many users first notice Above 4G Decoding when configuring GPU performance features, such as:

• Resizable BAR
• Re-Size BAR
• ReBAR
• Smart Access Memory
• SAM

They are related, but not the same thing.

Above 4G Decoding is the foundation. It allows PCIe device MMIO resources to be assigned above 4GB.

Resizable BAR is a further capability. Traditionally, even if the CPU can access GPU memory, it often does so through a relatively small window, such as a 256MB mapping. With ReBAR, the CPU can map a larger portion of the GPU’s VRAM at once, theoretically reducing access switching overhead.

Many motherboards require Above 4G Decoding to be enabled before Resizable BAR can be enabled. So:

• Above 4G Decoding: allows device addresses above 4GB.
• Resizable BAR / SAM: allows the GPU BAR window to become larger.

For NAS and SATA expansion cards, the important part is usually the PCIe address space provided by the first option, not ReBAR itself.

Side effects

On modern 64-bit Windows, Linux, Ubuntu, Debian, TrueNAS, Proxmox, and similar systems, enabling Above 4G Decoding usually has no obvious downside.

Still, keep these points in mind:

• Very old 32-bit operating systems may not be suitable.
• Some very old BIOS implementations or legacy PCIe devices may be incompatible.
• If the system cannot boot after changing BIOS settings, clear CMOS or restore defaults.
• If you enable ReBAR / SAM as well, verify that the GPU, motherboard, OS, and driver support it.

On modern hardware and 64-bit systems, it is usually a healthy low-level setting to keep enabled, especially when multiple PCIe devices are installed.

When should you enable it?

Consider enabling Above 4G Decoding when:

• You use a 64-bit operating system.
• Multiple PCIe devices are installed.
• You have a discrete GPU, especially with 4GB or more VRAM.
• You use JMB585, ASM1166, HBA, RAID, capture, or other expansion cards.
• You are building a multi-disk NAS or router.
• You use multi-GPU, AI accelerator, or local LLM hardware.
• Installing a PCIe card causes boot freeze, black screen, or blinking cursor.
• Each device works alone, but combinations fail.

If you are troubleshooting a JMB585 SATA expansion card freezing during POST, check it together with:

• Disable CSM.
• Disable unnecessary Storage OpROM.
• Change PCIe speed from Auto or Gen3 to Gen2.
• Enable Above 4G Decoding.
• Try another PCIe slot.

What is it called in BIOS?

Different motherboard vendors use slightly different names. Common names include:

1
2
3
4
5

Above 4G Decoding
Above 4GB MMIO BIOS assignment
Memory Mapped I/O above 4GB
64-bit PCIe decoding
PCI 64-bit Resource Handling

Common menu locations include:

• Advanced
• PCIe Settings
• PCI Subsystem Settings
• Chipset
• North Bridge
• IO Ports
• Boot

Some motherboards place it near Resizable BAR, while others hide it under advanced PCIe or chipset settings.

Safe BIOS Change Checklist

Record the current BIOS setting before changing it, enable one option at a time, and verify that the operating system still sees every GPU, NIC, and storage controller after rebooting. If a card disappears, check PCIe lane sharing, slot generation mode, and the expansion-card firmware before treating Above 4G Decoding as the only cause.

• PCIe SATA Expansion Card Troubleshooting
• 12V-2x6 vs 12VHPWR GPU Power Connector Notes

Above 4G Decoding BIOS Setup and Recovery

Above 4G Decoding should generally be turned on on computers with modern 64-bit systems, discrete graphics cards, or multiple PCIe expansion cards. It allows the firmware to put part of the MMIO/BAR resources required by the device into the address space above 4GB, reducing the problem of multiple devices competing for low address space.

Under what circumstances is it recommended to enable it?

• There is a discrete graphics card and the motherboard provides Resizable BAR / SAM options.
• Use multiple graphics cards, HBAs, SATA expansion cards, high-speed network cards, or other PCIe devices.
• The NAS or workstation has been expanded a lot, and has experienced device disappearance, insufficient resources, or abnormal startup.
• System is modern 64-bit Windows or Linux with newer motherboard and device firmware.

It’s not a switch that improves CPU performance, nor does it guarantee that all games or applications will be faster; its main purpose is to improve device address resource allocation. For concepts and MMIO/BAR principles, see What is Above 4G Decoding.

Relationship with Resizable BAR

Many motherboards will require Above 4G Decoding to be turned on before allowing Resizable BAR to be turned on. The former can be understood as preparing the address space for a wider range of device mapping, while the latter allows the CPU to access the graphics card BAR more flexibly. The two are related, but not identical.

Where is it usually located in BIOS?

The name may vary slightly from brand to brand, usually under Advanced, PCIe, Chipset, or similar menu, and may also be placed with Resizable BAR. Before modifying, take a photo to record the current value, and confirm the motherboard manual or firmware update instructions; do not blindly change other PCIe options just because the screenshots online are the same.

What to do if it cannot be started after being turned on?

Turn off the power first and restore the default BIOS settings according to the motherboard manual, such as using Clear CMOS or restoring default options. Then gradually change back to Above 4G Decoding only to confirm whether it is related to the old graphics card, expansion card, BIOS version or other compatibility settings. Do not stack multiple BIOS changes in succession without confirming the cause.

For local models or NAS expansion scenarios, graphics card memory, PCIe slot bandwidth, cooling, and power should also be checked separately; Above 4G Decoding is not a replacement for these bottlenecks. For video memory selection, please refer to RTX 3060 running Qwen3 quantization and video memory selection.

Confirm these prerequisites before modifying

Above 4G Decoding works on modern UEFI and 64-bit systems. If your machine is still using legacy boot mode, a very old expansion card, or a BIOS version, read the motherboard support notes and update to stable firmware first; don’t mix new settings with multiple unrelated overclocking and memory timing changes in one operation.

Recommendations before modification: record the current BIOS page, confirm the location of clear CMOS or motherboard recovery method, ensure stable power supply, and operate when there is no emergency work. This allows you to return to a known state even if the screen goes black or the device is not recognized.

A low-risk setup step

1. Enter the BIOS and find Advanced, PCIe, Chipset or a menu similar to Resizable BAR.
2. Only enable Above 4G Decoding, save and start the system.
3. Confirm that the graphics card, network card, HBA or SATA expansion card are recognized in the system.
4. If necessary, enable Resizable BAR/SAM and repeat the verification.
5. Use it continuously for a period of time and observe whether sleep wake-up, restart, virtualization and heavy load are normal.

It is important to verify the two switches separately. If you change multiple PCIe options at once, it can be difficult to know later which one is causing the compatibility issue.

How to judge common phenomena

What it doesn’t solve

Above 4G Decoding does not increase video memory, increase the physical bandwidth of PCIe slots, or repair underpowered, overheated, or damaged expansion cards. When the local large model cannot run, you should still check the model quantization, video memory, memory and context first; when the NAS cannot recognize the hard disk, you should also check the HBA chip, cables, power supply and driver.

Recommendations for multiple graphics cards and NAS

Multi-graphics workstations should pay particular attention to motherboard CPU channels, slot sharing rules and power margins. When adding HBA or multiple NVMe to the NAS, you also need to look at the chipset channels and heat dissipation; being able to turn on Above 4G Decoding only means that the address space pressure may be alleviated, but it does not mean that the overall machine expansion plan is reasonable.

FAQ: Do I need to enable it if I only have one graphics card?

If it’s a modern 64-bit UEFI platform and there are no compatibility issues, this can usually be turned on; but without ReBAR or extended device requirements, the performance difference may not be noticeable.

FAQ: Will turning it on damage the hardware?

Normally not. It is a firmware resource allocation option; the risk mainly comes from old device compatibility or modifying too many BIOS items at the same time resulting in failure to boot, which can be handled by following the recovery steps.

Summary

The core purpose of Above 4G Decoding is to let the motherboard allocate PCIe device MMIO / BAR address space above 4GB. It does not fix drivers; it addresses BIOS / PCIe resource allocation.

On a simple PC with few devices, it may feel invisible. On a multi-disk NAS, multi-NIC router, mini PC with JMB585 / ASM1166 SATA expansion card, multi-GPU workstation, or local AI box, it matters.

If installing a PCIe expansion card causes BIOS freezes, black screens, blinking cursor, missing devices, or failure only when multiple devices are installed together, Above 4G Decoding = Enabled is a BIOS option worth checking early. It is not a cure-all, but it helps modern 64-bit hardware escape the old below-4GB address-space limitation and reduces PCIe resource conflicts.