• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

Testing please: GPU-Z Resizable BAR Support Report

Correct. Ryzen 5000 is Zen 3. 5800X3D is best option for gaming and not that expensive.

Ryzen 3000 is Zen 2 and doed not support Resize Bar

not upwards - 7000 series needs a new mainboard since it has the new socket AM5
 
Correct. Ryzen 5000 is Zen 3. 5800X3D is best option for gaming and not that expensive.

Ryzen 3000 is Zen 2 and doed not support Resize Bar

not upwards - 7000 series needs a new mainboard since it has the new socket AM5
That's actually not true R-Bar can work even on the first Ryzen series but it kinda depends of your motherboard bios if have the option to turn on the rbar/sam.....also it can work on older boards like B450 with the updated bios......in fact it can work also on old intel CPU's with the modded bios for their motherboards like X79 or X99 platforms.....
 
Nice, thanks for info
Sure NP....Well you are also not been totally wrong because it was advertised the same as you claimed above that R-Bar need 5000 series to work properly but shortly after it was acknowledged that it can work on older platforms and it was left to the manufacturers to update their bioses so that "older" CPU's can also have this option.......
 
Sure NP....Well you are also not been totally wrong because it was advertised the same as you claimed above that R-Bar need 5000 series to work properly but shortly after it was acknowledged that it can work on older platforms and it was left to the manufacturers to update their bioses so that "older" CPU's can also have this option.......
after going through the bios settings in ch4vv's mobo manual there's only above 4G decode and no other setting for reBar gigabyte may not have enabled it in the bios for this mobo
 
Correct. Ryzen 5000 is Zen 3. 5800X3D is best option for gaming and not that expensive.

Ryzen 3000 is Zen 2 and doed not support Resize Bar

not upwards - 7000 series needs a new mainboard since it has the new socket AM5
Resizable Bar is from the PCIe Specs in Version 2.0. It only depends on the BIOS/UEFI if its working:

https://composter.com.ua/documents/ECN_Resizable_BAR.pdf

Any CPU/Chipset with PCIe Version 2.0 and above should work. But unfortunately the Mainboard-Vendors don't activate this Options by Default (on most older Mainboards) and the UEFI has no Option to activate it.

On my Ryzen 1700x with a Asrock X370 Killer SLI its working without any Problems. Thanks to Asrock - which implemented the Option to activate Resizable Bar in their UEFI. Otherwise you should use a unofficial BIOS-Mod - for your own Risk.


Little Video which is showing where to find the mentioned Resizable Bar-Options in the Asrock-UEFI on my First Gen Ryzen-Setup.
 
Last edited:
Hello everyone, I have a little problem, I found this option recently and the truth is that I don't know if it will help me but I see that there is a lot of knowledge here and maybe I am not aware of something, I need help about it.
Will the BAR work with these components?
- CPU r5 3400g
- GPU rx5600xt
- MOBO b450 ds3h.
Because I have checked if the option appeared and it turns out that it does not, I have already tried certain things and it still does not appear.
3400g is not supported, it's a zen2 APU.

Sometimes the unsupported CPU's could turn the option on, but as discussed in the posts above yours it's not likely.

Correct. Ryzen 5000 is Zen 3. 5800X3D is best option for gaming and not that expensive.

Ryzen 3000 is Zen 2 and doed not support Resize Bar

not upwards - 7000 series needs a new mainboard since it has the new socket AM5
It does work on ryzen 3000, but not the 3000G series as they're Zen+ and not Zen2.


AMD's pages get confusing because they discuss AMD's SAM - which requires their GPUs. Rebar is part of that, but works on other GPU's as well (and appeared in older boards as part of BIOS updates)
AMD Smart Access Memory | AMD
AMD Brings Smart Access Memory (Resizable Bar) To Ryzen 3000 Desktop CPUs (wccftech.com)

1692770955192.png


The part that varies is if the older chipset boards enabled Rebar or not - many did for 3000 and 5000, and some showed the setting regardless of your CPU (with varying performance - sometimes a performance loss)


This article says it's AGESA v2 1.1.0.0 that added intial Zen3 support to boards, that brought Rebar to the 400 series chipsets.
Support on 300 series was never official, but sometimes turned up anyway.
At the time, users did plenty of crossflashing to get Zen3 support earlier than official support and that's likely how this happened accidentally with official BIOSes, by them simply copy-pasting the code.
 
Last edited:
Asrock makes it possible because they are a Vendor of Intel GPU-Cards. So they could take financial Profit of it. Other Vendors say: Better buy a newer Mainboard. Its a shame. But thats how it goes. Resizable Bar is a old Feature from PCIe 2.0 but the Intel Arc-GPUs are the first GPU-Generation who needs this Feature - otherwise you loose around 25-50% of Perfomance in some Games.

On my old Rig (X370 based Board) its working absolute flawless. Thanks to Asrock and their Work (in the UEFI).

And yes:

SAM bases mostly on Resizable Bar but it has some more Features - its not 100% the same. So AMD is not lying. For this Feature you need basically a 3000 Version CPU and 500 Chipset.

But in my Case (Intel GPU)... and this Threat is about Resizable Bar testing... its perfect working.


Don't get confused.
 
Last edited:
I need a bit of help here.

I'm using the ASUS Rog G16 laptop that comes with a Mux switch. When my laptop is in Optimus mode the GPU-Z displays resizable Bar as "disabled". But when I switched to dGPU mode it was shown as "enabled" which is confusing. Is this normal?

The last bios update for the Rog series from ASUS states that rebar is functional. But do I make sure it is truly functional other than reading the GPU-Z info?
 
I need a bit of help here.

I'm using the ASUS Rog G16 laptop that comes with a Mux switch. When my laptop is in Optimus mode the GPU-Z displays resizable Bar as "disabled". But when I switched to dGPU mode it was shown as "enabled" which is confusing. Is this normal?

The last bios update for the Rog series from ASUS states that rebar is functional. But do I make sure it is truly functional other than reading the GPU-Z info?

makes sense to me, since only real point and benefit of rebar comes when you have a dgpu active.
 
I need a bit of help here.

I'm using the ASUS Rog G16 laptop that comes with a Mux switch. When my laptop is in Optimus mode the GPU-Z displays resizable Bar as "disabled". But when I switched to dGPU mode it was shown as "enabled" which is confusing. Is this normal?

The last bios update for the Rog series from ASUS states that rebar is functional. But do I make sure it is truly functional other than reading the GPU-Z info?
Your onboard GPU doesnt support ReBar, is all that says to me.
 
When my laptop is in Optimus mode the GPU-Z displays resizable Bar as "disabled". But when I switched to dGPU mode it was shown as "enabled" which is confusing. Is this normal?
Yes it is normal APU's already use system memory as Vram so no need for rebar DGPU's on the otherhand have their own Vram and access to system ram (upto however many GB of Vram your DGPU has ) is via rebar if enabled
it's like this
Bar 0 = DGPU's Vram in chunks so 8GB if you have 8GB's of Vram much faster to transfer data from system ram to Vram
Bar 1 = DGPU no rebar and a chunk size of 256MB's much slower to transfer data to Vram from system ram
 
Question: Why aren't BAR sizes shown for non resizable cards at the bottom?
bar.png
 
That would work for most cards but what about the others that are not 256MB. Maybe it's awkward to implement?
 
That would work for most cards but what about the others that are not 256MB. Maybe it's awkward to implement?
Are there any others that are not 256 MB? You can check the memory range in device manager
 
Yes can check there or even better with lspci under Linux. Seems hard to find something for Windows. :(
 
Just found SIV
BAR1.png

NvAPI_GPU_GetBarInfo can be used from userland for nvidia cards. Don't know why BAR0 is reading 16.98 @red-ray
It would have been nice on it's personal B:D:F page IMO but shows alignment instead?
BAR2.png



Code:
GT440 
[URL unfurl="true"]https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1845269[/URL]
 Region 0: Memory at f6000000 (32-bit, non-prefetchable) [size=16M]
 Region 1: Memory at e8000000 (64-bit, prefetchable) [size=128M]
 Region 3: Memory at f0000000 (64-bit, prefetchable) [size=32M]
 Region 5: I/O ports at e000 [size=128]

Tesla K40m
[URL unfurl="true"]https://www.cryptoprofi.info/?p=8632[/URL]
Region 0: Memory at a2000000 (32-bit, non-prefetchable) [size=16M]
Region 1: Memory at 4400000000 (64-bit, prefetchable) [size=16G]
Region 3: Memory at 4200000000 (64-bit, prefetchable) [size=32M]

GTX560Ti
[URL unfurl="true"]https://askubuntu.com/questions/760756/ubuntu-16-04-nvidia-gf114-geforce-gtx-560-ti-nvidia-driver-errors[/URL]
01:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 Ti] (rev a1) (prog-if 00 [VGA controller])
    Flags: bus master, fast devsel, latency 0, IRQ 28
    Memory at f8000000 (32-bit, non-prefetchable) [size=32M]
    Memory at c8000000 (64-bit, prefetchable) [size=128M]
    Memory at d4000000 (64-bit, prefetchable) [size=64M]
    I/O ports at cf00 [size=128]

GT630
[URL]https://bbs.archlinux.org/viewtopic.php?id=25362801:00.0[/URL] VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 630] (rev a1) (prog-if 00 [VGA controller])
        Subsystem: Micro-Star International Co., Ltd. [MSI] GF108 [GeForce GT 630]
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin A routed to IRQ 31
        Region 0: Memory at fd000000 (32-bit, non-prefetchable) [size=16M]
        Region 1: Memory at d0000000 (64-bit, prefetchable) [size=128M]
        Region 3: Memory at dc000000 (64-bit, prefetchable) [size=32M]
        Region 5: I/O ports at 9c00 [size=128]
        Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]

GTX580
[URL unfurl="true"]https://askubuntu.com/questions/114265/wrong-memory-info-for-ati-radeon-video-card-with-lspci-v-command[/URL]
03:00.0 VGA compatible controller: nVidia Corporation GF110 [GeForce GTX 580] (rev a1) (prog-if 00 [VGA controller])
        Flags: bus master, fast devsel, latency 0, IRQ 16
        Memory at f9000000 (32-bit, non-prefetchable) [size=16M]
        Memory at e0000000 (64-bit, prefetchable) [size=128M]
        Memory at ee000000 (64-bit, prefetchable) [size=32M]
        I/O ports at 7f00 [size=128]
        [virtual] Expansion ROM at e8000000 [disabled] [size=512K]
Various iGPU can have BAR adjusted.
Probably most compute cards are not 256MiB?

I guess as none of them have 0x15 capability (rebar) then perhaps it's understandable they are not shown on GPU-Z tab. Just thought it might be useful but after some thought maybe not.

P.S. Had to use BB code in spoiler otherwise formatting gets confused and changes font sizes.
 
Last edited:
Your onboard GPU doesnt support ReBar, is all that says to me.
Thanks for the feedback. Actually my GPU-z have two profiles Intel UHD Graphics and 4080M. It shows 4080M rebar is off when in Optimus (MsHybrid) mode.
 
Thanks for the feedback. Actually my GPU-z have two profiles Intel UHD Graphics and 4080M. It shows 4080M rebar is off when in Optimus (MsHybrid) mode.
That's not what you said above
But when I switched to dGPU mode it was shown as "enabled" which is confusing. Is this normal?

When you're in optimus mode, you're using the IGP unless a game is actively using the dGPU.
 
Forgot to update. After trying SIV it uses address range so not necessarily actual size of aperture. For example while playing around with a GT640 and being lazy/wasteful with addressing I got this.
SIV2.png

Actual BAR 1 size was configured to 2GiB.
 
I have a situation where the system has CSM disabled in BIOS, but GPU-Z reporting it as not disabled. Pretty confusing!

How does GPU-Z check this "CSM disabled" thinggy? Is this just a fluke in my case, or is there more to it?

It's an ancient Z620 HP workstation with a Sandy Bridge Xeon that had PCIE 3.0. The video card is RX580. Details are here:


gz01.gif
gz04.gif


Some more info on the system:

hw01.png

hw02.png

hw03.png

hw04.png
hw05.png
 
Last edited:
Bit of a odd thing I want to report :
You can have active rebar without disabling CSM in UEFI/BIOS :
Rebar1.png
Simply have a GPU without Legacy vBIOS part (ie. there is no legacy module), and "cope" with it not being able to enter BIOS at any point during POST (image appears only after Windows loads it's driver).
Having legacy vBIOS enabled device on hand might be required to have successful driver installation with EFI only card - however other than that, it should "just work".
 
Last edited:
Bit of a odd thing I want to report :
You can have active rebar without disabling CSM in UEFI/BIOS :

Simply have a GPU without Legacy vBIOS part (ie. there is no legacy module), and "cope" with it not being able to enter BIOS at any point during POST (image appears only after Windows loads it's driver).
Having legacy vBIOS enabled device on hand might be required to have successful driver installation with EFI only card - however other than that, it should "just work".

I believe "CSM disabled" test is kind of flaky. If you read this full thread you'll notice that it seemed to have always had a few issues here and there. It's not fully clear what that's actually testing!
 
Back
Top