Vasily Galkin

This doesn't look like a problem with VRAM. It more looks like special driver reservation. The heap size output below the red rect shows that the vulkan driver reports only...

GPU-Z screenshow looks fine. (BTW vulkan heap sizes are visible in the GPU-Z too on the Advanced->Vulkan page). Typically the third heap is related to PCIe Bar/resizable bar. It is...

Vulkan API can have several memory types for each memory heap. It seems that GPU-Z lists memory types, not memory heaps If you rename `memtest-vulkan.exe` by adding `verbose` to the...

Unfortunately, memory reserved/placed in another heap by the driver can't be tested in current memtest_vulkan paradigm. From my practice in VRAM testing - for stability testing 70% of memory is...

The memory size displayed in the GPU list id rounded up to 1GB. But according to logs and vulkaninfo the vulkan rumtime reports only 256MB usable GPU-DeviceLocal memory **total**. (I'm...

Thanks, great investigation. I rechecked my previous experiments - and indeed the smallest DeviceLocal memory I tested was 1 GB, not 512MB. So the 1 GB appears to be the...

I'm not sure if vulkan allows shaders accessing memory types that lacks DEVICE_LOCAL_BIT. I suppose that it is a somewhat strange behaviour of the driver to report such small memory...

Thanks for detailed reporting. It seems taht both modes allows allocation size greater than heap size reported by vualkn API. So, I'll try to implement a fix that allows allocating...

Similar problem with AMD Radeon R7 (device 1002 9874 1043 8719) - device-local is reported as 256MB, but actually up to 4GB works (windows driver U0382934-Radeon-Software-Adrenalin-2020-22.6.1)

Thanks for reporting. In general, the misdetection of total memory size shouldn't lead to total freeze since memtest_vulkan is using autodetection of the size of the actually usable memory. However...