Jump to content
Toggle menu
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

Voltage-glitch unlock (GA100VFI)

From CMP Wiki

GA100VFI (GA100 voltage fault injection) is the hardware unlock for the 8 GB CMP 170HX. A short dip in the GPU core voltage while the card senses its fuses makes the fuse that blocks the software override read wrong for that boot. With the gate open, the owner appends permanent fuseless-fuse (FF) records that change the card's floorsweep and PCIe options. The glitch itself changes nothing permanent. The records you burn do.

Kate Land published the method on 2026-11-10 in her blog post Using voltage glitching to unleash the A100 in my mining card, with her board, firmware and analysis in kate-land/ga100vfi. Her own results (80 GiB on nine of ten 8 GB cards, about 120-126 SMs) are on 8 GB compute and HBM. Since 2026-11-13 members have reproduced it with a Raspberry Pi Pico 2 in place of her board. The glitch tools only get you to the open gate: what to burn is per card, and you work it out from your own fuse read. On the 10 GB card the gate is opened by an RIR burn instead, with no glitch (RIR fuse burn).

Reported 8 GB
Source: repo github.com/kate-land/ga100vfi by kate-land on GitHub, 2026-11-10
Source: @m3gagluk, 2026-11-11 (CMP 170hx Clean Room Discussion server)
Source: @galygious, 2026-11-15
Source: @petrikrohn_26497, 2026-11-16 (CMP 170hx Clean Room Discussion server)

Warning Fuse burns are one-way. OTP bits go from 0 to 1 and never back. Fuses are individual per card: never burn from another card's plan. One card has already been stuck by a wrong row. Read Unlock without bricking and Fuses and floorsweep maps before you burn anything, and the safety rules below.

Source: @port00, 2026-11-17
Source: @wakeupmbrc1, 2026-11-17
Source: @zagitta, 2026-11-18

Status and reported outcomes

In date order, as members posted them. The method details stay in the authors' repos.

Before 10 November: why the 8 GB card needed a hardware route

On 2026-07-27 @paulbenjamin forced the GPC mask on an 8 GB card from 0xdc to 0xff three ways: the RM floorsweep structure, a host MMIO write and a patched GSP firmware instruction. Software then reported 8 GPCs and 112 SMs, but the hardware register read back 0xdc every time and cuInit segfaulted. On 2026-10-03 @akuchen_66498 measured that setting EN_SW_OVERRIDE to 1 changes nothing while DISABLE_SW_OVERRIDE_STATUS (0x820084) reads 1: the software fuse write (SW-IFF) never commits, its busy flag stays at 1, and the SM count does not move. On 2026-10-17 @mountains1605 hit the same wall writing feature registers directly, and @matstatman put it this way: EN_SW_OVERRIDE and DISABLE_SW_OVERRIDE_STATUS "opens all the door, if you are able to write to them". @stsoftware_88487 wrote the GPC status as DISABLE | DEFECTIVE | CTRL | (RECONFIG & ~OVERRIDE), and @matstatman concluded you cannot beat the fuse that way. On the 8 GB card that gate needs the glitch; on the 10 GB card, the RIR burn.

Reported 8 GB
Source: @paulbenjamin, 2026-07-27 (CMP 170hx Clean Room Discussion server)
Source: @akuchen_66498, 2026-10-03 (CMP 170hx Clean Room Discussion server)
Source: @matstatman, 2026-10-11 (CMP 170hx Clean Room Discussion server)
Source: @stsoftware_88487, 2026-10-11 (CMP 170hx Clean Room Discussion server)
Source: @mountains1605, 2026-10-17 (CMP 170hx Clean Room Discussion server)
Source: @matstatman, 2026-10-17 (CMP 170hx Clean Room Discussion server)

The idea and the first rigs, June to October

On 2026-06-27, the clean room server's first day, @m3gagluk linked the Tegra fault-injection paper "The Forgotten Threat of Voltage Glitching: A Case Study on Nvidia Tegra" (arXiv 2108.06131). On 2026-07-05 @bigptoughneigh posted that his AI assistant told him he would have to start hardware glitching. On 2026-10-02 @dalzyyy had "still haven't given up on the idea of voltage glitching", and on 10-03 @petrikrohn_26497 wrote that the fuse bits need not flip for good, only read differently for a moment so other fuses can be written. @petrikrohn_26497 also recalled (10-28) that very early in the research a member put an RP2040 on the card's SMI bus (as written) to sniff addresses; the results were inconclusive and were lost with the old Discord server. From 2026-10-24 @dalzyyy worked on the core voltage controller, an MP2888B (marking mp2888bgu, no public datasheet per @shirogeek). Over PMBus he saw the GA100 request about 0.7 V until the OS loads, and on 10-31 he found HBMVDD fixed at 1.25 V and not driven by PWMVID. He kept a card whose HBM seemed to be dying (an instant Xid in memtest_vulkan) for glitching tests.

Reported 8 GB and 10 GB
Source: @m3gagluk, 2026-06-27 (CMP 170hx Clean Room Discussion server)
Source: @bigptoughneigh, 2026-07-05 (CMP 170hx Clean Room Discussion server)
Source: @dalzyyy, 2026-10-02 (CMP 170hx Clean Room Discussion server)
Source: @petrikrohn_26497, 2026-10-03 (CMP 170hx Clean Room Discussion server)
Source: @dalzyyy, 2026-10-24 (CMP 170hx Clean Room Discussion server)
Source: @shirogeek, 2026-10-24 (CMP 170hx Clean Room Discussion server)
Source: @dalzyyy, 2026-10-24 (CMP 170hx Clean Room Discussion server)
Source: @dalzyyy, 2026-10-25 (CMP 170hx Clean Room Discussion server)
Source: @dalzyyy, 2026-10-25 (CMP 170hx Clean Room Discussion server)
Source: @petrikrohn_26497, 2026-10-28 (CMP 170hx Clean Room Discussion server)
Source: @dalzyyy, 2026-10-31 (CMP 170hx Clean Room Discussion server)

Kate Land's write-up and what she said after it

Kate (@onemillionkates) published on 2026-11-10. Asked on 11-11 whether the final waveform is universal and only the timing needs adjusting, she answered: "No, you will need much trial and error. But I'm pretty sure there is a waveform for every die". On 11-13 she said she does not offer the unlock as a service and had not glitched all of her own cards: "at this point I am reasonably certain it is reliable on every die". When @deejay9983 doubted the write-up on 11-13 because it showed no screenshots or video, she answered that screenshots and videos are trivially fakeable and the only proof worth giving is all the details and third parties reproducing it. On 11-16 he withdrew his doubt: "You did something that no one thought could be done". She calls her own PCB a proof of concept and points people to the Pico tools (see the tools).

Reported 8 GB
Source: @wakeupmbrc1, 2026-11-11
Source: @onemillionkates, 2026-11-11
Source: @deejay9983, 2026-11-13
Source: @onemillionkates, 2026-11-13
Source: @onemillionkates, 2026-11-13
Source: @onemillionkates, 2026-11-13
Source: @onemillionkates, 2026-11-13
Source: @onemillionkates, 2026-11-16
Source: @onemillionkates, 2026-11-16
Source: @deejay9983, 2026-11-16

First reproductions, 12 and 13 November

On 2026-11-12 @dalzyyy reported in the clean room server that he had DSOV flipped and "the correct fuse states rn to start burning" on an 8 GB card, and SW-IFF (the volatile software override) working on it, though the driver would not load yet. On 11-13 he posted a photo in the main server: his CMP was "burned to a100", in one shot. He used a Raspberry Pi Pico 2, not Kate's STM32 board (@cute_sc2, @finishtilt14). With "the method from the other researcher" he gets there "under <100 tries almost always", "<2 mins normally", and "Only pico 2 is needed". He pointed to his own repo, dalzyu/pico-ga100vfi, and JosiahWhite/rp2040-glitch-tool, the other researcher's ("pick your poison"). Kate: "yes it's legit, you should use these rather than my proof of concept slop fest"; she was hearing they do the job in a few minutes against hours. No memory or SM figures were posted in text with this first card.

Reported 8 GB
Source: @dalzyyy, 2026-11-12 (CMP 170hx Clean Room Discussion server)
Source: @dalzyyy, 2026-11-12 (CMP 170hx Clean Room Discussion server)
Source: @dalzyyy, 2026-11-12 (CMP 170hx Clean Room Discussion server)
Source: @dalzyyy, 2026-11-13 (CMP 170hx Clean Room Discussion server)
Source: @dalzyyy, 2026-11-13 (CMP 170hx Clean Room Discussion server)
Source: @dalzyyy, 2026-11-13
Source: @dalzyyy, 2026-11-13
Source: @cute_sc2, 2026-11-13
Source: @finishtilt14, 2026-11-13
Source: @dalzyyy, 2026-11-13 (CMP 170hx Clean Room Discussion server)
Source: @dalzyyy, 2026-11-13 (CMP 170hx Clean Room Discussion server)
Source: @dalzyyy, 2026-11-13 (CMP 170hx Clean Room Discussion server)
Source: @dalzyyy, 2026-11-13 (CMP 170hx Clean Room Discussion server)
Source: @onemillionkates, 2026-11-13 (CMP 170hx Clean Room Discussion server)
Source: @onemillionkates, 2026-11-13 (CMP 170hx Clean Room Discussion server)

Who was building, 11 to 15 November

Between 11-11 and 11-13: @ghostinthedatacenter_87281 ordered PCBs and stencils, @c133 the PCB and BOM from JLCPCB, @shirogeek the PCB on JLC; @tekkenz had an FPGA board and was gathering the rest of the BOM; @scallion_9883 was refining a Pico and VRM method with 20 cards to work through; @cute_sc2 would "go the safe route" with Kate's PCB. @marklintonca wanted independent verification first, and @wakeupmbrc1 noted that Kate did not kill a single card. On 11-14 @lia_oc said "lots" had tried it on 8 GB cards ("its real"): burning FF rows on the 8 GB card was not possible before Kate's finding, the hard part is done, and what is left is "figuring out what to/not to burn". @killred still had "no idea how to do ff program after the glitch", and @globalapathy called a tool that writes the plan to the card "the missing piece". On 11-15 @zagitta answered a member, relayed by @galygious, whose AI models gave different values: "There's no public recipe for the FF programming for legal reasons" (posted in Russian and English). Tools followed on 11-16 and 11-17 (see fuse capture and burn-plan tools).

Reported 8 GB
Source: @tekkenz, 2026-11-11
Source: @ghostinthedatacenter_87281, 2026-11-11
Source: @marklintonca, 2026-11-11
Source: @c133, 2026-11-11
Source: @wakeupmbrc1, 2026-11-11
Source: @scallion_9883, 2026-11-12
Source: @scallion_9883, 2026-11-12
Source: @cute_sc2, 2026-11-12
Source: @shirogeek, 2026-11-12
Source: @killred, 2026-11-14
Source: @lia_oc, 2026-11-14
Source: @lia_oc, 2026-11-14
Source: @lia_oc, 2026-11-14
Source: @lia_oc, 2026-11-14
Source: @globalapathy, 2026-11-14
Source: @galygious, 2026-11-15
Source: @zagitta, 2026-11-15

Finished cards, 15 to 18 November

  • On 11-15 @nolmerportion posted a photo ("it was quite tough") and said he had unlocked the VRAM and SMs but was holding off on the PCIe part for fear of bricking the card. The same card was posted on Reddit (r/LocalLLaMA) and X as 80 GB. @lia_oc said he would not share how he did it. Source: @nolmerportion, 2026-11-15
    Source: @nolmerportion, 2026-11-15
    Source: @dany0_, 2026-11-15
    Source: @lia_oc, 2026-11-15
  • On 11-16 @kingsizexxxl said a Pico "glitches fine", @lia_oc that multiple people had replicated Kate's result on the 8 GB card, and @mellojello_ counted "~15 people" who had replicated it (no list). Source: @kingsizexxxl, 2026-11-16 (CMP 170hx Clean Room Discussion server)
    Source: @mellojello_, 2026-11-16
    Source: @lia_oc, 2026-11-16
  • On 11-17 @.shakdiesel reached the glitch success state (the tools call it Goldilocks) and finished his card. The wiring and soldering were "diabolical" and the wires kept coming off the pads; he recommends a digital microscope. @ichundes did two cards with a Pico 2: one was easy, the other had to get up to temperature first. Source: @.shakdiesel, 2026-11-17
    Source: @.shakdiesel, 2026-11-17
    Source: @.shakdiesel, 2026-11-17
    Source: @.shakdiesel, 2026-11-17
    Source: @ichundes, 2026-11-17
  • On 11-17 @zanooda: "it really works", "memtest passes, pcie gen4 works", 112 SMs. Source: @zanooda, 2026-11-17
    Source: @zanooda, 2026-11-17
    Source: @zanooda, 2026-11-17
  • On 11-17 @jonathanyjoerrington ran a per-SM stress test (written by @samuel_hayden.) on his burned 8 GB card: "covered 126/126 target SMs" for 60 s, 276 launches, "All good". Source: @jonathanyjoerrington, 2026-11-17
    Source: @jonathanyjoerrington, 2026-11-17
  • On 11-18 @killred finished his first card and then his second, and called the step after the glitch "Fully automated unlock after Goldilocks" on his side (his own planner, not yet public). Source: @killred, 2026-11-18
    Source: @killred, 2026-11-18
    Source: @killred, 2026-11-18
  • On effort: @_arcanum_ thinks the glitch takes fewer work hours than the x16 capacitor mod, and @kingsizexxxl that working out the FF burns took a lot longer than the glitch. Asked whether the mod can be ported to software, @killred said no and @wakeupmbrc1 that people have explored every single bit. Source: @_arcanum_, 2026-11-17
    Source: @kingsizexxxl, 2026-11-17
    Source: @killred, 2026-11-18
    Source: @wakeupmbrc1, 2026-11-18

Several members finished 8 GB cards past the 74-SM software limit, two of them with numbers (112 SMs with memtest and Gen4; 126 of 126 SMs under a stress test).

Proven 8 GB
Source: @jonathanyjoerrington, 2026-11-17
Source: @zanooda, 2026-11-17
Source: @zanooda, 2026-11-17

The lab's two finished cards, 18 and 19 November

The lab glitched four of its own 8 GB cards with a Pico 2 W and finished two: 122 and 120 SMs (126 and 124 with the RECONFIG override), the 80 GB memory layout in the fuses, and PCIe fuses that advertise 2.5-16 GT/s, all read after a cold boot. A third card never reached the window in about 4,000 shots, and the fourth has no core rail. Setup, tool fixes and burn flow: Voltage-glitch unlock: lab method on a Pico 2 W. Results, the exact memory and PCIe FF records and the Gen3 fuse bit: Voltage-glitch unlock: lab results and fuse findings.

Proven 8 GB
Source: @darkmaniac7, 2026-11-19 (lab notes)

Memory and SM counts members post

  • Before the write-up (11-05 and 11-06, how the counts were read is not stated): @_orrorin: "only 80SM work" on his cards; @mbelli: "Through 15 the lowest I saw was 96 with most in the 120s", and he had heard 110 was the average. Source: @_orrorin, 2026-11-05 (CMP 170hx Clean Room Discussion server)
    Source: @mbelli, 2026-11-06 (CMP 170hx Clean Room Discussion server)
  • On 11-16 owners posted their batches, partly as unlock-potential readings from a check script rather than finished unlocks: @gnasherrr 7 of 8 cards at 80 GB and "1 dud" at 64 GB (124 SMs), one card at 128 SMs and 80 GB, one at 110 and 80, only one below 120; @jj48. one of four only "64gb unlockable" although it has all 124 SMs, and two at 108 and 112; @replacedriver47 one of four at 64 GB; @deejay9983 one of six at 64 GB. @nemz38_is_my_waifu_91412 said his check does not show the SM count accurately, at least in its summary. @zagitta noted that a retail A100 has 108 SMs, and @rangednyarnyar would take a full-SM 64 GB card over 80 GB for int8 throughput. Source: @zagitta, 2026-11-16
    Source: @replacedriver47, 2026-11-16
    Source: @jj48., 2026-11-16
    Source: @gnasherrr, 2026-11-16
    Source: @rangednyarnyar, 2026-11-16
    Source: @gnasherrr, 2026-11-16
    Source: @gnasherrr, 2026-11-16
    Source: @jj48., 2026-11-16
    Source: @gnasherrr, 2026-11-16
    Source: @gnasherrr, 2026-11-16
    Source: @rangednyarnyar, 2026-11-16
    Source: @nemz38_is_my_waifu_91412, 2026-11-16
    Source: @deejay9983, 2026-11-16
  • On 11-17 @.shakdiesel burned his fuses and got 124 SMs "but not the additional 16GB it claimed it can do, it's only at 64 gb". @anon33anon asked owners to post the full 512-row read before and after a burn, "if we collect enough of those maybe we can build a better ff calc". Source: @.shakdiesel, 2026-11-17
    Source: @.shakdiesel, 2026-11-17
    Source: @anon33anon, 2026-11-17
    Source: @anon33anon, 2026-11-17

Reported 8 GB The 64 GB cards are covered under buying.

OpenCL-Benchmark on an unlocked card

@kingsizexxxl posted OpenCL-Benchmark output from his hardware-unlocked card on 2026-11-16: 122 compute units at 1410 MHz (listed as 7808 cores, 22.019 TFLOPs/s); FP64 10.803, FP32 21.732 and FP16 (half2 FMA) 81.873 TFLOPs/s; memory 1535.11 GB/s coalesced read, 1820.42 GB/s coalesced write, 1381.14 GB/s misaligned read and 239.25 GB/s misaligned write; PCIe 11.00 GB/s send and 10.91 GB/s receive (Gen3 x16). These are vector FMA figures, not tensor-core throughput. Kate's published run shows about 85.9 TFLOP/s FP16 at 124 compute units.

Reported 8 GB
Source: @kingsizexxxl, 2026-11-16
Source: @kingsizexxxl, 2026-11-16

What cmpunlocker shows on an unlocked card

On 11-17 @.shakdiesel asked whether cmpunlocker was only showing 64 GB on his freshly unlocked card. @ob88594: some versions in circulation only unlock 64 GB; flash the A100 80 GB VBIOS. @.shakdiesel was stuck on cmpunlocker's original frame geometry, fixed it ("I think it should get to 80gb") and posted a screenshot ("standing on the shoulders of giants"). On 11-18 @killred wrote that mainline cmpunlocker does not yet support an 80 GB unlocked card: a patch is needed for the driver to use the 80 GB and to support PCIe 4.0. No patch was linked. After an FF burn cmpunlocker still added 4 SMs on one card (the RECONFIG override); @dalzyyy: you "need clear RECONFIG for your GPCs". @reala7096 asked how to make that persistent; his best guess was OPT_TPC_GPC0_RECONFIG, with no known FF block or bit. Unanswered.

Reported 8 GB
Source: @.shakdiesel, 2026-11-17
Source: @ob88594, 2026-11-17
Source: @.shakdiesel, 2026-11-17
Source: @.shakdiesel, 2026-11-17
Source: @ob88594, 2026-11-17
Source: @.shakdiesel, 2026-11-17
Source: @dalzyyy, 2026-11-17
Source: @dalzyyy, 2026-11-17
Source: @reala7096, 2026-11-17
Source: @killred, 2026-11-18

PCIe Gen3 and Gen4 after the glitch

On 11-15 @kingsizexxxl had written some blocks and got it "half working": the right blocks worked, "it just needs more", and he decided it could wait a week. @lia_oc: "that info isn't yet public/no tool yet to do it for you"; @froggao and @a1rm4x would hold off until everything works. On 11-17 @jonathanyjoerrington's burned 8 GB card, read with no cmpunlocker, did not reach Gen3: the Gen3 helper from his cmpunlocker v0.5 folder set speeds 1 and 2, then failed with SET_PCIE_SPEED failed status=0x56, although he says he burned the necessary rows. @68x0 asked for his FF rows. The same day @zanooda reported Gen4 working, and on 11-18 @killred that mainline cmpunlocker needs a patch for PCIe 4.0 on these cards. Kate's write-up reports Gen3 and Gen4 training.

Reported 8 GB
Source: @kingsizexxxl, 2026-11-15
Source: @froggao, 2026-11-15
Source: @kingsizexxxl, 2026-11-15
Source: @lia_oc, 2026-11-15
Source: @jonathanyjoerrington, 2026-11-17
Source: @68x0, 2026-11-17
Source: @zanooda, 2026-11-17
Source: @killred, 2026-11-18

Lab, 2026-11-19: three chain-2 FF records (block 47 bit 3, block 49 bit 7, block 39 bit 9) made LnkCap2 advertise 2.5-16 GT/s on two 8 GB cards after a cold boot. OPT_DISABLE_GEN3_SPEED (0x820250) is block 39 bit 9; a record clearing bit 1 left it at 1. The link itself still needs the driver route. Records and old values: the lab results.

Proven 8 GB
Source: @darkmaniac7, 2026-11-19 (lab notes)

Still open after the glitch: SS0 and SS1, ECC, the last 4 SMs

On 11-15 @zagitta reported that writing SS0 and SS1 through IFF worked for him (method not public). On 11-16 @truvv0r found nothing in the IFF program related to the SS0/SS1 limit, only rumours. On 11-17 @reala7096, planning his first burns, found "no info about FF records for compute throttling, the extra 4SM and ECC as of now" and was waiting for the rest of the FF patches before his first glitch. @dalzyyy: ECC also needs the row remapper and poison containment, not just the enable. @kingsizexxxl: "The iff is interesting".

Reported 8 GB
Source: @zagitta, 2026-11-15 (CMP 170hx Clean Room Discussion server)
Source: @truvv0r, 2026-11-16 (CMP 170hx Clean Room Discussion server)
Source: @reala7096, 2026-11-17
Source: @kingsizexxxl, 2026-11-17
Source: @reala7096, 2026-11-17 (CMP 170hx Clean Room Discussion server)
Source: @reala7096, 2026-11-17
Source: @dalzyyy, 2026-11-17 (CMP 170hx Clean Room Discussion server)

Glitcher builds and tools

State on 2026-11-18, from the posts and from the READMEs as members quoted them. The authors' repos are the place for the current firmware and scripts. Most of this tooling is days old, much of it written with AI assistants, and tested on few cards. A tool that builds a plan from your own card is not a plan you can skip checking.

Tool What it does State on 2026-11-18 Source
kate-land/ga100vfi (Kate's STM32 board) The original glitcher: an STM32G4 board (STM32G431CBT6), firmware and analysis. Taps NVVDD and NVVDD_PWMVID_IN and removes one 0402 resistor. Proof of concept. The author calls her PCB AI-generated and "not even remotely a good board" (no gpio0 exposed) and tells people to use the Pico tools. Reported at 1 to 48 hours per card. A broken test was fixed on 11-11 after @c133's report. Source: repo github.com/kate-land/ga100vfi by kate-land on GitHub, 2026-11-10
Source: @c133, 2026-11-11
Source: @onemillionkates, 2026-11-11
Source: @c133, 2026-11-11
Source: @onemillionkates, 2026-11-12
Source: @onemillionkates, 2026-11-12
Source: @onemillionkates, 2026-11-13
Source: @c133, 2026-11-15
dalzyu/pico-ga100vfi The glitch step on a Raspberry Pi Pico 2 class board (RP2350: Pico 2, Pico 2 W, Waveshare Plus-W). Drives the core-voltage dip over the card's own I2C link to the voltage controller and resets the card through PEX_RST so it re-senses its fuses. MIT licence. By @dalzyyy. Glitch only: the FF records are yours to plan. README: tested on one card, other cards may need tuning (adaptive calibration mode), repeated glitching stresses the VRM, at your own risk. The adaptive search was fixed on 11-17 ("pls pull the latest commit"); on 11-18 it still varies only v_dip. Source: @dalzyyy, 2026-11-13 (CMP 170hx Clean Room Discussion server)
Source: @mbelli, 2026-11-15
Source: @mbelli, 2026-11-15
Source: @galygious, 2026-11-15
Source: @dalzyyy, 2026-11-17
Source: @dalzyyy, 2026-11-17
Source: @dalzyyy, 2026-11-18
clee/pico-ga100vfi (branch port/rp2040-kb2040) Fork of the above with RP2040 support Posted 11-17 by @c133. The RP2350 Pico 2 is the best-supported path. Source: @c133, 2026-11-17 (CMP 170hx Clean Room Discussion server)
JosiahWhite/rp2040-glitch-tool USB CDC firmware and a Python API that let an RP2040 drive an external glitch circuit (I2C transfers, GPIO pulse sequences, PWM) Application release 1.0 per its README, which says the GPIO must drive an external glitch circuit and never a power rail directly, and that a failed voltage restore can leave a VRM low. The dalzyu README credits its author (@mellojello_) with proving the I2C path first. Source: @dalzyyy, 2026-11-13 (CMP 170hx Clean Room Discussion server)
Source: @ob88594, 2026-11-14
portz3r0/pico-ga100vfi-console A fuse console for the Pico glitcher: a live fuse-dump view and an inspector for the dump file By @port00, "still improving so be gentle", tested on his own card (the one stuck and restored, see brick reports). @jbranco91 suggested a check that reads each target row from the dump before a burn, to stop a fat-fingered value. Source: @port00, 2026-11-17
Source: @port00, 2026-11-17 (CMP 170hx Clean Room Discussion server)
Source: @jbranco91, 2026-11-17 (CMP 170hx Clean Room Discussion server)
Source: @jbranco91, 2026-11-17 (CMP 170hx Clean Room Discussion server)
Source: @port00, 2026-11-17 (CMP 170hx Clean Room Discussion server)
Source: @port00, 2026-11-17 (CMP 170hx Clean Room Discussion server)
kprinssu/ga100-ff-tools FF row capture and a per-card burn-plan generator, made more generic from the CMPGlitch work Published 11-17 by @68x0 ("most of the unlocks in an easy to go package"). AI-written, spot-checked by him: the bitmasks look right for compute, memory and Gen4, the chains and rows still to be checked. No burn with it reported by 11-18. Source: @68x0, 2026-11-16
Source: @68x0, 2026-11-16
Source: @68x0, 2026-11-17
Source: @68x0, 2026-11-17
matstatman/gpcprobe Read-only GPC, TPC and FBP fuse readout, see gpcprobe The read members point to for planning ("Use gpcprobe", @68x0). One 10 GB owner saw its spare-fuse line at 16/16 active although the RIR tool reads her gate burn as done (unresolved, see 10 GB). Source: @68x0, 2026-11-16
Source: @68x0, 2026-11-16
Source: @lycorascence, 2026-11-18
sayhellotojungle/cmp170hx-ffcalc Read-only fuse scan that predicts SM count and 64 or 80 GB, plus a burn plan, see cmp170hx-ffcalc Contested (below): its SM and memory readings matched gpcprobe on one card, its burn plan was called broken. "If you yolo ffcalcs you will brick your card." Source: @nemz38_is_my_waifu_91412, 2026-11-16
Source: @68x0, 2026-11-16
Source: @samuel_hayden., 2026-11-17
lixiangwuxian/170hx-rir-tool 10 GB card only: burns the two RIR records that open the override gate, no glitch, see 170hx-rir-tool The tested 10 GB gate route. The RIR burn is the risky part; the rest can be done in software overrides. Source: @ghostinthedatacenter_87281, 2026-10-17 (CMP 170hx Clean Room Discussion server)
Source: @petrikrohn_26497, 2026-10-20 (CMP 170hx Clean Room Discussion server)
ffdump.py (a zip posted by @killred, no repo) FF row dumper, run as root with --enable-memory and the card's PCI address Posted 11-16 after he found the ffcalc dumper could not read the FF rows. Source: @killred, 2026-11-16
Source: @killred, 2026-11-16
Source: @killred, 2026-11-16
Zagitta/gpu-unlock Driver-side unlock, with an IFF readout added on 11-09 @zagitta planned to have AI assistants post IFF readouts to the repo's GitHub Discussions to spot patterns. Not tested on RIR-gate-burned 10 GB cards, where one owner sees problems cmpunlocker does not show. Source: @zagitta, 2026-11-09 (CMP 170hx Clean Room Discussion server)
Source: @lycorascence, 2026-11-18
Source: @zagitta, 2026-11-18
@killred's auto planner (not public) Per-card FF planner "my slopped auto planner worked"; release after he has tried it on all of his cards. Source: @killred, 2026-11-18
Source: @killred, 2026-11-18
Source: @killred, 2026-11-18

Which controller board

  • A Pico 2 is enough. On 11-11 @dalzyyy said no Teensy is needed, "rp2350 is fast enough", and a standard RP2040 or RP2350 dev board should do; @scallion_9883: a Pico is sufficient, "pico 1 is even fast enough"; @xanthefin: a Pico 2; @m3gagluk prefers a Pico for its PIO and expected only a Pico board to be needed out of Kate's whole setup. Later: @kingsizexxxl "2040/2350 pi picos work fine" and "just a pico is plenty", @lia_oc "pico does the job", @samuel_hayden. "you only need a 2040 or anything with i2c", @c133 "Kate herself says to use the Pico version", @con3po7016 a Pico 2 or Pico 2 W as the repo says. @mbelli, on a KB2040 (an RP2040 board), had less luck and suspected temperature, the board or the card. Source: @dalzyyy, 2026-11-11 (CMP 170hx Clean Room Discussion server)
    Source: @dalzyyy, 2026-11-11 (CMP 170hx Clean Room Discussion server)
    Source: @scallion_9883, 2026-11-11 (CMP 170hx Clean Room Discussion server)
    Source: @xanthefin, 2026-11-11 (CMP 170hx Clean Room Discussion server)
    Source: @m3gagluk, 2026-11-11 (CMP 170hx Clean Room Discussion server)
    Source: @scallion_9883, 2026-11-11 (CMP 170hx Clean Room Discussion server)
    Source: @m3gagluk, 2026-11-12 (CMP 170hx Clean Room Discussion server)
    Source: @samuel_hayden., 2026-11-14
    Source: @samuel_hayden., 2026-11-14
    Source: @lia_oc, 2026-11-15
    Source: @c133, 2026-11-15
    Source: @kingsizexxxl, 2026-11-15
    Source: @mbelli, 2026-11-15
    Source: @kingsizexxxl, 2026-11-18
    Source: @con3po7016, 2026-11-18 (CMP 170hx Clean Room Discussion server)
  • Other microcontrollers. Any MCU with a hardware I2C peripheral will work, but the code has to be rewritten for its HAL, for example the ESP32's (@samuel_hayden.). It also needs a GPIO input; I2C alone is not enough, "otherwise it would only take CH341A to do this hack" (@angrykirc). @roman13036 asked about ESP32 boards; @samuel_hayden. named a very small part such as an 8-pin STM32G0 as a possible exception. @_arcanum_ is collecting which RP2350 silicon revision (2, 3 or 4) people use. Source: @_arcanum_, 2026-11-16
    Source: @roman13036, 2026-11-17
    Source: @samuel_hayden., 2026-11-17
    Source: @samuel_hayden., 2026-11-17
    Source: @samuel_hayden., 2026-11-17
    Source: @angrykirc, 2026-11-17
    Source: @angrykirc, 2026-11-17
    Source: @angrykirc, 2026-11-17
    Source: @samuel_hayden., 2026-11-17
  • Before the I2C tools (11-11 to 11-13). @samuel_hayden. ported the PWMVID glitcher to a Pico: it needs a PWM peripheral and DMA, plus a comparator and a fast 1.8 V level shifter (he named the TI SN74LVC1G126) on perfboard; any STM32 with a built-in comparator also works. He replaced Kate's single-board computer for the reboot loop with the motherboard's hardware watchdog (a Z690 board) through a systemd service. @shirogeek suggested the Teensy 4.1 (fast, analog comparator, good ADC), @wingrimez_40467 the STM32 Nucleo-144, or a Pico powered from 1.8 V; @globalapathy thought the faster STM32 was needed for accurate clocks up to 675 kHz. @c133: buy the STM32G431CBT6 from a trusted distributor such as Digikey or Mouser, not through the board house, because STM32s are among the most cloned chips (his AI assistant's advice). Source: @samuel_hayden., 2026-11-11
    Source: @samuel_hayden., 2026-11-11
    Source: @c133, 2026-11-11
    Source: @c133, 2026-11-11
    Source: @samuel_hayden., 2026-11-12
    Source: @globalapathy, 2026-11-12
    Source: @globalapathy, 2026-11-12
    Source: @samuel_hayden., 2026-11-12
    Source: @shirogeek, 2026-11-12
    Source: @shirogeek, 2026-11-12
    Source: @wingrimez_40467, 2026-11-12
    Source: @samuel_hayden., 2026-11-12
    Source: @samuel_hayden., 2026-11-12
    Source: @samuel_hayden., 2026-11-12
    Source: @wingrimez_40467, 2026-11-12
    Source: @samuel_hayden., 2026-11-12
  • Long I2C wires. Seeing twisted I2C cables in @ichundes's photos, @shirogeek warned that I2C runs past the bus's cable length drop commands now and then; he uses I2C accelerators. Source: @shirogeek, 2026-11-14
    Source: @shirogeek, 2026-11-14

Reported 8 GB

What the boards cost

  • An RP2350 board was 6 USD at Micro Center on 2026-11-16, one per household (@deejay9983, @froggao); @kingsizexxxl: "It really should be 6$" at Micro Center or another distributor, and it will not go up, "There are millions of those". @ins_mniac: "$10 pico glitching". Source: @ins_mniac, 2026-11-15
    Source: @deejay9983, 2026-11-16
    Source: @deejay9983, 2026-11-16
    Source: @froggao, 2026-11-16
    Source: @kingsizexxxl, 2026-11-16
    Source: @kingsizexxxl, 2026-11-16
    Source: @kingsizexxxl, 2026-11-16
  • Kate's board: @djpandaman put it at a 5 dollar board; @ins_mniac looked at having it made and the price "was gonna reach up near 120" (currency not stated). The PCB comes in a minimum order of five, so members in Canada and elsewhere asked for group buys; @spectakkular thinks the glitch raises a card's value by far more than the PCB order costs. To order it, @shirogeek imported the KiCad design into EasyEDA (part of JLCPCB). @truvv0r spent about 2 months clearing a 5 USD PCB through customs. On 11-13 @innospark found an eBay listing and asked if it was real; @spectakkular: "Almost certainly, the PCB has minimum order limits". @ghostinthedatacenter_87281 builds the PCBs himself. Source: @marklintonca, 2026-11-11
    Source: @spectakkular, 2026-11-11
    Source: @djpandaman, 2026-11-11 (CMP 170hx Clean Room Discussion server)
    Source: @marklintonca, 2026-11-11
    Source: @truvv0r, 2026-11-12 (CMP 170hx Clean Room Discussion server)
    Source: @globalapathy, 2026-11-12
    Source: @shirogeek, 2026-11-12
    Source: @innospark, 2026-11-13 (CMP 170hx Clean Room Discussion server)
    Source: @spectakkular, 2026-11-13 (CMP 170hx Clean Room Discussion server)
    Source: @ghostinthedatacenter_87281, 2026-11-13 (CMP 170hx Clean Room Discussion server)
    Source: @ins_mniac, 2026-11-14 (CMP 170hx Clean Room Discussion server)
  • Kate's board quality: @m3gagluk was "horrified" by the layout and said it needs a comparator for a specific voltage; @mellojello_: "Not exactly", "There are other routes". @cute_sc2: it was hacked together and could be improved. @globalapathy rerouted it onto an open STM32 dev board in a 64-pin QFN so it is not single purpose. Source: @m3gagluk, 2026-11-11 (CMP 170hx Clean Room Discussion server)
    Source: @m3gagluk, 2026-11-11 (CMP 170hx Clean Room Discussion server)
    Source: @mellojello_, 2026-11-11 (CMP 170hx Clean Room Discussion server)
    Source: @mellojello_, 2026-11-11 (CMP 170hx Clean Room Discussion server)
    Source: @cute_sc2, 2026-11-11 (CMP 170hx Clean Room Discussion server)
    Source: @globalapathy, 2026-11-12
    Source: @globalapathy, 2026-11-12
    Source: @globalapathy, 2026-11-13

Reported 8 GB

Fuse capture and burn-plan tools

On 11-15 @68x0 had a model write an FF row dumper and a burn planner: "This is slop, but the dumper does seem to be reading my FF rows", the planner untested and to be checked by hand against his own cards. On 11-16 he posted an updated capture, planner and README, spot-checked ("it looks to be producing valid data"); the model had trouble identifying the Gen4 bits, and he asked for help verifying the FF chains and rows. The same day he posted ga100-public-tools.zip in both servers ("Slop produced FF row capture and planner and burner", AI-written by his account) and on 11-17 the repo kprinssu/ga100-ff-tools. @killred posted his own dumper as a zip, and on 11-18 said his planner worked and would be released after testing on all of his cards. @port00 published his console. No member reported a burn made with one of these public planners by 11-18. In October an untested AI-written "recipe" (one RIR write to enable the software override) circulated in the clean room server; its poster had no 10 GB card to test it. The tested 10 GB route is the published RIR tool.

Reported 8 GB and 10 GB
Source: @akuchen_66498, 2026-10-07 (CMP 170hx Clean Room Discussion server)
Source: @stsoftware_88487, 2026-10-07 (CMP 170hx Clean Room Discussion server)
Source: @68x0, 2026-11-15
Source: @68x0, 2026-11-15
Source: @68x0, 2026-11-15
Source: @killred, 2026-11-16
Source: @68x0, 2026-11-16
Source: @68x0, 2026-11-16
Source: @68x0, 2026-11-16
Source: @68x0, 2026-11-16 (CMP 170hx Clean Room Discussion server)
Source: @68x0, 2026-11-16
Source: @68x0, 2026-11-17
Source: @port00, 2026-11-17
Source: @killred, 2026-11-18

Is cmp170hx-ffcalc safe to plan with?

In the order posted:

  • @lia_oc (11-15): "that ffcalc repo still has issues". Source: @lia_oc, 2026-11-15
  • @68x0 (11-16): "That repo is broken and doesn't dump FF rows"; its burn plan "doesn't account for existing data in the FF rows"; use gpcprobe, which shows the GPCs and TPCs. Source: @68x0, 2026-11-16
    Source: @68x0, 2026-11-16
    Source: @68x0, 2026-11-16
    Source: @68x0, 2026-11-16
  • @nemz38_is_my_waifu_91412 (11-16): at least consistent: the card gpcprobe shows with a defective GPC came out at 112 SMs in ffcalc, and its memory and SM figures looked right. Source: @nemz38_is_my_waifu_91412, 2026-11-16
    Source: @nemz38_is_my_waifu_91412, 2026-11-16
  • @lia_oc (11-16): "please do not yolo ffcalc without doing your research first or waiting for other people to post more tools"; @samuel_hayden.: "If you yolo ffcalcs you will brick your card". Source: @lia_oc, 2026-11-16
    Source: @samuel_hayden., 2026-11-17

Contested 8 GB The fix to ffcalc's issue #1 (planning over rows already burned, 11-16) is on cmp170hx-ffcalc; whether the criticism came before or after it is not stated.

Kits and no-solder rigs announced

  • CUTE's jig. On 11-16 @cute_sc2 described an unlock in which you remove the aluminium shroud, screw a jig on, connect cables to a computer and click unlock in a simple GUI, with no soldering; only NVLink still needs components soldered. He asked a seller to beta test it ("It might be ready in 2 weeks or so"). The hardware manual was to come "next weekend or the one after", software later. Source: @cute_sc2, 2026-11-16
    Source: @cute_sc2, 2026-11-16
    Source: @cute_sc2, 2026-11-16
    Source: @cute_sc2, 2026-11-16
    Source: @cute_sc2, 2026-11-16
    Source: @cute_sc2, 2026-11-16
  • Amogh's boards. On 11-18 @_j3ns, the cmpunlocker maintainer, answered @scallion_9883's remark that cmpunlocker is less relevant now with "Time to discontinue cmpunlocker and design unlock boards": an open-source board to fabricate plus a kit for sale, maybe a send-in service, while cmpunlocker gets minimal updates such as driver support. People with several cards do not want to solder many wires. @zagitta warned (not a lawyer) that the people who got into trouble over Tegra hacks were the ones selling things; @con3po7016 saw too much risk in a send-in service. @nyancat3355 suggested one board for the CMP 70HX, 90HX and 170HX. Source: @_j3ns, 2026-11-17
    Source: @scallion_9883, 2026-11-18
    Source: @_j3ns, 2026-11-18
    Source: @_j3ns, 2026-11-18
    Source: @_j3ns, 2026-11-18
    Source: @_j3ns, 2026-11-18
    Source: @con3po7016, 2026-11-18
    Source: @_j3ns, 2026-11-18
    Source: @zagitta, 2026-11-18
    Source: @nyancat3355, 2026-11-18
    Source: @zagitta, 2026-11-18

Reported 8 GB and 10 GB No board design, price or date was posted.

Practical tips members posted

These are individual members' reports from their own cards. Each die differs: treat any number here as where one person started, not a setting to copy.

Wiring: four points on the back of the card

The Pico route uses four connections: SDA, SCL, PEX_RST and GND. @ichundes: "i didn't use a NVVDD connection, only SDA, SCL, PEX_RST and GND". No NVVDD wire is needed (@zagitta, @lia_oc, @ghostinthedatacenter_87281) and nothing has to be removed (@gnasherrr), but a ground is (@gnasherrr, @wakeupmbrc1). Every point, PEX_RST included, is on the back of the card (@lia_oc), so a water block or the copper heatsink can stay on: with the stock air cooler, take the shell off and leave the copper heatsink on the card. The wiring diagram and photos are in the dalzyu/pico-ga100vfi README; @zagitta told a member to read it closely, and @dalzyyy took @ichundes's clearer photo for the repo after his own pictures confused people. @vuhuycan0322 proposed clips on U0808 (the I2C lines) and U0809 (unsure whether PEX_RST reaches it); @ichundes posted his measurements of those points as a photo. The wires do not need to stay after the unlock (@zagitta), but whoever solders them on also has to take them off again (@wakeupmbrc1). One Pico can move from card to card (@ju5t5omedude).

Reported 8 GB
Source: @ju5t5omedude, 2026-11-14 (CMP 170hx Clean Room Discussion server)
Source: @zagitta, 2026-11-15
Source: @zagitta, 2026-11-16
Source: @zagitta, 2026-11-16
Source: @vuhuycan0322, 2026-11-16
Source: @ichundes, 2026-11-16
Source: @wakeupmbrc1, 2026-11-16
Source: @wakeupmbrc1, 2026-11-16
Source: @gnasherrr, 2026-11-16
Source: @lia_oc, 2026-11-16
Source: @gnasherrr, 2026-11-16
Source: @lia_oc, 2026-11-16
Source: @lia_oc, 2026-11-16
Source: @lia_oc, 2026-11-16
Source: @lia_oc, 2026-11-16
Source: @ichundes, 2026-11-17
Source: @ghostinthedatacenter_87281, 2026-11-17
Source: @dalzyyy, 2026-11-17
Source: @dalzyyy, 2026-11-17

Flash the controller before you connect PEX_RST

Warning 8 GB "make sure you flash the glitch firmware first before you connect PEX_RST or it could damage the hardware." Flash the Pico on its own, then wire it to the card.

Source: @ichundes, 2026-11-17

Is the ground wire needed?

In the order posted (2026-11-18):

  • @fallengod9962 forgot to solder the ground; the Pico still saw I2C traffic, and his chat model warned him not to glitch without it. Source: @fallengod9962, 2026-11-18
    Source: @fallengod9962, 2026-11-18
  • @scallion_9883: not needed if the Pico is plugged into the same workstation as the GPU, which "Will complete the loop". Source: @scallion_9883, 2026-11-18
    Source: @scallion_9883, 2026-11-18
  • @kingsizexxxl: "Feel like that's an unnecessary risk", "More ground more better". Source: @kingsizexxxl, 2026-11-18
    Source: @kingsizexxxl, 2026-11-18
  • @fallengod9962: his rig "was very flacky" until he wired the ground. Source: @fallengod9962, 2026-11-18

Contested 8 GB

Kate's original hookup (STM32 board)

Kate's board needs more work than the Pico route. Members working from her write-up: solder a tap to NVVDD (likely on one of the bulk capacitor banks) and one to NVVDD_PWMVID_IN with magnet wire, a fine-tip iron and magnification, and remove one 0 ohm 0402 jumper, R30 in @samuel_hayden.'s photo, next to other 0402 parts. He rates it like the PCIe x16 capacitor mod but with adjacent components, so no heavy hot air: tape the area with Kapton, flow leaded solder on both pads and use 2 or 3 seconds of hot air, or just the iron. The wiring leaves through the PCI bracket and is only needed while the card is powered and rebooted for the glitch; afterwards the resistor goes back, or its pads are bridged with solder. The fuse change is permanent, and one glitch board serves many cards (@m3gagluk, @shirogeek, @globalapathy). @zanooda found NVVDD and GND on pins 31 and 32 (the part is not named). @shirogeek: push the resistor sideways so one pad stays soldered, to avoid losing it, and check the generated PWM's voltage, duty cycle and frequency with an oscilloscope before it is connected to the GPU. The Pico route needs none of this (@lia_oc: removing a resistor "was the old method (kates)").

Reported 8 GB
Source: @m3gagluk, 2026-11-11
Source: @shirogeek, 2026-11-11
Source: @shirogeek, 2026-11-11
Source: @samuel_hayden., 2026-11-12
Source: @shirogeek, 2026-11-12
Source: @zanooda, 2026-11-12
Source: @shirogeek, 2026-11-12
Source: @shirogeek, 2026-11-12
Source: @globalapathy, 2026-11-12
Source: @samuel_hayden., 2026-11-12
Source: @samuel_hayden., 2026-11-12
Source: @samuel_hayden., 2026-11-12
Source: @samuel_hayden., 2026-11-12
Source: @samuel_hayden., 2026-11-12
Source: @samuel_hayden., 2026-11-12
Source: @samuel_hayden., 2026-11-12
Source: @globalapathy, 2026-11-12
Source: @samuel_hayden., 2026-11-12
Source: @samuel_hayden., 2026-11-12
Source: @samuel_hayden., 2026-11-12
Source: @samuel_hayden., 2026-11-12
Source: @samuel_hayden., 2026-11-12
Source: @samuel_hayden., 2026-11-12
Source: @lia_oc, 2026-11-16

Soldering, probes and pogo fixtures

  • Soldering. Four joints, about 2 minutes per card to solder and unsolder with a good iron and good solder (@ins_mniac). @c133 used spare CAT6 wire; @con3po7016 chose soldered wires as the least error-prone. @.shakdiesel's wires kept coming off the pads: get a digital microscope. @lia_oc: "some people have already damaged their cards w/ soldering attempts". Pads and parts that came off are on Unlock without bricking. @kingsizexxxl: "if you have to ask this question you are not ready to do this mod in its current state". Source: @ins_mniac, 2026-11-13 (CMP 170hx Clean Room Discussion server)
    Source: @con3po7016, 2026-11-14 (CMP 170hx Clean Room Discussion server)
    Source: @c133, 2026-11-14 (CMP 170hx Clean Room Discussion server)
    Source: @kingsizexxxl, 2026-11-16
    Source: @lia_oc, 2026-11-16
    Source: @.shakdiesel, 2026-11-17
    Source: @.shakdiesel, 2026-11-17
  • Probes. @lia_oc bought a SensePeek PCBite kit (7028), easier than soldering, and @kingsizexxxl recommends PCBite ("It's a 3 minute job", "on the skill level of a ps1 modchip"). @con3po7016 put it at about 180 USD; @ob88594 found similar probes for 9 USD and says a good needle tip slightly enters the solder joint, and that someone has used it. @68x0 considered small test hooks on the IC legs; @kingsizexxxl: "Pogo pin is the right choice here not clips". @bigptoughneigh planned PCBite probes and would report if it bricks the card. Source: @bigptoughneigh, 2026-11-13 (CMP 170hx Clean Room Discussion server)
    Source: @bigptoughneigh, 2026-11-13 (CMP 170hx Clean Room Discussion server)
    Source: @68x0, 2026-11-16
    Source: @kingsizexxxl, 2026-11-16
    Source: @ob88594, 2026-11-16
    Source: @kingsizexxxl, 2026-11-16
    Source: @kingsizexxxl, 2026-11-16
    Source: @kingsizexxxl, 2026-11-16
    Source: @lia_oc, 2026-11-16
    Source: @lia_oc, 2026-11-16
    Source: @con3po7016, 2026-11-18 (CMP 170hx Clean Room Discussion server)
    Source: @ob88594, 2026-11-18 (CMP 170hx Clean Room Discussion server)
    Source: @ob88594, 2026-11-18 (CMP 170hx Clean Room Discussion server)
  • Jigs. A baseplate with pogo pins in front of the test points, as on PCB production lines, by custom PCB or 3D print (@g4bwy); @jbranco91 is taking one to a 3D print; @cmdrwaka324 planned to 3D scan the card; @ju5t5omedude would locate a jig with the heatsink bolts or the NVLink slot; @cibernox proposed a press-fit jig for a group order. Against: poor contact makes the microcontroller link unstable and too much pressure can damage the PCB (@ins_mniac), and for one card the soldering is not hard (@shirogeek). On 11-17 @con3po7016 asked who had used pogo pins and how well; no answer by 11-18. Source: @cibernox, 2026-11-13 (CMP 170hx Clean Room Discussion server)
    Source: @shirogeek, 2026-11-13 (CMP 170hx Clean Room Discussion server)
    Source: @ins_mniac, 2026-11-13 (CMP 170hx Clean Room Discussion server)
    Source: @ju5t5omedude, 2026-11-14 (CMP 170hx Clean Room Discussion server)
    Source: @ju5t5omedude, 2026-11-14 (CMP 170hx Clean Room Discussion server)
    Source: @cmdrwaka324, 2026-11-14 (CMP 170hx Clean Room Discussion server)
    Source: @g4bwy, 2026-11-16
    Source: @g4bwy, 2026-11-16
    Source: @g4bwy, 2026-11-16
    Source: @jbranco91, 2026-11-16
    Source: @con3po7016, 2026-11-17

Reported 8 GB

VRM temperature

The glitch is sensitive to the VRM temperature (@samuel_hayden.), and the window "is going to be unique for your card and even amongst your own cards". His first card was only sensitive in a range around 40.5-42.5C, read over I2C from the VRM controller itself (the MP2888B), not from the GPU core. @mbelli adjusted the VRM temperature from 36 to 41 between campaigns; the card cools while it is off the PCIe bus. @wakeupmbrc1 suggested a higher temperature might be needed; @jonathanyjoerrington runs it cool, with the fan at full, the adaptive mode, and only right after boot. One of @ichundes's two cards only glitched once it was up to temperature.

Reported 8 GB
Source: @ichundes, 2026-11-17
Source: @wakeupmbrc1, 2026-11-17
Source: @jonathanyjoerrington, 2026-11-17
Source: @mbelli, 2026-11-17
Source: @jonathanyjoerrington, 2026-11-17
Source: @jonathanyjoerrington, 2026-11-17
Source: @samuel_hayden., 2026-11-17
Source: @samuel_hayden., 2026-11-17
Source: @samuel_hayden., 2026-11-17
Source: @samuel_hayden., 2026-11-17
Source: @samuel_hayden., 2026-11-17
Source: @samuel_hayden., 2026-11-17
Source: @vuhuycan0322, 2026-11-18

Attempts, reboots and time per card

  • Spread. Under a minute (@kingsizexxxl, 11-15); "<2 mins normally" and under 100 tries with the newer method (@dalzyyy); about 100 attempts, "But it's all luck" (@.shakdiesel); about 600 for @zanooda's first card while his second had not yet glitched; about 3,000-4,000 for each of @killred's two cards; nothing after 652 attempts (@mbelli) or about 400 (@dr.bubotnic) on 11-17. Kate's original rig was reported at 1 to 48 hours. Hearsay relayed by @con3po7016: about 5 attempts, under an hour. Source: @dalzyyy, 2026-11-13 (CMP 170hx Clean Room Discussion server)
    Source: @dalzyyy, 2026-11-13 (CMP 170hx Clean Room Discussion server)
    Source: @kingsizexxxl, 2026-11-15
    Source: @mbelli, 2026-11-17
    Source: @.shakdiesel, 2026-11-17
    Source: @.shakdiesel, 2026-11-17
    Source: @dr.bubotnic, 2026-11-17
    Source: @con3po7016, 2026-11-18 (CMP 170hx Clean Room Discussion server)
    Source: @zanooda, 2026-11-18
    Source: @zanooda, 2026-11-18
    Source: @killred, 2026-11-18
  • No universal waveform. Kate: "No, you will need much trial and error". @dalzyyy: once the right settings for his card were found, "The correct params on my card have a 99% chance of goldilocks within 25 shots". Source: @onemillionkates, 2026-11-11
    Source: @dalzyyy, 2026-11-18
  • Reboot. @killred got nothing in his first 500 attempts and thinks the host needs a reboot after 500; he reboots after 2 batches of 500. When another member's run kept the same v_dip: "You need a reboot". His log then showed the success state on one card. Source: @killred, 2026-11-18
    Source: @killred, 2026-11-18
    Source: @killred, 2026-11-18
    Source: @killred, 2026-11-18
    Source: @killred, 2026-11-18
    Source: @killred, 2026-11-18
    Source: @killred, 2026-11-18
  • Check the soldering. When @mbelli had no luck on his KB2040, @kingsizexxxl: "id check your soldering". @dr.bubotnic checked all connections several times without reaching the state. Source: @mbelli, 2026-11-15
    Source: @kingsizexxxl, 2026-11-15
    Source: @dr.bubotnic, 2026-11-17

Reported 8 GB

Glitch settings: dip depth, pulses and recovery voltage

@mbelli (11-17): dropping off PCIe and losing reads "doesn't necessarily mean too low". His tries were at 354 and 348 (older mV labels), losing about 80 percent of reads at 348; he saw another member lose 80 percent at 375 yet hit at 360. @dalzyyy: some may have better luck with a single pulse instead of 3; @samuel_hayden.: play with the PWM waveforms. On 11-18, with @zanooda stuck, @dalzyyy suggested a different recovery voltage and said the adaptive mode only varies v_dip so as not to blow up the search space. Asked what recovery voltage range is safe to evaluate: his notes put the best for his card between 625 and 650 mV, "so between 600-675mV maybe?". For a full sweep he does 25 shots at each setting. He had earlier found that fuse sensing fails below about 400 mV. These are one card's numbers.

Reported 8 GB
Source: @dalzyyy, 2026-11-11 (CMP 170hx Clean Room Discussion server)
Source: @mbelli, 2026-11-17
Source: @dalzyyy, 2026-11-17
Source: @samuel_hayden., 2026-11-17
Source: @dalzyyy, 2026-11-18
Source: @dalzyyy, 2026-11-18
Source: @zanooda, 2026-11-18
Source: @dalzyyy, 2026-11-18
Source: @dalzyyy, 2026-11-18
Source: @dalzyyy, 2026-11-18

When the link drops: PEX_RST does not retrain the root port

On 11-17 @dr.bubotnic (a Z490 board) and @ghostinthedatacenter_87281 (an Asus WRX90E) both had the card leave config space (reads of 0xffffffff) while glitching: PEX_RST pulses from the Pico, but the root port does not retrain, and only a full power cycle recovers. Both checked voltages and continuity; on the WRX90E BAR resize did not work either, and neither had reached the success state then. On 11-18 @fallengod9962's PC locked up while glitching and needed a hard reboot; @dr.bubotnic saw the same. @samuel_hayden. found from scope probing that the issue went away after he disconnected PEX_RST (11-16). @ichundes posted the order he uses: hold PEX_RST low (hot reset), remove the device from the kernel's PCI tree so it frees the BAR windows, release PEX_RST (the hot reset reverts the card's resizable BAR to default sizes), wait about 6 s for boot, rescan, then re-enable the device's memory and bus-master bits. No cause was confirmed.

Reported 8 GB
Source: @samuel_hayden., 2026-11-16
Source: @dr.bubotnic, 2026-11-17
Source: @ghostinthedatacenter_87281, 2026-11-17
Source: @dr.bubotnic, 2026-11-17
Source: @ghostinthedatacenter_87281, 2026-11-17
Source: @ghostinthedatacenter_87281, 2026-11-17
Source: @ghostinthedatacenter_87281, 2026-11-17
Source: @fallengod9962, 2026-11-18
Source: @dr.bubotnic, 2026-11-18
Source: @ichundes, 2026-11-18

Lab, 2026-11-19: on the lab's cards the link loss was a brown-out loop. After a crash shot the tool hands the core rail back to the GPU, the crashed GPU commands the floor (READ_VOUT 301 mV, against 713 mV on a healthy idle card), and every PEX_RST then reboots it into a brown-out. Holding the rail at 787.5 mV under PMBus control, then PEX_RST, and only then the config read brought the card back in 0.2 s with no power cycle. A card that sits half-booted answering config reads with CRS can also freeze an Intel host on the next config read; the lab's Z790 host froze three times that way before the park step went into its campaign loop. The sequence: park and rescue.

Reported 8 GB
Source: @darkmaniac7, 2026-11-19 (lab notes)

Many cards

@fnerdman noted that at 1 to 48 hours per card owners of many cards would need weeks. Ideas: run several at once on cheap Huananzhi boards (@wakeupmbrc1); an x1 link is enough, so mining risers work (@djpandaman); a board with PCIe hotplug could make it much faster (@zagitta; @globalapathy's ASRock Rack board has hotplug, unused so far); buy more Picos (@con3po7016); pogo fixtures for batch glitching (@shirogeek). @cute_sc2 planned to do his cards one at a time through December, his test board having one x16 slot. @sekkit_75019 asked whether one Pico serves all cards and how long one card takes; no answer. With the Pico tools, single cards now take minutes to hours (above).

Theory 8 GB
Source: @fnerdman, 2026-11-11
Source: @wakeupmbrc1, 2026-11-11
Source: @wakeupmbrc1, 2026-11-11
Source: @djpandaman, 2026-11-11
Source: @cute_sc2, 2026-11-11
Source: @cute_sc2, 2026-11-11
Source: @zagitta, 2026-11-11
Source: @globalapathy, 2026-11-11
Source: @shirogeek, 2026-11-13 (CMP 170hx Clean Room Discussion server)
Source: @con3po7016, 2026-11-14 (CMP 170hx Clean Room Discussion server)
Source: @cute_sc2, 2026-11-14 (CMP 170hx Clean Room Discussion server)
Source: @sekkit_75019, 2026-11-18 (CMP 170hx Clean Room Discussion server)

The core voltage controller (MP2888B) and the I2C route

  • The GA100 only reads values from the core voltage controller over I2C and controls the voltage with PWM-VID, "so sniffing the bus won't achieve anything" (@dalzyyy, 10-24). Every register can be read, but writes are protected by a 4-byte write-unlock code, and a wrong code locks the chip until its VDD is power-cycled. He desoldered one controller (QFN 5x5), recovered its code (not reproduced here) and soldered it back; he wrote nothing to its EEPROM, "so nothing stuck". He found the MP2888B register set a superset of the MP2888A's and thinks they are pin compatible; @shirogeek's AI assistant said they are not (unresolved). @shirogeek noted the PWM signal is 1.8 V; @dalzyyy: the input is 3.3 V tolerant. His idea of a software P-state over I2C is untested. Source: @dalzyyy, 2026-10-24 (CMP 170hx Clean Room Discussion server)
    Source: @dalzyyy, 2026-10-24 (CMP 170hx Clean Room Discussion server)
    Source: @shirogeek, 2026-10-24 (CMP 170hx Clean Room Discussion server)
    Source: @dalzyyy, 2026-10-24 (CMP 170hx Clean Room Discussion server)
    Source: @dalzyyy, 2026-10-24 (CMP 170hx Clean Room Discussion server)
    Source: @dalzyyy, 2026-10-24 (CMP 170hx Clean Room Discussion server)
    Source: @shirogeek, 2026-10-24 (CMP 170hx Clean Room Discussion server)
    Source: @dalzyyy, 2026-10-24 (CMP 170hx Clean Room Discussion server)
    Source: @dalzyyy, 2026-10-24 (CMP 170hx Clean Room Discussion server)
    Source: @shirogeek, 2026-10-24 (CMP 170hx Clean Room Discussion server)
    Source: @dalzyyy, 2026-10-24 (CMP 170hx Clean Room Discussion server)
    Source: @dalzyyy, 2026-10-25 (CMP 170hx Clean Room Discussion server)
    Source: @dalzyyy, 2026-10-25 (CMP 170hx Clean Room Discussion server)
  • Monolithic Power Systems told @shirogeek they cannot send the datasheet or the programming GUI to him and that he should contact the seller of the ICs. In his understanding a blank chip has no code set: you set it yourself and it is written to NVS. Source: @shirogeek, 2026-11-07 (CMP 170hx Clean Room Discussion server)
    Source: @shirogeek, 2026-11-07 (CMP 170hx Clean Room Discussion server)
    Source: @shirogeek, 2026-11-07 (CMP 170hx Clean Room Discussion server)
  • On 11-12 @scallion_9883 advised skipping the PWMVID tap: talk I2C to the VRM controller (the same interface as the MP2888A, several tap points on the bus) and command the voltage drop there, with a Pico, a Raspberry Pi, an ESP32 or "pretty much anything with gpio that can run i2c". @samuel_hayden. probed the bus: 100 kHz, with the controllers polled for status. By 11-15 dalzyu/pico-ga100vfi did the dip over the card's own I2C link. @mrpec: "Pico sends commands to internal i2c which sends voltage". Asked whether it could be done with no external hardware at all, @kingsizexxxl: "Technically perhaps, with wildly specific motherboards and glitch times in the weeks". Source: @scallion_9883, 2026-11-12
    Source: @scallion_9883, 2026-11-12
    Source: @scallion_9883, 2026-11-12
    Source: @scallion_9883, 2026-11-12
    Source: @scallion_9883, 2026-11-12
    Source: @scallion_9883, 2026-11-12
    Source: @samuel_hayden., 2026-11-13
    Source: @samuel_hayden., 2026-11-13
    Source: @kingsizexxxl, 2026-11-13
    Source: @mrpec, 2026-11-13 (CMP 170hx Clean Room Discussion server)
    Source: @mbelli, 2026-11-15

Reported 8 GB and 10 GB

Cautions before you start

  • Do not try voltage glitching when tired, and learn the basics of voltage fault injection first: "If you see magic smoke then you know what not to do." (@cute_sc2, 10-03) Source: @cute_sc2, 2026-10-03 (CMP 170hx Clean Room Discussion server)
    Source: @cute_sc2, 2026-10-03 (CMP 170hx Clean Room Discussion server)
  • A chip can short itself through a glitch, for example by routing power to a faulty SM, so guard it from destroying itself too quickly (@m3gagluk, 10-26). Source: @m3gagluk, 2026-10-26 (CMP 170hx Clean Room Discussion server)
  • Go in baby steps: first verify that the glitch works, does not damage cards and is reversible (@ins_mniac, 11-11). First find where the power regulator is, and when and how to glitch (@truvv0r, 11-14). Source: @ins_mniac, 2026-11-11 (CMP 170hx Clean Room Discussion server)
    Source: @truvv0r, 2026-11-14 (CMP 170hx Clean Room Discussion server)
  • @shirogeek (11-12) sees little risk as long as the PWM you generate matches what the pad expects, so NVDD stays in bounds; you are reproducing the PWM to drop the voltage at the right time, not holding an overvoltage at the limit. The real risk is "flying totally blind" without a step-by-step guide. @robbbbbb7973 had the tools but found the risk too scary at current card prices. Source: @robbbbbb7973, 2026-11-12
    Source: @shirogeek, 2026-11-12
    Source: @shirogeek, 2026-11-12
    Source: @shirogeek, 2026-11-12
    Source: @shirogeek, 2026-11-12
    Source: @shirogeek, 2026-11-12

Reported 8 GB

Checking the result

  • "The only proof is a workload that writes distinct data above the nerf line and reads it back clean." A driver can be made to print a size while the memory folds (@bigptoughneigh, 07-12). See Verifying an unlock. Source: @bigptoughneigh, 2026-07-12 (CMP 170hx Clean Room Discussion server)
  • memtest_vulkan makes nvtop show an odd VRAM usage reading; the memory is fine and the reading returns to normal once another VRAM consumer starts (@m3gagluk). Source: @m3gagluk, 2026-08-13 (CMP 170hx Clean Room Discussion server)
  • Per-SM coverage: @samuel_hayden.'s SM stress test reported "covered 126/126 target SMs" on one burned card (above). Source: @jonathanyjoerrington, 2026-11-17

Reported 8 GB and 10 GB

Safety rules (short form)

One line each, as members posted them. The full entries, with the numbers, the cases behind them and every source, are on Unlock without bricking and Fuses and floorsweep maps. None of this is a burn plan: build yours from your own card's read.

  • Warning Every card needs its own plan. "Daily reminder fuses are INDIVIDUAL per card, do not blindly burn from another card's plan" (@zagitta). Have the full write plan before you glitch, "Otherwise glitching does you no good", and post your dump and intended writes for review. Source: @kingsizexxxl, 2026-11-17 (CMP 170hx Clean Room Discussion server)
    Source: @zagitta, 2026-11-18
    Source: @zagitta, 2026-11-18
    Source: @zagitta, 2026-11-18
    Source: @zagitta, 2026-11-18
  • Warning Never burn a word with bit 5 set inside the FF region. bit5=1 is the termination instruction that closes the FF pool; the IFF region starts after it and every later FF record is ignored. "i think bit5=1 writing should be strictly prohibited when doing any writing in FF" (@wakeupmbrc1, @port00 agreed). A bit-5 word lower down simply moves the IFF start to that row. Source: @stsoftware_88487, 2026-11-10 (CMP 170hx Clean Room Discussion server)
    Source: @stsoftware_88487, 2026-11-16 (CMP 170hx Clean Room Discussion server)
    Source: @wakeupmbrc1, 2026-11-17
    Source: @wakeupmbrc1, 2026-11-17
    Source: @port00, 2026-11-17
    Source: @wakeupmbrc1, 2026-11-17
    Source: @wakeupmbrc1, 2026-11-17
  • Warning Count your spare FF rows before burning. Members counted 196 (@dalzyyy) and about 100-200 in the valid range (@killred; first free row 308 on his card); in October @akuchen_66498 saw about 38 zero rows after the last record in rows 222-331 of an 8 GB dump. Some dies end the FF region around row 310, at least one card ran out of free FF rows, and one of five new cards had almost fully written fuse data. Source: @akuchen_66498, 2026-10-06 (CMP 170hx Clean Room Discussion server)
    Source: @dalzyyy, 2026-11-16
    Source: @killred, 2026-11-16
    Source: @killred, 2026-11-16
    Source: @petrikrohn_26497, 2026-11-17 (CMP 170hx Clean Room Discussion server)
    Source: @68x0, 2026-11-17
    Source: @simple98., 2026-11-17
  • Warning Burn only into empty rows, with a buffer above the boot records, leave a clear space at the end for reverts, and leave room to re-disable SMs that turn out to be bad (@samuel_hayden.). Source: @samuel_hayden., 2026-11-17
    Source: @samuel_hayden., 2026-11-17
    Source: @samuel_hayden., 2026-11-17
  • Warning A later record replaces the whole 16-bit block, so an appended block has to reproduce every other bit correctly (@akuchen_66498, 10-03). Source: @akuchen_66498, 2026-10-03 (CMP 170hx Clean Room Discussion server)
  • Warning Do not invalidate factory or mid-chain FF records until that has been verified on hardware (@zarquon3157); writing an old record to all ones only helps for records that are all 0 on a regular A100, not on a CMP (@cute_sc2). The stuck card below started with two invalidated factory records. Source: @port00, 2026-11-17
    Source: @cute_sc2, 2026-11-17 (CMP 170hx Clean Room Discussion server)
    Source: @zarquon3157, 2026-11-17 (CMP 170hx Clean Room Discussion server)
  • Warning Test in software first. Once DSOV is off, use SW-IFF to test changes before burning FF fields; SW-IFF is lost at a power cycle (@scallion_9883, 11-13). "Only do burns that have been tested and confirmed by others", and test any new 8 GB burn with software overrides (SW-IFF) on a 10 GB card first (@petrikrohn_26497, 11-17). Scripts that calculate a plan can be generic; a fixed list of writes cannot (@cmdrwaka324). Source: @scallion_9883, 2026-11-13 (CMP 170hx Clean Room Discussion server)
    Source: @scallion_9883, 2026-11-13 (CMP 170hx Clean Room Discussion server)
    Source: @petrikrohn_26497, 2026-11-17 (CMP 170hx Clean Room Discussion server)
    Source: @cmdrwaka324, 2026-11-17 (CMP 170hx Clean Room Discussion server)
  • Reported Burn an inert canary first and verify its exact readback before one targeted record; if records are already burned, debug (readback, re-sense or reset, driver) before burning more (@akuchen_66498). A canary with bit 5 set ends the FF parse. Source: @akuchen_66498, 2026-10-11 (CMP 170hx Clean Room Discussion server)
    Source: @akuchen_66498, 2026-11-12 (CMP 170hx Clean Room Discussion server)
    Source: @stsoftware_88487, 2026-11-16 (CMP 170hx Clean Room Discussion server)
  • Warning Check a generated plan offline. Build an offline decoder and checker, confirm the plan keeps unrelated settings and defect masks and that the target rows are unused; "Two models agreeing isn't verification" (@galygious). Do not run the ffcalc burn plan unchecked (above). Source: @galygious, 2026-11-15
    Source: @samuel_hayden., 2026-11-17
  • Warning Check the exact 32-bit word your tool will write. On two CMP 90HX cards a word meant to be 1 landed as 0x08000000 because of a script bug, and the rows are spent (below). Source: @truvv0r, 2026-11-03 (CMP 170hx Clean Room Discussion server)
    Source: @truvv0r, 2026-11-03 (CMP 170hx Clean Room Discussion server)
  • Warning Program as few single rows as possible, read each back, stop after a failure. About 40 program cycles in 2 hours stopped the fuse write path on two CMP 90HX cards (below). Source: @truvv0r, 2026-10-29 (CMP 170hx Clean Room Discussion server)
    Source: @truvv0r, 2026-11-02 (CMP 170hx Clean Room Discussion server)
  • Warning A fuse flag can disable RIR modification for good, even on unused RIR slots: "Ask me how I know" (@bigptoughneigh). A free slot does not guarantee that a gate burn lands; read the whole array first. Source: @bigptoughneigh, 2026-11-06 (CMP 170hx Clean Room Discussion server)
  • Warning Never burn ECC_EN_CONTROL. An AI-found table (@68x0) puts ECC_EN at row 6 bit 28 with a copy at row 7 bit 28, and ECC_EN_CONTROL at row 6 bit 29 and row 7 bit 29; @truvv0r: "Never do this", no reason given. ECC also needs the row remapper and poison containment (@dalzyyy). Source: @68x0, 2026-11-17 (CMP 170hx Clean Room Discussion server)
    Source: @truvv0r, 2026-11-17 (CMP 170hx Clean Room Discussion server)
    Source: @dalzyyy, 2026-11-17 (CMP 170hx Clean Room Discussion server)
  • Warning Enabling FBPs marked defective is the biggest brick risk named. On the 8 GB card all re-fusing happens in one glitch window with no software test of a defective FBP, and "If the fusing results in a unbootable card, there is no way to recover" (@petrikrohn_26497). Kate disagrees (see the sixth stack). Source: @petrikrohn_26497, 2026-11-11 (CMP 170hx Clean Room Discussion server)
  • Reported SBFE=0 is needed to burn inside the FF space; DSOV=0 alone is not the gate, and getting one without the other does not seem possible (@mellojello_). Contested in open questions. Source: @matstatman, 2026-11-16 (CMP 170hx Clean Room Discussion server)
    Source: @mellojello_, 2026-11-16 (CMP 170hx Clean Room Discussion server)
  • Reported Without the gate only the field-programmable rows take a burn. Burns in rows 192-221 worked on an 8 GB card; "everything outside of that window was no land", and a burn at row 302 was accepted and programmed nothing (@n2dcrypt). A landed burn there proves only the write path. Which rows are programmable depends on what is already spent (@zagitta). Source: @n2dcrypt, 2026-11-03 (CMP 170hx Clean Room Discussion server)
    Source: @n2dcrypt, 2026-11-03 (CMP 170hx Clean Room Discussion server)
    Source: @n2dcrypt, 2026-11-06 (CMP 170hx Clean Room Discussion server)
    Source: @n2dcrypt, 2026-11-07 (CMP 170hx Clean Room Discussion server)
    Source: @zagitta, 2026-11-16 (CMP 170hx Clean Room Discussion server)
  • Reported DSOV cannot be cleared with FF records. It is bit 5 of fuse rows 0 and 1; on 10 GB cards two RIR records override it, "Only RIRs can undo them" (@petrikrohn_26497). Reading DSOV back did not re-sense it (@zagitta: "DSOV reads latched hardware state"). Source: @petrikrohn_26497, 2026-10-17 (CMP 170hx Clean Room Discussion server)
    Source: @petrikrohn_26497, 2026-11-11 (CMP 170hx Clean Room Discussion server)
    Source: @zagitta, 2026-11-17 (CMP 170hx Clean Room Discussion server)
  • Reported Take a raw fuse dump read-only, one card at a time. @mbelli's procedure for ga100_fuse_dump.py (10-03): run --check, read rows 0, 8 and 24 twice in a different order, then all 512 rows twice, the second pass in reverse, and compare; discard the dump on any disagreement, timeout or unrestored controller. It must never be changed to write. @bigptoughneigh's AI agent rule (07-12): never write the fuse controller range 0x820004 to 0x820060. Such a dump does not include the RIR records. Never post a full dump (see Unlock without bricking). Source: @bigptoughneigh, 2026-07-12 (CMP 170hx Clean Room Discussion server)
    Source: @akuchen_66498, 2026-10-02 (CMP 170hx Clean Room Discussion server)
    Source: @mbelli, 2026-10-03 (CMP 170hx Clean Room Discussion server)
  • Reported Where the rows sit (members' reads, partly AI-assisted): regular fuses in rows 0-221 and FF records in 222-487 per Kate's blog (@killred, whose dump matched it for the first rows); on one 8 GB card rows 222-302 were consumed by the boot parser while 303-487, and records burned into 128-131, were ignored (@port00). An FF row decodes as a chain, an offset and 16 data bits, the higher row wins, and the 16 RIR records sit in a separate 8-row macro (AI-generated analysis, not measured). Source: @petrikrohn_26497, 2026-10-02 (CMP 170hx Clean Room Discussion server)
    Source: @petrikrohn_26497, 2026-10-02 (CMP 170hx Clean Room Discussion server)
    Source: @killred, 2026-11-16
    Source: @port00, 2026-11-16
    Source: @killred, 2026-11-17

Brick and failure reports

An 8 GB card stuck by invalidated factory records and a bit-5 row, reported restored on 18 November

Warning 8 GB On @port00's 8 GB card, two factory records were invalidated, which zeroed GPC_DISABLE and FBP_DISABLE ("the gpu worked fine until invalidation"), so dead units were enabled. The replacement records could not take effect: the AI-written tool had burned a word with bit 5 set into row 303, just above the card's last FF record ("it didn't know about bit5"), which ended the region, and no free row was left inside it. Records he then burned into regular rows below 222 were ignored too. The card still showed in lspci but would not load drivers, and a 4-GPU mining board would not boot with it. He mostly used Qwen8Max and GLM5.3. @killred suggested making that row get discarded by burning its remaining bits and called a model-written fix "hallucinating". On 11-18 @port00 reported the damage reversed, "with some help", by burning row 303 to all ones ("convert binary to hex and you get 0xFFFF...."); @wakeupmbrc1 did not understand how, since rows 304-307 now read as FF writes. One report. What to do instead: the bit-5 and invalidation rules above; add row-invalidation checks to a plan even when the burn is fully planned (@wakeupmbrc1); read Kate's blog before such a burn (@killred).

Source: @port00, 2026-11-16
Source: @port00, 2026-11-16
Source: @port00, 2026-11-17
Source: @killred, 2026-11-17
Source: @port00, 2026-11-17
Source: @port00, 2026-11-17
Source: @wakeupmbrc1, 2026-11-17
Source: @wakeupmbrc1, 2026-11-17
Source: @port00, 2026-11-17
Source: @port00, 2026-11-17
Source: @port00, 2026-11-17
Source: @killred, 2026-11-17
Source: @killred, 2026-11-17
Source: @killred, 2026-11-17
Source: @port00, 2026-11-17
Source: @port00, 2026-11-18
Source: @port00, 2026-11-18
Source: @wakeupmbrc1, 2026-11-18
Source: @wakeupmbrc1, 2026-11-18
Source: @port00, 2026-11-18

A card off the bus after repeated "revival" IFF burns

Warning @stsoftware_88487 (11-17): his card with the same bit-5 error ("With my bit5-killer card didnt boot: GFW_BOOT progress 0x1.") "went into the sunset" after several tries of "revival" fuses written as correct IFF opcodes: it no longer shows on the PCIe bus. His own reading points to an overflow of the VBIOS BBX (black box journal) region, with the dead VBIOS state happening while old journal content was being erased at the moment a power glitch was applied. Nobody else confirmed the cause; the card's variant was not stated. Answering @petrikrohn_26497's note that at least one card was bricked by running out of free FF rows, he wrote "at least two cards". What to do instead: after a failed burn, debug before burning more (the canary rule above).

Source: @stsoftware_88487, 2026-11-17 (CMP 170hx Clean Room Discussion server)
Source: @stsoftware_88487, 2026-11-17 (CMP 170hx Clean Room Discussion server)

The fuse write path stopped on two CMP 90HX cards after about 40 program cycles

Warning On 10-29 @truvv0r reported that "a session of ~40 program cycles in 2 hours on two cards permanently killed the fuse WRITE path on both (reads unaffected, survives power cycles)". His rule then: never batch several write commands under one programming-voltage window and never repeat program cycles back to back. On 11-02, challenged by @stsoftware_88487, he corrected it: the cards were GA102 CMP 90HX, not GA100; he had not measured the programming rail or proved permanent damage, only that writes stopped succeeding after many attempts; and one successful single-row probe is no permission to run a ten-row set. On 11-16 he said the only reason his attempt failed was a bug in his Python script that set an incorrect value. What to do instead: as few single-row programs as possible, each read back, and stop after a failure.

Source: @truvv0r, 2026-10-29 (CMP 170hx Clean Room Discussion server)
Source: @truvv0r, 2026-10-29 (CMP 170hx Clean Room Discussion server)
Source: @stsoftware_88487, 2026-11-02 (CMP 170hx Clean Room Discussion server)
Source: @truvv0r, 2026-11-02 (CMP 170hx Clean Room Discussion server)
Source: @truvv0r, 2026-11-16 (CMP 170hx Clean Room Discussion server)

A wrong word burned on two CMP 90HX cards

Warning On 11-03 @truvv0r tried to plant a two-word IFF instruction in unused OTP rows of two GA102 CMP 90HX cards. The header word landed as intended, but the data word meant to be 1 landed as 0x08000000 (bit 27 instead of bit 0), so the rows never executed and are spent. "That's mystery with 0x08000000 is something we need widely explore and understand." @n2dcrypt relayed an AI reading that the tool wrote the field mask instead of the value; @truvv0r later blamed a bug in his script. What to do instead: dump the exact 32-bit words before any program command and check them against an independent decode.

Source: @truvv0r, 2026-11-03 (CMP 170hx Clean Room Discussion server)
Source: @truvv0r, 2026-11-03 (CMP 170hx Clean Room Discussion server)
Source: @n2dcrypt, 2026-11-03 (CMP 170hx Clean Room Discussion server)
Source: @truvv0r, 2026-11-16 (CMP 170hx Clean Room Discussion server)

A fried core voltage controller

Warning 8 GB and 10 GB During his voltage-controller experiments @dalzyyy fried his card's MP2888B, the controller for the core rail, and replaced it with an MP2888A, which "flashed with correct settings works as replacement to the mp2888b" (photo). He bought the A part rather than pay about 1 USD more for a B. The settings are not reproduced here. The controller also locks itself after a wrong write-unlock code (see the controller).

Source: @dalzyyy, 2026-11-07 (CMP 170hx Clean Room Discussion server)
Source: @dalzyyy, 2026-11-07 (CMP 170hx Clean Room Discussion server)
Source: @dalzyyy, 2026-11-07 (CMP 170hx Clean Room Discussion server)

Can a wrong burn be undone?

In the order posted:

  • @dalzyyy (11-16): "in terms of FF burning so long as you have rows left you can undo everything(dont take this as advice)". On 11-13 he thought a card that was only unstable under load could be reverted quite easily. Source: @dalzyyy, 2026-11-13
    Source: @dalzyyy, 2026-11-16
  • @wakeupmbrc1: a fix still needs the Pico soldered on; @lia_oc: on the 8 GB card you need the Pico to burn at all. Source: @wakeupmbrc1, 2026-11-16
    Source: @lia_oc, 2026-11-16
  • @kingsizexxxl: enough may be written by the FF blocks to keep a card from coming up. Source: @kingsizexxxl, 2026-11-16
  • @gnasherrr (11-16), on the stuck card: a wrong bit in one row made the boot loader ignore all the following ones. Source: @gnasherrr, 2026-11-16
  • @samuel_hayden. (11-17): a wrong value has to be corrected with more burns, "so you only have a limited number of attempts even though there are quite a few open". Source: @samuel_hayden., 2026-11-17
  • @wakeupmbrc1 (11-17): "certains instructions in FF semantics can completely brick the card when written in IFF". Source: @wakeupmbrc1, 2026-11-17

Contested 8 GB One card was reported restored by a correcting burn on 11-18 (above).

The A100 identity route (device ID and VBIOS)

Two device IDs are fused into the die

@petrikrohn_26497 (2026-06-29): the GPU die has two device IDs fused in, named ORIGNAL and REBRAND in an NVIDIA patent, and a strap resistor (strap5) selects between them. On the 10 GB die they are 2082 and 20C2; on the 8 GB die both are 20C2. The VBIOS cannot change the device ID. On 07-26 he reported that a member who flashed the 8 GB VBIOS onto a 10 GB card found it would not boot, and that the DEVID_SEL resistors (R240, R241) had not been located on the PCB. @zarquon3157's AI-assisted decode of fuse chain 2 (10-10) agrees: PCIE_DEVIDA reads 0x20c2 on the 8 GB card and 0x2082 on the 10 GB card, PCIE_DEVIDB 0x20c2 on both. Moving the strap is untested.

Reported 8 GB and 10 GB
Source: @petrikrohn_26497, 2026-06-29 (CMP 170hx Clean Room Discussion server)
Source: @petrikrohn_26497, 2026-07-23 (CMP 170hx Clean Room Discussion server)
Source: @petrikrohn_26497, 2026-07-26 (CMP 170hx Clean Room Discussion server)
Source: @zarquon3157, 2026-10-10 (CMP 170hx Clean Room Discussion server)

Re-fusing the device ID, then an A100 VBIOS

  • On 11-11 @petrikrohn_26497 passed on that it is possible to re-fuse the 10 GB card with the device ID of the A100 PCIe 40GB and flash an A100 VBIOS, so no unlocker is needed; it should also work on 8 GB cards. He had found the 40 GB VBIOS on HPE's support site but never an A100 PCIe 80GB file. Source: @petrikrohn_26497, 2026-11-11 (CMP 170hx Clean Room Discussion server)
  • On 11-14 @zagitta: "I have flashed the A100 vbios shared here earlier to my card after changing devid and it is fully unlocked without any software" (screenshot), about 5-10 W more at idle with all 128 SMs. @ichundes saw the same at idle and maybe +50 W under load, with 170tune and ndiv70. @zagitta's steps as he posted them: "nvflash, change devida + devidb, coldboot, nvlfash a100 bios shared here earlier". He gives only high-level instructions, because details invite legal trouble. Source: @zagitta, 2026-11-14 (CMP 170hx Clean Room Discussion server)
    Source: @zagitta, 2026-11-14 (CMP 170hx Clean Room Discussion server)
    Source: @zagitta, 2026-11-14 (CMP 170hx Clean Room Discussion server)
    Source: @zagitta, 2026-11-14 (CMP 170hx Clean Room Discussion server)
    Source: @zagitta, 2026-11-15 (CMP 170hx Clean Room Discussion server)
    Source: @ichundes, 2026-11-15 (CMP 170hx Clean Room Discussion server)
    Source: @zagitta, 2026-11-16 (CMP 170hx Clean Room Discussion server)
  • On 11-15 and 11-16 he qualified it: the SS0 and SS1 issue-rate limiters were still at the CMP values after the A100 80 GB VBIOS ("It's not vbios"); they "need to be written via IFF", which worked for him. @dalzyyy: FP64 and ECC poison containment are column-backed and cannot be re-enabled by FF records. Source: @zagitta, 2026-11-15 (CMP 170hx Clean Room Discussion server)
    Source: @dalzyyy, 2026-11-15 (CMP 170hx Clean Room Discussion server)
    Source: @zagitta, 2026-11-15 (CMP 170hx Clean Room Discussion server)
    Source: @zagitta, 2026-11-16 (CMP 170hx Clean Room Discussion server)
    Source: @zagitta, 2026-11-16 (CMP 170hx Clean Room Discussion server)
  • On 11-16 @zagitta had ECC working after the glitch without software unlocking, and on 11-17 said burning the A100 device ID "It's required for ECC without software changes". @kingsizexxxl's own cmpunlocker-style tool for the SS values and ECC got through about 10 rows on the A100 VBIOS before the card wedged and dropped off the bus; his card identifies as an A100, and he was deciding whether to glitch again to make it identify as a CMP or wait for the rest of the FF and IFF patches. Source: @zagitta, 2026-11-16 (CMP 170hx Clean Room Discussion server)
    Source: @kingsizexxxl, 2026-11-16
    Source: @kingsizexxxl, 2026-11-17 (CMP 170hx Clean Room Discussion server)
    Source: @zagitta, 2026-11-17
  • On 11-18 @zagitta: there is also the choice of CMP against A100 VBIOS. "A100 has lower HBM clocks but that's relatively easy to fix with nvidia driver modprobe romOverride", the registry path of the stock 615 driver that he first used on 11-02 to flip a bit in GSP's in-memory copy of a card's own VBIOS (see ECC). @dalzyyy: A100 nvidia-smi power readings vary from 40 to 70 W because running nvidia-smi a few times in a row spikes the draw. Source: @zagitta, 2026-11-02 (CMP 170hx Clean Room Discussion server)
    Source: @zagitta, 2026-11-18
    Source: @dalzyyy, 2026-11-18
  • Other views: @68x0 (11-14): it gets you most A100 features without cmpunlocker; @ob88594 (11-17): even with the A100 VBIOS you still need unlocking software; @okrasit. on whether the card then runs as an A100 in Windows: "If current includes fuses to set the pci-id to A100, yes"; @.shakdiesel decided redoing the process to burn the A100 ID was not worth it, and @zanooda sees no reason while software patches are still needed. @cibernox read the glitch plus a VBIOS flash as a full A100 apart from the NVLink cutout in the heatsink and some missing NVLink parts, and asked whether it finally gives proper P-states (no answer). Source: @68x0, 2026-11-14 (CMP 170hx Clean Room Discussion server)
    Source: @cibernox, 2026-11-14 (CMP 170hx Clean Room Discussion server)
    Source: @ob88594, 2026-11-17
    Source: @okrasit., 2026-11-17
    Source: @.shakdiesel, 2026-11-17
    Source: @zanooda, 2026-11-17
    Source: @cibernox, 2026-11-18 (CMP 170hx Clean Room Discussion server)

Reported 8 GB and 10 GB One first-hand report with a screenshot, later qualified; nobody else posted an nvidia-smi readout of a re-fused card by 11-18.

Where do SS0 and SS1 come from?

In the order posted:

  • @zagitta (11-16): "It's not vbios": after changing DEVIDA and DEVIDB and flashing the A100 80 GB VBIOS, SS0 and SS1 were still at the CMP values; they need IFF. Source: @zagitta, 2026-11-16 (CMP 170hx Clean Room Discussion server)
    Source: @zagitta, 2026-11-16 (CMP 170hx Clean Room Discussion server)
  • @petrikrohn_26497 (11-16) had understood SS0 and SS1 to come from the VBIOS: a March test that put the 170HX VBIOS on an A100 engineering sample dropped the issue rate to 1/64. He asked whether IFF is really needed. Source: @petrikrohn_26497, 2026-11-16 (CMP 170hx Clean Room Discussion server)
  • @truvv0r (11-16): the IFF program has nothing related to the SS0/SS1 limit, only rumours that IFF can set it. Source: @truvv0r, 2026-11-16 (CMP 170hx Clean Room Discussion server)

Contested 8 GB and 10 GB

Warning Do not flash an A100 VBIOS without the device-ID change. The ID is fused, so without the re-fuse an A100 VBIOS leaves the card unbootable; an 8 GB VBIOS on a 10 GB card did not boot either. Board requirements for an A100 VBIOS are on Unlock without bricking; see also VBIOS and firmware.

Source: @petrikrohn_26497, 2026-07-26 (CMP 170hx Clean Room Discussion server)
Source: @petrikrohn_26497, 2026-11-11 (CMP 170hx Clean Room Discussion server)

The 10 GB card and the glitch

The 10 GB card needs no glitch for the gate

The 10 GB card has empty RIR slots: one RIR burn opens the software override, and the rest can be done in software. @petrikrohn_26497 (10-03): enable the software override of the fuses with one available RIR record and use the software method; "When you are absolutely 100% sure what you want to change, use the spare fuse rows to rewrite the FF fuses." @stsoftware_88487: one RIR record gives 10 GB owners SW-IFF and control of all fuses. Asked whether lixiangwuxian/170hx-rir-tool is safe, @djpandaman: take a second to work out what you are burning, why and how it was calculated; everything else is reset by a cold boot. @petrikrohn_26497 (10-20): burning the two RIR rows is the risky part. @ghostinthedatacenter_87281: "Only did the one burn so I could do the software override". See RIR fuse burn.

Reported 10 GB
Source: @petrikrohn_26497, 2026-10-03 (CMP 170hx Clean Room Discussion server)
Source: @petrikrohn_26497, 2026-10-03 (CMP 170hx Clean Room Discussion server)
Source: @stsoftware_88487, 2026-10-03 (CMP 170hx Clean Room Discussion server)
Source: @innospark, 2026-10-16 (CMP 170hx Clean Room Discussion server)
Source: @djpandaman, 2026-10-17 (CMP 170hx Clean Room Discussion server)
Source: @petrikrohn_26497, 2026-10-17 (CMP 170hx Clean Room Discussion server)
Source: @ghostinthedatacenter_87281, 2026-10-17 (CMP 170hx Clean Room Discussion server)
Source: @petrikrohn_26497, 2026-10-20 (CMP 170hx Clean Room Discussion server)
Source: @68x0, 2026-10-23 (CMP 170hx Clean Room Discussion server)

48 GB on some 10 GB cards, never 80 GB

10 GB cards reach 48 GB when none of the six HBM stacks is defective, only disabled (@petrikrohn_26497, 10-20). @_orrorin after his RIR burn: "my RIR unlocked 10GB definitely, for sure, only has 48GB onboard". @mbelli has unlocked two 10 GB cards to 48 GB (2 of 15; he has heard 10 percent is the average) and thinks more would need a Samsung-specific initialisation. @analyticeth: 4 of 5 of his 10 GB cards went to 48 GB and 4 of 5 to 128 SMs; "I tried pushing above 48GB but it just aliased back onto another stack already in use" (serial numbers not sequential). @_orrorin added on 11-17 that Kate unlocked a full card and said 48 GB is the maximum. @toffles3179 has one card with FBPs 6 and 11 disabled but not defective and another with them disabled and defective. @matstatman (11-17): "10gb have rare 48gb proven, 40gb is common." Asked whether the glitch changes this, @djpandaman: "yes but the main thing you're looking for to get 80GB is locked behind samsung's silicon not nvidia's"; @68x0: "Still 10GB=40/44/48GB, 8gb = 80GB"; @lia_oc: "10gb -> 80gb wasn't ever achieved stable or fully addressable". @c133 heard of no difference with the glitch, and nobody reported glitching a 10 GB card by 11-18.

Proven 10 GB
Source: @toffles3179, 2026-10-08 (CMP 170hx Clean Room Discussion server)
Source: @petrikrohn_26497, 2026-10-20 (CMP 170hx Clean Room Discussion server)
Source: @_orrorin, 2026-10-21 (CMP 170hx Clean Room Discussion server)
Source: @djpandaman, 2026-11-11
Source: @68x0, 2026-11-13
Source: @lia_oc, 2026-11-13
Source: @c133, 2026-11-15 (CMP 170hx Clean Room Discussion server)
Source: @matstatman, 2026-11-17
Source: @_orrorin, 2026-11-17 (CMP 170hx Clean Room Discussion server)
Source: @mbelli, 2026-11-17 (CMP 170hx Clean Room Discussion server)
Source: @analyticeth, 2026-11-17
Source: @mbelli, 2026-11-17
Source: @analyticeth, 2026-11-18

Why 80 GB fails on the 10 GB card (theories)

  • @petrikrohn_26497 (07-12): some, maybe most, 10 GB cards carry Samsung 16 GB HBM2e stacks strapped to the slower Samsung HBM2 setting, like the A100 40 GB. @djpandaman (10-04): the Samsung on-die logic kills a row-address bit, halving each stack; 80 GB would need the sixth stack plus IEEE 1500 commands; earlier (09-30) he said that without Samsung's vendor WIC code there is no getting around the on-die logic that "destroys bit 15". @bigptoughneigh (10-01) thought the bit is present, since it works during soft row remapping. Source: @petrikrohn_26497, 2026-07-12 (CMP 170hx Clean Room Discussion server)
    Source: @djpandaman, 2026-09-30 (CMP 170hx Clean Room Discussion server)
    Source: @bigptoughneigh, 2026-10-01 (CMP 170hx Clean Room Discussion server)
    Source: @djpandaman, 2026-10-04 (CMP 170hx Clean Room Discussion server)
  • @angrykirc (11-17): doubling the density on a 10 GB card would need the HBM base die reprogrammed, and it is unknown whether the stacks are 16-high or 8-high (@ob88594 answered "16" with nothing posted). @wakeupmbrc1: the HBM2 stacks are locked by "proprietary firmware/wic" even if they are likely 16 GB parts. @scallion_9883: "if the 10gb stacks are 16gb then they're fused on the actual HBM itself, not on the ga100 silicon", and "so 48gb will be max of all stacks if you have a unicorn". @dalzyyy named the HBM PHY as the next target for voltage glitching; Kate: "Nothing ever happens". Source: @dalzyyy, 2026-11-13 (CMP 170hx Clean Room Discussion server)
    Source: @angrykirc, 2026-11-17
    Source: @angrykirc, 2026-11-17
    Source: @ob88594, 2026-11-17
    Source: @wakeupmbrc1, 2026-11-17
    Source: @scallion_9883, 2026-11-17
    Source: @scallion_9883, 2026-11-17
    Source: @onemillionkates, 2026-11-17

Theory 10 GB

80 GB folds above 40 GB: July and November

July (clean room): @bigptoughneigh relayed that @jonpry_77715 measured full speed at 40 GB on a 10 GB card but only 70 percent compute speed stable at full size; @dalzyyy relayed a Bilibili follow-up: 40 GB replicated, 80 GB sometimes hits the same error; a 30 GiB write and read-back was clean at 40 GB; with all 20 FBPAs at 4 GB per channel his driverless chain still folded at 40 GiB; on 07-23 a driverless 80 GB setup booted with 81920 MiB and an alias probe over 310 blocks (77.5 GiB) found every tag distinct, and @gk_hun's two-context test allocated and cleared 77 GiB, but "The actual kernel launch on >40GB addresses caused fatal GPU loss". Re-running devinit on another strap stopped the driver loading (RmInitAdapter failed). November (main server): @bruno063185 gets 80 GB in nvidia-smi, but "anything above 37.5G (I do have the exact number somewhere) up to 80G, folds" and needs a power cycle, while 40 GB mode works; writes without CUDA came back as a mirror. @cute_sc2: on 10 GB cards above 40 GB does not work, "And might on a majority never work". @djpandaman: the fold is in the upper half of physical memory, and "I think 48G just works on the cards with 6 stacks and most have 5".

Reported 10 GB
Source: @bigptoughneigh, 2026-07-07 (CMP 170hx Clean Room Discussion server)
Source: @dalzyyy, 2026-07-18 (CMP 170hx Clean Room Discussion server)
Source: @bigptoughneigh, 2026-07-21 (CMP 170hx Clean Room Discussion server)
Source: @bigptoughneigh, 2026-07-22 (CMP 170hx Clean Room Discussion server)
Source: @bigptoughneigh, 2026-07-23 (CMP 170hx Clean Room Discussion server)
Source: @gk_hun, 2026-07-23 (CMP 170hx Clean Room Discussion server)
Source: @bigptoughneigh, 2026-07-27 (CMP 170hx Clean Room Discussion server)
Source: @gnasherrr, 2026-11-16
Source: @deejay9983, 2026-11-16
Source: @bruno063185, 2026-11-16
Source: @bruno063185, 2026-11-16
Source: @bruno063185, 2026-11-16
Source: @bruno063185, 2026-11-16
Source: @cute_sc2, 2026-11-16
Source: @djpandaman, 2026-11-16
Source: @djpandaman, 2026-11-16

The July "4 GB per channel" reading

In the order posted:

  • @bigptoughneigh (07-23), from his AI assistant's logs: a managed-memory atomic kernel paging past 40 GB flipped the value at 0x17E2A0 from 0x70000300 to 0x10000300, read as "4GB/ch RE-ENABLED", but the same fault poisoned the CUDA context and the value reverted. Source: @bigptoughneigh, 2026-07-23 (CMP 170hx Clean Room Discussion server)
  • @mbelli (10-02), from NVIDIA's public GA100 header in the linux-nvgpu tree: 0x17e2a0 and 0x17e2a4 are the L2 cache invalidate and clean controls; 0x10000300 leaves only the evict-last class. "It is not a 4 GB/channel setting." Source: @mbelli, 2026-10-02 (CMP 170hx Clean Room Discussion server)

Contested 10 GB

Does the canary paper explain 80 GB?

In the order posted (11-16 and 11-17):

  • @xanthefin: Jon unlocked to 80 GB in the original paper ("A Canary in the Crypto Mine") and explained how to avoid the crash in a single paragraph, though he never saw it replicated. Source: @xanthefin, 2026-11-16
    Source: @xanthefin, 2026-11-16
    Source: @xanthefin, 2026-11-16
    Source: @xanthefin, 2026-11-16
  • @bruno063185: the paper does not explain it properly, the author did not answer his email, and the memory above 40 GB is not faulty but unreachable by any write path. Source: @bruno063185, 2026-11-16
    Source: @bruno063185, 2026-11-16
    Source: @bruno063185, 2026-11-16
  • @ob88594: 40 to 80 GB needs a specific initialisation method for Samsung HBM that nobody discloses. Source: @ob88594, 2026-11-17

Contested 10 GB

gpu-unlock and gpcprobe on RIR-burned 10 GB cards

On 11-18 @lycorascence reported that gpu-unlock shows many issues on her 10 GB card, stock apart from the RIR burn, where cmpunlocker does not; @zagitta has not tested that path, says gpu-unlock is more or less 1:1 with cmpunlocker, and asked whether it might be unlocking defective SMs by mistake. She answered that her GPCs and sixth stack read disabled, not defective. Separately, gpcprobe showed 16/16 spare fuses active although the RIR tool reads her gate burn as done; minutes later she said she had misread a column, so whether that reading was a misread too is unclear. Compare gpcprobe's RIR line with the RIR tool before acting on it.

Reported 10 GB
Source: @lycorascence, 2026-11-18
Source: @zagitta, 2026-11-18
Source: @lycorascence, 2026-11-18
Source: @zagitta, 2026-11-18
Source: @lycorascence, 2026-11-18
Source: @lycorascence, 2026-11-18
Source: @lycorascence, 2026-11-18
Source: @lycorascence, 2026-11-18

NVLink after the glitch

What the board is missing

@gluckmaker (2026-07-07): NVLink is both fuse-disabled and missing small parts. Five resistors just above the GPU (PCIe connector down) with visible tracks to the middle NVLink connector are populated on a genuine A100 and missing on the CMP; from the schematic he expects R976, R1030 (page 4), R1029 (page 5), R1024, R238 and R236 (page 17). The last three run straight to the connector; R1029 and R1030 link to balls F1 and G1 at the chip edge and can be reached with a thin wire; R976 goes to ball F51 under the chip. Beyond that, @wakeupmbrc1 listed DrMOS stages, inductors and capacitors and maybe MP2888 PWM straps (11-16); @ghostinthedatacenter_87281 wonders about a second SPI chip and an STM32 for power sequencing; the STM32-like chip on full A100 boards turned out to be their root-of-trust chip (@m3gagluk). @bigptoughneigh understood from Kate that NVLink is only powered on the middle bridge connector (11-11).

Reported 8 GB and 10 GB
Source: @gluckmaker, 2026-07-07 (CMP 170hx Clean Room Discussion server)
Source: @gluckmaker, 2026-07-07 (CMP 170hx Clean Room Discussion server)
Source: @bigptoughneigh, 2026-11-11 (CMP 170hx Clean Room Discussion server)
Source: @wakeupmbrc1, 2026-11-16
Source: @ghostinthedatacenter_87281, 2026-11-16
Source: @m3gagluk, 2026-11-16
Source: @m3gagluk, 2026-11-16

Kate's 3.3 V jumper, and fitting the real part

Kate (@onemillionkates, 11-16): "3v3 bridge is not for the faint of heart". She passes the PCIe 3.3 V rail straight to the bridge, bypassing circuitry that presumably exists for protection and current limiting; in her use case that is fine, "all I can tell you is that it works", and the bandwidth "lined up with the full link rate". @shirogeek reads the minimum as U11 with its decoupling capacitors and some resistors (Kate suggests only the resistors) and plans to fit the missing parts, glitch and test with three bridges. @m3gagluk would rather fit the 5-pin chip: owners cutting their aluminium shells may leave metal whiskers, and a 5-pin part is cheaper to replace than power stages, a controller or a burned PCB; speed unlocks can still be written into the FF records. @cute_sc2 may go "the proper way". Fitting the missing IC (a QFN-40) needs hot air, a preheater and probably a stencil, more than the x16 capacitor mod (@samuel_hayden.; the glitch needs no preheater); a clamp will not hold it. @ghostinthedatacenter_87281 suggests the blog's workaround unless you want the board built as the schematic says. @prometasfw expects shops that do the x16 mod to offer it.

Reported 8 GB and 10 GB
Source: @ghostinthedatacenter_87281, 2026-11-12
Source: @ghostinthedatacenter_87281, 2026-11-12
Source: @samuel_hayden., 2026-11-12
Source: @samuel_hayden., 2026-11-12
Source: @samuel_hayden., 2026-11-12
Source: @prometasfw, 2026-11-12
Source: @samuel_hayden., 2026-11-12
Source: @samuel_hayden., 2026-11-12
Source: @samuel_hayden., 2026-11-12
Source: @shirogeek, 2026-11-16
Source: @onemillionkates, 2026-11-16
Source: @onemillionkates, 2026-11-16
Source: @onemillionkates, 2026-11-16
Source: @onemillionkates, 2026-11-16
Source: @onemillionkates, 2026-11-16
Source: @cute_sc2, 2026-11-16
Source: @onemillionkates, 2026-11-16
Source: @shirogeek, 2026-11-17
Source: @m3gagluk, 2026-11-17
Source: @m3gagluk, 2026-11-17

The NVLink disable fuse

On 11-13 @ghostinthedatacenter_87281, on 10 GB cards, burned an FF record so the NVLink disable mask reads 0 at boot, without the glitch; Kate: "that sounds like you did it the right way". @shirogeek asked whether NVLink had been tested physically; no answer. On 11-15 @bayley_w said the 8 GB card now gets "the same features as 10gb now (last stack of memory, nvlink, pcie4, all sm's)" through the glitch; no NVLink result on a glitched 8 GB card was posted by 11-18, and CUTE's no-solder jig still needs NVLink parts soldered. See NVLink.

Reported 8 GB and 10 GB
Source: @ghostinthedatacenter_87281, 2026-11-13
Source: @ghostinthedatacenter_87281, 2026-11-13
Source: @onemillionkates, 2026-11-13
Source: @shirogeek, 2026-11-14
Source: @bayley_w, 2026-11-15
Source: @bayley_w, 2026-11-15
Source: @cute_sc2, 2026-11-16

Buying a card for this

Not every 8 GB card reaches 80 GB

In each owner's batch posted on 11-16 one card stopped at 64 GB: @gnasherrr 1 of 8 ("1 dud"), @jj48. 1 of 4, @replacedriver47 1 of 4, @deejay9983 1 of 6. @froggao: "Not all 64gbs can" unlock to 80, and some owners have one card that stays at 64 GB but reaches 120+ SMs. @jj48. expects many 8 GB cards sold from now on to be 64 GB cards, and @zagitta wondered whether a seller then advertising heavily was pre-binning and shipping out the 64 GB-only cards. Before you pay for a card meant for this unlock, ask for the seller's read of that card's own fuses (a gpcprobe report or a fuse dump): that is what shows whether the card is a 64 GB card.

Reported 8 GB
Source: @replacedriver47, 2026-11-16
Source: @jj48., 2026-11-16
Source: @jj48., 2026-11-16
Source: @gnasherrr, 2026-11-16
Source: @deejay9983, 2026-11-16
Source: @froggao, 2026-11-16
Source: @froggao, 2026-11-17
Source: @zagitta, 2026-11-17

Does an unglitched card risk being a dud?

In the order posted (11-15):

  • @spectakkular: "If you buy a listing that hasn't been voltage glitched, it risks being a dud which drives down the price. Wait and you can eliminate that risk". Source: @spectakkular, 2026-11-15 (CMP 170hx Clean Room Discussion server)
  • @matstatman: "Dud as can't be glitched? I don't think thats possible". Source: @matstatman, 2026-11-15 (CMP 170hx Clean Room Discussion server)

Contested 8 GB

What the fuse reads of 8 GB cards show

  • @newman_08462 (10-06): "I checked almost 100 pcs 170HX-8G cards... all of them are 4 disabled FBP and 2 defective FBP"; among the 3 disabled GPCs there is about a 40 percent chance that one is defective and a 60 percent chance that none is. @n2dcrypt saw identical masks on every 8 GB card he tested (FBPs 1 and 4 disabled without a defect flag, 6 and 11 defect-flagged); @con3po7016 the same, with one extra defective compute unit on one card. @matstatman expected most 8 GB cards to reach 80 GB. @stsoftware_88487 posted a summary of 10 unique fuse dumps (11-02). Source: @newman_08462, 2026-10-06 (CMP 170hx Clean Room Discussion server)
    Source: @matstatman, 2026-10-06 (CMP 170hx Clean Room Discussion server)
    Source: @matstatman, 2026-10-06 (CMP 170hx Clean Room Discussion server)
    Source: @n2dcrypt, 2026-10-07 (CMP 170hx Clean Room Discussion server)
    Source: @con3po7016, 2026-10-07 (CMP 170hx Clean Room Discussion server)
    Source: @stsoftware_88487, 2026-11-02 (CMP 170hx Clean Room Discussion server)
  • July, read-only: @scallion_9883's ga100_topology_report.py on 8 GB and 10 GB cards from three owners (@bigptoughneigh, @gk_hun, @newman_08462): every card had 5 active GPCs and 35 TPCs (70 SMs) at the fuse floor, and in two GPCs one TPC was off only through RECONFIG. Which GPCs are disabled differs per card (@bigptoughneigh: "gpc_disable 85 instead of your 13"). Proven Source: @scallion_9883, 2026-07-24 (CMP 170hx Clean Room Discussion server)
    Source: @bigptoughneigh, 2026-07-24 (CMP 170hx Clean Room Discussion server)
    Source: @gk_hun, 2026-07-24 (CMP 170hx Clean Room Discussion server)
    Source: @newman_08462, 2026-07-24 (CMP 170hx Clean Room Discussion server)
    Source: @bigptoughneigh, 2026-07-24 (CMP 170hx Clean Room Discussion server)
    Source: @bigptoughneigh, 2026-07-24 (CMP 170hx Clean Room Discussion server)
  • @mountains1605 and @con3po7016 (10-04): the SKU ID is not constant on 8 GB cards, 0x82 on two of eight cards and 0x80 on six (@mbelli's AI review agreed); unexplained. @mountains1605's four 8 GB dies all read 0x004906D1 at the FBPA offset 0x350; he first read byte 1 as an SK hynix code, then corrected himself: in the JEDEC JEP106 list 0x06 is another maker, so whether it is a vendor field is unproven. Source: @mountains1605, 2026-10-04 (CMP 170hx Clean Room Discussion server)
    Source: @mountains1605, 2026-10-04 (CMP 170hx Clean Room Discussion server)
    Source: @mountains1605, 2026-10-04 (CMP 170hx Clean Room Discussion server)
    Source: @con3po7016, 2026-10-04 (CMP 170hx Clean Room Discussion server)
    Source: @mbelli, 2026-10-04 (CMP 170hx Clean Room Discussion server)
  • The "defective" FBPs may not be bad (theory): @petrikrohn_26497 (10-07): "If every 170HX has exactly two "defective" FBPs, then most likely they are not really defective, but only marked so."; @bigptoughneigh: the "defective" ones run much hotter, and he suspects bad-memory reports are stacks hitting 95 C. Source: @petrikrohn_26497, 2026-10-07 (CMP 170hx Clean Room Discussion server)
    Source: @bigptoughneigh, 2026-10-07 (CMP 170hx Clean Room Discussion server)
  • July (@petrikrohn_26497): all six HBM2 stacks are present on every card seen; a typical 8 GB card has 2 FBPs marked defective and 2 more disabled, and "Nvidia tested them and found them to be OK" for the disabled ones; on the one card read then, all SMs were marked good. @dalzyyy summed it up as 96 GB, 16 GB "defective", 16 GB disabled and 64 GB usable; @.d3dx9 read one defective and one disabled stack on an 8 GB dump; @bigptoughneigh: the host sees disabled against defective, and GSP-RM changes some values back when it loads. Against it, @jonpry_77715 (07-18): "its the floorsweep in vbios that turns all the cool stuff off". Source: @jonpry_77715, 2026-07-18 (CMP 170hx Clean Room Discussion server)
    Source: @petrikrohn_26497, 2026-07-18 (CMP 170hx Clean Room Discussion server)
    Source: @petrikrohn_26497, 2026-07-18 (CMP 170hx Clean Room Discussion server)
    Source: @dalzyyy, 2026-07-18 (CMP 170hx Clean Room Discussion server)
    Source: @bigptoughneigh, 2026-07-19 (CMP 170hx Clean Room Discussion server)
    Source: @bigptoughneigh, 2026-07-19 (CMP 170hx Clean Room Discussion server)
    Source: @.d3dx9, 2026-07-23 (CMP 170hx Clean Room Discussion server)
    Source: @petrikrohn_26497, 2026-07-23 (CMP 170hx Clean Room Discussion server)

Reported 8 GB How to read your own card is on Fuses and floorsweep maps and gpcprobe.

Prices and effort

@spectakkular expects the glitch to raise a card's value by far more than a PCB order costs. @cute_sc2 told a seller that an easy unlock would come within weeks, after which cards sell for more. Card prices are on Price history, November 2026.

Reported 8 GB
Source: @spectakkular, 2026-11-11
Source: @cute_sc2, 2026-11-16
Source: @cute_sc2, 2026-11-16

Open questions

Is there a working sixth HBM stack on the 8 GB card?

In the order posted:

  • @cute_sc2 (2026-10-02, before GA100VFI): 8 GB cards can do 64, 80 or 96 GB, "Somewhere like 30%, 60%, 10%". @bigptoughneigh: "no, sw only. All 8GB actual cmp170hx have 96". Source: @cute_sc2, 2026-10-02 (CMP 170hx Clean Room Discussion server)
    Source: @cute_sc2, 2026-10-02 (CMP 170hx Clean Room Discussion server)
    Source: @bigptoughneigh, 2026-10-02 (CMP 170hx Clean Room Discussion server)
  • @petrikrohn_26497 (11-01): the disabled and "defective" FBPs are often spread over four half-working stacks. Source: @petrikrohn_26497, 2026-11-01 (CMP 170hx Clean Room Discussion server)
  • @mbelli (11-11): should we try enabling the "defective" memory, since a failed memory training could be fixed by glitching again? On his 10 GB cards the defective memory really was defective. @cibernox: "If nvidia marked it as defective, I'm not touching it". Source: @mbelli, 2026-11-11 (CMP 170hx Clean Room Discussion server)
    Source: @cibernox, 2026-11-11 (CMP 170hx Clean Room Discussion server)
  • @petrikrohn_26497 (11-11): GPCs marked defective are genuinely defective, but FBPs 6 and 11, marked defective on almost all 8 GB cards, are probably there and working, with no way to test without fusing; Kate believes FBPs 6 and 11 sit on one stack that is missing from the package, he thinks they are on different stacks. @n2dcrypt posted an AI stack-map analysis agreeing with him (AI-generated analysis, not measured). Source: @petrikrohn_26497, 2026-11-11 (CMP 170hx Clean Room Discussion server)
    Source: @petrikrohn_26497, 2026-11-11 (CMP 170hx Clean Room Discussion server)
    Source: @n2dcrypt, 2026-11-11 (CMP 170hx Clean Room Discussion server)
  • @cibernox (11-11): the same two FBPs disabled on every card is fishy if they were real defects. @spectakkular: "Or it's a dummy stack". @cibernox: stacks cannot be dummies, and 96 GB A100s exist. @intervitens: memory stacks are separate dies, a GA100 die shot shows the dummy die, and a dummy needs no silicon change; he adds that rare cards are said to have four defective FBPs or none, the latter might reach 96 GB. @n2dcrypt suggested correlating the FBP profile with serial numbers or dates; @djpandaman: 2.5D packaging has a measurable failure rate and HBM cost about 100-150 per stack then (currency not stated), so a sixth stack is reasonable redundancy. Source: @cibernox, 2026-11-11 (CMP 170hx Clean Room Discussion server)
    Source: @spectakkular, 2026-11-11 (CMP 170hx Clean Room Discussion server)
    Source: @cibernox, 2026-11-11 (CMP 170hx Clean Room Discussion server)
    Source: @intervitens, 2026-11-11 (CMP 170hx Clean Room Discussion server)
    Source: @intervitens, 2026-11-11 (CMP 170hx Clean Room Discussion server)
    Source: @intervitens, 2026-11-11 (CMP 170hx Clean Room Discussion server)
    Source: @intervitens, 2026-11-11 (CMP 170hx Clean Room Discussion server)
    Source: @n2dcrypt, 2026-11-11 (CMP 170hx Clean Room Discussion server)
    Source: @djpandaman, 2026-11-12 (CMP 170hx Clean Room Discussion server)
    Source: @djpandaman, 2026-11-12 (CMP 170hx Clean Room Discussion server)
    Source: @djpandaman, 2026-11-12 (CMP 170hx Clean Room Discussion server)
  • Kate (@onemillionkates, 11-11): actual floorsweeping does not care about the DEFECTIVE mask, "good luck getting the dummy die to act like a real HBM stack though"; in her experience "it's not a one way door. you can always re-disable FBPs", a card boots to a fusing-capable state without a working framebuffer config, and it is at your own risk. On 11-13: you can disobey DEFECTIVE and set DISABLE to all zeroes; if the sixth stack is dead, framebuffer init fails, the card still boots to a state where fusing is possible, and you can glitch again for a more conservative value. Source: @onemillionkates, 2026-11-11 (CMP 170hx Clean Room Discussion server)
    Source: @onemillionkates, 2026-11-11 (CMP 170hx Clean Room Discussion server)
    Source: @onemillionkates, 2026-11-11 (CMP 170hx Clean Room Discussion server)
    Source: @onemillionkates, 2026-11-11 (CMP 170hx Clean Room Discussion server)
    Source: @onemillionkates, 2026-11-13
  • @mellojello_ (11-11) was fairly sure a function-level reset can test records in the glitched state without touching the fuse macro (untested); @replacedriver47 (11-16 and 11-18) called enabling a defective FBP a great way to brick the card and asked whether one could be tried for one boot through the software override. @djpandaman (11-16): opening everything might work, "but if one is defective it crashes off the bus". Source: @mellojello_, 2026-11-11 (CMP 170hx Clean Room Discussion server)
    Source: @replacedriver47, 2026-11-16
    Source: @replacedriver47, 2026-11-16
    Source: @djpandaman, 2026-11-16
    Source: @replacedriver47, 2026-11-18 (CMP 170hx Clean Room Discussion server)
  • 11-16 and 11-17: @jonathanyjoerrington had seen no dump of a 96 GB card; @cute_sc2: "No only 96gb", "And prob under 108sm"; @gnasherrr: "96 is vaporware"; @cmdaltesc: "Super super rare"; @matstatman: "96 gb are rare. Not fully proven yet. 80gb for 8gb is."; @angrykirc: six enabled stacks are very rare. Source: @jonathanyjoerrington, 2026-11-16
    Source: @cute_sc2, 2026-11-16
    Source: @cute_sc2, 2026-11-16
    Source: @gnasherrr, 2026-11-16
    Source: @cmdaltesc, 2026-11-16
    Source: @matstatman, 2026-11-17
    Source: @angrykirc, 2026-11-17

Contested 8 GB No 96 GB 8 GB card or dump was posted by 11-18. See Rumours and claims to verify.

What gates an FF burn?

In the order posted (clean room, 11-06 to 11-16), after @petrikrohn_26497 posted a fuse state machine diagram marking the programming step as suppressed when DSOV=1 (Source: @petrikrohn_26497, 2026-11-06 (CMP 170hx Clean Room Discussion server)):

  • @zarquon3157 doubted it: the programming power switch feeds the whole fuse macro, RIR records included. Source: @zarquon3157, 2026-11-06 (CMP 170hx Clean Room Discussion server)
  • @n2dcrypt: "I don't think that burns are DSOV gated, otherwise I couldn't have burned on 8GB." Source: @n2dcrypt, 2026-11-06 (CMP 170hx Clean Room Discussion server)
  • @petrikrohn_26497: no programming voltage is applied while DSOV is set; DSOV does not block burning the RIR rows, which is how 10 GB cards undo it. @stsoftware_88487 then asked why other rows still fail if DSOV protects only the first two. Source: @petrikrohn_26497, 2026-11-06 (CMP 170hx Clean Room Discussion server)
    Source: @stsoftware_88487, 2026-11-07 (CMP 170hx Clean Room Discussion server)
  • @scallion_9883: "fusing on main array other than that is gated by secure fusing field & DSOV field". Source: @scallion_9883, 2026-11-09 (CMP 170hx Clean Room Discussion server)
  • @mellojello_ (11-16): DSOV=0 is not needed in the traditional sense; SBFE=0 is required to burn any row within the FF space. Source: @mellojello_, 2026-11-16 (CMP 170hx Clean Room Discussion server)
  • The lab (11-19): on one 8 GB card, held states with DSOV 0 and CRC 0x55 but a privilege mask of 0xFFFFFEFE could not be burned: the burn tool's CMD_SENSE poisoned the fuse controller (FUSECTRL 0xBADF510E). Burns went through only from the full goldilocks state with the mask at 0xFFFFFFFF. This shows the privilege mask matters; it does not separate DSOV from SBFE. See states that cannot be burned. Source: @darkmaniac7, 2026-11-19 (lab notes)

Contested 8 GB and 10 GB No settling measurement was posted.

Can the 8 GB card's partly burned RIR record give Gen3?

In the order posted:

  • @petrikrohn_26497 (10-02) posted an AI answer from a private server: the one live RIR record on 8 GB cards is partly burned, and burning more bits into it redirects it so an FF record is spoiled and the Gen3-disable option clears, "proven safe across all 42 measured dies". His own explanation later: the trick spoils one FF row, and nobody knows what it does at the new offset. Source: @petrikrohn_26497, 2026-10-02 (CMP 170hx Clean Room Discussion server)
    Source: @petrikrohn_26497, 2026-10-03 (CMP 170hx Clean Room Discussion server)
    Source: @petrikrohn_26497, 2026-11-03 (CMP 170hx Clean Room Discussion server)
  • @akuchen_66498 followed the decode on paper and landed on a different row, which did not hold the expected record on his two 8 GB dumps. Source: @akuchen_66498, 2026-10-02 (CMP 170hx Clean Room Discussion server)
    Source: @akuchen_66498, 2026-10-03 (CMP 170hx Clean Room Discussion server)
  • @djpandaman asked whether the 42 dies were burned or only read. Source: @djpandaman, 2026-10-05 (CMP 170hx Clean Room Discussion server)
  • @replacedriver47 and @shirogeek (11-03): every 8 GB card reads the same record value ("All my cards show 0x0923") and they could not see how it reaches Gen3. Source: @replacedriver47, 2026-11-03 (CMP 170hx Clean Room Discussion server)
    Source: @replacedriver47, 2026-11-03 (CMP 170hx Clean Room Discussion server)
    Source: @shirogeek, 2026-11-03 (CMP 170hx Clean Room Discussion server)

Contested 8 GB Nobody posted a burned card; the bit-level steps are left out.

More memory bandwidth from more stacks?

@turbine expects bandwidth to improve a lot with the extra memory; @wakeupmbrc1: "+25% if +1fbp, 50% if +2". Arithmetic, not a measurement; the OpenCL run above is one member's figure.

Theory 8 GB
Source: @turbine, 2026-11-11
Source: @wakeupmbrc1, 2026-11-11

A reading of Kate's write-up

@m3gagluk (11-11): the route makes the controller skip the block on writing the fuseless fuses; he had expected to glitch through the whole fuse read and crowbar the rail. The glitcher only has to let the GPU reach a state where the FF rows can be edited; after that, by his reading, the card is unlocked without extra drivers, much like an RIR burn, and the wiring can come off. Later reports still needed IFF writes for SS0 and SS1, and a patched cmpunlocker for 80 GB.

Theory 8 GB
Source: @m3gagluk, 2026-11-11 (CMP 170hx Clean Room Discussion server)
Source: @m3gagluk, 2026-11-11 (CMP 170hx Clean Room Discussion server)

Other Ampere cards: CMP 90HX, RTX 3090 48 GB

  • CMP 90HX (GA102). @truvv0r rebuilt a GA102 register map from TU102 data; on his 90HX "IFF burning is working" but FF burning fails (10-23); the 90HX's IFF window starts earlier than a 3090's and runs 24 product-customization words, one result being that Gen3 is disabled; his multi-write tool did 102 writes in one run. @scallion_9883: there is no RIR on GA10x, and his tests on about 20 90HX cards behaved like the 8 GB 170HX without a spare RIR slot; @zagitta: GA102 has DSOV set and no RIR. See CMP 90HX unlock hub and the two 90HX failures above. Source: @truvv0r, 2026-10-23 (CMP 170hx Clean Room Discussion server)
    Source: @truvv0r, 2026-10-24 (CMP 170hx Clean Room Discussion server)
    Source: @scallion_9883, 2026-10-25 (CMP 170hx Clean Room Discussion server)
    Source: @truvv0r, 2026-10-26 (CMP 170hx Clean Room Discussion server)
    Source: @truvv0r, 2026-10-26 (CMP 170hx Clean Room Discussion server)
    Source: @zagitta, 2026-11-09 (CMP 170hx Clean Room Discussion server)
  • GeForce Ampere. Kate (11-17): researching a 48 GB RTX 3090 mod is what got her into this, finding Jon Pry's paper in August 2026; none of the 48 GB 3090 attempts she found had 48 GB usable, "arbitrary FF writes does change the likelihood a lot", but she has not looked into it seriously. @dalzyyy expects the device ID would have to be changed through FF records to use the A6000 VBIOS; @wakeupmbrc1 thinks a 48 GB 3090 and a 24 GB 3080 are possible with the glitch. @scallion_9883 (11-03): main-array fusing on GA10x had not been achieved. @nyancat3355 wondered whether a glitched CMP 70HX or 90HX becomes a full RTX 3070 Ti or 3080. Nothing tested. Source: @scallion_9883, 2026-11-03 (CMP 170hx Clean Room Discussion server)
    Source: @dalzyyy, 2026-11-17
    Source: @onemillionkates, 2026-11-17
    Source: @onemillionkates, 2026-11-17
    Source: @onemillionkates, 2026-11-17
    Source: @onemillionkates, 2026-11-17
    Source: @onemillionkates, 2026-11-17
    Source: @wakeupmbrc1, 2026-11-17
    Source: @wakeupmbrc1, 2026-11-17
    Source: @nyancat3355, 2026-11-18

Theory 8 GB and 10 GB

See also

Voltage-glitch unlock: lab method on a Pico 2 W, Voltage-glitch unlock: lab results and fuse findings, Unlock without bricking, Fuses and floorsweep maps, RIR fuse burn, Recovery, 8 GB compute and HBM: limits and open questions, Full SM unlock, NVLink, ECC, PCIe x16 capacitor mod, VBIOS and firmware, Verifying an unlock, gpcprobe, cmp170hx-ffcalc, 170hx-rir-tool, CMPGlitch fuse research archive, CMP 90HX unlock hub, The 10 GB card: provenance and the 80 GB question, Unlock history: who found what, and when, Unlock internals: status and what is next, Rumours and claims to verify.

Coverage: on 2026-11-12 @port00 posted a beyondimy.com article ("Voltage Glitching Unlocked an A100 in a Mining Card") and a YouTube short ("A mining card turned into an A100 with a voltage glitch (80 GB)"); @m3gagluk called the article a fully generated fluff piece with nothing added to Kate's post.

Source: @port00, 2026-11-12 (CMP 170hx Clean Room Discussion server)
Source: @port00, 2026-11-12 (CMP 170hx Clean Room Discussion server)
Source: @m3gagluk, 2026-11-12 (CMP 170hx Clean Room Discussion server)