Potential GPUZ bug on Above 4G decoding detection.

[chrcoluk]

I was fiddling with my bios last night to toggle some settings related to GPU. (mostly CSM to full UEFI and Rebar stuff)

The settings I was running on prior to changes was Above 4g Decoding enabled, and CAM (what ASRock call Rebar) disabled.
GPU-Z detected what was set in the bios.
I then disabled Above 4G Decoding and to my surprise GPU-Z carried on saying its enabled.
I currently have it turned on again, alongside CAM, and GPUZ reports Rebar and Above 4G decoding enabled, which is of course should be correct.

Is it possible to verify if Above 4g Decoding detection is working properly, it is possible its an ASRock bios bug in failing to turn off as lately their bios's have been getting worse quality.

 

[W1zzard]

Is it possible to verify if Above 4g Decoding detection is working properly

Turn it off, then check Windows Device Manager for "Large Memory" resources (not sure if "normal" memory, too), and check if they are located at an address above 4G

 

[chrcoluk]

Ok attaching couple of screenshots, the first one is the same when CAM is off, doesnt matter if above 4g is on or off, and I think from my interpretation its not using anything above 4G.

The second is with both Above 4G and rebar on and shows large memory and some normal using above 4G, and less normal allocation.

 

[W1zzard]

Looking good. This is for your GPU device specifically, right?

For "Above 4G" you need to check all devices though, because the setting is not specific to the GPU, but to all devices (and this is what GPU-Z is looking for, for the report on this option)

 

[chrcoluk]

Yes thats my GPU.

 

[W1zzard]

Can you check if you see anything else using a range above 4G, when 4G decode is disabled?

Device Manager -> View -> Resources By Type, look in both Large Memory and Memory, you can also expand and screenshot if you'd like help