GPU Texture Integrity and VRAM Limits
Understand the bounded texture readback check, allocation estimates, sampled mismatches, and why a browser run cannot validate all physical GPU memory.
What the round-trip check does
The integrity workload writes known RGBA8 patterns to bounded textures, renders them, and compares sampled readback values with the expected pattern. The counters describe values checked and mismatches observed by this software path. A clean run means those sampled values matched during that run, not that every memory cell was tested.
Allocation budget is not installed VRAM
The allocation budget limits requested texture storage for the test. It is not a measurement of installed, free, or resident GPU memory. Browser and driver implementations may copy, pool, or relocate resources. Integrated graphics may share system memory. Larger allocations also risk resource pressure without improving coverage of physical addresses.
Treat mismatches as observations
A mismatch can indicate a software, format, synchronization, browser, driver, or hardware problem. This check alone cannot distinguish them. Save the report and repeat at a lower budget. Compare a supported browser or another workload before assuming physical memory failure; do not infer a defect from an unsupported operation.
Use physical diagnostics for persistent faults
If corruption or crashes also occur in native applications, stop stress testing and follow the device manufacturer guidance. Keep reproduction steps, drivers, and report settings. A browser texture test cannot access the full address space, guarantee data retention, certify a repair, or decide whether the card should be replaced.