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.
Revision as of 10:01, 30 October 2026 by ImportBot (talk | contribs) (Import: everything for the 8 GB card, @c133, @wakeupmbrc1, @djpandaman, @rh3dai, @ob88594, @mountains1605, @reala7096, @matstatman, @cute_sc2, @replacedriver47, @68x0, @kellertreppe123; gap-fill from #general 2026-10-22 to 10-26: @froggao, @scallion_9883, @lia_oc, @hezz1891, @djpandaman)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Reported 8 GB

The 8 GB card is the CMP 170HX with PCI ID 10de:20c2 and SK hynix HBM2e. It is the more common version and the one most recipes are written for. After the public unlock it is a 64 GB, 74 SM GA100 card on a PCIe Gen2 link. Not sure which card you have? See Which card do I have. New owner? Start with Start here#8gb.

At a glance

Stock After cmpunlocker v0.5 With hardware work
Memory 8 GB 64 GB (65536 MiB) same
SMs 70 74 same; no further path known
PCIe Gen1 x4 Gen2 x4 (Gen2 link retrain) Gen2 x16 with the PCIe capacitor mod
ECC off on (DRAM and SRAM) same
BAR1 64 MiB 64 GiB same
P2P none with the P2P patches (not on cmpunlocker master) same
NVLink fused off none no known path
Power limit 250 W or 300 W, depends on VBIOS same same

Unlock geometry, BAR1 and ECC per the cmpunlocker README and constants. Source: repo github.com/amoghmunikote/cmpunlocker by amoghmunikote on GitHub, posted by @rh3dai, 2026-10-08 74 SMs measured with torch on four cards, Gen2 x16 on modded cards, 64 GiB BAR1 measured. Source: repo github.com/PixelML/club-170hx by PixelML on GitHub, posted by @c133, 2026-10-20

Unlock results

Details and steps: Driver unlock, cmpunlocker forks and Unlocks.

  • Proven The public state is cmpunlocker v0.5: 64 GB, +4 SMs (70 to 74) and ECC. RH-3D posted a walkthrough video of v0.5. Source: @rh3dai, 2026-10-11 v0.5 added +4 SMs for both variants; more SMs exist on the 10 GB card, not on the 8 GB. Source: @lia_oc, 2026-10-22 ECC is the other new piece. Source: @reala7096, 2026-10-22 Amogh has said there is not much more to get through software, so v0.5 is likely the last feature release. Source: @reala7096, 2026-10-22
  • One owner ran v0.5 with ECC for 25 h: 64 GB, memtest clean, 0 ECC errors. Source: @mistyashhole, 2026-10-10 A first-time owner: booted, installed the driver, ran the unlock, and it did the rest. Source: @lenxtroz, 2026-10-13
  • If your card shows 70 SMs after the unlock, you are on an older build; the current one gives 74. Source: @matstatman, 2026-10-08
  • The 8 GB unlock writes nothing permanent to the card. Only the special 10 GB unlocks burn fuses. Source: @ob88594, 2026-10-12 The unlocks are volatile: the patched driver reapplies them every boot and a cold power cycle returns the card to stock. Source: repo github.com/PixelML/club-170hx by PixelML on GitHub, posted by @c133, 2026-10-20
  • Rough edge: some 8 GB cards are single-rank and stop at 32 GB. Validate the unlock with a CUDA-side memtest, not only memtest_vulkan. See Which card do I have#Cards that are not a normal 170HX.

Memory

  • Layout. SK hynix HBM2e, 16 of 24 FBPA active (4096-bit): two full stacks and four half stacks. FBP 6 and 11 are physically dead; FBP 1 and 4 are only floorswept. The 64 GB unlock keeps the same 16 FBPA and widens each from a 512 MiB window to 4 GiB. Source: repo github.com/matstatman/gpcprobe by matstatman on GitHub, posted by @matstatman, 2026-10-20 Almost every 8 GB card shows FBP 6 and FBP 11 marked defective. Source: @petrikrohn_26497, 2026-10-10
  • Clock. Stock HBM clock depends on the VBIOS: 92.00.67.00.01 runs NDIV 54 (1,458 MHz), 92.00.6D.00.0A runs NDIV 64 (1,728 MHz), same board and timings. Raising two NDIV 54 cards to 64 with 170tune gave +5.8-6.3% single-user decode on GLM-5.3-Flash TP4. Source: repo github.com/PixelML/club-170hx by PixelML on GitHub, posted by @c133, 2026-10-20
  • Overclock. The HBM divider is set with 170tune. Source: @wakeupmbrc1, 2026-10-12 Hynix cards usually reach NDIV 68-70; 74 fails. Source: @alanoo, 2026-10-14 The gain depends on the workload: NDIV 54 to 70 gave +10.5% at c=1 on dense Qwen3.8-27B, Source: @wakeupmbrc1, 2026-10-14 NDIV 70 gave 3-4% on the same model for another owner, Source: @fnerdman, 2026-10-14 and alanoo measured zero gain up to NDIV 72 on MoE workloads. Source: @alanoo, 2026-10-14 See Glossary#HBM clock win.
  • Is the unlocked memory reliable? Contested No failure statistics exist yet; validate each card with a full memtest. The views, in the order posted:
    • It is lower-binned memory NVIDIA fused off for a reason, and software cannot fix that. Source: @_____josh_____, 2026-10-05
    • It runs fine and, apart from speed, no different from a 5090. Source: @jjb01957, 2026-10-05
    • Every card runs at NDIV 68 at least, better than typical binned memory. Source: @wakeupmbrc1, 2026-10-05
  • ECC does not change usable memory; HBM2e carries it natively. Source: @alanoo, 2026-10-05
  • Cards with HBM errors. Reported A card with a few bad HBM addresses can be kept in service. Zombie's card threw about 5k single-bit and 2-8 bit errors per 5-minute memtest_vulkan run, always at the same addresses (around 30 GB and 61 GB). He mapped those addresses to physical memory and had the driver mark the blocks bad at boot: only four 64 KB blocks were bad, which cost 8 MB because each block is held with 2 MB pages (63.06 GB to 63.05 GB). memtest_vulkan and gpu-burn then passed with ECC off. Source: @zombielurker, 2026-10-05
    Source: @zombielurker, 2026-10-05 The marking has to run at every boot; reala had the same script written for his card. Source: @reala7096, 2026-10-05 This is what the A100 does by itself, and it stops working when the errors span several GB. Source: @cute_sc2, 2026-10-05
    Source: @cute_sc2, 2026-10-05 See Troubleshooting.
  • 80 or 96 GB? Contested Not achieved. Screenshots of 8 GB cards at 80 or 96 GB circulated in October 2026 with nothing behind them. The positions, in the order posted:
    • A read-only fuse study puts the ceiling at 80 GiB (reviving FBP 1 and 4) and calls 96 GiB wrong because FBP 6 and 11 are dead silicon; its 80 GiB recipe is derived, incomplete and untested. Source: repo github.com/ahnguyen17/ga100-fuse-re by ahnguyen17 on GitHub, posted by @exile_1ck, 2026-10-07
    • In theory an 8 GB card could go to 96 GB if an unlock ever shipped. Source: @wakeupmbrc1, 2026-10-09
    • Without a signed VBIOS nobody sees how it would be possible. Source: @globalapathy, 2026-10-11
    • In theory 96 GB on some cards and 80 GB on most. Source: @djpandaman, 2026-10-12
    • The maximum confirmed on a production 8 GB card is 64 GB. Source: @djpandaman, 2026-10-12

Limits

  • No more SMs, no RIR path. Every RIR entry except the last reads 0xFFFFFFFF, so there is no software path past 74 SMs and 64 GB without NVIDIA-signed falcon code. Source: @wakeupmbrc1, 2026-10-07 Most cards have the full 128 SMs physically present. Source: @replacedriver47, 2026-10-07 Even with HS and debug mode, floorsweep values cannot change because of the DISABLE_SW_OVERRIDE fuse. Source: @cute_sc2, 2026-10-13 The 74 to 80 step that works on the 10 GB card does not work here: the extra TPCs sit behind OPT_TPC_DISABLE, which is burned to 1. Source: @djpandaman, 2026-10-10 The 8 GB card is "completely unfeasible on RIR paths". Source: @ob88594, 2026-10-27 Froggo checked one of his 8 GB cards and found no free RIRs; Humvee55: among Ampere-era NVIDIA parts, only the 10 GB card will take the RIR path. Source: @froggao, 2026-10-22
    Source: @scallion_9883, 2026-10-22 mrpandagod has found no good answer to why NVIDIA would blow 15 records and keep 1 partial. Source: @djpandaman, 2026-10-26
  • Is anything more possible? Contested In the order posted:
    • Mountains keeps hitting locks that look wired into the silicon. Source: @mountains1605, 2026-10-20
    • matstatman thinks everything software-unlockable has been found and the fuses cut off the rest. Source: @matstatman, 2026-10-27
    • replacedriver47: fuses are read and propagated by software, so it is unlockable in theory if the security mechanisms can be bypassed. Source: @replacedriver47, 2026-10-27
  • PCIe Gen3. Blocked. The fuse register is locked, which blocks the Gen3 retrain; the RIR tool is not for 8 GB. Source: @wakeupmbrc1, 2026-10-25 OPT_DISABLE_GEN3_SPEED reads 1 on every card read so far, and forcing 8 GT/s on such a card drops it off the bus until a full power cycle. Source: repo github.com/PixelML/club-170hx by PixelML on GitHub, posted by @c133, 2026-10-20
    • Contested Can the last RIR record give single-fuse Gen3? mrpandagod could not enable Gen3 without several fuses and will not spend his last record to test. Source: @djpandaman, 2026-10-10 Rickcal believes only some cards can do single-fuse Gen3. Source: @rrickk420, 2026-10-10
    • Asked on 2026-10-26 when an 8 GB Gen3 unlock would come out, _L_ answered that the 10 GB card's RIR rows are not blown, so it will come only when people find another way to unlock the 8 GB card, and for now there is no clear way. Source: @hezz1891, 2026-10-26
      Source: @lia_oc, 2026-10-26
      Source: @lia_oc, 2026-10-26
      Source: @lia_oc, 2026-10-26
    • A claim of Gen3 on an 8 GB card, with a release promised for 2026-12-09, came with no proof. Source: @rrickk420, 2026-10-09
  • PCIe width. The card links at x4 until the missing capacitors are fitted. Any x16 link, at any generation, needs the cap mod; x4 is the maximum without it. Source: @djpandaman, 2026-10-17 The mod is "borderline mandatory" for TP=2. Source: @cibernox, 2026-10-13 See PCIe capacitor mod. Paid services: GMZombie007 offered the mod through an eBay listing at about USD 50 plus shipping and says others charge 50-90; Source: @gmzombie, 2026-10-04 Tokukarin offers it too; Source: @tokukarin, 2026-10-04 Ikyo knows someone who last quoted USD 100 per card; Source: @ikyo, 2026-10-04 a shop in BC (Canada) charges CAD 120 per card. Source: @68x0, 2026-10-06 Alifond sells cards with the capacitor mod already done, about USD 2.6k DDP in early October. Source: @kellertreppe123, 2026-10-04
  • NVLink (NVLink). No path on the 8 GB card. Source: @n2dcrypt, 2026-10-06 The same NVLink and power components are missing on all boards, Source: @globalapathy, 2026-10-24 and 8 GB NVLink has not been unlocked. Source: @ob88594, 2026-10-24
  • Open research (none of it usable yet): reading HBM site A's IEEE 1500 DEVICE_ID through the SEC2 Booter path, with disabled sites B and E next; Source: @junsulee119, 2026-10-24 using the last RIR record to change the device ID to A800, which would not change PCIe speed. Source: @djpandaman, 2026-10-10 Theory Using the 10 GB card as a test bed: Humvee55 says the 10 GB card can run debug-signed firmware blobs and that the debug key is known; asked by Zagitta whether that could be used to find vulnerabilities that also apply to the 8 GB card, he answered yes. Nobody has reported doing it. Source: @scallion_9883, 2026-10-17
    Source: @scallion_9883, 2026-10-17
    Source: @zagitta, 2026-10-17
    Source: @scallion_9883, 2026-10-17
  • Warning Unreleased "high power mode". matstatman found a register that enables a high power mode, also on 8 GB cards, does not know what it does and will not release it. Do not chase full-power modes on cards whose defective-marked stacks may run hot. Source: @matstatman, 2026-10-20

Best recipes

Full list with numbers and filters: All recipes. Engines and how recipes are written: Recipes. Recipe pages for this card include GLM 5.3 Flash on 4x 8 GB, DeepSeek V4.1 Flash on 4x 8 GB (Morrowmake), DeepSeek V4.1 Flash on 4x 8 GB (GNmac), GLM 5.3 Flash on 2x 8 GB (ExLlamaV3 TP2) and GLM 5.3 Flash on 3x 8 GB. Numbers below are as posted; check the recipe page for engine, quant, context and concurrency.

  • 1 card (64 GB). Qwen3.8-27B W4A16 from a published Reddit recipe: about 170 tok/s decode reproduced; Source: @kellertreppe123, 2026-10-05 another owner reached about 3.7k tok/s prefill at about 100 tok/s decode. Source: @chonsworth, 2026-10-05 The current go-to single-card model is Qwen 3.8 Flash Next with PLE patches; the recommended recipe is "Qwen3.8-Flash-Next 3bpw MTP on 1x CMP 170HX SSD PLE AIO" (iIIusi0n). Source: @mountains1605, 2026-10-27
  • 2 cards (128 GB). Qwen 3.8 Flash Next: about 100-110 tok/s on 2 cards. Source: @68x0, 2026-10-09 Proven Plean's setup runs Qwen3.8 Flash Next on two 64 GB cards with vLLM pipeline parallel, MTP speculative decoding and the full BF16 PLE table offloaded to NVMe, with up to 6 concurrent requests at a 256K context; P2P was off on his board. Write-up: bozocentral.com/2x-cmp170hx-qwen3-flash-next. Source: @plean., 2026-10-07
    Source: @plean., 2026-10-07
    Source: @plean., 2026-10-07 GalyGames reproduced it almost identically on Proxmox. Source: @galygious, 2026-10-08 GLM-5.3-Flash EXL3 in TP2 with vision, on two x16-modded cards: decode up to about 28% faster than the layer split, about 120 tok/s and 134-147 tok/s on code edits and JSON, two agents at about 320K context each with idle sessions' KV parked in system RAM; the cards were limited to about 170 W with a modest memory overclock. Source: repo github.com/alexvnesta/glm53-flash-cmp170hx-tp by alexvnesta on GitHub, posted by @nestaa51, 2026-10-12
    Source: @nestaa51, 2026-10-14 Recipe page: GLM 5.3 Flash on 2x 8 GB (ExLlamaV3 TP2).
  • 3 cards (192 GB). Proven clee's Qwen3.8-Flash-Next setup runs on three unmodded (x4) cards in PP=3 with the PLE table offloaded to NVMe, and should work on two cards at PP=2 with less KV cache. Source: repo github.com/clee/qwen3.8-flash-next-3x170hx by clee on GitHub, posted by @c133, 2026-10-04
    Source: @c133, 2026-10-04 68x ran it on three unlocked 8 GB cards at 52-60 tok/s on a single-user agentic workload. Source: @68x0, 2026-10-08 A later update keeps the KV cache on NVMe across vLLM restarts, so a long agent session resumes quickly; with it, 2 and 3 cards are hard to tell apart, Source: @c133, 2026-10-11
    Source: @c133, 2026-10-11 and 68x sees 100+ tok/s decode with MTP on 2 cards. Source: @68x0, 2026-10-11 GLM-5.3-Flash W4A16 (about 4.3 bpw, 163 GiB) runs in PP3 with Morrowmake's recipe and 8-bit KV. Source: @shirogeek, 2026-10-19 An EXL3 GLM build scaled to 3 cards reached 60 tok/s in TP with full context, but the third card mostly buys context. Source: @wingrimez_40467, 2026-10-20
  • 4 cards (256 GB). Morrowmake's GLM 5.3 Flash recipe is the community daily driver: about 800 tok/s aggregate across agents, Source: @cibernox, 2026-10-19 130-160 tok/s single stream, Source: @mountains1605, 2026-10-20 317 tok/s at bs=1 on code and 164 on prose in TP4. Source: @turbine, 2026-10-27 For DeepSeek V4.1 Flash 1017, Morrowmake's recipe is rated above GLM Flash by Mountains after two days of agent work; Source: @mountains1605, 2026-10-26 greencandle's build streams the 189 GiB n-gram tables from NVMe. Source: @greencandle9753, 2026-10-21 The top DeepSeek decode numbers need the x16 mod. Source: @greencandle9753, 2026-10-22
  • Rule of thumb. Moving one card from x4 to x16 gave about +3% decode but about 4x prefill. Source: @wakeupmbrc1, 2026-10-07 With P2P working, PP still beat TP for very long-context prefill on one 4-card rig. Source: @mountains1605, 2026-10-15

Power, cooling and tuning

Details: Cooling and power.

  • Power input. One EPS 8-pin (CPU 8-pin), not PCIe. If you use the bundled 2x PCIe to EPS adapter, both PCIe inputs carry current. Source: @civiloid, 2026-10-15
  • Warning One cable into both adapter inputs. Feeding both inputs of the EPS adapter from one PCIe cable and its pigtail has burned hardware. Run a separate PSU cable to each adapter input, or use a CPU/EPS cable straight into the card. Source: @c133, 2026-10-19
  • Airflow. The card is passive and needs forced air even at idle; it falls off the bus at 95 C. Source: @analyticeth, 2026-10-07
  • Power cap. Most owners run 140-200 W. On GLM-5.3-Flash TP4 one club measured 412.7 tok/s single user at 140 W versus 418.6 at 165 W, with the best tokens per watt at 110 W; a driver reload resets the cap to the VBIOS default of 250 W, so reapply it at boot. Source: repo github.com/PixelML/club-170hx by PixelML on GitHub, posted by @c133, 2026-10-20
  • Undervolt. Shifting the V/F curve cuts power by up to 30-35% at the same clock; it is per card, and instability shows up as Xid 31. Source: @wakeupmbrc1, 2026-10-12 One water-cooled 4-card setup runs 170tune at --ndiv 66 --offset 270 --clk 1410 --timings "REFRESH 24" at about 202 W. Source: @rh3dai, 2026-10-08 RH-3D keeps a YouTube tuning series for this card in the undervolting guide channel: #011 (more compute and bandwidth at less power) and #012 (follow-up after the ECC merge); the video content is not transcribed here. Source: @rh3dai, 2026-10-04
    Source: @rh3dai, 2026-10-07
  • Idle. With the idle p-state patches, three cards idle at 23, 25 and 26 W. Source: @robbbbbb7973, 2026-10-10
  • 300 W. The 300 W VBIOS (92.00.6D.00.0A) exists for the 8 GB card only. Source: @zagitta, 2026-10-12

Known issues

Details: Troubleshooting, Driver and unlock failures, Instability under load.

  • 170tune preflight fails with "FBPA privilege masks are closed". One card out of 36 unlocked fine but refused 170tune with every unlocker and 170tune fork tried; the owner runs it on plain v0.5 without tuning. Source: @rh3dai, 2026-10-07 Another owner sees the same failure on all his cards and suspects a version mismatch between the unlocker and 170tune. Source: @drew_2, 2026-10-12
  • GSP init fails on every boot after Xid 119 and Xid 154. Reported on a card in a USB4 eGPU dock, persisting across hosts and power-off; unresolved. Source: @mistyashhole, 2026-10-10
  • Hangs under compute in a passthrough VM. Reported On Debian 13 in a VM with PCI passthrough (nvidia-open 615.71.09, cmpunlocker 2d10f89), the unlocked card showed 64 GB and passed verify.sh, but any compute job hung, nvidia-smi stopped answering and the VM could not reboot cleanly. The fix was to build cmpunlocker without bar1-resize-unlock.patch (remove the bar1_resize entry from common/constants.yaml and the patch from PATCH_ORDER in driver/build.sh); the hangs stopped and all 64 GB stayed. The same post fixes a Debian 13 build error (stdarg.h: No such file or directory) by setting KSRC=/lib/modules/${KVER}/source and KSOUT=/lib/modules/${KVER}/build in driver/build.sh. Source: @vipic, 2026-10-18 It had worked two days earlier, before a bootloader repair, a kernel update and a reinstall. Source: @vipic, 2026-10-18
  • Whole rig loses power under heavy prefill. Four cards on one PLX board with two 750 W PSUs all dropped at once under big prompt-processing jobs; Source: @replacedriver47, 2026-10-05 nine cards on three 750 W PSUs at 160 W showed the same about once a day. Source: @reala7096, 2026-10-05
  • Warning Cards that fail to unlock. The reported overall failure rate for bought cards is about 20%. Source: @civiloid, 2026-10-13 Known failure modes: HBM memory errors, GSP that cannot initialise, and engineering-sample boards. Source: @ob88594, 2026-10-13 Cheap "8 GB" listings in China next to "64 GB guaranteed" ones are often cards with serious memory failures. Source: @replacedriver47, 2026-10-13

Buying

Details: Buying.

  • Ailfond (also written Alifond; an Alibaba dealer). Quotes for the 8 GB card climbed through October: USD 2.4k on 10-04, Source: @cute_sc2, 2026-10-04 then 2,299-2,599, Source: @lenxtroz, 2026-10-04 up USD 300 per card the same evening; it cancelled one member's earlier order after the increase. Source: @busulle, 2026-10-04
    Source: @busulle, 2026-10-05 The official price was USD 2,699 on 10-07, Source: @cibernox, 2026-10-07 3,100 on 10-14, Source: @voidgiraffe, 2026-10-14 its eBay listing still at 3k on 10-16 when direct quotes went higher, Source: @_arcanum_, 2026-10-16 and 3,333 on 10-21. Source: @kellertreppe123, 2026-10-21 One member got a refund through Alibaba after one of two cards had bad HBM (it passed a basic Vulkan test 9 times out of 10 but failed most other tests). Source: @boz._., 2026-10-23
  • Other sellers and prices. tony (a seller on the Discord) reported China prices at 18,000-19,000 RMB on 2026-10-13. Source: @tony_smartecom, 2026-10-13 A seller in Tampa listed 18 cards on Facebook asking about USD 100k for the lot (2026-10-19). Source: @ghostinthedatacenter_87281, 2026-10-19
    Source: @con3po7016, 2026-10-19 In the EU one member found only an Austrian company, at about 2,800 EUR. Source: @busulle, 2026-10-04
  • Test before paying: if the card is local, bring a bootable Linux USB and run a test unlock first. Source: @dottoreargus, 2026-10-11 A seller who refuses to test has a reason. Source: @ob88594, 2026-10-12
  • Check the device ID, VBIOS and board number for the 32 GB engineering-sample boards: Which card do I have#Cards that are not a normal 170HX.
  • Reported prices (USD unless noted, per card): about 550 for one owner's first four cards, bought before the October rush; Source: @gnasherrr, 2026-10-14 an eBay sale at 1,900 on 2026-10-01; Source: @djpandaman, 2026-10-12 3,000-3,500 by 2026-10-13; Source: @lenxtroz, 2026-10-13 in China ¥18,500 regular and ¥24,000 in bulk lots on 2026-10-22; Source: @ob88594, 2026-10-22 3,300-3,600 delivered with shipping and taxes on 2026-10-25, when Alifond's cheapest listing said 2.6k (Miséricorde: 2.6k "is not real for 8g"). Source: @kellertreppe123, 2026-10-25
    Source: @wakeupmbrc1, 2026-10-25

See also

10 GB card · Variant comparison · CMP 170HX · Unlocks · Platforms · Glossary