- Joined
- May 29, 2016
- Messages
- 17 (0.01/day)
Processor | Intel Xeon E5-1680 v2 @ Stock |
---|---|
Motherboard | ASUS P9X79 WS/IPMI |
Cooling | Thermalright IFX-14 |
Memory | 64GB DDR3L-1600 ECC Reg (8 x 8GB Hynix HMT41GR7BFR8A-PB) |
Video Card(s) | Gigabyte R9 290X MBA (modded to 8GB VRAM Elpida 4032BABG + modded pure Copper heatsink) |
Storage | Intel 750 400GB AIC + 2 x 1TB WD RE4 Intel RAID0+1 |
Display(s) | 32" BenQ BL3200 (2560 x 1440 via DisplayPort) |
Case | Antec P182 |
Audio Device(s) | Int. ALC1150 |
Power Supply | Corsair AX760 |
Mouse | Logitech MX Master 2S |
Keyboard | Microsoft Curve 2000 |
Software | Windows 8.1 Professional 64-bit |
I have quite a unique R9 290X card, it had passed the memory replacement procedure, from 4GB Hynix AFR to 8GB Elpida BABG.
After that, and after all proper vBIOS modifications (there's a long Hawaii BIOS Editing thread at overclock.net) the GPU-Z is the only program that incorrectly detects the memory buffer loading.
For example, I run MSI Kombustor GPU Memory burner 6GB test, and the reported memory load increases linearly from 2D value to ~4000MB (see the screenshot) and then, resets to 0MB again and continues counting on. So, according to GPU-Z I'm running the test with ~2300MB, while in fact the load equals ~6400MB.
The same problem is observed in different apps requiring more that 4096MB of VRAM.
I want to note that GPU-Z detects the memory properly (see the screenshot), 8GB Elpida GDDR5.
I tried some other monitoring tools (AIDA64, HWInfo64), they correctly report the VRAM loading.
It seems to me there's some hard-coding in the program code, where 290X is assumed to be a 4GB card, while it's not always true...

After that, and after all proper vBIOS modifications (there's a long Hawaii BIOS Editing thread at overclock.net) the GPU-Z is the only program that incorrectly detects the memory buffer loading.
For example, I run MSI Kombustor GPU Memory burner 6GB test, and the reported memory load increases linearly from 2D value to ~4000MB (see the screenshot) and then, resets to 0MB again and continues counting on. So, according to GPU-Z I'm running the test with ~2300MB, while in fact the load equals ~6400MB.
The same problem is observed in different apps requiring more that 4096MB of VRAM.
I want to note that GPU-Z detects the memory properly (see the screenshot), 8GB Elpida GDDR5.
I tried some other monitoring tools (AIDA64, HWInfo64), they correctly report the VRAM loading.
It seems to me there's some hard-coding in the program code, where 290X is assumed to be a 4GB card, while it's not always true...

