chipintegrity.org GitHub
EVIDENCE

Results from every chip measured

Every row on this page is generated from a result file in the repository, and every chip also has its own page with the full detail. Nothing here is modelled or estimated.

ON THIS PAGE YOU WILL LEARN
  1. Which chips have been measured, and when
  2. What each probe found on each chip
  3. Where to download every raw result file
EXPLORE

Compare two chips

Pick two chips to see, side by side, how close each came to its proven error limit in every precision and kernel, and how many planted faults each caught.

EVIDENCE

Measured results

Every row comes from a result file in the repository, and the tables are generated from those files. Nothing here is modelled or estimated.

One page per chip

Each chip has its own page with every step of every probe, the setup, the self-test and the result files. All chips on one page.

Compute probe

DeviceDateShapes (M×K×N)PrecisionsRunsSilent faultsInjected caughtVerdictFiles
NVIDIA H100 80GB HBM3PyTorch 2.8.0+cu128 · tool v0.3.2 · error counters quiet 2026-10-10 1024x1024x1024
4096x4096x4096
32x4096x11008
fp32, fp16, bf16, int8, fp8, fp8fast 900 0 90 of 90 no-silent-errors clean · self-test
NVIDIA A100-SXM4-80GBPyTorch 2.8.0+cu128 · tool v0.2.0 2026-10-07 1024x1024x1024
4096x4096x4096
32x4096x11008
fp32, fp16, bf16, int8 600 0 60 of 60 no-silent-errors clean · self-test
NVIDIA GeForce RTX 4090PyTorch 2.8.0+cu128 · tool v0.3.2 · ECC off, so the error counters cannot see memory errors 2026-10-11 1024x1024x1024
4096x4096x4096
32x4096x11008
fp32, fp16, bf16, int8, fp8, fp8fast 900 0 90 of 90 no-silent-errors clean · self-test
NVIDIA H200PyTorch 2.8.0+cu128 · tool v0.2.0 2026-10-08 1024x1024x1024
4096x4096x4096
32x4096x11008
fp32, fp16, bf16, int8 600 0 60 of 60 no-silent-errors clean · self-test
NVIDIA RTX A5000PyTorch 2.8.0+cu128 · tool v0.3.2 · ECC off, so the error counters cannot see memory errors 2026-10-11 1024x1024x1024
4096x4096x4096
32x4096x11008
fp32, fp16, bf16, int8 (6 skipped) 600 0 60 of 60 no-silent-errors clean · self-test
Apple GPU (MPS) arm64PyTorch 2.14.1 · tool v0.2.0 2026-10-07 1024x1024x1024
4096x4096x4096
32x4096x11008
fp32, fp16, bf16 (3 skipped) 450 0 45 of 45 no-silent-errors clean · self-test

Kernel probe

DeviceDateKernelsPrecisionsRunsWorst error / boundSilent faultsInjected caughtVerdictFiles
NVIDIA H100 80GB HBM3PyTorch 2.8.0+cu128 · tool v0.2.2 · error counters quiet 2026-10-10 softmax, layernorm, gelu, rope, attention4096×4096; rope 4096×128; attention 8×1024×128 · attention: efficient (fp32); flash (fp16, bf16) fp32, fp16, bf16 375 0.999 0 45 of 45 no-silent-errors clean · self-test
NVIDIA GeForce RTX 4090PyTorch 2.8.0+cu128 · tool v0.2.2 · ECC off, so the error counters cannot see memory errors 2026-10-11 softmax, layernorm, gelu, rope, attention4096×4096; rope 4096×128; attention 8×1024×128 · attention: efficient (fp32); flash (fp16, bf16) fp32, fp16, bf16 375 0.999 0 45 of 45 no-silent-errors clean · self-test
NVIDIA RTX A5000PyTorch 2.8.0+cu128 · tool v0.2.2 · ECC off, so the error counters cannot see memory errors 2026-10-11 softmax, layernorm, gelu, rope, attention4096×4096; rope 4096×128; attention 8×1024×128 · attention: efficient (fp32); flash (fp16, bf16) fp32, fp16, bf16 375 0.999 0 45 of 45 no-silent-errors clean · self-test
Apple GPU (MPS) arm64PyTorch 2.14.1 · tool v0.2.0 2026-10-10 softmax, layernorm, gelu, rope, attention4096×4096; rope 4096×128; attention 8×1024×128 fp32, fp16, bf16 375 0.999 0 45 of 45 no-silent-errors clean · self-test

Worst error over bound is the largest measured error on the device divided by the bound at that element, across every kernel and precision. Values near 1 at fp16 and bf16 are expected: there the bound is dominated by the single rounding of the output, so there is almost nothing to spare. A value above 1 is a failed run. On NVIDIA GPUs the row also names the fused attention kernel that ran in each precision: flash, cuDNN or memory-efficient.

Checksum probe

DeviceDateShapesPrecisionsRunsSilent faultsBlind-spot runsThreshold / typical valueInjected locatedVerdictFiles
NVIDIA H100 80GB HBM3PyTorch 2.8.0+cu128 · tool v0.1.0 · error counters quiet 2026-10-10 1024x1024x1024
32x4096x11008
fp32, fp16, bf16 120 0 0 827.15 18 of 18 no-silent-errors clean · self-test
NVIDIA GeForce RTX 4090PyTorch 2.8.0+cu128 · tool v0.1.0 · ECC off, so the error counters cannot see memory errors 2026-10-11 1024x1024x1024
32x4096x11008
fp32, fp16, bf16 120 0 0 827.15 18 of 18 no-silent-errors clean · self-test
NVIDIA RTX A5000PyTorch 2.8.0+cu128 · tool v0.1.0 · ECC off, so the error counters cannot see memory errors 2026-10-11 1024x1024x1024
32x4096x11008
fp32, fp16, bf16 120 0 0 827.15 18 of 18 no-silent-errors clean · self-test
Apple GPU (MPS) arm64PyTorch 2.14.1 · tool v0.1.0 · no error counters 2026-10-10 1024x1024x1024
32x4096x11008
fp32, fp16, bf16 120 0 0 827.15 18 of 18 no-silent-errors clean · self-test

Threshold over typical value is how large an error must be, compared with a typical element of C, before a proven checksum is guaranteed to see it, at the worst precision and shape. It is set by the shape, the precision and the arithmetic model, not by the chip's answers, because the threshold adds up the worst-case rounding of every element in a row: on the H100 it runs from 2.3 (fp32 at 1024×1024×1024) to 827 (bf16 at 32×4096×11008). Below it, the reference and repeat checks carry the smaller faults. Blind-spot runs are runs the reference check failed while every checksum held.

Data pattern probe

DeviceDatePatternsPrecisionsRunsSilent faultsInjected caughtSubnormal inputsVerdictFiles
NVIDIA H100 80GB HBM3PyTorch 2.8.0+cu128 · tool v0.1.2 · error counters quiet 2026-10-10 wide, mantissa, cancel, alternate, sparse, subnormal, near_max, extremes fp32, fp16, bf16, int8, fp8, fp8fast 1,120 0 168 of 168 kept no-silent-errors clean · self-test
NVIDIA GeForce RTX 4090PyTorch 2.8.0+cu128 · tool v0.1.2 · ECC off, so the error counters cannot see memory errors 2026-10-11 wide, mantissa, cancel, alternate, sparse, subnormal, near_max, extremes fp32, fp16, bf16, int8, fp8, fp8fast 1,120 0 168 of 168 kept no-silent-errors clean · self-test
NVIDIA RTX A5000PyTorch 2.8.0+cu128 · tool v0.1.2 · ECC off, so the error counters cannot see memory errors 2026-10-11 wide, mantissa, cancel, alternate, sparse, subnormal, near_max, extremes fp32, fp16, bf16, int8 (8 skipped) 960 0 144 of 144 kept no-silent-errors clean · self-test
Apple GPU (MPS) arm64PyTorch 2.14.1 · tool v0.1.0 2026-10-10 wide, mantissa, cancel, alternate, sparse, subnormal, near_max fp32, fp16, bf16 (14 skipped) 840 0 126 of 126 flushed: fp32, bf16 no-silent-errors clean · self-test

Subnormal inputs says whether the chip kept or flushed subnormal inputs to zero, per precision and measured at each shape. Either is allowed; the probe measures which, then checks the chip against that exact model. Mixed means a kernel kept them in some places and flushed them in others.

Memory probe

DeviceDateMemory testedPatternsDwellBad wordsInjected caughtVerdictFiles
NVIDIA H100 80GB HBM3tool v0.1.1 · error counters quiet 2026-10-10 62.75 GiB of 79.18 GiB16,844,324,864 words 6 2.0 s 0 30 of 30 no-memory-errors clean · self-test
NVIDIA A100-SXM4-80GBtool v0.1.0 2026-10-07 63.00 GiB of 79.25 GiB16,911,433,728 words 6 2.0 s 0 30 of 30 no-memory-errors clean · self-test
NVIDIA GeForce RTX 4090tool v0.1.1 · ECC off, so the error counters cannot see memory errors 2026-10-11 18.50 GiB of 23.52 GiB4,966,055,936 words 6 2.0 s 0 30 of 30 no-memory-errors clean · self-test
NVIDIA H200tool v0.1.0 2026-10-08 111.25 GiB of 139.81 GiB29,863,444,480 words 6 2.0 s 0 30 of 30 no-memory-errors clean · self-test
NVIDIA RTX A5000tool v0.1.1 · ECC off, so the error counters cannot see memory errors 2026-10-11 18.50 GiB of 23.55 GiB4,966,055,936 words 6 2.0 s 0 30 of 30 no-memory-errors clean · self-test
Apple GPU (MPS) arm64tool v0.1.0 2026-10-07 5.50 GiB of 11.84 GiB1,476,395,008 words 6 2.0 s 0 30 of 30 no-memory-errors clean · self-test

Rented data centre GPUs are young, monitored and already screened, so clean rows are the expected result there. The research says faults concentrate in aged units and appear under data-dependent, long, hot workloads. Those are the next probes on the roadmap, and where the first real findings are expected.