CMP Wiki - User contributions [en]

Flashing the 300 W VBIOS

2026-10-31T21:42:29Z

ImportBot: Import: flashing the factory 300 W VBIOS 92.00.6D.00.0A onto 8 GB cards, the procedure proven on eight cards, results and hashrate numbers; @c133, @shirogeek, @derick2k, @phoenixone7, @wakeupmbrc1, @con3po7016, @cute_sc2, @mrpec, @unmotivatedgene, @xanthefin; repos polyuij42-del/cmp170hx-vbios-flash and Consensus-Protocol/cmp170hx; lab notes

Most 8 GB cards ship with VBIOS 92.00.67.00.01, the 250 W image. On it the driver reports a GPC and memory VF-offset
range of [0 .. +0], so no undervolt can be applied, whatever a tool says it set. The factory 300 W image
92.00.6D.00.0A, which NVIDIA shipped on the same board part number (900-11001-0108-000), exposes an offset range of
[-1000 .. +1000], boots the HBM at 1728 MHz instead of 1458 MHz, raises the SM ceiling from 1410 to 1695 MHz, and
keeps a 250 W default cap (300 W is the maximum it allows). This page is the flash procedure as run on eight cards in
one night, with the numbers before and after. It does not touch the memory or compute unlock, which stays in the
driver; see [[Driver unlock]].

The 10 GB card has no 300 W image (its only VBIOS is 92.00.66.00.02); this page is for 8 GB cards. See
[[VBIOS and firmware]] for the full image inventory.

== At a glance ==
What each image gives the card:
{| class="wikitable"
! !! 250 W image (92.00.67.00.01) !! 300 W image (92.00.6D.00.0A)
|-
| Core and memory VF-offset range || 0 .. 0 (no undervolt) || -1000 .. +1000
|-
| HBM clock || 1458 MHz || 1728 MHz
|-
| SM clock ceiling || 1410 MHz || 1695 MHz
|-
| Power cap, default / maximum || 250 / 250 W || 250 / 300 W
|}
What it did on the lab's eight 8 GB cards, with the caps the thermal governor allowed (230 to 250 W) and the same
airflow. The two groups of rows were measured on different days' air (inlet 22 to 23 C, then 17 to 18 C), so compare
within a group:
{| class="wikitable"
! Setup !! Miner total, 8 cards !! Inference (same engine, same benchmark, against offset 0)
|-
| 250 W image || 1,455 TH/s || not measured on this image
|-
| 300 W image, offset 0 || 1,459 to 1,470 TH/s || baseline
|-
| 300 W image, offset 0 (cooler inlet) || 1,488 TH/s || baseline
|-
| 300 W image, GPC offset +160 (long-soak point) || 1,604 TH/s (+7.8 %) || GLM 5.3 Flash +3 to 4 %, DeepSeek V4.1 Flash +6 to 9 %
|-
| 300 W image, GPC offset +190 (top clean rung) || 1,625 TH/s (+9.2 %) || within 1 to 2 % of +160
|}
The flash on its own changed nothing measurable on the miner; the faster HBM matters for inference, the open undervolt
range for both. Same watts, same temperatures throughout: the offset buys clock at the voltage the card already uses.
Details and the failure at +220 further down.

{{Source|handle=darkmaniac7|date=2026-10-31|note=lab notes}}

== Why flash it ==
=== The 250 W image has no undervolt lever ===
<code><nowiki>nvml_oc -i N</nowiki></code> (the helper 170tune uses) reports <code><nowiki>allowed range : [0 .. +0] MHz</nowiki></code>
for both the GPC and the memory VF offset on every 92.00.67.00.01 card. An offset call can return success and the
driver still drops it; only a readback proves it applied. On the same cards after the flash the range reads
[-1000 .. +1000].

{{Status|Proven}} {{Cards|8 GB}} 
{{Source|handle=mrpec|date=2026-08-01|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1533150703328039085}} 
{{Source|handle=unmotivatedgene|date=2026-08-23|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1541201873803943997}} 
{{Source|handle=darkmaniac7|date=2026-10-31|note=lab notes}}

=== Same board, same IDs ===
Both images carry device 10DE:20C2, subsystem 10DE:1585 and board ID 0x030A, and both have been read off cards with
board part number 900-11001-0108-000 and die 20C2-105-A1. nvflash accepts the 300 W image on a 250 W card without any
override because the IDs match; it is a signed NVIDIA image, not a modified one.

{{Status|Reported}} {{Cards|8 GB}} 
{{Source|handle=con3po7016|date=2026-08-23|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1541194940997046322}} 
{{Source|handle=wakeupmbrc1|date=2026-08-30|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1543658140875235459}}

== Before you start ==
# '''An 8 GB card on 92.00.67.00.01.''' Read it with <code><nowiki>nvidia-smi --query-gpu=index,pci.bus_id,vbios_version --format=csv</nowiki></code>. A card already on 92.00.6D.00.0A has nothing to gain.
# '''nvflash 5.867 for Linux''', the <code><nowiki>x64/nvflash</nowiki></code> binary from the TechPowerUp download (the zip holds x86, x64, aarch64 and ppc64 builds; the Windows zip is a different download).
# '''The ROM''', TechPowerUp VBIOS database entry 268495 (listed there as "CMP 170HX 0 MB"; the size column is wrong). Verify it before it goes near a card: see below. A copy is attached to this page.
# '''A rollback ROM.''' Save one card's 92.00.67.00.01 image with <code><nowiki>nvflash -i N --save</nowiki></code> before you write anything. The static part of the image is identical across cards of the same version, so one dump serves as the rollback for all of them.
# '''A way to power the machine off and on''' that does not depend on the GPUs: a BMC, or someone at the button. The procedure needs two cold cycles, and a wedged flash controller only clears on a cold cycle.
# '''The driver unloaded, or never loaded.''' nvflash refuses to write with the NVIDIA kernel module present. The method below boots without it, which also avoids the unbind hang described further down.

== Verify the ROM ==
The TechPowerUp file matched these values exactly:
{| class="wikitable"
! Field !! Value
|-
| Version || 92.00.6D.00.0A
|-
| Build / modification date || 06/16/21 / 04/07/22
|-
| Size || 1,044,480 bytes
|-
| Device / subsystem / board ID || 0x20C2 / 0x1585 / 0x030A
|-
| MD5 || a58aae86e72b13d50603c15653350664
|-
| SHA1 || efad37d514bb94ac345719a0c56d9cd147cddfb7
|-
| SHA256 || 789e8f8d4c70dc9eb114c9fdcef6ed2d00aedf15a1eca522519de02042818723
|}
Two checks that do not depend on a hash:
* <code><nowiki>nvflash --version 300w.rom</nowiki></code> reads the header from the file only (it does not touch a card) and must print the version, device, subsystem and board IDs above, and <code><nowiki>License Placeholder : Present</nowiki></code>.
* <code><nowiki>python3 check_rom.py 300w.rom --expect 300W</nowiki></code> (attached) checks the structural markers: the NVGI header, the 300 W power bytes <code><nowiki>E0 93 04</nowiki></code> at 0x46045, the strap tier byte 0x44 at 0x41F53 (0x66 there means a forged "64 GB" ROM that bricks the card at boot), an all-zero license region at 0xFE504, and the dual-bank mirror. The same script recognises the 250 W image (<code><nowiki>--expect 250W</nowiki></code>) for checking your rollback dump.

{{Status|Reported}} {{Cards|8 GB}} 
{{Source|repo=https://github.com/polyuij42-del/cmp170hx-vbios-flash}} 
{{Source|repo=https://github.com/Consensus-Protocol/cmp170hx}}

== The procedure (driverless boot) ==
Proven on eight cards in two rounds, 2026-10-31, on a bare-metal Ubuntu box with the cmpunlocker driver build 615.71.09,
BMC power control and the tooling attached below. Every write took about 10 seconds. Read the two rules first:

* '''One nvflash operation per card per boot.''' After a power-on, the first nvflash command that touches a card's flash controller (<code><nowiki>--check</nowiki></code>, <code><nowiki>--save</nowiki></code> or a write) works; a second one on the same card fails with <code><nowiki>Falcon In HALT or STOP state</nowiki></code> or <code><nowiki>Detecting GPU failed</nowiki></code> and nothing is written. So the rollback save comes from a card you are not writing in that boot (or from an earlier boot), and the write is the first and only thing you do to each target card. A PCIe remove and rescan of one device (<code><nowiki>echo 1 > /sys/bus/pci/devices/0000:XX:00.0/remove; echo 1 > /sys/bus/pci/rescan</nowiki></code>) re-opened the window once in the lab; do not count on it.
* '''nvflash 5.867 ignores <code><nowiki>-y</nowiki></code> and refuses piped input.''' The confirm prompt needs a real terminal. It prints the card's current and replacement version strings before the prompt, and the PCI bus only in its Results table after the operation, so the attached controller confirms on the version strings (current must be 92.00.67.00.01, replacement 92.00.6D.00.0A) and checks the bus afterwards. nvflash's <code><nowiki>-i</nowiki></code> index follows PCI bus order, the same order <code><nowiki>nvidia-smi</nowiki></code> uses with <code><nowiki>CUDA_DEVICE_ORDER=PCI_BUS_ID</nowiki></code>; the Results table confirmed <code><nowiki>-i 7</nowiki></code> = bus C2 on the lab box.

Steps:
# Stop everything that holds the GPUs (engines, miners), until <code><nowiki>lsof /dev/nvidia*</nowiki></code> shows nothing. Record every card's VBIOS version.
# Keep the driver out of the next boot: <code><nowiki>/etc/modprobe.d/zz-flash-window.conf</nowiki></code> with <code><nowiki>install nvidia /bin/false</nowiki></code> (and the same for nvidia_modeset, nvidia_drm, nvidia_uvm). Mask or disable the units that would start GPU work at boot (docker, miners, any model loader). Note what you changed.
# Cold cycle: power off, 30 seconds dark, power on. Confirm <code><nowiki>lsmod | grep nvidia</nowiki></code> is empty and that the cards are enumerated with no driver bound.
# Save the rollback ROM from a card you will not write this boot: <code><nowiki>nvflash -i N --save backup.rom</nowiki></code>, then <code><nowiki>check_rom.py backup.rom --expect 250W</nowiki></code>.
# Write each target card once: <code><nowiki>nvflash -i N 300w.rom</nowiki></code>, answer <code><nowiki>y</nowiki></code> at the prompt (or let the attached controller do it). Success looks like a progress bar to 100 %, two verification reads, and <code><nowiki>A reboot is required for the update to take effect.</nowiki></code> with exit code 0. Anything else: do not retry that card this boot.
# Remove the blacklist, restore the units, cold cycle again.
# Verify: <code><nowiki>nvidia-smi --query-gpu=index,vbios_version,memory.total,clocks.max.memory,power.default_limit,power.max_limit --format=csv</nowiki></code> should show 92.00.6D.00.0A, your unlocked memory size, 1728 MHz, 250 W default and 300 W maximum; <code><nowiki>nvml_oc -i N</nowiki></code> should show the [-1000 .. +1000] range.

The attached <code><nowiki>window.sh</nowiki></code> runs those phases (<code><nowiki>check</nowiki></code>, <code><nowiki>prep</nowiki></code>, <code><nowiki>flash</nowiki></code>, <code><nowiki>restore</nowiki></code>, <code><nowiki>verify</nowiki></code>) with the lab box's unit names and bus map; edit those before using it elsewhere.

{{Status|Proven}} {{Cards|8 GB}} 
{{Source|handle=darkmaniac7|date=2026-10-31|note=lab notes}} 
{{Source|repo=https://github.com/polyuij42-del/cmp170hx-vbios-flash}}

=== Why not unbind the driver instead ===
The repository above spent eighteen script versions on the unbind route. With any process still holding
<code><nowiki>/dev/nvidia*</nowiki></code>, <code><nowiki>echo ... > /sys/bus/pci/drivers/nvidia/unbind</nowiki></code> hangs in the driver's remove path and never
returns; on one of its two cards it hung even with zero handles open, and a <code><nowiki>reboot</nowiki></code> issued in that state stalled the
machine until someone cut the power. Booting with the modules blacklisted sidesteps all of it.

{{Status|Warning}} {{Cards|8 GB}} 
{{Source|repo=https://github.com/polyuij42-del/cmp170hx-vbios-flash}}

=== Others who flashed it with nvflash ===
Several owners did the same flash with stock nvflash before the lab did, on Linux and on Windows; none reported a
brick from it. The bricks reported on the server came from fuse burns, SPI strap edits and A100 cross-flashes, not from
this image.

{{Status|Reported}} {{Cards|8 GB}} 
{{Source|handle=c133|date=2026-08-23|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1541187172588326962}} 
{{Source|handle=c133|date=2026-08-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1542649519739769003}} 
{{Source|handle=shirogeek|date=2026-09-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1546191972392501369}} 
{{Source|handle=derick2k|date=2026-09-06|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1546163237186441286}} 
{{Source|handle=phoenixone7|date=2026-09-16|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1549930400707514490}} 
{{Source|handle=wakeupmbrc1|date=2026-08-30|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1543658182298173581}}

== Results on eight cards ==
Two of the eight (bus 41 and C1) have FBPA0 fused off (one dead HBM stack each). Both took the image and initialised
cleanly at 1728 MHz; the driver log after the flash matched the log before it line for line in shape (the unlock's
privilege-mask loop prints 54 "Booter failed" lines per card on every boot; that is normal, not damage).

{| class="wikitable"
! Card (bus) !! VBIOS after !! Memory !! Max mem clock !! Default / max cap !! Offset range !! Note
|-
| 0 (01) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 ||
|-
| 1 (22) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 ||
|-
| 2 (41) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 || FBPA0 fused
|-
| 3 (61) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 ||
|-
| 4 (81) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 ||
|-
| 5 (A1) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 ||
|-
| 6 (C1) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 || FBPA0 fused
|-
| 7 (C2) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 || first attempt aborted by the controller, window re-opened by a PCIe rescan, second write fine
|}
Zero Xids, zero ECC errors, zero RmInitAdapter failures across four cold cycles.

{{Status|Proven}} {{Cards|8 GB}} 
{{Source|handle=darkmaniac7|date=2026-10-31|note=lab notes}}

== What it changed ==
The load is a proof-of-work miner (pearlhash, OneZeroMiner) on all eight cards with the fan wall at 15 % and caps set
per card by a thermal governor (230 to 250 W). The rejected shares below were all "Stale share" (a share submitted after
the pool changed the job: timing, not a wrong answer); there were no invalid shares.

{| class="wikitable"
! State !! Total hashrate !! Core clock range !! Temps !! Notes
|-
| 250 W image, offset 0 || 1,455 TH/s || 1215 to 1290 MHz || 70 to 79 C || baseline, same caps
|-
| 300 W image, offset 0 || 1,459 to 1,470 TH/s || 1215 to 1290 MHz || 70 to 79 C || HBM 1728 MHz cost nothing on a compute load
|-
| 300 W image, GPC offset +100 || 1,525 TH/s || 1275 to 1365 MHz || unchanged || 20 min soak, 0 Xid
|-
| 300 W image, GPC offset +130 || 1,549 TH/s || 1290 to 1380 MHz || unchanged || 20 min soak, 0 Xid
|-
| 300 W image, GPC offset +160 || 1,564 TH/s || 1335 to 1410 MHz || unchanged || 20 min soak, 0 Xid
|-
| 300 W image, GPC offset +190 || 1,579 TH/s || 1335 to 1425 MHz || unchanged || 20 min soak, 0 Xid
|-
| 300 W image, GPC offset +220, six cards || 1,598 TH/s || 1350 to 1440 MHz || unchanged || 20 min soak, 0 Xid; two cards still parked by the false alarms
|-
| 300 W image, GPC offset +220, all eight || 1,631 TH/s || 1350 to 1440 MHz || unchanged || 09:57, after the two parked cards took +160/+190/+220 clean; +11.8 % over the morning baseline. Not a safe point: see the warning below
|}
Power draw stayed at the caps the whole time: the offset lets the core hold a higher clock at the same watts, so the
gain comes with no extra heat. Two cards were held back early by a stale share each (a rule that counted any rejected
share; it now counts only invalid ones); re-run from +160, both took every rung.

=== The miner does not qualify an offset for inference ===
{{Status|Warning}} {{Cards|8 GB}} 
One hour after all eight reached +220 with the miner clean, the lab ran its inference benchmark against GLM 5.3 Flash
(TP4) on cards 0 to 3. One minute in, card 0 (the hottest slot, 77 to 79 C under the miner) began flooding
<code><nowiki>Xid 48</nowiki></code> (uncorrectable ECC error in GPC3 GCC) and <code><nowiki>Xid 172</nowiki></code>
(uncorrectable SRAM error in GPC 3), 97,000 lines in five minutes, and the engine died. That is the same pair the
Discord reports for a too-deep offset. At the same time card 5, which only ever ran the miner, was found in "GPU
requires reset" with no Xid at all, about two hours into +220. Lowering the offset does not clear either state: card 0
recovered with <code><nowiki>nvidia-smi -r</nowiki></code>, card 5 needed a cold cycle. What this means:
* A 20-minute miner soak proves nothing about inference, and not much about a two-hour miner run either. Qualify each
card against the engine that will serve on it, with a benchmark as the workload rung, and soak for hours, not minutes.
* Hot-slot cards have the least margin.
* +220 is not a safe point on this box. The lab reverted every card to 0 and re-laddered with inference gating (next
section).

{{Source|handle=darkmaniac7|date=2026-10-31|note=lab notes}} 
{{Source|handle=ichundes|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1557350219111342183}}

=== Inference-gated ladder (second run) ===
{{Status|Reported}} {{Cards|8 GB}} 
Same eight cards after a cold cycle, inlet 17 to 18 C. Both groups of four ran in parallel, each serving its own engine
(GLM 5.3 Flash on cards 0 to 3, DeepSeek V4.1 Flash on cards 4 to 7). Each rung: a two-minute benchmark against that
group's engine (structured and code prompts, 1 and 4 streams, 512 tokens, any failed request is a fault), then one hour
under the miner with Xids attributed to the card the kernel names, then the same benchmark again. Rungs +100, +130,
+160 and +190: every card passed every rung, 0 Xid, 0 invalid shares, 0 failed requests. The lab then set all eight to
+160, one rung below the top clean rung, for a long soak; that is the point to start from, not +190.

{| class="wikitable"
! GPC offset !! Miner total (8 cards) !! Notes
|-
| 0 (stock) || 1,488 TH/s || same caps (230 to 250 W by temperature), same airflow
|-
| +130 || 1,578 TH/s ||
|-
| +160 || 1,604 TH/s || long-soak point
|-
| +190 || 1,625 TH/s || top clean rung; +220 faulted in the first run
|}

What it does for inference, measured as an A/B on the same engines with the same benchmark, stock against +160, at
512 and 1024 tokens (decode per stream at 1 stream / aggregate at 4 streams, tok/s):
{| class="wikitable"
! Prompt, tokens !! GLM stock !! GLM +160 !! Change !! DeepSeek stock !! DeepSeek +160 !! Change
|-
| structured, 512 || 260.9 / 510.7 || 270.2 / 524.4 || +3.6 % / +2.7 % || 141.4 / 227.4 || 150.9 / 247.7 || +6.7 % / +8.9 %
|-
| code, 512 || 243.4 / 499.2 || 252.2 / 512.3 || +3.6 % / +2.6 % || 189.8 / 278.3 || 201.8 / 295.1 || +6.3 % / +6.0 %
|-
| prose, 512 || 154.1 / 368.6 || 159.9 / 379.1 || +3.8 % / +2.8 % || 131.4 / 241.1 || 143.2 / 246.0 || +9.0 % / +2.0 %
|-
| structured, 1024 || 256.9 / 539.4 || 266.6 / 554.7 || +3.8 % / +2.8 % || 152.9 / 247.5 || 164.2 / 265.7 || +7.4 % / +7.4 %
|-
| code, 1024 || 274.6 / 548.7 || 284.5 / 564.8 || +3.6 % / +2.9 % || 176.7 / 297.8 || 190.3 / 337.5 || +7.7 % / +13.3 %
|-
| prose, 1024 || 150.9 / 357.5 || 156.6 / 368.2 || +3.8 % / +3.0 % || 135.8 / 234.8 || 145.6 / 251.9 || +7.2 % / +7.3 %
|}
GLM 5.3 Flash gains about 3 to 4 %; DeepSeek V4.1 Flash, which spends more of its time in compute, gains about 6 to 9 %.
Both at the same power cap and the same temperatures. One A/B run, stock first; every cell moved the same way.

{{Source|handle=darkmaniac7|date=2026-10-31|note=lab notes}}

{{Status|Proven}} {{Cards|8 GB}} 
{{Source|handle=darkmaniac7|date=2026-10-31|note=lab notes}}

== Risks and what the community saw ==
* {{Status|Warning}} One owner advised against the 300 W image because a photo of a burned 170HX had been posted earlier and the board lacks some power-delivery parts of the full layout. The photo is not in the exported history and no post ties a burned card to this image. The image's own default is 250 W; nothing on the lab box sets 300 W, and the undervolt reduces current at a given cap rather than raising it. Keep your cap at or below 250 W until you have a reason and the cooling to go higher. {{Source|handle=xanthefin|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561336153515364444}}
* {{Status|Contested}} HBM at 1728 MHz: one owner on the 300 W image with a 250 W limit passed GPU-burn with no errors but saw sporadic Vulkan memtest errors across the HBM dies; the eight lab cards (Hynix) ran clean. If a card misbehaves at 1728 MHz, 170tune can set the memory clock back down (not on FBPA0-fused cards, where the PLL tool must not write). {{Source|handle=cute_sc2|date=2026-08-08|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1535648815456198667}} {{Source|handle=darkmaniac7|date=2026-10-31|note=lab notes}}
* {{Status|Warning}} A failed flash is recoverable only with an SPI programmer with a 1.8 V adapter (the flash IC is 1.8 V; some "3.3 V" CH341A units put out 5 V, so a CH347 unit whose software selects the voltage is the safer buy). Power loss during the write and the wrong file are the two real ways to get there; both are yours to prevent. {{Source|repo=https://github.com/Consensus-Protocol/cmp170hx}}

== Rollback ==
The same procedure with your saved 92.00.67.00.01 dump as the image: one write per card in a driverless boot, then a
cold cycle. The lab keeps its dump with the rest of the evidence; any card's dump of the same version works for any
card of the same version.

== Files ==
* {{Download|file=CMP170HX_92.00.6D.00.0A.rom|compact=yes}} The 300 W image, byte-identical to TechPowerUp 268495 (hashes above).
* {{Download|file=Vbios_check_rom.py|compact=yes}} Structural ROM check (MIT, from polyuij42-del/cmp170hx-vbios-flash).
* {{Download|file=Vbios_flash_one.py|compact=yes}} The pty controller that answers nvflash's prompt only after it has echoed the expected versions, and checks the bus afterwards.
* {{Download|file=Vbios_window.sh.gz|compact=yes}} The lab's phase script (gzipped: the wiki refuses a shebang script under a plain extension) (check, prep, flash, restore, verify); unit names and bus map are the lab box's.

== Related ==
[[VBIOS and firmware]], [[Undervolting and power limits]], [[Driver unlock]], [[170tune]], [[Troubleshooting]].

{{ImportFooter}}
[[Category:Unlocks]]
[[Category:8 GB]]
[[Category:Cooling and power]]

CMP Wiki:Trusted uploaders

2026-10-31T21:36:25Z

ImportBot: Wording: site admins instead of a personal name

The '''trusted''' group may upload binaries, drivers, archives and scripts (sh, py, zip, gz, tgz, xz, run, deb, bin, rom)
in addition to the file types everyone may upload. Members: the site admins, and the tool authors they add once those have signed in.

Every file they upload carries a <code><nowiki>{{Download}}</nowiki></code> block on its file page: version, upstream
source link, and the sha256 and uploader read from the stored file. A hosted build that differs from its upstream release
shows a different hash.

Current members: [[Special:ListUsers/trusted]].

File:Heretic inplace.py

2026-10-31T21:36:15Z

ImportBot: Wording: lab notes / site admins instead of a personal name

'''heretic_inplace.py''' applies the pqhaz "heretic" FP8 patch to the <code>attn.wo_b</code> weights of the official
DeepSeek V4.1 Flash shards, in place, for engines that read attention weights straight from the official checkpoint.
Only the 38 <code>layers.N.attn.wo_b.weight</code> tensors change (same dtype F8_E4M3, same shape, same offsets); the
FP8 scales are untouched. Three commands: <code>apply</code>, <code>restore</code> and <code>status</code>. Python
standard library only.

{{Download|version=2026-10-29|source=[https://cmp.wiki/wiki/User:Darkmaniac7 lab notes (@darkmaniac7)]|expected_sha256=5c2e6a96b424ba5c6b2983bf06953704f0dd63e51c3beb5ef25e5a73cea44343|notes=Used by [[DeepSeek V4.1 Flash heretic on 4x 8 GB]].}}

== Usage ==
<pre>
heretic_inplace.py apply OFFICIAL_DIR PATCH.safetensors BACKUP.safetensors
heretic_inplace.py restore OFFICIAL_DIR PATCH.safetensors BACKUP.safetensors
heretic_inplace.py status OFFICIAL_DIR PATCH.safetensors BACKUP.safetensors
</pre>
* <code>OFFICIAL_DIR</code>: the official DeepSeek-V4.1-Flash-1017 checkpoint (with <code>model.safetensors.index.json</code>).
* <code>apply</code> first writes an exact byte backup of every original tensor (a safetensors file with the same names),
then overwrites, fsyncs and reads back. It refuses a shard that has more than one hard link, and refuses to run when
a tensor is already patched and there is no backup.
* <code>restore</code> writes the backup back; <code>status</code> counts tensors that are patched, stock (match the
backup) or neither. Both are safe to repeat: a tensor already in the wanted state is skipped.

== License ==
MIT (the file carries no license header).

{{Source|darkmaniac7|2026-10-29|note=lab notes}}

Template:Status

2026-10-31T21:36:13Z

ImportBot: Wording: lab notes / site admins instead of a personal name

<includeonly><span class="cmp-badge cmp-badge--{{#switch:{{lc:{{{1|}}}}}|proven=proven|reported=reported|theory=theory|contested=contested|warning=warning|#default=unset}}" title="{{#switch:{{lc:{{{1|}}}}}|proven=Proven: reproduced by a second person, or by the lab on its own hardware, with numbers|reported=Reported: one person's post with numbers or a clear result|theory=Theory: an idea nobody has tested yet|contested=Contested: people disagree, both sides are shown|warning=Warning: this damaged hardware or lost data|#default=Status not set}}">{{#switch:{{lc:{{{1|}}}}}|proven=Proven|reported=Reported|theory=Theory|contested=Contested|warning=Warning|#default={{{1|Unset}}}}}</includeonly><noinclude>
Status badge. Usage: <code><nowiki>{{Status|Reported}}</nowiki></code>. Values: Proven, Reported, Theory, Contested, Warning. See [[Status taxonomy]].

{{Status|Proven}} {{Status|Reported}} {{Status|Theory}} {{Status|Contested}} {{Status|Warning}}

The badge uses the shared classes <code>cmp-badge cmp-badge--<status></code> from <code>/shared/header.css</code>
(the design lane's file, loaded on every wiki page), so the wiki, the front door and the board show the same colours.
On recipes, platforms and unlocks nobody types Proven: those templates compute it from [[Template:Confirmation|confirmations]].
[[Category:Templates]]</noinclude>

Status taxonomy

2026-10-31T21:36:12Z

ImportBot: Wording: lab notes / site admins instead of a personal name

Every recipe, platform report and unlock carries one status badge, and any single fact on any page may carry one too
(<code><nowiki>{{Status|Theory}}</nowiki></code>). The badge tells a reader at a glance how far to trust it.

{| class="wikitable"
! Status !! Meaning
|-
| {{Status|Proven}} || Reproduced by a second person, or by the lab on its own hardware, with numbers.
|-
| {{Status|Reported}} || One person's post with numbers or a clear result.
|-
| {{Status|Theory}} || An idea nobody has tested. Theories feed the [[Board how-to|testing board]].
|-
| {{Status|Contested}} || People disagree. The page shows both sides, each with its source.
|-
| {{Status|Warning}} || Something that damaged hardware or lost data. Read before you try it.
|}

== How a page becomes Proven ==
Nobody sets Proven by hand. The forms only offer Reported, Theory, Contested and Warning.

# Someone posts a result: a recipe, platform report or unlock, with <code>tested_by</code> set to whoever ran it.
# Someone else runs it on their own card and presses '''Confirm on your own card''' in the page's infobox. That opens
#: [[Form:Confirmation]] and creates a confirmation page under the original page, with the result (Reproduced, Partly
#: reproduced or Did not reproduce), the card variant and their numbers.
# As soon as the page has a confirmation with result ''Reproduced'' whose author differs from <code>tested_by</code>,
#: the page shows {{Status|Proven}}, and [[All recipes]] and [[All platforms]] list it as Proven.

A confirmation always records the person who saves it: the wiki refuses a confirmation saved under someone else's
name. Imported Discord results that already had a second reproduction get their confirmation at import time, credited
to the second poster.

"Did not reproduce" and "Partly reproduced" stay visible in the infobox. If they pile up, change the page's status to
Contested and say what differs.

== Credits ==
Every imported fact ends with a credit line, <code><nowiki>{{Source|handle|YYYY-MM-DD|Discord message link}}</nowiki></code>,
for example {{Source|mountains|2026-10-12|https://discord.com/channels/1/2/3}}. See [[Contributing]].

[[Category:Help]]

Board how-to

2026-10-31T21:36:11Z

ImportBot: Wording: lab notes / site admins instead of a personal name

The board at [https://cmp.wiki/board/ cmp.wiki/board] is where testing tasks and ongoing work live. Anyone can read it;
sign in with Discord to take or move cards.

== Two projects ==
* '''CMP testing''': columns ''Wanted'', ''Testing'', ''Needs second confirmation'', ''Proven''. A card is a task
anyone can take ("Confirm Gen2 on a Dell R740", "Test recipe X on 10 GB"), and it links to its wiki page.
* '''Dev and research''': columns ''Idea'', ''Researching'', ''In progress'', ''Blocked'', ''Done''. One card per effort
(unlock and driver work, engine ports, VBIOS and firmware research, tooling), naming who is on it and the repo or thread.

== Taking a card ==
# Sign in on the board with Discord and move the card to ''Testing'' with your name on it.
# Run the test and write the result on the wiki page the card links to: a recipe, platform report or unlock, or a
#: confirmation on an existing page.
# Move the card on. A result that needs a second person goes to ''Needs second confirmation''.

== When a card reaches Proven ==
Only the board's managers (the site admins) move a card into ''Proven'', once the wiki page shows
{{Status|Proven}} (see [[Status taxonomy]]). The result lives on the wiki; the card closes.

[[Category:Help]]

Undervolting and power limits

2026-10-31T21:34:50Z

ImportBot: Undervolting (V/F offset), power caps and HBM clock on the CMP 170HX, with measured watts against tok/s and temperature; from the cmpunlocker Discord (including the Undervolting GUIDE thread), cachenetics/170tune and vektorprime/170tune (MIT), PixelML/club-170hx (Apache-2.0) and lab notes; gap-fill from #general 2026-10-23 to 10-25: @wakeupmbrc1, @munisix, @siriusrhi, @djpandaman, @xeax

Two levers decide how much power a CMP 170HX burns: the power cap, which every card has, and the undervolt (a V/F
offset), which only some VBIOS versions allow. Most owners serve at 140 to 200 W. This page covers both, plus the HBM
clock, which changes power and heat as well.

== What undervolting means on this card ==
* Undervolting is not lowering the clock. It shifts the V/F curve so the same frequency runs at a lower voltage. On this card it cuts power by up to 30 to 35 %. {{Source|handle=wakeupmbrc1|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559240649990078599}} At a lower clock a bigger offset is usually stable. {{Source|handle=sojun80|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1557395379727769661}} {{Source|handle=wakeupmbrc1|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559238426031562793}}
* In practice you raise the V/F offset (in MHz) and cap the clock with <code><nowiki>nvidia-smi -lgc</nowiki></code>; the card then reaches the capped clock at a lower voltage. On the 170tune reference card +250 MHz with a 1,400 MHz ceiling ran bf16 tensor GEMM at stock speed (186.5 against 184.3 TFLOPS) at 142.2 W instead of 199.2 W (29 % less), and the undervolt cut power 24.4 % (174.6 to 132.0 W) at a fixed 1,350 MHz. {{Source|handle=rh3dai|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1556287917775655053|repo=https://github.com/cachenetics/170tune|note=MIT license}}
* It is per card. Unlocked SMs and memory that were fused off as weak may not hold the same voltage as the factory parts, so step the offset up and find each card's limit. {{Source|handle=_orrorin|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559239454688944159}}
* The A100 PCIe cannot be undervolted and sits at its 300 W limit on compute-bound work; that is a large efficiency edge for the 170HX. {{Source|handle=wakeupmbrc1|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559794301708271767}}

== Before you start ==
# '''Check your VBIOS.''' Read it with <code><nowiki>nvidia-smi --query-gpu=index,vbios_version --format=csv</nowiki></code>. The V/F offset is only exposed by some versions:
#* 8 GB, 300 W VBIOS 92.00.6D.00.0A: NVML offset range -1000 to +1000. ([https://github.com/vektorprime/170tune/tree/fbpa-first-active branch fbpa-first-active]) {{Source|handle=rh3dai|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1556287917775655053|repo=https://github.com/vektorprime/170tune|note=MIT license; fork of cachenetics/170tune}}
#* 8 GB, 250 W VBIOS 92.00.67.00.01: range [0..0]. The set fails and reads back 0, and 170tune's gate still reports GATED because it tests whatever the card runs. {{Source|handle=c133|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562161732137386127|repo=https://github.com/PixelML/club-170hx|note=Apache-2.0 license}}
#* 10 GB VBIOS 92.00.66.00.02: range [0..+0], so there is no SM undervolt lever; max SM clock 1,410 MHz. {{Source|repo=https://github.com/vektorprime/170tune}}
#* An offset call can return success while the driver drops it; only a readback proves it applied. {{Source|repo=https://github.com/cachenetics/170tune}} On the lab's cards a miner's own core-offset call failed with "an internal driver error". {{Source|handle=darkmaniac7|date=2026-10-28|note=lab notes}}
#* {{Status|Contested}} Many Discord owners run offsets of +150 to +270 without saying which VBIOS they have {{Source|handle=cibernox|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1557385320465702933}} {{Source|handle=rh3dai|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1555480078089986138/1557687218473144411}}; check yours before you assume it works.
# '''Unlock first.''' 170tune needs the cmpunlocker memory unlock that opens the FBPA privilege masks, the kernel option <code><nowiki>iomem=relaxed</nowiki></code>, NVML and a CUDA toolkit; reference driver 610.43.03. <code><nowiki>sudo 170tune preflight</nowiki></code> checks all of it. {{Source|repo=https://github.com/cachenetics/170tune}} Some unlock builds leave the masks closed and preflight fails ("FBPA privilege masks (unlock)"); see [[Troubleshooting]]. {{Source|handle=rh3dai|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1556287917775655053}} {{Source|handle=drew_2|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1555480078089986138/1559076045645160469}}
# '''Know your fuse map before tuning the memory clock.''' {{Status|Warning}} On two of the lab's eight cards, which have FBPA0 fused off (one dead HBM stack each, read with matstatman/gpcprobe), a memory-PLL tuning driver build made the card fail at boot, because the PLL tools write FBPA0. Another unlock lineage runs those cards fine. {{Source|handle=darkmaniac7|date=2026-10-27|note=lab notes}}

== Steps with 170tune ==
These are the commands from the 170tune README; read <code><nowiki>170tune explain</nowiki></code> first. Gate one card at a time.
{{Source|repo=https://github.com/cachenetics/170tune}}
<syntaxhighlight lang="bash">
git clone https://github.com/cachenetics/170tune && cd 170tune
sudo ./install.sh # builds the helpers, installs to /usr/local/bin
sudo 170tune preflight # card, driver, unlock, iomem access, stock clock
sudo 170tune snapshot-stock # this card's stock values as its revert baseline (once)
sudo 170tune gate 250 1400 4 --workload /path/to/your-serving-check.sh # offset +250, ceiling 1400 MHz, 4 sweeps
sudo 170tune persist save --offset 250 --clk 1400 # refuses without a passing gate receipt
sudo 170tune persist enable # re-applies after boot; the card still boots stock first
sudo 170tune persist status
</syntaxhighlight>
* Start lower than +250. Several owners passed 170tune's gate and still saw errors days later: @cibernox went from +250 to +150 on one card {{Source|handle=cibernox|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1557385320465702933}}; @ichundes lowered his offset by 50 {{Source|handle=ichundes|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1557350219111342183}}. A slow ladder (30 MHz steps on the V/F shift) is what @wakeupmbrc1 suggests. {{Source|handle=wakeupmbrc1|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559795332014149763}}
* Gate at the temperature you will serve at. 170tune's default gate temperature is 60 C; PixelML serves at HBM 72 to 75 C and gated at 75 C. Gates soak at 300 W and 170tune's recover path sets 250 W, so re-apply your power cap afterwards. {{Source|repo=https://github.com/PixelML/club-170hx}}
* Back out with <code><nowiki>170tune persist disable</nowiki></code> or <code><nowiki>systemctl mask 170tune-persist.service</nowiki></code>; the card boots stock either way. {{Source|repo=https://github.com/cachenetics/170tune}}
* Other tools: the LACT curve editor accepts V/F curves that 170tune refuses, such as a curve from 210 MHz up to 1,695 MHz. {{Source|handle=vcore2191|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1534543856006332586/1557368673264476172}}

=== Signs the undervolt is too deep ===
Back off by 50 MHz and retest if you see any of these:
* {{Status|Proven}} <code><nowiki>Xid 48</nowiki></code> "uncorrectable ECC error ... in GPC0 GCC" with <code><nowiki>Xid 172</nowiki></code> "Uncorrectable SRAM error in GPC 0", then <code><nowiki>Xid 13</nowiki></code> Graphics Exception killing the vLLM worker. Lowering the offset by 50 fixed it {{Source|handle=ichundes|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1557350219111342183}}; a second owner stopped daily errors the same way (+250 to +150). {{Source|handle=cibernox|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1557385320465702933}} With ECC on, the engine crashes instead of producing garbage. {{Source|handle=ichundes|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1557350680342298647}}
* Gibberish output once or twice a day; gone after +250 to +150. {{Source|handle=cibernox|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1557385320465702933}}
* <code><nowiki>Xid 31</nowiki></code>. {{Source|handle=wakeupmbrc1|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559239856519913593}}
* <code><nowiki>Xid 13</nowiki></code> on the weakest SMs after a long soak, then <code><nowiki>Xid 43</nowiki></code> (+280 and above under a 200 W cap on the 170tune reference card; +300 and +350 profiles pass cool benchmarks and fail under long serving). {{Source|repo=https://github.com/cachenetics/170tune}}
* Random crashes on a multi-card model: suspect the weakest card. @cibernox's GLM-5.3-Flash failures stopped after he eased the undervolt on one of four cards. {{Source|handle=cibernox|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1556991885988339735}} {{Source|handle=voidgiraffe|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1556996431406043187}}
See [[Troubleshooting]] for Xid meanings.

== Power limits ==
<syntaxhighlight lang="bash">
sudo nvidia-smi --persistence-mode=1
sudo nvidia-smi -i 0 --power-limit=150 # per card; omit -i for all cards
nvidia-smi --query-gpu=index,power.draw,power.limit,temperature.gpu,temperature.memory --format=csv
</syntaxhighlight>
{{Source|repo=https://github.com/PixelML/club-170hx}} (per-card form: {{Source|handle=xeax|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560253213268250645}})
* A driver reload or a guest reboot resets the cap to the VBIOS default (250 W on most 8 GB cards), and services can overwrite it after boot. Set it from a unit that runs after everything else and check the live value. {{Source|repo=https://github.com/PixelML/club-170hx}}
* A power cap bounds heat whatever the workload does; a clock ceiling does not. 170tune recommends a cap for any box you cannot watch. ([https://github.com/cachenetics/170tune/blob/main/docs/power-cap-curve.md power-cap-curve.md]) {{Source|repo=https://github.com/cachenetics/170tune}}
* Draw goes above the cap in short spikes: up to 380 W on cards capped at 250 W {{Source|handle=n2dcrypt|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556771516803321877}}; over a 185 W cap during long 1M-token prefills {{Source|handle=c133|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1558163141723037798}}; one card drew 260 W at a 250 W cap {{Source|handle=moliminous|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1561769135057149953}}. Size PSUs for the spikes ([[Power supplies and cabling]]).
* {{Status|Reported}} Lowering the cap fixed instability: five cards on an external GPU switch board dropped off PCIe on large prompts until the cap went from 250 W to 180 W. {{Source|handle=moliminous|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1561749293717659774}} See [[Troubleshooting]].
* A cap is also the fix for poor cooling: 135 W while without proper fans {{Source|handle=wakeupmbrc1|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557500880452849735}}; 200 W when a card hits 85 C {{Source|handle=xeax|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560253213268250645}}. See [[Thermal limits]].
* Check for hardware power-brake slowdown with <code><nowiki>nvidia-smi -q | grep -A1 'HW Power Brake Slowdown'</nowiki></code>. {{Source|repo=https://github.com/PixelML/club-170hx}}

=== Caps people serve at ===
{| class="wikitable sortable"
! Cap !! Who and what !! Source
|-
| 110 to 165 W || four-card GLM-5.3-Flash TP4 sweep; 140 W chosen || {{Source|repo=https://github.com/PixelML/club-170hx}}
|-
| 140 W || DeepSeek V4.1 Flash on four cards, TP4 || {{Source|handle=anon33anon|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561910289799184445|repo=https://github.com/CurtisAccelerate/DeepSeekv41-Flash-1017-EXL3-CMP170HX|note=license in repo}}
|-
| 150 W || four cards, GLM-5.3-Flash TP with P2P on a consumer desktop || {{Source|handle=domrockt2|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1560417663564648499}}
|-
| 160 W || nine and ten-card rigs || {{Source|handle=reala7096|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556769461439168573}}
|-
| 170 W || one card, Qwen 3.8 27B w8a8 and w8a16 in vLLM || {{Source|handle=programmer_007|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560334482744152316}}
|-
| 175 W || the 170tune efficiency knee for unattended serving || {{Source|repo=https://github.com/cachenetics/170tune}}
|-
| 180 to 210 W || four cards "work perfectly fine if tuned properly" || {{Source|handle=wakeupmbrc1|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556358828629561365}}
|-
| 180 W || Morrowmake's GLM-5.3-Flash recipe on stock cards || {{Source|handle=wakeupmbrc1|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1560617496825036821}}
|-
| 180 to 230 W || The lab's eight-card server, set by an inlet-temperature governor (see [[Chassis builds]]) || {{Source|handle=darkmaniac7|date=2026-10-28|note=lab notes}}
|-
| about 202 W || four cards with 170tune <code><nowiki>--ndiv 66 --offset 270 --clk 1410 --timings "REFRESH 24"</nowiki></code> || {{Source|handle=rh3dai|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1555480078089986138/1557687218473144411}}
|-
| 200 W || four cards, +200 offset, clock 1,500 MHz, stock memory clock || {{Source|handle=alanoo|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559869739675942994}}
|-
| 230 W || 18 water-cooled cards at +210 to +240 offset, about 1,455 MHz || {{Source|handle=rh3dai|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559918625056366683}}
|-
| 300 W || four cards on one 1,600 W PSU || {{Source|handle=okrasit.|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556772848041988238}}
|-
| 150 to 180 W, rarely above 200 W || seven cards on a mining rack; an apartment breaker sets the ceiling, and above that the returns are minimal unless the cards are loaded all the time || {{Source|handle=munisix|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563786484912365689}}
|-
| 200 W || four cards for inference are "perfectly fine if properly undervolted and tuned" || {{Source|handle=wakeupmbrc1|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563783191725080629}}
|}
* @wakeupmbrc1 holds that GA100 is much more energy efficient for inference than GB202 (the RTX PRO 6000) in memory bandwidth per watt. {{Source|handle=wakeupmbrc1|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563782960648429669}} {{Source|handle=wakeupmbrc1|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563783041141313627}} @siriusrhi plans to start his cards at 200 W and go to 250 W once his wiring is fixed. {{Source|handle=siriusrhi|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563785800515063959}}

== Measured watts against throughput ==
=== Four cards, GLM-5.3-Flash TP4 ===
{{Status|Reported}} PixelML, 2026-10-02, HBM at 1,728 MHz on all cards, cap set live, structured output:
{| class="wikitable"
! Cap per card !! 1 user tok/s !! 8 users tok/s !! GPU power, 4 cards !! 8-user tok/s per W
|-
| 165 W || 418.6 || 822.4 || 650 W || 1.27
|-
| 150 W || 418.0 || 816.5 || 582 W || 1.40
|-
| 140 W || 412.7 || 814.2 || 537 W || 1.52
|-
| 130 W || 394.9 || 785.9 || 517 W || 1.52
|-
| 120 W || 374.4 || 756.5 || 476 W || 1.59
|-
| 110 W || 340.1 || 706.8 || 436 W || 1.62
|-
| 100 W || 291.9 || 627.4 || 398 W || 1.58
|}
At 150 W every card sits on the cap at about 1,320 MHz, yet 165 W adds only 0.1 to 1.1 %: decode waits on memory and
on the four-way synchronization. Below 130 W the core clock falls fast (1,290 to 1,050 MHz). At 165 W the HBM ran 82
to 83 C; the card with the worst airflow reached 80 to 85 C core on long prefill at 180 W.
([https://github.com/PixelML/club-170hx/blob/main/docs/CMP170HX-UNDERSTANDING.md power and heat table]) {{Source|repo=https://github.com/PixelML/club-170hx}}

=== One card, Qwen3.8-27B-FP8, offset +250 ===
{{Status|Reported}} 170tune reference card (8 GB, 300 W VBIOS), vLLM 0.26.0 with MTP:
{| class="wikitable"
! Cap !! Sustained clock !! Prefill (6.6k tokens) !! Decode, one stream !! Decode per request, 6-way load
|-
| 150 W || about 918 MHz || 1,421 tok/s || about 60 tok/s || 45 tok/s
|-
| 175 W || about 1,140 MHz || 1,712 tok/s || about 78 tok/s || 60 tok/s
|-
| 200 W || about 1,320 MHz || 1,929 tok/s || about 87 tok/s || 62 tok/s
|-
| 250 W || about 1,490 MHz || not measured || about 94 tok/s || not measured
|}
175 W is the knee: decode under load is flat from 175 to 200 W while the HBM runs about 6 C cooler. A 10-minute
6-way soak at 200 W held HBM at 84 to 85 C and the GPU at 78 C with zero Xids. Sustained clock against cap at +250:
250 W 1,490 MHz; 230 W 1,419; 200 W 1,291; 180 W 1,104; 150 W 901; 120 W 560; 110 W 517.
([https://github.com/cachenetics/170tune/blob/main/docs/power-cap-curve.md power-cap-curve.md]) {{Source|repo=https://github.com/cachenetics/170tune}} {{Source|repo=https://github.com/cachenetics/170tune}}
At 24 concurrent requests on Qwen3.6-27B INT8: +200/1,200 MHz under a 200 W cap gave 303.0 decode and 2,329 prefill
tok/s at 149 W (2.03 tok/s per W); +250/1,400 MHz under 300 W gave 342.9 and 2,669 at 178 W. {{Source|repo=https://github.com/cachenetics/170tune}}

=== Eight cards, sustained compute load at fixed caps ===
{{Status|Reported}} the lab server, four cards per run, stock clocks, fans at 20 % (a proof-of-work miner as the load,
not an LLM): 180 W was the best point. 150 W cost 13 to 22 % of throughput for 17 % less power; locking the clock at
1,200 MHz at 180 W cost 1 to 5 %; the miner's own core-offset option did not apply. At the same 180 W two of the four
cards ran 81 to 84 C and the other two 58 to 68 C, depending on the slot. {{Source|handle=darkmaniac7|date=2026-10-28|note=lab notes}}

== HBM clock (NDIV) and refresh ==
Memory clock = NDIV x 27 MHz. Stock NDIV is 54 (1,458 MHz) on the 8 GB 250 W VBIOS, 64 (1,728 MHz) on the 8 GB 300 W
VBIOS and 45 (1,215 MHz) on the 10 GB card. {{Source|repo=https://github.com/cachenetics/170tune}} Raising it costs power and heat; lowering it saves both.
* {{Status|Proven}} NDIV 70 is the usual ceiling: @alanoo's four cards do 70, maybe 72, and fail at 74. {{Source|handle=alanoo|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559862818432618529}} Hynix memory usually goes from 54 to 68 to 70. {{Source|handle=wakeupmbrc1|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559240995684483074}} 170tune qualifies NDIV 70 for serving only with HBM at or below about 76 C; NDIV 72 corrupts as it heats; 74 to 76 crash on the first real load. {{Source|repo=https://github.com/cachenetics/170tune}}
* {{Status|Contested}} What it buys depends on the workload. @alanoo found zero gain on real MoE loads up to NDIV 72 and runs stock memory {{Source|handle=alanoo|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559862818432618529}}; on dense Qwen 3.8 27B NDIV 54 to 70 gave +10.5 % at one stream {{Source|handle=wakeupmbrc1|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559901475528904796}}, NDIV 70 gave 3 to 4 % token generation for @fnerdman {{Source|handle=fnerdman|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559880359166877758}}, and about 5 % decode for @reala7096 {{Source|handle=reala7096|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1557604536649257041}}. 170tune: single-stream decode is not bandwidth bound, so the memory overclock buys nearly nothing there {{Source|repo=https://github.com/cachenetics/170tune}}. PixelML raised two slow cards to NDIV 64 and gained 5.8 to 6.3 % single-user and 3.1 to 3.8 % eight-user decode on GLM-5.3-Flash TP4. {{Source|repo=https://github.com/PixelML/club-170hx}}
* {{Status|Warning}} Never change NDIV under an active CUDA context: it wedges the GPU (Xid 45/119) and needs a power cycle. {{Source|repo=https://github.com/cachenetics/170tune}}
* {{Status|Contested}} @markshowa found NDIV cannot be changed at runtime and has to be set at boot {{Source|handle=markshowa|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1555480078089986138/1564081815013036093}}; 170tune changes it live with no CUDA context open, and the idle p-state settings switch between an idle and a busy NDIV (see [[P-states and idle power]]). {{Source|repo=https://github.com/cachenetics/170tune}}
* Lower NDIV for heat: NDIV 45 with REFRESH 24 saves heat with no loss on a proof-of-work load; raise it again for LLM work. {{Source|handle=markshowa|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1555480078089986138/1564081474989330453}}
* Refresh interval is an idle-power lever: at NDIV 76, REFRESH 24 cut idle from 41.0 to 34.9 W and load from 78.7 to 67.7 W with flat bandwidth; under a serving load it saves only about 2.5 % (206 against 201 W). Keep stock refresh if HBM goes above 85 C. {{Source|repo=https://github.com/vektorprime/170tune}}
* {{Status|Theory}} Headroom: @zorg33 thinks most cards can reach 1.9 to 2.0 TB/s with NDIV and timing tuning, which would put TP4 decode near 550 to 600 tok/s. {{Source|handle=zorg33|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1556935579919187989}}

== 10 GB cards ==
* {{Status|Reported}} After the SM unlock the 10 GB card is power bound. @djpandaman's card at 122 SMs hit the power cap and lost memory bandwidth even with the clock locked at 1,095 MHz; there was no difference between 108 and 122 SMs, and it capped even at 94 SMs. {{Source|handle=djpandaman|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559236914391949484}} {{Source|handle=emogop|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559239854842191903}}
* The 10 GB VBIOS has no SM offset range (see above), so the usual undervolt does not apply. {{Source|repo=https://github.com/vektorprime/170tune}}
* {{Status|Contested}} '''Can a fully SM-unlocked 10 GB card be undervolted?''' The question came up after @djpandaman's 122-SM card spiked to about 400 W at a 250 W limit (see [[Power supplies and cabling#PSU sizing]]). In the order posted:
** @djpandaman could not set the GPU clock by hand on that card the way he sets the memory clock, though he did not try hard, and presumes the SM clock is dynamic. {{Source|handle=djpandaman|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563223577501769749}}
** @wakeupmbrc1: set a GPU curve offset, so the card holds the same frequency at a lower voltage. {{Source|handle=wakeupmbrc1|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563225977906270380}} {{Source|handle=wakeupmbrc1|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563226038723547187}}
** The 170tune fork reads the offset range of the 10 GB VBIOS 92.00.66.00.02 as [0..+0] (the bullet above). {{Source|repo=https://github.com/vektorprime/170tune}}
* Safe power limits for fully SM-unlocked cards are not known yet. {{Source|handle=xeax|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563220557363814480}}
* {{Status|Contested}} What to do about it:
** @wakeupmbrc1: undervolting is necessary, and a shunt mod, better with the four unpopulated power phases soldered in (DrMOS, chokes, caps). {{Source|handle=wakeupmbrc1|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559237006444204075}} Untested in the posts. {{Status|Theory}}
** Asked whether he added power phases or limits power, @scallion_9883 said he swaps in the 300 W power curve from the 8 GB overclock VBIOS. {{Source|handle=globalapathy|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560792894401683577}} {{Source|handle=scallion_9883|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560793685116067925}}
** @djpandaman: "seemingly solved" by a method @lxtend found; details are not in the imported posts. {{Source|handle=djpandaman|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561024001516765365}}
* {{Status|Warning}} @xanthefin advises against the 300 W VBIOS: a photo of a burned 170HX was posted earlier, and the board lacks some power-delivery parts of the full layout. {{Source|handle=xanthefin|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561336153515364444}} The photo itself is not in the imported history.
* {{Status|Theory}} @matstatman found an unreleased "high power mode" that can be enabled even on 8 GB cards; he does not know what it does and will not release it. Defective-marked HBM may simply run too hot. {{Source|handle=matstatman|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562173369430974556}}

== Longer write-ups ==
* A longer write-up exists: the opening guide post of the Discord thread "Undervolting CMP170HX 8GB version GUIDE (Simple for every one!)", posted on 2026-10-02, before the imported history; see [https://discord.com/channels/1518634379604136178/1555480078089986138 Discord]. @rh3dai also posts tuning videos in that thread. {{Source|handle=rh3dai|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1555480078089986138/1556301132861800551}}

== See also ==
[[Cooling and power]] · [[P-states and idle power]] · [[Thermal limits]] · [[Power supplies and cabling]] ·
[[Troubleshooting]] · [[Recipes]] · [[Benchmarks]] · [[170tune]]

{{ImportFooter}}
[[Category:Cooling and power]]

[[Category:8 GB]]
[[Category:10 GB]]

Thermal limits

2026-10-31T21:34:50Z

ImportBot: Core and HBM temperature thresholds, throttling and drop-off behaviour, what temperatures people run at, how to read the sensors; from the cmpunlocker Discord (2026-10-04 to 10-27), cachenetics/170tune, PixelML/club-170hx, amoghmunikote/170th-Street, matstatman/hbmmon and lab notes; gap-fill from #general 2026-10-23 (400 W spike at a 250 W limit), @djpandaman, @xeax

The CMP 170HX runs hot for its power, and it has two temperatures that matter: the GPU core and the HBM memory. Under
load the HBM is usually the hotter one, and it is the one that limits memory overclocks and corrupts data first.
Keep the core under about 80 C and the HBM under about 80 to 85 C for daily use.

== Thresholds ==
{| class="wikitable"
! Sensor !! Temperature !! What happens !! Source
|-
| Core || about 76 C || throttling starts, according to a rough cooler model; keep core and HBM under 75 C || {{Status|Theory}} {{Source|handle=zorg33|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562110412395380767}}
|-
| Core || 80 C || PixelML's stop rule for core temperature || {{Source|handle=c133|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562161732137386127|repo=https://github.com/PixelML/club-170hx|note=Apache-2.0 license}}
|-
| Core || above about 80 C || GA100 leakage rises with temperature and the card runs away thermally || {{Source|handle=markshowa|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1561324784598384784|repo=https://github.com/amoghmunikote/170th-Street|note=no license stated}}
|-
| Core || 85 C || maximum operating temperature (read from the card, 170tune); "the cards will throttle at 85" {{Source|handle=matstatman|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1558212817121972318}}; "85 degrees is the maximum, so you're most likely bottlenecked by cooling" {{Source|handle=xeax|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560252687839133757}} || {{Source|handle=rh3dai|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1556287917775655053|repo=https://github.com/cachenetics/170tune|note=MIT license}}
|-
| Core || 95 C || hardware slowdown {{Source|repo=https://github.com/cachenetics/170tune}}; the card falls off the bus and turns off {{Source|handle=analyticeth|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557491900934791409}} || see cells
|-
| Core || 100 C || one card reached it by accident, cut its power as hard as it could, and still works || {{Source|handle=sojun80|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556855494008643698}}
|-
| HBM || about 75 to 76 C || a memory overclock (NDIV 70 and up) starts to corrupt data; 170tune qualifies NDIV 70 only with HBM at or below about 76 C || {{Source|repo=https://github.com/cachenetics/170tune}}
|-
| HBM || 80 C || "hbm doesn't have issues until 80c or so" {{Source|handle=replacedriver47|date=2026-10-10|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1558399070006157436}}; "anything above 80 is too hot" {{Source|handle=spectakkular|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1558215172294840442}} || see cells
|-
| HBM || 85 C || PixelML's stop rule for memory; above 85 C JEDEC halves the refresh interval, so keep stock refresh settings || {{Source|repo=https://github.com/PixelML/club-170hx}} {{Source|handle=rh3dai|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1556287917775655053|repo=https://github.com/vektorprime/170tune|note=MIT license; fork of cachenetics/170tune}}
|-
| HBM || 95 C || maximum operating temperature {{Source|repo=https://github.com/cachenetics/170tune}}; "a few minutes" at 95 C corrupts data in the WPR {{Source|handle=bigptoughneigh|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1558266699218812929}} || see cells
|}

=== Where people disagree ===
{{Status|Contested}}
* How hot is too hot: @mountains1605 called @arabus_74064's temperatures on Qwen3.8 Next Flash too hot, while @arabus_74064 thought them normal at full load. {{Source|handle=mountains1605|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1558199574974304338}} {{Source|handle=arabus_74064|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1558210159942041702}} @replacedriver47: the SMs are not the problem, the HBM is, and it is more prone to heat damage {{Source|handle=replacedriver47|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1558217213717254195}}; @rrickk420: "you're frying your mem" {{Source|handle=rrickk420|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1558221699038576726}}; @bigptoughneigh: memory is not always hotter than the core under load {{Source|handle=bigptoughneigh|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1558266699218812929}}; @dottoreargus barely reaches 65 C on the same model {{Source|handle=dottoreargus|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1558215409625333812}}.
* @impactic thought the card shuts itself down above 95 C; @prefix10k thought 85 C is already bad. {{Source|handle=prefix10k|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556853048943452211}} {{Source|handle=impactic|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556861368513331264}}
* The throttle point: 76 C by @zorg33's model {{Source|handle=zorg33|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562110412395380767}} against 85 C by @matstatman {{Source|handle=matstatman|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1558212817121972318}} and the card's own maximum operating value {{Source|repo=https://github.com/cachenetics/170tune}}.

== Without airflow the card dies fast ==
* {{Status|Proven}} A card without a fan reaches 95 C quickly even at its 40 W idle, falls off the bus and turns off. {{Source|handle=analyticeth|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557491900934791409}} {{Source|handle=nikhilr1696|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557492862344630364}} @programmerboi's passive card stopped showing in <code><nowiki>nvidia-smi</nowiki></code> at 85 C while idle {{Source|handle=programmerboi|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560492431768813611}}, and a new 10 GB card "clocked out in under 5 mins without cooling. way worse than V100" {{Source|handle=programmerboi|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1563704621388529725}}. The heatsink is designed for high-airflow servers and does not work even at idle without it. {{Source|handle=civiloid|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560561874188374087}} {{Source|handle=globalapathy|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1563704870073143377}}
* {{Status|Warning}} A failed fan means a dead card or worse; @nikhilr1696 only runs these cards supervised. {{Source|handle=nikhilr1696|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557491750145232997}} Use a decent fan, not necessarily a blower. {{Source|handle=cibernox|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557506106509631579}}

== Throttling behaviour ==
* When the cap or the temperature limit bites, the core clock drops and with it memory bandwidth and tokens per second. On a 10 GB card with all SMs unlocked, the power cap tanked memory bandwidth even with the clock locked. {{Source|handle=djpandaman|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559236914391949484}} See [[Undervolting and power limits]].
* {{Status|Warning}} '''A 250 W cap did not bound a fully SM-unlocked 10 GB card.''' @djpandaman's card at 122 SMs briefly reported about 400 W of board power during benchmarks with the limit at 250 W (he was unsure whether the reading was measured or calculated), and all of it ends up in the same heatsink and VRM. @xeax worries the VRM MOSFETs get overloaded and doubts he could cool that load. On such a card, watch core and HBM temperatures under real load instead of trusting the cap, and undervolt (see [[Undervolting and power limits#10 GB cards]] and [[Power supplies and cabling#PSU sizing]]). {{Source|handle=xeax|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563222111592521881}} {{Source|handle=djpandaman|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563222404627431497}}
* Prefill is where cards run hottest: @c133's cards spike over their cap during long prefills {{Source|handle=c133|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1558163141723037798}}; PixelML's worst-airflow card reached 80 to 85 C core on long-context prefill at 180 W, which is why they lowered the cap {{Source|repo=https://github.com/PixelML/club-170hx}}.
* Check whether the card is in hardware power-brake slowdown: <code><nowiki>nvidia-smi -q | grep -A1 'HW Power Brake Slowdown'</nowiki></code>. {{Source|repo=https://github.com/PixelML/club-170hx}}
* {{Status|Reported}} A card cooled by the fan that came in the Alifond package reached 85 C at full fan speed running a 27B Q8 model on llama.cpp; @xeax: 85 C is the maximum, so it is cooling-bound. {{Source|handle=programmer_007|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560252510193590395}} {{Source|handle=xeax|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560252687839133757}}
* Fixes, in order: improve the air path (see [[Fans and ducts]]), lower the cap ({{Source|handle=xeax|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560253213268250645}}: <code><nowiki>sudo nvidia-smi -i 0 -pl 200</nowiki></code>), then consider water ([[Water cooling]]). These chips run 400 W on SXM4 boards; better cooling is what unlocks more of them. {{Source|handle=xeax|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560253818329899039}}

== What temperatures people run at ==
{| class="wikitable sortable"
! Cooling !! Cap !! Hottest reading !! Source
|-
| Water block, full load || 250 W || 50 C || {{Source|handle=leenodie|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1545982693903306813/1564340979065163910}}
|-
| Water block, 360 mm radiator, fans at minimum || 180 W || 45 C || {{Source|repo=https://github.com/amoghmunikote/170th-Street}}
|-
| Water, general || not given || 50 to 60 C || {{Source|handle=endsjeremy|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1561901936494649345}}
|-
| Air, unlocked 64 GB card || 175 W || 60 C core, 65 C HBM || {{Source|handle=rrickk420|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1557800123457736795}}
|-
| One 80 mm fan per pair, no duct || 185 W || 63 C || {{Source|handle=c133|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1558160764370690100}}
|-
| S12038-4K push only, four cards, cold garage || 200 W || 62 C || {{Source|handle=alanoo|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564379568801058877}}
|-
| Blower at 50 to 60 % || 200 W || 60 C || {{Source|handle=68x0|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560301937675599944}}
|-
| P12 Pro on a shroud || 175 W || 65 C || {{Source|handle=rrickk420|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518691940646781070/1557456081607860236}}
|-
| Sealed funnel || 150 W || 70 C || {{Source|handle=globalapathy|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518691940646781070/1557451493379154061}}
|-
| S12038-4K push-pull, 24 C room || 300 W || HBM 72 C || {{Source|handle=wakeupmbrc1|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560655488331546715}}
|-
| P12 Pro push and pull on 3-card plenums, 10 minutes full power || full || 80 C || {{Source|handle=reala7096|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1557593651037737051}}
|-
| One card, 6-way inference soak for 10 minutes || 200 W || HBM 84 to 85 C, GPU 78 C || {{Source|repo=https://github.com/cachenetics/170tune}}
|-
| Four cards, GLM-5.3-Flash TP4 || 165 W || HBM 82 to 83 C || {{Source|repo=https://github.com/PixelML/club-170hx}}
|-
| Eight cards in a server with a fan wall, same cap, by slot || 180 W || 58 to 68 C on two slots per CPU, 81 to 84 C on the other two || {{Source|handle=darkmaniac7|date=2026-10-28|note=lab notes}}
|-
| Four idle cards, one 80 mm blower on a printed duct || idle || core 37 to 38 C, memory 41 to 51 C || {{Source|repo=https://github.com/PixelML/club-170hx}}
|-
| Sandwiched cards with shared intake || under load || 34 to 42 C || {{Source|handle=moliminous|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558686919033094145}}
|}

== Reading the sensors ==
* <code><nowiki>nvidia-smi -q -d TEMPERATURE</nowiki></code> {{Source|handle=xeax|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560253301985906692}}, or for logging <code><nowiki>nvidia-smi --query-gpu=index,temperature.gpu,temperature.memory,power.draw --format=csv</nowiki></code> {{Source|repo=https://github.com/PixelML/club-170hx}}. Watch <code><nowiki>temperature.memory</nowiki></code>: HBM is usually the warmest sensor under load. {{Source|repo=https://github.com/cachenetics/170tune}}
* The card has about 10 temperature sensors, including one per HBM stack. {{Source|handle=matstatman|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556770474695069718}} [https://github.com/matstatman/hbmmon matstatman/hbmmon] shows per-stack temperature, but it writes to the HBM debug interface by default and needs a custom driver; use its read-only mode on a stock driver. {{Source|handle=matstatman|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556758870565593288|repo=https://github.com/matstatman/hbmmon|note=no license file}}
* The 10 GB card's memory runs a few degrees warmer than the 8 GB card's (two more half stacks active): 41 C against 37 C, both at about 33 W idle, after a repaste; before the repaste the gap was 13 C, which pointed at the thermal interface. The owner used PTM on the 8 GB card and then ran out; what went on the 10 GB card is not stated. {{Source|handle=ghostinthedatacenter_87281|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559597067352023152}} {{Source|handle=colo2442|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559599442166812784}} {{Source|handle=djpandaman|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559649510827757569}} {{Source|handle=ghostinthedatacenter_87281|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559651382816936108}} {{Source|handle=ghostinthedatacenter_87281|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559653025700909117}}
* A server BMC cannot read the temperature of a card on a generic passive riser, so it will not ramp the fans for it. {{Source|handle=fafinet|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562300430439157850}}

== Room and inlet temperature ==
* Your intake air sets the floor. The lab's eight-card server raises its power caps only while the inlet is below 24 C and lowers them above 27 C; at about 2 kW into a room, the room became the limit before the fans did. See [[Chassis builds]]. {{Source|handle=darkmaniac7|date=2026-10-27|note=lab notes}}
* Twelve cards on dedicated circuits with an air conditioner pointed at them is still the warmest and loudest room in @gpmickey's house. {{Source|handle=gpmickey|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561664734179364944}}
* {{Status|Warning}} Do not feed cold winter air or sub-dew-point coolant to the cards: condensation. {{Source|handle=alanoo|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562111068204044420}} {{Source|handle=gnasherrr|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564185826538160159}}
* Paste and pads matter for the last few degrees; see [[Water cooling]] for opening the card.

== See also ==
[[Cooling and power]] · [[Fans and ducts]] · [[Water cooling]] · [[Undervolting and power limits]] ·
[[P-states and idle power]] · [[Troubleshooting]] · [[Tools]]

{{ImportFooter}}
[[Category:Cooling and power]]

[[Category:8 GB]]
[[Category:10 GB]]

Server BIOS setup

2026-10-31T21:34:49Z

ImportBot: Gen2 and 64 GB BAR1 runbook for servers, from @darkmaniac7 lab notes (8 cards bare metal, 4 cards under ESXi), plus Discord reports on MMIO windows, PLX hotplug and BMC fans

{{Status|Reported}} {{Cards|both}}

How to get a CMP 170HX to '''PCIe Gen2''' and a '''64 GB BAR1''' on a server, and what to check when it does not happen. It comes from getting 8 cards to Gen2 x16 with 64 GB BAR1 on bare metal, and 4 cards to Gen2 with 64 GB BAR1 under ESXi passthrough. The page works as a checklist for a person, and it works just as well handed to an AI agent with a root shell, with a person making the BIOS changes and power cycles. {{Source|handle=darkmaniac7|date=2026-10-29|note=lab notes}}

For what the two features are, see [[Gen2 link retrain]] and [[Resizable BAR and BAR1 64 GB]]. For desktop boards, see [[Consumer motherboards]]. For hypervisors, see [[Virtual machines and passthrough]].

== Rules ==
# '''Collect facts first''' (the script below). Change nothing until you know which case you are in.
# '''One change per reboot.''' Save the collect output before and after every change, so each change can be judged on its own.
# '''BIOS changes, reboots and cold power cycles are done by a person.''' If an agent is helping, it proposes the exact setting and the reason; it does not do them.
# '''Do not try Gen3 on 8 GB cards.''' On the 8 GB cards (<code><nowiki>10de:20c2</nowiki></code>) Gen3 and Gen4 are fused off, and so is the software fuse override (<code><nowiki>0x820084</nowiki></code> bit 0 = 1). One attempt through the XP/XVE registers left a card stuck at Gen1 until a power cycle. Gen2 is the ceiling. Gen3 on 10 GB cards is a separate route, see [[Unlocks]].
# '''Never flash a VBIOS''', and never write PCI config space by hand on a live system unless you know exactly why.
# '''If you have a working machine with the same cards''', run the collect script there too and diff the two. That is the fastest way to find the difference.
{{Source|handle=darkmaniac7|date=2026-10-29|note=lab notes}}

== What working looks like ==
Reference box: Supermicro H12DSG-O-CPU (dual EPYC Rome), 8 cards, Ubuntu 24.04, kernel 6.8.0, nvidia-open 615.71.09 patched by the Morrowmake cmpunlocker fork ([https://github.com/Morrowmake/cmpunlocker github.com/Morrowmake/cmpunlocker], branch <code><nowiki>p2p-ecc</nowiki></code>, commit <code><nowiki>87cb5fd</nowiki></code>), installed with:
<syntaxhighlight lang="bash">
sudo ./install.sh --p2p --profile=8gb --no-iommu --no-passthrough
</syntaxhighlight>

<pre>
$ nvidia-smi --query-gpu=index,pci.bus_id,pcie.link.gen.current,pcie.link.width.current,memory.total --format=csv,noheader
0, 00000000:01:00.0, 2, 16, 65536 MiB (all 8 cards the same)

$ nvidia-smi -q -i 0 | grep -A3 "BAR1 Memory Usage"
Total : 65536 MiB

$ lspci -s 01:00.0 -vvv
Region 1: Memory at 29000000000 (64-bit, prefetchable) [size=64G]
Region 3: Memory at 28800000000 (64-bit, prefetchable) [size=32M]
LnkCap: Port #0, Speed 5GT/s, Width x16
LnkSta: Speed 5GT/s, Width x16
Capabilities: [bb0 v1] Physical Resizable BAR
BAR 1: current size: 64GB, supported: 64MB 128MB ... 32GB 64GB

$ grep -E "RegistryDwords|EnableResizableBar" /proc/driver/nvidia/params
EnableResizableBar: 1
RegistryDwords: "RmForceEnableGen2=1;RMPcieLinkSpeed=0x1;ForceP2P=0x11"

$ cat /etc/modprobe.d/cmp-pcie-gen2.conf (written by the installer)
options nvidia NVreg_RegistryDwords="RmForceEnableGen2=1;RMPcieLinkSpeed=0x1;ForceP2P=0x11"

$ dmesg | grep -E "BAR 1|CMP BAR1"
pci 0000:01:00.0: BAR 1 [mem 0x380a8000000-0x380abffffff 64bit pref] <- firmware sizes it 64 MB
NVRM: CMP BAR1: before CYA=0x00000026 CFG=0x80000000 CAP=0x00000400
NVRM: CMP BAR1: after CYA=0x00000030 CFG=0x8000000a CAP=0x001ffc00
NVRM: CMP BAR1: resize enabled, will attempt up to 64 GB
NVRM: CMP BAR1: final size = 65536 MB <- the driver resized it
</pre>

Kernel command line: <code><nowiki>amd_iommu=on iommu=pt</nowiki></code>, nothing PCI-specific (no <code><nowiki>pci=realloc</nowiki></code>). Firmware put the 64 MB BAR1 above 4 GB, so "Above 4G Decoding" was on. The rest of the BIOS settings were not recorded.

<code><nowiki>nvidia-smi -q</nowiki></code> showing <code><nowiki>Device Max: 1</nowiki></code> under PCIe Generation is normal on these cards, even when they run Gen2. Read <code><nowiki>Current</nowiki></code>.
{{Source|handle=darkmaniac7|date=2026-10-29|note=lab notes}}

== How the two features work ==
Most dead ends come from treating these like normal ReBAR and normal link speed settings.

'''Gen2.''' Stock, the card trains at Gen1: LnkCap advertises 2.5 GT/s only. The BIOS and the root port cannot raise that, because the card's own LnkCap is the limit. The patched driver raises it from the GPU side during its unlock window: it programs the card's link registers for Gen2, requests a directed speed change and waits for the link to retrain. The RM keys in <code><nowiki>RegistryDwords</nowiki></code> switch that on. With the stock NVIDIA driver, or if those keys never reach the driver, the card stays at Gen1. Link width is whatever the slot or riser gives (an x8 slot gives Gen2 x8).

'''BAR1.''' At every power-on the card's Resizable BAR capability advertises only 64 MB (CAP <code><nowiki>0x400</nowiki></code>). So the BIOS sizes BAR1 at 64 MB, and a BIOS "Resizable BAR" option cannot do better, because the card is not offering more yet. The patched driver then writes two card registers (CYA <code><nowiki>0x724 = 0x30</nowiki></code>, CFG <code><nowiki>0xdcc = 0x8000000a</nowiki></code>). After that the capability offers 64 MB to 64 GB (CAP <code><nowiki>0x1ffc00</nowiki></code>), and the driver asks the kernel to resize BAR1 to 64 GB. BAR3 (32 MB) moves too.

For that resize to work, the kernel has to fit 64 GB + 32 MB per card, 64 GB-aligned, inside the 64-bit prefetchable window of the card's parent bridge, and grow that window if it is too small. That is where servers fail: tight MMIO layouts, bridge windows the firmware sized exactly, or two cards sharing one bridge or switch.

'''What you lose without a 64 GB BAR1.''' The 64 GB of VRAM and the compute unlock still work with a 64 MB BAR1. What it costs is P2P between cards. Engines like the Morrowmake recipes check P2P at startup and fall back to copies through host memory, so it is a speed loss for tensor parallel, not a failure.
{{Source|handle=darkmaniac7|date=2026-10-29|note=lab notes}}

== Collect facts ==
Run this as root and save the output (<code><nowiki>collect.sh > facts-$(hostname)-$(date +%H%M).txt 2>&1</nowiki></code>):
<syntaxhighlight lang="bash">
#!/bin/bash
echo "== system"; dmidecode -s system-manufacturer; dmidecode -s system-product-name; dmidecode -s bios-version
uname -r; cat /proc/cmdline
echo "== driver"; head -1 /proc/driver/nvidia/version 2>&1
grep -E "RegistryDwords|EnableResizableBar" /proc/driver/nvidia/params 2>&1
grep -rH "nvidia" /etc/modprobe.d/ /lib/modprobe.d/ 2>/dev/null | grep -v ":#"
lsinitramfs /boot/initrd.img-$(uname -r) 2>/dev/null | grep -E "nvidia|modprobe.d" | head
echo "== cards"
nvidia-smi --query-gpu=index,pci.bus_id,pcie.link.gen.current,pcie.link.gen.max,pcie.link.width.current,memory.total --format=csv,noheader
nvidia-smi -q | grep -A2 "BAR1 Memory Usage"
echo "== tree"; lspci -tv
for d in $(lspci -D -d 10de: | awk '{print $1}'); do
echo "=== GPU $d"
lspci -s $d -vvv | grep -E "Region|LnkCap:|LnkSta:|LnkCtl2|Resizable|BAR [0-9]:"
p=$(basename $(dirname $(readlink -f /sys/bus/pci/devices/$d)))
while [[ $p =~ ^[0-9a-f]{4}: ]]; do
echo "--- upstream $p"
lspci -s $p -vvv | grep -E "^[0-9a-f]|Prefetchable memory behind|LnkCap:|LnkSta:|LnkCtl2|SltCap|HotPlug"
p=$(basename $(dirname $(readlink -f /sys/bus/pci/devices/$p)))
done
done
echo "== dmesg: driver"; dmesg | grep -iE "NVRM: CMP|retrain|Xid" | head -40
echo "== dmesg: BARs"; dmesg | grep -iE "BAR 1|BAR 3|no space|failed to assign|can't assign|resiz" | head -40
echo "== dmesg: root windows"; dmesg | grep -E "root bus resource \[mem" | head -20
</syntaxhighlight>

The upstream walk shows every bridge between the card and the root complex. More than one bridge in that list means a PCIe switch (common on GPU risers and some Dell GPU configurations). The switch's windows have to grow too.
{{Source|handle=darkmaniac7|date=2026-10-29|note=lab notes}}

=== Dell PowerEdge: dump the BIOS PCI settings ===
If the box has an iDRAC, dump the BIOS PCI settings as they are now. Attribute names differ by PowerEdge generation, so list them rather than guessing:
<syntaxhighlight lang="bash">
racadm get BIOS.IntegratedDevices
racadm get BIOS.SysProfileSettings
racadm get BIOS | grep -iE "mmio|4g|bar|sriov|slot|speed|link|bifurc|aspm"
</syntaxhighlight>
On 14th-generation PowerEdge (R640, R740 and so on), the settings that matter are under Integrated Devices: "Memory Mapped I/O above 4GB" and "Memory Mapped I/O Base". Check the names on your BIOS before changing anything.
{{Source|handle=darkmaniac7|date=2026-10-29|note=lab notes}}

== Find your case and fix it ==

=== Case A: the unlock is not active (memory shows 8 GB, no <code><nowiki>NVRM: CMP</nowiki></code> lines) ===
Neither Gen2 nor BAR1 can work yet, so fix this first.
* Install the same unlocker commit and driver version as a working box, with <code><nowiki>--profile=8gb</nowiki></code> (8 GB cards) or <code><nowiki>--profile=10gb</nowiki></code> (10 GB cards). See [[Unlocks]].
* A kernel or nvidia package upgrade puts the stock modules back through DKMS. The cards drop to 8 GB and Gen1 without any error. Hold the kernel and every nvidia package once it works. See [[Operating systems and kernels]].
* The unlocker README says: if memory stays at its stock size, power off completely before booting. That means a real cold start (AC off, about 10 s), not a reboot.
{{Source|handle=darkmaniac7|date=2026-10-29|note=lab notes}}

=== Case B: unlocked (64 GB VRAM) but still Gen1 ===
# <code><nowiki>RegistryDwords</nowiki></code> must show the Gen2 keys in <code><nowiki>/proc/driver/nvidia/params</nowiki></code>. If it does not, the options file was not read. When nvidia is loaded from the initramfs, the options must be in it too: run <code><nowiki>update-initramfs -u</nowiki></code> and reboot. Only one <code><nowiki>NVreg_RegistryDwords</nowiki></code> line counts; a second file silently replaces the first. Grep every modprobe file.
# <code><nowiki>dmesg | grep -iE "retrain|gen2|link speed"</nowiki></code> shows whether the driver tried and what it got.
# On every upstream bridge, LnkCap must allow at least 5 GT/s, and LnkCtl2 "Target Link Speed" must not be 2.5 GT/s. If a root port targets 2.5 GT/s, the BIOS has that slot limited. Look in the BIOS for a per-slot link speed setting and set it to Auto, or Gen2 or higher.
# If LnkSta shows 2.5 GT/s with "(downgraded)" after a retrain, the link failed at Gen2 and fell back. That points at the signal path, not settings: a riser, an extension cable or a slot. Move the card to another slot to test. See [[Risers and bifurcation]].
# Do not change anything for Gen3 (see the rules at the top).
{{Source|handle=darkmaniac7|date=2026-10-29|note=lab notes}}

=== Case C: unlocked and Gen2, but BAR1 stays 64 MB (or 256 MB) ===
Read the <code><nowiki>NVRM: CMP BAR1</nowiki></code> lines first.
* '''No "resize enabled" line:''' check <code><nowiki>EnableResizableBar</nowiki></code> in <code><nowiki>/proc/driver/nvidia/params</nowiki></code>. It is 1 by default on the patched build; if it is 0, set <code><nowiki>options nvidia NVreg_EnableResizableBar=1</nowiki></code>.
* '''"final size" below 65536 MB, or kernel lines like "no space for" / "failed to assign" near BAR 1:''' the bridge window cannot take 64 GB. Try these one at a time, running the collect script after each:
# BIOS: "Memory Mapped I/O above 4GB" (Above 4G Decoding) Enabled. Without it nothing else matters.
# BIOS: give the 64-bit MMIO space as much room as the BIOS allows. On PowerEdge that is "Memory Mapped I/O Base". The options vary by generation, and a higher base address usually leaves more room above it. Linux handles any of them. Record the old value so it can go back.
# Kernel: add <code><nowiki>pci=realloc</nowiki></code> to the command line. This lets Linux release and reassign bridge windows that firmware sized too tightly. Edit <code><nowiki>/etc/default/grub</nowiki></code>, run <code><nowiki>update-grub</nowiki></code>, then reboot. If something other than the GPUs breaks (NICs, storage), remove it again.
# Isolate: test with one card. Two cards behind the same bridge or switch need room for two 64 GB + 32 MB blocks, each 64 GB-aligned, in one window. If one card resizes and two do not, it is window size or placement. Try the cards on different root ports if the chassis allows.
# A BIOS "Resizable BAR" option, if this model has one, will not help by itself: at power-on the card only offers 64 MB. Enabling it is harmless. Change one thing at a time.
{{Source|handle=darkmaniac7|date=2026-10-29|note=lab notes}}

'''If none of that works:''' the remaining route is resizing the card before the OS boots. That was done for ESXi with a small UEFI app that reserves a 64 GB-aligned block in the firmware memory map, then does the same two register writes plus the BAR and bridge-window programming. It works, but it has to run on every boot. The procedure, the risks and the code are on [[BAR1 64 GB on ESXi]] and in [https://github.com/darkmaniac7/cmp170hx-esxi darkmaniac7/cmp170hx-esxi]; read them rather than improvising. {{Source|handle=darkmaniac7|date=2026-10-21|repo=https://github.com/darkmaniac7/cmp170hx-esxi|note=lab notes}}

==== What others hit in case C ====
* '''Window too small for the card count.''' A Minisforum MS-01 host with 4 cards behind a PLX 88096 switch had an MMIO space of 256 GB, too small for four 64 GB BAR1s, and the firmware tried to place the BAR1s inside a 512 MB section. Resizable BAR was already enabled. {{Source|handle=replacedriver47|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562908042217922662}} {{Source|handle=replacedriver47|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562948169174749246}} {{Source|handle=replacedriver47|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562948621446549575}} Two days later the same owner got 2 of the 4 cards to 64 GB BAR1 by changing MMIOH and BAR sizes; the MMIOH size still prevented all 4. {{Source|handle=replacedriver47|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563629333552177284}} {{Source|handle=replacedriver47|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563629971082186753}} See [[Minisforum MS-01]].
* '''PCIe switch firmware.''' The same owner found the PLX 88096 firmware on his switch board did not have hotplug enabled, which he says is required to remap BAR addressing behind the switch. {{Source|handle=replacedriver47|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1563580726882861097}}
* '''Hidden MMIOH settings on older boards.''' On an ASUS P9X79 WS the BIOS allocates only a small 64-bit window above 4 GB, so a 64 GB BAR request fails. Above 4G Decoding was present; the owner's assistant changed Ubuntu (kernel) parameters and it then worked. The exact parameters were not posted. {{Source|handle=globalapathy|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561805422950875147}} {{Source|handle=globalapathy|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561806012179288205}} {{Source|handle=fdelfini|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561810276351741975}} See [[ASUS P9X79 WS]].
* '''Two cards behind one switch crash the kernel at boot''' unless the per-card BAR1 resize is serialized: the PixelML club host (two PLX PEX 8747 switches, two cards per switch) corrupted the kernel resource tree on every boot until a <code><nowiki>rebar-serialize.patch</nowiki></code> (one mutex around the resize, the same fix as upstream cmpunlocker PR #59) was applied. {{Source|handle=djpandaman|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563629622673936384|repo=https://github.com/PixelML/club-170hx}} (docs/CMP170HX-UNDERSTANDING.md)
* '''P2P at a 64 MB BAR1, instead of fighting MMIO.''' {{Status|Contested}}
** OB88594: do not try to fix MMIO sizing unless the motherboard has independent options for it; the Morrowmake fork can do P2P at a 64 MB BAR1. {{Source|handle=ob88594|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1558810215665893436}}
** replacedriver47: the Morrowmake build reports P2P working with no BAR1, but no transfers go through. {{Source|handle=replacedriver47|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1558844986156388454}}

=== Case D: the cards are passed through to a VM (Proxmox, ESXi) ===
The unlock has to run where the NVIDIA driver runs. Under ESXi, firmware sizes BAR1 at 64 MB before ESXi sees it, so the 64 GB BAR1 needs the pre-boot step above ([[BAR1 64 GB on ESXi]]). The VM also needs <code><nowiki>pciPassthru.use64bitMMIO = TRUE</nowiki></code> and a large <code><nowiki>pciPassthru.64bitMMIOSizeGB</nowiki></code> (1024 was needed for four cards). Gen2 works from inside the guest. P2P between CMPs inside a VM did not work; the same cards do 12/12 pairs on bare metal. Bare metal is much simpler. Details and Proxmox reports: [[Virtual machines and passthrough]]. {{Source|handle=darkmaniac7|date=2026-10-29|note=lab notes}}

== Verify ==
<syntaxhighlight lang="bash">
nvidia-smi --query-gpu=index,pcie.link.gen.current,pcie.link.width.current,memory.total --format=csv,noheader
nvidia-smi -q | grep -A1 "BAR1 Memory Usage" # Total 65536 MiB
python3 tools/p2p-content-check.py # from the cmpunlocker repo; must exit 0
</syntaxhighlight>
<code><nowiki>p2p-content-check.py</nowiki></code> copies random data between every ordered pair of cards and compares every byte. <code><nowiki>nvidia-smi topo</nowiki></code> and "peer access supported" alone do not prove P2P works. Morrowmake's README measured about 6.65 GB/s each way between two cards at Gen2 x16. Check that <code><nowiki>dmesg | grep Xid</nowiki></code> stays empty. {{Source|handle=darkmaniac7|date=2026-10-29|note=lab notes}}

== Undo ==
* Driver: <code><nowiki>sudo ./remove.sh --yes</nowiki></code> in the cmpunlocker repo, then reboot.
* BIOS: put back the values recorded by the collect script.
* Kernel: remove <code><nowiki>pci=realloc</nowiki></code> from <code><nowiki>/etc/default/grub</nowiki></code>, run <code><nowiki>update-grub</nowiki></code>, reboot.

== BMC and fan settings on GPU servers ==
* '''Supermicro BMC Full mode persists across power loss, the zone duty does not.''' A board left in Full fan mode comes back from a cold boot with every fan at 100% until the OS rewrites the duty. Leave the mode at Optimal when the OS is down, or have the fan service read the duty back and rewrite it. {{Source|handle=darkmaniac7|date=2026-10-27|note=lab notes}} The PixelML club measured the same on a Supermicro BMC: switching to Full and writing zone duties once left fans at 100% after a cold boot. {{Source|handle=djpandaman|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563629622673936384|repo=https://github.com/PixelML/club-170hx}}
* '''EPYC boards without BMC fan curves:''' on fafinet's EPYC host (EPYC 7502 with an AST2500 BMC daughterboard; the message does not name the board) the smart fan curve is linear and can only be set in the BIOS, with no BMC control, and the other fan headers can be set with <code><nowiki>ipmitool raw 0x0e 0x65 0 (value)</nowiki></code>. {{Source|handle=fafinet|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564263781108940871}} GlobalApathy finds the ASRock Rack ROMED8-2T's fan curve settings weak too. {{Source|handle=globalapathy|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562647408293318733}}
* Fan noise on 2U GPU servers and thermal-target fan control: see [[Cooling and power]].

== Related ==
* [[Platforms]], [[Consumer motherboards]], [[Risers and bifurcation]], [[Virtual machines and passthrough]], [[Operating systems and kernels]]
* [[Gen2 link retrain]], [[Resizable BAR and BAR1 64 GB]], [[P2P]], [[Kernel parameters and module options]], [[Unlocks]]
* [[Troubleshooting]], [[Card not detected or BAR allocation fails]]

== Credits ==
Runbook by @darkmaniac7 from the lab's own servers. The unlock is [https://github.com/amoghmunikote/cmpunlocker amoghmunikote/cmpunlocker]; the P2P/ECC fork used on the reference box is [https://github.com/Morrowmake/cmpunlocker Morrowmake/cmpunlocker].

{{ImportFooter}}
[[Category:Platforms]]
[[Category:8 GB]]
[[Category:10 GB]]

Rumours and claims to verify

2026-10-31T21:34:48Z

ImportBot: Import (V2): register of unverified claims from the cmpunlocker Discord, @ob88594, @wakeupmbrc1, @djpandaman, @aaasss1456, @analyticeth, @douya4305, @rrickk420, @bigptoughneigh, @cuddylac997, @zingy90210, @exile_1ck, @cute_sc2, @_____josh_____, @matstatman, @colo2442, @scallion_9883, @xanthefin, @feralzi, @kellertreppe123 and others

Claims made on the cmpunlocker Discord that nobody has reproduced. None of them is a result. Each entry gives the claim, who made it and when (in the credit line), what would settle it, and the board card if there is one. Where another page already covers the claim with its sources, the entry is short and links there.

* {{Status|Theory}} on this page: a claim with no evidence posted and no second person.
* {{Status|Contested}}: people disagree. Both sides are listed in the order they were posted, with no verdict.
* To settle one, post the evidence on Discord with the card variant, driver and method, and move the card on the [https://cmp.wiki/board/ board]. A settled claim moves to the page it belongs on.

Firmware and VBIOS claims appear here only as claims. This wiki does not carry keys, decryption or ways around NVIDIA's firmware protection.

== Memory ==

=== 8 GB card at 80 or 96 GB ===
On 2026-10-09 @ob88594 posted a Xianyu listing photo of cards marked 80G and 96G, whose CUDA count matched 128 SMs. His informant said they were 8 GB cards; later he added that the card in the photo "has not been shipped" and that the third party only sells a 10 GB unlock. A vendor advert quoted by @analyticeth said the 8 GB modification was "still under development, with major breakthroughs already achieved". Nobody posted a card, a dump or a buyer. In the order posted:
* The informant says the marked cards are 8 GB cards. {{Source|handle=ob88594|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558079963129978955}} {{Source|handle=ob88594|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558084426003382275}} {{Source|handle=ob88594|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558114667325423759}}
* In theory an 8 GB card could go to 96 GB. {{Source|handle=wakeupmbrc1|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558172335633211645}}
* The vendor advert's line on the 8 GB card. {{Source|handle=analyticeth|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558168218487623782}}
* Without a signed VBIOS @globalapathy does not see how it would be possible. {{Source|handle=globalapathy|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558682168983818333}}
* @djpandaman: in theory 96 GB on some cards and 80 GB on most; the maximum confirmed on a production 8 GB card is 64 GB. {{Source|handle=djpandaman|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559044323545456671}}
'''What would settle it.''' An 8 GB card (<code><nowiki>10de:20c2</nowiki></code>) showing more than 65024 MiB in nvidia-smi and passing a dense unique-data write and read-back over all of it, with the method posted. 
'''Board.''' D-072 and D-056 (Dev and research), T-029 (CMP testing) on the [https://cmp.wiki/board/ board]. 
More: [[8 GB card#Memory]].

{{Status|Contested}} {{Cards|8 GB}}

=== A screenshot showing 130104 MB (192 GB) on one card ===
A screenshot in the "Unlock 80GB stable ram on 10G version" feature-request channel appeared to show 130104 MB of VRAM, which some read as 192 GB on one card. In the order posted:
* "i thought it was 192g". {{Source|handle=squishysquare|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1534858283138158697/1560151279618101299}}
* The per-stack arithmetic (25.6 or 21.3 GB per stack) makes no sense. {{Source|handle=squishysquare|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1534858283138158697/1560165956494557257}}
* "VRAM 130104 MB= 65024 MiB x2 = 2x 64GB unlocked 8GB model": two unlocked 8 GB cards reported together. {{Source|handle=kio063218|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1534858283138158697/1560618333542293526}}
* "Fake pic." {{Source|handle=reggie7756|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1534858283138158697/1561867918864814234}}
'''What would settle it.''' A single-GPU <code><nowiki>nvidia-smi -q</nowiki></code> from the card in question. For comparison, an unlocked 8 GB card reports 65024 MiB. 
'''Board.''' T-032 (CMP testing) on the [https://cmp.wiki/board/ board]. 
More: [[Memory unlock on the 10 GB card#80 / 96 GB: not real on these dies]].

{{Status|Contested}} {{Cards|both}}

=== 80 GB working on the 10 GB card ===
In the order posted:
* Miséricorde relayed community research that memory above 40 GB "reads and returns meaningful values". {{Source|handle=wakeupmbrc1|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559709514553622549}}
* Some people had cards reading 80 GB, but the memory was unstable. @djpandaman linked a Chinese write-up, "170Hx 10G解锁80G探索" (10G unlock to 80G, an exploration), at [https://blog.kkk.rs/archives/71 blog.kkk.rs]. {{Source|handle=tekkenz|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559048743947341955}} {{Source|handle=djpandaman|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559050324411420762}}
* @colo2442 gets folding (aliasing) in every experiment, including physical accesses that bypass L2, unless a further unlock frees address bit 14. He asked for the serial number of any card said to work above 40 GB. {{Source|handle=colo2442|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559906143373885462}}
* Miséricorde: the "no folding" statement came from community research, not his own tests. {{Source|handle=wakeupmbrc1|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559906356889387049}}
* @lycorascence recalled papers that got 80 GB working on a 10 GB card at lower memory speed; Miséricorde: "they actually were not"; @scallion_9883: "I believe it is aliasing in L2 now also". {{Source|handle=lycorascence|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560782124049760389}} {{Source|handle=wakeupmbrc1|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560782191628259379}} {{Source|handle=scallion_9883|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560782273652195479}}
* @ob88594: the "special initialization" the paper mentions is still missing for a full 10 GB unlock. {{Source|handle=ob88594|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564546224567361578}}
'''What would settle it.''' A dense unique-data write and read-back above 40 GiB on a named 10 GB card (serial posted), with no folding and no Xid. 
'''Board.''' T-026 and T-027 (CMP testing), D-055 (Dev and research) on the [https://cmp.wiki/board/ board]. 
More: [[Memory unlock on the 10 GB card#80 / 96 GB: not real on these dies]].

{{Status|Contested}} {{Cards|10 GB}}

=== 48 GB on most 10 GB cards ===
In the order posted:
* @cuddylac997 posted ten 10 GB cards in one host, "ready to run 48gb on each one of these!", and said a 48 GB mode had not been released "but it can be figured out". {{Source|handle=cuddylac997|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1556837488541311058}} {{Source|handle=cuddylac997|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1557230581346213909}}
* @djpandaman: "48 max on some. most cards 40. looking like around 20%". {{Source|handle=djpandaman|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559042465758060625}}
* Miséricorde listed "48g on some (most cards)" among what the 10 GB card can do. {{Source|handle=wakeupmbrc1|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559705158961864908}}
* @djpandaman: 6 of 30 cards he saw tested could do 48 GB. {{Source|handle=djpandaman|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560920383782260797}}
'''What would settle it.''' gpcprobe's FBP disable and defective readout plus the unlock result for each 10 GB card owners have. 
'''Board.''' T-004 (CMP testing), D-027 (Dev and research) on the [https://cmp.wiki/board/ board]. 
More: [[Memory unlock on the 10 GB card#48 GB (the 6th stack, if it is good)]].

{{Status|Contested}} {{Cards|10 GB}}

=== Unlocked 8 GB memory is failure-prone ===
In the order posted:
* "No amount of software can make up for the fact that this was lower binned and prone to failure memory that nvidia had to fuse off." {{Source|handle=_____josh_____|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556569848069357612}}
* @jjb01957: his card's VRAM runs fine and, apart from speed, no different from his 5090. {{Source|handle=jjb01957|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556571811884310612}}
* Miséricorde: "every card runs on ndiv=68 as minimum". {{Source|handle=wakeupmbrc1|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556575473343922237}}
'''What would settle it.''' Failure statistics: cards, hours in service, memtest error counts. 
'''Board.''' T-030 and T-115 (CMP testing) on the [https://cmp.wiki/board/ board]. 
More: [[8 GB card#Memory]].

{{Status|Contested}} {{Cards|8 GB}}

=== The "defective" HBM stacks are good memory ===
In the order posted:
* A theory @n2dcrypt relayed from another chat: the same stacks are always marked defective because the HBM package height was wrong and they run hotter, so they may not be faulty memory. @globalapathy: at lower voltage and under water they could work, just not optimally. {{Source|handle=n2dcrypt|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558184726261399553}} {{Source|handle=globalapathy|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558185847654842420}}
* Petri Krohn: "Almost every 8GB card has FBP 6 and FBP 11 marked as *defective*. This cannot be true!" He reads it as two stages of disabling. {{Source|handle=petrikrohn_26497|date=2026-10-10|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558302260088545361}}
* @djpandaman: in his experience a part marked defective is truly defective, while a disabled part can be enabled. {{Source|handle=djpandaman|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561028809237602389}}
* @lxtend on 10 GB stacks: "they are mostly good even its labeled as defective". {{Source|handle=lxtend|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562165620693274655}}
'''What would settle it.''' One marked-defective stack enabled and memtested, at reduced clocks if needed. On the 8 GB card nobody has a way to enable it. 
'''Board.''' T-029 and T-133 (CMP testing), D-056 (Dev and research) on the [https://cmp.wiki/board/ board]. 
More: [[8 GB card#Memory]], [[10 GB card#Memory]].

{{Status|Contested}} {{Cards|both}}

=== Most cards reach 1.9 to 2.0 TB/s with HBM tuning ===
@zorg33 believes most cards can reach 1.9 to 2.0 TB/s with HBM fine tuning (he wrote "TH/s"), which he says would scale TP4 decode to 550-600 tok/s. Miséricorde: a 10 GB card with all six stacks would have a 6144-bit bus and "can run 2.5tbps+". No tuned bandwidth figure at that level has been posted. The highest posted so far: 1,741 GB/s on an unlocked 10 GB card at stock, and the NDIV results on [[8 GB card#Memory]]. 
'''What would settle it.''' HBM bandwidth and gpu-burn correctness at NDIV 70 and 73 on several cards; bandwidth on a 48 GB 10 GB card. 
'''Board.''' T-143 and T-028 (CMP testing) on the [https://cmp.wiki/board/ board]. 
More: [[Undervolting and power limits#HBM clock (NDIV) and refresh]].

{{Status|Theory}} {{Cards|both}} 
{{Source|handle=zorg33|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1556935579919187989}} 
{{Source|handle=wakeupmbrc1|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557273045259919401}} 
{{Source|handle=cuddylac997|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1557370302042738759}}

=== "ECC Enabled" after v0.5 means errors are corrected ===
In the order posted:
* @zombielurker: nvidia-smi says ECC is enabled, even on his RTX 3090s, but it corrected none of about 5,000 single-bit errors one card throws in memtest_vulkan; gpu-burn behaved the same. {{Source|handle=zombielurker|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556515369286504489}}
* Lab notes: the "ECC Enabled" readout comes from cmpunlocker's reporting patch; no corrected-error counter has been shown moving. {{Source|handle=darkmaniac7|date=2026-10-21|note=lab notes}}
* @cute_sc2, arguing the 170HX is no different from an A30 or A100 for serving: "We even have ecc now." {{Source|handle=cute_sc2|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563235845409087609}}
'''What would settle it.''' One corrected DRAM error shown on a counter that is not set by the reporting patch. 
'''Board.''' T-001 (CMP testing), D-032 (Dev and research) on the [https://cmp.wiki/board/ board]. 
More: [[ECC#Does it correct errors? (contested)]].

{{Status|Contested}} {{Cards|both}}

== SM and clocks ==

=== The 8 GB card can go past 74 SMs ===
In the order posted:
* Miséricorde: every RIR entry except the last reads all ones on the 8 GB card, so it cannot be overridden "without signed falcon code". {{Source|handle=wakeupmbrc1|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557273300986765383}} {{Source|handle=wakeupmbrc1|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557273462647558188}}
* @sojun80: "thats just software looking at it and setting a flag in init". {{Source|handle=sojun80|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557273393814835203}}
* @matstatman installed an 8 GB card with 0 defective GPCs that passed the standard 5-minute test. Miséricorde: "if 0 defective then 128"; matstatman: "sooner or later, we will be able to enable them". {{Source|handle=matstatman|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558242733242720267}} {{Source|handle=wakeupmbrc1|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558244852561612811}} {{Source|handle=matstatman|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558245242472239157}}
* @mountains1605: the path is clear for 10 GB cards, not for 8 GB cards. {{Source|handle=mountains1605|date=2026-10-10|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558307001061089391}}
* @replacedriver47: fuses are read and passed on by software, so it is software-unlockable in theory, "but it would require bypassing security mechanisms". {{Source|handle=replacedriver47|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1564590115722895434}}
'''What would settle it.''' An 8 GB card (<code><nowiki>10de:20c2</nowiki></code>) running more than 74 SMs, with the method posted. 
'''Board.''' D-072 and D-084 (Dev and research) on the [https://cmp.wiki/board/ board]. 
More: [[Full SM unlock#Why the 8 GB card cannot go past 74]], [[8 GB card#Limits]].

{{Status|Contested}} {{Cards|8 GB}}

=== OpenGL on unlocked cards ("opengl with ecc") ===
Asked whether OpenGL is actually enabled on these cards, @matstatman said his coding agent had offered to enable it that day: "opengl with ecc, huang level". Nothing was shown afterwards. 
'''What would settle it.''' <code><nowiki>glxinfo</nowiki></code> output or an OpenGL program running on an unlocked 170HX, with driver and patch named. 
'''Board.''' T-021 (CMP testing), D-087 (Dev and research) on the [https://cmp.wiki/board/ board]. 
More: [[Other CMP cards and other NVIDIA GPUs]] (graphics on a 170HX).

{{Status|Theory}} {{Cards|both}} 
{{Source|handle=phoenixone7|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556811290419404862}} 
{{Source|handle=matstatman|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556811828364054529}} 
{{Source|handle=matstatman|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556811981405692056}}

=== RT cores unlocked ("It's done.") ===
The only message in the feature-request channel "Unlock RT cores for CMP cards that have them" is @emogop's "It's done." with no details, link or proof. It may mean the unlock was done or that the request was closed. 
'''What would settle it.''' emogop's explanation, or a ray-tracing workload with numbers on a CMP card. 
'''Board.''' T-022 (CMP testing) on the [https://cmp.wiki/board/ board].

{{Status|Theory}} {{Cards|both}} 
{{Source|handle=emogop|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1549439096072700094/1563775342114639989}}

== PCIe and P2P ==

=== PCIe Gen4 x16 and "A100 PRO" screenshots ===
Screenshots collected in [https://github.com/amoghmunikote/cmpunlocker/issues/9 cmpunlocker issue #9] show (a) a Chinese marketplace listing for an in-person "170hx to A100 PRO" hard-mod service in Chengdu, three cards minimum, 10 GB cards first, with a card reported as an A100-PCIE-40GB with 126 SMs, 40960 MiB, PCIe Gen4 x16 and ECC on; and (b) a tweet showing a card with 65536 MiB at PCIe Gen4 x16 and 300 W. Neither names a method, and no second person has seen such a card. In the order posted:
* @matstatman posted the tweet ("Oh no, more rumors"), then screenshots of screenshots and a further comment on issue #9. {{Source|handle=matstatman|date=2026-10-10|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558556627261595768}} {{Source|handle=matstatman|date=2026-10-10|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558561426619105280}} {{Source|handle=matstatman|date=2026-10-10|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558561741133062186}}
* @matstatman: "I think it is a case of old screenhots being mixed". {{Source|handle=matstatman|date=2026-10-10|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558559268741980282}}
* @port00: "Looks like 8GB version"; @dottoreargus: "and an account created today". {{Source|handle=port00|date=2026-10-10|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558578917068251157}} {{Source|handle=dottoreargus|date=2026-10-10|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558588174643494923}}
* The lab notes on issue #9: the listing renames the card's device ID, which the public tools do not do; the issue is still open. {{Source|handle=darkmaniac7|date=2026-10-18|note=lab notes}}
The Chengdu service may be the same as the paid 10 GB unlock below; nothing confirms it. 
'''What would settle it.''' <code><nowiki>lspci -vv</nowiki></code> showing <code><nowiki>LnkSta: Speed 16GT/s, Width x16</nowiki></code> on both ends for a card the poster owns, with the method named. 
'''Board.''' D-065 (Dev and research), T-005 (CMP testing) on the [https://cmp.wiki/board/ board].

{{Status|Contested}} {{Cards|both}}

=== PCIe 4.0, ECC, NVLink and twice the SMs on the 8 GB card ===
In the order posted:
* @endsjeremy: PCIe 4.0 was "pretty definitively off the table without some way to sign the driver". {{Source|handle=endsjeremy|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558697247439593475}}
* @ob88594: there are two separate "8G cracked" reports, a team in Chengdu and someone in this channel. {{Source|handle=ob88594|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558697827461238854}}
* @douya4305: "8g card can also unlock pcie4.0, ecc,nvlink" and "2X sm is on the road"; asked, "right ,just not public". {{Source|handle=douya4305|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559706643380445285}} {{Source|handle=douya4305|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559706873228304415}} {{Source|handle=douya4305|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559707094683361371}}
* Miséricorde: "no", "at least not public", "thats all really rumored". {{Source|handle=wakeupmbrc1|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559706884829880433}} {{Source|handle=wakeupmbrc1|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559707273058586697}}
* @lia_oc: ECC is done in v0.5; the others are not public. {{Source|handle=lia_oc|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559708664175263932}}
* @tarxlazer: "The 8g card of cmp170 unlocks the full core and pcie4. I hope it will come soon." {{Source|handle=tarxlazer|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559908881138982993}}
'''What would settle it.''' An 8 GB card with an 8 or 16 GT/s LnkSta, an active NVLink in <code><nowiki>nvidia-smi nvlink -s</nowiki></code>, or more than 74 SMs. 
'''Board.''' D-072 (Dev and research), T-011 (CMP testing) on the [https://cmp.wiki/board/ board]. 
More: [[8 GB card#Limits]].

{{Status|Contested}} {{Cards|8 GB}}

=== PCIe Gen3 on an 8 GB card, release promised for 2026-12-09 ===
@rrickk420 (Rickcal) said he sees three paths ("RIR, Samsung memory & falcon") and "I already have gen 3 8GB". He would not share it yet because he does not want to fry people's cards, and said he would release it on 2026-12-09 if nothing else came out by then. The next day he said only some cards can do single-fuse Gen3. The same week @djpandaman mentioned that someone said they had Gen3 on an 8 GB card. No numbers, LnkSta or method were posted. 
'''What would settle it.''' The release, or <code><nowiki>lspci -vv</nowiki></code> showing 8 GT/s on an 8 GB card. 
'''Board.''' D-059 (Dev and research) on the [https://cmp.wiki/board/ board]. 
More: [[8 GB card#Limits]] (what the fuse readouts show).

{{Status|Theory}} {{Cards|8 GB}} 
{{Source|handle=rrickk420|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558121601181163732}} 
{{Source|handle=rrickk420|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558122896143155303}} 
{{Source|handle=rrickk420|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558123540425736354}} 
{{Source|handle=djpandaman|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558265701947416597}} 
{{Source|handle=rrickk420|date=2026-10-10|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558607148727017485}}

=== PCIe Gen4 on the 10 GB card ===
@arabus_74064 posted a screenshot of a 170HX at PCIe x16 4.0; @bigptoughneigh said it was a 10 GB card with "All the RiR" done. @djpandaman said he has Gen3 and "validated gen 4 on my plx" (his motherboard is Gen3). @cute_sc2 answered yes when asked whether the 10 GB card can use PCIe 4. Gen3 on the 10 GB card is published and reproduced; Gen4 is not: no 16 GT/s LnkSta and no recipe has been posted. @lxtend has Gen3 confirmed, says Gen4 needs "some tricky way to retrain", and has no Gen4 slot to test it. 
'''What would settle it.''' <code><nowiki>lspci -vv</nowiki></code> showing 16 GT/s x16 on a cap-modded 10 GB card in a Gen4 slot, plus a bandwidth test. 
'''Board.''' T-005 and T-118 (CMP testing), D-028 (Dev and research) on the [https://cmp.wiki/board/ board]. 
More: [[10 GB card#PCIe]], [[PCIe Gen3 on the 10 GB card]].

{{Status|Theory}} {{Cards|10 GB}} 
{{Source|handle=arabus_74064|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556807631165726720}} 
{{Source|handle=bigptoughneigh|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556833016741896336}} 
{{Source|handle=djpandaman|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558112557628133498}} 
{{Source|handle=lxtend|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560186430628831343}} 
{{Source|handle=cute_sc2|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1560422460568899615}}

=== PCIe 5.0 on the 170HX ===
In the order posted:
* The author of the CMP 100-210 unlock repository claimed PCIe 5.0 on the 170HX in a [https://github.com/amoghmunikote/cmpunlocker/issues/9#issuecomment-5607224444 comment on cmpunlocker issue #9]; @68x0 pointed to it: "I wouldn't trust any of this AI slop from this person". {{Source|handle=68x0|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558131626922344510}}
* Amogh (@_j3ns), the cmpunlocker author: "Exactly why I banned them!" {{Source|handle=_j3ns|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558136539966611477}}
'''What would settle it.''' <code><nowiki>lspci -vv</nowiki></code> showing a 32 GT/s link on a 170HX. Nobody has posted one. 
More: [[Other CMP cards and other NVIDIA GPUs#CMP 100HX (100-210)]].

{{Status|Contested}} {{Cards|both}}

=== NVLink working on a 170HX ===
@djpandaman said on 2026-10-12 he was still getting NVLink to work on his 10 GB cards and "it looks like it will". The paid 10 GB unlock was offered with "nvlink for extra" (see below). On 2026-10-23 @bigptoughneigh said NVLink "works fine, but requires a very simple hardware mod (easier than the x16 mod). It's not my finding to share though." No <code><nowiki>nvidia-smi nvlink</nowiki></code> output, photo or method has been posted. @lia_oc (2026-10-22): no NVLink yet, "not even for 10GB that's public"; @ob88594 (2026-10-24): "8G still hasn't been unlocked". 
'''What would settle it.''' <code><nowiki>nvidia-smi nvlink -s</nowiki></code> showing active links on a bridged pair and a P2P bandwidth test over the bridge. 
'''Board.''' D-025 and D-026 (Dev and research), T-011 (CMP testing) on the [https://cmp.wiki/board/ board]. 
More: [[NVLink#Status of the hardware mod]].

{{Status|Theory}} {{Cards|both}} 
{{Source|handle=djpandaman|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1559037159841988619}} 
{{Source|handle=lia_oc|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562930961207922811}} 
{{Source|handle=bigptoughneigh|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1563312993414946827}} 
{{Source|handle=ob88594|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1563650116756447233}}

== Firmware and VBIOS ==

=== Paid 10 GB unlock for about 500 USD in Chengdu ===
Relaying an informant, @ob88594 said a third party sells a paid 10 GB unlock: "$500, get more than A100 40G PCIE, nvlink for extra", in Chengdu. @aaasss1456 said a friend "went to the factory and made a 10g card", that it "displays as an a100" with "8912 cuda core" (a full 128-SM GA100 has 8192), and that it cost nearly 500 USD. @analyticeth quoted the vendor's advert: all changes are permanent inside the card, no unlock software or driver patches are needed, and the card behaves like an original A100. Miséricorde read it as an RIR macro burn. No buyer has posted <code><nowiki>lspci</nowiki></code>, <code><nowiki>nvidia-smi -q</nowiki></code> or a fuse dump from such a card. 
'''What would settle it.''' A buyer posting <code><nowiki>lspci -nn</nowiki></code>, <code><nowiki>nvidia-smi -q</nowiki></code> and a gpcprobe dump of a card that went through the service. 
'''Board.''' D-065 (Dev and research) on the [https://cmp.wiki/board/ board]. 
More: [[10 GB card#Buying]].

{{Status|Theory}} {{Cards|10 GB}} 
{{Source|handle=ob88594|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558116548130906113}} 
{{Source|handle=ob88594|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558162519070216295}} 
{{Source|handle=aaasss1456|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558164230073753630}} 
{{Source|handle=aaasss1456|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558164394951573627}} 
{{Source|handle=analyticeth|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558168182563545140}} 
{{Source|handle=wakeupmbrc1|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558168562542317812}} 
{{Source|handle=aaasss1456|date=2026-10-10|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558296445835026556}} 
{{Source|handle=aaasss1456|date=2026-10-10|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558296562550177795}}

=== Unlocks sold as a service, with cards as payment ===
@ob88594's account of the Chinese market: merchants pay unlockers in cards ("The fewer you break, the higher your reward"), then sell unlocking as a service. The unlock merchants on Xianyu took their service down after someone bought out the capacity, and the 10 GB unlock had circulated since early August among merchants who bought the information, which he says is why unknown buyers took the 10 GB cards. Only his informant photographed an "80G version", and the unlocker gave no details. For the 8 GB card there was "no public information" from the Chinese side. 
'''What would settle it.''' A listing, receipt or buyer report for the service. 
'''Board.''' D-065 (Dev and research) on the [https://cmp.wiki/board/ board].

{{Status|Theory}} {{Cards|10 GB}} 
{{Source|handle=ob88594|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1559044923804745809}} 
{{Source|handle=ob88594|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1559045338587865239}} 
{{Source|handle=ob88594|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1559045761071714396}} 
{{Source|handle=ob88594|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1559047009523081310}} 
{{Source|handle=ob88594|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1559188709918900286}}

=== 20 donor cards, 5 bricked during the 10 GB work ===
In the order posted:
* @ob88594, marked as hearsay: private groups get free hardware from merchants in exchange for early information; "the 10G unlock came about because a merchant gave them 20 cards; 5 were bricked during testing". {{Source|handle=ob88594|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558091916409839727}}
* Miséricorde relayed it in #hardware and guessed they tried enabling defective blocks or stacks. {{Source|handle=wakeupmbrc1|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558111527498686525}} {{Source|handle=wakeupmbrc1|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558111592527175701}}
* @djpandaman does not see how a cold reset would not recover a card: his sixth-stack errors that day always cleared on a cold boot. He agreed that doing unlocks one at a time through RIR can get you into trouble. {{Source|handle=djpandaman|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558111882181611665}} {{Source|handle=djpandaman|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558111963199053878}}
'''What would settle it.''' One of the bricked cards, with what was written to it. 
'''Board.''' T-024 and T-036 (CMP testing) on the [https://cmp.wiki/board/ board]. 
More: [[Driver and unlock failures#Bricked cards during 10 GB development (hearsay)]], [[RIR fuse burn]].

{{Status|Contested}} {{Cards|10 GB}}

=== A private unlock from "a guy with 400 cards" ===
On 2026-10-17, while the channel discussed whether anyone has NVIDIA's signing keys, Miséricorde said a private unlock result he had seen came from "guy with 400 cards" who "doesnt sell", and that "either tool is real or someone got the keys". The regulars answered that nobody on the server has them. @djpandaman: "be cautious, it's easier to fake a screenshot when there's money on the table than to do it legitimately." Which card and what result were not posted. 
'''What would settle it.''' The tool, or its result on a second owner's card. 
'''Board.''' D-065 (Dev and research) on the [https://cmp.wiki/board/ board].

{{Status|Theory}} {{Cards|both}} 
{{Source|handle=wakeupmbrc1|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561027185760805055}} 
{{Source|handle=wakeupmbrc1|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561027322071748679}} 
{{Source|handle=wakeupmbrc1|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561027370603905046}} 
{{Source|handle=djpandaman|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561027460177334314}} 
{{Source|handle=djpandaman|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561027717825036463}}

=== An earlier private "dirty" unlock under NDA ===
@zingy90210 (PJ) said a talk Petri Krohn gave covered NVIDIA's firmware signing, that "Petri, Jon and 3 others managed to do 'dirty' work and unlock it. Think NVIDIA made jon sign an NDA", and that they are now trying to turn their process into a clean unlock. He gave no link to the talk, and nobody corroborated it. Petri Krohn is on the server and can be asked directly. 
'''What would settle it.''' A link to the talk, or Petri Krohn's own account. 
'''Board.''' D-065 (Dev and research) on the [https://cmp.wiki/board/ board].

{{Status|Theory}} {{Cards|both}} 
{{Source|handle=zingy90210|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561265184918474953}} 
{{Source|handle=zingy90210|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561265407153938543}} 
{{Source|handle=zingy90210|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561265556248854569}}

=== A local model re-derived the v0.5 patch ===
In the order posted:
* @exile_1ck: when he asked Claude to install v0.5, it found that his local Qwen 3.8 Flash Next, told to reverse engineer the BIOS with [https://github.com/morluto/rea morluto/rea], had produced the same patch the day before. He added that the model also made Strata faster than he had seen it run unmodified. {{Source|handle=exile_1ck|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557239693043699736}} {{Source|handle=exile_1ck|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557239965161619547}} {{Source|handle=exile_1ck|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557240827267387422}}
* @djpandaman: "did it actually unlock it from scratch or did it just use the ecc branch before it was merged to master branch". eXile: "i am not entirely sure". {{Source|handle=djpandaman|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557240393169379330}} {{Source|handle=exile_1ck|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557240683666866237}}
'''What would settle it.''' The model's diff and session log, compared with the upstream ECC branch. 
'''Board.''' D-066 (Dev and research) on the [https://cmp.wiki/board/ board].

{{Status|Contested}} {{Cards|10 GB}}

=== Unlocks have permanent effects ===
@rrickk420 said on 2026-10-09 that since June his theory has been that someone would "sneak in brick fuse burns" into an unlock. On 2026-10-25 @stcord posted an X post by unixpickle with "Question everything, folks"; @segmond then said he would not unlock anything more until he is sure there are no permanent effects. The post's content is not in the Discord export. For context, the [[Driver unlock]] page states that cmpunlocker flashes and burns nothing, while the [[RIR fuse burn]] on 10 GB cards is permanent by design. 
'''What would settle it.''' The post's actual claim, or a fuse dump taken before and after a plain cmpunlocker install and a cold boot. 
'''Board.''' D-115 (Dev and research) on the [https://cmp.wiki/board/ board].

{{Status|Theory}} {{Cards|both}} 
{{Source|handle=rrickk420|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558124756312653966}} 
{{Source|handle=stcord|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1564038044032434186}} 
{{Source|handle=segmond|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1564044324793221302}}

=== A VBIOS TOCTOU test damaged a card for good ===
@youngju10000 (영쥬) wrote that he "saw in a post" that a VBIOS TOCTOU test caused permanent damage that restoring the original BIOS did not fix. The post was not linked and has not been found in the export. 
'''What would settle it.''' The original post. 
More: [[VBIOS and firmware]].

{{Status|Theory}} {{Cards|both}} 
{{Source|handle=youngju10000|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557647494417088513}}

=== An unlocked VBIOS for the 10 GB card ===
In the order posted:
* @supasnipa360: "hearing its been done for the 10gb variant as well but a harder find it seems due to legal concerns". {{Source|handle=supasnipa360|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561388811123167233}}
* @xanthefin: the unlock makes no VBIOS change in the first place. @globalapathy: someone able to write a VBIOS would not have stopped at 64 GB. {{Source|handle=xanthefin|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561391210906517565}} {{Source|handle=globalapathy|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561391800818733068}}
'''What would settle it.''' The file, compared with the stock 10 GB VBIOS (92.00.66.00.02). 
More: [[VBIOS and firmware#The "64 GB unlocked VBIOS" repos (bogus)]].

{{Status|Contested}} {{Cards|10 GB}}

=== Why driver-loaded VBIOS overrides work (Petri Krohn's explanation) ===
Petri Krohn posted "Ampere VBIOS modding explained", an account of why the driver can hand the GPU's microcontrollers modified VBIOS data. It is an explanation, not a measurement, and nobody has checked it against a dump. 
'''What would settle it.''' A dump that confirms or corrects it. 
'''Board.''' T-016 (CMP testing), D-060 (Dev and research) on the [https://cmp.wiki/board/ board]. 
More: [[VBIOS and firmware#Background: why driver-loaded overrides work (Petri Krohn)]].

{{Status|Theory}} {{Cards|both}} 
{{Source|handle=petrikrohn_26497|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562075696380248065}}

=== A complete 10 GB unlock exists privately ===
On 2026-10-07 Miséricorde said the 10 GB card "can be unlocked into full ga100": 128 SMs, 48 GB, six-stack bandwidth, "nvlink and 4.0 also"; 40 to 48 GB is "legit", 80 GB a "big maybe". The same day @cuddylac997 posted overnight tests of unlocked 10 GB cards, measured 1,741 GB/s, and said "There's no releasing it" and "not every card unlocks the same or in the same way". Since then the 128-SM unlock and Gen3 on the 10 GB card have been published and reproduced (see [[Full SM unlock]] and [[PCIe Gen3 on the 10 GB card]]). The NVLink and PCIe 4.0 parts of the claim have not been shown. 
'''What would settle it.''' See the Gen4 and NVLink entries above. 
'''Board.''' D-073, D-025 and D-028 (Dev and research) on the [https://cmp.wiki/board/ board].

{{Status|Theory}} {{Cards|10 GB}} 
{{Source|handle=wakeupmbrc1|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557244521992163329}} 
{{Source|handle=wakeupmbrc1|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557244574802513951}} 
{{Source|handle=wakeupmbrc1|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557244637893230603}} 
{{Source|handle=wakeupmbrc1|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557244790720962611}} 
{{Source|handle=cuddylac997|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1557367784130875396}} 
{{Source|handle=cuddylac997|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1557368521179275275}} 
{{Source|handle=cuddylac997|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1557461273518547055}}

== Cooling and power ==

=== The 300 W VBIOS burned a card ===
Asked about running the 300 W VBIOS, @xanthefin said a picture of a burned 170HX had already been posted on the Discord, and, from memory, that the PCB is missing power-delivery parts. The picture has not been found in the export. The 300 W VBIOS exists for the 8 GB card only. 
'''What would settle it.''' The original picture and post, with the card's VBIOS and power setup. 
'''Board.''' D-090 (Dev and research) on the [https://cmp.wiki/board/ board]. 
More: [[Power and cabling warnings#The 300 W VBIOS has burned a 170HX]].

{{Status|Theory}} {{Cards|8 GB}} 
{{Source|handle=xanthefin|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561336153515364444}} 
{{Source|handle=xanthefin|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561336277280759879}}

=== An unreleased "high power mode" ===
@matstatman: "I found a high power mode that you can enable, even on 8gb. No idea what it does so will not release." Nothing more has been posted. 
'''What would settle it.''' matstatman's description of the setting and a measurement with it on and off. 
'''Board.''' D-090 (Dev and research) on the [https://cmp.wiki/board/ board]. 
More: [[8 GB card#Limits]], [[Undervolting and power limits]].

{{Status|Theory}} {{Cards|both}} 
{{Source|handle=matstatman|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562174089920258139}}

=== Arctic fans wired onto the stock shroud are quieter ===
@danske1 has heard of people wiring Arctic fans onto the card and that "it's much quieter", but does not know what the wiring involves or how the temperatures compare. Nobody has posted a build. 
'''What would settle it.''' Noise and core and HBM temperatures at a fixed power limit, before and after. 
'''Board.''' T-048 (CMP testing) on the [https://cmp.wiki/board/ board]. 
More: [[Fans and ducts]].

{{Status|Theory}} {{Cards|both}} 
{{Source|handle=danske1|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564217476542365770}} 
{{Source|handle=danske1|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564224983301881968}}

== Recipes and speed ==

=== 4.5M tokens of KV cache for GLM-5.3-Flash on 4 cards ===
In the order posted:
* Miséricorde: "with 4 gpus you have w4a16 + 4.5m kv". {{Source|handle=wakeupmbrc1|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1560673558122987571}}
* @cibernox, running the 4-card recipe daily: "I only have 1.2M". {{Source|handle=cibernox|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1560682309978427494}}
'''What would settle it.''' The vLLM startup line together with KV dtype, layout and maximum sequence count. 
'''Board.''' T-069 (CMP testing) on the [https://cmp.wiki/board/ board]. 
More: [[GLM 5.3 Flash on 4x 8 GB#KV cache and context]].

{{Status|Contested}} {{Cards|8 GB}}

=== 225 tok/s on Qwen 3.8 27B with one card ===
In the order posted:
* @feralzi: "I was able to reach 225 tks on 3.8 27b". {{Source|handle=feralzi|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559796537935142963}}
* @matstatman: "Its dflash and temp set to 0 i think, nothing you want to code with". {{Source|handle=matstatman|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559942424833429586}}
'''What would settle it.''' The same run with and without the draft model, at temperature 0 and at a normal temperature. 
'''Board.''' T-158 and T-034 (CMP testing) on the [https://cmp.wiki/board/ board]. 
More: [[Qwen3.8 27B on 1x 8 GB (W4A16 vLLM)#Measured numbers]].

{{Status|Contested}} {{Cards|8 GB}}

=== Single-card Qwen 3.8 Flash Next numbers on a custom vLLM build ===
In the order posted:
* @exile_1ck posted screenshots of a single 64 GB card running a Q3 quant of Qwen 3.8 Flash Next on a "custom vllm build aimed at the 170hx". {{Source|handle=exile_1ck|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560340926998515827}} {{Source|handle=exile_1ck|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560342257532674060}}
* @xtj7 gets about 90 tok/s decode and 1600 tok/s prefill with Strata on one card at IQ2 without the x16 mod, called eXile's prefill "awfully high" and wondered whether it includes cache hits. @okrasit. asked whether the prefill was reported correctly, @shudza asked for the context size. No answers were posted. {{Source|handle=xtj7|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560350518847479850}} {{Source|handle=okrasit.|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560352574673260585}} {{Source|handle=xtj7|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560352992035868753}} {{Source|handle=shudza|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560371927141326909}}
'''What would settle it.''' The numbers with context size, system RAM and cache hits stated, and the build published. 
'''Board.''' T-077 (CMP testing) on the [https://cmp.wiki/board/ board].

{{Status|Contested}} {{Cards|8 GB}}

=== v0.5 decodes slower than v0.4 ===
In the order posted:
* @reala7096: ECC has no effect on bandwidth. @matstatman: random one-byte writes would suffer. {{Source|handle=reala7096|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556767677866049579}} {{Source|handle=matstatman|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556768044410343445}}
* @mowgli8628: after reinstalling with v0.5 he "can't get past 35 t/s with qwen 3.8 27b", against 60-80 on v0.4, and asks whether ECC is the cause. {{Source|handle=mowgli8628|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561450305529581640}}
'''What would settle it.''' The same model and settings on v0.4 and v0.5, with ECC on and off, on one card. 
'''Board.''' T-003 (CMP testing) on the [https://cmp.wiki/board/ board]. 
More: [[Driver and unlock failures#Performance changed after an update]].

{{Status|Contested}} {{Cards|8 GB}}

=== Broadwell CPUs halve the Qwen Flash recipe numbers ===
In the order posted:
* @segmond reached nowhere near Morrowmake's GLM numbers and put it down to missing x16 links and TP. {{Source|handle=segmond|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1561950054254645291}}
* @nathang6866 (ElectroHobo) got about half of Morrowmake's numbers on the Qwen Flash recipe: "It seems the Broadwell processors cause issues with certain Qwen Flash recipes." {{Source|handle=nathang6866|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1561951080882114701}}
'''What would settle it.''' The same recipe on a Broadwell host and a newer host with the same cards, links and P2P setting. 
'''Board.''' T-065 (CMP testing) on the [https://cmp.wiki/board/ board]. 
More: [[Platforms#Host CPU and RAM]].

{{Status|Contested}} {{Cards|8 GB}}

== Buying ==

=== One card earns up to 7,000 USD a year ===
In the order posted:
* @cute_sc2: "a single cmp 170hx can now earn up to 7k a year in profit alone, you only need to know how", through long-term rental contracts with cheap energy, Pearl mining or serving AI. {{Source|handle=cute_sc2|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563191373841170453}} {{Source|handle=cute_sc2|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563234262038347830}}
* @kellertreppe123: that is a service business, not the card's hardware value, and businesses would rather trust a cloud provider with a track record. {{Source|handle=kellertreppe123|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563235068573655140}} {{Source|handle=kellertreppe123|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563242677926101014}}
'''What would settle it.''' An owner's income and costs per card over several months. 
More: [[Price history and market]].

{{Status|Contested}} {{Cards|both}}

=== Half of all cards are bad ===
In the order posted:
* @_____josh_____: "the cards have a 50% failure rate". {{Source|handle=_____josh_____|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557666958608957521}}
* @lia_oc: "It's nowhere near that high for sure". {{Source|handle=lia_oc|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557693615038275648}}
* @c133 tested five cards, all good; @bigfoot1144 bought 12, all unlock. {{Source|handle=c133|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557769336930967614}} {{Source|handle=bigfoot1144|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557785453850140733}}
* @_____josh_____: the good stock sold earlier and sellers now mix lemons into each shipment. {{Source|handle=_____josh_____|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557793719309308017}}
'''What would settle it.''' A structured survey: cards bought, source, unlock result, HBM error count, tensor-core check. 
'''Board.''' T-115 (CMP testing) on the [https://cmp.wiki/board/ board]. 
More: [[Buying#How often cards are bad]].

{{Status|Contested}} {{Cards|both}}

=== The vouches for Alifond are bot accounts ===
In the order posted:
* @kellertreppe123: Alifond (Huateng) is vouched for by several members here. {{Source|handle=kellertreppe123|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556319764480131215}}
* @_____josh_____: "The multiple guys are their own bot accounts. Don't fall for it." @djpandaman: "this is true tho". {{Source|handle=_____josh_____|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556346381860474891}} {{Source|handle=djpandaman|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556346522562465864}}
'''What would settle it.''' Order reports from long-standing members, with dates and what arrived. 
More: [[Buying#Alifond]].

{{Status|Contested}} {{Cards|both}}

=== Listings promising PCIe 4.0, NVLink, ECC and 80 GB ===
In the order posted:
* An eBay listing showed a 170HX with PCIe 4.0. @con3po7016: "false alarm"; @spectakkular: "PCIe 4.0 is a listing mistake from before the cards were cracked. It's just eBay autofilling listing information". {{Source|handle=con3po7016|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558699238312116325}} {{Source|handle=spectakkular|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558743009380671579}}
* @tugoubxs found a seller whose description promised ECC, PCIe 4.0, NVLink and 80 GB. {{Source|handle=tugoubxs|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559792760477712456}} {{Source|handle=tugoubxs|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559795404076355676}}
* A seller's screenshot read as PCIe Gen4 x16 by @galygious2; @xeax: the field shows x1 Gen1 at idle. {{Source|handle=galygious2|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561264068508262462}} {{Source|handle=xeax|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561265565736370219}}
'''What would settle it.''' Nothing in a listing counts; check the card on arrival. 
More: [[Buying#Scam patterns]], [[Acceptance checklist]].

{{Status|Contested}} {{Cards|both}}

=== Die transplants and cards with no chips ===
@civiloid recalled reports of used-market cards "with no chips", and of a CMP that turned out to carry a die transplanted from the 32 GB A100 variant. No photo or link to the original reports was posted. 
'''What would settle it.''' The original reports or photos. 
More: [[Which card do I have]], [[Buying]].

{{Status|Theory}} {{Cards|both}} 
{{Source|handle=civiloid|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559466233009676352}} 
{{Source|handle=civiloid|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559466533091016737}}

=== A new finding is behind the late-October price jump ===
In the order posted:
* Miséricorde: "seems like someone found something"; a card he bought at 2,380 USD in the CIS market cost him 3,600+ on arrival. {{Source|handle=wakeupmbrc1|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562704071863959565}} {{Source|handle=wakeupmbrc1|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562706859755053077}}
* @ob88594: "No, what I know is that Russians are aggressively purchasing the 8G version in China"; bulk lots of 10 cost 20% more than the regular price. {{Source|handle=ob88594|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562727070851801112}} {{Source|handle=ob88594|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562727235771699293}}
'''What would settle it.''' A published unlock that explains the jump; otherwise it stays a market question. 
More: [[Price history and market]].

{{Status|Contested}} {{Cards|8 GB}}

=== At least 130,000 8 GB cards exist ===
@spectakkular: "there seems to be at least 130,000 of the 8G around the world". No source for the figure was given. 
'''What would settle it.''' A shipment or production figure with a source.

{{Status|Theory}} {{Cards|8 GB}} 
{{Source|handle=spectakkular|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556599044355137557}}

== See also ==
[[Buying]], [[Price history and market]], [[Other CMP cards and other NVIDIA GPUs]], [[8 GB card]], [[10 GB card]], [[Which card do I have]], [[VBIOS and firmware]], [[Status taxonomy]], [[Board how-to]].

{{ImportFooter}}
[[Category:Help]]

Recipes

2026-10-31T21:34:48Z

ImportBot: Import: Recipes overview from the recipes lane: card-count guide, table of recipe pages, choosing a model, engine and layout; Discord (clanker-talk, general, testing, development, hardware), 33 GitHub repos and lab notes; gap-fill from #general 2026-10-23 to 10-26: @wakeupmbrc1, @phoenixone7, @con3po7016, @segmond, @amishrakefightr, @c133, @feralzi, @_orrorin, @zingy90210

A recipe is a model running on CMP 170HX cards with the exact settings and the numbers that came out. Each recipe page
has an infobox (model, quant, engine, cards, topology, tok/s, power, status), the steps, the measured numbers with
their conditions, known issues and credits. [[All recipes]] lists every recipe page as a sortable table.

{{#forminput:form=Recipe|size=50|placeholder=Page name, e.g. Qwen3-32B AWQ on vLLM, 4x 10 GB|button text=Add a recipe|autocomplete on category=Recipes}}

How to read the numbers: unless a page says otherwise, the infobox '''decode''' is one user on code, and '''prefill''' is
a cold prompt read. Most recipe authors use the MiaAI-Lab protocol (400-token answers, temperature 0, thinking off) and
report three columns, structured / code / prose; code is usually the middle one and prose the slowest. Numbers from
different protocols, power caps (140 to 250 W) and link widths (x4 or x16) are not directly comparable. Every number with
its setup is on [[Benchmarks]].

Almost everything here runs on the '''8 GB card unlocked to 64 GB''' with the 74-SM unlock (see [[8 GB card]] and
[[Driver unlock]]). No recipe has been published for the 10 GB card yet; see the variant section below.

== Quick picks by card count ==
{| class="wikitable"
! Cards !! Model !! Recipe !! One user (code) !! Notes
|-
| 1 || Qwen3.8 Flash Next || [[Qwen3.8 Flash Next on 1x 8 GB (ElectroHobo 3 bpw)]] || 296 tok/s || needs 96 GB host RAM (or HMM disk mode) and an x16 card; the community's go-to for one card
|-
| 1 || Qwen3.8 Flash Next || [[Qwen3.8 Flash Next on 1x 8 GB (iIIusi0n SSD PLE)]] || 111 tok/s || runs with 15 GiB host RAM; PLE table on SSD; confirmed
|-
| 1 || Qwen3.8 27B (dense) || [[Qwen3.8 27B on 1x 8 GB (W4A16 vLLM)]] || about 170 tok/s || reported, one run (a second run only partly matches)
|-
| 2 || Qwen3.8 Flash Next || [[Qwen3.8 Flash Next on 2x 8 GB (ElectroHobo W4A16 TP2)]] || 350 tok/s || x16 + P2P; up to 128 users; confirmed in the lab
|-
| 2 || Qwen3.8 Flash Next || [[Qwen3.8 Flash Next on 2x 8 GB (mannydelrio PP2)]] || 178 tok/s || stock x4 cards, no P2P, 16 GB host RAM; fastest prompt reading (7,006 tok/s)
|-
| 2 || GLM 5.3 Flash || [[GLM 5.3 Flash on 2x 8 GB (ExLlamaV3 TP2)]] || 108 tok/s || everything in HBM, 393K context, one or two requests at a time
|-
| 3 || Qwen3.8 Flash Next || [[Qwen3.8 Flash Next on 3x 8 GB (clee PP3)]] || 74 tok/s || unmodded x4 cards, 1M context, 7.36M KV; confirmed
|-
| 2 || Qwen3.8 Flash Next || [[Qwen3.8 Flash Next on 2x 8 GB (Plean PP2)]] || 197 tok/s (predictable output) || no P2P, BF16 PLE table on NVMe, 6 concurrent at 256K
|-
| 3 || GLM 5.3 Flash || [[GLM 5.3 Flash on 3x 8 GB]] || not posted || Morrowmake's recipe at PP3 with an 8-bit KV cache
|-
| 4 || GLM 5.3 Flash || [[GLM 5.3 Flash on 4x 8 GB]] || 442 tok/s || the community daily driver; confirmed
|-
| 4 || DeepSeek V4.1 Flash || [[DeepSeek V4.1 Flash on 4x 8 GB (Morrowmake)]] || up to 287 tok/s || about 240 GiB host RAM and 680 GiB disk; second runs only partly match
|-
| 4 || DeepSeek V4.1 Flash || [[DeepSeek V4.1 Flash on 4x 8 GB (GNmac)]] || 258 tok/s || less RAM (Engram on NVMe); confirmed; see its long-context copy issue
|-
| 4 || Qwen3.8 Flash Next || [[Qwen3.8 Flash Next on 4x 8 GB]] || 116 tok/s || one compose file, 32 GB host RAM, 1M context
|-
| 4 || MiMo V2.6 Flash || [[MiMo V2.6 Flash on 4x 8 GB]] || 275 tok/s || 1M context, image input
|-
| 6 || DeepSeek V4.1 Flash (full checkpoint) || [[DeepSeek V4.1 Flash on 6x 8 GB (Deepinfer-SM80 TP2 x PP3)]] || 161 tok/s || native precision, 4.6M KV
|-
| 8 || DeepSeek V4.1 Flash (full checkpoint) || [[DeepSeek V4.1 Flash on 8x 8 GB (Zanooda PP8)]] || 117 tok/s || best prefill (about 6k tok/s), 6.2M KV, 1M context
|-
| 8 || GLM 5.3 (full) || [[GLM 5.3 on 8x 8 GB (vllm-170hx-glm5)]] || 49 tok/s || 8 to 10 cards, 1M context; confirmed
|-
| 8 || GLM 5.3 Flash, two instances || [[GLM 5.3 Flash on 4x 8 GB#Eight cards]] || || about 1,600 tok/s aggregate
|}
"Confirmed" means the page has a confirmation by a second person at import time; the badge on each page is authoritative.

== All recipe pages ==
{| class="wikitable sortable"
! Model !! Cards !! Engine !! Page
|-
| GLM 5.3 Flash || 4 || Morrowmake vLLM fork, W4A16 || [[GLM 5.3 Flash on 4x 8 GB]]
|-
| GLM 5.3 Flash || 3 || Morrowmake vLLM fork, W4A16 PP3 || [[GLM 5.3 Flash on 3x 8 GB]]
|-
| GLM 5.3 Flash || 2 || ExLlamaV3 TP2, EXL3 3.05 bpw || [[GLM 5.3 Flash on 2x 8 GB (ExLlamaV3 TP2)]]
|-
| GLM 5.3 Flash || 2 || ExLlamaV3 layer split, EXL3 3.05 bpw || [[GLM 5.3 Flash on 2x 8 GB (ExLlamaV3 layer split)]]
|-
| GLM 5.3 Flash || 2 || Project Maya, GGUF || [[GLM 5.3 Flash on 2x 8 GB (Project Maya)]]
|-
| GLM 5.3 (full) || 8 to 10 || Morrowmake ampere-glm53 + patches, PP8 || [[GLM 5.3 on 8x 8 GB (vllm-170hx-glm5)]]
|-
| GLM 5.3 (full) || 8 || vLLM PP8, Int4-Int8Mix || [[GLM 5.3 on 8x 8 GB (Int4-Int8Mix PP8)]]
|-
| DeepSeek V4.1 Flash || 4 || Morrowmake vLLM fork, EXL3 experts || [[DeepSeek V4.1 Flash on 4x 8 GB (Morrowmake)]]
|-
| DeepSeek V4.1 Flash heretic || 4 || Morrowmake vLLM fork + in-place abliteration patch || [[DeepSeek V4.1 Flash heretic on 4x 8 GB]]
|-
| DeepSeek V4.1 Flash || 4 || vLLM + sm_80 patch stack (GNmac) || [[DeepSeek V4.1 Flash on 4x 8 GB (GNmac)]]
|-
| DeepSeek V4.1 Flash || 4 || GNmac + fidelity patches || [[DeepSeek V4.1 Flash on 4x 8 GB (alanoo fidelity build)]]
|-
| DeepSeek V4.1 Flash || 4 || Morrowmake engine + TC-MoE kernels || [[DeepSeek V4.1 Flash on 4x 8 GB (CurtisAccelerate TC-MoE)]]
|-
| DeepSeek V4.1 Flash || 4 + RTX PRO 6000 || ExLlamaV3 + TabbyAPI TP5 || [[DeepSeek V4.1 Flash on 4x 8 GB plus RTX PRO 6000 (ExLlamaV3 TP5)]]
|-
| DeepSeek V4.1 Flash || 6 || custom SM80 vLLM, TP6 || [[DeepSeek V4.1 Flash on 6x 8 GB (TP6)]]
|-
| DeepSeek V4.1 Flash || 6 || Deepinfer-SM80, TP2 x PP3 || [[DeepSeek V4.1 Flash on 6x 8 GB (Deepinfer-SM80 TP2 x PP3)]]
|-
| DeepSeek V4.1 Flash || 8 || Deepinfer-SM80, TP4 x PP2 || [[DeepSeek V4.1 Flash on 8x 8 GB (Deepinfer-SM80 TP4 x PP2)]]
|-
| DeepSeek V4.1 Flash || 8 || vLLM PR #56201 + 20 patches, PP8 || [[DeepSeek V4.1 Flash on 8x 8 GB (Zanooda PP8)]]
|-
| DeepSeek V4.1 Flash || 2 || Project Maya || [[DeepSeek V4.1 Flash on 2x 8 GB (Project Maya)]]
|-
| Qwen3.8 Flash Next || 1 || Morrowmake image + patches, 3 bpw || [[Qwen3.8 Flash Next on 1x 8 GB (ElectroHobo 3 bpw)]]
|-
| Qwen3.8 Flash Next || 1 || patched vLLM, PLE on SSD || [[Qwen3.8 Flash Next on 1x 8 GB (iIIusi0n SSD PLE)]]
|-
| Qwen3.8 Flash Next || 2 || Morrowmake image + patches, W4A16 TP2 || [[Qwen3.8 Flash Next on 2x 8 GB (ElectroHobo W4A16 TP2)]]
|-
| Qwen3.8 Flash Next || 2 || Morrowmake vLLM fork, EXL3 || [[Qwen3.8 Flash Next on 2x 8 GB (Morrowmake EXL3)]]
|-
| Qwen3.8 Flash Next || 2 || wtdcode/vllm-backport PP2 || [[Qwen3.8 Flash Next on 2x 8 GB (mannydelrio PP2)]]
|-
| Qwen3.8 Flash Next || 2 || vLLM v0.30.0 + INT4-PLE plugin PP2 || [[Qwen3.8 Flash Next on 2x 8 GB (DUFRelic PP2)]]
|-
| Qwen3.8 Flash Next || 2 || vLLM PR #53899 + patches PP2 || [[Qwen3.8 Flash Next on 2x 8 GB (vektorprime PP2)]]
|-
| Qwen3.8 Flash Next || 2 || vLLM 0.29.1rc1 + checkpoint patches PP2 || [[Qwen3.8 Flash Next on 2x 8 GB (Plean PP2)]]
|-
| Qwen3.8 Flash Next || 3 (or 2) || vLLM nightly + clee/vllm-sm80 PP3 || [[Qwen3.8 Flash Next on 3x 8 GB (clee PP3)]]
|-
| Qwen3.8 Flash Next || 4 || wtdcode/vllm-backport TP4 + EP || [[Qwen3.8 Flash Next on 4x 8 GB]]
|-
| Qwen3.8 27B || 1 || vLLM W4A16 || [[Qwen3.8 27B on 1x 8 GB (W4A16 vLLM)]]
|-
| MiMo V2.6 Flash || 4 || Morrowmake image, NVFP4 TP4 || [[MiMo V2.6 Flash on 4x 8 GB]]
|}

Write-ups from Discord, summarised with credit: Plean's two-card build on [[Qwen3.8 Flash Next on 2x 8 GB (Plean PP2)]],
matstatman's four-card compose on [[Qwen3.8 Flash Next on 4x 8 GB]], and Feralzi's single-card overclock setup on
[[Qwen3.8 27B on 1x 8 GB (W4A16 vLLM)]].

Other published recipes not yet written up as pages: the localairecipes entry "DeepSeek-V4.1-Flash (764B) on 4x CMP 170HX,
PP4, shadow KV, EXL3 2bpw" (Miséricorde's critique: the author has no P2P, uses FP8 KV at about 4 KB per token where the
native FP4 KV is about 0.9 KB, and 2 bpw is unnecessary because 3.05 to 3.15 bpw fits), PixelML/club-170hx's DeepSeek
V4.1 Flash EXL3 4-card TP4 EP4 DSpark result, AlexBrandes/cmp170hx-qwen38-flash-next (two cards, PP2, x4 links) and
kaka86mm/vllm-mimo-170hx. More two-card Qwen3.8 Flash Next builds listed on localairecipes (author-reported, no public
reproductions as of 2026-10-27): bluespace3 (PP2, MTP4, FP8 PLE table memory-mapped from NVMe, YaRN to 1,048,576
context: 62-112 tok/s, 6,080 tok/s prefill at 80K); moriyasujapan (TP2 + expert parallel, MTP4, FP8 PLE, 92 GB host:
101-114 tok/s prose, 170-173 code, 2,637-3,068 prefill; FP8 KV costs 6-11% decode); nguyenthimy2022kg-alt (NVFP4,
TEP2, PLE table read from SSD over GPUDirect Storage, 32 GiB host: 151-171 tok/s, about 2,000 prefill, one sequence,
needs the BAR1 P2P driver and a GDS-validated NVMe); and a 4-card official-FP8 PP4 MTP4 build at 1M context by g4bwy.
{{Source|handle=darkmaniac7|date=2026-10-27|note=lab notes}}
{{Source|handle=wakeupmbrc1|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560989699693092926}} 
{{Source|handle=c133|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562161732137386127}}

== Choosing a model ==
The community view as of late October 2026 (a rough consensus, with dissent):
* '''One card:''' Qwen3.8 Flash Next with the PLE patches is the go-to; the dense Qwen3.8 27B is the alternative. {{Source|handle=68x0|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564715517355229206}}
* '''Two cards:''' Qwen3.8 Flash Next. Miséricorde: "3.8fn for 2 is the best", and for two cards it beats any GLM recipe because GLM needs four cards to run properly in integer weights. {{Source|handle=wakeupmbrc1|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1559514038453673998}} {{Source|handle=wakeupmbrc1|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564374464362446952}}
* '''Four cards:''' GLM 5.3 Flash W4A16 on Morrowmake's recipe, with DeepSeek V4.1 Flash 1017 as an option if you have the RAM or SSD for its Engram tables. Four cards give disproportionately more than two because the whole "Flash" model stack fits; Miséricorde found even his best overclocked Qwen Flash Next 1.6x slower than GLM Flash on stock 180 W cards. {{Source|handle=wakeupmbrc1|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1560617240997658635}} {{Source|handle=wakeupmbrc1|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561342529318821920}} {{Source|handle=lia_oc|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564319786618327141}} His further argument: on two cards the only Flash option is Qwen3.8 Flash Next, which Strata already makes reachable on regular GPUs; GlobalApathy's reply: Qwen Flash Next "if you have the system resources". {{Source|handle=wakeupmbrc1|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561342921817722922}} {{Source|handle=wakeupmbrc1|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561342946723504171}} {{Source|handle=globalapathy|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561364165673754717}}
* '''Six cards:''' DeepSeek V4.1 Flash at native precision (TP2 x PP3). 384 GB should be enough for DeepSeek V4.1 Flash and more than enough for GLM 5.3 Flash. {{Status|Theory}} Miséricorde thinks six may be worse than four for DeepSeek because TP6 is impossible. {{Source|handle=wakeupmbrc1|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560998728507068447}} {{Source|handle=civiloid|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1561806539872931933}}
* '''Eight cards:''' full GLM 5.3, DeepSeek V4.1 Flash at native precision with the best prefill, or two 4-card instances of GLM 5.3 Flash for throughput. Two Flash instances beat one full GLM 5.3: much faster and not really different in capability (Miséricorde). {{Source|handle=wakeupmbrc1|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560774490755960833}}
* '''Five cards''' are mostly wasted: vLLM's TP must divide the model's attention head count (DeepSeek V4.1: TP 1, 2, 4 or 8), so buy 4 or 6. A fifth card can still hold mmproj or a draft model in llama.cpp. {{Source|handle=ob88594|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562547098791051296}} {{Source|handle=greencandle9753|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562580021153894501}} {{Source|handle=da6b|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562556812148998207}} Asked what to run on five unlocked 8 GB cards, clee answered DeepSeek V4.1 Flash 1017. {{Source|handle=amishrakefightr|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563641385813278792}} {{Source|handle=c133|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563644556048597003}}

{{Status|Contested}} Model quality, by person:
* GLM 5.3 Flash against Qwen Flash Next on four cards: Mountains finds GLM a step up in logic; OB88594 sums up Qwen for world knowledge, GLM for coding; segmond thinks Qwen 3.8 Flash is excellent and GLM will not beat it everywhere. {{Source|handle=mountains1605|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556411170519392327}} {{Source|handle=segmond|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556303204407316591}} {{Source|handle=ob88594|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556898270280814615}}
* DeepSeek V4.1 Flash against GLM 5.3 Flash: Mountains found DeepSeek a bit more intelligent but less consistent at first, then rated Morrowmake's DeepSeek build above GLM Flash; DeeJay's own suite had DeepSeek 1017 ahead of GLM 5.3 Flash; reala thinks full GLM 5.3 may still win pure coding. {{Source|handle=deejay9983|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562913695791579207}} {{Source|handle=mountains1605|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563027744571392021}} {{Source|handle=mountains1605|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1564695486911217665}}
* Qwen Flash Next against the 27B: PJ finds the 27B better at tool calling and reasoning; dash got a better game out of Flash Next IQ3_S than 27B Q6; Programmer007: Next builds, 27B fixes bugs. orrorin: low-quant Flash Next and high-quant 27B are neck and neck in benchmarks; dottoreargus: Flash Next is much faster for the same knowledge. {{Source|handle=_orrorin|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1557125328407896136}} {{Source|handle=dottoreargus|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1557126227079200941}} {{Source|handle=zingy90210|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560953990319964276}} {{Source|handle=mowgli8628|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560944262349193260}} {{Source|handle=programmer_007|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560960210254700715}}
* Qwen looping at long context: @_____josh_____ says anything over 150k context loops without supervision, the 27B worst, and "It has nothing to do with the temp. I have tried all"; matstatman sees Qwen loop at temperature 0 but leaves it running for hours at temperature 1 without trouble; Miséricorde: verbose on max reasoning, but constant looping is not normal, and reasoning can be limited. Nobody posted a test on a CMP rig. {{Source|handle=matstatman|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556380275590561813}} {{Source|handle=_____josh_____|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556381383616757861}} {{Source|handle=matstatman|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556381759187324989}} {{Source|handle=wakeupmbrc1|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556381869237346407}} {{Source|handle=_____josh_____|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556383653007986719}}
* DeepSeek V4.1 Flash 1017 takes images as well as text (a 32-layer vision tower, up to 1,024 image tokens); the Zanooda, Morrowmake and GNmac recipes all keep the vision tower in BF16. At long context, Con3po finds it "goes a bit crazy" around 200k context; 68x: usually a KV issue (single report, recipe not named). {{Source|handle=darkmaniac7|date=2026-10-27|note=lab notes}}
* MiMo V2.6 Flash: see [[MiMo V2.6 Flash on 4x 8 GB#Is it better than GLM 5.3 Flash?]].
* Context in practice: matstatman runs Qwen3.8 Flash on four cards at the normal 265k context and finds compaction fast enough that he does not need 1M. {{Source|handle=matstatman|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562214943703568550}} {{Source|handle=matstatman|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562215886914588815}}
* Step 5: Con3po runs it at almost 100 tok/s prose with 1M context on six cards and keeps it for vision. {{Source|handle=con3po7016|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1561026955111829556}}
* GLM 5.3 Flash against Qwen 3.8 27B: Miséricorde calls the 27B very verbose and finds GLM 5.3 Flash about 2x less verbose and 2 to 3x faster on code; Phoenix17's Swift 1.5 fine-tune of the 27B is meant to cut that verbosity (see [[Qwen3.8 27B on 1x 8 GB (W4A16 vLLM)]]). {{Source|handle=wakeupmbrc1|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563206459955609635}} {{Source|handle=wakeupmbrc1|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563206518537457676}} {{Source|handle=phoenixone7|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563206670149091419}}
* MiniMax M3.1: Con3po runs it on 4 GPUs at 76 tok/s decode at concurrency 1; segmond needed 6 GPUs and gets 30 tok/s. Neither posted engine, quant or flags, and it is not stated whether all of Con3po's GPUs are CMPs (he also runs mixed GPUs). Asked for a MiniMax recipe, Con3po said he had none: the model (version not stated in that reply) was a complete failure at computer use for him, in his own harness and in the vendor's, and he doubts its published OSWorld score. Summary of their posts; see [https://discord.com/channels/1518634379604136178/1518692084729511967/1563943584120709192 Discord]. {{Source|handle=con3po7016|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563759486269792378}} {{Source|handle=con3po7016|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563759802230907013}} {{Source|handle=segmond|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563943463873937509}} {{Source|handle=con3po7016|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563943584120709192}} {{Source|handle=segmond|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563943781034885143}}

== Choosing a layout and engine ==
* '''Use vLLM (or sglang), not llama.cpp.''' llama.cpp is too slow on these cards; the CMP prefers INT4/INT8 weights (W4A16 through Marlin), which vLLM serves well. See [[Engines]] and [[Quantization on the 170HX]]. {{Source|handle=ob88594|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556898516910215230}} {{Source|handle=gnasherrr|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564318714722254939}}
* '''TP needs x16 links (and ideally P2P); PP tolerates x4.''' On PCIe Gen2 x4, TP4 gives usable decode but unusable prefill; PP passes only activations. With x16 and P2P, TP4 wins decode for GLM Flash and MiMo, and P2P off costs about 40% on MiMo TP4. See [[Unlocks]] for the x16 mod and P2P. {{Source|handle=voidgiraffe|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556157382273400935}} {{Source|handle=wakeupmbrc1|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561400726448513137}}
* {{Status|Contested}} Jeremy (Ends): a dense model in TP over PCIe will be bandwidth-choked, so PP with P2P DMA is the safer default; Miséricorde: TP4 viability depends on the model's architecture (GLM Flash is latency-bound, not bandwidth-bound, and faster in TP4 than in PP4 or TP2 x PP2). Plean: TP is repeatedly shown to be PCIe-limited on these cards. NikhilR finds TP2 x PP2 better than TP4 on four cards for A3B models. {{Source|handle=plean.|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1557095904572342403}} {{Source|handle=nikhilr1696|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557490632635842651}} {{Source|handle=endsjeremy|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561400267503566900}} {{Source|handle=wakeupmbrc1|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561400395392094352}} {{Source|handle=wakeupmbrc1|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561400726448513137}} {{Source|handle=wakeupmbrc1|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561400861647708201}}
** Lab measurements, GLM 5.3 Flash W4A16 on four 8 GB cards (Morrowmake engine, recipe 1.8.0): at Gen2 x8 without P2P, TP4 decodes 1.6 to 1.9x faster than PP4 while PP4 prefills 2.8 to 3.9x faster and holds about 1.7x the KV pool. On a second host TP2 x PP2 sat in between, about a third less single-stream decode than TP4 for 2.5x its prefill. Both hosts had x8 or x16 links; nobody has run the same matrix on x4 cards. {{Source|handle=darkmaniac7|date=2026-10-19|note=lab notes}} {{Source|handle=darkmaniac7|date=2026-10-28|note=lab notes}}
* PixelML's reasoning for PP on PCIe-only cards: TP does two all-reduces per layer (about 86 collectives per forward pass on a 43-layer model), while PP sends one hidden-state hand-off per stage boundary, about 28x less data, and overlaps it with compute. Their GLM-5.3-Flash recipe of record (older stack) was PP4 with native MTP k=3 at 87.55 tok/s for one user against 60.4 on TP4. A community PP8 cost model puts a step at about 32 ms fixed plus 2.1 ms per verified token, so accepted draft length is the throughput lever. {{Source|handle=darkmaniac7|date=2026-09-05|note=lab notes}}
* The x16 mod in one line: the card routes all 16 lanes but the factory leaves the AC-coupling capacitors for lanes 4-15 unpopulated; fitting 24 x 0402 220 nF X7R capacitors (2 per differential pair) restores x16, and fitting 12 gives x8. It changes link width only, never PCIe generation. Details on [[Unlocks]]. {{Source|handle=darkmaniac7|date=2026-04-30|note=lab notes}}
* P2P routes in one line: static BAR1 P2P (bayley's patches and descendants; bare metal, IOMMU off or passthrough, 1.07-6.4 GB/s depending on host) and mailbox P2P with the TRAP31 PLM opened through the Booter (Morrowmake/cmpunlocker with <code><nowiki>ForceP2P=0x11</nowiki></code>; works with a 64 MiB BAR1 and the IOMMU translating, about 5.8-6.65 GB/s). Neither has been run inside a VM. Details on [[Unlocks]]. {{Source|handle=darkmaniac7|date=2026-10-19|note=lab notes}}
* '''Host RAM and NVMe matter''' for the n-gram models: Qwen3.8 Flash Next's PLE table is about 100 GB in BF16 (48 GiB in FP8) and DeepSeek V4.1's Engram tables about 189 GiB. In RAM a lookup costs about 0.3 ms per token, from SSD about 1 to 1.5 ms; RAM speed itself is irrelevant because the lookups are latency-bound. See [[Quantization on the 170HX]]. {{Source|handle=wakeupmbrc1|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1558843833285087285}} {{Source|handle=wakeupmbrc1|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560991144454918319}}
* '''Power:''' most published numbers are at 180 W per card. See [[Cooling and power]].
* '''Mixing 8 GB and 10 GB cards:''' you are limited by the slowest card. {{Status|Theory}} {{Source|handle=moliminous|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1559200727794974821}}
* {{Status|Theory}} Takka's idea for prefill on Gen2 cards: keep a TP copy in VRAM and a PP copy in host RAM and swap the whole model to PP for large prefills (10 to 15 s per swap on Gen2); untested. {{Source|handle=spectakkular|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556200373352661124}}

== 10 GB card ==
No recipe in this list was measured on the 10 GB card. What exists:
* eXile runs Qwen3.8 Flash Next (IQ3_S) with Strata on a single 10 GB-variant card configured at 40 GB (14600K, 128 GB DDR4); moving it from x4 to x16 mainly improved prefill. See [[Benchmarks]] and [[10 GB card]]. {{Source|handle=exile_1ck|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557241785695211612}}
* {{Status|Reported}} Feralzi runs [https://huggingface.co/dealignai/Nanbeige4.3-33B-UNCENSORED-GGUF dealignai/Nanbeige4.3-33B-UNCENSORED-GGUF] at Q6_K with about 200K context on a single 40 GB card, at 27 tok/s while still tuning (earlier he posted 40 tok/s "optimized", setup not stated). {{Source|handle=feralzi|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564051736979701845}} {{Source|handle=feralzi|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564092189397491872}} {{Source|handle=feralzi|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564092405026660406}} {{Source|handle=feralzi|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564114097694445662}} [https://huggingface.co/Nanbeige/Nanbeige4.3-33B Nanbeige4.3-33B] is dense with no sparse attention, so its KV cache is large: Miséricorde estimates about 208 KB per token at 16 bit, about 100 GB for 512K tokens, and for 256K about 20+ GB at 8 bit or 10 to 12 GB at 4 bit. Phoenix17: the FP16 weights are about 65 GB and a W8A8 quant about 33 GB, which with 256K context would about fill a 64 GB card; on a 40 GB card he suggests a W4A16 quant. orrorin was making a W4A16 quant on 2026-10-25 and had hit a few snags. {{Source|handle=phoenixone7|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563946316134883410}} {{Source|handle=wakeupmbrc1|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563947653900013742}} {{Source|handle=wakeupmbrc1|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563953011162751027}} {{Source|handle=wakeupmbrc1|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563953289782104085}} {{Source|handle=wakeupmbrc1|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563953340314812437}} {{Source|handle=wakeupmbrc1|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563953818293641409}} {{Source|handle=wakeupmbrc1|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563953911373766676}} {{Source|handle=phoenixone7|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563955593172226079}} {{Source|handle=phoenixone7|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563957085580828763}} {{Source|handle=_orrorin|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563946121942925317}} {{Source|handle=_orrorin|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564054183089406013}}
* {{Status|Theory}} With an 80 GB unlock, four cards (320 GB) would hold the full GLM 5.3 EXL3 quant, which is under 300 GB. {{Source|handle=stcord|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558098919249150063}} {{Source|handle=globalapathy|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558099082743128095}}
If you run a recipe on 10 GB cards, add a confirmation on its page with the card variant set to 10 GB.

== Other workloads ==
* '''Video and image generation:''' MiniMax H3 makes an 8-second clip in 10 to 15 minutes on one unlocked 8 GB card (domrockt2); Phoenix17 makes 30-second clips at 640x960 in about 15 minutes with a custom H3 model and says much longer will not fit on one card; LTX 2.5 is lighter with a better latent upscaler. quark2world made a full music video with H3; Qwen Image 2.1 needs about 40 GB. Takka recommends Breeze for one-shot voice cloning. {{Source|handle=phoenixone7|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556411173497344092}} {{Source|handle=quark2world|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556364987717525556}} {{Source|handle=spectakkular|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518691940646781070/1556985426323968033}} {{Source|handle=domrockt2|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557621895074029609}}
* '''Training:''' a single CMP trained almost 4x slower than a 5090 (same nominal BF16 TFLOPs); programmerboi suspects no tuned GEMM kernel exists for the harvested die. orrorin's SFT on four cards was slow and PCIe 2.0 x4 was the bottleneck during offload, so the x16 mod is essential; prototype locally and rent for serious training. {{Source|handle=programmerboi|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560681327848726559}} {{Source|handle=_orrorin|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560681653788217435}} programmerboi trains on the CMPs with his own mixed-precision int4 + bf16 stack, which he says gives slightly better compute than most FP4 training schemes, so he does not need Blackwell; against a Blackwell card at a similar price he counts lower throughput, lower bandwidth and double the cost, with only Gen5 and FP8/FP4 in the Blackwell's favour. No link to the stack was posted. {{Source|handle=programmerboi|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562108203565846539}}
* '''Mining between jobs:''' Pearl mining runs at 145 to 164 TH/s per card at about 200 W; lower HBM NDIV with REFRESH 24 saves heat without hash loss but must be raised again for LLM work. RH-3D's water-cooled 170tune settings: <code><nowiki>--ndiv 66 --offset 270 --clk 1410 --timings "REFRESH 24"</nowiki></code> at about 202 W (an earlier <code><nowiki>--ndiv 66 --offset 240 --clk 1380</nowiki></code> gave 164 TH/s at about 200 W). {{Source|handle=rh3dai|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1555480078089986138/1557687218473144411}} {{Source|handle=rh3dai|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518691940646781070/1556536892759998566}} See [[Cooling and power]] and [[Tools]]. {{Source|handle=analyticeth|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518691940646781070/1556400027016892517}} {{Source|handle=markshowa|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1555480078089986138/1564081815013036093}}

== Not yet run on these cards ==
* {{Status|Theory}} unsloth/flint-GGUF (39.8B, 2.5B active): Programmer007 expects Q8 to fit one card and be very fast. {{Source|handle=programmer_007|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562632155153301527}}
* {{Status|Theory}} MiniMax 3.1 Flash at 4 bits should not fit four cards (quants keep parts at BF16 or FP8, so expect more than 250 GB) unless it uses the same n-gram approach as DeepSeek V4.1 Flash. {{Source|handle=civiloid|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562331287849664573}} Con3po has since reported MiniMax M3.1 on 4 GPUs at 76 tok/s (see [[#Choosing a model]]); whether those were all CMPs, and the quant, were not stated. {{Source|handle=con3po7016|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563943584120709192}}
* {{Status|Theory}} Open question from cibernox for a company build: is 8x CMP 170HX still the most convenient way to 512 GB of VRAM after the October price rises (16 V100s being too inconvenient)? No answer yet. {{Source|handle=cibernox|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1561700967077122070}}
* {{Status|Theory}} PJ, without the x16 cap mod, wants to run [https://huggingface.co/ISTA-DASLab/DeepSeek-V4.1-Flash-1017-GSQ-RCO-GGUF ISTA-DASLab/DeepSeek-V4.1-Flash-1017-GSQ-RCO-GGUF] at IQ2_XXS with Strata offloading to system RAM, and asked for cheap DDR4 (see [[Buying#Other parts people bought]]). No result yet. {{Source|handle=zingy90210|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563543212763648089}} {{Source|handle=zingy90210|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563551730380312648}} {{Source|handle=zingy90210|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563551825708195973}}
* {{Status|Theory}} roboalchemist is packing an FP4 DeepSeek V4.1 1017 mix sized for six cards. {{Source|handle=roboalchemist.|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1561155845344198687}}

== Related ==
[[Engines]] · [[Quantization on the 170HX]] · [[Benchmarks]] · [[Unlocks]] · [[Driver unlock]] · [[8 GB card]] ·
[[10 GB card]] · [[Cooling and power]] · [[Troubleshooting]] · [[Tools]]

{{ImportFooter}}
[[Category:Recipes]]

Qwen3.8 Flash Next on 2x 8 GB (Plean PP2)

2026-10-31T21:34:47Z

ImportBot: Import: Plean's 2-card Qwen3.8 Flash Next write-up (Discord and bozocentral.com), GalyGames' reproduction, Ryko's warning, the lab notes on the localairecipes listing; sources: @plean., @darkmaniac7, @ob88594, @dufrelic, @mountains1605, @vektor_prime, @galygious; GitHub vektorprime/qwen38-flash-next-pp2

{{Recipe
|model=Qwen3.8-Flash-Next
|quant=Mixed INT4 AutoRound (Minachist/Qwen3.8-Flash-Next-INT4-Mixed-AutoRound, about 65 GB) with the full BF16 PLE table on NVMe
|engine=vLLM 0.29.1rc1 nightly plus the checkpoint author's patches
|cards=8 GB
|card_count=2
|topology=PP2, MTP 3, no P2P
|context=262,144 (256K in the post)
|decode_tps=197
|prefill_tps=5800
|vram_per_card=64 GB
|flags=--pipeline-parallel-size 2, MTP 3 draft tokens, max concurrency 6, BF16 PLE table offloaded to NVMe
|status=Reported
|tested_by=plean.
|tested_on=2026-10-07
|source=https://www.bozocentral.com/2x-cmp170hx-qwen3-flash-next
}}
Plean's setup for Qwen3.8 Flash Next on two 64 GB cards: vLLM pipeline parallel 2, MTP speculative decoding, and the
full BF16 PLE (n-gram) table offloaded to NVMe instead of held on the cards. It uses Minachist's mixed INT4 AutoRound
checkpoint and runs up to 6 concurrent requests with a 256K context window. P2P is off on his rig because of a chipset
issue with how lanes are assigned between his motherboard and CPU, so it needs neither P2P nor the x16 mod. The full
write-up is on his site, linked in the infobox. Infobox numbers are from the localairecipes listing of this build
(predictable output; see below).
{{Source|handle=plean.|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1557427236447985704}} 
{{Source|handle=plean.|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1557460249424826449}} 
{{Source|handle=plean.|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1557461178018566226}}

== Prerequisites ==
* Two CMP 170HX at 64 GB ([[Driver unlock]], [[8 GB card]]). No P2P needed; PP2 passes only activations, so x4 links work.
* A fast NVMe for the BF16 PLE table (about 95 GiB) and about 64 GB of host RAM.
* The checkpoint [https://huggingface.co/Minachist/Qwen3.8-Flash-Next-INT4-Mixed-AutoRound Minachist/Qwen3.8-Flash-Next-INT4-Mixed-AutoRound] (gated; body about 65-67 GiB).
{{Source|handle=plean.|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1557427236447985704}} 
{{Source|handle=darkmaniac7|date=2026-10-27|note=lab notes}}

== Steps ==
Follow Plean's write-up at [https://www.bozocentral.com/2x-cmp170hx-qwen3-flash-next bozocentral.com]. In outline, as
listed on localairecipes and in the lab notes:
# Pull the vLLM image <code><nowiki>vllm-openai 0.29.1rc1.dev47</nowiki></code> and apply the checkpoint author's patches (16 patch files, local build).
# Download the Minachist INT4-Mixed AutoRound checkpoint (revision <code><nowiki>6a995be5</nowiki></code> in the listing).
# Serve with pipeline parallel 2 and MTP 3, the BF16 PLE table memory-mapped from NVMe, 262K context. The listing reports a 1.8M-token BF16 KV pool.
# Plean serves it through llama-swap; set the concurrency you need (he runs 6).
{{Source|handle=darkmaniac7|date=2026-10-27|note=lab notes}}

== Measured numbers ==
* Per stream, from Plean: about 100 tok/s each with 2 streams and about 80 each with 3 to 4. Per-stream speed drops because vLLM runs prefill and decode one after the other here (OB88594). DUFRelic has the same problem on his setup: 120 tok/s for one stream and only about double that at 4 concurrent. {{Source|handle=plean.|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1557459833928556697}} {{Source|handle=ob88594|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1557464371838451723}} {{Source|handle=dufrelic|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1557460484830138469}}
* localairecipes listing of this build (rev 74b4d06): 197-201 tok/s on predictable output, 116-122 on thinking-heavy output for one user; 154-212 tok/s for 2 streams; prefill about 5,800 tok/s. {{Source|handle=darkmaniac7|date=2026-10-27|note=lab notes}}
* For comparison, Mountains pointed 68x to another localairecipes entry, W4A16 with an INT4 PLE table on two x16-modded cards (PP2, MTP3), listed at 133 tok/s for one user and 245 at 4 concurrent; he was not sure he liked the INT4 PLE table. {{Source|handle=mountains1605|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1557599164530040852}}

== Known issues ==
* Ryko warns that a run-to-run variance issue he found in upstream vLLM (KL divergence that changed between identical runs) probably affects anyone serving this model with vLLM; his fix notes are in [https://github.com/vektorprime/qwen38-flash-next-pp2/commit/32595fbaa3ae24764055e5b6341e7a63c35fbcf1 vektorprime/qwen38-flash-next-pp2 commit 32595fb]. Plean's table is the full BF16 one on NVMe, which he expects to be unaffected. See [[Qwen3.8 Flash Next on 2x 8 GB (vektorprime PP2)]]. {{Source|handle=vektor_prime|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1557443747892035674}} {{Source|handle=plean.|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1557460674093912109}}
* The checkpoint is gated on Hugging Face.

== Variants ==
* GalyGames reproduced it on a Proxmox setup and added the huihui "decision matrix" abliteration to remove refusals for local coding. {{Source|handle=galygious|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1557608614318047253}}

== Related ==
* Other 2-card recipes: [[Qwen3.8 Flash Next on 2x 8 GB (ElectroHobo W4A16 TP2)]], [[Qwen3.8 Flash Next on 2x 8 GB (mannydelrio PP2)]], [[Qwen3.8 Flash Next on 2x 8 GB (DUFRelic PP2)]].
* [[Engines]], [[Quantization on the 170HX]], [[Benchmarks]].

== Sources ==
* Plean's posts in the testing channel, 2026-10-07, and his write-up at bozocentral.com.
* Lab notes, 2026-10-27 (localairecipes listing).

{{ImportFooter}}
[[Category:8 GB]]

Qwen3.8 Flash Next on 2x 8 GB (Morrowmake EXL3)

2026-10-31T21:34:46Z

ImportBot: Import: Morrowmake's Qwen3.8-Flash-Next EXL3 recipe (figures quoted in ElectroHobo's README and the vllm-cmp170hx docs), cibernox's and Morrowmake's Discord comments, ElectroHobo's Broadwell measurement; sources: @voidgiraffe, @nathang6866, @cibernox, @darkmaniac7; GitHub ElectroHobo/qwen38-flash-next-w4a16-2x-cmp170hx-recipe, Morrowmake/qwen38-flash-next-cmp170hx-recipe, Morrowmake/vllm-cmp170hx

{{Recipe
|model=Qwen3.8-Flash-Next
|quant=EXL3 5.05 bpw; PLE (n-gram) table read from SSD
|engine=Morrowmake/vllm-cmp170hx (EXL3 path)
|engine_version=tag qwen38-recipe-1.0.0, engine 18305948ac
|cards=8 GB
|card_count=2
|topology=TP2 with expert parallel
|context=262,144
|decode_tps=152.6
|prefill_tps=2651
|vram_per_card=64 GiB, --gpu-memory-utilization 0.95
|flags=--quantization exl3 --load-format exl3 --tensor-parallel-size 2 --enable-expert-parallel --engram-config cpu_offload false, VLLM_EXL3_PLE_PLACEMENT=ssd, cudagraph PIECEWISE, MTP 3
|status=Reported
|tested_by=voidgiraffe
|tested_on=2026-10-16
|source=https://github.com/Morrowmake/qwen38-flash-next-cmp170hx-recipe
}}
Morrowmake's Qwen3.8-Flash-Next recipe on two cards with his vLLM fork's EXL3 path (release 1.0.0, engine tag
<code><nowiki>qwen38-recipe-1.0.0</nowiki></code>). He chose 5.05 bpw because a 1M-token KV cache still fit, and said on 2026-10-16 that
W4A16 is probably a better choice than EXL3. The ElectroHobo two-card recipe
descends from its scripts and runs the same engine image. Infobox numbers are the published one-user code figure and
cold prefill, as quoted in ElectroHobo's README.
{{Source|handle=voidgiraffe|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1560409434339934329}} 
{{Source|handle=voidgiraffe|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1560599553210851400}} 
{{Source|handle=nathang6866|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563590746710478919|repo=https://github.com/ElectroHobo/qwen38-flash-next-w4a16-2x-cmp170hx-recipe}}

Morrowmake released this recipe as a first attempt alongside the GLM update, after two weeks spent moving his custom code behind vLLM plugins. On x4 links he expects it to hurt prefill (untested) and planned a PP2 version. {{Source|handle=voidgiraffe|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1560411313212227727}} {{Source|handle=voidgiraffe|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1560412542096904213}} {{Source|handle=voidgiraffe|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1560579094666678283}}

== Prerequisites ==
Two CMP 170HX at 64 GiB and 74 SMs on x16 links with P2P, Docker with the NVIDIA Container Toolkit, driver 580 or newer;
a fast CPU, because the PLE table is read from SSD inside each step (see Known issues). See [[Driver unlock]],
[[8 GB card]], [[Unlocks]].

== Steps ==
The recipe repo follows the same pattern as Morrowmake's GLM and DeepSeek recipes (clone, <code><nowiki>./start.sh</nowiki></code>), pinned to
engine commit 18305948ac and image
<code><nowiki>ghcr.io/morrowmake/vllm-cmp170hx@sha256:5b45c4d6feafefe2eba962375b0a9a0b64fd22b9e05abb4d1966f14a32a2db79</nowiki></code>.
The engine's documentation gives the two-card command:
<syntaxhighlight lang="bash">
CUDA_VISIBLE_DEVICES=0,1 VLLM_EXL3_PLE_PLACEMENT=ssd VLLM_USE_BREAKABLE_CUDAGRAPH=1 \
vllm serve <exl3 checkpoint> --quantization exl3 --load-format exl3 --mm-encoder-tp-mode data \
--tensor-parallel-size 2 --pipeline-parallel-size 1 --enable-expert-parallel --dtype bfloat16 \
--kv-cache-dtype bfloat16 --attention-config '{"indexer_kv_dtype":"bf16"}' --engram-config '{"cpu_offload":false}' \
--max-model-len 262144 --gpu-memory-utilization 0.95 --compilation-config '{"cudagraph_mode":"PIECEWISE"}' \
--speculative-config '{"method":"mtp","num_speculative_tokens":3}'
</syntaxhighlight>
Optional: <code><nowiki>--hf-overrides</nowiki></code> with <code><nowiki>text_config.moe_router_dtype float32</nowiki></code> and <code><nowiki>mtp_hidden_norm per_stream</nowiki></code>.
The EXL3 extension is built for SM 8.0 only; several dense paths are validated for 74-SM cards at TP2.
{{Source|handle=voidgiraffe|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1560413471055548446|repo=https://github.com/Morrowmake/vllm-cmp170hx}}

== Measured numbers ==
Morrowmake's published figures (his box, a current CPU), as quoted by ElectroHobo; tok/s structured / code / prose:
{| class="wikitable"
! 1 user !! 2 users !! 4 users !! 8 users !! Cold prefill !! KV pool
|-
| 152.8 / 152.6 / 118.3 || 236.5 / 265.0 / 204.6 || 357.1 / 458.6 / 327.2 || 588.2 / 674.7 / 489.9 || 2,651 || 1,044,325
|}
{{Source|handle=nathang6866|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563590746710478919|repo=https://github.com/ElectroHobo/qwen38-flash-next-w4a16-2x-cmp170hx-recipe}}
* Before release: about 150 tok/s single stream on EXL3 5.05 bpw, aiming near 200 single and over 600 multi-stream. 4 bpw would likely not be much faster. {{Source|handle=cibernox|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1560296987838914591}} {{Source|handle=voidgiraffe|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1560409434339934329}}

== Known issues ==
* {{Status|Contested}} CPU dependence. On ElectroHobo's dual Broadwell host the mid-step SSD n-gram read costs about 44 ms per step and the recipe runs at 55 to 70 tok/s for one user against the published 153; PIECEWISE graphs are about 3x slower per step on an old CPU. The lab notes count it CPU-bound for the same reason. His W4A16 recipe keeps the table in host RAM with full CUDA graphs instead. {{Source|handle=nathang6866|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563590746710478919|repo=https://github.com/ElectroHobo/qwen38-flash-next-w4a16-2x-cmp170hx-recipe}} {{Source|handle=darkmaniac7|date=2026-10-27|note=lab notes}}
* EXL3 decode on these cards is compute-bound; see [[Quantization on the 170HX]].

== Related ==
* [[Qwen3.8 Flash Next on 2x 8 GB (ElectroHobo W4A16 TP2)]] (descends from this recipe, faster), [[Engines]], [[Benchmarks]].

== Sources ==
* Recipe: Morrowmake/qwen38-flash-next-cmp170hx-recipe (release 1.0.0, engine tag <code><nowiki>qwen38-recipe-1.0.0</nowiki></code>); announcement on X linked from Discord. The recipe repo itself was not cloned for this page; numbers are quoted from ElectroHobo's README.

{{ImportFooter}}
[[Category:8 GB]]

Qwen3.8 Flash Next on 2x 8 GB (ElectroHobo W4A16 TP2)

2026-10-31T21:34:40Z

ImportBot: Import: ElectroHobo/qwen38-flash-next-w4a16-2x-cmp170hx-recipe 0.1.0 to 0.3.1 (repo and Discord posts); Miséricorde on the drafter; the lab run of four instances; gap-fill from #general 2026-10-25 (P2P), @galygious2, @nathang6866

{{Recipe
|model=Qwen3.8-Flash-Next (125B MoE per the recipe)
|quant=W4A16: halt95/Qwen3.8-Flash-Next-W4A16-Merlin (AutoRound INT4 g128 experts, INT8 GDN projections, FP8 n-gram table)
|engine=Morrowmake/vllm-cmp170hx image (Qwen EXL3 release) with patch files mounted read-only
|engine_version=recipe 0.3.1; engine 18305948ac
|cards=8 GB
|card_count=2
|topology=TP2 with whole-expert expert parallel
|context=262,144
|decode_tps=349.7
|prefill_tps=4696
|vram_per_card=64 GiB, GPU_UTIL 0.95 (fixed)
|power_cap=180 W
|driver=580 or newer (measured on 610.57.04); open modules with HMM for the table-on-disk mode
|unlock_build=cmpunlocker (64 GiB, 74 SMs) with a P2P-capable build
|flags=--tensor-parallel-size 2 --enable-expert-parallel --kv-cache-dtype bfloat16 --engram-config cpu_offload --max-num-seqs 128 --block-size 912 cudagraph FULL_AND_PIECEWISE; DFlash 2 drafter 7/5/3/2 by load
|status=Reported
|tested_by=nathang6866
|tested_on=2026-10-23
|source=https://github.com/ElectroHobo/qwen38-flash-next-w4a16-2x-cmp170hx-recipe
}}
Qwen3.8-Flash-Next in W4A16 on two 64 GB cards with inco.ai's DFlash 2 drafter, full 262,144-token context, vision,
reasoning and tool calls, and up to 128 concurrent requests. It runs Morrowmake's engine image as released with a few
patch files mounted over it. It exists for old CPUs: the 48 GiB n-gram (PLE) table stays in host RAM (or, since 0.3.0,
in a disk file the cards read through HMM), so the whole decode step runs as one CUDA graph instead of a Python-driven
piecewise step. It is the fastest two-card recipe on code and prose and needs x16 links and P2P. Infobox numbers are
release 0.2.0, one user on code.
{{Source|handle=nathang6866|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563590746710478919|repo=https://github.com/ElectroHobo/qwen38-flash-next-w4a16-2x-cmp170hx-recipe}} 
{{Source|handle=nathang6866|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1561924044666839091}}

== Prerequisites ==
* Two CMP 170HX exposing 64 GiB on PCIe Gen2 x16 (the x16 capacitor mod) with peer-to-peer, content-checked at every start (<code><nowiki>P2P=auto</nowiki></code>). See [[Driver unlock]], [[Unlocks]], [[8 GB card]].
* An expert cannot be split across the two cards (INT4 scale groups are 128 wide, the expert inner width is 640) and the engine refuses pipeline parallel for the n-gram table, so TP2 with x16 links and P2P is required.
* NVIDIA driver 580 or newer, Docker with the NVIDIA Container Toolkit, about 130 GiB of disk.
* Host RAM: 96 GB with the table in RAM (48 GiB table, 64 GiB as allocated). With the table on disk (0.3.0) far less (the whole container ran capped at 22 GiB), but that needs the NVIDIA open kernel modules with HMM (<code><nowiki>nvidia-smi -q</nowiki></code> shows "Addressing Mode: HMM" on every card) and 48 GiB of SSD.
* Author's host: 2x Xeon E5-2697A v4 (Broadwell), 204 GiB RAM.
{{Source|handle=nathang6866|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563590746710478919|repo=https://github.com/ElectroHobo/qwen38-flash-next-w4a16-2x-cmp170hx-recipe}}

== Steps ==
<syntaxhighlight lang="bash">
git clone https://github.com/ElectroHobo/qwen38-flash-next-w4a16-2x-cmp170hx-recipe
cd qwen38-flash-next-w4a16-2x-cmp170hx-recipe
./start.sh # pull the engine image, fetch the model, start, wait for /health
</syntaxhighlight>
The first start compiles kernels and runs the RecoverSSM verify (about 22 minutes, the verify about 95 s); later starts
take 5 to 11 minutes. 0.3.1 sets <code><nowiki>PYTHONPYCACHEPREFIX=/cache/pycache</nowiki></code>, which cut start-to-/health from 414 s
to 304 s.

Pins: engine Morrowmake/vllm-cmp170hx at <code><nowiki>18305948acba3f4c4d912cdd56f2202d2ebd94e8</nowiki></code>, image
<code><nowiki>ghcr.io/morrowmake/vllm-cmp170hx@sha256:5b45c4d6feafefe2eba962375b0a9a0b64fd22b9e05abb4d1966f14a32a2db79</nowiki></code>;
checkpoint [https://huggingface.co/halt95/Qwen3.8-Flash-Next-W4A16-Merlin halt95/Qwen3.8-Flash-Next-W4A16-Merlin] at
<code><nowiki>cec53e9f</nowiki></code> (115.3 GiB); drafter [https://huggingface.co/incoai/Qwen3.8-Flash-Next-DFlash2 incoai/Qwen3.8-Flash-Next-DFlash2]
at <code><nowiki>a22a1744</nowiki></code> (Apache-2.0, 1.1 GiB).

The container command:
<syntaxhighlight lang="bash">
vllm serve /models/Qwen3.8-Flash-Next-W4A16-Merlin --tensor-parallel-size 2 --pipeline-parallel-size 1 \
--enable-expert-parallel --dtype bfloat16 --kv-cache-dtype bfloat16 --load-format auto --mm-encoder-tp-mode data \
--attention-config '{"indexer_kv_dtype":"bf16"}' --engram-config '{"cpu_offload":true}' \
--max-model-len 262144 --gpu-memory-utilization 0.95 --max-num-seqs 128 --max-num-batched-tokens 3460 \
--long-prefill-token-threshold 0 --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder \
--prefix-match-unit 16 --block-size 912 --mamba-ssm-cache-dtype bfloat16 \
--compilation-config '{"cudagraph_mode":"FULL_AND_PIECEWISE"}' \
--speculative-config '{"method":"dflash","model":"/drafter","num_speculative_tokens":7,"num_speculative_tokens_per_batch_size":[[1,2,7],[3,4,5],[5,32,3],[33,128,2]]}'
</syntaxhighlight>
Env: <code>VLLM_GDN_RECOVER=1 VLLM_USE_BREAKABLE_CUDAGRAPH=1 VLLM_QWEN4_QSA_TOPK_CANONICAL=1 VLLM_CUSTOM_ALLREDUCE_FLAGS=1
VLLM_THIN_GEMM=1 VLLM_THIN_GEMM_GLUON=1 VLLM_FLA_AUTOTUNE_SKIP_SPILLING=1 PYTORCH_CUDA_ALLOC_CONF=expandable_segments:False
CUDA_DEVICE_ORDER=PCI_BUS_ID</code>, plus <code><nowiki>VLLM_CUSTOM_ALLREDUCE_PCIE_P2P=1</nowiki></code> and <code><nowiki>NCCL_P2P_LEVEL=SYS</nowiki></code>
after the P2P check passes. <code><nowiki>MAX_LEN</nowiki></code> and <code><nowiki>GPU_UTIL</nowiki></code> are refused if changed.
{{Source|handle=nathang6866|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563590746710478919|repo=https://github.com/ElectroHobo/qwen38-flash-next-w4a16-2x-cmp170hx-recipe}}

=== The three differences from Morrowmake's EXL3 recipe ===
<code><nowiki>--load-format auto</nowiki></code> (theirs <code><nowiki>exl3</nowiki></code>), <code><nowiki>--engram-config '{"cpu_offload":true}'</nowiki></code> (theirs false)
and <code><nowiki>cudagraph_mode FULL_AND_PIECEWISE</nowiki></code> (theirs PIECEWISE). On a Broadwell host the EXL3 recipe's mid-step SSD
n-gram read costs about 44 ms per step (55 to 70 tok/s for one user against its published 153); with the table in RAM
and full graphs the step drops to 15 ms. PIECEWISE is about 3x slower per step on an old CPU.
{{Source|handle=nathang6866|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563590746710478919|repo=https://github.com/ElectroHobo/qwen38-flash-next-w4a16-2x-cmp170hx-recipe}}

=== Engine patches mounted over the image ===
DFlash 2 capture hook (Eagle3 auxiliary layers 6, 16, 26, 36, 46); RecoverSSM for the Gated DeltaNet layers (one
recurrent state per request instead of one per draft position, checked bitwise; 128 requests fit at 94% of the pool
where 28 of 48 did before; <code><nowiki>RECOVER_SSM=0</nowiki></code> reverts); a shared n-gram table loader (<code><nowiki>PLE_SHARED_DIR</nowiki></code> on
tmpfs lets several servers share one 48 GiB copy); chunked copy-on-write (256 MiB chunks, fixes a
<code><nowiki>torch.OutOfMemoryError</nowiki></code> under bursts of shared prompts). All pinned to engine commit 18305948ac.
{{Source|handle=nathang6866|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563590746710478919|repo=https://github.com/ElectroHobo/qwen38-flash-next-w4a16-2x-cmp170hx-recipe}}

== Measured numbers ==
Release 0.2.0, fresh clone 2026-10-23, 74 SMs, 180 W, PCIe x16, P2P on, MiaAI-Lab protocol. Tok/s structured / code /
prose:
{| class="wikitable"
! !! DFlash 2 (default) !! MTP (<code><nowiki>SPEC_MODE=mtp</nowiki></code>)
|-
| 1 user || 241.2 / 349.7 / 198.4 || 208.1 / 242.9 / 184.1
|-
| 2 users || 374.4 / 489.3 / 288.4 || 330.4 / 387.7 / 299.0
|-
| 4 users || 556.2 / 730.8 / 489.1 || 538.2 / 569.0 / 476.5
|-
| 8 users || 894.5 / 986.8 / 769.7 || 841.7 / 829.3 / 728.4
|-
| 128 users (700 tokens) || 1,937 || 1,966
|-
| Cold prefill || 4,696 || 4,520
|-
| KV pool || 1,475,836 || 1,438,968
|}
Code editing, one user: 495 tok/s. Quality (thinking on): HumanEval 162/164, GSM8K 198/200 (first 200). DFlash 2 is
44% faster than MTP on code for one user and 83% faster editing code; MTP pulls ahead from about 32 users.

Table on disk (0.3.0), disk against RAM: 1 user 232.8 / 344.4 / 199.3 against 234.9 / 358.6 / 200.8; 128 users 1,851
against 1,934; cold prefill 4,000 against 4,723. FP8 KV (not default): pool +73% (2,578,229 tokens), one-user decode
-8 to -10%, answers shift. KV offload to a 64 GiB RAM tier brings an evicted 100k-token context back in 0.89 s instead
of 21 to 22 s of re-prefill.
{{Source|handle=nathang6866|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563590746710478919|repo=https://github.com/ElectroHobo/qwen38-flash-next-w4a16-2x-cmp170hx-recipe}}

* Release 0.1.0 (2026-10-20): 253 / 349 / 203 tok/s for one user, 497 tok/s editing code, 842 / 992 / 727 at 8 concurrent, 1.4M-token KV. Miséricorde confirmed the inco.ai drafter, published that day, actually helps. {{Source|handle=nathang6866|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1561924044666839091}} {{Source|handle=wakeupmbrc1|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1561924555486920825}}
* The 2026-10-24 update tuned for concurrency: 1,814 tok/s at 128 requests. {{Source|handle=nathang6866|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563590746710478919}}
* The lab ran release 0.2.0 on its box (Gen2 x16, P2P, 1,024-token answers): one user code 263, structured 266, prose 215; 8 users 916 / 961 / 729; prefill 4.6k on a 17k prompt; 53% draft acceptance; vision works. Four instances at once (two cards each, one shared 48 GiB table in <code><nowiki>/dev/shm</nowiki></code>, 77 GiB of host RAM for all four) each kept 90 to 100% of their lone speed: box aggregate at 32 users 3,617 / 3,316 / 2,664 tok/s and 17.4k tok/s prefill. {{Source|handle=darkmaniac7|date=2026-10-28|note=lab notes}}

=== Other two-card recipes on the same protocol ===
Numbers from their READMEs (as of 2026-10-19), not re-run by ElectroHobo:
{| class="wikitable"
! !! This recipe (TP2, x16) !! AlexBrandes (PP2, x4, table on NVMe) !! mannydelrio (PP2, x4, 4-bit table on SSD)
|-
| 1 user || 241.2 / 349.7 / 198.4 || 250.8 / 226.2 / 157.4 || 192.4 / 177.8 / 145.4
|-
| 8 users || 894.5 / 986.8 / 769.7 || 999.5 / 840.4 / 566.8 || 986.4 / 734.2 / 619.6
|-
| Cold prefill || 4,696 || 6,300 to 7,100 || 7,006
|}
This recipe leads on code and prose; the PP2 recipes read prompts 33 to 50% faster and run on stock x4 cards. See
[[Qwen3.8 Flash Next on 2x 8 GB (mannydelrio PP2)]].
{{Source|handle=nathang6866|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563590746710478919|repo=https://github.com/ElectroHobo/qwen38-flash-next-w4a16-2x-cmp170hx-recipe}}

== Known issues ==
* Decode is power-bound at 180 W (cards at 1,400 to 1,499 MHz); clock locks do nothing.
* Community recipe, not tested or endorsed by Morrowmake or halt95; measured on one Broadwell host. The engine image is pinned by digest and the patches to engine commit 18305948ac, so a new engine release needs them re-made. 0.3.0 (table on disk) had not served real traffic at release.
* <code><nowiki>KV_OFFLOAD_DIR</nowiki></code> is write-through and never pruned (one benchmark run wrote 58 GB).
* '''P2P on other unlock builds.''' galygious2 found the recipe promising for x16-modded cards but saw it needs P2P, and asked whether anyone has P2P working with Amogh's unlock. ElectroHobo had P2P working with an older method, and thinks Morrowmake's vLLM fixes it for many people on supported hardware. Setups where P2P still fails are on [[P2P]] and [[Risers and bifurcation]]. {{Source|handle=galygious2|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563940267365507132}} {{Source|handle=nathang6866|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564023832107417662}}
{{Source|handle=nathang6866|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563590746710478919|repo=https://github.com/ElectroHobo/qwen38-flash-next-w4a16-2x-cmp170hx-recipe}}
* Keep vLLM's custom all-reduce on with this recipe: on the lab box turning it off cost 17 to 25% single-stream and 12 to 15% at 8 users. This is the opposite of what it measured for GLM 5.3 Flash TP4 (see [[GLM 5.3 Flash on 4x 8 GB]]). {{Source|handle=darkmaniac7|date=2026-10-28|note=lab notes}}
* Copying another instance's <code><nowiki>cache/</nowiki></code> directory can carry stale build locks that hang custom all-reduce at init; let each instance compile its own. {{Source|handle=darkmaniac7|date=2026-10-27|note=lab notes}}

== Variants ==
* Uncensored base in the same Merlin layout: ntmcgee/Orca-Qwen3.8-Flash-Next-W4A16-Merlin (its FP8 table differs byte-wise, so it needs its own 48 GiB shared table), or halt95/Swift1.5-Huihui-Qwen3.8-Flash-Next-W4A16-Merlin, which shares the base table. Neither had been run on this engine as of 2026-10-27. Switch with <code><nowiki>TARGET_REPO</nowiki></code>, <code><nowiki>TARGET_REVISION</nowiki></code> and <code><nowiki>MODEL</nowiki></code> in <code><nowiki>.env</nowiki></code>. {{Source|handle=darkmaniac7|date=2026-10-27|note=lab notes}}
* One card: [[Qwen3.8 Flash Next on 1x 8 GB (ElectroHobo 3 bpw)]] (shares the engine, patches and table).

== Sources ==
* Repo: [https://github.com/ElectroHobo/qwen38-flash-next-w4a16-2x-cmp170hx-recipe ElectroHobo/qwen38-flash-next-w4a16-2x-cmp170hx-recipe] (MIT; engine Apache-2.0; checkpoint Qwen Community License 1.0). Releases 0.1.0 (2026-10-19, as qwen38-flash-next-w4a16-cmp170hx-recipe, which redirects), 0.2.0 (2026-10-24), 0.3.0 and 0.3.1 (2026-10-28).
* Related: [[Engines]], [[Quantization on the 170HX]], [[Benchmarks]].

{{ImportFooter}}
[[Category:8 GB]]

Quantization on the 170HX

2026-10-31T21:34:40Z

ImportBot: Import: Quant formats on sm_80 CMP cards (W4A16, W8A16/W8A8, EXL3 bpw choices, FP8 and FP4 handling, KV cache formats, PLE and Engram tables), what fits in 64 and 80 GB per card, heretic and abliterated variants; from Discord, the recipe repos and lab notes; sources: @wakeupmbrc1, @gnasherrr, @programmerboi, @xeax, @nathang6866, @dale063629, @c133, @darkmaniac7, @anon33anon, @cibernox, @nestaa51, @wingrimez_40467 (+19 more); GitHub CurtisAccelerate/DeepSeekv41-Flash-1017-EXL3

The CMP 170HX is sm_80: it has INT8 and INT4 tensor cores and BF16/FP16, but no FP8 or FP4 hardware. That decides which
quants are fast. This page collects what people measured; the per-model setups are on the [[Recipes]] pages and every
number is on [[Benchmarks]].

== The short version ==
* '''Use INT4 weights with 16-bit activations (W4A16)''' served through vLLM's sm_80 Marlin kernels. It is what most people run, and the CMP gets large speedups on INT4/INT8 over regular GGUF-style quants. {{Source|handle=wakeupmbrc1|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559796095750639798}} {{Source|handle=gnasherrr|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564318714722254939}}
* All Ampere chips support INT4 at twice the theoretical INT8 throughput (about 1.2 PFLOPS on this die), even though NVIDIA's A100 page lists only INT8. Choose INT4 or INT8 by the model's quantization quality curve, and always use the quantization kernels. {{Source|handle=programmerboi|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559807103491907668}} {{Source|handle=programmerboi|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559797761019486299}}
* W8A16 costs about 30% against W4A16 on Qwen3.8 27B. W8A8 is slightly higher quality. {{Source|handle=wakeupmbrc1|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559918772268171379}} {{Source|handle=xeax|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560268172081365042}}
* FP8 and FP4 checkpoints still run, but as weight-only formats: NVFP4 runs through Marlin as 4-bit weights with BF16 activations (MiMo V2.6 Flash); official MXFP8 dense layers run as Marlin W8A16 and MXFP4 experts as W4A16 (DeepSeek V4.1 Flash); FP8 KV caches are stored as uint8 and decoded in software. NVFP4 GLM checkpoints that need SM12x FlashInfer do not run. {{Source|handle=nathang6866|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1561264547455569952|repo=https://github.com/ElectroHobo/mimo-v26-flash-cmp170hx-recipe}} {{Source|handle=dale063629|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561547352693538856|repo=https://github.com/wgkbfcp/deepseek-v4.1-flash-1017-cmp170hx-recipe}} {{Source|handle=c133|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562161732137386127|repo=https://github.com/PixelML/club-170hx}}
* What runs on GA100 (sm_80), from PixelML's and allover326's notes: AWQ/GPTQ INT4 through Marlin, weight-only FP8 through the Marlin fallback, INT8 W8A8 through CUTLASS, FP8 KV cache (software conversion, costs throughput), BF16, MXFP4-stored experts dequantized. What does not: native NVFP4/MXFP4 or FP8 tensor-core math (Hopper and Blackwell only), DeepGEMM TF32, CuteDSL kernels, Triton <code><nowiki>fp8e4nv</nowiki></code> stores, TileLang FP8 x FP4 GEMM. On PixelML's pool NVFP4 checkpoints widened on load to about 60 GiB per card and ran out of memory, so they prefer AWQ W4A16; gate fast paths on compute capability, not on whether a package is installed. Sources: [https://github.com/PixelML/club-170hx PixelML/club-170hx], [https://github.com/allover326/vllm-dsa-mtp-sm80 allover326/vllm-dsa-mtp-sm80]. {{Source|handle=darkmaniac7|date=2026-09-05|note=lab notes}}
* Stock engines want compute capability 9.0 for ModelOpt FP8 and NVFP4 checkpoints; on the CMP they run only through an engine that routes them to Marlin weight-only kernels (Morrowmake's fork does). {{Source|handle=darkmaniac7|date=2026-10-20|note=lab notes}}

== EXL3 ==
EXL3 (turboderp's trellis format) gives the best size for the quality, which is why the two-card GLM and the four-card
DeepSeek recipes use it.
* {{Status|Proven}} Quality: EXL3 at 3 bpw performs close to other 4-bit quants (anon33anon); a 3.5 bpw EXL3 quant is virtually indistinguishable from W4A16 or Q4_K_L on medium and large models, with differences possibly more visible under 30B (cibernox). The GLM 3.05 bpw quant is an average with the important parameters at higher precision (Nestaa51). {{Source|handle=anon33anon|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1559506822111694894}} {{Source|handle=cibernox|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1559513516585779303}} {{Source|handle=nestaa51|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1559384024491761846}}
* {{Status|Contested}} Speed: EXL3 decode is compute-bound on sm_80 in ExLlamaV3; inside the vLLM forks with tensor-core MoE kernels it is much faster. See [[Engines#ExLlamaV3, TabbyAPI and EXL3]].

=== bpw choices that people use ===
{| class="wikitable"
! Model !! Quant !! Cards !! Notes
|-
| GLM-5.3-Flash || turboderp EXL3 3.05 bpw (about 116.6 GiB resident) || 2 || [[GLM 5.3 Flash on 2x 8 GB (ExLlamaV3 TP2)]]
|-
| Qwen3.8-Flash-Next || turboderp EXL3 5.05 bpw (0.0040 KLD from BF16) || 2 (or 1 with offload) || Morrowmake chose 5.05 because a 1M KV cache still fit
|-
| DeepSeek-V4.1-Flash-1017 || LibertAI EXL3 2.9 bpw routed experts (layers 18-22 at 2 bpw) + official FP8 dense || 4 || the hybrid used by Morrowmake, GNmac and CurtisAccelerate
|-
| DeepSeek-V4.1-Flash-1017 || 2.9 bpw pack with layers 18-22 grafted from the 3.5 bpw pack (all experts 3-bit) || 4 || alanoo: perplexity -1.80% overall, -4.45% French, +1.98 GiB per card
|-
| DeepSeek-V4.1-Flash-1017 || LibertAI EXL3 3.5 bpw || 4 + RTX PRO 6000, or 6 || does not fit four 64 GB cards
|-
| GLM-5.3 (full) || EXL3 3.05 bpw || 4 + RTX PRO 6000 || 30 tok/s (Mountains); under 300 GB, so four 80 GB cards would hold it
|}
{{Source|handle=wingrimez_40467|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1562164200372179017|repo=https://github.com/Flun/glm53-flash-cmp170hx-exl3}} 
{{Source|handle=tekkenz|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1557126972360884366}} 
{{Source|handle=alanoo|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1564681525365186711|repo=https://github.com/alanoo81/deepseek-v41-flash-4x-cmp170hx}} 
{{Source|handle=anon33anon|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561903682608697426|repo=https://github.com/anoane/09-deepseek-v41-flash-1017-exl3-tp5-1m}} 
{{Source|handle=stcord|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558098919249150063}}

=== DeepSeek V4.1 Flash on four cards: how many bits ===
* Miséricorde: on 4 cards (256 GB) 3.1 bpw is the maximum; the early LibertAI 2.9 and 3.5 bpw quants are uncalibrated and 2.9 is too aggressive (important tensors dequantized too much); a properly calibrated 3 to 3.1 bpw gives very low perplexity and KLD. W4A16, NVFP4 and MXFP4 do not fit four cards, so the quant is mostly EXL3: decent at concurrency 4 to 8, not amazing at 1. {{Source|handle=wakeupmbrc1|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1561136859457917009}} {{Source|handle=wakeupmbrc1|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1561136712846020619}} {{Source|handle=wakeupmbrc1|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1561916569590702201}}
* HeNryous' calibrated 2.75 bpw measures 0.0201 / 95.96% (almost lossless). {{Status|Theory}} Miséricorde's plan: keep some hot experts in MXFP4 in the 20 to 25 GB that 2.75 bpw leaves free across four cards. {{Source|handle=wakeupmbrc1|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1561918179763298376}} {{Source|handle=wakeupmbrc1|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561908506746167410}}
* cibernox thinks a good 3 to 3.2 bpw is achievable in 256 GB; Gnasherrr: possible with heavy 2.9 bpw quants, and a fifth card does not help. {{Source|handle=cibernox|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562167583476809739}} {{Source|handle=gnasherrr|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562160670508720159}}
* Native MXFP4 weights would beat INT autocalibration in quality, but sm_80 has no MXFP4 support; a W4A16 (INT4) quant would decode much faster than EXL3, as it did for the previous DeepSeek. {{Source|handle=wakeupmbrc1|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561911726386057247}} {{Source|handle=anon33anon|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562015317117509656}}
* Miséricorde on the first day of 1017: it fits four cards at 3 to 3.5 bpw with decent quality, especially as EXL3, but on the slower side. {{Source|handle=wakeupmbrc1|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1560957672642183260}}
* Accuracy of the 2.9 bpw pack: code perplexity 1.9094 against 1.8749 unquantized (+1.8%), prose 6.4520 against 6.4277 (+0.4%) for the full-trunk pack; the hybrids quantize only the routed experts. KLD for the Mia-AiLab EAQ v1 2.9 bpw pack is on its model card. {{Source|handle=anon33anon|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561910289799184445|repo=https://github.com/CurtisAccelerate/DeepSeekv41-Flash-1017-EXL3-CMP170HX}} {{Source|handle=greencandle9753|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562927286968262689}}
* reala found the 3.5 bpw EXL3 on six cards kept making silly tool-call mistakes, which the original FP4 weights did not. {{Source|handle=reala7096|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562899649256489011}}

== Group size, MTP heads and n-gram tables ==
* {{Status|Contested}} Group size for Qwen3.8 Flash Next 4-bit: aleksandartsvetanov argues G32 over G128, since G128 saves VRAM and compute but loses too much quality outside benchmarks; he calls G128 a trade-off, not obsolete. Most W4A16 checkpoints in the recipes use G128 for experts; mannydelrio's AWQ uses G32. {{Source|handle=aleksandartsvetanov|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1557733392773021757}}
* An INT4 MTP head has a much smaller footprint and runs faster, with a worse acceptance rate that balances out. {{Source|handle=aleksandartsvetanov|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1557733392773021757}}
* '''Qwen3.8 Flash Next's PLE (n-gram) table''' is 51B parameters of the model (about 125B in all): about 100 GB in BF16 against 70 GB for the W4A16 weights. Options: BF16 (aleksandartsvetanov: anything else is not worth discussing), FP8 (48 GiB; vektorprime measured KLD 0.0163 and 95.98% top-1 against BF16), INT4 (about 26.8 to 29.8 GB; zankich's INT4-PLE g32 and mannydelrio's tinybeast plugin). clee: with the table on NVMe there is no reason to quantize it; BF16 over NVMe was not noticeably slower than FP8. {{Source|handle=vektor_prime|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1557443747892035674|repo=https://github.com/vektorprime/qwen38-flash-next-pp2}} {{Source|handle=c133|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1557602145052921867}} {{Source|handle=_arcanum_|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1558838584000258119}} {{Source|handle=wakeupmbrc1|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1558843643245109302}}
* Where the table lives: from RAM a lookup costs about 0.3 ms per token, from SSD 1 to 1.5 ms (SSD dependent). RAM speed hardly matters because the lookups are latency-bound; RAM against NVMe does, because NVMe latency adds up every round (about 1.5 ms per round on Qwen Flash Next; DeepSeek V4.1 calls its tables only in layers 1 and 14, so about 0.2 to 0.3 ms). {{Source|handle=wakeupmbrc1|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1558843833285087285}} {{Source|handle=wakeupmbrc1|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560993926201085984}}
* Asked who runs DeepSeek Flash with its n-gram tables on NVMe instead of RAM, clee answered: not DeepSeek, but Qwen3.8 Flash Next yes. (Several DeepSeek recipes now read Engram from SSD; see their pages.) {{Source|handle=stcord|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564739554030911499}} {{Source|handle=c133|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564740171532869684}}
* '''DeepSeek V4.1's Engram tables''' are about 189 GiB (the last two official shards). Turning Engram off raises code perplexity from 1.91 to 4.16 and prose from 6.45 to 9.06, so they are not optional. Morrowmake measured SSD placement with a 38 GiB cache at 6% later first token on a cold 2K prompt and decode within 1%. {{Source|handle=anon33anon|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561910289799184445|repo=https://github.com/CurtisAccelerate/DeepSeekv41-Flash-1017-EXL3-CMP170HX}} {{Source|handle=lia_oc|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563528168688586764|repo=https://github.com/Morrowmake/dsv41-flash-cmp170hx-recipe}}

== KV cache formats ==
* '''GLM 5.3 Flash:''' Morrowmake's recipe keeps the KV cache at full precision (1.2M tokens on four cards). FP8 KV would roughly double it; cibernox finds FP8 KV quality still very good. 1a2b3c0967 credits the 16-bit KV for the model staying sharp at high context; Morrowmake: research shows basically no loss but people report otherwise. Shirogeek runs 8-bit KV on three cards for about 1M context. {{Status|Contested}} {{Source|handle=1a2b3c0967|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556142317566431303}} {{Source|handle=voidgiraffe|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556142515491704976}} {{Source|handle=cibernox|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1560685197618323570}}
* '''Qwen3.8 Flash Next:''' FP8 KV grows the pool 73% but costs 8 to 10% one-user decode and shifts answers (ElectroHobo, not default); clee stores FP8 KV as uint8 with software e4m3 decode; vLLM 0.30.0's QSA path rejects an FP8 cache. {{Source|handle=c133|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1556357466026025001|repo=https://github.com/clee/qwen3.8-flash-next-3x170hx}} {{Source|handle=nathang6866|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563590746710478919|repo=https://github.com/ElectroHobo/qwen38-flash-next-w4a16-2x-cmp170hx-recipe}}
* '''DeepSeek V4.1 Flash:''' the native KV is FP4 at about 0.9 KB (890 B) per token per TP unit, so a 1M-token KV costs about 3.6 GiB at TP4 and 1.8 GiB at TP2 x PP2, but there is no sm_80 build of that format. GNmac's <code><nowiki>fp8_ds_mla</nowiki></code> writes the DeepSeek V4 record (448 FP8 dims, one scale per 64) because V4.1's <code><nowiki>nvfp4_ds_mla</nowiki></code> needs SM100; Morrowmake's BF16 KV reproduces the reference's rounding bit for bit. {{Source|handle=wakeupmbrc1|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561016701364211743}} {{Source|handle=wakeupmbrc1|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1561138546989867129}} {{Source|handle=wakeupmbrc1|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561907315953897523}} {{Source|handle=alanoo|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1564681525365186711|repo=https://github.com/alanoo81/deepseek-v41-flash-4x-cmp170hx}}
* {{Status|Theory}} Miséricorde suggests assembling an FP4 KV cache for DeepSeek V4.1 1017 to reach 5M+ tokens on four cards (DeepSeek only, not GLM). {{Source|handle=wakeupmbrc1|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1561796404446367916}}
* '''Full GLM 5.3:''' packed <code><nowiki>fp8_ds_mla</nowiki></code> at 656 B per token per layer plus FP8 indexer keys (vllm-170hx-glm5). On the lab's eight-card run the int8 KV tile matched plain FP8 in quality and was 10% faster single-stream. {{Source|handle=reala7096|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1557544812972871813|repo=https://github.com/arvkmr/vllm-170hx-glm5}} {{Source|handle=darkmaniac7|date=2026-10-28|note=lab notes}}

== What fits ==
Per card, an unlocked 8 GB-variant card exposes 64 GiB ([[8 GB card]]). Weight footprints from the recipes:
{| class="wikitable"
! Model and quant !! Weights !! Fits on !! Recipe
|-
| Qwen3.8 27B W4A16 || not stated || 1 card, about 3 concurrent requests at native context with FP8 KV || [[Qwen3.8 27B on 1x 8 GB (W4A16 vLLM)]]
|-
| Qwen3.8 Flash Next AutoRound mixed 2/3-bit || 47 GiB on card, table in host RAM || 1 card || [[Qwen3.8 Flash Next on 1x 8 GB (ElectroHobo 3 bpw)]]
|-
| Qwen3.8 Flash Next W4A16 (Merlin) || 115.3 GiB incl. FP8 table || 2 cards with the table in host RAM || [[Qwen3.8 Flash Next on 2x 8 GB (ElectroHobo W4A16 TP2)]]
|-
| Qwen3.8 Flash Next W4A16 AutoRound || about 169 GiB incl. BF16 table || 3 cards with the table streamed from NVMe || [[Qwen3.8 Flash Next on 3x 8 GB (clee PP3)]]
|-
| GLM-5.3-Flash EXL3 3.05 bpw || 116.6 GiB || 2 cards, 393K context || [[GLM 5.3 Flash on 2x 8 GB (ExLlamaV3 TP2)]]
|-
| GLM-5.3-Flash W4A16 (about 4.3 bpw) || 163 GiB || 3 cards, 8-bit KV || [[GLM 5.3 Flash on 3x 8 GB]]
|-
| GLM-5.3-Flash W4A16 (canada-quant) || about 178 GiB || 4 cards, BF16 KV || [[GLM 5.3 Flash on 4x 8 GB]]
|-
| MiMo-V2.6-Flash NVFP4 || 183 GiB (45.5 GiB per card) || 4 cards || [[MiMo V2.6 Flash on 4x 8 GB]]
|-
| DeepSeek-V4.1-Flash hybrid (EXL3 2.9 bpw experts) || about 62.5 GB used per card, Engram in host RAM or on SSD || 4 cards || [[DeepSeek V4.1 Flash on 4x 8 GB (Morrowmake)]]
|-
| DeepSeek-V4.1-Flash official FP8 / FP4 || about 475 GiB || 6 or 8 cards || [[DeepSeek V4.1 Flash on 8x 8 GB (Zanooda PP8)]]
|-
| GLM-5.3 Int4-Int8Mix || about 8 to 10 cards of weights and KV || 8 to 10 cards || [[GLM 5.3 on 8x 8 GB (vllm-170hx-glm5)]]
|}

80 GB per card: {{Status|Theory}} with an 80 GB unlock, four cards (320 GB) would hold the full GLM 5.3 EXL3 quant.
The 8 GB variant cannot reach 80 GB (four HBM stacks of 16 GB = 64 GB). For the 10 GB card's memory, see
[[10 GB card]].
{{Source|handle=globalapathy|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558099082743128095}} 
{{Source|handle=mrmannyatx|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1557099855242072094|repo=https://github.com/mannydelrio/qwen38-flash-next-2x-cmp170hx}}

== Heretic and abliterated variants ==
Refusal-removed models are popular here. Two ways to get one: a published abliterated checkpoint, or an edit applied to
the official weights (or at runtime).
* '''DeepSeek V4.1 Flash heretic''' (pqhaz/DeepSeek-V4.1-Flash-1017-heretic): edits only the 38 <code><nowiki>attn.wo_b</nowiki></code> tensors (rank-1 along published refusal directions, FP8 re-encoded, scales unchanged), so it drops into the hybrid recipes with no requantization. Model card: 1 refusal in 100 held-out prompts (base 97), KL 0.136 on harmless prompts, median completion 1,517 tokens against 357. The lab's weight-level check found nothing beyond the advertised edit plus FP8 rounding. See [[DeepSeek V4.1 Flash heretic on 4x 8 GB]]. Alternatives the lab did not use: mrfakename's rank-2 edit (lowest KL, needs your own apply) and dealignai's FP8 build (MMLU -3.9); "uncensored" EXL3 bundles whose edit lives in dense tensors do nothing on engines that take dense tensors from the official checkpoint. {{Source|handle=darkmaniac7|date=2026-10-29|note=lab notes}}
* '''GLM 5.3 Flash:''' the lab runs an abliterated W4A16 + MTP checkpoint on the Morrowmake recipe; vision and video still work. The Weightless GLP-44 vector (msuiche, gated on Hugging Face) steers refusals at runtime and is ported to the ExLlamaV3 TP2 build; alpha 2.0, and 2.5 or more garbles the model. Nestaa51 runs stock GLM and wants to try Weightless. Project Maya ships a Maya-M-Derisked GLM quant. {{Source|handle=mountains1605|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1558154558625153034|repo=https://github.com/msuiche/weightless}} {{Source|handle=nestaa51|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1559884044768911471}} {{Source|handle=darkmaniac7|date=2026-10-27|note=lab notes}}
* '''Making your own W4A16 abliterated GLM-5.3-Flash''' (lab notes, 2026-10-19): pull dealignai/GLM-5.3-Flash-UNCENSORED-FP8 (328 GB), dequantize the block-FP8 to BF16 (703 GB, so the source must sit in host RAM), then run llm-compressor's GPTQModifier one-shot to the canada-quant format: compressed-tensors pack-quantized INT4, group size 128, symmetric, static act-order, no activation or KV quantization, and only the routed-expert gate/up/down projections quantized (ignore lm_head, embeddings, the MTP layer 45, every <code><nowiki>mlp.gate</nowiki></code>, all attention and indexer weights, shared experts, the dense MLPs of layers 0-2, the vision tower and the hyper-connection projections). Calibration: 512 samples x 2,048 tokens of HuggingFaceH4/ultrachat_200k. It ran 271 minutes on one RTX PRO 6000 of a rented 4-GPU node with 1.5 TB host RAM, about 113 USD; output 164 GB in 9 shards (MTP head not saved; not needed with DFlash2). On four CMPs at TP4 with DFlash2 it passed the boot check (671 of 675 drafts accepted) and runs at 88-97% of the base's speed (one user 349 / 254 / 181 against 361 / 284 / 199); code loses most because the drafter was trained on the base model. {{Source|handle=darkmaniac7|date=2026-10-19|note=lab notes}}
* {{Status|Reported}} Cost of abliteration, from the lab's multi-turn test: all three abliterated GLM builds it ran followed a deliberately wrong hint where stock DeepSeek refused it. The non-abliterated GLM has not been run on the same test yet, so the cost is not isolated. {{Source|handle=darkmaniac7|date=2026-10-28|note=lab notes}}
* '''Full GLM 5.3:''' dealignai/GLM-5.3-ABLITERATED-NVFP4 (the lab requantized it to NVFP4 experts plus INT8 for sm_80); vllm-170hx-glm5's <code><nowiki>serve-uncensored.sh</nowiki></code> swaps in a GLM-5.3-UNCENSORED-Int4-Int8Mix checkpoint. {{Source|handle=reala7096|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1557544812972871813|repo=https://github.com/arvkmr/vllm-170hx-glm5}} {{Source|handle=darkmaniac7|date=2026-10-28|note=lab notes}}
* '''Qwen3.8 Flash Next:''' the huihui "decision matrix" abliteration on top of Plean's recipe (GalyGames); OrcaRouter's uncensored base in several quants (leoncca AWQ g32 used by mannydelrio, klee100's uncensored AutoRound 3 bpw, ntmcgee's Orca Merlin W4A16); halt95's Swift1.5-Huihui Merlin W4A16, which shares the base n-gram table byte for byte. 68x needed an uncensored variant to get MTP working on clee's setup. {{Source|handle=mrmannyatx|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1557099855242072094|repo=https://github.com/mannydelrio/qwen38-flash-next-2x-cmp170hx}} {{Source|handle=galygious|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1557608614318047253}} {{Source|handle=68x0|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1558918008859267103}}
* '''Qwen3.8 27B:''' Phoenix17's Swift-1.5-Qwen3.8-27b-heretic-W8A8-DFlash2; kellertreppe123's own AutoRound requant of the huihui variant ran at 60 to 70 tok/s against about 170 for the stock W4A16 recipe. {{Source|handle=phoenixone7|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556455316307316776}} {{Source|handle=kellertreppe123|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1556774302961897675}}
* {{Status|Contested}} Pruning: REAP-pruned models do not work without post-training to restore quality (orrorin, on Qwen); REAP builds show DeepSeek V4.1 prunes quite well and 20% pruning is enough, so light pruning plus MXFP4 may be a good idea (Miséricorde). Weightless steering vectors are rejected on REAP builds because removing experts changes the circuit the vector was derived on. {{Source|handle=mountains1605|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1558154558625153034|repo=https://github.com/msuiche/weightless}} {{Source|handle=_orrorin|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558674536701100145}} {{Source|handle=wakeupmbrc1|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561017626006790246}} {{Source|handle=wakeupmbrc1|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561017678372544643}}

== Related ==
[[Recipes]] · [[Engines]] · [[Benchmarks]] · [[8 GB card]] · [[10 GB card]] · [[Driver unlock]] · [[Tools]]

{{ImportFooter}}
[[Category:Recipes]]

Power supplies and cabling

2026-10-31T21:34:39Z

ImportBot: The CMP 170HX power input, cable rules, connector ratings, PSU sizing per card count, burned and failed hardware, wall power; from the cmpunlocker Discord (2026-10-04 to 10-27, including the asrock PG-1600g thread), PixelML/club-170hx and lab notes; gap-fill from #general 2026-10-23 (400 W spike at a 250 W limit), @djpandaman, @xeax

The CMP 170HX takes all its power through one EPS12V socket. Most failures in the Discord came from feeding that
socket wrongly: one PSU cable split two ways, pigtails, thin adapters, or a modular cable from a different PSU brand.
Read the rules below before you plug anything in. Burned and failed hardware is collected under
[[Power and cabling warnings]].

== The power input ==
* {{Status|Proven}} The card has a single EPS12V 8-pin socket (the "CPU 8-pin": 4x 12 V and 4x ground), not a PCIe 8-pin. The pinouts differ even though the plugs look alike. {{Source|handle=wakeupmbrc1|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558163640446619709}} {{Source|handle=civiloid|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560436414829559809}}
* The 2x PCIe 8-pin to EPS adapter that comes with many cards is not for redundancy: the card draws through both inputs, each feeding half of the socket. {{Source|handle=reala7096|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560434233871171615}} {{Source|handle=civiloid|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560436414829559809}}
* {{Status|Proven}} A CPU (EPS12V) cable straight from the PSU works and needs no adapter. {{Source|handle=analyticeth|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558175554165940368}} {{Source|handle=ropuls|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558183124129808405}} Plug it into a PSU output labelled PCIe/CPU (or CPU). {{Source|handle=reala7096|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560434592928895057}} Corsair's "CPU 8-pin" and EPS differ only in the width of the locking tab. {{Source|handle=civiloid|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560437065844392039}}
* The latch: most EPS cables have the double-width 4+4 latch (for compatibility with old 4-pin EPS boards), which does not clip onto the card. Trim it with a bandsaw or a rotary tool. {{Source|handle=civiloid|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558217306167844906}} {{Source|handle=ropuls|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558219569946955830}} {{Source|handle=c133|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561564052306526299}} EPS-to-EPS cables bought from Amazon or PC Case Gear also needed "5 minutes with a dremel" to fit {{Source|handle=zarquon3157|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564587334882697299}}; @danske1 bought eight EPS-to-EPS cables (with a Gigabyte chassis) from an [https://www.ebay.com.au/itm/800469481794 eBay Australia seller]. {{Source|handle=danske1|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564601521927233633}}
* Right-angle adapters are only sold in PCIe form: a [https://www.amazon.com/SinLoon-Extension-Express-Power-Graphics/dp/B0D1VBYBXB SinLoon PCIe right-angle extension] "won't fit; you need a PCIe to CPU 4+4 cable", so @boz._. is splicing one onto an EPS cable. {{Source|handle=boz._.|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560431149048922203}} {{Source|handle=reala7096|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560433099001696257}}

== Cable rules ==
# '''One EPS cable per card''', straight from the PSU. This is the simplest and safest option. {{Source|handle=jjb01957|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561553832176255036}} {{Source|handle=.henrykrinkle|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561570495030108253}}
# '''Or two completely separate PCIe 8-pin cables''' into the two inputs of the PCIe-to-EPS adapter. Every adapter input needs its own cable back to the PSU. {{Source|handle=c133|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561551536994132139}} {{Source|handle=endsjeremy|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561578794983366737}}
# '''Never''' plug one PSU cable into both adapter inputs, and never use the 6+2 pigtails that hang off a PCIe cable for anything else. {{Source|handle=endsjeremy|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561361091450372137}} {{Source|handle=con3po7016|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561553067290136629}} This is not about PSU wattage: "other users here have already proven that this is not safe". {{Source|handle=c133|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561572630480293939}} @froggao ran a Corsair RM1000e with one 8-pin to dual 8-pin cable and said it worked; the group's answer was that poor wires, poor contact and high power limits combine, and that separate cables are required, not just safer. {{Source|handle=froggao|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561576491727331419}} {{Source|handle=wakeupmbrc1|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561578263732551804}} {{Source|handle=endsjeremy|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561578431982870619}} The opposite advice was given earlier in the same thread: @squishysquare said he would be comfortable using both the 8-pin and the 6+2 pigtail of one cable for one EPS adapter (but would not run the 300 W VBIOS); the posts above, from the next day, advise against exactly that. {{Source|handle=squishysquare|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561332642358493296}} {{Source|handle=squishysquare|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561332714840260660}}
# '''Never use 6-pin to 8-pin adapters.''' A 6-pin carries the same three 12 V terminals as a 6+2, but its cable is not built for the load. {{Source|handle=wakeupmbrc1|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1561161829311324191}} {{Source|handle=civiloid|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1561173569843503147}} Use two 6+2 cables into the EPS adapter or build proper EPS cables. {{Source|handle=neapopa|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1561127991713599499}}
# '''Meter the PSU side before you use a cable from another brand.''' Modular connector housings fit across brands while the pinout does not: on an ASRock PG-1600G the side opposite the latch is all +12 V and the latch side is all ground, the reverse of a Corsair-compatible pinout, so a Corsair-type cable would have put +12 V on ground. {{Source|handle=c133|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1561556993171259554/1561559679505539163}} {{Source|handle=globalapathy|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1561556993171259554/1561560011459797033}} The wrong pinout will likely kill a 170HX. {{Source|handle=c133|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561552472714117223}} PixelML's rule: never mix modular cables between PSU models, even when they fit. {{Source|handle=c133|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562161732137386127|repo=https://github.com/PixelML/club-170hx|note=Apache-2.0 license}}
# '''Use 16 AWG wire''' and good contacts; crimp quality and wire gauge are the limit, not the connector shape. {{Source|handle=wakeupmbrc1|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561575042381381664}}

Ready-made and custom cables:
* Corsair Type 4 PSUs (for example RM850x, not the RMx Shift): [https://www.corsair.com/us/en/p/pc-components-accessories/cp-8920141/type-4-sleeved-black-8-pin-4-4-atx12v-eps12v-cable-compatible-with-all-corsair-type-4-pin-out-psu-cp-8920141 Corsair CP-8920141] sleeved 8-pin (4+4) EPS12V cable, PSU to card, but its 4+4 latch does not fit the card cleanly. {{Source|handle=c133|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561554430225158235}}
* @c133 builds Type 4 EPS cables from 16 AWG stranded copper and genuine Molex Mini-Fit Jr housings, cheaper than Corsair's if you own crimpers, and offered to make some for confirmed Type 4 PSU owners. {{Source|handle=c133|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561554636135993405}}
* Server PSU breakout boards: two 6-pin to EPS splitters per card have worked for years for @finishtilt14 {{Source|handle=finishtilt14|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560223928540991499}}; @backwardsminer had custom-length cables made, measured the current per pin and doubled the lowest-draw pins {{Source|handle=backwardsminer|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560304322447802380}}.

== Connector ratings ==
{{Status|Contested}} Posters quote different numbers; the differences are spec rating against what the terminals carry.
{| class="wikitable"
! Connector !! Numbers posted !! Source
|-
| PCIe 6-pin || 65 W rating; three 12 V terminals of 9 A minimum each, the same terminals as a 6+2 || {{Source|handle=civiloid|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1561156518555029505}} {{Source|handle=wakeupmbrc1|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561565222110634007}}
|-
| PCIe 8-pin (6+2) || 150 W rating {{Source|handle=civiloid|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1561156586221740073}}; "about 175 W" per cable in practice {{Source|handle=endsjeremy|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561360791817429095}} || see cells
|-
| EPS12V 8-pin || 235 W {{Source|handle=civiloid|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560436414829559809}}; "about 330 W" {{Source|handle=civiloid|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1561156621915131937}}; 300 W continuous, the margin above is for transients {{Source|handle=endsjeremy|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561576387641344102}}; 300 W rated, 400 W peak, about 600 W possible {{Source|handle=endsjeremy|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558695673681944599}}; four 12 V terminals of 9 A or more, at least 432 VA {{Source|handle=wakeupmbrc1|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561575829874413650}} || see cells
|-
| 18 AWG wire || 10 A at 60 C, so about 360 W on a 6-pin's three 12 V wires || {{Source|handle=_arcanum_|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560226013512736769}}
|-
| 12VHPWR terminal (for comparison) || rated "8a each or so"; the PCIe ATX 2.0 terminals above are about twice the size and four times the cross-section || {{Source|handle=wakeupmbrc1|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561574683730640907}} {{Source|handle=wakeupmbrc1|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561574740165005333}}
|}
* A single EPS12V feeds even the A100 PCIe at its 300 W factory limit; the slot supplies only a small share (a guess of about 25 W). {{Source|handle=wakeupmbrc1|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561575604640555089}}
* The PCIe 8-pin has its grounds reversed relative to the EPS 8-pin. {{Source|handle=endsjeremy|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558695475685752835}}

== Burned and failed hardware ==
Each of these has its own entry, with the full thread, on [[Power and cabling warnings]] and [[Troubleshooting]].
* {{Status|Warning}} '''PSU burned after 48 hours at about 220 W per card''' on a DeepCool PX1000P, running cards from one PCIe cable each; the owner did not know each card needs two. The PSU protected the card. {{Source|handle=con3po7016|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558660679295180912}} {{Source|handle=endsjeremy|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558695475685752835}} The PSU model rates well on a community [https://docs.google.com/spreadsheets/d/1akCHL7Vhzk_EhrpIGkz8zTEvYfLDcaSpZRB6Xt6JWkc/edit?usp=sharing PSU tier list], so the cabling was the cause. {{Source|handle=globalapathy|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558667430551625728}} "Cheap out on the gpu not the psu." {{Source|handle=con3po7016|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558659981165854730}}
* {{Status|Warning}} '''Magic smoke''' from powering a card through one cable plus its pigtail. {{Source|handle=con3po7016|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561553067290136629}} A PSU shut down under load when an RTX 3090 was fed the same way. {{Source|handle=xeax|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561334034926280838}}
* {{Status|Warning}} '''A 6-pin to 8-pin adapter melted at 170 W''' within weeks, one of six on HP server PSUs with hard-wired 6+2 leads. {{Source|handle=neapopa|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1561122626586415135}}
* {{Status|Warning}} '''A refurbished HP 1,200 W server PSU exploded''' with a loud bang after about two hours: three of them fed ten cards capped at 160 W, with GPU peaks near 2,000 W (55 % of rated capacity), during a 30-minute thermal bench then long-prefill GLM-5.3 work. The PSU fans never spun up and the units were very hot. Cards and system survived. {{Source|handle=reala7096|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562183774475919512}} Capacitors in those PSUs "go bang" {{Source|handle=sojun80|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562205111365804134}}; test used PSUs on a CRPS tester away from your GPUs {{Source|handle=endsjeremy|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562220361901281392}}.
* {{Status|Warning}} '''Aged breakout boards''': constant reboots and PSU shutdowns under load came from server PSU breakout boards that failed after 3 to 4 years, not from the PSUs (the owner had bought six PSUs). The failed boards were ZSX-AMPS; he replaced them with X11-AMPS. {{Source|handle=finishtilt14|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560224891343736936}}
* {{Status|Reported}} '''A Lian Li 1200G PSU shut down after a few hours at about 600 W''' because its quiet fan curve let it overheat; a USB fan on the PSU grille kept it running. {{Source|handle=phoenixone7|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556813394701713419}} Another member called that not normal and suspected the fan. {{Source|handle=squishysquare|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556822393408856136}}
* {{Status|Warning}} '''The 300 W VBIOS''': a photo of a burned 170HX was posted earlier, and the board lacks some power-delivery parts of the full layout. {{Source|handle=xanthefin|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561336153515364444}} See [[Undervolting and power limits]].
* {{Status|Reported}} '''12VHPWR''' (not CMP-specific, relevant if you adapt such a PSU): connectors degraded twice on an RTX 5090 at no more than 70 % power, close to burning; another member's 12VHPWR terminal turned yellow. {{Source|handle=endsjeremy|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1560810497115426928}} {{Source|handle=wakeupmbrc1|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1560810856726401025}}

== PSU sizing ==
Size for the CPU, board, fans and every card's cap, plus margin for spikes. {{Source|repo=https://github.com/PixelML/club-170hx}} Short spikes go well above the
cap: up to 380 W on cards capped at 250 W. {{Source|handle=n2dcrypt|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556771516803321877}} @reala7096 worked out that nine cards spiking to
350 W together would need 3,000 W, but in a PP8 layout only about half the cards are busy at once.
{{Source|handle=reala7096|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556771733208440974}}
{| class="wikitable sortable"
! Cards !! Cap !! Power supply !! Result !! Status !! Source
|-
| 4 || 300 W || one 1,600 W PSU || no shutdowns || {{Status|Reported}} || {{Source|handle=okrasit.|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556772848041988238}}
|-
| 8 || not given || two 1,600 W PSUs || no shutdowns yet || {{Status|Reported}} || {{Source|handle=n2dcrypt|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556772789510344801}}
|-
| 4 || 180 W || one used 1,200 W PSU (about $50) || bought for it || {{Status|Reported}} || {{Source|handle=voidgiraffe|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556940563759235107}}
|-
| 4 || not given || whole system || up to 1,500 W at the wall || {{Status|Reported}} || {{Source|handle=quark2world|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556358835097305119}}
|-
| 2 CMP + 4 RTX 3090, no power limits || none || two ASRock PG-1600 (sold as Gold, tested Platinum by third parties), each on its own 20 A 120 V circuit || runs || {{Status|Reported}} || {{Source|handle=zombielurker|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556775187351871549}}
|-
| 4 || 175 W || two 750 W PSUs, two cards each, joined by a 24-pin Y adapter || all four cards and the PCIe switch lose power at once during heavy prompt processing || {{Status|Reported}} || {{Source|handle=replacedriver47|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556768982357377065}}
|-
| 9 || 160 W || three 750 W PSUs (2,250 W) || all cards drop about once a day || {{Status|Reported}} || {{Source|handle=reala7096|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556769461439168573}}
|-
| 10 || 160 W || three refurbished 1,200 W server PSUs || one exploded (see above) || {{Status|Warning}} || {{Source|handle=reala7096|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562212397744132237}}
|-
| 8 || 160 to 250 W (governor) || the server's own redundant PSUs on a 240 V circuit || runs; about 2.0 kW at 250 W caps || {{Status|Reported}} || {{Source|handle=darkmaniac7|date=2026-10-27|note=lab notes}}
|}
* {{Status|Proven}} About four cards per 1,600 W PSU works: four cards at a 300 W cap on one 1,600 W PSU with no shutdowns {{Source|handle=okrasit.|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556772848041988238}}, and eight cards on two 1,600 W PSUs {{Source|handle=n2dcrypt|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556772789510344801}}.
* With several independent PSUs, one tripping on a spike can take down everything on a PCIe switch board. {{Source|handle=reala7096|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556773757920477186}} A hot PLX switch chip can also drop cards. {{Source|handle=zombielurker|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556775187351871549}} See [[Troubleshooting]].
* PCIe switch boards need their own 24-pin and EPS power. {{Source|handle=gnasherrr|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562275360177922212}}
* {{Status|Warning}} '''A fully SM-unlocked 10 GB card spiked to about 400 W at a 250 W limit.''' @djpandaman's 10 GB card, unlocked to 122 SMs, briefly reported about 400 W of board power during benchmark tests with the power limit set to 250 W; he was not sure whether the value was measured or calculated. @xeax recalled him mentioning about 375 W at a 250 W limit earlier. @xeax is weighing whether to fit the 6 MOSFETs missing from his own card's VRM, because he fears overloading the ones that are fitted, and doubts he could cool that load. Safe power limits for fully SM-unlocked cards are not known. Until they are, do not count on the cap to bound peak draw on such a card: size the PSU for the spikes, keep one EPS cable per card (rules above), and undervolt rather than raise the limit (see [[Undervolting and power limits#10 GB cards]]). The card's own power reading above 80 SMs is also reported to be unreliable; see [[10 GB card#Limits]]. {{Source|handle=xeax|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563220557363814480}} {{Source|handle=xeax|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563221992587534357}} {{Source|handle=xeax|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563222111592521881}} {{Source|handle=djpandaman|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563222404627431497}}

=== Where to get power cheaply ===
* {{Status|Contested}} Used ATX PSUs: @zorg33, who sold hundreds in the mining era, says 9 in 10 used ATX units are degraded and may hold only half their rating; test one near its rating for a few hours. His recipe: a small new quality PSU for the motherboard, and decommissioned 1,600 W Platinum server PSUs (about $20) for the cards, with custom EPS cables or adapters. {{Source|handle=zorg33|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556939640894918788}} @ob88594 suggests used EVGA 1600 T2/G2 units. {{Source|handle=ob88594|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556934754987933769}}
* HP DPS-1200SB server PSUs with a cheap breakout backplane: about $50 each, 2,400 W for $150, quiet at 40 % load. {{Source|handle=reala7096|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556775358177480778}} (Compare the exploded refurbished HP unit above.)
* {{Status|Reported}} Most server PSUs derate to about half power on 120 V and need 220 to 240 V for full output. {{Source|handle=endsjeremy|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562276070340821089}} C-Payne sells CRPS breakout boards ([https://c-payne.com/collections/psu-breakout-boards c-payne.com]). {{Source|handle=endsjeremy|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562276384049594481}} Some cheap ATX units go up to 3,000 W. {{Source|handle=endsjeremy|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562275853822464101}}
* Two PSUs in one box: use a PSU sync board. {{Source|handle=wakeupmbrc1|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561578856127660143}}

== Wall power ==
* Plan circuits before you scale. @gpmickey added three 115 V 20 A breakers for twelve cards {{Source|handle=gpmickey|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562196542574690395}}; @con3po7016 cleared two circuits for his {{Source|handle=con3po7016|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558696494343913579}}; @zombielurker gives each PSU its own 20 A 120 V circuit {{Source|handle=zombielurker|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556775187351871549}}.
* {{Status|Reported}} 240 V: the two hots are out of phase and need no neutral, only ground. Use a two-pole breaker with a hot on each pole and the existing ground if it is large enough; 12 AWG for a 20 A 240 V circuit. Use a non-contact voltage tester ([https://www.amazon.com/dp/B008M6YLF4 the one @endsjeremy linked]) every time: the work is simple but dangerous. {{Source|handle=endsjeremy|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562218990888157267}} If in doubt, hire an electrician. {{Source|handle=endsjeremy|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562217046606090251}} the lab's eight-card server and its UPS run on a dedicated 240 V circuit. {{Source|handle=darkmaniac7|date=2026-10-26|note=lab notes}}
* A whole-panel surge protective device ([https://www.amazon.com/dp/B09DK1726H the one @endsjeremy used], about $60) snaps in like a breaker with a wire to the ground bar and shunts lightning, transformer and large-load surges to ground; its green light goes out when it is spent. The cheapest protection there is. {{Source|handle=endsjeremy|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562226820441571471}}
* {{Status|Contested}} UPS: no UPS above about 1,600 W can go on a normal household outlet; larger ones need a 20 A receptacle. Tripp Lite (Eaton) is a safe choice; replace lead-acid batteries on principle. {{Source|handle=endsjeremy|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562272950034501643}} @sojun80 prefers portable power stations ([https://www.ankersolix.com/products/s2000-portable-power-station Anker SOLIX S2000], about $600) and says the transfer time must be under 30 ms; Anker and a few others do 20 ms or less. {{Source|handle=sojun80|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562274839731896341}}

== See also ==
[[Power and cabling warnings]] · [[Troubleshooting]] · [[Cooling and power]] · [[Undervolting and power limits]] ·
[[Chassis builds]] · [[Platforms]]

{{ImportFooter}}
[[Category:Cooling and power]]

[[Category:8 GB]]
[[Category:10 GB]]

PCIe x16 capacitor mod

2026-10-31T21:34:38Z

ImportBot: Import: PCIe x16 capacitor mod (width x4 to x16), parts, placement, technique, results and failures; amoghmunikote/170th-Street, Consensus-Protocol, @lxtend, @djpandaman, @anon33anon, @globalapathy, @neapopa, @bigfoot1144, @exile_1ck and others

{{Unlock
|unlocks=PCIe x16 link width (capacitor mod)
|variant=both
|unlock_build=hardware mod: 24 x 0402 220 nF capacitors
|steps_page=PCIe x16 capacitor mod
|status=Reported
|tested_by=_j3ns
|source=https://github.com/amoghmunikote/170th-Street/blob/master/modifications/pcie-capacitor-mod.md
}}

The CMP 170HX trains its PCIe link at '''x4''' because the AC-coupling capacitors on 12 of its 16 lanes were never
fitted at the factory. Soldering in the 24 missing capacitors gives a full '''x16''' link. It is the only hardware step in
the usual unlock, it needs no software of any kind, and it works the same on the 8 GB and the 10 GB card.

The mod changes link '''width''' only, never the PCIe '''generation'''. A modded card with no unlock installed reports
Gen1 x16; with [[Driver unlock|cmpunlocker]] it reports Gen2 x16. Generation is a separate, software problem: see
[[Gen2 link retrain]] and [[PCIe Gen3 on the 10 GB card]].

== What the card ships with ==

=== The card is wired for x16 but trains x4 ===
All 16 lanes are routed on the PCB; only the AC-coupling capacitors for lanes 4-15 are missing. The lanes are not fused
off: <code><nowiki>OPT_PCIE_LANE_DISABLE</nowiki></code> (<code>0x00820394</code>) reads <code>0x00000000</code> on
every card probed. A stock card shows <code><nowiki>LnkCap: ... Width x16</nowiki></code> but
<code><nowiki>LnkSta: Speed 2.5GT/s, Width x4 (downgraded)</nowiki></code>; the "(downgraded)" marker is what a link
with no signal on 12 lanes produces.

{{Status|Reported}} {{Cards|both}} 
{{Source|handle=rrickk420|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558127650223030302|repo=https://github.com/Consensus-Protocol/cmp170hx}}

=== Any x16 link needs the mod; x4 is the most without it ===
"Any pcie gen with 16x needs cap mod." Without the mod the maximum width is x4, at any generation, including Gen3 on a
10 GB card.

{{Status|Proven}} {{Cards|both}} 
{{Source|handle=lxtend|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560914210811150400}} 
{{Source|handle=djpandaman|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561021502739189892}}

=== Gen3 x16 and Gen4 on the 10 GB card also need the caps ===
Humvee55's 10 GB cards run Gen3 x16 after the mod. Without the caps, mrpandagod could not get a Gen4 link: it kept
falling back to 8.0 GT/s.

{{Status|Reported}} {{Cards|10 GB}} 
{{Source|handle=djpandaman|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1557883050690347082}} 
{{Source|handle=scallion_9883|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560778919412633681}}

== Parts ==

=== 24 x 0402 220 nF X7R capacitors ===
You need 2 capacitors per lane for 12 lanes: 24 parts, 0402 size (about 1.0 x 0.5 mm), 0.22 uF (220 nF), X7R. The
value comes from the A100 reference schematic (GA100-883, P1001-B02, page 3, PCIe connector). Order at least 30 to cover
losses. Rated 16 V in Amogh's write-up; Consensus-Protocol gives 6.3 V or higher.

Confirmed parts:
* Samsung Electro-Mechanics <code>CL05B224KO5NNNC</code> (DigiKey 1276-1176-1-ND, 16 V). @globalapathy bought 200 for
under 5 USD; Mouser and LCSC also stock it.
* Taiyo Yuden <code>MAASJ105SB7224KFCA01</code> (6.3 V).

{{Status|Reported}} {{Cards|both}} 
{{Source|repo=https://github.com/amoghmunikote/170th-Street}} 
{{Source|handle=globalapathy|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558668384181424161}} 
{{Source|handle=gpmickey|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558667768730099774}}

=== No strap resistors, no VBIOS chip ===
Only the lane capacitors matter for width. No strap resistor is moved and no backup flash chip is added. A circulating
"A100 hardware restore" PDF lists a Winbond backup VBIOS chip and other parts; none of them are needed for x16.

{{Status|Reported}} {{Cards|both}} 
{{Source|handle=rrickk420|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558127650223030302|repo=https://github.com/Consensus-Protocol/cmp170hx}}

== Where on the board ==

=== The C1100-C1350 pads beside the gold fingers ===
The empty pads carry reference designators in the <code>C1100</code>-<code>C1350</code> range (for example C1120,
C1125, C1130, C1135), two per differential pair. They sit on the PCIe lane routing between the fan-out traces and the
edge-connector gold fingers, on the outer surface, uncramped and with visible copper. Cross-check the schematic against
your own board to find exactly which pads are empty. The card has to come out of its shroud first: follow the teardown
on 170th Street (see [[Cooling and power]]).

{{Status|Reported}} {{Cards|both}} 
{{Source|handle=markshowa|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1561324784598384784|repo=https://github.com/amoghmunikote/170th-Street}}

=== The leftmost group by the mounting hole is the hardest ===
With hot air, the leftmost capacitor group next to the mounting hole takes the most heat to do. A solder stencil for
the mod is in the pinned messages of the hardware channel, but you need a laser cutter to make it.

{{Status|Reported}} {{Cards|both}} 
{{Source|handle=globalapathy|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564704266352861275}} 
{{Source|handle=globalapathy|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564479895952695377}}

== Before you start ==

# Test the card stock first. The acceptance tests do not need the mod, and a card you have soldered is harder to return.
See [[Acceptance checklist]].
# Open the card once: repad and repaste at the same time if you plan to.
{{Source|handle=gpmickey|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558670011336368199}}
# If you have never soldered 0402 parts, practise on a dead board first. Several members learned on these cards.

== Tools ==

=== What members used ===
A hot-air station and magnification are the core; a fine iron works too. Reported kits:
* @neapopa: a hot-air station and a magnifying glass, about 100 USD for both, enough for 8 cards with little prior
experience.
* @civiloid: an ATTEN hot-air station, a Pinecil iron (any 60 W or more iron with SMD tips), an Andonstar microscope
and tacky flux. He would rather use a microscope with a camera than work off a screen.
* @globalapathy: an Atten ST-862D (1000 W) works, but slower than a 1400 W station; Sequre hot tweezers to pull a bad
capacitor off.
* @_arcanum_: microsoldering tweezers are essential, the capacitors are almost impossible to handle otherwise; clean
with isopropyl alcohol, foam swabs, a brush and wipes.
* @gpmickey (twelve cards to do): an upgraded soldering iron, a digital scope and a hot-air station on top of the DMM
he had, plus extra flux, solder and braid so he would not run short. @globalapathy added a 50 MHz scope meter for
under 100 USD.

More tools are on [[Tools]].

{{Status|Reported}} {{Cards|both}} 
{{Source|handle=globalapathy|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558677685541281927}} 
{{Source|handle=gpmickey|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558674179950383125}} 
{{Source|handle=gpmickey|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558681059644805231}} 
{{Source|handle=civiloid|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558803228362145833}} 
{{Source|handle=_arcanum_|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558857956961820794}} 
{{Source|handle=globalapathy|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564749663116992587}} 
{{Source|handle=neapopa|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564536383396380683}}

== Steps, as reported ==

Two methods work. Both start from the same advice: flux and a clean tip, and fix one side of every capacitor before
doing the other side.
{{Source|handle=shirogeek|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559648609191075851}}

=== Hot air (neapopa, globalapathy) ===
# Preheat the board.
# Hold each capacitor with tweezers in contact with its two pads.
# Heat with hot air until it bonds, then remove the heat. Use the medium nozzle at low air (globalapathy runs 15 percent)
so the parts do not blow away.
# Nudge the capacitor to confirm it is soldered, then move to the next.

@neapopa added no solder: the solder already on the pads was enough. His first card took 2 hours, the last about 30
minutes.

{{Status|Reported}} {{Cards|both}} 
{{Source|handle=neapopa|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564541107097042974}} 
{{Source|handle=globalapathy|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564755478498639884}}

=== Iron (cmurrayis, Waka324) ===
@cmurrayis removed the factory solder first, re-applied solder, then fitted each capacitor one at a time with soldering
tweezers; about an hour per card. Any wobble shifts the alignment, and it is hard to see whether both ends wetted. Clean
the flux off afterwards; @civiloid advises a second round of cleaning, since every flux has long-term side effects.
@gpmickey: done well, a soldering iron is a solid alternative to hot air, and there is very little risk on this part of
the board.

@cmdrwaka324 (Waka324) found his own iron-and-wick method easier than the video's:
# Apply flux.
# Use wick and a large flat tip to soak up the original solder (important, or hand work is difficult).
# Place a new bead on one side, going up and down the caps, by tinning the tip and dabbing the pads.
# With good tweezers, pin one side of each cap with a fine-tipped iron: heat the deposited blob and slide the cap in.
# Do the other side, patiently, so solder wicks to both the pad and the cap.
# Check by briefly reheating the first side of every cap and watching for movement; if good, no cap should move.
# Clean and done.

{{Status|Reported}} {{Cards|both}} 
{{Source|handle=gpmickey|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559613899232251917}} 
{{Source|handle=cmurrayis|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562968219709607947}} 
{{Source|handle=civiloid|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562032473108389980}} 
{{Source|handle=cmdrwaka324|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556530666378764359}}

=== Remove the factory solder first, or not ===
{{Status|Contested}}
* Remove the factory solder with wick first, then re-apply; on the Consensus-Protocol procedure, wick off the lead-free
factory solder and use leaded solder. {{Source|handle=cmurrayis|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562968219709607947}}
* No extra solder needed; the solder on the pads is enough with hot air. {{Source|handle=neapopa|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564539205277720608}}

=== Video guides ===
The video "How to Solder Components Without Blowing Them Away (NVIDIA CMP 170HX)" shows the mod done quickly;
mrpandagod calls it the best guide, used together with the 170th Street page. Members vouch for the channel's work.
https://www.youtube.com/watch?v=HO2T4TgNzlQ

{{Status|Reported}} {{Cards|both}} 
{{Source|handle=djpandaman|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556529467520843809}} 
{{Source|handle=_orrorin|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559614704513712240}}

== Verify ==

<syntaxhighlight lang="bash">
sudo lspci -s <port> -vvv | grep LnkSta
</syntaxhighlight>

Read <code>LnkSta</code>, never <code>LnkCap</code> (LnkCap advertises x16 even on a stock card). After a good mod the
width field loses "(downgraded)":

{| class="wikitable"
! State !! LnkSta
|-
| Stock, no unlock || <code><nowiki>Speed 2.5GT/s, Width x4 (downgraded)</nowiki></code>
|-
| Mod, no unlock || <code><nowiki>Speed 2.5GT/s, Width x16</nowiki></code>
|-
| Unlock, no mod || <code><nowiki>Speed 5GT/s, Width x4 (downgraded)</nowiki></code>
|-
| Mod and unlock || <code><nowiki>Speed 5GT/s, Width x16</nowiki></code>
|}

Also check the slot is electrically x16, and that the card is fully seated: one card in a 4-card rig trained only x4 or
x8 until a spacer pushed it fully into the slot.

{{Status|Reported}} {{Cards|both}} 
{{Source|repo=https://github.com/amoghmunikote/170th-Street}} 
{{Source|handle=nestaa51|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560102604988616776}} 
{{Source|handle=cibernox|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518691940646781070/1557014423242145894}}

== Results ==

=== x4 to x16, confirmed on many cards ===
Amogh documented the first public success on a 170HX in April 2026: <code><nowiki>Speed 2.5GT/s, Width x4 (downgraded)</nowiki></code>
before, <code><nowiki>Speed 2.5GT/s, Width x16</nowiki></code> after. Since then many members report x16, among them
@anon33anon (three cards), @neapopa (8 cards) and Humvee55 (10 GB cards at Gen3 x16). See the confirmation below.

{{Status|Reported}} {{Cards|both}} 
{{Source|repo=https://github.com/amoghmunikote/170th-Street}} 
{{Source|handle=anon33anon|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560084461008461875}}

=== Bandwidth ===
Stock Gen1 x4 is about 1 GB/s (0.85 GB/s measured). The mod alone gives Gen1 x16, about 4 GB/s. With the Gen2 unlock,
Gen2 x16 measured 6.63-6.67 GB/s once. Morrowmake's P2P fork measured about 6.65 GB/s each way between cards at Gen2
x16 (see [[P2P]]).

{{Status|Reported}} {{Cards|both}} 
{{Source|handle=markshowa|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1561324784598384784|repo=https://github.com/amoghmunikote/170th-Street}} 
{{Source|handle=rrickk420|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558127650223030302|repo=https://github.com/Consensus-Protocol/cmp170hx}}

=== Prefill gains a lot, single-card decode barely moves ===
On a single 40 GB card running Strata, going from x4 to x16 gave about 4x prefill but only about 3 % more decode.

{{Status|Reported}} {{Cards|10 GB}} 
{{Source|handle=exile_1ck|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557241785695211612}} 
{{Source|handle=wakeupmbrc1|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557257675396489257}}

=== Multi-card recipes: the mod is behind the top numbers ===
* @segmond ran Morrowmake's GLM recipe on 4 cards without P2P and without the mod and was "not even close" to the
published numbers; @cibernox: "the 16x mod is doing a lot for the high speed".
* @greencandle9753: to match his DeepSeek V4.1 Flash numbers (150-296 tok/s single user) you have to do the x16 mod.
* @zingy90210 (2x 8 GB, no mod) concluded the mod is what makes @nestaa51's 2-card GLM Flash setup fast.
* The mod is not required for TP4: Finishtilt14 runs the 4-card GLM recipe without it in TP or PP. TP=2 works well with
it, and @cibernox calls it "borderline mandatory" for TP=2.

{{Status|Reported}} {{Cards|both}} 
{{Source|handle=cibernox|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559577294194876477}} 
{{Source|handle=finishtilt14|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1559516402849939478}} 
{{Source|handle=cibernox|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562107263009689731}} 
{{Source|handle=greencandle9753|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562929719794602087}} 
{{Source|handle=zingy90210|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563537275944566836}}

=== Same link bandwidth as a Gen3 unlock, without a fuse burn ===
Gen2 x16 carries what Gen3 x8 would, so for tensor parallel the mod gives the gain a Gen3 unlock would, with a soldering
iron instead of an irreversible [[RIR fuse burn]]. A lab estimate for TP4 single user, 280-355 tok/s toward 440-480
tok/s, is a projection, not a measurement.

{{Status|Theory}} {{Cards|both}} 
{{Source|handle=darkmaniac7|date=2026-10-19|note=lab notes}}

=== No benefit for mining ===
One member modded one card and skipped the rest because the mod gives no mining advantage.

{{Status|Reported}} {{Cards|both}} 
{{Source|handle=port00|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1562885518558105611}}

== When it does not come up x16 ==

=== x8 means a bad joint, not a hardware limit ===
Width falls back to the next legal value instead of failing: 12 of 24 good capacitors gives x8, and so does any cold,
missing or bridged joint. A card that trains x8 or x4 after the mod still works at that width while you fix it.
* @bigfoot1144: still x4 after the first soldering, x8 after cleaning the caps.
* @anon33anon: third card stuck at x8 although continuity from each cap top to the slot looked fine and nothing was
shorted; after redoing the suspect caps it came up x16.
* @cmdrwaka324: on his early cards a bad cap job showed as x16 dropping to x8, until he refined his process.

{{Status|Reported}} {{Cards|both}} 
{{Source|handle=bigfoot1144|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559674887482769459}} 
{{Source|handle=anon33anon|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560221482720825405}} 
{{Source|handle=cmdrwaka324|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1560640558685233254}}

=== How to find the bad capacitor ===
# Test continuity between each capacitor and the gold finger it should reach, not just from the cap top to the slot.
@globalapathy notes the top pad cannot be probed without scraping the trace, so a cap that measures fine from the top
can still be lifting.
# With a DMM, check for shorts between the signal lines.
# Under the microscope, tilt the card to see under the ends of each capacitor; dull joints are cold joints. Reheat them
with good SMD flux.
# Or tap both ends of every capacitor with the iron; a cap that is not making contact shows up quickly.
More link problems after the mod: [[Card not detected or BAR allocation fails]].

{{Status|Reported}} {{Cards|both}} 
{{Source|handle=globalapathy|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559688049355395196}} 
{{Source|handle=ghostinthedatacenter_87281|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560088415985336381}} 
{{Source|handle=chonsworth|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560111059031949345}} 
{{Source|handle=cmdrwaka324|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560112661276921898}} 
{{Source|handle=globalapathy|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564479040235241623}}

=== Full x16 can expose a power problem ===
Five cards on an external GPU switch baseboard, cap modded, dropped off PCIe with lane and IOMMU errors on large
prompts; the logs showed the first card drawing 260 W. Lowering the power limit from 250 W to 180 W fixed it (GLM 5.3
Flash at 380k context). See [[Cooling and power]].

{{Status|Reported}} {{Cards|both}} 
{{Source|handle=moliminous|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1561749293717659774}}

== Risks ==

=== Hot air blows the parts away ===
{{Status|Warning}} At normal air flow a hot-air nozzle blows 0402 capacitors (yours and the board's) off the pads; the
board components do not stick until it has warmed up. Use the medium nozzle at low air (about 15 percent), preheat, and
keep hot tweezers or an iron ready to pull a misplaced part. @_orrorin shields neighbouring parts with aluminium tape.

{{Source|handle=globalapathy|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564755478498639884}} 
{{Source|handle=_orrorin|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559584745367806053}}

=== No card is reported killed by the mod ===
Across the Discord history (2026-10-04 to 10-28) nobody reports a card damaged by the mod itself. A failed attempt that
does not damage other components is easy for a technician to fix, and the card keeps working at x4 meanwhile.

{{Status|Reported}} {{Cards|both}} 
{{Source|handle=_orrorin|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559584745367806053}} 
{{Source|handle=gpmickey|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559613899232251917}}

=== A card from a repair technician arrived dead ===
@exile_1ck had his card's x16 mod done by a local GPU repair technician in under an hour; he found him on Facebook
Marketplace as a buyer of broken GPUs, which gave him a repair history to check. The technician takes no online orders
and eXile keeps his name private, so he is not listed here. Later eXile bought a non-working 10 GB card from the same
technician (taken in from a customer, history unknown); it does not finish booting and appears blocked by GPC6 (see
[[Recovery]]). Nothing links its failure to the cap mod.

{{Status|Reported}} {{Cards|10 GB}} 
{{Source|handle=exile_1ck|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556225673553649715}} 
{{Source|handle=exile_1ck|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558964000564183041}}

== Having it done ==

=== Repair shops and prices ===
Shops that do board-level GPU work treat this as basic: fitting capacitors, far less work than a reball. Ways members
found one: search for "microsolder" on a local review site and call around; or look for people buying broken GPUs to
repair and resell, who have review histories. Quotes reported (October 2026), all for a seller doing only the soldering:
* 45 USD per card, customer supplying the 0402 caps (California).
* 120 CAD per card (British Columbia); 160 CAD per card (Edmonton).
* 65 EUR per card for 13 cards (EU); 300 AUD for one card (Australia); about 900 USD for 8 cards.
* 175 USD per card with the customer supplying the caps; the shop would not guarantee the GPU would be "repaired".
* In China about 50 CNY (under 10 USD).
* A paid service at about 500 USD was judged too expensive when the gear costs under 100 USD.

'''Ailfond''' ships cards already modded, about 2,600 USD DDP (October 2026); members asked whether anyone does the mod
cheaper than Ailfond, with no clear answer.

{{Status|Reported}} 
{{Source|handle=kellertreppe123|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556319940942893168}} 
{{Source|handle=nikhilr1696|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556292538951012437}} 
{{Source|handle=cibernox|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1561715822559498371}} 
{{Source|handle=68x0|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556848174449299488}} 
{{Source|handle=gpmickey|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556865392876453901}} 
{{Source|handle=exile_1ck|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556139940939571233}} 
{{Source|handle=gnasherrr|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562489999650324684}} 
{{Source|handle=lxtend|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562505132497838254}} 
{{Source|handle=cmurrayis|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562968838574702633}} 
{{Source|handle=reala7096|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562969168737865800}} 
{{Source|handle=impactic|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562969877751267359}} 
{{Source|handle=danske1|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564531936184115221}} 
{{Source|handle=endsjeremy|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560688687858061566}}

=== Community members who offered the service ===
Members who said they would do the mod for others (October 2026):
* @gmzombie (GMZombie007), US, 20+ years electronics work: offered it through an eBay listing so buyers get a receipt,
about 50 USD plus shipping, discount for multiples. {{Source|handle=gmzombie|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556124053839020085}}
* @tokukarin (Tokukarin): offers the service and did all his own cards. {{Source|handle=tokukarin|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556143083807187005}}
* @neapopa (Nea Popa): would do it for 50 USD with caps supplied; did 8 cards himself. {{Source|handle=neapopa|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564539130241617953}}
* @ikyo (Ikyo) knows a US contact last quoted at 100 USD per card. {{Source|handle=ikyo|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556148743575961641}}
* GPU Lab (gpulab.net, product id 16) lists the mod as a paid service at about 500 USD; @endsjeremy argued that is too
much when the gear costs under 100 USD. {{Source|handle=globalapathy|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560685405781889145}} 
{{Source|handle=endsjeremy|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560688687858061566}}

=== Shops say no ===
Owners report being turned away by many shops before finding one that would simply do the work; the job is 24
capacitors on labelled pads, with no diagnosis and no firmware step. Hand the shop the parts and that description.
Local options are thin in some countries: an EU buyer weighed a 1,900 EUR unmodded card partly because nobody local
could do the mod.

{{Status|Reported}} 
{{Source|handle=rrickk420|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558127650223030302|repo=https://github.com/Consensus-Protocol/cmp170hx}} 
{{Source|handle=shudza|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1561737931473948823}}

== Status ==

x4 to x16 is reproduced by many owners on both cards, so the unlock shows {{Status|Proven}} through the confirmation
below.

== Related ==

[[Gen2 link retrain]], [[PCIe Gen3 on the 10 GB card]], [[P2P]], [[Unlocks]], [[Which card do I have]],
[[8 GB card]], [[10 GB card]], [[Tools]], [[Acceptance checklist]], [[Card not detected or BAR allocation fails]],
[[Recovery]], [[Cooling and power]], [[Buying]].

{{ImportFooter}}
[[Category:Unlocks]]
[[Category:8 GB]]
[[Category:10 GB]]

Memory unlock on the 10 GB card

2026-10-31T21:34:38Z

ImportBot: The 10 GB card's memory ceiling: 40 GB from cmpunlocker, 48 GB on a lucky 6th stack, and why the disputed 80 GB is aliasing not memory. Discord Oct 2026 and the research repos.; sources: @_j3ns, @programmerboi, @djpandaman, @artistosu, @bigfoot1144, @_orrorin, @darkmaniac7, @rh3dai, @atsasin2126, @marklintonca, @tekkenz, @scallion_9883 (+6 more); GitHub ahnguyen17/ga100-fuse-re, amoghmunikote/cmpunlocker

{{Unlock
|unlocks=Memory on the 10 GB card (40 GB, 48 GB on a lucky card)
|variant=10 GB
|driver_version=cmpunlocker-patched driver (610+)
|unlock_build=cmpunlocker (40 GB) + RIR software override (6th stack)
|steps_page=Memory unlock on the 10 GB card
|status=Reported
|tested_by=_j3ns
|source=https://github.com/amoghmunikote/cmpunlocker
}}

The 8 GB card unlocks to a flat '''64 GB''' (see [[Driver unlock]]). The 10 GB card is different and the ceiling is a
lottery. {{Status|warning}} Do not expect 80 GB.

== 40 GB (the baseline) ==

[[Driver unlock|cmpunlocker]] sets the 10 GB card to '''40 GB''' (40960 MiB): CFG1 <code>0x009a0204 = 0x02669000</code>,
LMR <code>0x00100ce0 = 0x0000028A</code>. That is 5 HBM stacks of 8 GB. This is {{Status|Proven}} and reproduced by
everyone running the unlock. {{Source|programmerboi|2026-10-25|https://discord.com/channels/1518634379604136178/1534370835220004885/1563704621388529725}}

== 48 GB (the 6th stack, if it is good) ==

48 GB comes from enabling a disabled sixth stack (48 GB = 6 x 8 GB). It needs the [[RIR fuse burn]] (software fuse
remask) and the card must have a working 6th stack, which not all do; estimates put the chance around 20% or less.
{{Source|djpandaman|2026-10-11|https://discord.com/channels/1518634379604136178/1518692084729511967/1558942410724085843}}
{{Source|artistosu|2026-10-26|https://discord.com/channels/1518634379604136178/1518695328008638516/1564127408305479803}}
On most sampled cards the last stack is marked '''defective''', not merely disabled (bigfoot: all 6 of his; orrorin:
both of his), and defective-marked stacks really are defective. A "pristine" card with the 6th stack only disabled
(gpcprobe <code>OPT_FBP_DISABLE 0x840</code>, all DEFECTIVE masks 0) is the one that can reach 48 GB.
{{Source|bigfoot1144|2026-10-19|https://discord.com/channels/1518634379604136178/1518695328008638516/1561796223017681007}} 
{{Source|handle=_orrorin|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562165405924069639}}

== HBM vendor ==

{{Status|Reported}} The 10 GB card carries '''Samsung HBM2e'''; the 8 GB card carries '''SK hynix'''. Checked by the lab
on its own cards. {{Source|darkmaniac7|2026-10-30|note=lab notes}}

Earlier Discord posts on the question, kept for reference:
* RH-3D: 10 GB = Samsung HBM2, 8 GB = Hynix HBM2e 16 GB stacks.
{{Source|rh3dai|2026-10-17|https://discord.com/channels/1518634379604136178/1518692084729511967/1561039191343632425}}
* atsasin: the 10 GB card never had HBM2e, only the 8 GB.
{{Source|atsasin2126|2026-10-16|https://discord.com/channels/1518634379604136178/1518692084729511967/1560781758667169864}}
* mrpandagod: the evidence says the stacks are binned 16 GB HBM2e.
{{Source|djpandaman|2026-10-17|https://discord.com/channels/1518634379604136178/1518692084729511967/1560892095739469847}}
* Mark Linton's read-only dumps of two 8 GB cards show the SK Hynix strap <code>0x004906D1</code>.
{{Source|marklintonca|2026-10-10|https://discord.com/channels/1518634379604136178/1518695328008638516/1558556618818457612}}

== 80 / 96 GB: not real on these dies ==

{{Status|contested}} Several people got a 10 GB card to '''report''' 80 GB, but the memory was unstable above 40 GB.
{{Source|tekkenz|2026-10-12|https://discord.com/channels/1518634379604136178/1534370835220004885/1559048743947341955}}
Humvee55, a co-author of the paper that used a 10 GB card as the test vehicle, now believes the apparent extra capacity
is '''aliasing in L2''', not real memory. {{Source|handle=scallion_9883|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560782230777888841}} 
{{Source|handle=scallion_9883|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560782273652195479}}
A read-only fuse RE of a Samsung 10 GB card found the 80 GiB aperture (LMR <code>0x28B</code>) '''folds''' at about
16 KB above the expected address (address folding confirmed die-side), i.e. the upper half is aliased, not addressable.
{{Source|ahnguyen17|2026-10-03|https://github.com/ahnguyen17/ga100-fuse-re}}
Stacks are physically 16 GB parts that Samsung binned; unlocking the upper half is "basically impossible" with the
information available, likely needing internal Samsung codes. {{Source|handle=djpandaman|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559096192036642817}}
On 2026-10-20 Mountains put the current memory maximum for a 10 GB card at 48 GB, and bigfoot saw "no indication that
80 or 96 gb is achievable", with 48 GB possible "if your last 2 stacks are lucky".
{{Source|handle=mountains1605|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561898669966364697}} 
{{Source|handle=bigfoot1144|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562173508094533753}}

A Chinese write-up "170Hx 10G 解锁80G探索" (10G unlock to 80G exploration) is at blog.kkk.rs/archives/71; no one reported a
stable 80 GB card from it. A screenshot claiming 130104 MB was debunked as two 64 GB-unlocked 8 GB cards reported
together (65024 MiB x 2). {{Source|handle=kio063218|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1534858283138158697/1560618333542293526}}

== How the state is reported ==

Community agreement as of 2026-10-23: a 10 GB card now equals "an A100 40G PCIe with more SM"; after the RIR tool went
open source, except for the 40 to 80/96 GB VRAM-initialisation issue, most unlock problems are solved. NVLink is still
not public. {{Source|ob88594|2026-10-23|https://discord.com/channels/1518634379604136178/1518695328008638516/1563057728887328779}}

== Known issues ==

* A dead region that returns 0 and stores nothing: AnalyticETH had an agent write a script that pins a 2 MB throwaway
allocation over the bad address at startup so nothing important lands there, rather than discarding the card.
{{Source|analyticeth|2026-10-08|https://discord.com/channels/1518634379604136178/1518692084729511967/1557566171195383850}}
* Cards with HBM errors: Zombie's card threw about 5,000 single-bit and some multi-bit errors per 5-minute
<code>memtest_vulkan</code> run, always at the same addresses (around 30 GB and 61 GB). He mapped the failing
addresses to physical memory and used the driver's boot-time bad-block marking; only 4 blocks (64 KB each) were bad,
costing 8 MB (63.06 to 63.05 GB), after which <code>memtest_vulkan</code> and <code>gpu-burn</code> passed with ECC
off. The script must run every boot; the card refuses if there are too many errors (multiple GB). See
[[Troubleshooting]]. {{Source|zombielurker|2026-10-05|https://discord.com/channels/1518634379604136178/1518692084729511967/1556530076105838723}}

== Status ==

40 GB is {{Status|Proven}}. 48 GB is {{Status|Reported}} and card-dependent. 80/96 GB is {{Status|Contested}} and most
evidence says it is aliasing, not memory.

== Related ==

[[RIR fuse burn]], [[Full SM unlock]], [[Driver unlock]], [[Which card do I have]], [[10 GB card]], [[Troubleshooting]],
[[VBIOS and firmware]].

{{ImportFooter}}
[[Category:Unlocks]]
[[Category:10 GB]]

GLM 5.3 on 8x 8 GB (vllm-170hx-glm5)

2026-10-31T21:34:37Z

ImportBot: Import: arvkmr/vllm-170hx-glm5 (repo posted by reala) with 1a2b3c0967's confirmation on 8 cards; Con3po and reala context notes; sources: @reala7096, @1a2b3c0967, @con3po7016; GitHub arvkmr/vllm-170hx-glm5

{{Recipe
|model=GLM-5.3 (full 78-layer DSA MoE, not Flash)
|quant=GLM-5.3-Int4-Int8Mix-AWQ-g64; drafter incoai/GLM-5.3-DFlash2
|engine=Morrowmake/vllm-cmp170hx branch ampere-glm53 plus fail-closed source patches
|engine_version=vLLM 0.30.1rc1, fork commit 378c37b0
|cards=8 GB
|card_count=8
|topology=PP8 (also PP9 and PP10), TP1
|context=1,048,576 per request
|decode_tps=48.7
|prefill_tps=1833
|vram_per_card=64 GiB, GPU_UTIL 0.96 at PP8
|power_cap=170 W (author's 10-card run)
|flags=--attention-backend TRITON_MLA_SPARSE, packed fp8_ds_mla KV, --block-size 128, async scheduling required; PP8 partition 11,10,10,10,10,10,9,8
|status=Reported
|tested_by=reala7096
|tested_on=2026-09-29
|source=https://github.com/arvkmr/vllm-170hx-glm5
}}
The full GLM-5.3 (744B total, 40B active) on eight to ten 64 GB cards under pipeline parallel, with the DFlash2
speculative drafter and a 1M-token context. It pins a commit of Morrowmake's vLLM fork and applies a set of patches that
port the DSA sparse-attention path to sm_80. reala published it, built on bayley's and Morrowmake's work. Infobox
numbers are the author's single-stream run on 10 cards (the 8-card layout came later).
{{Source|handle=reala7096|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1557545116321718285}} 
{{Source|handle=reala7096|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1557544812972871813|repo=https://github.com/arvkmr/vllm-170hx-glm5}}

reala's own summary on Discord: 45 tok/s on short context, never below 30 on long context, and still about 30 tok/s per stream at concurrency 8: "still slow, but it feels quite usable now". {{Source|handle=reala7096|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1557544329080213637}}

== Prerequisites ==
* Eight, nine or ten CMP 170HX at 64 GiB each ([[Driver unlock]], [[8 GB card]]).
* CUDA 13.x toolkit (checked by <code><nowiki>install.sh</nowiki></code>), Python 3.12, torch 2.13.0, torchvision 0.28.0, torchaudio 2.11.0.
* The drafter is CC BY-NC-ND 4.0: <code><nowiki>download_drafter.sh</nowiki></code> needs <code><nowiki>DFLASH_LICENSE_ACK=1</nowiki></code>.
{{Source|handle=reala7096|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1557544812972871813|repo=https://github.com/arvkmr/vllm-170hx-glm5}}

== Steps ==
<syntaxhighlight lang="bash">
git clone https://github.com/arvkmr/vllm-170hx-glm5 && cd vllm-170hx-glm5
./install.sh # builds ~/vllm_glm53_dflash2 (engine, venv)
DFLASH_LICENSE_ACK=1 ./download_drafter.sh # drafter is CC-BY-NC-ND-4.0
MAX_SEQS=8 ./start.sh
python3 bench_conc.py 8000 decode 8 512 # C8 decode
python3 bench_conc.py 8000 prefill 8 8192 # C8 prefill
</syntaxhighlight>
* Pins (<code><nowiki>versions.env</nowiki></code>): <code><nowiki>VLLM_REPO</nowiki></code> Morrowmake/vllm-cmp170hx, branch <code><nowiki>ampere-glm53</nowiki></code>, commit <code><nowiki>378c37b0098a41a5cd25b3bf8b56d158e33a6cbf</nowiki></code>, precompiled wheel commit <code><nowiki>b6761e8d</nowiki></code>; drafter [https://huggingface.co/incoai/GLM-5.3-DFlash2 incoai/GLM-5.3-DFlash2] revision <code><nowiki>425aa615</nowiki></code>.
* <code><nowiki>preflight.py</nowiki></code> checks the target shape: GlmMoeDsaForCausalLM, hidden 6144, 78 layers, vocab 154880, index_topk 2048.
* Profiles: <code><nowiki>smoke</nowiki></code> (32K context, 1 seq, eager), <code><nowiki>agent</nowiki></code> (1M context, 4 seqs, 512 batched tokens, FULL_AND_PIECEWISE graphs; used by <code><nowiki>start.sh</nowiki></code>), <code><nowiki>production</nowiki></code> (1M, 8 seqs, 2048 batched). Served name <code><nowiki>glm-5.3</nowiki></code>, parsers <code><nowiki>glm47</nowiki></code>.
{{Source|handle=reala7096|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1557544812972871813|repo=https://github.com/arvkmr/vllm-170hx-glm5}}

=== Layouts ===
{| class="wikitable"
! PP size !! Partition !! GPU_UTIL !! KV pool
|-
| 8 (default since 2026-10-05) || 11,10,10,10,10,10,9,8 || 0.96 || 1,025,573 tokens
|-
| 9 || 10,9,9,9,9,9,9,8,6 || 0.93 || 1,600,895
|-
| 10 || 10,8,8,8,8,8,8,8,8,4 || 0.93 || about 2.09M
|}
KV is packed <code><nowiki>fp8_ds_mla</nowiki></code> at 656 B per token per layer plus FP8 indexer keys; <code><nowiki>--block-size 128</nowiki></code> is
required. Async scheduling is required: with <code><nowiki>--no-async-scheduling</nowiki></code>, PP plus DFlash2 asserts on the first short
prompt. The DFlash2 drafter keeps its own BF16 KV, window-bounded to 2,048 tokens; without that bound the drafter's KV
caps the pool at about 0.96M tokens.
{{Source|handle=reala7096|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1557544812972871813|repo=https://github.com/arvkmr/vllm-170hx-glm5}}

== Measured numbers ==
Author's run on 10 cards, 2026-09-29 (+250 MHz VF offset, 1,350 MHz SM ceiling, 1,300 MHz on one marginal card,
170 W cap, MAX_SEQS 8):
{| class="wikitable"
! Concurrency !! Decode per stream !! Aggregate !! Notes
|-
| 1 || 48.7 tok/s || || 3.92 accepted tokens per step; 4.3 s TTFT at about 7.8K prompt tokens (1,833 tok/s prefill)
|-
| 4 || 32.6 || 108.4 ||
|-
| 8 || 27.1 || 174.1 || prefill 2,351 tok/s aggregate
|}
A single 31K prompt prefills in 13.1 s (2,372 tok/s). Decode step 82.7 ms with the decode kernel work on, 92.0 ms with
it off (41.3 vs 35.4 tok/s). On 2026-09-28 single-stream was 39.7 tok/s.
{{Source|handle=reala7096|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1557544812972871813|repo=https://github.com/arvkmr/vllm-170hx-glm5}}

* 1a2b3c0967 ran it on 8 cards after reala added PP8, PP9 and PP10 support on 2026-10-08: concurrency 1 with an 850k-token KV pool, "big performance bump" over his own 8-card build. {{Source|handle=1a2b3c0967|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1557602682028691480}} {{Source|handle=1a2b3c0967|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1557602773208666163}}
* reala: GPU memory utilization 0.96 reaches 1M tokens without crashes so far. {{Source|handle=reala7096|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1557603135906779137}}

== Tuning notes from the repo ==
* Decode kernel work, each with a kill switch: <code><nowiki>GLM52_MLA_WIDE</nowiki></code> (64 heads per program; about 5 to 6 ms per step), <code><nowiki>VLLM_GLM5_DECODE_KERNELS</nowiki></code> + <code><nowiki>VLLM_GLM5_DECODE_MOE_ROUTE_V2</nowiki></code> (fused sm_80 MoE router, 2 to 3 ms), <code><nowiki>VLLM_GLM5_SHARED_EXPERT_REORDER</nowiki></code> (about 1 ms), <code><nowiki>GLM52_MLA_HEAD_BMM</nowiki></code> (about 0.6 ms).
* <code><nowiki>GLM53_TOPK_CANON=1</nowiki></code> replaces the fork's TIEFIX/SORTED post-processing, which corrupted decode on this target (logprob gaps up to 13 nats, stray digit tokens).
* <code><nowiki>VLLM_GLM5_THIN_GEMM</nowiki></code> stays off: 0.75 ms saved but DFlash2 acceptance 4% lower. <code><nowiki>GLM52_LMHEAD_BITS=8</nowiki></code> is optional (about 0.5 ms, small top-1 changes).
* Measured and rejected: TP2 x PP5 (NCCL all-reduce about 100 us on Gen2 x4, about 4.5% net, and it crashed); plain PP8 without the top-k relay; an HBM overclock to NDIV 70 (corrupts output, no ECC); a Triton W8A16 GEMM for the dense INT8 layers (slower than Marlin). MoE experts are about 56% of the step and already stream at the HBM bandwidth limit. Underclocking costs 3 to 5% speed for 10 to 20% power savings.
* <code><nowiki>serve-uncensored.sh</nowiki></code> swaps in an abliterated ("CRACK-edited") GLM-5.3-UNCENSORED-Int4-Int8Mix-AWQ-g64 checkpoint with everything else identical.
{{Source|handle=reala7096|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1557544812972871813|repo=https://github.com/arvkmr/vllm-170hx-glm5}}
* {{Status|Theory}} reala's untested idea: with the x16 mod and PCIe switches, TP2 x PP4 on 8 cards could reach 70 to 80 tok/s at the cost of context; TP2 x PP5 on 10 cards might be the best balance. {{Source|handle=reala7096|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1557546737516679239}}

== Faulty-card procedure ==
One of the author's cards computed all-zero MoE output rows about once per 3,000 decode steps, and occasional garbage
top-k indices, at default clock while passing GEMM and memory tests. <code><nowiki>probe_bang.py 8000 30</nowiki></code> flags any generated
token id 0 with logprob -11.95 (minus ln of the vocab size) as silent corruption: 30 greedy repeats must be identical
with no token 0. Swap two devices in <code><nowiki>CUDA_VISIBLE_DEVICES</nowiki></code> to confirm the fault follows the physical card, then
cap that card with <code><nowiki>gpu-clock-cap.service</nowiki></code> (<code><nowiki>nvidia-smi -i <bus id> -lgc 210,1300</nowiki></code>), which removed the
fault at no measurable decode cost. That card was pulled on 2026-10-03, which is why PP9 and PP8 exist. See
[[Troubleshooting]].
{{Source|handle=reala7096|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1557544812972871813|repo=https://github.com/arvkmr/vllm-170hx-glm5}}

== Known issues ==
* As of 2026-10-30 the fork's remote branches are <code><nowiki>ampere</nowiki></code>, <code><nowiki>main</nowiki></code>, <code><nowiki>plugin</nowiki></code> and two <code><nowiki>queue/*</nowiki></code> branches; <code><nowiki>ampere-glm53</nowiki></code> is gone, so <code><nowiki>install.sh</nowiki></code> (which clones that branch) is likely to fail unless commit 378c37b0 is still reachable by SHA. The recipe sits on the frozen <code><nowiki>ampere</nowiki></code> lineage, not the fork's new plugin layout. See [[Engines]].
* No license file. The drafter is non-commercial, no-derivatives. Single host, single author.
* Full GLM 5.3 lacks vision; Con3po pushed it to 490k context but does not use it for that reason. {{Source|handle=con3po7016|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1557606472811151404}}

== Related ==
* Same model, flags posted in Discord: [[GLM 5.3 on 8x 8 GB (Int4-Int8Mix PP8)]].
* Other full GLM 5.3 results (Impactic's W4A16 on 8 cards, Mountains' EXL3 on 4 CMPs plus an RTX PRO 6000, the lab's NVFP4 TP2 x PP4): [[Recipes]] and [[Benchmarks]].
* The vLLM pipeline hand-off bug at TP2 x PP4 (vLLM PR #60477): [[Engines]].

== Sources ==
* Repo: [https://github.com/arvkmr/vllm-170hx-glm5 arvkmr/vllm-170hx-glm5] (no license file; commits signed Arveen), last commit 2026-10-08. Posted on Discord by reala on 2026-10-08.

{{ImportFooter}}
[[Category:8 GB]]

GLM 5.3 Flash on 4x 8 GB

2026-10-31T21:34:36Z

ImportBot: Import: Morrowmake glm53-flash-cmp170hx-recipe 1.8.0 (repo) plus Discord reports by cibernox, turbine, Mountains, ikyo, 1a2b3c0967, Impactic, peter643, Con3po, Miséricorde and lab notes; gap-fill from #general 2026-10-23 to 10-25: @wakeupmbrc1 (claim, not reproduced), @jjb01957

{{Recipe
|model=GLM-5.3-Flash (320B MoE, 18B active)
|quant=W4A16 (INT4 weights, group size 128, FP16 activations): canada-quant/GLM-5.3-Flash-W4A16-MTP
|engine=Morrowmake/vllm-cmp170hx (vLLM fork, container image)
|engine_version=recipe 1.8.0, engine 819146023f
|cards=8 GB
|card_count=4
|topology=TP4 (default) or PP4
|context=262,144
|decode_tps=442.1
|prefill_tps=3161
|vram_per_card=64 GiB exposed, --gpu-memory-utilization 0.95
|power_cap=180 W
|driver=NVIDIA 580 or newer; P2P needs the Morrowmake/cmpunlocker build
|unlock_build=cmpunlocker (64 GiB, 74 SMs); Morrowmake/cmpunlocker for P2P
|flags=LAYOUT=tp4 or LAYOUT=pp4, P2P=auto, --max-num-seqs 8, --gpu-memory-utilization 0.95, --max-num-batched-tokens 3463 (TP4) or 2312 (PP4)
|status=Reported
|tested_by=voidgiraffe
|tested_on=2026-10-16
|source=https://github.com/Morrowmake/glm53-flash-cmp170hx-recipe
}}
The community's reference build for four cards: GLM-5.3-Flash in W4A16 on Morrowmake's Ampere vLLM fork, with a
DFlash2 speculative drafter, tool calls, reasoning, images and video, behind an OpenAI-compatible API. Most 4-card
owners run W4A16 on this recipe, and Impactic says nobody really cares to upgrade past it. Infobox numbers are the
author's TP4 release figures for one user on code.
{{Source|handle=gnasherrr|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564473314502508557}} 
{{Source|handle=ob88594|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556898939234558013|repo=https://github.com/Morrowmake/glm53-flash-cmp170hx-recipe}} 
{{Source|handle=impactic|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563623398037393520}}

== Prerequisites ==
* Four CMP 170HX that each expose 64 GiB (<code><nowiki>nvidia-smi</nowiki></code> shows 65,536 MiB). The preflight stops below 61,440 MiB. See [[Driver unlock]] and [[8 GB card]].
* PCIe Gen2 x16 links for TP4 (the x16 capacitor modification). Cards stuck at x4 should use PP4. See [[Unlocks]].
* NVIDIA driver 580 or newer, Docker with the NVIDIA Container Toolkit. <code><nowiki>docker run --rm --gpus all nvidia/cuda:13.3.1-base-ubuntu24.04 nvidia-smi</nowiki></code> must list all four cards.
* Optional: a P2P-capable driver build (Morrowmake/cmpunlocker: mainline cmpunlocker plus the maintainer P2P patch and the TRAP31 PLM patch, <code><nowiki>ForceP2P=0x11</nowiki></code>). Without it the server runs with P2P off.
* About 180 GiB (193 GB) of disk for the two checkpoints (about 178 GiB model, 2.2 GiB drafter), plus the engine image and compile caches.
* <code><nowiki>git</nowiki></code>, <code><nowiki>curl</nowiki></code>, <code><nowiki>flock</nowiki></code>, <code><nowiki>setsid</nowiki></code>, <code><nowiki>python3</nowiki></code>, <code><nowiki>jq</nowiki></code>.
{{Source|handle=ob88594|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556898939234558013|repo=https://github.com/Morrowmake/glm53-flash-cmp170hx-recipe}}

== Steps ==
<syntaxhighlight lang="bash">
git clone https://github.com/Morrowmake/glm53-flash-cmp170hx-recipe.git
cd glm53-flash-cmp170hx-recipe
./start.sh # pull the engine image by digest, fetch the model, start, wait for /health
./start.sh smoke # one chat request and one tool call
</syntaxhighlight>
Pick the layout with one variable, either in <code><nowiki>.env</nowiki></code> or as a prefix: <code><nowiki>LAYOUT=pp4 ./start.sh restart</nowiki></code>.
<code><nowiki>./start.sh</nowiki></code> checks link width and suggests PP4 if a card is narrower than x16. Docker Compose is the
alternative (<code><nowiki>docker compose up</nowiki></code>); use one or the other. Other subcommands: <code><nowiki>status</nowiki></code>,
<code><nowiki>logs</nowiki></code>, <code><nowiki>stop</nowiki></code>, <code><nowiki>restart</nowiki></code>, <code><nowiki>update</nowiki></code>; <code><nowiki>DRY=1 ./start.sh</nowiki></code> prints the
launch without running it.

Test request:
<syntaxhighlight lang="bash">
curl http://127.0.0.1:8000/v1/chat/completions -H 'Content-Type: application/json' \
-d '{"model": "glm-5.3-flash", "messages": [{"role": "user", "content": "Write a haiku about PCIe."}], "max_tokens": 4096}'
</syntaxhighlight>
The API listens on 127.0.0.1:8000 with no key unless <code><nowiki>HOST</nowiki></code> and <code><nowiki>API_KEY</nowiki></code> are set in
<code><nowiki>.env</nowiki></code>. The first boot compiles kernels into <code><nowiki>./cache</nowiki></code> and is slow; "No available shared memory
broadcast block found in 60 seconds" lines during that compile are harmless.
{{Source|handle=ob88594|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556898939234558013|repo=https://github.com/Morrowmake/glm53-flash-cmp170hx-recipe}}

=== What the release pins ===
* Engine: Morrowmake/vllm-cmp170hx branch <code><nowiki>ampere</nowiki></code> at <code><nowiki>819146023facb31c04f1f8512e52464835a10d40</nowiki></code> (tag <code><nowiki>glm53-recipe-1.8.0</nowiki></code>), on upstream vLLM 4e0681ed56. Image <code><nowiki>ghcr.io/morrowmake/vllm-cmp170hx:engine-819146023f</nowiki></code>, digest <code><nowiki>sha256:18a2f26207568128e1d792ce923e86a74e40def1e43e492db83132cab8cdbe14</nowiki></code>.
* Model: [https://huggingface.co/canada-quant/GLM-5.3-Flash-W4A16-MTP canada-quant/GLM-5.3-Flash-W4A16-MTP] at revision <code><nowiki>5681f7c2</nowiki></code> (base [https://huggingface.co/zai-org/GLM-5.3-Flash zai-org/GLM-5.3-Flash]).
* Drafter: [https://huggingface.co/incoai/GLM-5.3-Flash-DFlash2 incoai/GLM-5.3-Flash-DFlash2] at revision <code><nowiki>bf582e4e</nowiki></code>. It drafts up to 7 tokens for one user, 5 at two, 3 under load.
* KV cache full precision, no FP8 anywhere, no CPU or disk offload. Defaults: 262,144 context, <code><nowiki>--max-num-seqs 8</nowiki></code>, <code><nowiki>--gpu-memory-utilization 0.95</nowiki></code>, prefill chunks of 3,456 tokens (TP4) or 2,304 (PP4), fair prefill in 384-token slices, prefix caching on, <code><nowiki>glm47</nowiki></code> reasoning and tool parsers.
* Every performance feature is a one-variable kill switch set by <code><nowiki>serve.sh</nowiki></code>. Keep <code><nowiki>PREFILL_CAP=0</nowiki></code>. <code><nowiki>VLLM_CUSTOM_ALLREDUCE_ALGO=2stage</nowiki></code> is set because the built-in crossover is tuned for NVLink. 1.8.0 renamed every <code><nowiki>VLLM_GLM5_*</nowiki></code> switch; old names are ignored with a warning.
{{Source|handle=ob88594|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556898939234558013|repo=https://github.com/Morrowmake/glm53-flash-cmp170hx-recipe}}

* Pin the release tag, not the branch: the fork's <code><nowiki>ampere</nowiki></code> branch was rebased onto new upstream on 2026-10-26, more than 1,000 commits past 1.8.0. {{Source|handle=darkmaniac7|date=2026-10-26|note=lab notes}}

=== P2P ===
With <code><nowiki>P2P=auto</nowiki></code> (default) the recipe content-checks every ordered GPU pair at start (cudaMemcpyPeer, SM-kernel
peer reads and writes, a separate-process CUDA IPC write; 128 KiB and 512 KiB with one byte either side, plus 1, 8 and
32 MiB). A pass sets <code><nowiki>VLLM_CUSTOM_ALLREDUCE_PCIE_P2P=1</nowiki></code> and <code><nowiki>NCCL_P2P_LEVEL=SYS</nowiki></code>; a fail sets
<code><nowiki>NCCL_P2P_DISABLE=1</nowiki></code> and TP uses a host-staged all-reduce. <code><nowiki>nvidia-smi topo</nowiki></code> saying OK is not a
data-integrity test. See [[Unlocks]] for the P2P driver.
{{Source|handle=ob88594|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556898939234558013|repo=https://github.com/Morrowmake/glm53-flash-cmp170hx-recipe}}

== Measured numbers ==
Author's release 1.8.0, measured 2026-10-16 at 74 SMs and 180 W per card, PCIe x16, P2P verified, MiaAI-Lab protocol
(400 tokens, temperature 0). Tok/s as structured / code / prose.

{| class="wikitable"
! Layout !! 1 user !! 2 users !! 4 users !! 8 users !! Cold prefill !! KV pool
|-
| TP4 || 482.6 / 442.1 / 232.1 || 606.5 / 460.3 / 314.7 || 717.7 / 618.7 / 501.4 || 943.7 / 835.0 / 667.2 || 3,161 || 1,203,765
|-
| PP4 || 232.4 / 209.9 / 100.1 || || || 664.1 / 608.8 / 469.2 || 7,419 || 2,088,960
|}
Quality (TP4): HumanEval 151/164, GSM8K 1,286/1,319.
{{Source|handle=ob88594|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556898939234558013|repo=https://github.com/Morrowmake/glm53-flash-cmp170hx-recipe}}

=== Other people's numbers on this recipe ===
* cibernox (daily driver, x16, P2P on, TP4): over 350 tok/s in short bursts, 270+ tok/s on real workflows. {{Source|handle=cibernox|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1559515598797672479}} About 800 tok/s aggregate across agents. {{Source|handle=cibernox|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1561716217897689259}}
* turbine (TP4): 317 tok/s at batch 1 on code, 164 on prose. {{Source|handle=turbine|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1564557999463202917}}
* Mountains (PP4 on PCIe Gen2 x4 links): 90 to 140 tok/s decode with a 1M context window, prefill around 3k tok/s. {{Source|handle=mountains1605|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556410859117482025}} 340 tok/s total at 8 concurrent on real agent work. {{Source|handle=mountains1605|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1557598774887710792}}
* ikyo (first 4-card run, an early release Morrowmake said had bugs; 768-token answers, reasoning counted): concurrency 1 161.8 tok/s per user; 2: 124.3 per user, 231.0 aggregate; 4: 92.6 / 307.5; 8: 51.7 / 296.1 with 4.55 s median TTFT. Single user by workload: structured 182.1, code 161.8, prose 141.2. {{Source|handle=ikyo|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556906534926028921}}
* 1a2b3c0967 (release 1.7, PP4): concurrency 3, 1M context, KV pool about 3M tokens, still over 75 tok/s on prose. {{Source|handle=1a2b3c0967|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556144621451747412}}
* peter643 (4x 64 GB capped at 180 W, P2P on; recipe not named): 200 to 400 tok/s at single concurrency, about 104 W per card while generating, just over 400 W for the four cards. {{Source|handle=peter643|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562011301243523115}}
* PixelML's Club CMP 170HX (four cards behind two PLX switches on a Broadwell host, release 1.6.0): 396.0 tok/s structured for one user and 798.6 at eight users at 180 W with P2P off, matching Morrowmake's own EPYC P2P-off figures (394.0 / 797.9); 418.0 / 816.5 after equalising HBM clocks, at 150 W. {{Source|handle=c133|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562161732137386127|repo=https://github.com/PixelML/club-170hx}}
* The lab (8-card box, two TP4 instances of this recipe, abliterated W4A16 + MTP checkpoint in place of canada-quant's, 1,024-token answers, effort low, NCCL only): see the layout table below. {{Source|handle=darkmaniac7|date=2026-10-28|note=lab notes}}
* {{Status|Reported}} Miséricorde, a claim that has not been reproduced: four cards on Morrowmake's runtime reach 1,000+ tok/s at 8 concurrent and 350+ tok/s at one stream on code, with "some millions" of tokens of KV, and Morrowmake's published numbers are for stock cards at lower power limits. He posted no setup, power limit or log; the release figures above for code are 442.1 tok/s (1 user) and 835.0 (8 users) at 180 W. He also finds GLM 5.3 Flash about 2x less verbose than Qwen 3.8 27B and 2 to 3x faster on code. Summary of his posts; see [https://discord.com/channels/1518634379604136178/1518692084729511967/1563780170735816828 Discord]. {{Source|handle=wakeupmbrc1|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563206459955609635}} {{Source|handle=wakeupmbrc1|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563206518537457676}} {{Source|handle=wakeupmbrc1|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563206538083041301}} {{Source|handle=wakeupmbrc1|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563780086359003279}} {{Source|handle=wakeupmbrc1|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563780170735816828}} {{Source|handle=wakeupmbrc1|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563780191715856415}} {{Source|handle=wakeupmbrc1|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563780259097092150}} {{Source|handle=wakeupmbrc1|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563780268819619881}} {{Source|handle=wakeupmbrc1|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563780320774586479}}

== Layouts ==
The recipe ships TP4 and PP4. Measured trade-offs from the Discord:
* TP4 over PCIe Gen2 needs x16 links. On x4 links decode is usable but prefill is not, and PP4 feels snappier in conversation because prefill drives that feeling. {{Source|handle=voidgiraffe|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556157382273400935}} {{Source|handle=1a2b3c0967|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556160688219627542}}
* The x16 mod is not required: Finishtilt14 runs the recipe without it and it runs well in TP or PP. {{Source|handle=finishtilt14|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1559516402849939478}}
* Mountains got P2P working, tried TP, and went back to PP4 because prefill on very long contexts is better. {{Source|handle=mountains1605|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1560411703114596473}}
* TP2 x PP2 (community flavour by cibernox on four x16 cards behind one PCIe switch): decode slower than TP4, prefill above 5k tok/s, so it sits between PP4 and TP4. He suggests it for people stuck on x4 links; not measured on x4. {{Source|handle=cibernox|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1557424695370850426}}

Lab measurements, same bench on all three (single stream code / structured / prose, aggregate at 8 users, 17k-token
prefill):

{| class="wikitable"
! Layout !! 1 user !! 8 users !! Prefill 17k !! TTFT on a 49k prompt !! KV pool at 262K
|-
| TP4 || 252 / 235 / 139 || 623 / 617 / 421 || 1.7k || 18 s || 1.20M
|-
| TP2 x PP2 || 171 / 146 / 98 || 567 / 503 / 383 || 4.2k || 11 s || 1.14M
|-
| TP1 x PP4 || 113 / 121 / 71 || 499 / 515 / 376 || 6.8k || not measured || 2.09M
|}
TP2 x PP2 suits long prompts with short answers (coding agents); PP4 suits prefill-bound batch work. Raising
<code><nowiki>MAX_BATCHED</nowiki></code> to 8192 gave nothing on TP4 or TP2 x PP2 and cost KV.
{{Source|handle=darkmaniac7|date=2026-10-28|note=lab notes}}

On eight cards as a single instance (the lab, cap 250 W): TP8 gave 95 / 105 / 56 tok/s for one user and 440 aggregate at 8
users with 554 tok/s prefill, because the 8-way all-reduce over Gen2 plus the socket hop dominates. TP4 x PP2 gave
103 / 145 / 38 for one user, dropped to 38 tok/s per stream at 2 users and only paid off at 32 users (492 aggregate) and
in prefill (1,856). Two TP4 instances, one per CPU socket, is the better use of eight cards.
{{Source|handle=darkmaniac7|date=2026-10-27|note=lab notes}}

=== Gen2 x8 without P2P (the lab, in an ESXi VM) ===
The lab ran release 1.8.0 exactly as published (canada-quant checkpoint, DFlash2) on four 8 GB cards inside an ESXi
guest at Gen2 x8 with no P2P (host-staged collectives), 180 W, on the recipe's own MiaAI protocol. Tok/s structured /
code / prose at 74 SMs, the published figures in brackets:
{| class="wikitable"
! Layout !! 1 user !! 2 users !! 4 users !! 8 users !! Cold 32k prefill
|-
| TP4 || 361 / 284 / 199 (483 / 442 / 232) || 441 / 371 / 273 (607 / 460 / 315) || 545 / 468 / 401 (718 / 619 / 501) || 697 / 587 / 529 (944 / 835 / 667) || 1,633-1,753 (3,161)
|-
| PP4 || 201 / 149 / 97 (232 / 210 / 100) || 309 / 223 / 183 (344 / 273 / 196) || 386 / 353 / 300 (409 / 383 / 314) || 664 / 548 / 477 (664 / 609 / 469) || 6,834-6,977 (7,419)
|}
PP4 lands close to the published numbers, so it is not link-bound. TP4 sits at about 0.75x because its all-reduce goes
through host memory over Gen2 x8. Draft acceptance matched the published regime (95-99% structured, 74-89% code, 41-48%
prose), so the drafter is not the gap. The 74-SM unlock (70 to 74) was decode-neutral within noise and worth 2-5% on PP4
prefill; clear the torch.compile and Triton caches when the SM count changes. Single-user prose varies about 10% boot to
boot at temperature 0, other cells about 3%. TP4 settings there: <code><nowiki>VLLM_HOST_ALLREDUCE=1</nowiki></code>,
<code><nowiki>VLLM_HOST_ALLREDUCE_MAX_SIZE=524288</nowiki></code> (32 MiB was 9% slower on prefill), custom all-reduce off. A clock lock
(<code><nowiki>nvidia-smi -lgc 1410,1410</nowiki></code>) did nothing: the cards already run 1,410 MHz under load. Recommendation: PP4 for
long prompts, RAG, agents and many streams; TP4 for one interactive user with short prompts.
{{Source|handle=darkmaniac7|date=2026-10-19|note=lab notes}}

=== Drafter settings ===
On TP4 (the lab's VM runs), DFlash2 with the release's adaptive table (7 / 5 / 3 drafts by load) is the best single
setting for every workload and user count: it is worth 3.6x / 2.8x / 2.0x over no drafter for one user (structured /
code / prose) and still 1.25-1.5x at eight users. An adaptive [7,7,5] table helps agent traffic (+14% structured, +7%
code at 4 users) and costs prose. Without a drafter TP4 decodes 101 tok/s (9.9 ms per step), PP4 48 tok/s. Deeper
drafts do not pay on these cards: each extra draft token costs about 1.1 ms of verify per step (21.2 / 23.4 / 25.6 ms at
depth 7 / 8 / 10), and depth 8 trips an assert in the fork's fused sm_80 KDA decode kernel without a patch.
{{Source|handle=darkmaniac7|date=2026-10-20|note=lab notes}}

=== Planning a custom split ===
The model has 45 decoder layers (dense MLP at 0-2, MoE at 3-44), with 11 sparse MLA attention layers at 3, 7, 11 ... 43
and KDA linear attention elsewhere. <code><nowiki>VLLM_PP_LAYER_PARTITION</nowiki></code> needs one entry per stage summing to 45 (the
MTP layer is not counted), and every pipeline stage must hold at least one MLA layer. Each rank plans its own KV pool and
all ranks are cut to the smallest, so a split must balance memory as well as compute. Explicit <code><nowiki>PP</nowiki></code> and
<code><nowiki>TP</nowiki></code> keys override <code><nowiki>LAYOUT</nowiki></code>.
{{Source|handle=darkmaniac7|date=2026-10-19|note=lab notes}}

== Eight cards ==
* Two instances of the recipe: about 1,600 tok/s aggregate on 8 cards (two PP4 groups, or two TP4 groups if x16 modded), release 1.6, power limit 180 to 200 W. {{Source|handle=impactic|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1561913182132375593}}
* Miséricorde expects 2,000+ if the cards are tuned and you can cool a 230 to 250 W power limit (not measured). {{Status|Theory}} {{Source|handle=wakeupmbrc1|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1561913397082325033}}
* Con3po runs two GLM 5.3 Flash instances on 8 cards for an agent farm: 6 VMs and 8 sub-agents, about 12 s per action. {{Source|handle=con3po7016|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560773140257312779}}

== KV cache and context ==
* Vanilla TP4 startup line on cibernox's box: "GPU KV cache size: 1,204,813 tokens, Maximum concurrency for 262,144 tokens per request: 4.60x". He notes FP8 KV would roughly double it and that vLLM shares the cache, so five parallel 250k sub-agents rarely collide. {{Source|handle=cibernox|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1560687961530572833}}
* Dropping <code><nowiki>--max-num-seqs</nowiki></code> from 8 to 3 grew 1a2b3c0967's pool from 1.9M to about 3.5M tokens. He credits the 16-bit KV cache for the model staying sharp at high context; Morrowmake says research shows little loss from KV quantization but people report otherwise. {{Source|handle=1a2b3c0967|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556154620588466276}} {{Source|handle=voidgiraffe|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556142515491704976}}
* Con3po runs 1.3M max context stable on 4 cards. {{Source|handle=con3po7016|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1557605746945036419}}
* Miséricorde: 4 cards serve 8 users with W4A16 plus 4.5M tokens of KV, for example 9 threads at 500k each. {{Status|Contested}} cibernox gets 1.2M on the stock recipe; the 4.5M figure needs a smaller sequence count or FP8 KV. {{Source|handle=wakeupmbrc1|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1560673558122987571}} {{Source|handle=cibernox|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1560682309978427494}}

== Power ==
* The published numbers are at 180 W per card on stock cards; tuned cards could add maybe 20%. {{Source|handle=wakeupmbrc1|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1561897014189367309}}
* peter643 sees about 104 W per card while generating under a 180 W cap; at idle he downclocks and relaxes the HBM refresh to about 25 W per card. {{Source|handle=peter643|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562011301243523115}}
* PixelML's power curve for this recipe (TP4, HBM 1,728 MHz; structured tok/s one user / eight users / four-card GPU power / tokens per watt): 165 W 418.6 / 822.4 / 650 W / 1.27; 150 W 418.0 / 816.5 / 582 W / 1.40; 140 W 412.7 / 814.2 / 537 W / 1.52; 120 W 374.4 / 756.5 / 476 W / 1.59; 110 W 340.1 / 706.8 / 436 W / 1.62; 100 W 291.9 / 627.4 / 398 W. Below 130 W the core clock falls fast. A driver reload or guest reboot resets the cap to the VBIOS default of 250 W, so re-apply it. {{Source|handle=c133|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562161732137386127|repo=https://github.com/PixelML/club-170hx}}
See [[Cooling and power]] and [[Tools]] for caps and clock tools.

== Known issues ==
* Release 1.7 had a TP4 lost-context / endless-repetition bug when a speculative step ended exactly on a 1,152-token block boundary. Fixed in 1.7.2, along with GPU memory growth over hours and garbage output after a non-local cached prefix. Two-card owners hit by the repetition moved to the ExLlamaV3 builds; the fix only concerned 4 cards. {{Source|handle=ob88594|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556898939234558013|repo=https://github.com/Morrowmake/glm53-flash-cmp170hx-recipe}} {{Source|handle=mountains1605|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1559793849239478352}}
* GLM-5.3 always reasons. Set <code><nowiki>max_tokens</nowiki></code> for reasoning plus answer, or <code><nowiki>content</nowiki></code> comes back empty with <code><nowiki>finish_reason: "length"</nowiki></code>. <code><nowiki>enable_thinking: false</nowiki></code> is ignored; use <code><nowiki>reasoning_effort</nowiki></code> (low, high, max).
* From Z.ai's model notes: <code><nowiki>reasoning_effort</nowiki></code> on GLM-5.3-Flash accepts low, high and max and defaults to max when omitted or set to anything else; the chat template's <code><nowiki>clear_thinking</nowiki></code> defaults to false, so pass true for chat (toggling it mid-conversation costs the prompt cache). {{Source|handle=cmdrwaka324|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1557656402435121172|repo=https://github.com/zai-org/GLM-5}}
* PP4 on real x4 links is not measured by the author (Mountains' numbers above are the field data).
* The default DFlash2 drafter is CC BY-NC-ND 4.0, so the published configuration is non-commercial.
* Updating is forward-only; older images may be retired.
{{Source|handle=ob88594|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556898939234558013|repo=https://github.com/Morrowmake/glm53-flash-cmp170hx-recipe}}
* {{Status|Contested}} Custom all-reduce on Gen2. The recipe turns vLLM's custom all-reduce on after the P2P check. On the lab box it first hung all workers at init for 20+ minutes; the cause was stale build locks in the compile cache. Once it started, on GLM TP4 it cost about 40% decode for 13% more prefill (205 vs 252 tok/s single, 380 vs 623 aggregate at 8), so its production runs NCCL only (<code><nowiki>VLLM_CUSTOM_ALLREDUCE_PCIE_P2P=0</nowiki></code>). On the Qwen3.8 Flash Next TP2 recipe the same switch helped instead (see [[Qwen3.8 Flash Next on 2x 8 GB (ElectroHobo W4A16 TP2)]]). A/B it on your box. {{Source|handle=darkmaniac7|date=2026-10-27|note=lab notes}}
* {{Status|Contested}} P2P on TP4. Morrowmake measured P2P helping on his EPYC host (about +11%) and his release numbers are with P2P verified. PixelML measured it hurting on their PLX + Broadwell host (-20 to -26% for one user, -38 to -48% at eight users, decode step 19.4 to 26.1 ms) and runs TP4 with P2P off (398.4 / 812.0 tok/s). ElectroHobo found the opposite on the same kind of host for MiMo V2.6 Flash, where P2P off is about 40% slower. {{Source|handle=nathang6866|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1561264547455569952|repo=https://github.com/ElectroHobo/mimo-v26-flash-cmp170hx-recipe}} {{Source|handle=c133|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562161732137386127|repo=https://github.com/PixelML/club-170hx}}
* canada-quant's GLM-5.3-Flash-DFlash2-G drafter does not load on this engine (indexer.k_cache page size error); NVFP4 GLM checkpoints do not run on sm_80 (SM12x FlashInfer only). {{Source|handle=c133|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562161732137386127|repo=https://github.com/PixelML/club-170hx}}
* <code><nowiki>MAX_SEQS=16</nowiki></code> on TP4 crashed vLLM's CUDA-graph profiling ("operation not permitted"); keep 8 per instance. {{Source|handle=darkmaniac7|date=2026-10-27|note=lab notes}}
* MTP is broken on PP4 in this fork: acceptance 0.27 / 0.11 / 0.08 and 53 / 40 / 38 tok/s, worse than no drafter (48), because the MTP head gets the wrong inputs on the pipeline layout; the recipe lists MTP as unsupported there. PP2 with <code><nowiki>SPEC_MODE</nowiki></code> none or mtp failed to come up. The no-drafter mode fails the recipe's boot check (missing spec-decode counters): run it with <code><nowiki>BOOT_CHECK=0</nowiki></code>. {{Source|handle=darkmaniac7|date=2026-10-19|note=lab notes}}
* <code><nowiki>./start.sh stop</nowiki></code> needs the recipe's lifecycle lock and exits 1 without stopping anything if another command holds it. When passing a GPU subset to Docker, keep the inner double quotes (<code><nowiki>GPUS='"device=0,1,2,3"'</nowiki></code>), because Docker parses it as CSV. Do not benchmark while a CPU-heavy job runs on the host: layouts benched beside one read 180 / 126 / 94 instead of 247 / 233 / 138. {{Source|handle=darkmaniac7|date=2026-10-28|note=lab notes}}
* Running the recipe's checkpoint on the lazymio/vllm-backport engine instead does not work: the loader fails on the first dense layer (KeyError on <code><nowiki>layers.0.mlp.gate_up_proj.weight</nowiki></code>). {{Source|handle=darkmaniac7|date=2026-10-28|note=lab notes}}

== With other GPUs in the same job ==
The lab runs the same engine across CMP and RTX PRO 6000 Blackwell cards in one vLLM job (sm_80 + sm_120):
* Two CMPs as pipeline stage 0 (12 of 45 layers) plus two Blackwells as stage 1 (33 layers), PP2 x TP2: 349 / 261 / 180 tok/s for one user (structured / code / prose), 895 / 703 / 611 at eight users, the best eight-user aggregate the lab measured; 32k cold prefill in 5.95 s; a 996,784-token prompt prefilled in 206 s; KV pool 1.9M tokens at 262k (2.19M at 1M context in production). Two CMPs stay idle, because two cards cannot hold the 178 GB model.
* Four CMPs plus two Blackwells: PP3 x TP2 gave 553 / 484 / 425 tok/s at eight users (code / JSON / prose) and a 7.1M-token KV pool; PP6 x TP1 prefilled 32k in 2.92 s (11,174 tok/s). Single-user decode was lower than a Blackwell-only stack.
* It needs three small Python patches to the fork (device capability per rank, the MLA backend on sm_120, the host-staged all-reduce only on sm_80 TP groups) and launch settings: <code><nowiki>kda_prefill_backend: triton</nowiki></code>, <code><nowiki>CUTE_DSL_ARCH=sm_120a</nowiki></code>, FlashInfer autotune off, Blackwells as the last stage, every stage holding at least one MLA layer.
* Raising HBM to 1,728 MHz on the two CMPs gave only +1.6-1.9% single stream in this hybrid, because the Blackwell stage dominates the step.
{{Source|handle=darkmaniac7|date=2026-10-19|note=lab notes}}

== Variants and related ==
* Three cards: [[GLM 5.3 Flash on 3x 8 GB]].
* Two cards: [[GLM 5.3 Flash on 2x 8 GB (ExLlamaV3 TP2)]], [[GLM 5.3 Flash on 2x 8 GB (ExLlamaV3 layer split)]], [[GLM 5.3 Flash on 2x 8 GB (Project Maya)]].
* Engine notes: [[Engines]]. Quant choices: [[Quantization on the 170HX]]. All numbers: [[Benchmarks]].
* Abliterated: the lab re-quantized dealignai's uncensored GLM-5.3-Flash FP8 checkpoint to the same W4A16 format for this engine (see [[Quantization on the 170HX#Heretic and abliterated variants]]); with the base-trained DFlash2 drafter it runs at 88-97% of the base's speed (one user 349 / 254 / 181 against 361 / 284 / 199). {{Source|handle=darkmaniac7|date=2026-10-19|note=lab notes}}
* Refusal steering: the Weightless GLP-44 vector (msuiche/weightless) is ported to the ExLlamaV3 two-card build, not to this recipe.

== Sources ==
* Repo: [https://github.com/Morrowmake/glm53-flash-cmp170hx-recipe Morrowmake/glm53-flash-cmp170hx-recipe] (MIT), last commit 2026-10-26. Posted on Discord by OB88594, Mountains and jjb. {{Source|handle=ob88594|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556898939234558013}}
* Model: [https://huggingface.co/zai-org/GLM-5.3-Flash zai-org/GLM-5.3-Flash] (MIT); vendor notes in [https://github.com/zai-org/GLM-5 zai-org/GLM-5].
* jjb's pointers for this stack (2026-10-23): the recipe, the fork's [https://github.com/Morrowmake/vllm-cmp170hx/tree/ampere-glm53 ampere-glm53 branch], [https://github.com/wtdcode/vllm-backport wtdcode/vllm-backport] as an alternative or backport reference, and the existing [https://huggingface.co/wtdcode/GLM-5.3-Flash-AWQ-W4A16 wtdcode/GLM-5.3-Flash-AWQ-W4A16] checkpoint. The 1.8.0 release on this page pins the <code><nowiki>ampere</nowiki></code> branch and canada-quant's checkpoint instead. {{Source|handle=jjb01957|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563303837937176596|repo=https://github.com/Morrowmake/glm53-flash-cmp170hx-recipe}}
* Lab notes, 2026-10-27 and 2026-10-28.

{{ImportFooter}}
[[Category:8 GB]]

Engines

2026-10-31T21:34:35Z

ImportBot: Import: Inference engines on the CMP 170HX (sm_80): vLLM forks (Morrowmake/vllm-cmp170hx, wtdcode/vllm-backport, arvkmr, clee and others), Deepinfer-SM80, ExLlamaV3 and TabbyAPI, llama.cpp, Strata and Project Maya, sglang, speculative decoding; from repos.json, Discord and lab notes; sources: @voidgiraffe, @jjb01957, @matstatman, @darkmaniac7, @reala7096, @c133, @gnasherrr, @exile_1ck, @xtj7, @68x0, @segmond, @wingrimez_40467 (+20 more); GitHub 1CatAI/1Cat-vLLM, Flun/glm53-fl

The CMP 170HX is a GA100 die with compute capability 8.0 (sm_80, the A100 family), 64 GB of HBM after the unlock
([[Driver unlock]]), no NVLink and PCIe Gen2 at best ([[Unlocks]]). Engines built for Hopper or Blackwell kernels do not
run on it as shipped, and engines that assume NVLink lose time in all-reduce. This page lists what runs, which recipes
use it, and the flags and traps that matter. For the per-model setups see [[Recipes]].

== Summary ==
{| class="wikitable"
! Engine !! What it is !! sm_80 status !! Used by
|-
| [https://github.com/Morrowmake/vllm-cmp170hx Morrowmake/vllm-cmp170hx] || vLLM with an sm_80 plugin and a short patch queue || the reference CMP engine || [[GLM 5.3 Flash on 4x 8 GB]], [[DeepSeek V4.1 Flash on 4x 8 GB (Morrowmake)]], [[Qwen3.8 Flash Next on 2x 8 GB (Morrowmake EXL3)]], the ElectroHobo recipes, CurtisAccelerate, arvkmr
|-
| [https://github.com/wtdcode/vllm-backport wtdcode/vllm-backport] || vLLM fork for frontier MoE models on Ampere and Ada (A100, A6000, 3090), images <code><nowiki>lazymio/vllm-backport:*-sm80</nowiki></code> || runs; not CMP-specific || [[Qwen3.8 Flash Next on 2x 8 GB (mannydelrio PP2)]], matstatman's 4-card Qwen, the lab's full GLM 5.3
|-
| [https://github.com/HalfVulpes/Deepinfer-SM80 HalfVulpes/Deepinfer-SM80] || DeepInfer ideas ported to sm_80 as two vLLM patches + 30 drop-ins || measured on 74-SM CMP cards || [[DeepSeek V4.1 Flash on 6x 8 GB (Deepinfer-SM80 TP2 x PP3)]], [[DeepSeek V4.1 Flash on 8x 8 GB (Deepinfer-SM80 TP4 x PP2)]], the GNmac image
|-
| Patched upstream vLLM || per-recipe patch sets on a pinned commit or PR || works where patched || Zanooda (PR #56201 + 20 patches), iIIusi0n (a5a30471 + 13-file patch), clee/vllm-sm80, vektorprime (PR #53899), DUFRelic (v0.30.0 + zankich INT4-PLE plugin), wgkbfcp (79a7108d)
|-
| [https://github.com/turboderp-org/exllamav3 ExLlamaV3] + TabbyAPI || EXL3 quants, layer split or TP || runs; compute-bound on sm_80 || [[GLM 5.3 Flash on 2x 8 GB (ExLlamaV3 TP2)]], [[GLM 5.3 Flash on 2x 8 GB (ExLlamaV3 layer split)]], [[DeepSeek V4.1 Flash on 4x 8 GB plus RTX PRO 6000 (ExLlamaV3 TP5)]]
|-
| [https://github.com/mw00/project-maya Project Maya] / Strata || expert tiering across VRAM, RAM and NVMe (Strata and llama.cpp lineage) || runs (compute capability 7.0+) || [[GLM 5.3 Flash on 2x 8 GB (Project Maya)]], [[DeepSeek V4.1 Flash on 2x 8 GB (Project Maya)]]
|-
| llama.cpp || GGUF || runs, but slow on these cards || not recommended
|-
| sglang || || FP8 Qwen 27B reported || see [[Qwen3.8 27B on 1x 8 GB (W4A16 vLLM)]]
|-
| DeepInfer (upstream), TokenSpeed, 1Cat-vLLM, EAGLE-4 || || not runnable or unmeasured on sm_80 || see below
|}

== Morrowmake/vllm-cmp170hx ==
The engine the community recipes pin. Since late October 2026 it is not a classic fork but a <code><nowiki>vllm-sm80</nowiki></code>
plugin (Python package <code><nowiki>vllm_sm80</nowiki></code> with sm_80 kernels, attention backends, EXL3 and Marlin extensions, model
classes and a launcher) plus a short patch queue on an exact upstream vLLM commit: an engine is three pins (upstream
commit, queue commit, plugin commit). Upstream vLLM's sparse-attention path for GLM-5.3 needs Hopper; this fork adds the
Ampere kernels that make it run at all.
* Branches: <code><nowiki>plugin</nowiki></code> (default), <code><nowiki>queue/330c5bffee</nowiki></code> (development line) and <code><nowiki>queue/165213f911</nowiki></code> (newest tested upstream), <code><nowiki>main</nowiki></code> (plain upstream mirror), <code><nowiki>ampere</nowiki></code> (frozen at 12d6ed3ce0, no more changes). The <code><nowiki>ampere-glm53</nowiki></code> branch is gone. Discord posts before late October describe the old single-tree <code><nowiki>ampere</nowiki></code> branch.
* Recipe pins are tagged and never deleted: <code><nowiki>glm53-recipe-1.3.0</nowiki></code> to <code><nowiki>1.8.0</nowiki></code> (1.8.0 = 819146023f), <code><nowiki>qwen38-recipe-1.0.0</nowiki></code> (18305948ac), <code><nowiki>dsv41-flash-recipe-1.0.0</nowiki></code> (a0c57b5237). Run it through the recipes' container images; that is the supported way.
* Build from source (no GPU needed): Python 3.12, torch 2.14.0, CUDA 12.8+; check out the queue branch and install with <code><nowiki>VLLM_USE_PRECOMPILED=1 VLLM_PRECOMPILED_WHEEL_COMMIT=<upstream commit></nowiki></code>, install the <code><nowiki>plugin</nowiki></code> worktree with <code><nowiki>--no-deps</nowiki></code>, then <code><nowiki>python csrc/exl3/build_standalone.py --out vllm_sm80</nowiki></code> for the EXL3 kernels (optionally <code><nowiki>VLLM_AMPERE_MARLIN_BUILD=1 python csrc/ampere_marlin/build_standalone.py</nowiki></code>). <code><nowiki>vllm_sm80/guard.py</nowiki></code> stops vLLM at start if the plugin is missing.
* EXL3 inside vLLM: <code><nowiki>--quantization exl3 --load-format exl3 --dtype bfloat16</nowiki></code>, integer rates 1 to 8 bits (1.5 / 2.5 / 3.5 need the mul1 codebook), TP cuts must keep 128-channel transform blocks, whole-expert expert parallel; PP other than 1 and LoRA are rejected. Tensor-core paths behind <code><nowiki>VLLM_EXL3_MOE_V2</nowiki></code>, <code><nowiki>VLLM_EXL3_MOE_PREFILL_TC</nowiki></code>, <code><nowiki>VLLM_DEEPSEEK_V41_MOE_PREFILL_TC</nowiki></code> and others. Several dense paths are validated only for 74-SM cards at TP2.
* Speculative decoding: DFlash2 and DSpark speculators, <code><nowiki>adaptive_k</nowiki></code> (draft count by load), <code><nowiki>shard_argmax</nowiki></code>, <code><nowiki>pp_draft_tail</nowiki></code>. PCIe-only helpers: <code><nowiki>host_shm_all_reduce</nowiki></code>, <code><nowiki>ce_ring_all_reduce</nowiki></code>, <code><nowiki>custom_all_reduce_flags</nowiki></code>, a <code><nowiki>pcie_p2p</nowiki></code> gate. A tuning table <code><nowiki>vllm_sm80/tuning/nvidia-cmp-170hx.toml</nowiki></code>. 111 fork environment flags, all off by default; the recipes turn on what they need.
* Contribution rules: sm_80 kernels and model code go to <code><nowiki>plugin</nowiki></code>; hooks in upstream files go to the newest <code><nowiki>queue/*</nowiki></code> branch, one commit per file; recipes for other models or layouts belong in your own repo, must pin the fork's commits, tag the repo <code><nowiki>cmp170hx</nowiki></code> and keep the NOTICE.
* License: Apache-2.0 (LICENSE added 2026-10-29); the plugin also carries MIT code adapted from ExLlamaV3.
{{Source|handle=voidgiraffe|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1560413471055548446|repo=https://github.com/Morrowmake/vllm-cmp170hx}} 
{{Source|handle=jjb01957|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563675495542038650}}

Morrowmake on the plugin layout (2026-10-15/16): most of two weeks went into repeatable processes and into moving all his custom code behind vLLM plugins, so rebasing onto newer vLLM stops being painful; the GLM update and a first Qwen3.8 Flash Next recipe were released with it. He added a community-recipes section to the fork for setups adapted from his, agreed to matstatman's request for a Docker image that contains everything, and said x4 links will hurt prefill (untested) with a PP2 Qwen version to come. {{Source|handle=voidgiraffe|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1560412542096904213}} {{Source|handle=matstatman|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1560414067095765084}} {{Source|handle=voidgiraffe|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1560598988779167825}} {{Source|handle=voidgiraffe|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1560579094666678283}}

== wtdcode/vllm-backport ==
A vLLM fork for frontier MoE models on older Ampere and Ada cards, with prebuilt single-arch Docker images
(<code><nowiki>lazymio/vllm-backport:latest-sm80</nowiki></code>, pinned <code><nowiki>:v0.13.0-sm80</nowiki></code>; no FA3 or Hopper kernels) and a paired LMCache
fork. It is not CMP-specific but is the base of mannydelrio's two-card recipe and the alternative engine lineage to
Morrowmake's.
* Models by fork version: DeepSeek-V4-Flash-0731 native FP4 (0.6.0+), Qwen3.8-27B BF16 / AWQ W4A16 (0.8.0+), Qwen3.8-Flash-Next FP8 + AWQ W4A16 (0.9.0+), GLM-5.3-Flash FP8 + AWQ W4A16 (0.11.2+), DeepSeek-V4.1-Flash native FP4 with Engram (0.13.0+). It publishes wtdcode/Qwen3.8-Flash-Next-AWQ-W4A16 and wtdcode/GLM-5.3-Flash-AWQ-W4A16.
* FULL_AND_PIECEWISE CUDA graphs on Ampere need <code><nowiki>NCCL_ALGO=Ring NCCL_PROTO=Simple</nowiki></code> and preferably <code><nowiki>--disable-custom-all-reduce</nowiki></code>: the "crash on Ampere" was NCCL's size-adaptive algorithm switching under graph replay. Bound <code><nowiki>cudagraph_capture_sizes</nowiki></code>; FULL graphs can cost more than 800 MB per GPU.
* Qwen3.8-Flash-Next: <code><nowiki>VLLM_PLE_CPU_OFFLOAD=1</nowiki></code> keeps the n-gram embedding in pinned host RAM; <code><nowiki>--enable-expert-parallel</nowiki></code> is required (plain TP makes the 640-wide expert intermediate 160 per rank); <code><nowiki>--prefix-match-unit=16</nowiki></code> is effectively mandatory, otherwise nothing under 1,600 tokens is reused.
* DeepSeek V4.1 Flash: <code><nowiki>--engram-config '{"cpu_offload": true}'</nowiki></code>, <code><nowiki>--tokenizer-mode deepseek_v41</nowiki></code>, DSpark K=5. Agentic clients should pass <code><nowiki>reasoning_effort</nowiki></code> from the first turn or sessions drift into reasoning loops.
{{Source|handle=matstatman|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1560599247475314711|repo=https://github.com/wtdcode/vllm-backport}}
* matstatman ran Qwen3.8 Flash Next on four cards with this engine and only 32 GB of host RAM. His compose file, flags and numbers are on [[Qwen3.8 Flash Next on 4x 8 GB]]. {{Source|handle=matstatman|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1560599247475314711}}
* The lab: the full 753B GLM-5.3 (an abliterated NVFP4-expert / INT8 requant) runs on eight cards with this engine at TP2 x PP4 with P2P and MTP, 524K context and a 570K-token KV pool, but only with a one-line worker fix for the pipeline hand-off bug (below): 77 / 76 / 48 tok/s single (code / structured / prose), 172 / 189 / 146 at 8 users, prefill 1,650 tok/s on a 17k prompt, 68% draft acceptance. The int8 KV tile beat plain FP8 KV by 10% single-stream at the same quality. Schema-constrained output (named <code><nowiki>tool_choice</nowiki></code>, <code><nowiki>json_schema</nowiki></code>) returns HTTP 500 with MTP on, because xgrammar rejects the draft tokens; serve that traffic without speculation. GLM-5.3-Flash checkpoints with a dense layer 0 fail to load on it (KeyError on <code><nowiki>layers.0.mlp.gate_up_proj.weight</nowiki></code>). {{Source|handle=darkmaniac7|date=2026-10-28|note=lab notes}}

== Other vLLM patch sets ==
* '''[https://github.com/arvkmr/vllm-170hx-glm5 arvkmr/vllm-170hx-glm5]''': fail-closed source patches on Morrowmake's frozen <code><nowiki>ampere-glm53</nowiki></code> commit that port GLM-5.3's DSA path to sm_80 (packed <code><nowiki>fp8_ds_mla</nowiki></code> KV reader, software e4m3, Triton indexer, canonical top-k, DFlash over PP, top-k PP relay). See [[GLM 5.3 on 8x 8 GB (vllm-170hx-glm5)]]. {{Source|handle=reala7096|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1557544812972871813|repo=https://github.com/arvkmr/vllm-170hx-glm5}}
* '''[https://github.com/clee/vllm-sm80 clee/vllm-sm80]''': pure-Python fork on a pinned vLLM nightly with FP8 KV on sm_80 (software e4m3 decode), PLE under PP>1 and an NVMe-staged PLE reader; its PP KV fix is also used by mannydelrio. See [[Qwen3.8 Flash Next on 3x 8 GB (clee PP3)]]. {{Source|handle=c133|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1556357466026025001|repo=https://github.com/clee/qwen3.8-flash-next-3x170hx}}
* '''Zanooda''': a 20-patch series on vLLM PR #56201 plus haosdent/vllm's dsv4-flash-a100 sm_80 layer, with an sm_80-only image. See [[DeepSeek V4.1 Flash on 8x 8 GB (Zanooda PP8)]]. {{Source|handle=gnasherrr|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560998024136753172}}
* '''iIIusi0n''', '''vektorprime''', '''DUFRelic''' (zankich INT4-PLE plugin), '''wgkbfcp''': see their recipe pages under [[Recipes]].
* eXile has a custom vLLM build aimed at the 170HX running Q3 Qwen 3.8 Flash Next on one 64 GB card; HumanEval matched his Strata results. {{Status|Contested}} Others doubted the prefill figure (xtj7 suspected cache hits); no answer was posted. {{Source|handle=exile_1ck|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560342257532674060}} {{Source|handle=xtj7|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560352992035868753}}

== DeepInfer and Deepinfer-SM80 ==
[https://github.com/deepseek-ai/DeepInfer deepseek-ai/DeepInfer] is DeepSeek's open-sourced inference framework for
DeepSeek-V4.1-Flash (DSpark, SWA bounded replay, batch-invariant modes). Upstream supports only NVIDIA SM100 and Huawei
Ascend 950, so it does not run on the CMP as released. {{Source|handle=68x0|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562102232441299087|repo=https://github.com/deepseek-ai/DeepInfer}}

[https://github.com/HalfVulpes/Deepinfer-SM80 HalfVulpes/Deepinfer-SM80] ports its ideas to sm_80 as two vLLM patches on
the unmerged PR #56201 commit (79a7108d) plus 30 drop-in Python, Triton and TileLang modules. Build with
<code><nowiki>TORCH_CUDA_ARCH_LIST="8.0 8.6"</nowiki></code>, CUDA 13.0, Python 3.12, GCC 13+, torch 2.13.0+cu130; check with
<code><nowiki>scripts/check_dropin_sync.py</nowiki></code> ("30 same, 0 diff, 0 missing") and <code><nowiki>scripts/verify_env.py</nowiki></code>. Kernel speedups on
74-SM sm_80: <code><nowiki>_combine_topk_swa_indices_kernel</nowiki></code> 22.17x (bit-exact), <code><nowiki>dequantize_and_gather_k_cache</nowiki></code> 4.02x at 16K
and 7.64x at 48K, mHC fused post/pre 2.89x, sparse-attention decode 2.08 to 2.14x, sparse prefill 1.17x. 108-SM parts
(A100, A800) gain less because the tunings are wave-aligned for 74 SMs. The patches do not apply to newer vLLM main.
{{Source|handle=segmond|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562224915501813811}} 
{{Source|handle=reala7096|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562151531690860657|repo=https://github.com/HalfVulpes/Deepinfer-SM80}}

== ExLlamaV3, TabbyAPI and EXL3 ==
* turboderp's ExLlamaV3 loads EXL3 quants (for example turboderp/GLM-5.3-Flash-exl3 at 3.05 bpw) and runs on sm_80 when built with <code><nowiki>TORCH_CUDA_ARCH_LIST=8.0</nowiki></code>. The two-card GLM recipes use it with layer split or tensor parallel over NCCL; anoane serves DeepSeek V4.1 Flash through an ExLlamaV3 fork plus a TabbyAPI fork (TabbyAPI is AGPL-3.0). vcruz305/vllm-exl3 (AGPL-3.0) brings EXL3 into vLLM and is part of the GNmac image. {{Source|handle=wingrimez_40467|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1562164200372179017|repo=https://github.com/Flun/glm53-flash-cmp170hx-exl3}} {{Source|handle=anon33anon|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561903682608697426|repo=https://github.com/anoane/09-deepseek-v41-flash-1017-exl3-tp5-1m}}
* {{Status|Contested}} EXL3 speed on CMPs. Miséricorde: EXL3 is very slow on CMP because the sm_80 dequant path is heavily compute-bound, using only 10 to 20% of HBM bandwidth; do not run EXL3 quants on CMPs. Takka: small-batch decode should still be bandwidth-bound; the card has only about 12 TFLOPs of INT32. Morrowmake reached about 150 tok/s on Qwen Flash Next EXL3 5.05 bpw, then said W4A16 is probably the better choice. Miséricorde also says EXL3 is acceptable for DeepSeek V4.1 Flash because only about 30% of its decode is EXL3 work (about 95% for GLM). {{Source|handle=wakeupmbrc1|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1559867344367652865}} {{Source|handle=wakeupmbrc1|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559796160724475996}} {{Source|handle=spectakkular|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1560298253109432392}} {{Source|handle=voidgiraffe|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1560599553210851400}} {{Source|handle=wakeupmbrc1|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1561137015167254579}}
* Why the EXL3-expert DeepSeek V4.1 Flash ports run 2.7 to 3x faster than the PP8 recipes (lab analysis of the repos' docs and Discord numbers, 2026-10-27): the layout, not EXL3. 2.9 bpw experts plus FP8 for the rest fit four 64 GB cards with a 1.2 to 1.4M-token KV pool, so the ports run TP4 + EP4 on x16 with a P2P all-reduce and every card works on every token; the official MXFP4 model (about 286 GiB without Engram) needs eight cards in PP8, where seven of eight idle per token for one user. GNmac's own PP4 column on the same weights (118 / 91 / 63) matches Zanooda's PP8 (117 / 61). The vLLM ports (Morrowmake's <code><nowiki>moe_v2.cu</nowiki></code> and GNmac's coop tile, both from CurtisAccelerate's TC-MoE port) decode trellis tiles straight into FP16 tensor-core operands, but decode stays ALU-bound: about 210 GB/s per card, roughly 15% of HBM, from GNmac's step profile. With the layout held equal EXL3 loses 15 to 20% to native FP4 W4A16 (reala on 8 GPUs: 117.1 against 135 to 139 code decode). Speculative verify is nearly free for a decode-bound kernel (+0.6 to 1.0 ms per extra row against 4 ms for the first), which is why structured and code output beat prose by so much; prefill is where the EXL3 cost shows (2.4 to 3.8k against PP8's 4.5 to 6k). {{Source|handle=darkmaniac7|date=2026-10-27|note=lab notes}}
* tekkenz ran turboderp's Qwen3.8-Flash-Next EXL3 at 5.05 bpw (0.0040 KLD from BF16) on one card: 69 to 82 tok/s decode, about 1,000 tok/s prefill. How it fits one card without RAM offload was asked and not answered. {{Source|handle=tekkenz|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1557128719422853223}}
* Ryko serves GLM-5.3-Flash 4-bit EXL3 on ExLlamaV3 across two 64 GB CMPs, a 40 GB card and an RTX 3080 20 GB (188 GB total) with 768k context at 16-bit KV: about 70 tok/s decode, a 100k-token prefill at 3,500 to 3,600 tok/s, after letting an AI agent optimize ExLlamaV3 for the hardware. {{Source|handle=vektor_prime|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1560023669416402965}}
* Mountains runs the full GLM 5.3 EXL3 3.05 bpw across four 8 GB CMPs plus an RTX PRO 6000 with pipeline parallel at 30 tok/s; it did not work out of the box with PP and mixed architectures. {{Source|handle=mountains1605|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1559063237775990795}} {{Source|handle=mountains1605|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1559339980541796483}}

== llama.cpp ==
Runs, but it is the slow option on these cards; use vLLM or sglang with INT4/INT8 weights instead.
* ikyo's Mac Studio beat a single CMP in most tests on Qwen 27B Q8 with llama.cpp; the community said llama.cpp is very suboptimal on CMPs. {{Source|handle=ikyo|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564314992998613125}} {{Source|handle=lia_oc|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564315280916615251}}
* Tokukarin cannot get past 60 tok/s on Qwen Flash Next at 4.27 bpw on one card even with MTP; he will not go lower because 3.84 bpw degraded multilingual output. {{Source|handle=tokukarin|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564443422314602559}}
* llama.cpp can put mmproj and the speculative draft on a separate device, so a fifth card is still useful while the main model stays on four. {{Source|handle=da6b|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562556812148998207}}
* Comparison point: xanthe_ gets 88 tok/s on Qwen 3.6 across two V100s with llama.cpp built from source at 5-bit. {{Source|handle=xanthefin|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561337005105746011}}
* PixelML measured a single-kernel decode engine at 70.6 tok/s against llama.cpp 53.4 on Qwen3.8-Flash-Next UD-Q3_K_XL on one card; the 26.8 GiB PLE table must sit on local disk (29 tok/s from a network mount). {{Source|handle=c133|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562161732137386127|repo=https://github.com/PixelML/club-170hx}}

== Strata and Project Maya ==
Strata is a consumer local-LLM app with its own engine; it lists no CMP support but people run it. Project Maya forked
it (plus llama.cpp) to tier MoE experts across VRAM, RAM and NVMe.
* pcsv: Strata works well with CMPs, 100+ tok/s with default settings; forks (mw00/project-maya for DeepSeek 4.1 Flash, ro99/Strata for Kimi K3) proved larger models. {{Source|handle=pcsv.|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563917658334695467}}
* acedogblast: more than 60 tok/s on Qwen 3.8 Flash Next on one card with Strata (Unsloth QD-4K_XL, FP16 KV). {{Source|handle=acedogblast|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1556834517103157331}}
* xtj7: Strata on one card with quad-channel DDR4 gives about 90 tok/s decode and 1,600 tok/s prefill at IQ2, without an x16 mod. {{Source|handle=xtj7|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560350518847479850}}
* eXile (one 10 GB-variant card at 40 GB, 14600K, 128 GB DDR4): moving from x4 to x16 mostly improved prefill; his modified Strata build beats stock (110+ against under 100). {{Status|Theory}} Miséricorde expects ECC DDR4 server memory to double Strata speed. {{Source|handle=exile_1ck|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557241785695211612}} {{Source|handle=exile_1ck|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557256690255134751}} {{Source|handle=wakeupmbrc1|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557241997138333698}}
* Project Maya pages: [[GLM 5.3 Flash on 2x 8 GB (Project Maya)]], [[DeepSeek V4.1 Flash on 2x 8 GB (Project Maya)]].

== Speculative decoding ==
* '''DFlash2''' (inco.ai drafters for GLM-5.3-Flash and Qwen3.8-Flash-Next) is the default in the Morrowmake GLM recipe and the ElectroHobo Qwen recipes. The GLM drafter is CC BY-NC-ND 4.0 (non-commercial); the Qwen one is Apache-2.0. Miséricorde confirmed the Qwen drafter helps. {{Source|handle=wakeupmbrc1|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1561924555486920825}}
* '''DSpark''' is DeepSeek V4.1 Flash's own drafter, built into the checkpoint. Acceptance runs about 5.1 tokens per step on code and about 2.9 on reasoning text (reala), which leaves reasoning at 55-75 tok/s on six to eight cards. On the GNmac port the draft count must be 5: 6 or 7 do not start, and 3 or 4 boot but every request fails, so that recipe narrows verification with <code><nowiki>DSV41_DYNK</nowiki></code> instead. On the lab's mixed bench DSpark accepted 2.1 of 5 draft tokens per step (2.6x decode), and a fine-tuned FP8 DSpark refit measured identical to stock (2.14 against 2.13). More from the lab notes: the drafter sits in the checkpoint under <code><nowiki>mtp.0..2</nowiki></code> (three stages, about 7.9 GB, block size 5) and the patched vLLM refuses <code><nowiki>method:"mtp"</nowiki></code> on V4.1. <code><nowiki>num_speculative_tokens</nowiki></code> must be at most 5 or a multiple of 5 (7 is refused; PixelML's k=10 run was slower, 4.01 against 4.40 tokens per step at k=5). Upstream adaptive verification is not supported with pipeline parallel. Acceptance elsewhere: Zanooda PP8 about 5.9 tokens per step on repetitive output and 3.9 on prose; PixelML's TP4 + EP4 EXL3 build 67.9% (4.40 per step), and 25.4 tok/s without a drafter against 99.5 / 48.9 with it. No other trained drafter targets V4.1: the EAGLE3 and DFlash heads are for V4 Flash (hidden 4096, 43 layers; V4.1 is 5120 and 40). Drop-in refits: [https://huggingface.co/SubconsciousDev/deepseek-v4.1-flash-1017-dspark SubconsciousDev/deepseek-v4.1-flash-1017-dspark] (FP8, same tensor names) and [https://huggingface.co/ursuciprian/DeepSeek-V4.1-Flash-1017-DSpark-D1 ursuciprian/DeepSeek-V4.1-Flash-1017-DSpark-D1] (EXL3 overlay, author claims 6.6 to 11.6% on prose on other hardware). n-gram and suffix decoding exist only on the GNmac V1-runner path and replace DSpark, so they should lose on prose. {{Source|handle=reala7096|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562917910165323808}} {{Source|handle=darkmaniac7|date=2026-10-27|note=lab notes}} {{Source|handle=darkmaniac7|date=2026-10-28|note=lab notes}}
* '''MTP''' heads ship with Qwen3.8 and GLM-5.3 checkpoints. On Qwen3.8 27B matstatman recommends MTP with k=3 over DFlash. On Qwen Flash Next DFlash reached only 14% acceptance at the 4th token for Sojun, and Mountains never got speculative decoding working for it on the 170HX (it worked for the 27B). The ElectroHobo recipes now ship a DFlash2 drafter for it. {{Source|handle=sojun80|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1557431093119033375}} {{Source|handle=mountains1605|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1557890449186758737}} {{Source|handle=matstatman|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560828125863084103}}
* {{Status|Theory}} '''EAGLE-4''' (eagle-hq): its Triton kernel tier admits sm_80 and cibernox flagged it as faster than MTP and DSpark2, but nothing has been measured on Ampere or a CMP, it needs patched engine wheels, and it has drafts only for Qwen3.8-27B and Nemotron. Source-available license, not open source. {{Source|handle=cibernox|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562247115562942555|repo=https://github.com/eagle-hq/EAGLE-4}}

== Mixing CMP and newer GPUs in one job ==
The lab runs Morrowmake's engine across CMP 170HX (sm_80) and RTX PRO 6000 Blackwell (sm_120) cards in one vLLM job with
pipeline parallel, CMPs first and Blackwells as the last stage. It needed three small Python patches (resolve the
device capability per rank instead of from device 0, pick the MLA backend on sm_120 without the FP8 KV path, build the
host-staged all-reduce only on sm_80 TP groups) and four launch settings, each found by a failed boot:
<code><nowiki>--additional-config {"kda_prefill_backend":"triton"}</nowiki></code>, <code><nowiki>CUTE_DSL_ARCH=sm_120a</nowiki></code>,
<code><nowiki>--kernel-config {"enable_flashinfer_autotune":false}</nowiki></code> (autotune on one stage deadlocked the others), and at least
one MLA layer on every stage. Results for GLM 5.3 Flash are on [[GLM 5.3 Flash on 4x 8 GB#With other GPUs in the same job]].
The full GLM 5.3 does not run this way on the Morrowmake fork: its DSA indexer path needs DeepGEMM kernels that exist
only for Hopper and Blackwell, and its KV writers use an FP8 type Triton refuses below sm_89; wtdcode/vllm-backport
already has the sm_80 pieces but no sm_120 build. {{Status|Theory}} the lab estimates a port at 2 to 4 days.
{{Source|handle=darkmaniac7|date=2026-10-19|note=lab notes}}

== Load times ==
Loading 350 to 380 GB models takes under 5 minutes from NVMe (impactic), about 20 minutes from SATA (matstatman) and
about 8 minutes at Gen2 x4 (Mountains). First starts also compile kernels: 5 to 22 minutes depending on the recipe.
{{Source|handle=darkmaniac7|date=2026-10-20|note=lab notes}} 
{{Source|handle=mountains1605|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1564747358661509230}}

== Engine-level known issues ==
* '''Kernel launch overhead on the n-gram models.''' Qwen3.8 Flash Next launches about 2,000 small kernels per step: decode compute is only 1.5 to 1.8 ms of a 10 to 11 ms round, so the model is cheap at high concurrency on big GPUs but ineffective at low concurrency on CMPs; hand-built megakernels gave 20 to 25%. {{Source|handle=wakeupmbrc1|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1559631250766168075}} {{Source|handle=wakeupmbrc1|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560992853927403583}}
* '''Prefill stalls decode''' in vLLM on PP setups: per-stream speed drops with concurrency because decode stops during prefill; fair prefill slicing (Morrowmake, ElectroHobo) mitigates it. {{Source|handle=ob88594|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1557464371838451723}}
* {{Status|Contested}} '''Custom all-reduce and P2P on Gen2.''' Results differ by host and model: on the lab's EPYC box custom all-reduce cost GLM-5.3-Flash TP4 about 40% decode but helped Qwen Flash Next TP2 by 17 to 25%; PixelML saw P2P hurt GLM TP4 on PLX + Broadwell; ElectroHobo saw P2P off cost MiMo TP4 40% on PLX + Broadwell. A/B it per recipe. A hang at init can be stale build locks in a copied compile cache. {{Source|handle=c133|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562161732137386127|repo=https://github.com/PixelML/club-170hx}} {{Source|handle=darkmaniac7|date=2026-10-28|note=lab notes}}
* '''Pipeline hand-off bug at TP>1 with PP''' (GLM-5.x DSA models, vLLM PR #60477): a non-last pipeline stage sends an un-reduced partial sum, corrupting the first layer of the next stage at TP2 x PP4. Symptoms in the lab's runs: about 3 points lower teacher-forced agreement, 32k-token degeneration loops and reasoning that eats the budget on long prompts. The one-line worker fix costs no speed. A second, separate bug (vLLM issue #63170, draft PR #59961): GLM-5.x shared-indexer layers at a stage start read stale top-k indices, so choose a PP split that starts every stage on a full indexer layer. {{Source|handle=darkmaniac7|date=2026-10-28|note=lab notes}}
* '''Agent clients and the reasoning field.''' On Schaka's 8-card host a vLLM fork emitted reasoning text only under a field named <code><nowiki>reasoning</nowiki></code>; most clients (opencode included) expect <code><nowiki>reasoning_content</nowiki></code>, so without a patch that emits both, the whole think block lands in the assistant content, fills the history and drives long agent sessions into a repetition loop. Set <code><nowiki>reasoning_effort</nowiki></code> on every request (max, not high: low and high rendered an empty thinking prefix that accumulates), and give each context size its own served model name so clients read the right context length. LMCache does not unify the KV spec on mixed attention + Mamba/GDN models. Journal: [https://github.com/Schaka/170hx-journey Schaka/170hx-journey]. {{Source|handle=darkmaniac7|date=2026-09-12|note=lab notes}}
* '''TP size must divide the attention head count.''' DeepSeek V4.1: TP 1, 2, 4 or 8 only; TP6 works only with wgkbfcp's virtual-head padding. {{Source|handle=greencandle9753|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562580021153894501}} greencandle was confirming cibernox, who recalled TP=3 working on models whose head-related count divides by 3. A later post claimed vLLM needs a power-of-two GPU count "for all the llm models"; that conflicts with cibernox's TP=3 recollection and with greencandle's divisor rule. {{Source|handle=cibernox|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562550500224667649}} {{Source|handle=cibernox|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562550864952950919}} {{Source|handle=kill3again|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562847068383354981}}
* '''One bad card can look like an engine bug.''' A DeepSeek V4.1 Flash user once had garbage top-k indices that followed one physical card when cards were swapped; see also the zero-row card on [[GLM 5.3 on 8x 8 GB (vllm-170hx-glm5)]] and [[Troubleshooting]]. {{Source|handle=darkmaniac7|date=2026-10-27|note=lab notes}}
* '''No tuned GEMM for the harvested die''': training on one CMP ran almost 4x slower than a 5090 with the same nominal BF16 TFLOPs. {{Source|handle=programmerboi|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560682620012990505}}

== Engines that do not run on sm_80 (yet) ==
* TokenSpeed (LightSeek Foundation): day-0 GLM-5.3-Flash and Qwen3.8-Flash-Next support, but the README documents no Ampere path. Its sm_80 pull request was closed as won't-fix. {{Source|handle=c133|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1556808015003390052|repo=https://github.com/lightseekorg/tokenspeed}} {{Source|handle=darkmaniac7|date=2026-10-20|note=lab notes}}
* 1Cat-vLLM: a V100 (sm_70) fork; a comparison point and technique source (FP8 KV emulation, NVFP4 on hardware without FP8 tensor cores), not a CMP engine. {{Source|handle=xeax|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563519176327299192|repo=https://github.com/1CatAI/1Cat-vLLM}}
* PixelML's negative results: NVFP4 GLM checkpoints need SM12x FlashInfer; EXL3 / TR3 4 bpw ships SM121-only kernels; the Ninfer sm_80 fork was 3.6x slower than vLLM with DFlash2. {{Source|handle=c133|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562161732137386127|repo=https://github.com/PixelML/club-170hx}}

== Related ==
[[Recipes]] · [[Quantization on the 170HX]] · [[Benchmarks]] · [[Unlocks]] · [[Driver unlock]] · [[Troubleshooting]] · [[Tools]]

{{ImportFooter}}
[[Category:Engines]]

DeepSeek V4.1 Flash on 8x 8 GB (Zanooda PP8)

2026-10-31T21:34:29Z

ImportBot: Import: Zanooda/deepseek-v4.1-flash-cmp170hx (repo, posted by Gnasherrr); Justinjja's comment; the lab run on 8 cards, including an NVMe drop; sources: @Zanooda, @gnasherrr, @justinjja, @darkmaniac7; GitHub Zanooda/deepseek-v4.1-flash-cmp170hx, vllm-project/vllm.git

{{Recipe
|model=DeepSeek-V4.1-Flash-1017
|quant=Official checkpoint as downloaded: MXFP4 routed experts as Marlin W4A16, MXFP8 dense as Marlin W8A16; KV fp8
|engine=vLLM PR #56201 head (79a7108d) plus a 20-patch sm_80 series; image zanooda/vllm-sm80-ds41f:v41-sm80
|engine_version=recipe 31318fd; patches 0001-0020
|cards=8 GB
|card_count=8
|topology=PP8, partition 5,5,5,5,5,5,5,5
|context=1,048,576
|decode_tps=117
|prefill_tps=6066
|vram_per_card=64 GB; weights 35.9 GB per rank (ranks 1-6), 37.6 GB rank 0, 46.3 GB rank 7
|power_cap=180 W (one card unstable at 250 W)
|unlock_build=cmpunlocker with the BAR1 P2P patches (64 GiB BAR1 per card)
|flags=--pipeline-parallel-size 8 --max-model-len 1048576 --gpu-memory-utilization 0.95 --block-size 128 --kv-cache-dtype fp8 --max-num-batched-tokens 4096 --max-num-seqs 32; DSpark 5; VLLM_DSV41_SPREAD_DECODE=2; --engram-config storage cpu
|status=Reported
|tested_by=Zanooda
|tested_on=2026-10-19
|source=https://github.com/Zanooda/deepseek-v4.1-flash-cmp170hx
}}
A complete serving recipe for DeepSeek-V4.1-Flash-1017 on eight 64 GB cards with vLLM pipeline parallel 8: a 20-patch
series on the open vLLM PR #56201 plus haosdent's sm_80 layer, a prebuilt sm_80-only Docker image, launch scripts and
benchmark harnesses. It serves the official checkpoint without conversion or EXL3, gives a 6.2M-token KV pool and 1M
context, and has the best prefill of the DeepSeek recipes. It builds on allover326/deepseek-v4-cmp170hx and is
independent of the Morrowmake recipes. Justinjja found it a bit faster than the alternatives at the time.
{{Source|handle=gnasherrr|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560998024136753172|repo=https://github.com/Zanooda/deepseek-v4.1-flash-cmp170hx}} 
{{Source|handle=gnasherrr|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560998024136753172}} 
{{Source|handle=justinjja|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561016129550286868}}

== Prerequisites ==
* Eight CMP 170HX at 64 GB ([[Driver unlock]], [[8 GB card]]). The author's were six at PCIe Gen2 x4 and two at x16, with no measured difference.
* The checkpoint [https://huggingface.co/deepseek-ai/DeepSeek-V4.1-Flash-1017 deepseek-ai/DeepSeek-V4.1-Flash-1017] on local NVMe: 510 GB, 48 shards; shards 47 and 48 are the two 101 GB Engram tables.
* About 240 GB of host RAM for the default Engram <code><nowiki>cpu</nowiki></code> mode (both tables pinned, 203 GB). With less RAM use <code><nowiki>storage=disk</nowiki></code> (patch 0010's C gather, runs on a 32 GB host) or the page-cache warmer.
* Author's host: EPYC 7402P, 278 GB DDR4.
{{Source|handle=gnasherrr|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560998024136753172|repo=https://github.com/Zanooda/deepseek-v4.1-flash-cmp170hx}}

== Steps ==
<syntaxhighlight lang="bash">
git clone https://github.com/Zanooda/deepseek-v4.1-flash-cmp170hx ~/deepseek-v4-cmp170hx
# 1. the patched vLLM tree: PR #56201 head + all 20 patches
git clone https://github.com/vllm-project/vllm.git ~/vllm-v41 && cd ~/vllm-v41
git fetch origin pull/56201/head && git checkout -b v41-sm80 79a7108d9a
git am ~/deepseek-v4-cmp170hx/patches/v41/*.patch
# 2. the image: sm_80-only SASS, built from the PR head + patches 0001-0008
docker pull zanooda/vllm-sm80-ds41f:v41-sm80
# 3. checkpoint deepseek-ai/DeepSeek-V4.1-Flash-1017 (510 GB, 48 shards) under /models, then
DSV41_VLLM_SRC=$HOME/vllm-v41/vllm ~/deepseek-v4-cmp170hx/launch/run-v41-pp8.sh
</syntaxhighlight>
The image holds patches 0001 to 0008 only; 0009 to 0020 are Python-only and are bind-mounted through
<code><nowiki>DSV41_VLLM_SRC</nowiki></code>. Without 0009 the engine does not start. Startup takes about 10 minutes. API on port 8099,
served name <code><nowiki>dsv41</nowiki></code>, up to 8 images per request.
{{Source|handle=gnasherrr|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560998024136753172|repo=https://github.com/Zanooda/deepseek-v4.1-flash-cmp170hx}}

What the patches do (from the README): 0009 lets PP8 start (it replicates the KV-source and indexer caches across
ranks); 0010 is a C gather for the Engram tables, 3.4x faster prefill than the Python preadv path; 0013 adds host-RAM
Engram with exact-size pinning; 0019 spreads decode bursts over the pipeline; 0020 syncs the prompt encoder to the 1017
checkpoint, without which the engine emits an empty think block after every tool result and drifts into ad-hoc XML
tool calls. With Engram read from NVMe, prefill at 105k is 4,455-4,930 tok/s (6,066 from RAM).
{{Source|handle=darkmaniac7|date=2026-10-19|note=lab notes}}

Field notes from the lab's run:
* The launcher bind-mounts the changed Python files by diffing your checkout against <code><nowiki>DSV41_IMG_COMMIT</nowiki></code>. Its default commit exists only in the author's repo; on another checkout the diff fails silently, nothing is mounted and the engine does not start. Set <code><nowiki>DSV41_IMG_COMMIT</nowiki></code> to the commit your own patched checkout was built from, and check that the launch prints "bind-mounting 24 changed python file(s)"; if it says 0, stop.
* Pin the image by digest: <code><nowiki>zanooda/vllm-sm80-ds41f@sha256:283fc7b05791b41b804851b395d088cda91dcdc23e72d190563af772079a6b6e</nowiki></code> (the tag is mutable).
* Engram <code><nowiki>cpu</nowiki></code> mode ran out of memory on a 125 GB host; use <code><nowiki>disk</nowiki></code>.
* The API listens on 0.0.0.0 with no key; add <code><nowiki>--api-key</nowiki></code> through <code><nowiki>DSV41_EXTRA_ARGS</nowiki></code> if anything beyond your LAN can reach it.
{{Source|handle=darkmaniac7|date=2026-10-27|note=lab notes}}

== Measured numbers ==
Author's numbers (measured 2026-09-10/11 on the pre-1017 weights; config and index are byte-identical for 1017):
* Decode: 117 tok/s single stream at 128k context, 96 at 512k (Engram pinned in RAM). Step cadence flat at 40 to 56 ms from 4k to 115k prompt tokens; 3.9 (prose) to 5.9 (repetitive text) tokens per step.
* Multi-stream with patch 0019: 8 streams 560 tok/s aggregate warm (stock scheduler 274), 16 streams 806 to 813.
* Prefill (Engram in RAM, patch 0013): 26,208 tokens in 5.8 s (4,486 tok/s), 104,881 in 17.3 s (6,066), 419,430 in 78.7 s (5,328); a 1,007,820-token prompt in 468 s; eight concurrent 105k prompts about 6,900 tok/s aggregate.
* KV pool 6,171,394 tokens at 0.95 (5.9 concurrent 1M requests).
* Correctness: needle-in-haystack 19/19 from 4k to 1M (820k real tokens), 4 concurrent needles with no cross-request bleed, tool calls verified, vision works.
{{Source|handle=gnasherrr|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560998024136753172|repo=https://github.com/Zanooda/deepseek-v4.1-flash-cmp170hx}}

* The lab, 8 cards at Gen2 x16 with P2P, 1,024-token answers: at 180 W one user code 64 / structured 46 / prose 32 tok/s, 8 users 546 / 316 / 285 aggregate, prefill 5,478 tok/s on a 17k prompt; at 150 W 65 / 50 / 34, 533 / 296 / 284, prefill 5,276, up in 8 minutes, 1M context with a 5.56M-token KV pool, image understanding correct, 0 Xids. Engram in RAM was exactly as fast as from NVMe. Single-stream decode is well below the author's; aggregate and prefill match. {{Source|handle=darkmaniac7|date=2026-10-27|note=lab notes}}

== Known issues ==
* {{Status|Warning}} '''NVMe drop under the Engram disk stream.''' On the lab box, about a minute after the first PP8 benchmark with the Engram tables read from disk (189 GiB by 32 threads, because 125 GB of RAM was too little for <code><nowiki>cpu</nowiki></code> mode), the 2 TB NVMe holding the OS and models fell off and the box would not boot. The drive sat on a PCIe-to-M.2 sled with no heatsink or airflow. A reseat brought it back with no SMART errors, but the system journal was lost with the filesystem, so overheating is the best explanation, not proof. With a 120 mm fan on the sled the drive later held 31 to 36 C under the same loads (it had reached 71 to 81 C before). Cool the NVMe, cap its read rate, or keep the tables in RAM. See [[Cooling and power]] and [[Troubleshooting]]. {{Source|handle=darkmaniac7|date=2026-10-27|note=lab notes}}
* One of the author's cards fell off the bus (Xid 79) three times under sustained load at the stock 250 W limit and was stable at <code><nowiki>nvidia-smi -pl 180</nowiki></code>; <code><nowiki>nvidia-smi</nowiki></code> reports up to 333 W against a 250 W limit during prefill on every card.
* PWRBRK# trap: some boards (ASUS Pro WS WRX80E-SAGE) assert PWRBRK# on edge pin B30 and pin the card at about 88 W / 1,140 MHz. Check with <code><nowiki>nvidia-smi -q | grep -A1 "HW Power Brake Slowdown"</nowiki></code> ("Active" on an idle card means braked); fix with Kapton tape over B30 or a riser that does not route B30.
* P2P with the BAR1 patches gave peer copies of 1.55 GB/s and routed every pipeline hop GPU to GPU, with no measurable speed change (hops are bound by the Gen2 x4 link). Tensor parallel measured 6.6x slower on prefill; <code><nowiki>--enforce-eager</nowiki></code> gives 8 to 10 tok/s.
* <code><nowiki>--block-size 256</nowiki></code> fails KV allocation; a last rank with fewer than 4 layers cannot start (the drafter needs layers 36 to 38).
* Keep <code><nowiki>VLLM_DSV41_SPREAD_DECODE=2</nowiki></code>: the stock scheduler packs a burst into one micro-batch (274 against 560 tok/s at 8 streams).
* <code><nowiki>reasoning_effort</nowiki></code> is a 1 to 100 budget; low, high, xhigh, max map to 25, 50, 75, 100 (upstream maps high to 75); none disables thinking; minimal and medium return HTTP 400.
* The base vLLM PR #56201 is open and may be force-pushed.
{{Source|handle=gnasherrr|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560998024136753172|repo=https://github.com/Zanooda/deepseek-v4.1-flash-cmp170hx}}

== Related ==
* Same card count, other engine: [[DeepSeek V4.1 Flash on 8x 8 GB (Deepinfer-SM80 TP4 x PP2)]].
* Four-card recipes: [[DeepSeek V4.1 Flash on 4x 8 GB (Morrowmake)]], [[DeepSeek V4.1 Flash on 4x 8 GB (GNmac)]].
* [[Engines]], [[Benchmarks]], [[Tools]].

== Sources ==
* Repo: [https://github.com/Zanooda/deepseek-v4.1-flash-cmp170hx Zanooda/deepseek-v4.1-flash-cmp170hx] (Apache-2.0), last commit 2026-10-19. Credit also to allover326/deepseek-v4-cmp170hx and haosdent/vllm dsv4-flash-a100. Posted on Discord by Gnasherrr.
* Lab notes, 2026-10-27.

{{ImportFooter}}
[[Category:8 GB]]

DeepSeek V4.1 Flash on 4x 8 GB (alanoo fidelity build)

2026-10-31T21:34:29Z

ImportBot: Import: alanoo81/deepseek-v41-flash-4x-cmp170hx (repo, patches on GNmac-lab 1.2.0) and alanoo's Discord posts; Miséricorde's comment; sources: @alanoo, @wakeupmbrc1; GitHub GNmac-lab/deepseek-v41-flash-1017-cmp170hx, alanoo81/deepseek-v41-flash-4x-cmp170hx

{{Recipe
|model=DeepSeek-V4.1-Flash-1017
|quant=Hybrid: all 40 expert layers at 3 bits (LibertAI 2.9 bpw pack with layers 18-22 grafted from the 3.5 bpw pack), official FP8 dense tensors
|engine=GNmac-lab recipe image 1.2.0 (vLLM with sm_80 patches) plus three patches
|engine_version=GNmac-lab at 2ad5741ab1; image ds41-cmp170hx:1.2.0-fidelity
|cards=8 GB
|card_count=4
|topology=TP4, P2P on
|context=262,144
|decode_tps=105.0
|prefill_tps=2514
|vram_per_card=64 GiB (64,911 MiB usable), GPU_MEMORY_UTILIZATION 0.98
|power_cap=200 W
|driver=NVIDIA open 610.43.02 from a cmpunlocker fork with a P2P patch
|unlock_build=cmpunlocker fork with P2P (without Morrowmake's TRAP31 patch)
|flags=LAYOUT=tp4, MAX_MODEL_LEN=262144, MAX_NUM_SEQS=8, GPU_MEMORY_UTILIZATION=0.98, P2P=1, SPEC_TOKENS=0 (DSpark off), ENGRAM_STORAGE=ssd from a tmpfs
|status=Reported
|tested_by=alanoo
|tested_on=2026-10-27
|source=https://github.com/alanoo81/deepseek-v41-flash-4x-cmp170hx
}}
A fidelity-first configuration of [[DeepSeek V4.1 Flash on 4x 8 GB (GNmac)]], aimed at agentic and concurrent work. It
grafts 3-bit experts from LibertAI's 3.5 bpw pack into layers 18-22 of the 2.9 bpw pack (so every expert layer is
3-bit), turns the DSpark drafter off to free KV room, loads the Engram tables from a tmpfs, and runs at 0.98 memory
utilization for a 2.7M-token KV pool. Single-user decode is lower than the speed-tuned builds; 8-user throughput stays
around 450 to 550 tok/s. The author calls it a first rough version. Infobox decode is one user on code without DSpark.
{{Source|handle=alanoo|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1564537669646680087}} 
{{Source|handle=alanoo|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1564681525365186711|repo=https://github.com/alanoo81/deepseek-v41-flash-4x-cmp170hx}}

== Prerequisites ==
* Everything [[DeepSeek V4.1 Flash on 4x 8 GB (GNmac)]] needs: four cards at 64 GiB and 74 SMs on PCIe Gen2 x16 with working P2P (the author's <code><nowiki>nvidia-smi topo -p2p</nowiki></code> reports OK and NCCL passes on all four).
* About 428 GiB of disk for the pinned weights (against 671.5 GiB for the Morrowmake recipe).
* About 190 GiB of tmpfs for the Engram tables plus engine memory (the author's container limit was 460 GiB; 240 GiB is an inferred floor, not measured). Author's host: ASRock Rack ROMED8-2T, EPYC 7F52, 512 GB DDR4-3200 in 8 channels, 170tune +200 MHz at 1,500 MHz, Docker inside LXC with GPUs passed by CDI.
* <code><nowiki>bc</nowiki></code>; <code><nowiki>serve.sh</nowiki></code> refuses to start if the GPUs already hold more than 2,000 MiB.
{{Source|handle=alanoo|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1564681525365186711|repo=https://github.com/alanoo81/deepseek-v41-flash-4x-cmp170hx}}

== Steps ==
The repo holds only patches against the GNmac recipe, pinned download and graft tools, test scripts and raw data. In
outline:
# Clone [https://github.com/GNmac-lab/deepseek-v41-flash-1017-cmp170hx GNmac-lab/deepseek-v41-flash-1017-cmp170hx] at <code><nowiki>2ad5741ab1</nowiki></code> (release 1.2.0) and apply <code><nowiki>recipe/serve.sh.patch</nowiki></code>, <code><nowiki>recipe/start.sh.patch</nowiki></code> and <code><nowiki>tools/fetch_official_nonexpert.py.patch</nowiki></code> (CDI GPUs, optional drafter, Engram dir mount, graft-aware expert-file regex, pinned official revision).
# Download with pinned revisions: <code><nowiki>recipe/tools/download-pinned.sh</nowiki></code> (the 2.9 bpw pack, shards 20 to 24 of the 3.5 bpw pack, the official non-expert tensors and Engram shards). All 55 LFS files are checked against Hugging Face SHA-256.
# Build the grafted hybrid: <code><nowiki>recipe/tools/make_hybrid_graft.py</nowiki></code> (profile <code><nowiki>k3</nowiki></code>; it checks K in the headers).
# Copy the Engram tables into a tmpfs before start: <code><nowiki>recipe/engram-ram.sh</nowiki></code>.
# Start with <code><nowiki>recipe/env.example</nowiki></code> values: <code><nowiki>LAYOUT=tp4</nowiki></code>, <code><nowiki>MAX_MODEL_LEN=262144</nowiki></code>, <code><nowiki>MAX_NUM_SEQS=8</nowiki></code>, <code><nowiki>GPU_MEMORY_UTILIZATION=0.98</nowiki></code>, <code><nowiki>P2P=1</nowiki></code>, <code><nowiki>PORT=8011</nowiki></code>, <code><nowiki>IMAGE=ds41-cmp170hx:1.2.0-fidelity</nowiki></code> (17.8 GB, about 20 minutes to build, first start about 10 minutes).
# Expect the log line <code><nowiki>Built engram token map (129280 -> 99092 ids) for layers (1, 14)</nowiki></code>.
Pinned weights: [https://huggingface.co/LibertAIDAI/DeepSeek-V4.1-Flash-1017-EXL3-2.9bpw LibertAIDAI 2.9 bpw] at
<code><nowiki>0be63c33</nowiki></code> (196.3 GiB), [https://huggingface.co/LibertAIDAI/DeepSeek-V4.1-Flash-1017-EXL3-3.5bpw LibertAIDAI 3.5 bpw]
at <code><nowiki>04a492fc</nowiki></code> shards 00020 to 00024 (about 24 GiB), official
[https://huggingface.co/deepseek-ai/DeepSeek-V4.1-Flash-1017 deepseek-ai/DeepSeek-V4.1-Flash-1017] at <code><nowiki>1bae0e10</nowiki></code>
(non-expert tensors by HTTP range, about 17.5 GiB, and Engram shards 00047-00048, about 189 GiB), Curtis White's
<code><nowiki>quantization_config.json</nowiki></code> at <code><nowiki>b8b9e99</nowiki></code>.
{{Source|handle=alanoo|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1564681525365186711|repo=https://github.com/alanoo81/deepseek-v41-flash-4x-cmp170hx}}

== Measured numbers ==
At 200 W, MiaAI-Lab protocol (temperature 0, thinking off, 400-token cap), tok/s structured / code / prose:
{| class="wikitable"
! !! 1 user !! 8 users (aggregate) !! Cold prefill
|-
| DSpark off (default) || 105.4 / 105.0 / 104.8 || 559.7 / 482.4 / 449.2 || 2,514 (median of 9 runs, 24k to 38k-token prompts)
|-
| DSpark 5 || 369.8 / 267.3 / 200.1 || structured +52%, code -7%, prose -2.5% ||
|}
DSpark acceptance: 99.4% structured, about 70% code, 43 to 53% prose.

KV pool at 262,144 context on the all-3-bit build: 1,817,233 tokens at 0.95, 2,417,392 at 0.97, 2,717,420 at 0.98
(10.37 full sequences). The original 2.9 pack gives 3,347,338 at 0.97. DSpark costs 2.78 GiB per card (pool falls to
1,113,781 at 0.97). MTP is not available for V4.1 in this vLLM, only DSpark.
{{Source|handle=alanoo|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1564681525365186711|repo=https://github.com/alanoo81/deepseek-v41-flash-4x-cmp170hx}}

=== Quality and fidelity ===
* Graft effect by paired NLL on 64 frozen 1,024-token windows per set, bootstrap 95% CI: perplexity -1.80% overall [-2.00, -1.60], -4.45% on French [-4.97, -3.93] (64 of 64 windows better), -0.70% English, -0.18% code; it costs about 1.98 GiB per card.
* Moving layers 0, 1, 3 and 6 to 4 bits gave +0.08% [-0.01, +0.18] for 1.58 GiB per card and was dropped. The full 3.5 bpw pack needs about 9.8 GiB more per card and does not fit. Miséricorde: no change from 4-bit layers is expected if the original MXFP4 parts are kept; those help decode speed more than quality. {{Source|handle=wakeupmbrc1|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1564693828072378409}}
* Copy test of 40 random identifiers per list: 300/300 exact over 100 lists x 3 passes (cold, prefix-cached, second turn). 5 tasks x 5 solo repeats byte-identical. Prompt logprobs bit-identical across restarts and between 0.97 and 0.98. Two waves of 8 concurrent unique 100k-token prompts completed 16/16.
* A comparison against Morrowmake's recipe (from reading it, not running it) is in <code><nowiki>docs/comparison-morrowmake.md</nowiki></code>: much better perplexity in French, roughly equivalent in English. A 5-agent, 2-hour real-world run succeeded.
{{Source|handle=alanoo|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1564681525365186711|repo=https://github.com/alanoo81/deepseek-v41-flash-4x-cmp170hx}} 
{{Source|handle=alanoo|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1564695733389631599}}

== Known issues ==
* '''Engram trap.''' Leaving <code><nowiki>ENGRAM_STORAGE</nowiki></code> empty ("host" mode) reserves 2 x 23.6 GiB pinned per rank but never fills it: the hybrid index lacks <code><nowiki>engram.embed.*</nowiki></code> and vLLM skips its missing-weights check when a quantization method is set. Symptoms: 15/20 exact copies, dropped underscores in identifiers, output changing between runs at temperature 0, while decode speed and the smoke test look normal. The log line "offloaded to pinned" means host mode. Fix: <code><nowiki>ENGRAM_STORAGE=ssd</nowiki></code> reading from a tmpfs prepared by <code><nowiki>recipe/engram-ram.sh</nowiki></code>.
* Margin at 0.98: 63,580 MiB peak per card under the 8 x 100k stress (about 1.3 GiB left); <code><nowiki>prompt_logprobs</nowiki></code> on 1,024-token windows peaked at 64,676 MiB (0.23 GiB left), so use 0.97 or windows of 512 tokens or fewer for NLL work.
* Engine numerics: GNmac's <code><nowiki>--kv-cache-dtype fp8_ds_mla</nowiki></code> writes the DeepSeek-V4 record (448 FP8 dims, one scale per 64) because V4.1's <code><nowiki>nvfp4_ds_mla</nowiki></code> format needs SM100; Morrowmake's BF16 KV reproduces the reference's FP8/FP4 rounding bit for bit.
* The engine image contains AGPL-3.0-only vllm-exl3 code (section 13 applies if served over a network). Single machine, single set of measurements, at 200 W (not directly comparable with 180 W numbers). Test script messages are in French.
{{Source|handle=alanoo|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1564681525365186711|repo=https://github.com/alanoo81/deepseek-v41-flash-4x-cmp170hx}}
* This build runs on the GNmac engine, where the lab found long-context copy errors on 75k to 92k-token turns (see [[DeepSeek V4.1 Flash on 4x 8 GB (GNmac)]]). This build's own copy test (40 identifiers, shorter prompts) passed 300/300; it has not been run on the lab's test.

== Related ==
* [[DeepSeek V4.1 Flash on 4x 8 GB (GNmac)]] (base), [[DeepSeek V4.1 Flash on 4x 8 GB (Morrowmake)]], [[Quantization on the 170HX]], [[Benchmarks]].

== Sources ==
* Repo: [https://github.com/alanoo81/deepseek-v41-flash-4x-cmp170hx alanoo81/deepseek-v41-flash-4x-cmp170hx] (MIT), last commit 2026-10-27. Research was run by an AI coding agent with human sign-off (<code><nowiki>docs/agentic-methodology.md</nowiki></code>).
* Discord: alanoo's posts in clanker-talk, 2026-10-27.

{{ImportFooter}}
[[Category:8 GB]]

DeepSeek V4.1 Flash on 4x 8 GB (Morrowmake)

2026-10-31T21:34:28Z

ImportBot: Import: Morrowmake/dsv41-flash-cmp170hx-recipe 1.0.0 (repo, posted by _L_ and Mountains); Mountains' two-day report; CurtisAccelerate's same-board comparison; the lab run; sources: @voidgiraffe, @lia_oc, @jjb01957, @anon33anon, @darkmaniac7, @mountains1605, @alanoo; GitHub CurtisAccelerate/DeepSeekv41-Flash-1017-EXL3-CMP170HX, Morrowmake/dsv41-flash-cmp170hx-recipe, Morrowmake/dsv41-flash-cmp170hx-recipe.git

{{Recipe
|model=DeepSeek-V4.1-Flash-1017
|quant=Hybrid: routed experts EXL3 2.9 bpw (LibertAIDAI), everything else official FP8/BF16; KV BF16
|engine=Morrowmake/vllm-cmp170hx (vLLM fork, container image)
|engine_version=recipe 1.0.0, engine a0c57b5237
|cards=8 GB
|card_count=4
|topology=TP4 with expert parallel (96 whole experts per card)
|context=262,144
|decode_tps=287
|prefill_tps=3818
|vram_per_card=64 GiB exposed, --gpu-memory-utilization 0.95
|power_cap=180 W
|driver=NVIDIA 580 or newer; P2P needs the Morrowmake/cmpunlocker build
|unlock_build=cmpunlocker (64 GiB, 74 SMs); Morrowmake/cmpunlocker for P2P
|flags=P2P=auto, VLLM_ENGRAM_PLACEMENT=auto (ram or ssd), MAX_SEQS 8, MAX_BATCHED 2048, DSpark drafter up to 7 tokens
|status=Reported
|tested_by=voidgiraffe
|tested_on=2026-10-24
|source=https://github.com/Morrowmake/dsv41-flash-cmp170hx-recipe
}}
DeepSeek-V4.1-Flash-1017 on four 64 GB cards with tool calls, reasoning, images and the checkpoint's own DSpark
drafter. The served checkpoint is a hybrid built locally from links: routed experts from LibertAI's EXL3 2.9 bpw export,
every other weight in DeepSeek's own FP8/BF16, and the two Engram lookup tables (about 189 GiB) in host RAM, or read
from SSD on smaller hosts. Same engine family and tooling as [[GLM 5.3 Flash on 4x 8 GB]]. Infobox numbers are the
author's "up to" figures for one user on code and cold prefill on a 2,048-token prompt. jjb: heavy lifting for the
4x 8 GB owners.
{{Source|handle=lia_oc|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563528168688586764|repo=https://github.com/Morrowmake/dsv41-flash-cmp170hx-recipe}} 
{{Source|handle=lia_oc|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563528168688586764}} 
{{Source|handle=jjb01957|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563675495542038650}}

== Prerequisites ==
* Four CMP 170HX that each expose 64 GiB (preflight stops under 60 GiB, <code><nowiki>MIN_GPU_MIB 61440</nowiki></code>). See [[Driver unlock]] and [[8 GB card]].
* PCIe Gen2 x16 links. The single TP4 layout runs on x4 but is bus-bound; <code><nowiki>./start.sh</nowiki></code> warns below x16. See [[Unlocks]].
* NVIDIA driver 580 or newer; Docker with the NVIDIA Container Toolkit (<code><nowiki>docker run --rm --gpus all nvidia/cuda:13.3.1-base-ubuntu24.04 nvidia-smi</nowiki></code> lists four cards).
* Host RAM: about 240 GiB for the published numbers (Engram tables in RAM; the server takes 202 to 204 GiB). Less RAM works with the tables on SSD; put <code><nowiki>MODELS_DIR</nowiki></code> on an NVMe with its own DRAM.
* Disk: about 680 GiB (730 GB) in all (<code><nowiki>NEED_DISK_GB 680</nowiki></code>).
* <code><nowiki>git</nowiki></code>, <code><nowiki>curl</nowiki></code>, <code><nowiki>flock</nowiki></code>, <code><nowiki>setsid</nowiki></code>, <code><nowiki>python3</nowiki></code>, <code><nowiki>jq</nowiki></code>.
* Optional but needed for full speed: the P2P driver build (mainline cmpunlocker + maintainer P2P + TRAP31 Booter PLM patch, <code><nowiki>ForceP2P=0x11</nowiki></code>).
{{Source|handle=lia_oc|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563528168688586764|repo=https://github.com/Morrowmake/dsv41-flash-cmp170hx-recipe}}

== Steps ==
<syntaxhighlight lang="bash">
git clone https://github.com/Morrowmake/dsv41-flash-cmp170hx-recipe.git
cd dsv41-flash-cmp170hx-recipe
./start.sh # install, download, build the hybrid, launch, wait for /health, boot check
./start.sh smoke # one chat request and one tool call
</syntaxhighlight>
Test request (model id <code><nowiki>dsv41-flash</nowiki></code>):
<syntaxhighlight lang="bash">
curl http://127.0.0.1:8000/v1/chat/completions -H 'Content-Type: application/json' \
-d '{"model": "dsv41-flash", "messages": [{"role": "user", "content": "Write a haiku about PCIe."}], "max_tokens": 4096}'
</syntaxhighlight>
<code><nowiki>docker compose up</nowiki></code> is the alternative. The first start compiles kernels into <code><nowiki>./cache</nowiki></code> and loads the
Engram tables, so it is slow (<code><nowiki>READY_TIMEOUT</nowiki></code> 3600 s). Other subcommands: <code><nowiki>status</nowiki></code>, <code><nowiki>logs</nowiki></code>,
<code><nowiki>stop</nowiki></code>, <code><nowiki>restart</nowiki></code>, <code><nowiki>update</nowiki></code>, <code><nowiki>DRY=1</nowiki></code>.
{{Source|handle=lia_oc|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563528168688586764|repo=https://github.com/Morrowmake/dsv41-flash-cmp170hx-recipe}}

=== What the release pins ===
* Engine: Morrowmake/vllm-cmp170hx branch <code><nowiki>ampere</nowiki></code> at <code><nowiki>a0c57b52376efd67c57735bc949d4bafa22ae29e</nowiki></code> on upstream vLLM 4e0681ed56. Image <code><nowiki>ghcr.io/morrowmake/vllm-cmp170hx:engine-a0c57b5237</nowiki></code>, digest <code><nowiki>sha256:f67d9be47ffbd4a8b84c77fe76bdb3f842187d9b2786fff573e390ae5361bfb0</nowiki></code>. The release's launch is baked into the image at <code><nowiki>/opt/recipe/serve.sh</nowiki></code>.
* Export: [https://huggingface.co/LibertAIDAI/DeepSeek-V4.1-Flash-1017-EXL3-2.9bpw LibertAIDAI/DeepSeek-V4.1-Flash-1017-EXL3-2.9bpw] at <code><nowiki>c178a012</nowiki></code> (about 196 GiB, routed experts only are used).
* Official: [https://huggingface.co/deepseek-ai/DeepSeek-V4.1-Flash-1017 deepseek-ai/DeepSeek-V4.1-Flash-1017] at <code><nowiki>1bae0e10</nowiki></code> (about 475 GiB FP8, including the Engram tables in its last two shards).
* The served directory <code><nowiki>DeepSeek-V4.1-Flash-1017-hybrid-exl3-fp8</nowiki></code> holds only links plus a config, index and quantization config that must match validated bytes.
* Model: 384 routed experts per layer, 6 active per token.
* Engine switches the release sets to 1, each a kill switch through <code><nowiki>.env</nowiki></code>: <code><nowiki>VLLM_DEEPSEEK_V41_ATTN_PIPELINE</nowiki></code>, <code><nowiki>VLLM_DEEPSEEK_V41_FUSED_ROUTE</nowiki></code>, <code><nowiki>VLLM_DEEPSEEK_V41_GATE_GEMV</nowiki></code>, <code><nowiki>VLLM_DEEPSEEK_V41_ROUTER_MMA</nowiki></code>, <code><nowiki>VLLM_EXL3_MOE_V2</nowiki></code>, <code><nowiki>VLLM_DEEPSEEK_V41_MOE_PREFILL_TC</nowiki></code>, <code><nowiki>VLLM_DEEPSEEK_V41_PREFILL_CE_ALLREDUCE</nowiki></code>, <code><nowiki>VLLM_DEEPSEEK_V41_PREFILL_SPLIT_REDUCE</nowiki></code>, <code><nowiki>VLLM_HOST_ALLREDUCE</nowiki></code>.
* Serving defaults: 262,144 context, up to 8 requests, 2,048 tokens per scheduler step, CUDA graphs for decode steps up to 48 tokens, fair prefill in 512-token pieces, prefix caching on, <code><nowiki>deepseek_v41</nowiki></code> tool and reasoning parsers, images on. DSpark drafts up to 7 tokens for one request, 5 for more; <code><nowiki>EXTRA_ARGS="--speculative-config None"</nowiki></code> turns speculation off.
{{Source|handle=lia_oc|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563528168688586764|repo=https://github.com/Morrowmake/dsv41-flash-cmp170hx-recipe}}

=== Engram placement ===
<code><nowiki>VLLM_ENGRAM_PLACEMENT=auto</nowiki></code> (default) picks RAM when 212 GiB (<code><nowiki>NEED_RAM_GIB</nowiki></code>) is available, else SSD. In
SSD mode each card gets a row cache of (available RAM minus 29 GiB) / 4, clamped to 1 to 48 GiB (48 GiB holds a card's
whole share); at 12 GiB or more it preloads at start (about 49 GB read per card) and reads past the page cache.
Measured cost of SSD mode with a 38 GiB cache: first token on a cold 2K prompt 6% later (772 vs 725 ms), a 32K prompt 1%
later, decode within 1%. Swap is disabled through <code><nowiki>MEM_LIMIT</nowiki></code>, because swapped Engram tables cost about 8%
prefill.
{{Source|handle=lia_oc|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563528168688586764|repo=https://github.com/Morrowmake/dsv41-flash-cmp170hx-recipe}}

== Measured numbers ==
Author's release check, 2026-10-24: 74 SMs and 180 W per card, PCIe x16, P2P verified, Engram in RAM, MiaAI-Lab
protocol (400 tokens, temperature 0, thinking off), median of five runs including time to first token. Tok/s
structured / code / prose, marked "up to".
{| class="wikitable"
! !! 1 user !! 2 users !! 4 users !! 8 users
|-
| Default || 319 / 287 / 162 || 360 / 431 / 230 || 545 / 602 / 324 || 765 / 729 / 432
|}
* Cold prefill 3,818 tok/s (2,048-token prompt), 3,808 tok/s (32,768-token prompt). KV pool 1,247,406 tokens (BF16, not quantized).
* Quality: HumanEval 157/164, GSM8K 1,280/1,319, against a reference of 157/164 and 1,279/1,319.
* Fallbacks (prose 1 user / 8 users / cold 2K prefill): Engram from SSD with a 48 GiB cache 151 / 428 / 3,607; <code><nowiki>P2P=off</nowiki></code> 133 / 344 / 3,804 (2 and 4 users without P2P up to 192 and 271).
{{Source|handle=lia_oc|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563528168688586764|repo=https://github.com/Morrowmake/dsv41-flash-cmp170hx-recipe}}

=== Other people's numbers ===
{{Status|Contested}} Two other people measured this recipe well below the published figures, each with stated
differences:
* CurtisAccelerate (same board as his own recipe: dual-socket Broadwell, 140 W, peer access off), one user count / code / prose 122.8 / 90.3 / 62.4 tok/s, 8-user aggregate 168.7, cold prefill at 128K 1,558.7 tok/s (faster than his own stack at every length). Another of his tables reads 254.1 / 196.2 / 139.7, with large boot-to-boot spread. {{Source|handle=anon33anon|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561910289799184445|repo=https://github.com/CurtisAccelerate/DeepSeekv41-Flash-1017-EXL3-CMP170HX}}
* The lab (heretic patch applied, a miner sharing the cards so <code><nowiki>--gpu-memory-utilization 0.92</nowiki></code>, Engram on SSD, its own bench): one user code 158, structured 136, prose 121; 8 users 323 / 261 / 249; warm prefill 2,453 tok/s on a 17k prompt. See [[DeepSeek V4.1 Flash heretic on 4x 8 GB]]. {{Source|handle=darkmaniac7|date=2026-10-29|note=lab notes}}
* Mountains ran it for two days on PCIe Gen2 x4 cards: better quality than the earlier GNmac build, roughly similar speed, handles complex work better, and he rates it above GLM 5.3 Flash; he is staying on it. No tok/s posted. {{Source|handle=mountains1605|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1564695486911217665}} {{Source|handle=mountains1605|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1564711187659362447}}

== Accuracy on long contexts ==
On the lab's long-context copy test (75k to 92k-token roleplay turns that must copy image paths and names exactly), this
recipe's engine got 0 of 29 paths wrong with the same 2.9 bpw expert files on which the GNmac engine got 85% wrong.
OpenRouter's full-precision 1017 also scored 0%. See [[DeepSeek V4.1 Flash on 4x 8 GB (GNmac)]].
{{Source|handle=darkmaniac7|date=2026-10-29|note=lab notes}}

== Known issues ==
* Reasoning is on by default and arrives in the <code><nowiki>reasoning</nowiki></code> field. <code><nowiki>"chat_template_kwargs": {"thinking": false}</nowiki></code> turns it off; <code><nowiki>reasoning_effort</nowiki></code> takes low, high (default), xhigh, max, or a number 1 to 100 in <code><nowiki>chat_template_kwargs</nowiki></code>. <code><nowiki>max_tokens</nowiki></code> must cover reasoning plus answer, or <code><nowiki>content</nowiki></code> is empty with <code><nowiki>finish_reason: "length"</nowiki></code>.
* One layout only (TP4), needing x16 links; no PP layout yet.
* Heavy host requirements: about 240 GiB RAM for the published numbers and about 680 GiB of disk. alanoo notes it is much larger on disk than his mixed-bpw build. {{Source|handle=alanoo|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1564697318081560679}}
* First release (1.0.0), so less field history than the GLM recipe.
{{Source|handle=lia_oc|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563528168688586764|repo=https://github.com/Morrowmake/dsv41-flash-cmp170hx-recipe}}
* With anything else holding memory on the cards (a miner holds 2.5 GiB per card), the default 0.95 runs out of memory on a 17k-token prefill; 0.92 fixed it. {{Source|handle=darkmaniac7|date=2026-10-29|note=lab notes}}
* The recipe does not pass <code><nowiki>CUDA_DEVICE_ORDER</nowiki></code> into the container. To serve from four cards of a larger box, add it to <code><nowiki>CONTAINER_KEYS</nowiki></code> in <code><nowiki>start.sh</nowiki></code> and set <code><nowiki>CUDA_DEVICE_ORDER=PCI_BUS_ID</nowiki></code> plus <code><nowiki>CUDA_VISIBLE_DEVICES</nowiki></code> in <code><nowiki>.env</nowiki></code>. {{Source|handle=darkmaniac7|date=2026-10-29|note=lab notes}}

== Related ==
* With pqhaz's heretic (abliteration) patch: [[DeepSeek V4.1 Flash heretic on 4x 8 GB]].
* Other 4-card builds: [[DeepSeek V4.1 Flash on 4x 8 GB (GNmac)]], [[DeepSeek V4.1 Flash on 4x 8 GB (alanoo fidelity build)]], [[DeepSeek V4.1 Flash on 4x 8 GB (CurtisAccelerate TC-MoE)]].
* More cards: [[DeepSeek V4.1 Flash on 8x 8 GB (Zanooda PP8)]], [[DeepSeek V4.1 Flash on 6x 8 GB (Deepinfer-SM80 TP2 x PP3)]].
* [[Engines]], [[Quantization on the 170HX]], [[Benchmarks]].

== Sources ==
* Repo: [https://github.com/Morrowmake/dsv41-flash-cmp170hx-recipe Morrowmake/dsv41-flash-cmp170hx-recipe] (MIT; checkpoints MIT), last commit 2026-10-26. Credits GNmac-lab's recipe for an adapted grouped FP8 GEMM and design ideas.
* Posted on Discord by _L_ (2026-10-24) and recommended for 4-card owners with enough RAM or SSD. {{Source|handle=lia_oc|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564319994152488971}}

{{ImportFooter}}
[[Category:8 GB]]

DeepSeek V4.1 Flash on 4x 8 GB (GNmac)

2026-10-31T21:34:27Z

ImportBot: Import: GNmac-lab/deepseek-v41-flash-1017-cmp170hx 1.0.0 to 1.2.0 (repo and greencandle's Discord posts); Mountains' x4 run; the lab run and long-context copy finding; sources: @greencandle9753, @cibernox, @darkmaniac7, @mountains1605; GitHub GNmac-lab/deepseek-v41-flash-1017-cmp170hx; lab notes of @darkmaniac7

{{Recipe
|model=DeepSeek-V4.1-Flash-1017
|quant=Hybrid: routed experts EXL3 (mostly 3 bpw, 2 bpw on layers 18-22) from LibertAI's 2.9 bpw pack; attention, shared experts, indexer and DSpark drafter official FP8; KV fp8_ds_mla
|engine=vLLM with a pinned sm_80 patch stack (built locally from source)
|engine_version=recipe 1.2.0
|cards=8 GB
|card_count=4
|topology=TP4 (default) or PP4 for x1/x4 links
|context=262,144 (up to 1,048,576)
|decode_tps=258
|prefill_tps=2416
|vram_per_card=64 GiB, GPU_MEMORY_UTILIZATION 0.95
|power_cap=180 W (nvidia-smi -pl 180)
|driver=CUDA 13 capable; measured on 610.43.02
|unlock_build=cmpunlocker (64 GiB, 74 SMs) with a P2P-capable driver for TP4
|flags=LAYOUT=tp4, MAX_MODEL_LEN 262144, MAX_NUM_SEQS 8, GPU_MEMORY_UTILIZATION 0.95, P2P 1, DSV41_GATE_TAU 0.10, DSV41_DYNK accept:3,5
|status=Reported
|tested_by=greencandle9753
|tested_on=2026-10-26
|source=https://github.com/GNmac-lab/deepseek-v41-flash-1017-cmp170hx
}}
DeepSeek-V4.1-Flash-1017 on four 64 GB cards with vLLM and a patch stack for sm_80, an OpenAI-compatible API with
tools, reasoning and images, and up to 1M tokens of context. The checkpoint is a hybrid (Curtis White's layout): EXL3
routed experts plus the official FP8 dense tensors, with the 189 GiB Engram n-gram tables streamed from NVMe instead of
loaded, so it needs far less host RAM than the Morrowmake recipe. Infobox numbers are release 1.2.0, one user on code.
{{Source|handle=greencandle9753|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562465339395280909|repo=https://github.com/GNmac-lab/deepseek-v41-flash-1017-cmp170hx}} 
{{Source|handle=greencandle9753|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562465339395280909}}

'''Read the long-context copy finding under Known issues before using it for work that must copy names or paths
exactly.'''

== Prerequisites ==
* Four CMP 170HX at 64 GiB and 74 SMs ([[Driver unlock]], [[8 GB card]]).
* PCIe 2.0 x16 links with a P2P-capable driver for TP4 (<code><nowiki>tools/p2p_check.sh</nowiki></code>); on x1 or x4 links use <code><nowiki>LAYOUT=pp4</nowiki></code>. greencandle: to match his single-user numbers you have to do the x16 mod. {{Source|handle=greencandle9753|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562929719794602087}}
* Driver with CUDA 13 support (measured on 610.43.02), Docker with the NVIDIA Container Toolkit.
* About 400 GiB of fast NVMe for checkpoints plus about 40 GiB for the image; 64 GB+ of host RAM.
{{Source|handle=greencandle9753|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562465339395280909|repo=https://github.com/GNmac-lab/deepseek-v41-flash-1017-cmp170hx}}

== Steps ==
<syntaxhighlight lang="bash">
git clone https://github.com/GNmac-lab/deepseek-v41-flash-1017-cmp170hx && cd deepseek-v41-flash-1017-cmp170hx
cp .env.example .env # set MODELS_DIR (fast NVMe, ~400 GiB free)
tools/download.sh # model parts + hybrid assembly (resumable)
./start.sh # builds the image on first use (~30-45 min), starts, waits until ready
./start.sh smoke # one chat, one tool call, one image
</syntaxhighlight>
Test request (model name <code><nowiki>deepseek-v4.1-flash</nowiki></code>):
<syntaxhighlight lang="bash">
curl -s http://127.0.0.1:8000/v1/chat/completions -H 'Content-Type: application/json' -d '{
"model": "deepseek-v4.1-flash", "messages": [{"role": "user", "content": "Hello!"}], "max_tokens": 200}'
</syntaxhighlight>
The server binds 127.0.0.1:8000 with no API key; reach it from another machine through an SSH tunnel
(<code><nowiki>ssh -N -L 127.0.0.1:8000:127.0.0.1:8000 you@gpu-host</nowiki></code>). Update: <code><nowiki>git pull && docker/build.sh && ./start.sh restart</nowiki></code>.
{{Source|handle=greencandle9753|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562465339395280909|repo=https://github.com/GNmac-lab/deepseek-v41-flash-1017-cmp170hx}}

=== Checkpoint and engine ===
* Routed experts, layers 0-39: EXL3 trellis mul1, 3 bpw (2 bpw on layers 18-22), from [https://huggingface.co/LibertAIDAI/DeepSeek-V4.1-Flash-1017-EXL3-2.9bpw LibertAIDAI/DeepSeek-V4.1-Flash-1017-EXL3-2.9bpw] (197 GB).
* Attention, shared experts, KV compressor, indexer and the DSpark drafter: FP8 e4m3 UE8M0 from [https://huggingface.co/deepseek-ai/DeepSeek-V4.1-Flash-1017 the official release] (18 GB, fetched by HTTP range requests).
* Engram tables for layers 1 and 14: FP8+E8M0, 190 GB (shards 47-48), read from NVMe while serving. KV cache <code><nowiki>fp8_ds_mla</nowiki></code>.
* Engine pins (NOTICE.md): base image <code><nowiki>vllm/vllm-openai:deepseekv41-flash-0909</nowiki></code>, zebgop-ops/dsv41reap-pp <code><nowiki>138e748</nowiki></code>, kaka86mm/dsv41-flash-pp4-170hx <code><nowiki>950f4c0</nowiki></code>, turboderp exllamav3 v1.5.3 (<code><nowiki>d3739fd</nowiki></code>), vcruz305/vllm-exl3 <code><nowiki>223e246</nowiki></code>, CurtisAccelerate/DeepSeekv41-Flash-EXL3-TC-MoE <code><nowiki>88eb6e1</nowiki></code>, FlashInfer v0.7.0.post1 (PCIe IPC all-reduce), HalfVulpes/Deepinfer-SM80 <code><nowiki>2a828fc</nowiki></code>, Morrowmake/vllm-cmp170hx <code><nowiki>a0c57b5</nowiki></code>; <code><nowiki>TORCH_CUDA_ARCH_LIST=8.0</nowiki></code>. No prebuilt image: the first build takes 30 to 45 minutes.
* <code><nowiki>.env</nowiki></code> keys: <code><nowiki>LAYOUT</nowiki></code> tp4 or pp4, <code><nowiki>MAX_MODEL_LEN</nowiki></code> 262144 (up to 1048576, KV pool then 1,270,789 tokens), <code><nowiki>MAX_NUM_SEQS</nowiki></code> 8, <code><nowiki>GPU_MEMORY_UTILIZATION</nowiki></code> 0.95, <code><nowiki>P2P</nowiki></code> 1 (0 routes NCCL through host memory), <code><nowiki>DSV41_GATE_TAU</nowiki></code> 0.10 (confidence-gated draft verification; 0 verifies all 5 drafts), <code><nowiki>DSV41_DYNK</nowiki></code> accept:3,5 (TP4 only), <code><nowiki>DSV41_VARIANTS</nowiki></code>, <code><nowiki>BIND</nowiki></code>, <code><nowiki>PORT</nowiki></code>.
* <code><nowiki>reasoning_effort</nowiki></code> accepts none, low, high, xhigh, max; minimal and medium are rejected by the chat template (HTTP 400).
{{Source|handle=greencandle9753|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562465339395280909|repo=https://github.com/GNmac-lab/deepseek-v41-flash-1017-cmp170hx}}

== Measured numbers ==
Author's numbers, 4 cards at 180 W, MiaAI-Lab protocol, tok/s structured / code / prose:
{| class="wikitable"
! Release !! Layout !! 1 user !! 8 users !! Cold prefill !! KV pool
|-
| 1.0.0 (2026-10-21) || TP4 || 296 / 212 / 150 || 796 / 477 / 359 || 1,759 || 1.57M
|-
| 1.1.0 (2026-10-23) || TP4 || 336 / 247 / 180 || +6 to +7% on code and prose || 1,764 ||
|-
| 1.2.0 (2026-10-26) || TP4 || 356 / 258 / 184 || 868 / 544 / 441 || 2,416 || 1,395,731
|-
| 1.2.0 || PP4 || 118 / 91 / 63 || 341 / 214 / 163 || 2,311 || 2,539,313
|}
1.2.0 at 2 users: 433 / 244 / 239; at 4 users: 626 / 388 / 349. Quality 1.2.0 (TP4): HumanEval 154/164, GSM8K
1,275/1,319 (1.1.0: 156 and 1,273); dqeval NLL 3.50001 against 3.48019; a 20-minute 8-stream soak served 1,018 requests
with 0 errors at 334.8 tok/s. In a quick comparison it gave greencandle better results than his previous GLM Flash
setup.
{{Source|handle=greencandle9753|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562465339395280909|repo=https://github.com/GNmac-lab/deepseek-v41-flash-1017-cmp170hx}} 
{{Source|handle=greencandle9753|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563066699840884806}} 
{{Source|handle=greencandle9753|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562822643663511564}}

* Decode was the focus; prefill has headroom. cibernox: prefill on the weaker side but totally usable. {{Source|handle=greencandle9753|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562471620478763063}} {{Source|handle=cibernox|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562470944130342945}}
* KLD for the weights is on the [https://huggingface.co/Mia-AiLab/DeepSeek-V4.1-Flash-1017-EXL3-EAQ-v1-2.9-bpw Mia-AiLab EXL3 EAQ v1 2.9 bpw] model card. The vLLM changes are kernel, scheduling or memory changes that are bit-identical or only reorder FP32 sums; speculative decoding does not change the output distribution because the target model verifies every kept token. {{Source|handle=greencandle9753|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563300802238484561}}

=== Other people's numbers ===
* The lab (TP4 on four cards of an 8-card box, Gen2 x16, P2P on, its own bench with 1,024-token answers): one user code 244, structured 212, prose 136; 8 users 522 / 425 / 346; prefill 2.0k to 2.6k tok/s (a 48k prompt in 20 to 25 s); KV pool 1.4M at 262K. DSpark gives 2.6x decode. Keep the prefill budget at 2,048 as shipped: 8,192 and 16,384 were slower, and 8,192 with DSpark crashed. {{Source|handle=darkmaniac7|date=2026-10-28|note=lab notes}}
* Mountains (four cards on PCIe Gen2 x4): PP4 did not work well, so he switched to TP4 with P2P; single stream maybe 10% below GLM 5.3 Flash and never felt slow; first load about 8 minutes or more on Gen2 x4. He found it a bit more intelligent than GLM 5.3 Flash but less consistent, went back to GLM, then moved to the Morrowmake build, which he found better on prefill and quality. {{Source|handle=mountains1605|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562849601697095793}} {{Source|handle=mountains1605|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562982101157150771}} {{Source|handle=mountains1605|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1564711187659362447}}

== Known issues ==
* '''Long-context copy errors (engine defect).''' On the lab's test (75k to 92k-token roleplay turns that must copy image paths and names exactly), this build got 85% of named paths wrong. Bisecting one change at a time on stock dense weights: cutting the prompt to the last 5 turns, 33% wrong (long-range); BF16 KV cache, 100%; the synchronous Engram path, 100%; OpenRouter's full-precision 1017, 0%; Morrowmake's recipe with the same 2.9 bpw expert files, 0% (0 of 29). Ruled out: the heretic patch, the sampler, DSpark, the prompts, the detokenizer (the model ranks the wrong token first). So the defect is in this stack's sm_80 attention or kernel path, not the quant. See [[DeepSeek V4.1 Flash on 4x 8 GB (Morrowmake)]]. {{Source|handle=darkmaniac7|date=2026-10-29|note=lab notes}}
* TP4 on links narrower than x16 is very slow (about 86 all-reduces per step); use PP4 there. PP4 on x4 links is extrapolated by the author, not measured.
* A startup hang at 100% GPU and low power is an all-reduce waiting on broken P2P: try <code><nowiki>P2P=0</nowiki></code>. Never <code><nowiki>kill -9</nowiki></code> a multi-GPU vLLM; use <code><nowiki>./stop.sh</nowiki></code>.
* Prose runs about 20% slower right after a restart until the Engram rows are in the page cache. A 1M-token prefill takes about 25 minutes.
* TP4 greedy text is not bit-reproducible across processes (compare NLL, not text).
* A worker OOM at load (about 25 GB host RAM per worker) means <code><nowiki>VLLM_EXL3_MODEL_DIR</nowiki></code> is unset.
* License: MIT except <code><nowiki>patches/vllm-exl3/</nowiki></code>, which is AGPL-3.0-only; anyone serving others from the built image inherits AGPL obligations (NOTICE.md). The hybrid assembly depends on a <code><nowiki>quantization_config.json</nowiki></code> fetched from CurtisAccelerate's repo, which states no license.
{{Source|handle=greencandle9753|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562465339395280909|repo=https://github.com/GNmac-lab/deepseek-v41-flash-1017-cmp170hx}}
* A slow NVMe and little RAM headroom can struggle with the streamed Engram tables. {{Source|handle=greencandle9753|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562470200211800095}}

=== Build and run traps (lab notes) ===
* The draft count (<code><nowiki>SPEC_TOKENS</nowiki></code>) must be 5: 6 and 7 do not start; 3 and 4 boot but every request fails.
* Keep the shipped prefill budget of 2,048: 8,192 without DSpark gave 1,400-1,770 tok/s at 48k and 94 tok/s decode, 16,384 shrank the KV pool to 619k tokens, and 8,192 with DSpark died on the first 48k request. The prefill chunk must stay 2,048 with images (1,024 does not start, 4,096 runs out of memory).
* The image build needs Docker buildx (the Dockerfile uses <code><nowiki>RUN --mount=type=bind</nowiki></code>) and runs about 32 nvcc jobs at once (MAX_JOBS=16, two stages in parallel), so build on a machine that can take it. It took 1,351 s here, no GPU needed, about 40 GiB.
* <code><nowiki>serve.sh</nowiki></code> uses <code><nowiki>--gpus all</nowiki></code> and a busy guard that sums memory over every card, so a second instance on other cards of the same box needs a wrapper.
* This stack never uses vLLM's custom all-reduce; it uses FlashInfer's PCIe IPC all-reduce (<code><nowiki>VLLM_ALLREDUCE_USE_FLASHINFER_PCIE_IPC=1</nowiki></code>).
{{Source|handle=darkmaniac7|date=2026-10-28|note=lab notes}}

== Abliterated variant ==
pqhaz's heretic patch edits only the 38 <code><nowiki>attn.wo_b</nowiki></code> tensors, and this recipe takes exactly those dense tensors
from the official checkpoint, so the patch drops in with no requantization: rewrite the 18 GB of non-expert shards with
the patch and point the hybrid at them. Uncensored EXL3 bundles whose edit lives in other dense tensors would silently
do nothing here. See [[DeepSeek V4.1 Flash heretic on 4x 8 GB]].
{{Source|handle=darkmaniac7|date=2026-10-28|note=lab notes}}

== Related ==
* Forks of this recipe: [[DeepSeek V4.1 Flash on 4x 8 GB (alanoo fidelity build)]]. Its kernel source: [[DeepSeek V4.1 Flash on 4x 8 GB (CurtisAccelerate TC-MoE)]].
* [[DeepSeek V4.1 Flash on 4x 8 GB (Morrowmake)]], [[Engines]], [[Quantization on the 170HX]], [[Benchmarks]].

== Sources ==
* Repo: [https://github.com/GNmac-lab/deepseek-v41-flash-1017-cmp170hx GNmac-lab/deepseek-v41-flash-1017-cmp170hx], releases 1.0.0 (2026-10-21), 1.1.0 (2026-10-23), 1.2.0 (2026-10-26). Posted on Discord by greencandle.

{{ImportFooter}}
[[Category:8 GB]]

DeepSeek V4.1 Flash heretic on 4x 8 GB

2026-10-31T21:34:26Z

ImportBot: Import: The lab recipe (lab notes, 2026-10-29): Morrowmake dsv41-flash-cmp170hx-recipe 1.0.0 with pqhaz's heretic patch written into the official checkpoint in place; sources: @darkmaniac7; GitHub Morrowmake/dsv41-flash-cmp170hx-recipe

{{Recipe
|model=DeepSeek-V4.1-Flash-1017 heretic (pqhaz abliteration)
|quant=Hybrid: routed experts EXL3 2.9 bpw (LibertAIDAI), everything else official FP8/BF16 with the 38 heretic attn.wo_b tensors
|engine=Morrowmake/vllm-cmp170hx (vLLM fork, container image)
|engine_version=recipe 1.0.0 (commit d4d1f525), engine a0c57b52
|cards=8 GB
|card_count=4
|topology=TP4
|context=262,144
|decode_tps=158
|prefill_tps=2453
|vram_per_card=64 GiB, --gpu-memory-utilization 0.92 (miner co-resident)
|flags=EXTRA_ARGS="--gpu-memory-utilization 0.92", VLLM_ENGRAM_PLACEMENT=ssd, CUDA_DEVICE_ORDER=PCI_BUS_ID
|status=Reported
|tested_by=darkmaniac7
|tested_on=2026-10-29
|source=https://github.com/Morrowmake/dsv41-flash-cmp170hx-recipe
}}
Morrowmake's recipe for DeepSeek-V4.1-Flash on four CMP 170HX, unchanged except for a few <code><nowiki>.env</nowiki></code> lines, with
pqhaz's heretic patch written into the official checkpoint in place. Nothing was retrained or requantized. The result
answers prompts the stock model refuses, keeps tool calls and long-context copying accurate, and reasons longer.
{{Source|handle=darkmaniac7|date=2026-10-29|note=lab notes}}

== Parts (pinned) ==
{| class="wikitable"
! Part !! Source !! Pin
|-
| Recipe || [https://github.com/Morrowmake/dsv41-flash-cmp170hx-recipe Morrowmake/dsv41-flash-cmp170hx-recipe] || commit <code><nowiki>d4d1f525</nowiki></code> (release 1.0.0)
|-
| Engine image || <code><nowiki>ghcr.io/morrowmake/vllm-cmp170hx</nowiki></code> || <code><nowiki>sha256:f67d9be47ffbd4a8b84c77fe76bdb3f842187d9b2786fff573e390ae5361bfb0</nowiki></code> (vLLM fork Morrowmake/vllm-cmp170hx at <code><nowiki>a0c57b52</nowiki></code>)
|-
| Routed experts || [https://huggingface.co/LibertAIDAI/DeepSeek-V4.1-Flash-1017-EXL3-2.9bpw LibertAIDAI/DeepSeek-V4.1-Flash-1017-EXL3-2.9bpw] || EXL3 2.9 bpw, about 211 GB
|-
| Everything else || [https://huggingface.co/deepseek-ai/DeepSeek-V4.1-Flash-1017 deepseek-ai/DeepSeek-V4.1-Flash-1017] || official FP8/BF16, about 510 GB
|-
| Abliteration || [https://huggingface.co/pqhaz/DeepSeek-V4.1-Flash-1017-heretic pqhaz/DeepSeek-V4.1-Flash-1017-heretic], <code><nowiki>patch/</nowiki></code> folder only || 38 tensors, 1.6 GB; the lab copy sha256 <code><nowiki>16e63cd3e79c3590855aad340b5b9dc37f27562bf2d0a40f85268915da221ce2</nowiki></code>
|}
{{Source|handle=darkmaniac7|date=2026-10-29|note=lab notes}}

== Why an in-place patch is enough ==
The recipe's <code><nowiki>download.sh</nowiki></code> fetches both checkpoints and builds <code><nowiki>DeepSeek-V4.1-Flash-1017-hybrid-exl3-fp8</nowiki></code>,
a directory of links. The routed experts (<code><nowiki>layers.N.ffn.experts.*</nowiki></code>) come from the EXL3 export; every other
tensor, attention included, is a link to the official shards.

The heretic edit only touches <code><nowiki>layers.2-39.attn.wo_b.weight</nowiki></code>. Each edited tensor keeps the same FP8 dtype, shape
and byte offset, and the block scales are untouched. Those tensors live in the official shards, so overwriting them
there makes the served hybrid heretic with no rebuild. The heretic release leaves the routed experts alone (their FP4
storage cannot hold the edit), so it combines cleanly with the 2.9 bpw EXL3 experts.
{{Source|handle=darkmaniac7|date=2026-10-29|note=lab notes}}

== Steps ==
# Do the recipe's one-time host setup, clone it and run <code><nowiki>./install.sh</nowiki></code>, as its README says. Prerequisites are those of [[DeepSeek V4.1 Flash on 4x 8 GB (Morrowmake)]].
# <code><nowiki>./download.sh</nowiki></code> fetches both checkpoints and builds the hybrid. Budget about 680 GiB.
# Fetch the patch only: <syntaxhighlight lang="bash" inline>hf download pqhaz/DeepSeek-V4.1-Flash-1017-heretic --include "patch/*" --local-dir heretic</syntaxhighlight>
# Write it into the official checkpoint in place with <code><nowiki>heretic_inplace.py</nowiki></code> (below, stdlib Python only):
#: {{Download|file=Heretic_inplace.py|compact=yes}} The script applies the heretic patch to the official shards in place, restores them byte-exact from the backup, or reports their status.
<syntaxhighlight lang="bash">
python3 heretic_inplace.py apply <MODELS_DIR>/DeepSeek-V4.1-Flash-1017 heretic/patch/<file>.safetensors stock-wo_b-backup.safetensors
python3 heretic_inplace.py status <same three args> # expect: heretic 38, stock 0, other 0
python3 heretic_inplace.py restore <same three args> # undo, byte-exact
</syntaxhighlight>
#: <code><nowiki>apply</nowiki></code> first saves the 38 stock tensors to the backup file (1.6 GB), then overwrites each tensor, fsyncs and reads it back. It refuses any shard that has other hard links, so it cannot patch a second copy by accident. Re-running it does nothing.
#: To avoid patching in place, the heretic repo's own <code><nowiki>ds_patch.py apply <official> <patch> <new_dir></nowiki></code> writes a patched copy instead. It rewrites 38 full shards (about 7 GB each, roughly 260 GB extra) and hard-links the rest. Put that copy under the official checkpoint's directory name: the hybrid's links resolve by that name, and the index and config the builder checks are unchanged.
# <code><nowiki>.env</nowiki></code> changes, all specific to the lab box:
#* <code><nowiki>CUDA_VISIBLE_DEVICES=4,5,6,7</nowiki></code> and <code><nowiki>CUDA_DEVICE_ORDER=PCI_BUS_ID</nowiki></code>, because this runs on four cards of an 8-card machine. The recipe does not pass <code><nowiki>CUDA_DEVICE_ORDER</nowiki></code> into the container, so it was added to <code><nowiki>CONTAINER_KEYS</nowiki></code> in <code><nowiki>start.sh</nowiki></code> (a one-word change). On a 4-card box you need neither.
#* <code><nowiki>EXTRA_ARGS="--gpu-memory-utilization 0.92"</nowiki></code>, only because a miner shares the cards and holds 2.5 GiB on each. At the default 0.95 a 17k-token prefill ran out of memory. With nothing else on the cards, keep the default.
#* <code><nowiki>VLLM_ENGRAM_PLACEMENT=ssd</nowiki></code> (default <code><nowiki>auto</nowiki></code>) keeps the Engram tables on SSD instead of in RAM. If you have the RAM, <code><nowiki>auto</nowiki></code> is fine.
#* <code><nowiki>PORT</nowiki></code> and <code><nowiki>SERVED_MODEL_NAME</nowiki></code> are cosmetic.
# <code><nowiki>./start.sh</nowiki></code>, then <code><nowiki>./start.sh smoke</nowiki></code> (one chat request and one tool call).
{{Source|handle=darkmaniac7|date=2026-10-29|note=lab notes}}

== Measured numbers ==
On the lab box: four CMP 170HX on PCIe, sharing the machine with a miner, measured with its own bench script. Not
comparable with the numbers the recipe publishes.
{| class="wikitable"
! !! Result
|-
| Decode, 1 user || code 158, structured 136, prose 121 tok/s
|-
| Decode, 8 users (total) || code 323, structured 261, prose 249 tok/s
|-
| Prefill, 17k-token prompt (warm) || 2,453 tok/s
|-
| Long-context copy accuracy (75k to 92k-token roleplay turns that must copy image paths and names exactly) || 1 wrong of 30. The miss picked a different variant of the right image, not a garbled path
|-
| Same 2.9 bpw expert files on a different engine (GNmac) || 85% wrong on the same test. So that engine causes the copy errors, not the quant or the heretic edit
|-
| Refusal spot check (4 prompts, 1,500-token cap) || 2 answered, 2 hit the cap while still reasoning, 0 refused
|-
| Tool calls (<code><nowiki>deepseek_v41</nowiki></code> parser) || work
|}
The heretic model card reports 1 refusal in 100 held-out prompts (base: 97) and KL 0.136 on harmless prompts.
An earlier run under the same conditions read 150 / 131 / 117 tok/s for one user (code / structured / prose); the GNmac engine on the same cards read 248 / 177 / 135 and 542 / 396 / 347 at 8 users, prefill 2,697.
{{Source|handle=darkmaniac7|date=2026-10-29|note=lab notes}} 
{{Source|handle=darkmaniac7|date=2026-10-29|note=lab notes}}

== Things to know ==
* It reasons much longer after the edit. The model card puts the median completion at 1,517 tokens against 357 for the base. Set <code><nowiki>max_tokens</nowiki></code> generously, or <code><nowiki>content</nowiki></code> comes back empty with <code><nowiki>finish_reason: "length"</nowiki></code>.
* No capability benchmarks have been run on the heretic version, the lab's or the model card's. KL 0.136 means general behaviour has shifted somewhat.
* Speed is engine-bound. On the lab box the GNmac engine decodes 1.1 to 1.7x faster (prefill 1.1x) but corrupts long-context copying, so it kept Morrowmake. See [[DeepSeek V4.1 Flash on 4x 8 GB (GNmac)]].
* Uncensored EXL3 bundles whose edit lives in dense tensors do nothing on the GNmac engine, which takes dense tensors from the official checkpoint; the heretic patch works on both engines because it patches those official tensors. {{Source|handle=darkmaniac7|date=2026-10-28|note=lab notes}}
{{Source|handle=darkmaniac7|date=2026-10-29|note=lab notes}}

== Checks ==
* After applying the patch the lab checked the weights: the dequantize/requantize round trip reproduces 100.00% of the original FP8 codes; 92-99% of the patched codes are within one FP8 step of the ideal rank-1 edit; the change is 3.7-4.7% of the weight norm on all 38 tensors. Nothing beyond the advertised edit plus rounding is visible.
* After any restart, confirm which checkpoint the container actually loaded (<code><nowiki>docker inspect <container> --format '{{.Args}}'</nowiki></code>): one reload silently came up on the stock hybrid.
* {{Status|Contested}} Capability: the write-up above says no capability benchmarks have been run on the heretic version. The lab's chassis notes also cite independent numbers for this layout (GSM8K and HumanEval unchanged, MMLU -0.4, HarmBench compliance 287 of 300 against 30 of 300 stock) without naming who measured them.
{{Source|handle=darkmaniac7|date=2026-10-29|note=lab notes}}

== heretic_inplace.py ==
A lab helper, stdlib Python only. It applies or undoes the patch in the official shards for engines that read
attention weights straight from the official checkpoint (Morrowmake).
<syntaxhighlight lang="python">
#!/usr/bin/env python3
"""Apply (or undo) the pqhaz heretic patch IN PLACE in the official DeepSeek-V4.1-Flash-1017 shards, for engines that
read attention weights straight from the official checkpoint (Morrowmake). Only the 38 `layers.N.attn.wo_b.weight`
tensors change (same dtype F8_E4M3, same shape, same offsets); FP8 scales are untouched, as the patch was built.

heretic_inplace.py apply OFFICIAL_DIR PATCH.safetensors BACKUP.safetensors
heretic_inplace.py restore OFFICIAL_DIR PATCH.safetensors BACKUP.safetensors
heretic_inplace.py status OFFICIAL_DIR PATCH.safetensors BACKUP.safetensors

apply: writes an exact byte backup of every original tensor first (a safetensors file with the same names), then
overwrites, fsyncs and reads back; refuses a shard with more than one hard link. restore: writes the backup back.
Idempotent: a tensor already in the wanted state is skipped. Stdlib only."""
import hashlib, json, os, struct, sys

def header(path):
with open(path, "rb") as f:
n = struct.unpack("<Q", f.read(8))[0]
h = json.loads(f.read(n))
return h, 8 + n

def region(path, name):
h, base = header(path)
t = h[name]
a, b = t["data_offsets"]
return t["dtype"], t["shape"], base + a, b - a

def read_at(path, off, size):
with open(path, "rb") as f:
f.seek(off)
return f.read(size)

def sha(b):
return hashlib.sha256(b).hexdigest()

def write_safetensors(path, tensors): # tensors: name -> (dtype, shape, bytes)
hdr, off = {}, 0
for k in sorted(tensors):
dt, shp, data = tensors[k]
hdr[k] = {"dtype": dt, "shape": shp, "data_offsets": [off, off + len(data)]}
off += len(data)
hb = json.dumps(hdr, separators=(",", ":")).encode()
hb += b" " * ((8 - len(hb) % 8) % 8)
tmp = path + ".tmp"
with open(tmp, "wb") as f:
f.write(struct.pack("<Q", len(hb)) + hb)
for k in sorted(tensors):
f.write(tensors[k][2])
f.flush(); os.fsync(f.fileno())
os.replace(tmp, path)

def main():
mode, odir, patch, backup = sys.argv[1:5]
wm = json.load(open(os.path.join(odir, "model.safetensors.index.json")))["weight_map"]
ph, _ = header(patch)
names = sorted(k for k in ph if k != "__metadata__")
plan = []
for k in names:
shard = os.path.join(odir, wm[k])
dt, shp, off, size = region(shard, k)
pdt, pshp, poff, psize = region(patch, k)
assert (dt, shp, size) == (pdt, pshp, psize), (k, dt, shp, size, pdt, pshp, psize)
plan.append((k, shard, off, size, poff))
print(f"{len(plan)} tensors in {len({p[1] for p in plan})} shards")

if mode == "status":
bh = header(backup)[0] if os.path.exists(backup) else {}
n_patched = n_stock = n_other = 0
for k, shard, off, size, poff in plan:
cur = sha(read_at(shard, off, size))
if cur == sha(read_at(patch, poff, size)): n_patched += 1
elif bh and cur == sha(read_at(backup, region(backup, k)[2], size)): n_stock += 1
else: n_other += 1
print(f"heretic {n_patched}, stock (matches backup) {n_stock}, other {n_other}")
return

if mode == "apply":
for k, shard, *_ in plan:
assert os.stat(shard).st_nlink == 1, f"{shard} has other hard links; refusing to write in place"
if not os.path.exists(backup):
orig = {}
for k, shard, off, size, poff in plan:
data = read_at(shard, off, size)
if data == read_at(patch, poff, size):
sys.exit(f"{k} is already patched and there is no backup: refusing (stock bytes unknown)")
orig[k] = (region(shard, k)[0], region(shard, k)[1], data)
write_safetensors(backup, orig)
print(f"backup written: {backup} ({os.path.getsize(backup) / 2**30:.2f} GiB)")
src = lambda k, poff, size: read_at(patch, poff, size)
elif mode == "restore":
assert os.path.exists(backup), "no backup"
src = lambda k, poff, size: read_at(backup, region(backup, k)[2], size)
else:
sys.exit("mode: apply | restore | status")

done = skipped = 0
for k, shard, off, size, poff in plan:
want = src(k, poff, size)
if read_at(shard, off, size) == want:
skipped += 1; continue
fd = os.open(shard, os.O_RDWR)
try:
assert os.pwrite(fd, want, off) == size
os.fsync(fd)
finally:
os.close(fd)
assert sha(read_at(shard, off, size)) == sha(want), f"read-back mismatch on {k}"
done += 1
print(f"{mode}: {done} written, {skipped} already in place, all read back OK")

if __name__ == "__main__":
main()
</syntaxhighlight>
{{Source|handle=darkmaniac7|date=2026-10-29|note=lab notes}}

== Credits ==
DeepSeek for the model. Morrowmake for the recipe and the Ampere vLLM fork. LibertAI for the EXL3 2.9 bpw quant. pqhaz
for the heretic ablation of 1017. p-e-w for the Heretic method.

== Related ==
* The base recipe: [[DeepSeek V4.1 Flash on 4x 8 GB (Morrowmake)]]. Other heretic and abliterated variants: [[Quantization on the 170HX]].
* [[Engines]], [[Benchmarks]], [[Recipes]].

== Sources ==
* Lab notes, 2026-10-29 (public write-up of the recipe).
* The script is [[:File:Heretic_inplace.py]]; its sha256 is shown in the Download box in the Steps section.

{{ImportFooter}}
[[Category:8 GB]]

Cooling and power

2026-10-31T21:34:26Z

ImportBot: Cooling and power overview, from the cmpunlocker Discord (cooling-power items, 2026-10-04 to 10-28), cachenetics/170tune, PixelML/club-170hx, amoghmunikote/170th-Street and lab notes; sources: @analyticeth, @nikhilr1696, @programmerboi, @rh3dai, @mlx4, @wakeupmbrc1, @zorg33, @darkmaniac7, @c133, @68x0, @_arcanum_, @artistosu (+5 more); GitHub PixelML/club-170hx, cachenetics/170tune

The CMP 170HX is a passive data-center card. It has a large copper heatsink and no fan. It was built for a server that
forces air through its fins, so on a desk or in a normal case it overheats unless you add that airflow yourself or fit a
water block. This page is the short version. The detail lives on the pages listed at the end.

== Before you power a card on ==
* {{Status|Warning}} Never run the card without forced airflow, not even at idle. An idle card draws about 40 W and with no fan it reaches 95 C quickly; at 95 C it falls off the bus and turns off. {{Source|handle=analyticeth|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557491900934791409}} {{Source|handle=nikhilr1696|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557492862344630364}} One card on passive cooling stopped showing in <code><nowiki>nvidia-smi</nowiki></code> at 85 C while idle {{Source|handle=programmerboi|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560492431768813611}}; another clocked out in under 5 minutes with no cooling. {{Source|handle=programmerboi|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1563704621388529725}} See [[Thermal limits]].
* The power input is one EPS12V socket (the CPU 8-pin, 4x 12 V and 4x ground), not a PCIe 8-pin. Feed it with one EPS cable, or with both inputs of the bundled 2x PCIe 8-pin adapter on two separate PSU cables. Never use pigtails or one cable for both inputs. See [[Power supplies and cabling]] and [[Power and cabling warnings]].
* Watch the memory (HBM) temperature, not only the core. HBM is usually the hottest sensor under load. ([https://github.com/cachenetics/170tune/blob/main/docs/power-cap-curve.md power-cap notes]) {{Source|handle=rh3dai|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1556287917775655053|repo=https://github.com/cachenetics/170tune|note=MIT license}}

== What airflow it needs ==
The fins are dense and the heatsink is long, so the fan has to push air through a restriction. What matters is static
pressure and a sealed path, not open-air flow.
* Air has to go through the fins, from the end of the card out through the slot bracket. Gaps where air can leak around the card cost you most of the effect. Taping over gridded slot brackets in a 2U server took 10 C off one card at 250 W. {{Source|handle=mlx4|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562008624908214304}}
* Push-pull (a fan on each end of the card) helps a lot and lets you run fans slower. {{Source|handle=wakeupmbrc1|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560656839547424841}}
* Airflow needed rises steeply with power. A rough model by @zorg33 put a 250 W cap at 2 to 3 times the airflow of 200 W. {{Status|Theory}} {{Source|handle=zorg33|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562110134271090689}}
* The room matters too. The lab's eight-card server put about 2 kW into the room; raising its fan wall from 10 % to 25 % did not cool the hottest cards (they stayed at 84 to 85 C) while the inlet air rose from 24 C to 26 C. {{Status|Reported}} {{Source|handle=darkmaniac7|date=2026-10-27|note=lab notes}}. See [[Chassis builds]].

== Cooling options, cheapest to best ==
{| class="wikitable"
! Option !! Rough cost !! Noise !! What people measured !! More
|-
| One 120 mm or 80 mm fan per pair of cards, taped or clipped to the card ends, no duct || one fan per two cards || low to medium || under 63 C at a 185 W cap with Supermicro FAN-0074L4 80 mm fans {{Source|handle=c133|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1558160764370690100}} || [[Fans and ducts]]
|-
| 3D-printed intake plenum with 120 mm server fans (Arctic S12038-4K), push or push-pull || filament plus two fans per four cards || medium || 300 W per card at 3,500 rpm with HBM at 72 C in a 24 C room, push-pull {{Source|handle=wakeupmbrc1|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560655488331546715}} || [[Fans and ducts]]
|-
| Printed housing with a blower per card (9733 or 8025 blower) || one blower per card || loud at full speed || 60 C at a 200 W cap with the blower at 50 to 60 % {{Source|handle=68x0|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560301937675599944}} || [[Fans and ducts]]
|-
| Server chassis with its own fan wall || a used GPU server || loud; the BMC fan curve follows GPU temperature || see [[Chassis builds]] || [[Chassis builds]]
|-
| Dual-card AIO water cooler (two blocks, one radiator) || about $250 to $400 per two cards before shipping (October 2026) {{Source|handle=_arcanum_|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1556176261703925861}} {{Source|handle=artistosu|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1556178792190320735}} || quiet || 4 cards "cool and quiet" {{Source|handle=civiloid|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560654690897629264}} || [[Water cooling]]
|-
| Full-cover water block on a custom loop || about $140 to $220 per block plus the loop {{Source|handle=peter643|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1545982693903306813/1562011865465487431}} {{Source|handle=_syn_thetic_|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1545982693903306813/1563734136701722645}} || quiet || 50 C max at 250 W full load {{Source|handle=leenodie|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1545982693903306813/1564340979065163910}} || [[Water cooling]]
|}

== Power facts ==
* Stock power limit is 250 W on the common 8 GB VBIOS (92.00.67.00.01); some 8 GB cards ship with a 300 W VBIOS (92.00.6D.00.0A). Both share the board part 900-11001-0108-000. {{Source|handle=c133|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562161732137386127|repo=https://github.com/PixelML/club-170hx|note=Apache-2.0 license}}
* Most people serve at a cap between 140 W and 200 W. A four-card GLM-5.3-Flash TP4 sweep found 140 W only about 1 % slower than 150 W for 8 % less power {{Source|repo=https://github.com/PixelML/club-170hx}}; 175 W is the knee in the 170tune single-card curve {{Source|repo=https://github.com/cachenetics/170tune}}. See [[Undervolting and power limits]].
* Short spikes go above the cap: up to 380 W on cards capped at 250 W. {{Source|handle=n2dcrypt|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556771516803321877}} Size PSUs for that.
* Idle draw is 30 to 40 W per card stock; patched idle settings reach 23 to 26 W. See [[P-states and idle power]].
* Undervolting (shifting the V/F curve) cut power 24 % at a fixed 1,350 MHz on the 170tune reference card. It needs a VBIOS that exposes the VF offset; the 250 W 8 GB VBIOS and the 10 GB VBIOS do not. {{Source|repo=https://github.com/cachenetics/170tune}}

== Pages in this section ==
* [[Fans and ducts]]: fan models, measured temperatures, printable shrouds and ducts, fan control.
* [[Water cooling]]: blocks that fit, AIOs, installation, pads and paste.
* [[Undervolting and power limits]]: V/F offset, power caps, measured watts against tok/s.
* [[P-states and idle power]]: idle draw and how to lower it.
* [[Power supplies and cabling]]: the EPS input, cable rules, PSU sizing per card count.
* [[Thermal limits]]: core and HBM thresholds, throttling, what people run at.
* [[Chassis builds]]: multi-card builds, fan walls and power distribution.

== See also ==
[[Troubleshooting]] · [[Power and cabling warnings]] · [[Platforms]] · [[Recipes]] · [[Benchmarks]]

{{ImportFooter}}
[[Category:Cooling and power]]

[[Category:8 GB]]
[[Category:10 GB]]

Chassis builds

2026-10-31T21:34:25Z

ImportBot: Multi-card CMP 170HX builds: cases, servers, open frames, fan walls, power distribution, including the lab's eight-card server; from the cmpunlocker Discord (2026-10-04 to 10-27) and lab notes (2026-10-26 to 10-29); gap-fill from #general 2026-10-25 (custom-loop case plan), @siriusrhi

Two cards fit in most desktops with a shroud and a pair of fans. Past four cards the questions change: where the air
comes from and where it goes, how many circuits you have, and how loud the room can be. This page collects the builds
people posted, with their cooling and power. Photos were posted in the linked Discord messages; the descriptions
below are the posters' own words, since the images are not part of the import.

== The lab's eight-card server ==
{{Status|Reported}} Built by @darkmaniac7, notes from 2026-10-26 to 10-29. {{Source|handle=darkmaniac7|date=2026-10-27|note=lab notes}}
* '''Hardware.''' A 4U eight-GPU server with two CPUs and four cards per CPU in direct-attached slots; eight 8 GB cards unlocked to 64 GB with Gen2 x16 links. Power from the chassis's redundant server PSUs on a dedicated 240 V circuit behind a 3,000 VA UPS.
* '''Airflow.''' Two rear fans plus a fan wall of eight fans across the middle of the chassis, all on the BMC. In its automatic mode the BMC reads the GPU temperatures and drives the GPU zone to 100 % at about 80 C, which is very loud.
* '''Fan control.''' A script puts the BMC in manual (Full) mode and writes one duty to all four fan zones every 30 seconds: base 10 to 20 %, 40 % when the board reaches 60 C or a GPU 88 C, 100 % at 70 C board or 92 C GPU. Measured speeds: the rear fans floor at 1,260 rpm (10 % and 20 % give the same) and reach 3,640 rpm at full; the wall fans run 2,240 rpm at 10 %, 3,220 rpm at 20 % and 3,780 rpm at 25 %.
* '''Power governor.''' GPU heat is handled by the power cap, not the fans. Every 60 seconds a timer reads the chassis inlet temperature from the BMC and the GPU temperatures:
** inlet above 27 C or any GPU above 80 C: lower every card's cap by 10 W (floor 110 W);
** inlet below 24 C and every GPU below 72 C for three checks in a row: raise it by 10 W (ceiling 250 W).
** With caps at 250 W the box draws about 2.0 kW; the cards read 63 to 79 C in the first 20 seconds. In daily use the governor holds the caps between 180 and 230 W.
* '''What it showed.'''
** With only the two rear fans running at their floor, the governor walked the caps down from 250 W to 160 W (hottest GPU 81 C).
** Raising the wall from 10 % to 25 % did not cool the hottest cards: they stayed at 84 to 85 C while the governor cut from 240 to 200 W, and the inlet air climbed from 24 C to 26 C. About 2 kW was heating the room; the room, not the fan wall, was the limit.
** Slot position matters more than fan speed: at the same 180 W and 20 % fans, two of the four cards per CPU ran 81 to 84 C and the other two 58 to 68 C. Under a lighter 150 W load the split was the same (51 to 54 C against 40 to 43 C). Those hot slots are the ones to re-space.
** The fan wall was later unplugged until a fan-to-heatsink contact problem is fixed.
* '''Traps hit.'''
** {{Status|Reported}} BMC Full mode survives a power loss but the duty does not, so the next power-on ran every fan at 100 % (at night). Now the BMC rests in automatic mode, a shutdown hook hands the fans back before the OS goes down, and the power-restore policy keeps the box off after an AC loss. PixelML/club-170hx documents the same lesson on a Supermicro BMC. {{Source|handle=c133|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562161732137386127|repo=https://github.com/PixelML/club-170hx|note=Apache-2.0 license}}
** A fan below about 420 rpm makes the BMC flag a fault and hold 100 % until AC is removed, so the script never writes less than 10 %. On every boot the BMC flips the first manual write back to 100 % once; the 30-second re-check catches it. Fan header names changed after a re-plug, so never key a script on a header name.
** {{Status|Warning}} The boot and model NVMe sat on a PCIe-to-M.2 adapter with no airflow beside eight hot cards. During the heaviest sustained read it had seen (streaming about 189 GiB of model tables) the drive dropped off the bus and the box would not boot until it was reseated; the system journal was lost with the filesystem. With a fan and then a heatsink on the drive it peaked at 36 C at 250 MB/s, against 81 C at 450 MB/s before; model loads now wait for the drive to cool to 55 C and pause at 79 C. {{Source|handle=darkmaniac7|date=2026-10-29|note=lab notes}}
* Results on this box are on [[Recipes]] and [[Benchmarks]]; the power data is on [[Undervolting and power limits]].

== Servers ==
* {{Status|Reported}} '''Gigabyte G292-Z20''' (2U, single socket, eight GPU slots, about $500): "a steal for 8cmp setup" {{Source|handle=neapopa|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564039002724634717}}; units around $500 {{Source|handle=voidgiraffe|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560336120095580221}}. @cmdrwaka324 runs five CMP 170HX, two RTX 3090 and an Intel B60 in one: good BIOS and out-of-band management, an aggressive fan tune that still idles "like a big box fan at near full speed", and all cards stay cool even in a summer garage. Each GPU pair sits on its own PCIe switch, so P2P is fast within a pair and slower between pairs. {{Source|handle=cmdrwaka324|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564042507090788514}} @danske1: it handles eight cards in 2U, the stock fans are ear-piercing (fine for a warehouse), and you need EPS-to-EPS cables because adapters do not fit in the back section. {{Source|handle=danske1|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564151316819877921}} A fan-tuning script exists, but the floor is still about 3,750 to 4,000 rpm {{Source|handle=a1rm4x|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560284530244591637}} {{Source|handle=voidgiraffe|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560290311111057529}}. The 4U G482-Z52 is dual socket, so half the cards cross the socket to reach the others; check the system diagram. {{Source|handle=cmdrwaka324|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564123814940508274}} See [[Gigabyte G292-Z20]].
* {{Status|Reported}} '''Supermicro SYS-4028GR''': too loud even in a garage, and about 300 W with no load, mostly the fans. {{Source|handle=catchyuser|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1558163504878457046}} '''Supermicro 1028GQ-TRT''' (1U): nine FAN-0163L4 fans, about 85 dBA; its owner colocates it. {{Source|handle=programmerboi|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1558163867526242387}}
* {{Status|Reported}} '''2U Supermicro, one card at 250 W''': 3 A 80 mm fans were not enough until the gridded slot brackets were taped over (10 C cooler, stable); "it wants 3A min". {{Source|handle=mlx4|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562008624908214304}} Four such fans can draw 200 W. {{Source|handle=mlx4|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562008844039749803}}
* {{Status|Contested}} '''Four cards in a GPU server with empty slots''' (photo posted {{Source|handle=lamune6809|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1561949362031042580}}): fill every slot or print shrouds {{Source|handle=zorg33|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562156091595554999}}, or just seal the openings {{Source|handle=markshowa|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562177680009596973}}.
* A Gigabyte server "on idle its screaming but then on a 20-60% load quiet as can be" on 220 V. {{Source|handle=sojun80|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562275884314918934}}
* Fan control on servers: see [[Fans and ducts]]. A BMC cannot see a card on a passive riser. {{Source|handle=fafinet|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562300430439157850}}

== Cases ==
* {{Status|Reported}} '''FSP U500''' with a custom sliding plenum: @alanoo's two- and three-card builds, a dual-fan four-card plenum printing; cheap but well made; no display output used. Photos posted. {{Source|handle=alanoo|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1563578108513222707}} His four cards run at 200 W, at most 62 C in a garage. {{Source|handle=alanoo|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564379568801058877}}
* {{Status|Reported}} '''EK-Fluid Works V3000''': four cards on two dual-card AIOs with 480 mm radiators; a fifth card needs a case mod. {{Source|handle=globalapathy|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561377732435382384}} See [[Water cooling]].
* {{Status|Reported}} '''RM52 case''': dual 80 mm fans at the back and more right above the cards. {{Source|handle=ikyo|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558976989124370445}}
* {{Status|Reported}} '''Sandwiched cards''' with a shared intake: 34 to 42 C under load (photo posted). {{Source|handle=daveedcoles|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558681046336274482}} {{Source|handle=moliminous|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558686919033094145}}
* {{Status|Reported}} '''Dell T5810''' as a host: you need unusual cables just to power one CMP, the fan PWM controls are locked on Linux, and there is little room in front of the card. {{Source|handle=kellertreppe123|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557512606510489693}} Branded workstations lock you into their parts; swapping their PSUs can start fires. {{Source|handle=endsjeremy|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557500011212963873}}
* An AIO-cooled card in a desktop: riser cable, OCuLink from an M.2 slot, or the radiator outside the case. {{Source|handle=robbbbbb7973|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1561267848729591880}} {{Source|handle=globalapathy|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1561275681499783230}} {{Source|handle=boz._.|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1561341400308645929}}
* {{Status|Reported}} '''Three cards in an ATX "sleeper" case''' (@pekoraali, photos posted). Everything fits in a nearly standard ATX case with 8 expansion slots. Cooling: two Arctic P14 Pro in push-pull at 40 to 50 % (about 1,500 rpm each), the other case fans at 20 to 30 %; the exhaust P14 Pro sits on a piece of cardboard with cut-outs for the cards' exhaust vents, almost every gap is sealed with tape or foam, and unused case openings are foamed to stop recirculation. Cardboard is easy to cut to an unusual layout and a fine stopgap, but a printed shroud made for the case is the better answer. Power: 120 W cap, spikes to 130 to 160 W; two cards take 2x 8-pin PCIe into the bundled EPS adapter and the middle card a direct PSU-to-EPS cable that clicked in snugly, five 8-pin cables in all from a 1,300 W class PSU (similar to an NGDP 1300W). Result: 69 to 79 C under test load, fine for winter but not summer; he would like 140 to 150 W under 75 C. Noise is mostly air through the copper fins plus a high-pitched VRM chirp. One card had been serviced before (green liquid pads on the VRM) and two had dried paste; he left the paste alone after once knocking an SMD capacitor off a 5700 XT while removing a fused heatsink. He rates the build below average. {{Source|handle=pekoraali|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561605338183245887}}
* {{Status|Theory}} '''Mountain Mods Ascension with a custom loop''' (@siriusrhi's plan, nothing built yet): five cards at x16 with two x8 slots left for a 25GbE NIC, or six cards if one drops to Gen2 x8; the case holds two 360 mm radiators plus a 480 mm one, and two PSUs. He chose a loop over ready-made liquid-cooled cards because those need one AIO and 240 mm radiator per card (see [[Water cooling#All-in-one coolers]]). {{Source|handle=siriusrhi|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563807579086258258}} {{Source|handle=siriusrhi|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563807759034613791}} His question whether standard A100 blocks fit is answered on [[Water cooling#Blocks that fit]]. {{Source|handle=siriusrhi|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563805542428844073}}

== Open frames and racks ==
* Mining frames: @endsjeremy likes the [https://miningeek.com/ miningeek] open frames; one Chinese maker sells them under many names, so custom parts and bulk orders are possible. {{Source|handle=endsjeremy|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557988892920250469}} With two to six cards the usual chassis plan falls apart; a double-layer open frame is an option. {{Source|handle=ob88594|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557986953360576514}}
* [https://www.amazon.com/gp/aw/d/B08Y8N7FD1 2020 aluminium extrusion] with a 3D printer and M2/M3 screws. {{Source|handle=mountains1605|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562314226461057057}}
* A $25 [https://www.amazon.com/dp/B0DRJSSKN7 AL03 open-air ATX test bench] (not stackable; about $35 for a stackable one). {{Source|handle=globalapathy|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562322041825271841}}
* A test bench at the bottom of an AWAVE mining rack with risers up to the cards, going into a high-airflow noise box for about 10 dB less. {{Source|handle=impactic|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562971730186731591}}
* Two [https://www.aliexpress.us/item/3256803608464989.html AliExpress mining frames] {{Source|handle=con3po7016|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562511459832041492}}; an [https://www.ebay.com/itm/147104007949 eBay server rack], "surprisingly effective" {{Source|handle=_syn_thetic_|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1563736590914814073}}; a 12-GPU rack like [https://www.ebay.com/itm/126425695240 this eBay listing], found locally for $20 {{Source|handle=gnasherrr|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1563736969274593451}}.
* A small printed plate (<code><nowiki>frontplateminimal.stl</nowiki></code>) ties the backs of four cards into one block when the fronts share an intake shroud; see [[Fans and ducts]]. {{Source|handle=mountains1605|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558876438629715970}}

== Larger builds ==
* {{Status|Reported}} '''Twelve cards''' on a few dedicated circuits with an air conditioner pointed at them: still the warmest and loudest room in the house (photos posted). {{Source|handle=gpmickey|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561664734179364944}} @gpmickey added three 115 V 20 A breakers for them. {{Source|handle=gpmickey|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562196542574690395}}
* {{Status|Reported}} '''Octominer X12 Ultra''': @segmond runs twelve cards with only the cards in the case (motherboard and the rest outside); the case holds, powers and cools the cards, the stock fans are moved outside and a script sets them from GPU temperature, no extra fans needed. @reala7096 put motherboard, PSUs and cards all in the same case with only the rear fans and the CPU radiator outside, and printed a pull-fan front shroud for it (see [[Fans and ducts]]). @cibernox asked for printed front shrouds that add pull fans. {{Source|handle=cibernox|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560299591319031983}} {{Source|handle=reala7096|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560301909078843402}} {{Source|handle=segmond|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560404041782263948}} See also [[Octominer X12 Ultra builds]].
* {{Status|Reported}} '''Eight cards with printed push and pull plenums''' (@neapopa). Before the plenums, three push and three pull Delta server fans at 100 % held 175 W with the hottest card at 70 C and the rest at 60 C. The plenums (STL files on [[Fans and ducts]]) slot tightly onto the stack with no air leakage; the rear one needs the slot brackets removed. A temperature screenshot after 20 minutes of load on stock paste was posted. Fans: Delta AFB1212SHE in front and Bitmain L3+ fans for exhaust, six fans drawing 11 to 12 A; "works great as a white noise machine". Power: HP 1,200 W 94 % efficient server PSUs with custom soldered cables, four cards per PSU. {{Source|handle=neapopa|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562902214878568450}}
* {{Status|Reported}} '''Eight cards''' with eight 80 mm fans in push-pull, "very quiet". {{Source|handle=con3po7016|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1557608012397547551}}
* {{Status|Reported}} '''Eight water-cooled cards''' in single-slot blocks, a first PC build. {{Source|handle=djpandaman|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1557822968921456653}}
* {{Status|Reported}} '''Eight cards for the full GLM-5.3''' at 200 W each "using a cardboard box fan shroud and duct-tape". {{Source|handle=1a2b3c0967|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1557622760476250116}}
* {{Status|Reported}} '''Five cards on a 5-GPU PCIe switch board''' with slim printed housings, 33 to 37 C. {{Source|handle=moliminous|date=2026-10-10|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558530004852412577}} Five cards on an external GPU switch baseboard next to six RTX 3090s needed a 180 W cap to stop PCIe drops on large prompts. {{Source|handle=moliminous|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1561749293717659774}}
* {{Status|Reported}} '''Four cards on a 5-slot PCIe switch''' with the middle slot empty, one P12 Pro per pair. {{Source|handle=cibernox|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557506106509631579}}
* {{Status|Reported}} '''18 or more cards''' on a ground-cooled liquid loop at 230 W that heats the house. {{Source|handle=rh3dai|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559918625056366683}}

== Air in and out of the room ==
* An insulated intake box with two 100 mm hoses was not enough: the rig needs 3 to 5 times that air, so it now sits open to cold outdoor air. {{Source|handle=finishtilt14|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560224383761391696}}
* {{Status|Theory}} Put the loud fan elsewhere: an inline duct fan exhausting the box from outside the room. {{Source|handle=roboalchemist.|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564155936510189638}} {{Source|handle=endsjeremy|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564206258792304643}}
* Basements and garages are where most of the loud builds live. {{Source|handle=catchyuser|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1558163504878457046}} {{Source|handle=civiloid|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560655014370877481}}

== Power distribution ==
Plan circuits before cards: see [[Power supplies and cabling]] for PSU sizing per card count, 240 V circuits, surge
protection and UPS limits, and [[Power and cabling warnings]] for what has burned.

== See also ==
[[Cooling and power]] · [[Fans and ducts]] · [[Water cooling]] · [[Thermal limits]] · [[Platforms]] · [[Recipes]] ·
[[Benchmarks]] · [[Troubleshooting]]

{{ImportFooter}}
[[Category:Cooling and power]]

[[Category:8 GB]]
[[Category:10 GB]]

Benchmarks

2026-10-31T21:34:25Z

ImportBot: Import: Every tok/s number collected by the recipes lane, with setup and source (Discord, recipe repos, lab notes); gap-fill from #general 2026-10-22 to 10-26: clpeak peaks @djpandaman, rows @ob88594, @c133, @con3po7016, @segmond, @feralzi

Every throughput number the recipes lane found, one row per measurement, with the setup it was measured on and its
source. Click a column header to sort. The recipe pages give the full conditions; this table is for comparing.

'''Read before comparing.''' Numbers differ by protocol and setup:
* Most recipe authors use the MiaAI-Lab protocol (400-token answers, temperature 0, thinking off) and report three columns, '''structured / code / prose'''. The lab bench uses 1,024-token answers and lists '''code / structured / prose'''; rows say which order applies when it differs.
* "1 user" is single-stream decode in tok/s. "Many users" is aggregate tok/s across all streams, with the user count in brackets.
* Prefill is prompt-reading tok/s; cold unless marked warm. Prompt length is in brackets where known.
* Power caps (140 to 250 W), link width (Gen2 x4 or x16), P2P and the host CPU all move the numbers. Speculative decoding (DFlash2, DSpark, MTP) is on in most rows; temperature-0 benchmarks inflate draft acceptance against real use.
* The lab rows are on its own 8-card box and are marked "lab notes". All other rows are one person's report unless the recipe page shows a confirmation.
* Card count is CMP 170HX 8 GB-variant cards unlocked to 64 GB unless stated.

{| class="wikitable sortable"
! Model !! Quant !! Engine / recipe !! Cards !! Layout and links !! Power !! Workload !! 1 user (tok/s) !! Many users (tok/s) !! Prefill (tok/s) !! Source
|-
| GLM 5.3 Flash || W4A16 || [[GLM 5.3 Flash on 4x 8 GB]] 1.8.0 || 4 || TP4, x16, P2P || 180 W || MiaAI-Lab 400 tok || 482.6 / 442.1 / 232.1 || 943.7 / 835.0 / 667.2 (8) || 3,161 || {{Source|handle=ob88594|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556898939234558013|repo=https://github.com/Morrowmake/glm53-flash-cmp170hx-recipe}}
|-
| GLM 5.3 Flash || W4A16 || [[GLM 5.3 Flash on 4x 8 GB]] 1.8.0 || 4 || PP4, x16 || 180 W || MiaAI-Lab 400 tok || 232.4 / 209.9 / 100.1 || 664.1 / 608.8 / 469.2 (8) || 7,419 || {{Source|handle=ob88594|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556898939234558013|repo=https://github.com/Morrowmake/glm53-flash-cmp170hx-recipe}}
|-
| GLM 5.3 Flash || W4A16 || [[GLM 5.3 Flash on 4x 8 GB]] || 4 || TP4, x16, P2P || || real workflows || 350+ bursts, 270+ real || about 800 (agents) || || {{Source|handle=cibernox|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1559515598797672479}}
|-
| GLM 5.3 Flash || W4A16 || [[GLM 5.3 Flash on 4x 8 GB]] || 4 || TP4 || || bs=1 || 317 code, 164 prose || || || {{Source|handle=turbine|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1564557999463202917}}
|-
| GLM 5.3 Flash || W4A16 || [[GLM 5.3 Flash on 4x 8 GB]] || 4 || PP4, Gen2 x4 || || 1M context || 90 to 140 || || about 3,000 || {{Source|handle=mountains1605|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556410859117482025}}
|-
| GLM 5.3 Flash || W4A16 || [[GLM 5.3 Flash on 4x 8 GB]] || 4 || PP4, Gen2 x4 || || real agent work || || 340 (8) || || {{Source|handle=mountains1605|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1557598774887710792}}
|-
| GLM 5.3 Flash || W4A16 || [[GLM 5.3 Flash on 4x 8 GB]] early release || 4 || || || 768 tok, mixed, reasoning counted || 182.1 / 161.8 / 141.2 || 231.0 (2), 307.5 (4), 296.1 (8) || || {{Source|handle=ikyo|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556906534926028921}}
|-
| GLM 5.3 Flash || W4A16 || [[GLM 5.3 Flash on 4x 8 GB]] 1.7 || 4 || PP4 || || c=3, 1M ctx || 75+ prose (per stream) || || || {{Source|handle=1a2b3c0967|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556144621451747412}}
|-
| GLM 5.3 Flash || W4A16 || [[GLM 5.3 Flash on 4x 8 GB]] (recipe not named) || 4 || P2P on || 180 W cap || single concurrency || 200 to 400 || || || {{Source|handle=peter643|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562011301243523115}}
|-
| GLM 5.3 Flash || W4A16 || [[GLM 5.3 Flash on 4x 8 GB]] 1.6.0 || 4 || TP4, PLX, P2P off || 180 W || MiaAI-Lab || 396.0 structured || 798.6 (8) || || {{Source|handle=c133|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562161732137386127|repo=https://github.com/PixelML/club-170hx}}
|-
| GLM 5.3 Flash || W4A16 || [[GLM 5.3 Flash on 4x 8 GB]] 1.6.0, HBM equalised || 4 || TP4, PLX, P2P off || 150 W || MiaAI-Lab || 418.0 structured || 816.5 (8) || || {{Source|handle=c133|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562161732137386127|repo=https://github.com/PixelML/club-170hx}}
|-
| GLM 5.3 Flash || W4A16 abliterated || [[GLM 5.3 Flash on 4x 8 GB]] 1.8.0 engine || 4 || TP4, x16, NCCL only || governor 170 to 230 W || 1,024 tok, effort low || 252 / 235 / 139 (code / struct / prose) || 623 / 617 / 421 (8) || 1,700 (17k) || {{Source|handle=darkmaniac7|date=2026-10-28|note=lab notes}}
|-
| GLM 5.3 Flash || W4A16 abliterated || [[GLM 5.3 Flash on 4x 8 GB]] 1.8.0 engine || 4 || TP2 x PP2 || || 1,024 tok || 171 / 146 / 98 (code / struct / prose) || 567 / 503 / 383 (8) || 4,200 (17k) || {{Source|handle=darkmaniac7|date=2026-10-28|note=lab notes}}
|-
| GLM 5.3 Flash || W4A16 abliterated || [[GLM 5.3 Flash on 4x 8 GB]] 1.8.0 engine || 4 || TP1 x PP4 || || 1,024 tok || 113 / 121 / 71 (code / struct / prose) || 499 / 515 / 376 (8) || 6,800 (17k) || {{Source|handle=darkmaniac7|date=2026-10-28|note=lab notes}}
|-
| GLM 5.3 Flash || W4A16 abliterated || Morrowmake engine || 8 || TP8 || 250 W || 1,024 tok || 95 / 105 / 56 (code / struct / prose) || 440 (8) || 554 || {{Source|handle=darkmaniac7|date=2026-10-27|note=lab notes}}
|-
| GLM 5.3 Flash || W4A16 || two instances of [[GLM 5.3 Flash on 4x 8 GB]] 1.6 || 8 || 2x PP4 or 2x TP4 || 180 to 200 W || aggregate || || about 1,600 || || {{Source|handle=impactic|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1561913182132375593}}
|-
| GLM 5.3 Flash || W4A16 || 4 cards || 4 || TP4 || || || 130 || || || {{Source|handle=turbine|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1557123766063071255}}
|-
| GLM 5.3 Flash || EXL3 3.05 bpw || [[GLM 5.3 Flash on 2x 8 GB (ExLlamaV3 TP2)]] || 2 || TP2, NCCL P2P, x16 || 180 W || single request || 96.71 / 107.67 / 47.83; counting 129.38 || 67.25 (2) || 1,512 to 1,533 || {{Source|handle=nestaa51|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1559307749429354510|repo=https://github.com/alexvnesta/glm53-flash-cmp170hx-tp}}
|-
| GLM 5.3 Flash || EXL3 3.05 bpw || [[GLM 5.3 Flash on 2x 8 GB (ExLlamaV3 layer split)]] || 2 || layer split || || easy / hard text || 96.2 / 34.2 || || || {{Source|handle=nestaa51|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1559307749429354510|repo=https://github.com/alexvnesta/glm53-flash-cmp170hx-tp}}
|-
| GLM 5.3 Flash || EXL3 3.05 bpw || [[GLM 5.3 Flash on 2x 8 GB (ExLlamaV3 layer split)]] || 2 || layer split, no DFlash || || || about 60 || || || {{Source|handle=68x0|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1562167480275836939}}
|-
| GLM 5.3 Flash || EXL3 3.05 bpw || Flun repo scaled to 3 cards || 3 || TP || || full context || about 60 || || || {{Source|handle=wingrimez_40467|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1562166545856077926}}
|-
| GLM 5.3 Flash || Maya-M GGUF || [[GLM 5.3 Flash on 2x 8 GB (Project Maya)]] v1.0.6 || 2 || Gen2 x4 || || maya.sh --bench || 61.3 || || 514 || {{Source|handle=pcsv.|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563923997970796645|repo=https://github.com/mw00/project-maya}}
|-
| GLM 5.3 Flash || Maya-S GGUF, 128K || [[GLM 5.3 Flash on 2x 8 GB (Project Maya)]] v1.1.15 || 2 (listed as 40 GB) || Gen2 x16 || || maya.sh --bench || 54.3 || || 831 || {{Source|handle=pcsv.|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563923997970796645|repo=https://github.com/mw00/project-maya}}
|-
| GLM 5.3 Flash || Maya-S24 GGUF, 32K || Project Maya v1.1.8 || 1 || Gen2 x16 || || maya.sh --bench || 20.6 || || 797 || {{Source|handle=pcsv.|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563923997970796645|repo=https://github.com/mw00/project-maya}}
|-
| GLM 5.3 Flash || EXL3 4-bit || ExLlamaV3, 2x CMP 64 GB + 40 GB card + RTX 3080 || 2 + 2 other || mixed || || 768k ctx, 16-bit KV || about 70 || || 3,500 to 3,600 (100k) || {{Source|handle=vektor_prime|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1560023669416402965}}
|-
| GLM 5.3 (full) || Int4-Int8Mix || [[GLM 5.3 on 8x 8 GB (vllm-170hx-glm5)]] || 10 || PP10 || 170 W || MAX_SEQS 8 || 48.7 || 108.4 (4), 174.1 (8) || 1,833; 2,351 aggregate (8) || {{Source|handle=reala7096|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1557544812972871813|repo=https://github.com/arvkmr/vllm-170hx-glm5}}
|-
| GLM 5.3 (full) || Int4-Int8Mix || [[GLM 5.3 on 8x 8 GB (Int4-Int8Mix PP8)]] || 8 || PP8, MTP 5 || 200 W || || about 25 (about 10 at high context) || || || {{Source|handle=1a2b3c0967|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1557521014685180006}}
|-
| GLM 5.3 (full) || W4A16 || own setup (not published) || 8 || || || || 64 code, 59 to 60 reasoning, 49 prose || || 1,250 to 2,000 || {{Source|handle=impactic|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563055165878050897}}
|-
| GLM 5.3 (full) || || own setup || 4 || || || || 32 || || || {{Source|handle=mountains1605|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1561915195155021998}}
|-
| GLM 5.3 (full) || EXL3 3.05 bpw || ExLlamaV3, 4x CMP + RTX PRO 6000 || 4 + 1 other || PP || || || 30 || || || {{Source|handle=mountains1605|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1559063237775990795}}
|-
| GLM 5.3 (full, 753B) || NVFP4 experts + INT8 (abliterated requant) || wtdcode/vllm-backport with the PP hand-off fix || 8 || TP2 x PP4, P2P, MTP || 110 to 130 W governor || 1,024 tok || 77 / 76 / 48 (code / struct / prose) || 172 / 189 / 146 (8) || 1,650 (17k) || {{Source|handle=darkmaniac7|date=2026-10-28|note=lab notes}}
|-
| DeepSeek V4.1 Flash || EXL3 2.9 experts + FP8 || [[DeepSeek V4.1 Flash on 4x 8 GB (Morrowmake)]] 1.0.0 || 4 || TP4, x16, P2P, Engram RAM || 180 W || MiaAI-Lab, up to || 319 / 287 / 162 || 765 / 729 / 432 (8) || 3,818 (2K), 3,808 (32K) || {{Source|handle=lia_oc|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563528168688586764|repo=https://github.com/Morrowmake/dsv41-flash-cmp170hx-recipe}}
|-
| DeepSeek V4.1 Flash || EXL3 2.9 experts + FP8 || [[DeepSeek V4.1 Flash on 4x 8 GB (Morrowmake)]] 1.0.0 || 4 || TP4, P2P off, PLX || 140 W || Curtis protocol || 122.8 / 90.3 / 62.4 (count / code / prose) || 168.7 (8) || 1,558.7 (128K) || {{Source|handle=anon33anon|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561910289799184445|repo=https://github.com/CurtisAccelerate/DeepSeekv41-Flash-1017-EXL3-CMP170HX}}
|-
| DeepSeek V4.1 Flash heretic || EXL3 2.9 experts + FP8 + heretic patch || [[DeepSeek V4.1 Flash heretic on 4x 8 GB]] || 4 || TP4, Engram SSD, miner co-resident || || own bench || 136 / 158 / 121 || 261 / 323 / 249 (8) || 2,453 (17k warm) || {{Source|handle=darkmaniac7|date=2026-10-29|note=lab notes}}
|-
| DeepSeek V4.1 Flash || EXL3 experts + FP8 || [[DeepSeek V4.1 Flash on 4x 8 GB (GNmac)]] 1.0.0 || 4 || TP4, x16 || 180 W || MiaAI-Lab || 296 / 212 / 150 || 796 / 477 / 359 (8) || 1,759 || {{Source|handle=greencandle9753|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562465339395280909}}
|-
| DeepSeek V4.1 Flash || EXL3 experts + FP8 || [[DeepSeek V4.1 Flash on 4x 8 GB (GNmac)]] 1.1.0 || 4 || TP4, x16 || 180 W || MiaAI-Lab || 336 / 247 / 180 || || 1,764 || {{Source|handle=greencandle9753|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563066699840884806}}
|-
| DeepSeek V4.1 Flash || EXL3 experts + FP8 || [[DeepSeek V4.1 Flash on 4x 8 GB (GNmac)]] 1.2.0 || 4 || TP4, x16, P2P || 180 W || MiaAI-Lab || 356 / 258 / 184 || 868 / 544 / 441 (8) || 2,416 || {{Source|handle=greencandle9753|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562465339395280909|repo=https://github.com/GNmac-lab/deepseek-v41-flash-1017-cmp170hx}}
|-
| DeepSeek V4.1 Flash || EXL3 experts + FP8 || [[DeepSeek V4.1 Flash on 4x 8 GB (GNmac)]] 1.2.0 || 4 || PP4 || 180 W || MiaAI-Lab || 118 / 91 / 63 || 341 / 214 / 163 (8) || 2,311 || {{Source|handle=greencandle9753|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562465339395280909|repo=https://github.com/GNmac-lab/deepseek-v41-flash-1017-cmp170hx}}
|-
| DeepSeek V4.1 Flash || EXL3 experts + FP8 || [[DeepSeek V4.1 Flash on 4x 8 GB (GNmac)]] || 4 || TP4, x16, P2P || || 1,024 tok || 212 / 244 / 136 || 425 / 522 / 346 (8) || 2,000 to 2,600 || {{Source|handle=darkmaniac7|date=2026-10-28|note=lab notes}}
|-
| DeepSeek V4.1 Flash || EXL3 experts + FP8 || [[DeepSeek V4.1 Flash on 4x 8 GB (GNmac)]] (localairecipes listing) || 4 || TP4 + P2P, Gen2 x4 || || || about 10% below GLM 5.3 Flash || || || {{Source|handle=mountains1605|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562982101157150771}}
|-
| DeepSeek V4.1 Flash || all-3-bit EXL3 experts + FP8 || [[DeepSeek V4.1 Flash on 4x 8 GB (alanoo fidelity build)]], DSpark off || 4 || TP4, x16, P2P || 200 W || MiaAI-Lab || 105.4 / 105.0 / 104.8 || 559.7 / 482.4 / 449.2 (8) || 2,514 || {{Source|handle=alanoo|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1564681525365186711|repo=https://github.com/alanoo81/deepseek-v41-flash-4x-cmp170hx}}
|-
| DeepSeek V4.1 Flash || all-3-bit EXL3 experts + FP8 || [[DeepSeek V4.1 Flash on 4x 8 GB (alanoo fidelity build)]], DSpark 5 || 4 || TP4, x16, P2P || 200 W || MiaAI-Lab || 369.8 / 267.3 / 200.1 || || || {{Source|handle=alanoo|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1564681525365186711|repo=https://github.com/alanoo81/deepseek-v41-flash-4x-cmp170hx}}
|-
| DeepSeek V4.1 Flash || EXL3 2.9 experts + FP8/FP4 || [[DeepSeek V4.1 Flash on 4x 8 GB (CurtisAccelerate TC-MoE)]] 2026-10-22 || 4 || TP4, P2P off || 140 W || Curtis protocol || 187.2 / 144.2 / 101.2 (count / code / prose) || 271.6 (8, standardized suite) || 1,523 (2K), 1,330 (131K) || {{Source|handle=anon33anon|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561910289799184445|repo=https://github.com/CurtisAccelerate/DeepSeekv41-Flash-1017-EXL3-CMP170HX}}
|-
| DeepSeek V4.1 Flash || EXL3 3.5 bpw || [[DeepSeek V4.1 Flash on 4x 8 GB plus RTX PRO 6000 (ExLlamaV3 TP5)]] || 4 + 1 other || TP5, native backend || 150 W (CMP) || C coding, mean of 9 || 99.9 || 34.4 per stream (2) || 2,116 (26K), 1,645 (1M) || {{Source|handle=anon33anon|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561903682608697426|repo=https://github.com/anoane/09-deepseek-v41-flash-1017-exl3-tp5-1m}}
|-
| DeepSeek V4.1 Flash || official MXFP8 / MXFP4 || [[DeepSeek V4.1 Flash on 6x 8 GB (TP6)]] || 6 || TP6, x16 || || effort max, end to end incl. reasoning || 78.55 code, 76.56 writing || || || {{Source|handle=dale063629|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561547352693538856|repo=https://github.com/wgkbfcp/deepseek-v4.1-flash-1017-cmp170hx-recipe}}
|-
| DeepSeek V4.1 Flash || official || [[DeepSeek V4.1 Flash on 6x 8 GB (Deepinfer-SM80 TP2 x PP3)]] || 6 || TP2 x PP3 || || 1 stream code || 160.8 || || 4,037 (16K), 4,507 (64K) || {{Source|handle=reala7096|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562151531690860657|repo=https://github.com/HalfVulpes/Deepinfer-SM80}}
|-
| DeepSeek V4.1 Flash || official FP4 || own setup || 6 || TP2 + PP3, x4 || || code, 1 user || 144.4 || || 1,970 cold, 1,987 (131K) || {{Source|handle=reala7096|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562917910165323808}}
|-
| DeepSeek V4.1 Flash || EXL3 3.5 bpw || own setup || 6 || TP2 + PP3, x4 || || code, 1 user || 123.4 || || 1,695 cold, 1,647 (131K) || {{Source|handle=reala7096|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562917910165323808}}
|-
| DeepSeek V4.1 Flash || native quant || own setup || 6 || PP6, x4 || || || about 67 || || || {{Source|handle=deejay9983|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562929048248909906}}
|-
| DeepSeek V4.1 Flash || not stated || own setup || 6 || || || prose, c=1 || 157 || || || {{Source|handle=con3po7016|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562304093228245125}}
|-
| DeepSeek V4.1 Flash || official || [[DeepSeek V4.1 Flash on 8x 8 GB (Deepinfer-SM80 TP4 x PP2)]] || 8 || TP4 x PP2 || || C=1 code || 153.35 || 620.22 (12) || about 3,463; 2,759.9 at 649K || {{Source|handle=reala7096|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562151531690860657|repo=https://github.com/HalfVulpes/Deepinfer-SM80}}
|-
| DeepSeek V4.1 Flash || official FP8 || Deepinfer-SM80 vLLM || 8 || PP8, no P2P || || 256k ctx || 74 then about 80 || || 6,000 (zero cache hit) || {{Source|handle=segmond|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562224597221249146}}
|-
| DeepSeek V4.1 Flash || official FP4 || own setup || 8 || TP2 x PP4, x4 || || code, 1 user || 135 to 139 || || 2,520 to 2,690 cold; 2,708 to 2,730 (131K) || {{Source|handle=reala7096|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562917910165323808}}
|-
| DeepSeek V4.1 Flash || EXL3 3.5 bpw || own setup || 8 || TP2 x PP4, x4 || || code, 1 user || 117.1 || || 2,025 to 2,126 || {{Source|handle=reala7096|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562917910165323808}}
|-
| DeepSeek V4.1 Flash || official MXFP4 / MXFP8 || [[DeepSeek V4.1 Flash on 8x 8 GB (Zanooda PP8)]] || 8 || PP8, mostly x4 || 180 W || 128k ctx || 117 || 560 (8), 806 to 813 (16) || 4,486 (26K), 6,066 (105K) || {{Source|handle=gnasherrr|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560998024136753172|repo=https://github.com/Zanooda/deepseek-v4.1-flash-cmp170hx}}
|-
| DeepSeek V4.1 Flash || official MXFP4 / MXFP8 || [[DeepSeek V4.1 Flash on 8x 8 GB (Zanooda PP8)]] || 8 || PP8, x16, P2P, Engram disk || 180 W || 1,024 tok || 64 / 46 / 32 (code / struct / prose) || 546 / 316 / 285 (8) || 5,478 (17k) || {{Source|handle=darkmaniac7|date=2026-10-27|note=lab notes}}
|-
| DeepSeek V4.1 Flash || Maya GGUF || [[DeepSeek V4.1 Flash on 2x 8 GB (Project Maya)]] || 2 || || || README figure || about 63 || || 500 to 550 (68x) || {{Source|handle=pcsv.|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563924151662678087}}
|-
| Qwen3.8 Flash Next || AutoRound 2/3-bit + FP8 table || [[Qwen3.8 Flash Next on 1x 8 GB (ElectroHobo 3 bpw)]] || 1 || x16 || 180 W || MiaAI-Lab || 197.8 / 296.4 / 135.5 || 799.5 / 791.3 / 586.4 (8); 1,384 (48) || 4,243 || {{Source|handle=nathang6866|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563591773228507138|repo=https://github.com/ElectroHobo/qwen38-flash-next-3bpw-1x-cmp170hx-recipe}}
|-
| Qwen3.8 Flash Next || AutoRound 3 bpw + MTP || [[Qwen3.8 Flash Next on 1x 8 GB (iIIusi0n SSD PLE)]] || 1 || PLE on SATA SSD || 180 W || 128 tok, temp 0 || 110.99 || 277 (4), 429 (8), 667 (16) || 2,636 (8K) || {{Source|handle=c133|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1557934564024909965|repo=https://github.com/iIIusi0n/qwen3.8-flash-next-cmp170hx}}
|-
| Qwen3.8 Flash Next || AutoRound 3 bpw + MTP || [[Qwen3.8 Flash Next on 1x 8 GB (iIIusi0n SSD PLE)]], tuned || 1 || || 200 W, NDIV 67, +250 || || || || 5,000+ || {{Source|handle=dottoreargus|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1557303145204293694}}
|-
| Qwen3.8 Flash Next || AutoRound 3 bpw + MTP || [[Qwen3.8 Flash Next on 1x 8 GB (iIIusi0n SSD PLE)]] || 1 || MTP 3, 2,048 chunk || || || || || 3,500 || {{Source|handle=tekkenz|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1557139178284777554}}
|-
| Qwen3.8 Flash Next || EXL3 5.05 bpw || ExLlamaV3, one card || 1 || || || || 69 to 82 || || about 1,000 || {{Source|handle=tekkenz|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1557128719422853223}}
|-
| Qwen3.8 Flash Next || 4.27 bpw GGUF || llama.cpp, MTP || 1 || || || || 60 (ceiling) || || || {{Source|handle=tokukarin|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564443422314602559}}
|-
| Qwen3.8 Flash Next || Unsloth QD-4K_XL, FP16 KV || Strata || 1 || || || || 60+ || || || {{Source|handle=acedogblast|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1556834517103157331}}
|-
| Qwen3.8 Flash Next || IQ2 || Strata, quad-channel DDR4 || 1 || no x16 mod || || || about 90 || || 1,600 || {{Source|handle=xtj7|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560350518847479850}}
|-
| Qwen3.8 Flash Next || IQ3_S || Strata (modified build), 10 GB card at 40 GB || 1 || x16 || || || 110+ (stock build under 100) || || || {{Source|handle=exile_1ck|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557256690255134751}}
|-
| Qwen3.8 Flash Next || UD-Q3_K_XL || single-kernel decode engine vs llama.cpp || 1 || || || || 70.6 vs 53.4 || || || {{Source|handle=c133|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562161732137386127|repo=https://github.com/PixelML/club-170hx}}
|-
| Qwen3.8 Flash Next || W4A16 Merlin + FP8 table || [[Qwen3.8 Flash Next on 2x 8 GB (ElectroHobo W4A16 TP2)]] 0.2.0 || 2 || TP2, x16, P2P || 180 W || MiaAI-Lab || 241.2 / 349.7 / 198.4 || 894.5 / 986.8 / 769.7 (8); 1,937 (128) || 4,696 || {{Source|handle=nathang6866|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563590746710478919|repo=https://github.com/ElectroHobo/qwen38-flash-next-w4a16-2x-cmp170hx-recipe}}
|-
| Qwen3.8 Flash Next || W4A16 Merlin || [[Qwen3.8 Flash Next on 2x 8 GB (ElectroHobo W4A16 TP2)]] 0.1.0 || 2 || TP2 || || || 253 / 349 / 203 || 842 / 992 / 727 (8) || || {{Source|handle=nathang6866|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1561924044666839091}}
|-
| Qwen3.8 Flash Next || W4A16 Merlin || [[Qwen3.8 Flash Next on 2x 8 GB (ElectroHobo W4A16 TP2)]] update || 2 || TP2 || || max concurrency || || 1,814 (128) || || {{Source|handle=nathang6866|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563590746710478919}}
|-
| Qwen3.8 Flash Next || W4A16 Merlin || [[Qwen3.8 Flash Next on 2x 8 GB (ElectroHobo W4A16 TP2)]] 0.2.0 || 2 || TP2, x16, P2P || || 1,024 tok || 263 / 266 / 215 (code / struct / prose) || 916 / 961 / 729 (8) || 4,600 (17k) || {{Source|handle=darkmaniac7|date=2026-10-28|note=lab notes}}
|-
| Qwen3.8 Flash Next || W4A16 Merlin || four instances of [[Qwen3.8 Flash Next on 2x 8 GB (ElectroHobo W4A16 TP2)]] || 8 || 4x TP2 || || 1,024 tok || || 3,617 / 3,316 / 2,664 (32, code / struct / prose) || 17,400 total || {{Source|handle=darkmaniac7|date=2026-10-28|note=lab notes}}
|-
| Qwen3.8 Flash Next || EXL3 5.05 bpw || [[Qwen3.8 Flash Next on 2x 8 GB (Morrowmake EXL3)]] || 2 || TP2 || || MiaAI-Lab || 152.8 / 152.6 / 118.3 || 588.2 / 674.7 / 489.9 (8) || 2,651 || {{Source|handle=nathang6866|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563590746710478919|repo=https://github.com/ElectroHobo/qwen38-flash-next-w4a16-2x-cmp170hx-recipe}}
|-
| Qwen3.8 Flash Next || EXL3 5.05 bpw || [[Qwen3.8 Flash Next on 2x 8 GB (Morrowmake EXL3)]] on a Broadwell host || 2 || TP2 || || || 55 to 70 || || || {{Source|handle=nathang6866|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563590746710478919|repo=https://github.com/ElectroHobo/qwen38-flash-next-w4a16-2x-cmp170hx-recipe}}
|-
| Qwen3.8 Flash Next || AWQ g32 uncensored, INT4 table on SSD || [[Qwen3.8 Flash Next on 2x 8 GB (mannydelrio PP2)]] || 2 || PP2, x4, no P2P || 180 W || MiaAI-Lab || 192.4 / 177.8 / 145.4 || 986.4 / 734.2 / 619.6 (8) || 7,006 || {{Source|handle=mrmannyatx|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1557099855242072094|repo=https://github.com/mannydelrio/qwen38-flash-next-2x-cmp170hx}}
|-
| Qwen3.8 Flash Next || Intel W4A16, table on NVMe || AlexBrandes/cmp170hx-qwen38-flash-next || 2 || PP2, x4 || || MiaAI-Lab || 250.8 / 226.2 / 157.4 || 999.5 / 840.4 / 566.8 (8) || 6,300 to 7,100 || {{Source|handle=nathang6866|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563590746710478919|repo=https://github.com/ElectroHobo/qwen38-flash-next-w4a16-2x-cmp170hx-recipe}}
|-
| Qwen3.8 Flash Next || W4A16 INT4-PLE || [[Qwen3.8 Flash Next on 2x 8 GB (DUFRelic PP2)]] || 2 || PP2, MTP 3, 74 SMs || 140 W || llama-benchy pp16384 tg2048 || 133.39 || 245.17 (4) || 6,213.66 (C1), 6,639.25 (C4) || {{Source|handle=dufrelic|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1556592394517094460|repo=https://github.com/DUFRelic/qwen38-flash-next-recipe}}
|-
| Qwen3.8 Flash Next || W4A16 || own setup, PP || 2 || PP2 || || || about 120 || about double (4) || || {{Source|handle=dufrelic|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1557460484830138469}}
|-
| Qwen3.8 Flash Next || INT4-mixed AutoRound || Plean's setup || 2 || PP2, MTP || || || || about 100 each (2), about 80 each (3 to 4) || || {{Source|handle=plean.|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1557459833928556697}}
|-
| Qwen3.8 Flash Next || AWQ INT4 || [[Qwen3.8 Flash Next on 2x 8 GB (vektorprime PP2)]] || 2 || PP2, MTP k=1 || || || 75.4 to 75.8 (58.1 to 58.6 without MTP) || || || {{Source|handle=vektor_prime|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1557443747892035674|repo=https://github.com/vektorprime/qwen38-flash-next-pp2}}
|-
| Qwen3.8 Flash Next || W4A16 AutoRound, BF16 table on NVMe || [[Qwen3.8 Flash Next on 3x 8 GB (clee PP3)]] || 3 || PP3, x4, no P2P || || cold, temp 0 || 74.4 (1K), 72.9 (1M) || || 4,831 (64K), 4,748 (1M) || {{Source|handle=c133|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1556357466026025001|repo=https://github.com/clee/qwen3.8-flash-next-3x170hx}}
|-
| Qwen3.8 Flash Next || uncensored variant || [[Qwen3.8 Flash Next on 3x 8 GB (clee PP3)]] || 3 / 2 || PP, MTP 1 || || agentic || about 90 (3 cards), 100 to 110 (2 cards) || || || {{Source|handle=68x0|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1557910994322333746}}
|-
| Qwen3.8 Flash Next || || own setup || 3 || || || || 110+ || || || {{Source|handle=trustinter|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1556510298477830305}}
|-
| Qwen3.8 27B || W4A16 || [[Qwen3.8 27B on 1x 8 GB (W4A16 vLLM)]] || 1 || || || 262k ctx || about 170 (60 to 70 near long ctx) || || || {{Source|handle=kellertreppe123|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556696293655576633}}
|-
| Qwen3.8 27B || || own setup || 1 || || || || about 100 || || about 3,700 || {{Source|handle=chonsworth|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1556775994692731011}}
|-
| Qwen3.8 27B || W4A16 + drafter || || 1 || || || c=1, about 30k ctx || about 200 || || || {{Source|handle=wakeupmbrc1|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559918550213201962}}
|-
| Qwen3.8 27B || DFlash || || 1 || || || code, 16k / 200k ctx || 210+ / 110+ || || || {{Source|handle=wakeupmbrc1|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1556196939240841259}}
|-
| Qwen3.8 27B || FP8 + DSpark || sglang || 1 || || || HLE / MMLU / GSM8K || || 200 to 400, avg about 300 (4) || || {{Source|handle=reggie7756|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1556256686904447080}}
|-
| Qwen3.8 27B || FP8 || sglang || 1 || || || single stream || 60 to 80, spikes 125 || || || {{Source|handle=c133|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1560616484349153341}}
|-
| Qwen3.8 27B || INT4 Swift || || 1 || 131k ctx, c=3 || || || about 55 || 200+ (7 sub-agents) || || {{Source|handle=globalapathy|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556691664029097985}}
|-
| Qwen3.8 27B || W8A8 INT8 || vLLM + MTP || 1 || c=2 || || || 30 to 40 || || || {{Source|handle=amishrakefightr|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556692979605835789}}
|-
| Qwen3.8 27B || INT kernels || vLLM, DFlash, temp 0 || 1 || || || || 225 || || || {{Source|handle=feralzi|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559796537935142963}}
|-
| Qwen3.8 27B || W4A16 AutoRound + DFlash2 k=7 || vLLM || 1 || || 180 W || || 136.38 to 140.3 || || || {{Source|handle=c133|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562161732137386127|repo=https://github.com/PixelML/club-170hx}}
|-
| Qwen3.8 27B || Q8 || llama.cpp || 1 || no x16 mod || || || || || about 800 || {{Source|handle=programmer_007|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560252510193590395}}
|-
| Qwen3.8 27B || 4-bit || own TP4 code (not released) || 4 || TP4 || 190 W || with speculation || 440 || || about 4,000 (2,200 without his all-reduce compression) || {{Source|handle=turbine|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1556907874385662175}}
|-
| MiMo V2.6 Flash || NVFP4 || [[MiMo V2.6 Flash on 4x 8 GB]] || 4 || TP4, x16, P2P || 180 W || MiaAI-Lab || 322.0 / 274.9 / 170.1 || 753.8 / 738.0 / 555.5 (8) || 2,722 || {{Source|handle=nathang6866|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1561264547455569952|repo=https://github.com/ElectroHobo/mimo-v26-flash-cmp170hx-recipe}}
|-
| MiMo V2.6 Flash || NVFP4 || [[MiMo V2.6 Flash on 4x 8 GB]], P2P off || 4 || TP4 || 180 W || MiaAI-Lab || 181.3 / 164.4 / 96.8 || 426.1 / 388.9 / 254.3 (8) || || {{Source|handle=nathang6866|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1561264547455569952|repo=https://github.com/ElectroHobo/mimo-v26-flash-cmp170hx-recipe}}
|-
| Step 5 || || own setup || 6 || || || prose || almost 100 || || || {{Source|handle=con3po7016|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1561026955111829556}}
|-
| Qwen 3.6 (comparison, not CMP) || 5-bit || llama.cpp on 2x V100 || 2 V100 || || || || 88 || || || {{Source|handle=xanthefin|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561337005105746011}}
|-
| GLM 5.3 Flash || W4A16 (canada-quant) || [[GLM 5.3 Flash on 4x 8 GB]] 1.8.0, ESXi VM || 4 || TP4, Gen2 x8, no P2P, 74 SMs || 180 W || MiaAI-Lab || 361 / 284 / 199 || 697 / 587 / 529 (8) || 1,633-1,753 (32k) || {{Source|handle=darkmaniac7|date=2026-10-19|note=lab notes}}
|-
| GLM 5.3 Flash || W4A16 (canada-quant) || [[GLM 5.3 Flash on 4x 8 GB]] 1.8.0, ESXi VM || 4 || PP4, Gen2 x8, no P2P, 74 SMs || 180 W || MiaAI-Lab || 201 / 149 / 97 || 664 / 548 / 477 (8) || 6,834-6,977 (32k) || {{Source|handle=darkmaniac7|date=2026-10-19|note=lab notes}}
|-
| GLM 5.3 Flash || W4A16 (canada-quant) || [[GLM 5.3 Flash on 4x 8 GB]] 1.8.0, no drafter || 4 || TP4 / PP4, Gen2 x8 || 180 W || MiaAI-Lab || 101 (TP4), 48 (PP4) || 470 / 419 / 422 (8, TP4) || || {{Source|handle=darkmaniac7|date=2026-10-19|note=lab notes}}
|-
| GLM 5.3 Flash || W4A16 abliterated (own requant) || [[GLM 5.3 Flash on 4x 8 GB]] 1.8.0 engine || 4 || TP4, Gen2 x8 || 180 W || MiaAI-Lab || 349 / 254 / 181 || || || {{Source|handle=darkmaniac7|date=2026-10-19|note=lab notes}}
|-
| GLM 5.3 Flash || W4A16 abliterated || Morrowmake engine, 2 CMP + 2 RTX PRO 6000 || 2 + 2 other || PP2 x TP2, CMPs stage 0 || 180 W (CMP) || MiaAI-Lab || 349 / 261 / 180 || 895 / 703 / 611 (8) || 5,495 (32k) || {{Source|handle=darkmaniac7|date=2026-10-19|note=lab notes}}
|-
| GLM 5.3 Flash || W4A16 || Morrowmake engine, 4 CMP + 2 RTX PRO 6000 || 4 + 2 other || PP3 x TP2 || 180 W (CMP) || code / JSON / prose || 224-235 code, 101-110 prose || 553 / 484 / 425 (8) || || {{Source|handle=darkmaniac7|date=2026-10-19|note=lab notes}}
|-
| GLM 5.3 Flash || AWQ W4A16 || PixelML club recipe of record (older stack) || 4 || PP4 (14,12,12,7), MTP k=3 || || c=1 || 87.6 || || || {{Source|handle=c133|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562161732137386127|repo=https://github.com/PixelML/club-170hx}}
|-
| DeepSeek V4.1 Flash || official MXFP4 / MXFP8 || [[DeepSeek V4.1 Flash on 8x 8 GB (Zanooda PP8)]], Engram on NVMe || 8 || PP8 || || 105k prompt || || || 4,455-4,930 || {{Source|handle=gnasherrr|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560998024136753172}}
|-
| GLM 5.3 (full) || || own setup, after a week of tuning || not stated (reply in an 8-card thread) || || || || 60 code / reasoning, 50 prose || || || {{Source|handle=impactic|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1559060750356717669}}
|-
| DeepSeek V4.1 Flash (1017) || not stated || own setup || 6 (posted as "6x single streams": six cards or six streams, not clear) || || || single stream || 80 to 100 || || about 5,000 || {{Source|handle=ob88594|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563649833594650828}}
|-
| Qwen3.8 Flash Next || not stated || own setup (not stated) || not stated || || || c=1 || 75 || || 3,000+ || {{Source|handle=c133|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563650307781562369}}
|-
| MiniMax M3.1 || not stated || own setup || 4 (GPU types not stated) || || || c=1 || 76 || || || {{Source|handle=con3po7016|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563943584120709192}}
|-
| MiniMax M3.1 || not stated || own setup || 6 (GPU types not stated) || || || c=1 || 30 || || || {{Source|handle=segmond|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563943781034885143}}
|-
| Nanbeige4.3-33B || Q6_K GGUF (dealignai uncensored) || not stated || 1 (10 GB card at 40 GB) || || || about 200K context, still tuning || 27 (40 posted earlier as "optimized") || || || {{Source|handle=feralzi|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564051736979701845}} {{Source|handle=feralzi|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564092405026660406}} {{Source|handle=feralzi|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564114097694445662}}
|}

== Compute and memory peaks ==
{{Status|Reported}} {{Cards|10 GB}} @djpandaman (mrpandagod) ran <code><nowiki>clpeak --cuda</nowiki></code> on an unlocked 10 GB card
that reports sm_80, 122 SMs and 40,483 MB of VRAM (CUDA driver 13.3, toolkit 12.0). He believes the card ran at stock
power settings but had not double-checked. He finds clpeak a better view of what the card can do than OpenCL-benchmark.
{| class="wikitable"
! Test !! Result
|-
| FP32 (vector) || 21.9 TFLOPS
|-
| FP16 (vector, half / half2) || 43.7 / 43.8 TFLOPS
|-
| FP64 (vector) || 11.0 TFLOPS
|-
| FP16 x FP16 + FP32 and BF16 x BF16 + FP32 (vector) || 21.9 TFLOPS each
|-
| INT32 (IMAD) || 21.9 TOPS
|-
| INT8 dot product (dp4a) || 87.3 to 87.5 TOPS
|-
| Tensor cores (WMMA / mma.sync) || FP16 312 TFLOPS (331 with FP16 accumulate), BF16 312, TF32 156, FP64 21.4 TFLOPS; INT8 605 TOPS (607 at k32), INT4 647 TOPS
|-
| cuBLASLt GEMM peak || FP16 302, BF16 308, TF32 146, FP32 21.6, FP64 21.9 TFLOPS; INT8 424 TOPS
|-
| Global memory bandwidth (float / float2 / float4) || 1.68 / 1.74 / 1.82 TB/s
|-
| Local memory bandwidth (float / float2 / float4) || 10.7 / 17.1 / 18.3 TB/s
|-
| Image memory bandwidth (float4) || 1.64 TB/s
|-
| Pinned host transfers || 12.3 GB/s host to device, 13.2 GB/s device to host
|-
| Kernel launch round trip || 6.79 us
|}
{{Source|handle=djpandaman|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563170579643760770}} {{Source|handle=djpandaman|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563221594401407107}}
More on this card variant: [[10 GB card]] and [[Full SM unlock]].

== Not in the table ==
* Image and video generation (minutes per clip): see [[Recipes#Other workloads]].
* Mining hash rates (TH/s): see [[Cooling and power]] and [[Tools]].
* Kernel microbenchmarks (Deepinfer-SM80, ExLlamaV3 GEMM): see [[Engines]].
* Long write-ups with numbers that wait for their authors (Plean, matstatman, Feralzi): see [[Recipes]].

== Related ==
[[Recipes]] · [[Engines]] · [[Quantization on the 170HX]] · [[Tools]] · [[Cooling and power]]

{{ImportFooter}}
[[Category:Recipes]]

Flashing the 300 W VBIOS

2026-10-31T21:20:15Z

Most 8 GB cards ship with VBIOS 92.00.67.00.01, the 250 W image. On it the driver reports a GPC and memory VF-offset
range of [0 .. +0], so no undervolt can be applied, whatever a tool says it set. The factory 300 W image
92.00.6D.00.0A, which NVIDIA shipped on the same board part number (900-11001-0108-000), exposes an offset range of
[-1000 .. +1000], boots the HBM at 1728 MHz instead of 1458 MHz, raises the SM ceiling from 1410 to 1695 MHz, and
keeps a 250 W default cap (300 W is the maximum it allows). This page is the flash procedure as run on eight cards in
one night, with the numbers before and after. It does not touch the memory or compute unlock, which stays in the
driver; see [[Driver unlock]].

The 10 GB card has no 300 W image (its only VBIOS is 92.00.66.00.02); this page is for 8 GB cards. See
[[VBIOS and firmware]] for the full image inventory.

== Why flash it ==
=== The 250 W image has no undervolt lever ===
<code><nowiki>nvml_oc -i N</nowiki></code> (the helper 170tune uses) reports <code><nowiki>allowed range : [0 .. +0] MHz</nowiki></code>
for both the GPC and the memory VF offset on every 92.00.67.00.01 card. An offset call can return success and the
driver still drops it; only a readback proves it applied. On the same cards after the flash the range reads
[-1000 .. +1000].

{{Status|Proven}} {{Cards|8 GB}} 
{{Source|handle=mrpec|date=2026-08-01|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1533150703328039085}} 
{{Source|handle=unmotivatedgene|date=2026-08-23|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1541201873803943997}} 
{{Source|handle=darkmaniac7|date=2026-10-31|note=lab notes}}

=== Same board, same IDs ===
Both images carry device 10DE:20C2, subsystem 10DE:1585 and board ID 0x030A, and both have been read off cards with
board part number 900-11001-0108-000 and die 20C2-105-A1. nvflash accepts the 300 W image on a 250 W card without any
override because the IDs match; it is a signed NVIDIA image, not a modified one.

{{Status|Reported}} {{Cards|8 GB}} 
{{Source|handle=con3po7016|date=2026-08-23|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1541194940997046322}} 
{{Source|handle=wakeupmbrc1|date=2026-08-30|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1543658140875235459}}

== Before you start ==
# '''An 8 GB card on 92.00.67.00.01.''' Read it with <code><nowiki>nvidia-smi --query-gpu=index,pci.bus_id,vbios_version --format=csv</nowiki></code>. A card already on 92.00.6D.00.0A has nothing to gain.
# '''nvflash 5.867 for Linux''', the <code><nowiki>x64/nvflash</nowiki></code> binary from the TechPowerUp download (the zip holds x86, x64, aarch64 and ppc64 builds; the Windows zip is a different download).
# '''The ROM''', TechPowerUp VBIOS database entry 268495 (listed there as "CMP 170HX 0 MB"; the size column is wrong). Verify it before it goes near a card: see below. A copy is attached to this page.
# '''A rollback ROM.''' Save one card's 92.00.67.00.01 image with <code><nowiki>nvflash -i N --save</nowiki></code> before you write anything. The static part of the image is identical across cards of the same version, so one dump serves as the rollback for all of them.
# '''A way to power the machine off and on''' that does not depend on the GPUs: a BMC, or someone at the button. The procedure needs two cold cycles, and a wedged flash controller only clears on a cold cycle.
# '''The driver unloaded, or never loaded.''' nvflash refuses to write with the NVIDIA kernel module present. The method below boots without it, which also avoids the unbind hang described further down.

== Verify the ROM ==
The TechPowerUp file matched these values exactly:
{| class="wikitable"
! Field !! Value
|-
| Version || 92.00.6D.00.0A
|-
| Build / modification date || 06/16/21 / 04/07/22
|-
| Size || 1,044,480 bytes
|-
| Device / subsystem / board ID || 0x20C2 / 0x1585 / 0x030A
|-
| MD5 || a58aae86e72b13d50603c15653350664
|-
| SHA1 || efad37d514bb94ac345719a0c56d9cd147cddfb7
|-
| SHA256 || 789e8f8d4c70dc9eb114c9fdcef6ed2d00aedf15a1eca522519de02042818723
|}
Two checks that do not depend on a hash:
* <code><nowiki>nvflash --version 300w.rom</nowiki></code> reads the header from the file only (it does not touch a card) and must print the version, device, subsystem and board IDs above, and <code><nowiki>License Placeholder : Present</nowiki></code>.
* <code><nowiki>python3 check_rom.py 300w.rom --expect 300W</nowiki></code> (attached) checks the structural markers: the NVGI header, the 300 W power bytes <code><nowiki>E0 93 04</nowiki></code> at 0x46045, the strap tier byte 0x44 at 0x41F53 (0x66 there means a forged "64 GB" ROM that bricks the card at boot), an all-zero license region at 0xFE504, and the dual-bank mirror. The same script recognises the 250 W image (<code><nowiki>--expect 250W</nowiki></code>) for checking your rollback dump.

{{Status|Reported}} {{Cards|8 GB}} 
{{Source|repo=https://github.com/polyuij42-del/cmp170hx-vbios-flash}} 
{{Source|repo=https://github.com/Consensus-Protocol/cmp170hx}}

== The procedure (driverless boot) ==
Proven on eight cards in two rounds, 2026-10-31, on a bare-metal Ubuntu box with the cmpunlocker driver build 615.71.09,
BMC power control and the tooling attached below. Every write took about 10 seconds. Read the two rules first:

* '''One nvflash operation per card per boot.''' After a power-on, the first nvflash command that touches a card's flash controller (<code><nowiki>--check</nowiki></code>, <code><nowiki>--save</nowiki></code> or a write) works; a second one on the same card fails with <code><nowiki>Falcon In HALT or STOP state</nowiki></code> or <code><nowiki>Detecting GPU failed</nowiki></code> and nothing is written. So the rollback save comes from a card you are not writing in that boot (or from an earlier boot), and the write is the first and only thing you do to each target card. A PCIe remove and rescan of one device (<code><nowiki>echo 1 > /sys/bus/pci/devices/0000:XX:00.0/remove; echo 1 > /sys/bus/pci/rescan</nowiki></code>) re-opened the window once in the lab; do not count on it.
* '''nvflash 5.867 ignores <code><nowiki>-y</nowiki></code> and refuses piped input.''' The confirm prompt needs a real terminal. It prints the card's current and replacement version strings before the prompt, and the PCI bus only in its Results table after the operation, so the attached controller confirms on the version strings (current must be 92.00.67.00.01, replacement 92.00.6D.00.0A) and checks the bus afterwards. nvflash's <code><nowiki>-i</nowiki></code> index follows PCI bus order, the same order <code><nowiki>nvidia-smi</nowiki></code> uses with <code><nowiki>CUDA_DEVICE_ORDER=PCI_BUS_ID</nowiki></code>; the Results table confirmed <code><nowiki>-i 7</nowiki></code> = bus C2 on the lab box.

Steps:
# Stop everything that holds the GPUs (engines, miners), until <code><nowiki>lsof /dev/nvidia*</nowiki></code> shows nothing. Record every card's VBIOS version.
# Keep the driver out of the next boot: <code><nowiki>/etc/modprobe.d/zz-flash-window.conf</nowiki></code> with <code><nowiki>install nvidia /bin/false</nowiki></code> (and the same for nvidia_modeset, nvidia_drm, nvidia_uvm). Mask or disable the units that would start GPU work at boot (docker, miners, any model loader). Note what you changed.
# Cold cycle: power off, 30 seconds dark, power on. Confirm <code><nowiki>lsmod | grep nvidia</nowiki></code> is empty and that the cards are enumerated with no driver bound.
# Save the rollback ROM from a card you will not write this boot: <code><nowiki>nvflash -i N --save backup.rom</nowiki></code>, then <code><nowiki>check_rom.py backup.rom --expect 250W</nowiki></code>.
# Write each target card once: <code><nowiki>nvflash -i N 300w.rom</nowiki></code>, answer <code><nowiki>y</nowiki></code> at the prompt (or let the attached controller do it). Success looks like a progress bar to 100 %, two verification reads, and <code><nowiki>A reboot is required for the update to take effect.</nowiki></code> with exit code 0. Anything else: do not retry that card this boot.
# Remove the blacklist, restore the units, cold cycle again.
# Verify: <code><nowiki>nvidia-smi --query-gpu=index,vbios_version,memory.total,clocks.max.memory,power.default_limit,power.max_limit --format=csv</nowiki></code> should show 92.00.6D.00.0A, your unlocked memory size, 1728 MHz, 250 W default and 300 W maximum; <code><nowiki>nvml_oc -i N</nowiki></code> should show the [-1000 .. +1000] range.

The attached <code><nowiki>window.sh</nowiki></code> runs those phases (<code><nowiki>check</nowiki></code>, <code><nowiki>prep</nowiki></code>, <code><nowiki>flash</nowiki></code>, <code><nowiki>restore</nowiki></code>, <code><nowiki>verify</nowiki></code>) with the lab box's unit names and bus map; edit those before using it elsewhere.

{{Status|Proven}} {{Cards|8 GB}} 
{{Source|handle=darkmaniac7|date=2026-10-31|note=lab notes}} 
{{Source|repo=https://github.com/polyuij42-del/cmp170hx-vbios-flash}}

=== Why not unbind the driver instead ===
The repository above spent eighteen script versions on the unbind route. With any process still holding
<code><nowiki>/dev/nvidia*</nowiki></code>, <code><nowiki>echo ... > /sys/bus/pci/drivers/nvidia/unbind</nowiki></code> hangs in the driver's remove path and never
returns; on one of its two cards it hung even with zero handles open, and a <code><nowiki>reboot</nowiki></code> issued in that state stalled the
machine until someone cut the power. Booting with the modules blacklisted sidesteps all of it.

{{Status|Warning}} {{Cards|8 GB}} 
{{Source|repo=https://github.com/polyuij42-del/cmp170hx-vbios-flash}}

=== Others who flashed it with nvflash ===
Several owners did the same flash with stock nvflash before the lab did, on Linux and on Windows; none reported a
brick from it. The bricks reported on the server came from fuse burns, SPI strap edits and A100 cross-flashes, not from
this image.

{{Status|Reported}} {{Cards|8 GB}} 
{{Source|handle=c133|date=2026-08-23|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1541187172588326962}} 
{{Source|handle=c133|date=2026-08-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1542649519739769003}} 
{{Source|handle=shirogeek|date=2026-09-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1546191972392501369}} 
{{Source|handle=derick2k|date=2026-09-06|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1546163237186441286}} 
{{Source|handle=phoenixone7|date=2026-09-16|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1549930400707514490}} 
{{Source|handle=wakeupmbrc1|date=2026-08-30|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1543658182298173581}}

== Results on eight cards ==
Two of the eight (bus 41 and C1) have FBPA0 fused off (one dead HBM stack each). Both took the image and initialised
cleanly at 1728 MHz; the driver log after the flash matched the log before it line for line in shape (the unlock's
privilege-mask loop prints 54 "Booter failed" lines per card on every boot; that is normal, not damage).

{| class="wikitable"
! Card (bus) !! VBIOS after !! Memory !! Max mem clock !! Default / max cap !! Offset range !! Note
|-
| 0 (01) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 ||
|-
| 1 (22) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 ||
|-
| 2 (41) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 || FBPA0 fused
|-
| 3 (61) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 ||
|-
| 4 (81) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 ||
|-
| 5 (A1) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 ||
|-
| 6 (C1) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 || FBPA0 fused
|-
| 7 (C2) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 || first attempt aborted by the controller, window re-opened by a PCIe rescan, second write fine
|}
Zero Xids, zero ECC errors, zero RmInitAdapter failures across four cold cycles.

{{Status|Proven}} {{Cards|8 GB}} 
{{Source|handle=darkmaniac7|date=2026-10-31|note=lab notes}}

== What it changed ==
The load is a proof-of-work miner (pearlhash, OneZeroMiner) on all eight cards with the fan wall at 15 % and caps set
per card by a thermal governor (230 to 250 W). The rejected shares below were all "Stale share" (a share submitted after
the pool changed the job: timing, not a wrong answer); there were no invalid shares.

{| class="wikitable"
! State !! Total hashrate !! Core clock range !! Temps !! Notes
|-
| 250 W image, offset 0 || 1,455 TH/s || 1215 to 1290 MHz || 70 to 79 C || baseline, same caps
|-
| 300 W image, offset 0 || 1,459 to 1,470 TH/s || 1215 to 1290 MHz || 70 to 79 C || HBM 1728 MHz cost nothing on a compute load
|-
| 300 W image, GPC offset +100 || 1,525 TH/s || 1275 to 1365 MHz || unchanged || 20 min soak, 0 Xid
|-
| 300 W image, GPC offset +130 || 1,549 TH/s || 1290 to 1380 MHz || unchanged || 20 min soak, 0 Xid
|-
| 300 W image, GPC offset +160 || 1,564 TH/s || 1335 to 1410 MHz || unchanged || 20 min soak, 0 Xid
|-
| 300 W image, GPC offset +190 || 1,579 TH/s || 1335 to 1425 MHz || unchanged || 20 min soak, 0 Xid
|-
| 300 W image, GPC offset +220, six cards || 1,598 TH/s || 1350 to 1440 MHz || unchanged || 20 min soak, 0 Xid; two cards still parked by the false alarms
|-
| 300 W image, GPC offset +220, all eight || 1,631 TH/s || 1350 to 1440 MHz || unchanged || 09:57, after the two parked cards took +160/+190/+220 clean; +11.8 % over the morning baseline. Not a safe point: see the warning below
|}
Power draw stayed at the caps the whole time: the offset lets the core hold a higher clock at the same watts, so the
gain comes with no extra heat. Two cards were held back early by a stale share each (a rule that counted any rejected
share; it now counts only invalid ones); re-run from +160, both took every rung.

=== The miner does not qualify an offset for inference ===
{{Status|Warning}} {{Cards|8 GB}} 
One hour after all eight reached +220 with the miner clean, the lab ran its inference benchmark against GLM 5.3 Flash
(TP4) on cards 0 to 3. One minute in, card 0 (the hottest slot, 77 to 79 C under the miner) began flooding
<code><nowiki>Xid 48</nowiki></code> (uncorrectable ECC error in GPC3 GCC) and <code><nowiki>Xid 172</nowiki></code>
(uncorrectable SRAM error in GPC 3), 97,000 lines in five minutes, and the engine died. That is the same pair the
Discord reports for a too-deep offset. At the same time card 5, which only ever ran the miner, was found in "GPU
requires reset" with no Xid at all, about two hours into +220. Lowering the offset does not clear either state: card 0
recovered with <code><nowiki>nvidia-smi -r</nowiki></code>, card 5 needed a cold cycle. What this means:
* A 20-minute miner soak proves nothing about inference, and not much about a two-hour miner run either. Qualify each
card against the engine that will serve on it, with a benchmark as the workload rung, and soak for hours, not minutes.
* Hot-slot cards have the least margin.
* +220 is not a safe point on this box. The lab reverted every card to 0 and re-laddered with inference gating (next
section).

{{Source|handle=darkmaniac7|date=2026-10-31|note=lab notes}} 
{{Source|handle=ichundes|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1557350219111342183}}

=== Inference-gated ladder (second run) ===
{{Status|Reported}} {{Cards|8 GB}} 
Same eight cards after a cold cycle, inlet 17 to 18 C. Both groups of four ran in parallel, each serving its own engine
(GLM 5.3 Flash on cards 0 to 3, DeepSeek V4.1 Flash on cards 4 to 7). Each rung: a two-minute benchmark against that
group's engine (structured and code prompts, 1 and 4 streams, 512 tokens, any failed request is a fault), then one hour
under the miner with Xids attributed to the card the kernel names, then the same benchmark again. Rungs +100, +130,
+160 and +190: every card passed every rung, 0 Xid, 0 invalid shares, 0 failed requests. The lab then set all eight to
+160, one rung below the top clean rung, for a long soak; that is the point to start from, not +190.

{| class="wikitable"
! GPC offset !! Miner total (8 cards) !! Notes
|-
| 0 (stock) || 1,488 TH/s || same caps (230 to 250 W by temperature), same airflow
|-
| +130 || 1,578 TH/s ||
|-
| +160 || 1,604 TH/s || long-soak point
|-
| +190 || 1,625 TH/s || top clean rung; +220 faulted in the first run
|}

What it does for inference, measured as an A/B on the same engines with the same benchmark, stock against +160, at
512 and 1024 tokens (decode per stream at 1 stream / aggregate at 4 streams, tok/s):
{| class="wikitable"
! Prompt, tokens !! GLM stock !! GLM +160 !! Change !! DeepSeek stock !! DeepSeek +160 !! Change
|-
| structured, 512 || 260.9 / 510.7 || 270.2 / 524.4 || +3.6 % / +2.7 % || 141.4 / 227.4 || 150.9 / 247.7 || +6.7 % / +8.9 %
|-
| code, 512 || 243.4 / 499.2 || 252.2 / 512.3 || +3.6 % / +2.6 % || 189.8 / 278.3 || 201.8 / 295.1 || +6.3 % / +6.0 %
|-
| prose, 512 || 154.1 / 368.6 || 159.9 / 379.1 || +3.8 % / +2.8 % || 131.4 / 241.1 || 143.2 / 246.0 || +9.0 % / +2.0 %
|-
| structured, 1024 || 256.9 / 539.4 || 266.6 / 554.7 || +3.8 % / +2.8 % || 152.9 / 247.5 || 164.2 / 265.7 || +7.4 % / +7.4 %
|-
| code, 1024 || 274.6 / 548.7 || 284.5 / 564.8 || +3.6 % / +2.9 % || 176.7 / 297.8 || 190.3 / 337.5 || +7.7 % / +13.3 %
|-
| prose, 1024 || 150.9 / 357.5 || 156.6 / 368.2 || +3.8 % / +3.0 % || 135.8 / 234.8 || 145.6 / 251.9 || +7.2 % / +7.3 %
|}
GLM 5.3 Flash gains about 3 to 4 %; DeepSeek V4.1 Flash, which spends more of its time in compute, gains about 6 to 9 %.
Both at the same power cap and the same temperatures. One A/B run, stock first; every cell moved the same way.

{{Source|handle=darkmaniac7|date=2026-10-31|note=lab notes}}

{{Status|Proven}} {{Cards|8 GB}} 
{{Source|handle=darkmaniac7|date=2026-10-31|note=lab notes}}

== Risks and what the community saw ==
* {{Status|Warning}} One owner advised against the 300 W image because a photo of a burned 170HX had been posted earlier and the board lacks some power-delivery parts of the full layout. The photo is not in the exported history and no post ties a burned card to this image. The image's own default is 250 W; nothing on the lab box sets 300 W, and the undervolt reduces current at a given cap rather than raising it. Keep your cap at or below 250 W until you have a reason and the cooling to go higher. {{Source|handle=xanthefin|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561336153515364444}}
* {{Status|Contested}} HBM at 1728 MHz: one owner on the 300 W image with a 250 W limit passed GPU-burn with no errors but saw sporadic Vulkan memtest errors across the HBM dies; the eight lab cards (Hynix) ran clean. If a card misbehaves at 1728 MHz, 170tune can set the memory clock back down (not on FBPA0-fused cards, where the PLL tool must not write). {{Source|handle=cute_sc2|date=2026-08-08|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1535648815456198667}} {{Source|handle=darkmaniac7|date=2026-10-31|note=lab notes}}
* {{Status|Warning}} A failed flash is recoverable only with an SPI programmer with a 1.8 V adapter (the flash IC is 1.8 V; some "3.3 V" CH341A units put out 5 V, so a CH347 unit whose software selects the voltage is the safer buy). Power loss during the write and the wrong file are the two real ways to get there; both are yours to prevent. {{Source|repo=https://github.com/Consensus-Protocol/cmp170hx}}

== Rollback ==
The same procedure with your saved 92.00.67.00.01 dump as the image: one write per card in a driverless boot, then a
cold cycle. The lab keeps its dump with the rest of the evidence; any card's dump of the same version works for any
card of the same version.

== Files ==
* {{Download|file=CMP170HX_92.00.6D.00.0A.rom|compact=yes}} The 300 W image, byte-identical to TechPowerUp 268495 (hashes above).
* {{Download|file=Vbios_check_rom.py|compact=yes}} Structural ROM check (MIT, from polyuij42-del/cmp170hx-vbios-flash).
* {{Download|file=Vbios_flash_one.py|compact=yes}} The pty controller that answers nvflash's prompt only after it has echoed the expected versions, and checks the bus afterwards.
* {{Download|file=Vbios_window.sh.gz|compact=yes}} The lab's phase script (gzipped: the wiki refuses a shebang script under a plain extension) (check, prep, flash, restore, verify); unit names and bus map are the lab box's.

== Related ==
[[VBIOS and firmware]], [[Undervolting and power limits]], [[Driver unlock]], [[170tune]], [[Troubleshooting]].

{{ImportFooter}}
[[Category:Unlocks]]
[[Category:8 GB]]
[[Category:Cooling and power]]

Flashing the 300 W VBIOS

2026-10-31T15:13:47Z

Most 8 GB cards ship with VBIOS 92.00.67.00.01, the 250 W image. On it the driver reports a GPC and memory VF-offset
range of [0 .. +0], so no undervolt can be applied, whatever a tool says it set. The factory 300 W image
92.00.6D.00.0A, which NVIDIA shipped on the same board part number (900-11001-0108-000), exposes an offset range of
[-1000 .. +1000], boots the HBM at 1728 MHz instead of 1458 MHz, raises the SM ceiling from 1410 to 1695 MHz, and
keeps a 250 W default cap (300 W is the maximum it allows). This page is the flash procedure as run on eight cards in
one night, with the numbers before and after. It does not touch the memory or compute unlock, which stays in the
driver; see [[Driver unlock]].

The 10 GB card has no 300 W image (its only VBIOS is 92.00.66.00.02); this page is for 8 GB cards. See
[[VBIOS and firmware]] for the full image inventory.

== Why flash it ==
=== The 250 W image has no undervolt lever ===
<code><nowiki>nvml_oc -i N</nowiki></code> (the helper 170tune uses) reports <code><nowiki>allowed range : [0 .. +0] MHz</nowiki></code>
for both the GPC and the memory VF offset on every 92.00.67.00.01 card. An offset call can return success and the
driver still drops it; only a readback proves it applied. On the same cards after the flash the range reads
[-1000 .. +1000].

{{Status|Proven}} {{Cards|8 GB}} 
{{Source|handle=mrpec|date=2026-08-01|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1533150703328039085}} 
{{Source|handle=unmotivatedgene|date=2026-08-23|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1541201873803943997}} 
{{Source|handle=darkmaniac7|date=2026-10-31|note=lab notes}}

=== Same board, same IDs ===
Both images carry device 10DE:20C2, subsystem 10DE:1585 and board ID 0x030A, and both have been read off cards with
board part number 900-11001-0108-000 and die 20C2-105-A1. nvflash accepts the 300 W image on a 250 W card without any
override because the IDs match; it is a signed NVIDIA image, not a modified one.

{{Status|Reported}} {{Cards|8 GB}} 
{{Source|handle=con3po7016|date=2026-08-23|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1541194940997046322}} 
{{Source|handle=wakeupmbrc1|date=2026-08-30|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1543658140875235459}}

== Before you start ==
# '''An 8 GB card on 92.00.67.00.01.''' Read it with <code><nowiki>nvidia-smi --query-gpu=index,pci.bus_id,vbios_version --format=csv</nowiki></code>. A card already on 92.00.6D.00.0A has nothing to gain.
# '''nvflash 5.867 for Linux''', the <code><nowiki>x64/nvflash</nowiki></code> binary from the TechPowerUp download (the zip holds x86, x64, aarch64 and ppc64 builds; the Windows zip is a different download).
# '''The ROM''', TechPowerUp VBIOS database entry 268495 (listed there as "CMP 170HX 0 MB"; the size column is wrong). Verify it before it goes near a card: see below. A copy is attached to this page.
# '''A rollback ROM.''' Save one card's 92.00.67.00.01 image with <code><nowiki>nvflash -i N --save</nowiki></code> before you write anything. The static part of the image is identical across cards of the same version, so one dump serves as the rollback for all of them.
# '''A way to power the machine off and on''' that does not depend on the GPUs: a BMC, or someone at the button. The procedure needs two cold cycles, and a wedged flash controller only clears on a cold cycle.
# '''The driver unloaded, or never loaded.''' nvflash refuses to write with the NVIDIA kernel module present. The method below boots without it, which also avoids the unbind hang described further down.

== Verify the ROM ==
The TechPowerUp file matched these values exactly:
{| class="wikitable"
! Field !! Value
|-
| Version || 92.00.6D.00.0A
|-
| Build / modification date || 06/16/21 / 04/07/22
|-
| Size || 1,044,480 bytes
|-
| Device / subsystem / board ID || 0x20C2 / 0x1585 / 0x030A
|-
| MD5 || a58aae86e72b13d50603c15653350664
|-
| SHA1 || efad37d514bb94ac345719a0c56d9cd147cddfb7
|-
| SHA256 || 789e8f8d4c70dc9eb114c9fdcef6ed2d00aedf15a1eca522519de02042818723
|}
Two checks that do not depend on a hash:
* <code><nowiki>nvflash --version 300w.rom</nowiki></code> reads the header from the file only (it does not touch a card) and must print the version, device, subsystem and board IDs above, and <code><nowiki>License Placeholder : Present</nowiki></code>.
* <code><nowiki>python3 check_rom.py 300w.rom --expect 300W</nowiki></code> (attached) checks the structural markers: the NVGI header, the 300 W power bytes <code><nowiki>E0 93 04</nowiki></code> at 0x46045, the strap tier byte 0x44 at 0x41F53 (0x66 there means a forged "64 GB" ROM that bricks the card at boot), an all-zero license region at 0xFE504, and the dual-bank mirror. The same script recognises the 250 W image (<code><nowiki>--expect 250W</nowiki></code>) for checking your rollback dump.

{{Status|Reported}} {{Cards|8 GB}} 
{{Source|repo=https://github.com/polyuij42-del/cmp170hx-vbios-flash}} 
{{Source|repo=https://github.com/Consensus-Protocol/cmp170hx}}

== The procedure (driverless boot) ==
Proven on eight cards in two rounds, 2026-10-31, on a bare-metal Ubuntu box with the cmpunlocker driver build 615.71.09,
BMC power control and the tooling attached below. Every write took about 10 seconds. Read the two rules first:

* '''One nvflash operation per card per boot.''' After a power-on, the first nvflash command that touches a card's flash controller (<code><nowiki>--check</nowiki></code>, <code><nowiki>--save</nowiki></code> or a write) works; a second one on the same card fails with <code><nowiki>Falcon In HALT or STOP state</nowiki></code> or <code><nowiki>Detecting GPU failed</nowiki></code> and nothing is written. So the rollback save comes from a card you are not writing in that boot (or from an earlier boot), and the write is the first and only thing you do to each target card. A PCIe remove and rescan of one device (<code><nowiki>echo 1 > /sys/bus/pci/devices/0000:XX:00.0/remove; echo 1 > /sys/bus/pci/rescan</nowiki></code>) re-opened the window once in the lab; do not count on it.
* '''nvflash 5.867 ignores <code><nowiki>-y</nowiki></code> and refuses piped input.''' The confirm prompt needs a real terminal. It prints the card's current and replacement version strings before the prompt, and the PCI bus only in its Results table after the operation, so the attached controller confirms on the version strings (current must be 92.00.67.00.01, replacement 92.00.6D.00.0A) and checks the bus afterwards. nvflash's <code><nowiki>-i</nowiki></code> index follows PCI bus order, the same order <code><nowiki>nvidia-smi</nowiki></code> uses with <code><nowiki>CUDA_DEVICE_ORDER=PCI_BUS_ID</nowiki></code>; the Results table confirmed <code><nowiki>-i 7</nowiki></code> = bus C2 on the lab box.

Steps:
# Stop everything that holds the GPUs (engines, miners), until <code><nowiki>lsof /dev/nvidia*</nowiki></code> shows nothing. Record every card's VBIOS version.
# Keep the driver out of the next boot: <code><nowiki>/etc/modprobe.d/zz-flash-window.conf</nowiki></code> with <code><nowiki>install nvidia /bin/false</nowiki></code> (and the same for nvidia_modeset, nvidia_drm, nvidia_uvm). Mask or disable the units that would start GPU work at boot (docker, miners, any model loader). Note what you changed.
# Cold cycle: power off, 30 seconds dark, power on. Confirm <code><nowiki>lsmod | grep nvidia</nowiki></code> is empty and that the cards are enumerated with no driver bound.
# Save the rollback ROM from a card you will not write this boot: <code><nowiki>nvflash -i N --save backup.rom</nowiki></code>, then <code><nowiki>check_rom.py backup.rom --expect 250W</nowiki></code>.
# Write each target card once: <code><nowiki>nvflash -i N 300w.rom</nowiki></code>, answer <code><nowiki>y</nowiki></code> at the prompt (or let the attached controller do it). Success looks like a progress bar to 100 %, two verification reads, and <code><nowiki>A reboot is required for the update to take effect.</nowiki></code> with exit code 0. Anything else: do not retry that card this boot.
# Remove the blacklist, restore the units, cold cycle again.
# Verify: <code><nowiki>nvidia-smi --query-gpu=index,vbios_version,memory.total,clocks.max.memory,power.default_limit,power.max_limit --format=csv</nowiki></code> should show 92.00.6D.00.0A, your unlocked memory size, 1728 MHz, 250 W default and 300 W maximum; <code><nowiki>nvml_oc -i N</nowiki></code> should show the [-1000 .. +1000] range.

The attached <code><nowiki>window.sh</nowiki></code> runs those phases (<code><nowiki>check</nowiki></code>, <code><nowiki>prep</nowiki></code>, <code><nowiki>flash</nowiki></code>, <code><nowiki>restore</nowiki></code>, <code><nowiki>verify</nowiki></code>) with the lab box's unit names and bus map; edit those before using it elsewhere.

{{Status|Proven}} {{Cards|8 GB}} 
{{Source|handle=darkmaniac7|date=2026-10-31|note=lab notes}} 
{{Source|repo=https://github.com/polyuij42-del/cmp170hx-vbios-flash}}

=== Why not unbind the driver instead ===
The repository above spent eighteen script versions on the unbind route. With any process still holding
<code><nowiki>/dev/nvidia*</nowiki></code>, <code><nowiki>echo ... > /sys/bus/pci/drivers/nvidia/unbind</nowiki></code> hangs in the driver's remove path and never
returns; on one of its two cards it hung even with zero handles open, and a <code><nowiki>reboot</nowiki></code> issued in that state stalled the
machine until someone cut the power. Booting with the modules blacklisted sidesteps all of it.

{{Status|Warning}} {{Cards|8 GB}} 
{{Source|repo=https://github.com/polyuij42-del/cmp170hx-vbios-flash}}

=== Others who flashed it with nvflash ===
Several owners did the same flash with stock nvflash before the lab did, on Linux and on Windows; none reported a
brick from it. The bricks reported on the server came from fuse burns, SPI strap edits and A100 cross-flashes, not from
this image.

{{Status|Reported}} {{Cards|8 GB}} 
{{Source|handle=c133|date=2026-08-23|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1541187172588326962}} 
{{Source|handle=c133|date=2026-08-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1542649519739769003}} 
{{Source|handle=shirogeek|date=2026-09-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1546191972392501369}} 
{{Source|handle=derick2k|date=2026-09-06|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1546163237186441286}} 
{{Source|handle=phoenixone7|date=2026-09-16|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1549930400707514490}} 
{{Source|handle=wakeupmbrc1|date=2026-08-30|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1543658182298173581}}

== Results on eight cards ==
Two of the eight (bus 41 and C1) have FBPA0 fused off (one dead HBM stack each). Both took the image and initialised
cleanly at 1728 MHz; the driver log after the flash matched the log before it line for line in shape (the unlock's
privilege-mask loop prints 54 "Booter failed" lines per card on every boot; that is normal, not damage).

{| class="wikitable"
! Card (bus) !! VBIOS after !! Memory !! Max mem clock !! Default / max cap !! Offset range !! Note
|-
| 0 (01) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 ||
|-
| 1 (22) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 ||
|-
| 2 (41) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 || FBPA0 fused
|-
| 3 (61) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 ||
|-
| 4 (81) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 ||
|-
| 5 (A1) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 ||
|-
| 6 (C1) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 || FBPA0 fused
|-
| 7 (C2) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 || first attempt aborted by the controller, window re-opened by a PCIe rescan, second write fine
|}
Zero Xids, zero ECC errors, zero RmInitAdapter failures across four cold cycles.

{{Status|Proven}} {{Cards|8 GB}} 
{{Source|handle=darkmaniac7|date=2026-10-31|note=lab notes}}

== What it changed ==
The load is a proof-of-work miner (pearlhash, OneZeroMiner) on all eight cards with the fan wall at 15 % and caps set
per card by a thermal governor (230 to 250 W). The rejected shares below were all "Stale share" (a share submitted after
the pool changed the job: timing, not a wrong answer); there were no invalid shares.

{| class="wikitable"
! State !! Total hashrate !! Core clock range !! Temps !! Notes
|-
| 250 W image, offset 0 || 1,455 TH/s || 1215 to 1290 MHz || 70 to 79 C || baseline, same caps
|-
| 300 W image, offset 0 || 1,459 to 1,470 TH/s || 1215 to 1290 MHz || 70 to 79 C || HBM 1728 MHz cost nothing on a compute load
|-
| 300 W image, GPC offset +100 || 1,525 TH/s || 1275 to 1365 MHz || unchanged || 20 min soak, 0 Xid
|-
| 300 W image, GPC offset +130 || 1,549 TH/s || 1290 to 1380 MHz || unchanged || 20 min soak, 0 Xid
|-
| 300 W image, GPC offset +160 || 1,564 TH/s || 1335 to 1410 MHz || unchanged || 20 min soak, 0 Xid
|-
| 300 W image, GPC offset +190 || 1,579 TH/s || 1335 to 1425 MHz || unchanged || 20 min soak, 0 Xid
|-
| 300 W image, GPC offset +220, six cards || 1,598 TH/s || 1350 to 1440 MHz || unchanged || 20 min soak, 0 Xid; two cards still parked by the false alarms
|-
| 300 W image, GPC offset +220, all eight || 1,631 TH/s || 1350 to 1440 MHz || unchanged || 09:57, after the two parked cards took +160/+190/+220 clean; +11.8 % over the morning baseline. Not a safe point: see the warning below
|}
Power draw stayed at the caps the whole time: the offset lets the core hold a higher clock at the same watts, so the
gain comes with no extra heat. Two cards were held back early by a stale share each (a rule that counted any rejected
share; it now counts only invalid ones); re-run from +160, both took every rung.

=== The miner does not qualify an offset for inference ===
{{Status|Warning}} {{Cards|8 GB}} 
One hour after all eight reached +220 with the miner clean, the lab ran its inference benchmark against GLM 5.3 Flash
(TP4) on cards 0 to 3. Single-stream decode measured 268 tok/s against 232 before the undervolt (+15 %), 197 against
181 at two streams; then, one minute in, card 0 (the hottest slot, 77 to 79 C under the miner) began flooding
<code><nowiki>Xid 48</nowiki></code> (uncorrectable ECC error in GPC3 GCC) and <code><nowiki>Xid 172</nowiki></code>
(uncorrectable SRAM error in GPC 3), 97,000 lines in five minutes, and the engine died. That is the same pair the
Discord reports for a too-deep offset. At the same time card 5, which only ever ran the miner, was found in "GPU
requires reset" with no Xid at all, about two hours into +220. Lowering the offset does not clear either state: card 0
recovered with <code><nowiki>nvidia-smi -r</nowiki></code>, card 5 needed a cold cycle. What this means:
* A 20-minute miner soak proves nothing about inference, and not much about a two-hour miner run either. Qualify each
card against the engine that will serve on it, with a benchmark as the workload rung, and soak for hours, not minutes.
* Hot-slot cards have the least margin. Expect them to land well below the cool ones.
* +220 is not a safe point on this box. The lab reverted every card to 0 and will re-ladder with inference gating from
+100 in 30 MHz steps.

{{Source|handle=darkmaniac7|date=2026-10-31|note=lab notes}} 
{{Source|handle=ichundes|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1557350219111342183}}

{{Status|Proven}} {{Cards|8 GB}} 
{{Source|handle=darkmaniac7|date=2026-10-31|note=lab notes}}

== Risks and what the community saw ==
* {{Status|Warning}} One owner advised against the 300 W image because a photo of a burned 170HX had been posted earlier and the board lacks some power-delivery parts of the full layout. The photo is not in the exported history and no post ties a burned card to this image. The image's own default is 250 W; nothing on the lab box sets 300 W, and the undervolt reduces current at a given cap rather than raising it. Keep your cap at or below 250 W until you have a reason and the cooling to go higher. {{Source|handle=xanthefin|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561336153515364444}}
* {{Status|Contested}} HBM at 1728 MHz: one owner on the 300 W image with a 250 W limit passed GPU-burn with no errors but saw sporadic Vulkan memtest errors across the HBM dies; the eight lab cards (Hynix) ran clean. If a card misbehaves at 1728 MHz, 170tune can set the memory clock back down (not on FBPA0-fused cards, where the PLL tool must not write). {{Source|handle=cute_sc2|date=2026-08-08|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1535648815456198667}} {{Source|handle=darkmaniac7|date=2026-10-31|note=lab notes}}
* {{Status|Warning}} A failed flash is recoverable only with an SPI programmer with a 1.8 V adapter (the flash IC is 1.8 V; some "3.3 V" CH341A units put out 5 V, so a CH347 unit whose software selects the voltage is the safer buy). Power loss during the write and the wrong file are the two real ways to get there; both are yours to prevent. {{Source|repo=https://github.com/Consensus-Protocol/cmp170hx}}

== Rollback ==
The same procedure with your saved 92.00.67.00.01 dump as the image: one write per card in a driverless boot, then a
cold cycle. The lab keeps its dump with the rest of the evidence; any card's dump of the same version works for any
card of the same version.

== Files ==
* {{Download|file=CMP170HX_92.00.6D.00.0A.rom|compact=yes}} The 300 W image, byte-identical to TechPowerUp 268495 (hashes above).
* {{Download|file=Vbios_check_rom.py|compact=yes}} Structural ROM check (MIT, from polyuij42-del/cmp170hx-vbios-flash).
* {{Download|file=Vbios_flash_one.py|compact=yes}} The pty controller that answers nvflash's prompt only after it has echoed the expected versions, and checks the bus afterwards.
* {{Download|file=Vbios_window.sh.gz|compact=yes}} The lab's phase script (gzipped: the wiki refuses a shebang script under a plain extension) (check, prep, flash, restore, verify); unit names and bus map are the lab box's.

== Related ==
[[VBIOS and firmware]], [[Undervolting and power limits]], [[Driver unlock]], [[170tune]], [[Troubleshooting]].

{{ImportFooter}}
[[Category:Unlocks]]
[[Category:8 GB]]
[[Category:Cooling and power]]

Flashing the 300 W VBIOS

2026-10-31T14:58:06Z

Most 8 GB cards ship with VBIOS 92.00.67.00.01, the 250 W image. On it the driver reports a GPC and memory VF-offset
range of [0 .. +0], so no undervolt can be applied, whatever a tool says it set. The factory 300 W image
92.00.6D.00.0A, which NVIDIA shipped on the same board part number (900-11001-0108-000), exposes an offset range of
[-1000 .. +1000], boots the HBM at 1728 MHz instead of 1458 MHz, raises the SM ceiling from 1410 to 1695 MHz, and
keeps a 250 W default cap (300 W is the maximum it allows). This page is the flash procedure as run on eight cards in
one night, with the numbers before and after. It does not touch the memory or compute unlock, which stays in the
driver; see [[Driver unlock]].

The 10 GB card has no 300 W image (its only VBIOS is 92.00.66.00.02); this page is for 8 GB cards. See
[[VBIOS and firmware]] for the full image inventory.

== Why flash it ==
=== The 250 W image has no undervolt lever ===
<code><nowiki>nvml_oc -i N</nowiki></code> (the helper 170tune uses) reports <code><nowiki>allowed range : [0 .. +0] MHz</nowiki></code>
for both the GPC and the memory VF offset on every 92.00.67.00.01 card. An offset call can return success and the
driver still drops it; only a readback proves it applied. On the same cards after the flash the range reads
[-1000 .. +1000].

{{Status|Proven}} {{Cards|8 GB}} 
{{Source|handle=mrpec|date=2026-08-01|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1533150703328039085}} 
{{Source|handle=unmotivatedgene|date=2026-08-23|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1541201873803943997}} 
{{Source|handle=darkmaniac7|date=2026-10-31|note=lab notes}}

=== Same board, same IDs ===
Both images carry device 10DE:20C2, subsystem 10DE:1585 and board ID 0x030A, and both have been read off cards with
board part number 900-11001-0108-000 and die 20C2-105-A1. nvflash accepts the 300 W image on a 250 W card without any
override because the IDs match; it is a signed NVIDIA image, not a modified one.

{{Status|Reported}} {{Cards|8 GB}} 
{{Source|handle=con3po7016|date=2026-08-23|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1541194940997046322}} 
{{Source|handle=wakeupmbrc1|date=2026-08-30|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1543658140875235459}}

== Before you start ==
# '''An 8 GB card on 92.00.67.00.01.''' Read it with <code><nowiki>nvidia-smi --query-gpu=index,pci.bus_id,vbios_version --format=csv</nowiki></code>. A card already on 92.00.6D.00.0A has nothing to gain.
# '''nvflash 5.867 for Linux''', the <code><nowiki>x64/nvflash</nowiki></code> binary from the TechPowerUp download (the zip holds x86, x64, aarch64 and ppc64 builds; the Windows zip is a different download).
# '''The ROM''', TechPowerUp VBIOS database entry 268495 (listed there as "CMP 170HX 0 MB"; the size column is wrong). Verify it before it goes near a card: see below. A copy is attached to this page.
# '''A rollback ROM.''' Save one card's 92.00.67.00.01 image with <code><nowiki>nvflash -i N --save</nowiki></code> before you write anything. The static part of the image is identical across cards of the same version, so one dump serves as the rollback for all of them.
# '''A way to power the machine off and on''' that does not depend on the GPUs: a BMC, or someone at the button. The procedure needs two cold cycles, and a wedged flash controller only clears on a cold cycle.
# '''The driver unloaded, or never loaded.''' nvflash refuses to write with the NVIDIA kernel module present. The method below boots without it, which also avoids the unbind hang described further down.

== Verify the ROM ==
The TechPowerUp file matched these values exactly:
{| class="wikitable"
! Field !! Value
|-
| Version || 92.00.6D.00.0A
|-
| Build / modification date || 06/16/21 / 04/07/22
|-
| Size || 1,044,480 bytes
|-
| Device / subsystem / board ID || 0x20C2 / 0x1585 / 0x030A
|-
| MD5 || a58aae86e72b13d50603c15653350664
|-
| SHA1 || efad37d514bb94ac345719a0c56d9cd147cddfb7
|-
| SHA256 || 789e8f8d4c70dc9eb114c9fdcef6ed2d00aedf15a1eca522519de02042818723
|}
Two checks that do not depend on a hash:
* <code><nowiki>nvflash --version 300w.rom</nowiki></code> reads the header from the file only (it does not touch a card) and must print the version, device, subsystem and board IDs above, and <code><nowiki>License Placeholder : Present</nowiki></code>.
* <code><nowiki>python3 check_rom.py 300w.rom --expect 300W</nowiki></code> (attached) checks the structural markers: the NVGI header, the 300 W power bytes <code><nowiki>E0 93 04</nowiki></code> at 0x46045, the strap tier byte 0x44 at 0x41F53 (0x66 there means a forged "64 GB" ROM that bricks the card at boot), an all-zero license region at 0xFE504, and the dual-bank mirror. The same script recognises the 250 W image (<code><nowiki>--expect 250W</nowiki></code>) for checking your rollback dump.

{{Status|Reported}} {{Cards|8 GB}} 
{{Source|repo=https://github.com/polyuij42-del/cmp170hx-vbios-flash}} 
{{Source|repo=https://github.com/Consensus-Protocol/cmp170hx}}

== The procedure (driverless boot) ==
Proven on eight cards in two rounds, 2026-10-31, on a bare-metal Ubuntu box with the cmpunlocker driver build 615.71.09,
BMC power control and the tooling attached below. Every write took about 10 seconds. Read the two rules first:

* '''One nvflash operation per card per boot.''' After a power-on, the first nvflash command that touches a card's flash controller (<code><nowiki>--check</nowiki></code>, <code><nowiki>--save</nowiki></code> or a write) works; a second one on the same card fails with <code><nowiki>Falcon In HALT or STOP state</nowiki></code> or <code><nowiki>Detecting GPU failed</nowiki></code> and nothing is written. So the rollback save comes from a card you are not writing in that boot (or from an earlier boot), and the write is the first and only thing you do to each target card. A PCIe remove and rescan of one device (<code><nowiki>echo 1 > /sys/bus/pci/devices/0000:XX:00.0/remove; echo 1 > /sys/bus/pci/rescan</nowiki></code>) re-opened the window once in the lab; do not count on it.
* '''nvflash 5.867 ignores <code><nowiki>-y</nowiki></code> and refuses piped input.''' The confirm prompt needs a real terminal. It prints the card's current and replacement version strings before the prompt, and the PCI bus only in its Results table after the operation, so the attached controller confirms on the version strings (current must be 92.00.67.00.01, replacement 92.00.6D.00.0A) and checks the bus afterwards. nvflash's <code><nowiki>-i</nowiki></code> index follows PCI bus order, the same order <code><nowiki>nvidia-smi</nowiki></code> uses with <code><nowiki>CUDA_DEVICE_ORDER=PCI_BUS_ID</nowiki></code>; the Results table confirmed <code><nowiki>-i 7</nowiki></code> = bus C2 on the lab box.

Steps:
# Stop everything that holds the GPUs (engines, miners), until <code><nowiki>lsof /dev/nvidia*</nowiki></code> shows nothing. Record every card's VBIOS version.
# Keep the driver out of the next boot: <code><nowiki>/etc/modprobe.d/zz-flash-window.conf</nowiki></code> with <code><nowiki>install nvidia /bin/false</nowiki></code> (and the same for nvidia_modeset, nvidia_drm, nvidia_uvm). Mask or disable the units that would start GPU work at boot (docker, miners, any model loader). Note what you changed.
# Cold cycle: power off, 30 seconds dark, power on. Confirm <code><nowiki>lsmod | grep nvidia</nowiki></code> is empty and that the cards are enumerated with no driver bound.
# Save the rollback ROM from a card you will not write this boot: <code><nowiki>nvflash -i N --save backup.rom</nowiki></code>, then <code><nowiki>check_rom.py backup.rom --expect 250W</nowiki></code>.
# Write each target card once: <code><nowiki>nvflash -i N 300w.rom</nowiki></code>, answer <code><nowiki>y</nowiki></code> at the prompt (or let the attached controller do it). Success looks like a progress bar to 100 %, two verification reads, and <code><nowiki>A reboot is required for the update to take effect.</nowiki></code> with exit code 0. Anything else: do not retry that card this boot.
# Remove the blacklist, restore the units, cold cycle again.
# Verify: <code><nowiki>nvidia-smi --query-gpu=index,vbios_version,memory.total,clocks.max.memory,power.default_limit,power.max_limit --format=csv</nowiki></code> should show 92.00.6D.00.0A, your unlocked memory size, 1728 MHz, 250 W default and 300 W maximum; <code><nowiki>nvml_oc -i N</nowiki></code> should show the [-1000 .. +1000] range.

The attached <code><nowiki>window.sh</nowiki></code> runs those phases (<code><nowiki>check</nowiki></code>, <code><nowiki>prep</nowiki></code>, <code><nowiki>flash</nowiki></code>, <code><nowiki>restore</nowiki></code>, <code><nowiki>verify</nowiki></code>) with the lab box's unit names and bus map; edit those before using it elsewhere.

{{Status|Proven}} {{Cards|8 GB}} 
{{Source|handle=darkmaniac7|date=2026-10-31|note=lab notes}} 
{{Source|repo=https://github.com/polyuij42-del/cmp170hx-vbios-flash}}

=== Why not unbind the driver instead ===
The repository above spent eighteen script versions on the unbind route. With any process still holding
<code><nowiki>/dev/nvidia*</nowiki></code>, <code><nowiki>echo ... > /sys/bus/pci/drivers/nvidia/unbind</nowiki></code> hangs in the driver's remove path and never
returns; on one of its two cards it hung even with zero handles open, and a <code><nowiki>reboot</nowiki></code> issued in that state stalled the
machine until someone cut the power. Booting with the modules blacklisted sidesteps all of it.

{{Status|Warning}} {{Cards|8 GB}} 
{{Source|repo=https://github.com/polyuij42-del/cmp170hx-vbios-flash}}

=== Others who flashed it with nvflash ===
Several owners did the same flash with stock nvflash before the lab did, on Linux and on Windows; none reported a
brick from it. The bricks reported on the server came from fuse burns, SPI strap edits and A100 cross-flashes, not from
this image.

{{Status|Reported}} {{Cards|8 GB}} 
{{Source|handle=c133|date=2026-08-23|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1541187172588326962}} 
{{Source|handle=c133|date=2026-08-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1542649519739769003}} 
{{Source|handle=shirogeek|date=2026-09-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1546191972392501369}} 
{{Source|handle=derick2k|date=2026-09-06|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1546163237186441286}} 
{{Source|handle=phoenixone7|date=2026-09-16|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1549930400707514490}} 
{{Source|handle=wakeupmbrc1|date=2026-08-30|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1543658182298173581}}

== Results on eight cards ==
Two of the eight (bus 41 and C1) have FBPA0 fused off (one dead HBM stack each). Both took the image and initialised
cleanly at 1728 MHz; the driver log after the flash matched the log before it line for line in shape (the unlock's
privilege-mask loop prints 54 "Booter failed" lines per card on every boot; that is normal, not damage).

{| class="wikitable"
! Card (bus) !! VBIOS after !! Memory !! Max mem clock !! Default / max cap !! Offset range !! Note
|-
| 0 (01) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 ||
|-
| 1 (22) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 ||
|-
| 2 (41) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 || FBPA0 fused
|-
| 3 (61) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 ||
|-
| 4 (81) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 ||
|-
| 5 (A1) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 ||
|-
| 6 (C1) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 || FBPA0 fused
|-
| 7 (C2) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 || first attempt aborted by the controller, window re-opened by a PCIe rescan, second write fine
|}
Zero Xids, zero ECC errors, zero RmInitAdapter failures across four cold cycles.

{{Status|Proven}} {{Cards|8 GB}} 
{{Source|handle=darkmaniac7|date=2026-10-31|note=lab notes}}

== What it changed ==
The load is a proof-of-work miner (pearlhash, OneZeroMiner) on all eight cards with the fan wall at 15 % and caps set
per card by a thermal governor (230 to 250 W). The rejected shares below were all "Stale share" (a share submitted after
the pool changed the job: timing, not a wrong answer); there were no invalid shares.

{| class="wikitable"
! State !! Total hashrate !! Core clock range !! Temps !! Notes
|-
| 250 W image, offset 0 || 1,455 TH/s || 1215 to 1290 MHz || 70 to 79 C || baseline, same caps
|-
| 300 W image, offset 0 || 1,459 to 1,470 TH/s || 1215 to 1290 MHz || 70 to 79 C || HBM 1728 MHz cost nothing on a compute load
|-
| 300 W image, GPC offset +100 || 1,525 TH/s || 1275 to 1365 MHz || unchanged || 20 min soak, 0 Xid
|-
| 300 W image, GPC offset +130 || 1,549 TH/s || 1290 to 1380 MHz || unchanged || 20 min soak, 0 Xid
|-
| 300 W image, GPC offset +160 || 1,564 TH/s || 1335 to 1410 MHz || unchanged || 20 min soak, 0 Xid
|-
| 300 W image, GPC offset +190 || 1,579 TH/s || 1335 to 1425 MHz || unchanged || 20 min soak, 0 Xid
|-
| 300 W image, GPC offset +220, six cards || 1,598 TH/s || 1350 to 1440 MHz || unchanged || 20 min soak, 0 Xid; two cards still parked by the false alarms
|-
| 300 W image, GPC offset +220, all eight || 1,631 TH/s || 1350 to 1440 MHz || unchanged || 09:57, after the two parked cards took +160/+190/+220 clean; +11.8 % over the morning baseline
|}
Power draw stayed at the caps the whole time: the offset lets the core hold a higher clock at the same watts, so the
gain comes with no extra heat. Two cards were held back early by a stale share each (a rule that counted any rejected
share; it now counts only invalid ones); re-run from +160, both took every rung. +9.5 % total at the same watts and the same
temperatures. +220 was the ladder's chosen top, not a measured ceiling; the long soak and the persist step come next.

{{Status|Proven}} {{Cards|8 GB}} 
{{Source|handle=darkmaniac7|date=2026-10-31|note=lab notes}}

== Risks and what the community saw ==
* {{Status|Warning}} One owner advised against the 300 W image because a photo of a burned 170HX had been posted earlier and the board lacks some power-delivery parts of the full layout. The photo is not in the exported history and no post ties a burned card to this image. The image's own default is 250 W; nothing on the lab box sets 300 W, and the undervolt reduces current at a given cap rather than raising it. Keep your cap at or below 250 W until you have a reason and the cooling to go higher. {{Source|handle=xanthefin|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561336153515364444}}
* {{Status|Contested}} HBM at 1728 MHz: one owner on the 300 W image with a 250 W limit passed GPU-burn with no errors but saw sporadic Vulkan memtest errors across the HBM dies; the eight lab cards (Hynix) ran clean. If a card misbehaves at 1728 MHz, 170tune can set the memory clock back down (not on FBPA0-fused cards, where the PLL tool must not write). {{Source|handle=cute_sc2|date=2026-08-08|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1535648815456198667}} {{Source|handle=darkmaniac7|date=2026-10-31|note=lab notes}}
* {{Status|Warning}} A failed flash is recoverable only with an SPI programmer with a 1.8 V adapter (the flash IC is 1.8 V; some "3.3 V" CH341A units put out 5 V, so a CH347 unit whose software selects the voltage is the safer buy). Power loss during the write and the wrong file are the two real ways to get there; both are yours to prevent. {{Source|repo=https://github.com/Consensus-Protocol/cmp170hx}}

== Rollback ==
The same procedure with your saved 92.00.67.00.01 dump as the image: one write per card in a driverless boot, then a
cold cycle. The lab keeps its dump with the rest of the evidence; any card's dump of the same version works for any
card of the same version.

== Files ==
* {{Download|file=CMP170HX_92.00.6D.00.0A.rom|compact=yes}} The 300 W image, byte-identical to TechPowerUp 268495 (hashes above).
* {{Download|file=Vbios_check_rom.py|compact=yes}} Structural ROM check (MIT, from polyuij42-del/cmp170hx-vbios-flash).
* {{Download|file=Vbios_flash_one.py|compact=yes}} The pty controller that answers nvflash's prompt only after it has echoed the expected versions, and checks the bus afterwards.
* {{Download|file=Vbios_window.sh.gz|compact=yes}} The lab's phase script (gzipped: the wiki refuses a shebang script under a plain extension) (check, prep, flash, restore, verify); unit names and bus map are the lab box's.

== Related ==
[[VBIOS and firmware]], [[Undervolting and power limits]], [[Driver unlock]], [[170tune]], [[Troubleshooting]].

{{ImportFooter}}
[[Category:Unlocks]]
[[Category:8 GB]]
[[Category:Cooling and power]]

Flashing the 300 W VBIOS

2026-10-31T13:57:10Z

Most 8 GB cards ship with VBIOS 92.00.67.00.01, the 250 W image. On it the driver reports a GPC and memory VF-offset
range of [0 .. +0], so no undervolt can be applied, whatever a tool says it set. The factory 300 W image
92.00.6D.00.0A, which NVIDIA shipped on the same board part number (900-11001-0108-000), exposes an offset range of
[-1000 .. +1000], boots the HBM at 1728 MHz instead of 1458 MHz, raises the SM ceiling from 1410 to 1695 MHz, and
keeps a 250 W default cap (300 W is the maximum it allows). This page is the flash procedure as run on eight cards in
one night, with the numbers before and after. It does not touch the memory or compute unlock, which stays in the
driver; see [[Driver unlock]].

The 10 GB card has no 300 W image (its only VBIOS is 92.00.66.00.02); this page is for 8 GB cards. See
[[VBIOS and firmware]] for the full image inventory.

== Why flash it ==
=== The 250 W image has no undervolt lever ===
<code><nowiki>nvml_oc -i N</nowiki></code> (the helper 170tune uses) reports <code><nowiki>allowed range : [0 .. +0] MHz</nowiki></code>
for both the GPC and the memory VF offset on every 92.00.67.00.01 card. An offset call can return success and the
driver still drops it; only a readback proves it applied. On the same cards after the flash the range reads
[-1000 .. +1000].

{{Status|Proven}} {{Cards|8 GB}} 
{{Source|handle=mrpec|date=2026-08-01|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1533150703328039085}} 
{{Source|handle=unmotivatedgene|date=2026-08-23|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1541201873803943997}} 
{{Source|handle=darkmaniac7|date=2026-10-31|note=lab notes}}

=== Same board, same IDs ===
Both images carry device 10DE:20C2, subsystem 10DE:1585 and board ID 0x030A, and both have been read off cards with
board part number 900-11001-0108-000 and die 20C2-105-A1. nvflash accepts the 300 W image on a 250 W card without any
override because the IDs match; it is a signed NVIDIA image, not a modified one.

{{Status|Reported}} {{Cards|8 GB}} 
{{Source|handle=con3po7016|date=2026-08-23|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1541194940997046322}} 
{{Source|handle=wakeupmbrc1|date=2026-08-30|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1543658140875235459}}

== Before you start ==
# '''An 8 GB card on 92.00.67.00.01.''' Read it with <code><nowiki>nvidia-smi --query-gpu=index,pci.bus_id,vbios_version --format=csv</nowiki></code>. A card already on 92.00.6D.00.0A has nothing to gain.
# '''nvflash 5.867 for Linux''', the <code><nowiki>x64/nvflash</nowiki></code> binary from the TechPowerUp download (the zip holds x86, x64, aarch64 and ppc64 builds; the Windows zip is a different download).
# '''The ROM''', TechPowerUp VBIOS database entry 268495 (listed there as "CMP 170HX 0 MB"; the size column is wrong). Verify it before it goes near a card: see below. A copy is attached to this page.
# '''A rollback ROM.''' Save one card's 92.00.67.00.01 image with <code><nowiki>nvflash -i N --save</nowiki></code> before you write anything. The static part of the image is identical across cards of the same version, so one dump serves as the rollback for all of them.
# '''A way to power the machine off and on''' that does not depend on the GPUs: a BMC, or someone at the button. The procedure needs two cold cycles, and a wedged flash controller only clears on a cold cycle.
# '''The driver unloaded, or never loaded.''' nvflash refuses to write with the NVIDIA kernel module present. The method below boots without it, which also avoids the unbind hang described further down.

== Verify the ROM ==
The TechPowerUp file matched these values exactly:
{| class="wikitable"
! Field !! Value
|-
| Version || 92.00.6D.00.0A
|-
| Build / modification date || 06/16/21 / 04/07/22
|-
| Size || 1,044,480 bytes
|-
| Device / subsystem / board ID || 0x20C2 / 0x1585 / 0x030A
|-
| MD5 || a58aae86e72b13d50603c15653350664
|-
| SHA1 || efad37d514bb94ac345719a0c56d9cd147cddfb7
|-
| SHA256 || 789e8f8d4c70dc9eb114c9fdcef6ed2d00aedf15a1eca522519de02042818723
|}
Two checks that do not depend on a hash:
* <code><nowiki>nvflash --version 300w.rom</nowiki></code> reads the header from the file only (it does not touch a card) and must print the version, device, subsystem and board IDs above, and <code><nowiki>License Placeholder : Present</nowiki></code>.
* <code><nowiki>python3 check_rom.py 300w.rom --expect 300W</nowiki></code> (attached) checks the structural markers: the NVGI header, the 300 W power bytes <code><nowiki>E0 93 04</nowiki></code> at 0x46045, the strap tier byte 0x44 at 0x41F53 (0x66 there means a forged "64 GB" ROM that bricks the card at boot), an all-zero license region at 0xFE504, and the dual-bank mirror. The same script recognises the 250 W image (<code><nowiki>--expect 250W</nowiki></code>) for checking your rollback dump.

{{Status|Reported}} {{Cards|8 GB}} 
{{Source|repo=https://github.com/polyuij42-del/cmp170hx-vbios-flash}} 
{{Source|repo=https://github.com/Consensus-Protocol/cmp170hx}}

== The procedure (driverless boot) ==
Proven on eight cards in two rounds, 2026-10-31, on a bare-metal Ubuntu box with the cmpunlocker driver build 615.71.09,
BMC power control and the tooling attached below. Every write took about 10 seconds. Read the two rules first:

* '''One nvflash operation per card per boot.''' After a power-on, the first nvflash command that touches a card's flash controller (<code><nowiki>--check</nowiki></code>, <code><nowiki>--save</nowiki></code> or a write) works; a second one on the same card fails with <code><nowiki>Falcon In HALT or STOP state</nowiki></code> or <code><nowiki>Detecting GPU failed</nowiki></code> and nothing is written. So the rollback save comes from a card you are not writing in that boot (or from an earlier boot), and the write is the first and only thing you do to each target card. A PCIe remove and rescan of one device (<code><nowiki>echo 1 > /sys/bus/pci/devices/0000:XX:00.0/remove; echo 1 > /sys/bus/pci/rescan</nowiki></code>) re-opened the window once in the lab; do not count on it.
* '''nvflash 5.867 ignores <code><nowiki>-y</nowiki></code> and refuses piped input.''' The confirm prompt needs a real terminal. It prints the card's current and replacement version strings before the prompt, and the PCI bus only in its Results table after the operation, so the attached controller confirms on the version strings (current must be 92.00.67.00.01, replacement 92.00.6D.00.0A) and checks the bus afterwards. nvflash's <code><nowiki>-i</nowiki></code> index follows PCI bus order, the same order <code><nowiki>nvidia-smi</nowiki></code> uses with <code><nowiki>CUDA_DEVICE_ORDER=PCI_BUS_ID</nowiki></code>; the Results table confirmed <code><nowiki>-i 7</nowiki></code> = bus C2 on the lab box.

Steps:
# Stop everything that holds the GPUs (engines, miners), until <code><nowiki>lsof /dev/nvidia*</nowiki></code> shows nothing. Record every card's VBIOS version.
# Keep the driver out of the next boot: <code><nowiki>/etc/modprobe.d/zz-flash-window.conf</nowiki></code> with <code><nowiki>install nvidia /bin/false</nowiki></code> (and the same for nvidia_modeset, nvidia_drm, nvidia_uvm). Mask or disable the units that would start GPU work at boot (docker, miners, any model loader). Note what you changed.
# Cold cycle: power off, 30 seconds dark, power on. Confirm <code><nowiki>lsmod | grep nvidia</nowiki></code> is empty and that the cards are enumerated with no driver bound.
# Save the rollback ROM from a card you will not write this boot: <code><nowiki>nvflash -i N --save backup.rom</nowiki></code>, then <code><nowiki>check_rom.py backup.rom --expect 250W</nowiki></code>.
# Write each target card once: <code><nowiki>nvflash -i N 300w.rom</nowiki></code>, answer <code><nowiki>y</nowiki></code> at the prompt (or let the attached controller do it). Success looks like a progress bar to 100 %, two verification reads, and <code><nowiki>A reboot is required for the update to take effect.</nowiki></code> with exit code 0. Anything else: do not retry that card this boot.
# Remove the blacklist, restore the units, cold cycle again.
# Verify: <code><nowiki>nvidia-smi --query-gpu=index,vbios_version,memory.total,clocks.max.memory,power.default_limit,power.max_limit --format=csv</nowiki></code> should show 92.00.6D.00.0A, your unlocked memory size, 1728 MHz, 250 W default and 300 W maximum; <code><nowiki>nvml_oc -i N</nowiki></code> should show the [-1000 .. +1000] range.

The attached <code><nowiki>window.sh</nowiki></code> runs those phases (<code><nowiki>check</nowiki></code>, <code><nowiki>prep</nowiki></code>, <code><nowiki>flash</nowiki></code>, <code><nowiki>restore</nowiki></code>, <code><nowiki>verify</nowiki></code>) with the lab box's unit names and bus map; edit those before using it elsewhere.

{{Status|Proven}} {{Cards|8 GB}} 
{{Source|handle=darkmaniac7|date=2026-10-31|note=lab notes}} 
{{Source|repo=https://github.com/polyuij42-del/cmp170hx-vbios-flash}}

=== Why not unbind the driver instead ===
The repository above spent eighteen script versions on the unbind route. With any process still holding
<code><nowiki>/dev/nvidia*</nowiki></code>, <code><nowiki>echo ... > /sys/bus/pci/drivers/nvidia/unbind</nowiki></code> hangs in the driver's remove path and never
returns; on one of its two cards it hung even with zero handles open, and a <code><nowiki>reboot</nowiki></code> issued in that state stalled the
machine until someone cut the power. Booting with the modules blacklisted sidesteps all of it.

{{Status|Warning}} {{Cards|8 GB}} 
{{Source|repo=https://github.com/polyuij42-del/cmp170hx-vbios-flash}}

=== Others who flashed it with nvflash ===
Several owners did the same flash with stock nvflash before the lab did, on Linux and on Windows; none reported a
brick from it. The bricks reported on the server came from fuse burns, SPI strap edits and A100 cross-flashes, not from
this image.

{{Status|Reported}} {{Cards|8 GB}} 
{{Source|handle=c133|date=2026-08-23|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1541187172588326962}} 
{{Source|handle=c133|date=2026-08-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1542649519739769003}} 
{{Source|handle=shirogeek|date=2026-09-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1546191972392501369}} 
{{Source|handle=derick2k|date=2026-09-06|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1546163237186441286}} 
{{Source|handle=phoenixone7|date=2026-09-16|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1549930400707514490}} 
{{Source|handle=wakeupmbrc1|date=2026-08-30|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1543658182298173581}}

== Results on eight cards ==
Two of the eight (bus 41 and C1) have FBPA0 fused off (one dead HBM stack each). Both took the image and initialised
cleanly at 1728 MHz; the driver log after the flash matched the log before it line for line in shape (the unlock's
privilege-mask loop prints 54 "Booter failed" lines per card on every boot; that is normal, not damage).

{| class="wikitable"
! Card (bus) !! VBIOS after !! Memory !! Max mem clock !! Default / max cap !! Offset range !! Note
|-
| 0 (01) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 ||
|-
| 1 (22) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 ||
|-
| 2 (41) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 || FBPA0 fused
|-
| 3 (61) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 ||
|-
| 4 (81) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 ||
|-
| 5 (A1) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 ||
|-
| 6 (C1) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 || FBPA0 fused
|-
| 7 (C2) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 || first attempt aborted by the controller, window re-opened by a PCIe rescan, second write fine
|}
Zero Xids, zero ECC errors, zero RmInitAdapter failures across four cold cycles.

{{Status|Proven}} {{Cards|8 GB}} 
{{Source|handle=darkmaniac7|date=2026-10-31|note=lab notes}}

== What it changed ==
The load is a proof-of-work miner (pearlhash, OneZeroMiner) on all eight cards with the fan wall at 15 % and caps set
per card by a thermal governor (230 to 250 W). The rejected shares below were all "Stale share" (a share submitted after
the pool changed the job: timing, not a wrong answer); there were no invalid shares.

{| class="wikitable"
! State !! Total hashrate !! Core clock range !! Temps !! Notes
|-
| 250 W image, offset 0 || 1,455 TH/s || 1215 to 1290 MHz || 70 to 79 C || baseline, same caps
|-
| 300 W image, offset 0 || 1,459 to 1,470 TH/s || 1215 to 1290 MHz || 70 to 79 C || HBM 1728 MHz cost nothing on a compute load
|-
| 300 W image, GPC offset +100 || 1,525 TH/s || 1275 to 1365 MHz || unchanged || 20 min soak, 0 Xid
|-
| 300 W image, GPC offset +130 || 1,549 TH/s || 1290 to 1380 MHz || unchanged || 20 min soak, 0 Xid
|-
| 300 W image, GPC offset +160 || 1,564 TH/s || 1335 to 1410 MHz || unchanged || 20 min soak, 0 Xid
|-
| 300 W image, GPC offset +190 || 1,579 TH/s || 1335 to 1425 MHz || unchanged || 20 min soak, 0 Xid
|-
| 300 W image, GPC offset +220 || 1,598 TH/s || 1350 to 1440 MHz || unchanged || 20 min soak, 0 Xid; six cards at the ladder's top rung, two re-running after false alarms
|}
Power draw stayed at the caps the whole time: the offset lets the core hold a higher clock at the same watts, so the
gain comes with no extra heat. Two cards were held back early by a stale share each (a rule that counted any rejected
share; it now counts only invalid ones) and are being re-run from +160. +9.5 % total at the same watts and the same
temperatures. +220 was the ladder's chosen top, not a measured ceiling; the long soak and the persist step come next.

{{Status|Proven}} {{Cards|8 GB}} 
{{Source|handle=darkmaniac7|date=2026-10-31|note=lab notes}}

== Risks and what the community saw ==
* {{Status|Warning}} One owner advised against the 300 W image because a photo of a burned 170HX had been posted earlier and the board lacks some power-delivery parts of the full layout. The photo is not in the exported history and no post ties a burned card to this image. The image's own default is 250 W; nothing on the lab box sets 300 W, and the undervolt reduces current at a given cap rather than raising it. Keep your cap at or below 250 W until you have a reason and the cooling to go higher. {{Source|handle=xanthefin|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561336153515364444}}
* {{Status|Contested}} HBM at 1728 MHz: one owner on the 300 W image with a 250 W limit passed GPU-burn with no errors but saw sporadic Vulkan memtest errors across the HBM dies; the eight lab cards (Hynix) ran clean. If a card misbehaves at 1728 MHz, 170tune can set the memory clock back down (not on FBPA0-fused cards, where the PLL tool must not write). {{Source|handle=cute_sc2|date=2026-08-08|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1535648815456198667}} {{Source|handle=darkmaniac7|date=2026-10-31|note=lab notes}}
* {{Status|Warning}} A failed flash is recoverable only with an SPI programmer with a 1.8 V adapter (the flash IC is 1.8 V; some "3.3 V" CH341A units put out 5 V, so a CH347 unit whose software selects the voltage is the safer buy). Power loss during the write and the wrong file are the two real ways to get there; both are yours to prevent. {{Source|repo=https://github.com/Consensus-Protocol/cmp170hx}}

== Rollback ==
The same procedure with your saved 92.00.67.00.01 dump as the image: one write per card in a driverless boot, then a
cold cycle. The lab keeps its dump with the rest of the evidence; any card's dump of the same version works for any
card of the same version.

== Files ==
* {{Download|file=CMP170HX_92.00.6D.00.0A.rom|compact=yes}} The 300 W image, byte-identical to TechPowerUp 268495 (hashes above).
* {{Download|file=Vbios_check_rom.py|compact=yes}} Structural ROM check (MIT, from polyuij42-del/cmp170hx-vbios-flash).
* {{Download|file=Vbios_flash_one.py|compact=yes}} The pty controller that answers nvflash's prompt only after it has echoed the expected versions, and checks the bus afterwards.
* {{Download|file=Vbios_window.sh.gz|compact=yes}} The lab's phase script (gzipped: the wiki refuses a shebang script under a plain extension) (check, prep, flash, restore, verify); unit names and bus map are the lab box's.

== Related ==
[[VBIOS and firmware]], [[Undervolting and power limits]], [[Driver unlock]], [[170tune]], [[Troubleshooting]].

{{ImportFooter}}
[[Category:Unlocks]]
[[Category:8 GB]]
[[Category:Cooling and power]]

VBIOS and firmware

2026-10-31T13:22:03Z

ImportBot: Link the 300 W VBIOS flash procedure (lab notes 2026-10-31) from the inventory and Status

The 170HX VBIOS is '''signed''', and the memory/compute unlock does '''not''' come from flashing a modified VBIOS; it
comes from the driver patch ([[Driver unlock|cmpunlocker]]). Most VBIOS work on these cards is either identification,
power-limit editing, or dead ends. Treat anything that writes the flash chip as high-risk.

== Background: why driver-loaded overrides work (Petri Krohn) ==

Petri Krohn's explanation of the firmware model, as background, not a measured result: the GA100 does not load firmware
blobs directly from the SPI ROM chip; the driver loads them into the Falcon cores. The IMEM sections are encrypted and
signed, but the DMEM data (power tables, fan curves) is cleartext and unsigned apart from the whole-image signature, so
the driver can hand the Falcon a modified DMEM. The bootrom only checks the ROM copy at power-up, so in a Linux VM you
can present the driver a modified shadow VBIOS. {{Source|petrikrohn_26497|2026-10-20|https://discord.com/channels/1518634379604136178/1518692084729511967/1562075696380248065}}
Separately, he says the unlocker does not use or need the debug version of <code>booter_load</code> (that was only
needed while developing the ROP chain, because the debug AES key let the booter be disassembled), so NVIDIA cannot
disable the unlocker except perhaps by forcing a firmware upgrade. {{Source|petrikrohn_26497|2026-10-27|https://discord.com/channels/1518634379604136178/1518692084729511967/1564781631712272495}}

== Stock VBIOS inventory ==

{| class="wikitable"
! Version !! Card !! Notes
|-
| 92.00.67.00.01 || 8 GB || stock production (2021-05-14, 250 W)
|-
| 92.00.6D.00.0A || 8 GB || 300 W OC image, memory OC allowed; the undervolt range opens on it; flashing it onto a 92.00.67.00.01 card: [[Flashing the 300 W VBIOS]]
|-
| 92.00.6D.00.09 || 8 GB || 300 W, no memory OC
|-
| 92.00.66.00.02 || 10 GB || the only 10 GB image
|-
| 92.00.6D.00.01 || 8 GB (ES) || PG199 engineering-sample 170HX, unlocks to 32 GB only
|}

The VBIOS version does not decide whether the unlock works. {{Source|rrickk420|2026-08-22|https://github.com/Consensus-Protocol/cmp170hx}}
92.00.6D.00.0A is an 8 GB image. {{Source|ghostinthedatacenter_87281|2026-10-17|https://discord.com/channels/1518634379604136178/1534370835220004885/1560857113105010820}}
Board part numbers: 900-11001-0108-000 (8 GB), 900-11001-0105-000 (10 GB); an ES/32 GB card uses a
699-xxxxx-xxxx-RCx number. See [[Which card do I have]].

== The vix no-flash loaders (Panchovix) ==

[https://github.com/Panchovix/nvidia-linux-vbios-vix-loader nvidia-linux-vbios-vix-loader] (Linux) and
nvidia-windows-vbios-vix-loader load a modified VBIOS at boot in memory by patching the 615.x open modules so GSP starts
with the override image; the flash chip is never written, and the companion
[https://github.com/Panchovix/nvidia-vbios-vix-editor nvidia-vbios-vix-editor] edits power limits, voltages and fan
curves. {{Status|warning}} '''These do not support the CMP 170HX today''': the device table has no
<code>0x20C2</code>/<code>0x2082</code> entry and GA100 GSP firmware is explicitly unaudited.

lxwx tested the Linux loader on a 170HX 10 GB and reports it works and let him tweak TDP to 300 W on 610/615 drivers,
together with the gen3 unlock. {{Source|lxtend|2026-10-20|https://discord.com/channels/1518634379604136178/1518692084729511967/1562103260490240172}}
But the override is applied in GSP, which is '''too late in boot''' to touch anything still locked on the 8 GB card, so
for the unlock it adds nothing new; clocks and similar settings should be reachable through it, little else.
{{Source|handle=scallion_9883|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561103147215224983}} {{Source|handle=scallion_9883|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561816073844555929}} {{Source|handle=scallion_9883|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561816657788276867}} {{Source|handle=scallion_9883|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518691940646781070/1561841116603621527}}
The 300 W power-limit bytes sit outside the VBIOS signature section, implying the power limit is editable without the
signing key. {{Source|xanthefin|2026-10-18|https://discord.com/channels/1518634379604136178/1518692084729511967/1561368219657179187}}

An older method: before the vix loader, the 10 GB card's VF offset and 300 W limit were reached by giving the driver
the 8 GB unlocked VBIOS, truncated, instead of normal operation; Mr Pec got 300 W max on a 10 GB card this way.
{{Source|bigptoughneigh|2026-10-04|https://discord.com/channels/1518634379604136178/1518692084729511967/1556320331457761301}}

== The "64 GB unlocked VBIOS" repos (bogus) ==

{{Status|warning}} The repos '''344303947/CMP-170HX-64GB-Unlocked-VBIOS''' and its mirror
'''justin-kk-coder/CMP-170HX-64GB-Unlocked-VBIOS''' (git author "Thaurock") present a 1 MB ROM
(sha256 <code>2e8961ac518924cebd52363555c875071e6a58ece1ef494e192e42d5c1dcd5a2</code>) as a "64 GB unlocked" VBIOS with
<code>nvflash -6</code> instructions. By version, date and IDs it is the '''stock''' 8 GB production VBIOS
(92.00.67.00.01); the 64 GB readout in its screenshot is what the driver-side unlock produces, not the ROM. The unlock
involves no VBIOS change. When members compared the file to the original in August there was no difference.
'''Do not flash it.''' {{Source|c133|2026-10-18|https://discord.com/channels/1518634379604136178/1518692084729511967/1561390399283535955}}
{{Source|handle=xanthefin|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561391210906517565}} {{Source|handle=globalapathy|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561391800818733068}} {{Source|handle=c133|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561392232370806855}}

{{Status|Contested}} An "unlocked VBIOS" for the 10 GB card is also said to exist, "a harder find it seems due to legal
concerns"; this was hearsay, with no file or result shown. {{Source|handle=supasnipa360|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561388811123167233}}
The answer in the same thread applies to both variants: the unlock makes no VBIOS change, and someone able to write a
VBIOS would not have stopped at 64 GB. {{Source|handle=xanthefin|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561391210906517565}} {{Source|handle=globalapathy|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561391800818733068}}

== SPI flashing (if you must) ==

Flashing a different VBIOS (e.g. A100) means opening the card and programming the flash IC. {{Status|warning}} Be
careful which programmer you buy: flash ICs are 1.8 V or 3 V and a 3 V programmer fries a 1.8 V flash; some "3.3 V"
CH341a units are really 5 V. Prefer a CH347-based flasher (its software selects the voltage).
{{Source|wakeupmbrc1|2026-10-13|https://discord.com/channels/1518634379604136178/1518695328008638516/1559582577503899649}}
The 170HX VBIOS is signed, so flashing a modified image is a separate (unsolved) problem; and
{{Status|warning}} a VBIOS TOCTOU test was reported to brick a card permanently, unrecoverable even after restoring the
original image. {{Source|youngju10000|2026-10-08|https://discord.com/channels/1518634379604136178/1518692084729511967/1557647494417088513}}

A dead-on-arrival 10 GB card whose VBIOS ROM reads <code>0xFFFF</code> and fails GSP init is likely a bad SPI flash;
see [[Troubleshooting]].

== GSP-off and vGPU ==

* '''GSP disabled:''' applying the unlock, building a dual-stack driver that persists the unlock kernels, then loading
the proprietary driver with <code>NVreg_EnableGpuFirmware=0</code> let certain register changes survive the reload
with no GSP panics. GreenDam replied that it works well on the 90HX. matstatman doubts it helps, since everything
software can unlock has been found and the fuses cut off the rest. {{Source|zarknoth|2026-10-27|https://discord.com/channels/1518634379604136178/1518695328008638516/1564547690019160145}} 
{{Source|handle=matstatman|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1564575816010965024}} 
{{Source|handle=green_dam|date=2026-10-28|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1564799215874474065}}
* '''vGPU:''' close to working in cmpunlocker on the <code>vGPU-and-others</code> branch (three patches:
vgpu-kvm-build, vgpu-ga100-host, vgpu-umd-version). {{Source|_j3ns|2026-10-26|https://discord.com/channels/1518634379604136178/1518692084729511967/1564421429703737355}}
arabus's build note: clone with <code><nowiki>git clone --branch vGPU-and-others --single-branch https://github.com/amoghmunikote/cmpunlocker.git</nowiki></code>;
the patches live in <code>driver/patches/vgpu-*.patch</code>, must be in <code>PATCH_ORDER</code> in
<code>driver/build.sh</code>, and each must be declared under <code>unlocks:</code> in <code>common/constants.yaml</code>
(three entries before the <code>ecc:</code> block, each with <code>registers: {}</code>) or
<code>tools/read-constants.py</code> rejects the build; then <code>sudo ./install.sh --profile=10gb</code>. Whether
vGPU then worked is not stated. {{Source|arabus_74064|2026-10-27|https://discord.com/channels/1518634379604136178/1518692084729511967/1564633314298568776}}

== Fuse RE references ==

The GA100 fuse / RIR architecture is reverse-engineered read-only in
[https://github.com/ahnguyen17/ga100-fuse-re ahnguyen17/ga100-fuse-re] (FF instruction layout, RIR macro, the
corrected Gen3 burn list, the 80 GiB fold). Use it as a cross-check before trusting any burn list; the repo's own verdict
on burning a working card is NO-GO. {{Source|exile_1ck|2026-10-07|https://github.com/ahnguyen17/ga100-fuse-re}}

== Status ==

VBIOS editing can change power/clocks (reported); it cannot do the memory/compute/PCIe unlock (that is driver-side).
Flashing modified or third-party ROMs is a warning, not a recommendation. Flashing the factory 300 W image onto an 8 GB card is a different matter: proven on eight cards, see [[Flashing the 300 W VBIOS]].

== Related ==

[[RIR fuse burn]], [[Which card do I have]], [[Driver unlock]], [[NVLink]], [[Troubleshooting]], [[Tools]].

{{ImportFooter}}
[[Category:Unlocks]]
[[Category:8 GB]]
[[Category:10 GB]]

Flashing the 300 W VBIOS

2026-10-31T13:21:34Z

Most 8 GB cards ship with VBIOS 92.00.67.00.01, the 250 W image. On it the driver reports a GPC and memory VF-offset
range of [0 .. +0], so no undervolt can be applied, whatever a tool says it set. The factory 300 W image
92.00.6D.00.0A, which NVIDIA shipped on the same board part number (900-11001-0108-000), exposes an offset range of
[-1000 .. +1000], boots the HBM at 1728 MHz instead of 1458 MHz, raises the SM ceiling from 1410 to 1695 MHz, and
keeps a 250 W default cap (300 W is the maximum it allows). This page is the flash procedure as run on eight cards in
one night, with the numbers before and after. It does not touch the memory or compute unlock, which stays in the
driver; see [[Driver unlock]].

The 10 GB card has no 300 W image (its only VBIOS is 92.00.66.00.02); this page is for 8 GB cards. See
[[VBIOS and firmware]] for the full image inventory.

== Why flash it ==
=== The 250 W image has no undervolt lever ===
<code><nowiki>nvml_oc -i N</nowiki></code> (the helper 170tune uses) reports <code><nowiki>allowed range : [0 .. +0] MHz</nowiki></code>
for both the GPC and the memory VF offset on every 92.00.67.00.01 card. An offset call can return success and the
driver still drops it; only a readback proves it applied. On the same cards after the flash the range reads
[-1000 .. +1000].

{{Status|Proven}} {{Cards|8 GB}} 
{{Source|handle=mrpec|date=2026-08-01|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1533150703328039085}} 
{{Source|handle=unmotivatedgene|date=2026-08-23|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1541201873803943997}} 
{{Source|handle=darkmaniac7|date=2026-10-31|note=lab notes}}

=== Same board, same IDs ===
Both images carry device 10DE:20C2, subsystem 10DE:1585 and board ID 0x030A, and both have been read off cards with
board part number 900-11001-0108-000 and die 20C2-105-A1. nvflash accepts the 300 W image on a 250 W card without any
override because the IDs match; it is a signed NVIDIA image, not a modified one.

{{Status|Reported}} {{Cards|8 GB}} 
{{Source|handle=con3po7016|date=2026-08-23|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1541194940997046322}} 
{{Source|handle=wakeupmbrc1|date=2026-08-30|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1543658140875235459}}

== Before you start ==
# '''An 8 GB card on 92.00.67.00.01.''' Read it with <code><nowiki>nvidia-smi --query-gpu=index,pci.bus_id,vbios_version --format=csv</nowiki></code>. A card already on 92.00.6D.00.0A has nothing to gain.
# '''nvflash 5.867 for Linux''', the <code><nowiki>x64/nvflash</nowiki></code> binary from the TechPowerUp download (the zip holds x86, x64, aarch64 and ppc64 builds; the Windows zip is a different download).
# '''The ROM''', TechPowerUp VBIOS database entry 268495 (listed there as "CMP 170HX 0 MB"; the size column is wrong). Verify it before it goes near a card: see below. A copy is attached to this page.
# '''A rollback ROM.''' Save one card's 92.00.67.00.01 image with <code><nowiki>nvflash -i N --save</nowiki></code> before you write anything. The static part of the image is identical across cards of the same version, so one dump serves as the rollback for all of them.
# '''A way to power the machine off and on''' that does not depend on the GPUs: a BMC, or someone at the button. The procedure needs two cold cycles, and a wedged flash controller only clears on a cold cycle.
# '''The driver unloaded, or never loaded.''' nvflash refuses to write with the NVIDIA kernel module present. The method below boots without it, which also avoids the unbind hang described further down.

== Verify the ROM ==
The TechPowerUp file matched these values exactly:
{| class="wikitable"
! Field !! Value
|-
| Version || 92.00.6D.00.0A
|-
| Build / modification date || 06/16/21 / 04/07/22
|-
| Size || 1,044,480 bytes
|-
| Device / subsystem / board ID || 0x20C2 / 0x1585 / 0x030A
|-
| MD5 || a58aae86e72b13d50603c15653350664
|-
| SHA1 || efad37d514bb94ac345719a0c56d9cd147cddfb7
|-
| SHA256 || 789e8f8d4c70dc9eb114c9fdcef6ed2d00aedf15a1eca522519de02042818723
|}
Two checks that do not depend on a hash:
* <code><nowiki>nvflash --version 300w.rom</nowiki></code> reads the header from the file only (it does not touch a card) and must print the version, device, subsystem and board IDs above, and <code><nowiki>License Placeholder : Present</nowiki></code>.
* <code><nowiki>python3 check_rom.py 300w.rom --expect 300W</nowiki></code> (attached) checks the structural markers: the NVGI header, the 300 W power bytes <code><nowiki>E0 93 04</nowiki></code> at 0x46045, the strap tier byte 0x44 at 0x41F53 (0x66 there means a forged "64 GB" ROM that bricks the card at boot), an all-zero license region at 0xFE504, and the dual-bank mirror. The same script recognises the 250 W image (<code><nowiki>--expect 250W</nowiki></code>) for checking your rollback dump.

{{Status|Reported}} {{Cards|8 GB}} 
{{Source|repo=https://github.com/polyuij42-del/cmp170hx-vbios-flash}} 
{{Source|repo=https://github.com/Consensus-Protocol/cmp170hx}}

== The procedure (driverless boot) ==
Proven on eight cards in two rounds, 2026-10-31, on a bare-metal Ubuntu box with the cmpunlocker driver build 615.71.09,
BMC power control and the tooling attached below. Every write took about 10 seconds. Read the two rules first:

* '''One nvflash operation per card per boot.''' After a power-on, the first nvflash command that touches a card's flash controller (<code><nowiki>--check</nowiki></code>, <code><nowiki>--save</nowiki></code> or a write) works; a second one on the same card fails with <code><nowiki>Falcon In HALT or STOP state</nowiki></code> or <code><nowiki>Detecting GPU failed</nowiki></code> and nothing is written. So the rollback save comes from a card you are not writing in that boot (or from an earlier boot), and the write is the first and only thing you do to each target card. A PCIe remove and rescan of one device (<code><nowiki>echo 1 > /sys/bus/pci/devices/0000:XX:00.0/remove; echo 1 > /sys/bus/pci/rescan</nowiki></code>) re-opened the window once in the lab; do not count on it.
* '''nvflash 5.867 ignores <code><nowiki>-y</nowiki></code> and refuses piped input.''' The confirm prompt needs a real terminal. It prints the card's current and replacement version strings before the prompt, and the PCI bus only in its Results table after the operation, so the attached controller confirms on the version strings (current must be 92.00.67.00.01, replacement 92.00.6D.00.0A) and checks the bus afterwards. nvflash's <code><nowiki>-i</nowiki></code> index follows PCI bus order, the same order <code><nowiki>nvidia-smi</nowiki></code> uses with <code><nowiki>CUDA_DEVICE_ORDER=PCI_BUS_ID</nowiki></code>; the Results table confirmed <code><nowiki>-i 7</nowiki></code> = bus C2 on the lab box.

Steps:
# Stop everything that holds the GPUs (engines, miners), until <code><nowiki>lsof /dev/nvidia*</nowiki></code> shows nothing. Record every card's VBIOS version.
# Keep the driver out of the next boot: <code><nowiki>/etc/modprobe.d/zz-flash-window.conf</nowiki></code> with <code><nowiki>install nvidia /bin/false</nowiki></code> (and the same for nvidia_modeset, nvidia_drm, nvidia_uvm). Mask or disable the units that would start GPU work at boot (docker, miners, any model loader). Note what you changed.
# Cold cycle: power off, 30 seconds dark, power on. Confirm <code><nowiki>lsmod | grep nvidia</nowiki></code> is empty and that the cards are enumerated with no driver bound.
# Save the rollback ROM from a card you will not write this boot: <code><nowiki>nvflash -i N --save backup.rom</nowiki></code>, then <code><nowiki>check_rom.py backup.rom --expect 250W</nowiki></code>.
# Write each target card once: <code><nowiki>nvflash -i N 300w.rom</nowiki></code>, answer <code><nowiki>y</nowiki></code> at the prompt (or let the attached controller do it). Success looks like a progress bar to 100 %, two verification reads, and <code><nowiki>A reboot is required for the update to take effect.</nowiki></code> with exit code 0. Anything else: do not retry that card this boot.
# Remove the blacklist, restore the units, cold cycle again.
# Verify: <code><nowiki>nvidia-smi --query-gpu=index,vbios_version,memory.total,clocks.max.memory,power.default_limit,power.max_limit --format=csv</nowiki></code> should show 92.00.6D.00.0A, your unlocked memory size, 1728 MHz, 250 W default and 300 W maximum; <code><nowiki>nvml_oc -i N</nowiki></code> should show the [-1000 .. +1000] range.

The attached <code><nowiki>window.sh</nowiki></code> runs those phases (<code><nowiki>check</nowiki></code>, <code><nowiki>prep</nowiki></code>, <code><nowiki>flash</nowiki></code>, <code><nowiki>restore</nowiki></code>, <code><nowiki>verify</nowiki></code>) with the lab box's unit names and bus map; edit those before using it elsewhere.

{{Status|Proven}} {{Cards|8 GB}} 
{{Source|handle=darkmaniac7|date=2026-10-31|note=lab notes}} 
{{Source|repo=https://github.com/polyuij42-del/cmp170hx-vbios-flash}}

=== Why not unbind the driver instead ===
The repository above spent eighteen script versions on the unbind route. With any process still holding
<code><nowiki>/dev/nvidia*</nowiki></code>, <code><nowiki>echo ... > /sys/bus/pci/drivers/nvidia/unbind</nowiki></code> hangs in the driver's remove path and never
returns; on one of its two cards it hung even with zero handles open, and a <code><nowiki>reboot</nowiki></code> issued in that state stalled the
machine until someone cut the power. Booting with the modules blacklisted sidesteps all of it.

{{Status|Warning}} {{Cards|8 GB}} 
{{Source|repo=https://github.com/polyuij42-del/cmp170hx-vbios-flash}}

=== Others who flashed it with nvflash ===
Several owners did the same flash with stock nvflash before the lab did, on Linux and on Windows; none reported a
brick from it. The bricks reported on the server came from fuse burns, SPI strap edits and A100 cross-flashes, not from
this image.

{{Status|Reported}} {{Cards|8 GB}} 
{{Source|handle=c133|date=2026-08-23|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1541187172588326962}} 
{{Source|handle=c133|date=2026-08-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1542649519739769003}} 
{{Source|handle=shirogeek|date=2026-09-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1546191972392501369}} 
{{Source|handle=derick2k|date=2026-09-06|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1546163237186441286}} 
{{Source|handle=phoenixone7|date=2026-09-16|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1549930400707514490}} 
{{Source|handle=wakeupmbrc1|date=2026-08-30|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1543658182298173581}}

== Results on eight cards ==
Two of the eight (bus 41 and C1) have FBPA0 fused off (one dead HBM stack each). Both took the image and initialised
cleanly at 1728 MHz; the driver log after the flash matched the log before it line for line in shape (the unlock's
privilege-mask loop prints 54 "Booter failed" lines per card on every boot; that is normal, not damage).

{| class="wikitable"
! Card (bus) !! VBIOS after !! Memory !! Max mem clock !! Default / max cap !! Offset range !! Note
|-
| 0 (01) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 ||
|-
| 1 (22) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 ||
|-
| 2 (41) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 || FBPA0 fused
|-
| 3 (61) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 ||
|-
| 4 (81) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 ||
|-
| 5 (A1) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 ||
|-
| 6 (C1) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 || FBPA0 fused
|-
| 7 (C2) || 92.00.6D.00.0A || 65536 MiB || 1728 MHz || 250 / 300 W || -1000 .. +1000 || first attempt aborted by the controller, window re-opened by a PCIe rescan, second write fine
|}
Zero Xids, zero ECC errors, zero RmInitAdapter failures across four cold cycles.

{{Status|Proven}} {{Cards|8 GB}} 
{{Source|handle=darkmaniac7|date=2026-10-31|note=lab notes}}

== What it changed ==
The load is a proof-of-work miner (pearlhash, OneZeroMiner) on all eight cards with the fan wall at 15 % and caps set
per card by a thermal governor (230 to 250 W). The rejected shares below were all "Stale share" (a share submitted after
the pool changed the job: timing, not a wrong answer); there were no invalid shares.

{| class="wikitable"
! State !! Total hashrate !! Core clock range !! Temps !! Notes
|-
| 250 W image, offset 0 || 1,455 TH/s || 1215 to 1290 MHz || 70 to 79 C || baseline, same caps
|-
| 300 W image, offset 0 || 1,459 to 1,470 TH/s || 1215 to 1290 MHz || 70 to 79 C || HBM 1728 MHz cost nothing on a compute load
|-
| 300 W image, GPC offset +100 || 1,525 TH/s || 1275 to 1365 MHz || unchanged || 20 min soak, 0 Xid
|-
| 300 W image, GPC offset +130 || 1,549 TH/s || 1290 to 1380 MHz || unchanged || 20 min soak, 0 Xid
|-
| 300 W image, GPC offset +160 || 1,564 TH/s || 1335 to 1410 MHz || unchanged || 20 min soak, 0 Xid; cool-slot cards at the 1410 MHz ceiling
|}
Power draw stayed at the caps the whole time: the offset lets the core hold a higher clock at the same watts, so the
gain comes with no extra heat. Two cards were held back early by a stale share each (a rule that counted any rejected
share; it should count only invalid ones); they sit at +50 and +80 until re-run.

{{Status|Proven}} {{Cards|8 GB}} 
{{Source|handle=darkmaniac7|date=2026-10-31|note=lab notes}}

== Risks and what the community saw ==
* {{Status|Warning}} One owner advised against the 300 W image because a photo of a burned 170HX had been posted earlier and the board lacks some power-delivery parts of the full layout. The photo is not in the exported history and no post ties a burned card to this image. The image's own default is 250 W; nothing on the lab box sets 300 W, and the undervolt reduces current at a given cap rather than raising it. Keep your cap at or below 250 W until you have a reason and the cooling to go higher. {{Source|handle=xanthefin|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561336153515364444}}
* {{Status|Contested}} HBM at 1728 MHz: one owner on the 300 W image with a 250 W limit passed GPU-burn with no errors but saw sporadic Vulkan memtest errors across the HBM dies; the eight lab cards (Hynix) ran clean. If a card misbehaves at 1728 MHz, 170tune can set the memory clock back down (not on FBPA0-fused cards, where the PLL tool must not write). {{Source|handle=cute_sc2|date=2026-08-08|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1535648815456198667}} {{Source|handle=darkmaniac7|date=2026-10-31|note=lab notes}}
* {{Status|Warning}} A failed flash is recoverable only with an SPI programmer with a 1.8 V adapter (the flash IC is 1.8 V; some "3.3 V" CH341A units put out 5 V, so a CH347 unit whose software selects the voltage is the safer buy). Power loss during the write and the wrong file are the two real ways to get there; both are yours to prevent. {{Source|repo=https://github.com/Consensus-Protocol/cmp170hx}}

== Rollback ==
The same procedure with your saved 92.00.67.00.01 dump as the image: one write per card in a driverless boot, then a
cold cycle. The lab keeps its dump with the rest of the evidence; any card's dump of the same version works for any
card of the same version.

== Files ==
* {{Download|file=CMP170HX_92.00.6D.00.0A.rom|compact=yes}} The 300 W image, byte-identical to TechPowerUp 268495 (hashes above).
* {{Download|file=Vbios_check_rom.py|compact=yes}} Structural ROM check (MIT, from polyuij42-del/cmp170hx-vbios-flash).
* {{Download|file=Vbios_flash_one.py|compact=yes}} The pty controller that answers nvflash's prompt only after it has echoed the expected versions, and checks the bus afterwards.
* {{Download|file=Vbios_window.sh.gz|compact=yes}} The lab's phase script (gzipped: the wiki refuses a shebang script under a plain extension) (check, prep, flash, restore, verify); unit names and bus map are the lab box's.

== Related ==
[[VBIOS and firmware]], [[Undervolting and power limits]], [[Driver unlock]], [[170tune]], [[Troubleshooting]].

{{ImportFooter}}
[[Category:Unlocks]]
[[Category:8 GB]]
[[Category:Cooling and power]]

File:Vbios window.sh.gz

2026-10-31T13:21:31Z

ImportBot: Upload for Flashing the 300 W VBIOS (lab notes; source on the file page)

{{Download|version=2026-10-31|source=[https://cmp.wiki/wiki/Flashing_the_300_W_VBIOS Flashing the 300 W VBIOS]}}
Phase script for the driverless-boot VBIOS window (check, prep, flash, restore, verify) as run on the lab eight-card box; unit names and the index-to-bus map are that box's, edit before reuse. Gzipped because the wiki refuses a shebang script under any plain extension: gunzip after download. From [[Flashing the 300 W VBIOS]].

File:Vbios flash one.py

2026-10-31T13:20:40Z

ImportBot: Upload for Flashing the 300 W VBIOS (lab notes; sources on the file page)

{{Download|version=2026-10-31|source=[https://cmp.wiki/wiki/Flashing_the_300_W_VBIOS Flashing the 300 W VBIOS]}}
Drives one nvflash write or save through a pty and answers the confirm prompt only after nvflash has echoed the expected current and replacement versions; checks the PCI bus from the Results table afterwards. Lab tool written for [[Flashing the 300 W VBIOS]].

File:Vbios check rom.py

2026-10-31T13:20:39Z

ImportBot: Upload for Flashing the 300 W VBIOS (lab notes; sources on the file page)

{{Download|version=2026-09-26|source=[https://github.com/polyuij42-del/cmp170hx-vbios-flash polyuij42-del/cmp170hx-vbios-flash on GitHub]}}
Structural check of a CMP 170HX VBIOS image (250 W or 300 W build): NVGI header, power bytes, strap tier, license region, dual-bank mirror. MIT licence, unmodified copy of scripts/check_rom.py. Used on [[Flashing the 300 W VBIOS]].

File:CMP170HX 92.00.6D.00.0A.rom

2026-10-31T13:20:39Z

ImportBot: Upload for Flashing the 300 W VBIOS (lab notes; sources on the file page)

{{Download|version=92.00.6D.00.0A|source=[https://www.techpowerup.com/vgabios/268495/268495 TechPowerUp VBIOS database 268495]}}
300 W factory VBIOS 92.00.6D.00.0A for the 8 GB CMP 170HX, byte-identical to TechPowerUp VBIOS database entry 268495 (MD5 a58aae86e72b13d50603c15653350664, SHA1 efad37d514bb94ac345719a0c56d9cd147cddfb7). Signed NVIDIA image, unmodified. Read [[Flashing the 300 W VBIOS]] before using it.

DeepSeek V4.1 Flash heretic on 4x 8 GB

2026-10-30T10:36:53Z

ImportBot: Import: the lab recipe (lab notes, 2026-10-29): Morrowmake dsv41-flash-cmp170hx-recipe 1.0.0 with pqhaz's heretic patch written into the official checkpoint in place; sources: @darkmaniac7; GitHub Morrowmake/dsv41-flash-cmp170hx-recipe

{{Recipe
|model=DeepSeek-V4.1-Flash-1017 heretic (pqhaz abliteration)
|quant=Hybrid: routed experts EXL3 2.9 bpw (LibertAIDAI), everything else official FP8/BF16 with the 38 heretic attn.wo_b tensors
|engine=Morrowmake/vllm-cmp170hx (vLLM fork, container image)
|engine_version=recipe 1.0.0 (commit d4d1f525), engine a0c57b52
|cards=8 GB
|card_count=4
|topology=TP4
|context=262,144
|decode_tps=158
|prefill_tps=2453
|vram_per_card=64 GiB, --gpu-memory-utilization 0.92 (miner co-resident)
|flags=EXTRA_ARGS="--gpu-memory-utilization 0.92", VLLM_ENGRAM_PLACEMENT=ssd, CUDA_DEVICE_ORDER=PCI_BUS_ID
|status=Reported
|tested_by=darkmaniac7
|tested_on=2026-10-29
|source=https://github.com/Morrowmake/dsv41-flash-cmp170hx-recipe
}}
Morrowmake's recipe for DeepSeek-V4.1-Flash on four CMP 170HX, unchanged except for a few <code><nowiki>.env</nowiki></code> lines, with
pqhaz's heretic patch written into the official checkpoint in place. Nothing was retrained or requantized. The result
answers prompts the stock model refuses, keeps tool calls and long-context copying accurate, and reasons longer.
{{Source|handle=darkmaniac7|date=2026-10-29|note=lab notes}}

== Parts (pinned) ==
{| class="wikitable"
! Part !! Source !! Pin
|-
| Recipe || [https://github.com/Morrowmake/dsv41-flash-cmp170hx-recipe Morrowmake/dsv41-flash-cmp170hx-recipe] || commit <code><nowiki>d4d1f525</nowiki></code> (release 1.0.0)
|-
| Engine image || <code><nowiki>ghcr.io/morrowmake/vllm-cmp170hx</nowiki></code> || <code><nowiki>sha256:f67d9be47ffbd4a8b84c77fe76bdb3f842187d9b2786fff573e390ae5361bfb0</nowiki></code> (vLLM fork Morrowmake/vllm-cmp170hx at <code><nowiki>a0c57b52</nowiki></code>)
|-
| Routed experts || [https://huggingface.co/LibertAIDAI/DeepSeek-V4.1-Flash-1017-EXL3-2.9bpw LibertAIDAI/DeepSeek-V4.1-Flash-1017-EXL3-2.9bpw] || EXL3 2.9 bpw, about 211 GB
|-
| Everything else || [https://huggingface.co/deepseek-ai/DeepSeek-V4.1-Flash-1017 deepseek-ai/DeepSeek-V4.1-Flash-1017] || official FP8/BF16, about 510 GB
|-
| Abliteration || [https://huggingface.co/pqhaz/DeepSeek-V4.1-Flash-1017-heretic pqhaz/DeepSeek-V4.1-Flash-1017-heretic], <code><nowiki>patch/</nowiki></code> folder only || 38 tensors, 1.6 GB; Ivan's copy sha256 <code><nowiki>16e63cd3e79c3590855aad340b5b9dc37f27562bf2d0a40f85268915da221ce2</nowiki></code>
|}
{{Source|handle=darkmaniac7|date=2026-10-29|note=lab notes}}

== Why an in-place patch is enough ==
The recipe's <code><nowiki>download.sh</nowiki></code> fetches both checkpoints and builds <code><nowiki>DeepSeek-V4.1-Flash-1017-hybrid-exl3-fp8</nowiki></code>,
a directory of links. The routed experts (<code><nowiki>layers.N.ffn.experts.*</nowiki></code>) come from the EXL3 export; every other
tensor, attention included, is a link to the official shards.

The heretic edit only touches <code><nowiki>layers.2-39.attn.wo_b.weight</nowiki></code>. Each edited tensor keeps the same FP8 dtype, shape
and byte offset, and the block scales are untouched. Those tensors live in the official shards, so overwriting them
there makes the served hybrid heretic with no rebuild. The heretic release leaves the routed experts alone (their FP4
storage cannot hold the edit), so it combines cleanly with the 2.9 bpw EXL3 experts.
{{Source|handle=darkmaniac7|date=2026-10-29|note=lab notes}}

== Steps ==
# Do the recipe's one-time host setup, clone it and run <code><nowiki>./install.sh</nowiki></code>, as its README says. Prerequisites are those of [[DeepSeek V4.1 Flash on 4x 8 GB (Morrowmake)]].
# <code><nowiki>./download.sh</nowiki></code> fetches both checkpoints and builds the hybrid. Budget about 680 GiB.
# Fetch the patch only: <syntaxhighlight lang="bash" inline>hf download pqhaz/DeepSeek-V4.1-Flash-1017-heretic --include "patch/*" --local-dir heretic</syntaxhighlight>
# Write it into the official checkpoint in place with <code><nowiki>heretic_inplace.py</nowiki></code> (below, stdlib Python only):
#: {{Download|file=Heretic_inplace.py|compact=yes}} The script applies the heretic patch to the official shards in place, restores them byte-exact from the backup, or reports their status.
<syntaxhighlight lang="bash">
python3 heretic_inplace.py apply <MODELS_DIR>/DeepSeek-V4.1-Flash-1017 heretic/patch/<file>.safetensors stock-wo_b-backup.safetensors
python3 heretic_inplace.py status <same three args> # expect: heretic 38, stock 0, other 0
python3 heretic_inplace.py restore <same three args> # undo, byte-exact
</syntaxhighlight>
#: <code><nowiki>apply</nowiki></code> first saves the 38 stock tensors to the backup file (1.6 GB), then overwrites each tensor, fsyncs and reads it back. It refuses any shard that has other hard links, so it cannot patch a second copy by accident. Re-running it does nothing.
#: To avoid patching in place, the heretic repo's own <code><nowiki>ds_patch.py apply <official> <patch> <new_dir></nowiki></code> writes a patched copy instead. It rewrites 38 full shards (about 7 GB each, roughly 260 GB extra) and hard-links the rest. Put that copy under the official checkpoint's directory name: the hybrid's links resolve by that name, and the index and config the builder checks are unchanged.
# <code><nowiki>.env</nowiki></code> changes, all specific to Ivan's box:
#* <code><nowiki>CUDA_VISIBLE_DEVICES=4,5,6,7</nowiki></code> and <code><nowiki>CUDA_DEVICE_ORDER=PCI_BUS_ID</nowiki></code>, because this runs on four cards of an 8-card machine. The recipe does not pass <code><nowiki>CUDA_DEVICE_ORDER</nowiki></code> into the container, so it was added to <code><nowiki>CONTAINER_KEYS</nowiki></code> in <code><nowiki>start.sh</nowiki></code> (a one-word change). On a 4-card box you need neither.
#* <code><nowiki>EXTRA_ARGS="--gpu-memory-utilization 0.92"</nowiki></code>, only because a miner shares the cards and holds 2.5 GiB on each. At the default 0.95 a 17k-token prefill ran out of memory. With nothing else on the cards, keep the default.
#* <code><nowiki>VLLM_ENGRAM_PLACEMENT=ssd</nowiki></code> (default <code><nowiki>auto</nowiki></code>) keeps the Engram tables on SSD instead of in RAM. If you have the RAM, <code><nowiki>auto</nowiki></code> is fine.
#* <code><nowiki>PORT</nowiki></code> and <code><nowiki>SERVED_MODEL_NAME</nowiki></code> are cosmetic.
# <code><nowiki>./start.sh</nowiki></code>, then <code><nowiki>./start.sh smoke</nowiki></code> (one chat request and one tool call).
{{Source|handle=darkmaniac7|date=2026-10-29|note=lab notes}}

== Measured numbers ==
On Ivan's box: four CMP 170HX on PCIe, sharing the machine with a miner, measured with his own bench script. Not
comparable with the numbers the recipe publishes.
{| class="wikitable"
! !! Result
|-
| Decode, 1 user || code 158, structured 136, prose 121 tok/s
|-
| Decode, 8 users (total) || code 323, structured 261, prose 249 tok/s
|-
| Prefill, 17k-token prompt (warm) || 2,453 tok/s
|-
| Long-context copy accuracy (75k to 92k-token roleplay turns that must copy image paths and names exactly) || 1 wrong of 30. The miss picked a different variant of the right image, not a garbled path
|-
| Same 2.9 bpw expert files on a different engine (GNmac) || 85% wrong on the same test. So that engine causes the copy errors, not the quant or the heretic edit
|-
| Refusal spot check (4 prompts, 1,500-token cap) || 2 answered, 2 hit the cap while still reasoning, 0 refused
|-
| Tool calls (<code><nowiki>deepseek_v41</nowiki></code> parser) || work
|}
The heretic model card reports 1 refusal in 100 held-out prompts (base: 97) and KL 0.136 on harmless prompts.
An earlier run under the same conditions read 150 / 131 / 117 tok/s for one user (code / structured / prose); the GNmac engine on the same cards read 248 / 177 / 135 and 542 / 396 / 347 at 8 users, prefill 2,697.
{{Source|handle=darkmaniac7|date=2026-10-29|note=lab notes}} 
{{Source|handle=darkmaniac7|date=2026-10-29|note=lab notes}}

== Things to know ==
* It reasons much longer after the edit. The model card puts the median completion at 1,517 tokens against 357 for the base. Set <code><nowiki>max_tokens</nowiki></code> generously, or <code><nowiki>content</nowiki></code> comes back empty with <code><nowiki>finish_reason: "length"</nowiki></code>.
* No capability benchmarks have been run on the heretic version, Ivan's or the model card's. KL 0.136 means general behaviour has shifted somewhat.
* Speed is engine-bound. On Ivan's box the GNmac engine decodes 1.1 to 1.7x faster (prefill 1.1x) but corrupts long-context copying, so he kept Morrowmake. See [[DeepSeek V4.1 Flash on 4x 8 GB (GNmac)]].
* Uncensored EXL3 bundles whose edit lives in dense tensors do nothing on the GNmac engine, which takes dense tensors from the official checkpoint; the heretic patch works on both engines because it patches those official tensors. {{Source|handle=darkmaniac7|date=2026-10-28|note=lab notes}}
{{Source|handle=darkmaniac7|date=2026-10-29|note=lab notes}}

== Checks ==
* After applying the patch Ivan checked the weights: the dequantize/requantize round trip reproduces 100.00% of the original FP8 codes; 92-99% of the patched codes are within one FP8 step of the ideal rank-1 edit; the change is 3.7-4.7% of the weight norm on all 38 tensors. Nothing beyond the advertised edit plus rounding is visible.
* After any restart, confirm which checkpoint the container actually loaded (<code><nowiki>docker inspect <container> --format '{{.Args}}'</nowiki></code>): one reload silently came up on the stock hybrid.
* {{Status|Contested}} Capability: the write-up above says no capability benchmarks have been run on the heretic version. Ivan's chassis notes also cite independent numbers for this layout (GSM8K and HumanEval unchanged, MMLU -0.4, HarmBench compliance 287 of 300 against 30 of 300 stock) without naming who measured them.
{{Source|handle=darkmaniac7|date=2026-10-29|note=lab notes}}

== heretic_inplace.py ==
Ivan's helper, stdlib Python only. It applies or undoes the patch in the official shards for engines that read
attention weights straight from the official checkpoint (Morrowmake).
<syntaxhighlight lang="python">
#!/usr/bin/env python3
"""Apply (or undo) the pqhaz heretic patch IN PLACE in the official DeepSeek-V4.1-Flash-1017 shards, for engines that
read attention weights straight from the official checkpoint (Morrowmake). Only the 38 `layers.N.attn.wo_b.weight`
tensors change (same dtype F8_E4M3, same shape, same offsets); FP8 scales are untouched, as the patch was built.

heretic_inplace.py apply OFFICIAL_DIR PATCH.safetensors BACKUP.safetensors
heretic_inplace.py restore OFFICIAL_DIR PATCH.safetensors BACKUP.safetensors
heretic_inplace.py status OFFICIAL_DIR PATCH.safetensors BACKUP.safetensors

apply: writes an exact byte backup of every original tensor first (a safetensors file with the same names), then
overwrites, fsyncs and reads back; refuses a shard with more than one hard link. restore: writes the backup back.
Idempotent: a tensor already in the wanted state is skipped. Stdlib only."""
import hashlib, json, os, struct, sys

def header(path):
with open(path, "rb") as f:
n = struct.unpack("<Q", f.read(8))[0]
h = json.loads(f.read(n))
return h, 8 + n

def region(path, name):
h, base = header(path)
t = h[name]
a, b = t["data_offsets"]
return t["dtype"], t["shape"], base + a, b - a

def read_at(path, off, size):
with open(path, "rb") as f:
f.seek(off)
return f.read(size)

def sha(b):
return hashlib.sha256(b).hexdigest()

def write_safetensors(path, tensors): # tensors: name -> (dtype, shape, bytes)
hdr, off = {}, 0
for k in sorted(tensors):
dt, shp, data = tensors[k]
hdr[k] = {"dtype": dt, "shape": shp, "data_offsets": [off, off + len(data)]}
off += len(data)
hb = json.dumps(hdr, separators=(",", ":")).encode()
hb += b" " * ((8 - len(hb) % 8) % 8)
tmp = path + ".tmp"
with open(tmp, "wb") as f:
f.write(struct.pack("<Q", len(hb)) + hb)
for k in sorted(tensors):
f.write(tensors[k][2])
f.flush(); os.fsync(f.fileno())
os.replace(tmp, path)

def main():
mode, odir, patch, backup = sys.argv[1:5]
wm = json.load(open(os.path.join(odir, "model.safetensors.index.json")))["weight_map"]
ph, _ = header(patch)
names = sorted(k for k in ph if k != "__metadata__")
plan = []
for k in names:
shard = os.path.join(odir, wm[k])
dt, shp, off, size = region(shard, k)
pdt, pshp, poff, psize = region(patch, k)
assert (dt, shp, size) == (pdt, pshp, psize), (k, dt, shp, size, pdt, pshp, psize)
plan.append((k, shard, off, size, poff))
print(f"{len(plan)} tensors in {len({p[1] for p in plan})} shards")

if mode == "status":
bh = header(backup)[0] if os.path.exists(backup) else {}
n_patched = n_stock = n_other = 0
for k, shard, off, size, poff in plan:
cur = sha(read_at(shard, off, size))
if cur == sha(read_at(patch, poff, size)): n_patched += 1
elif bh and cur == sha(read_at(backup, region(backup, k)[2], size)): n_stock += 1
else: n_other += 1
print(f"heretic {n_patched}, stock (matches backup) {n_stock}, other {n_other}")
return

if mode == "apply":
for k, shard, *_ in plan:
assert os.stat(shard).st_nlink == 1, f"{shard} has other hard links; refusing to write in place"
if not os.path.exists(backup):
orig = {}
for k, shard, off, size, poff in plan:
data = read_at(shard, off, size)
if data == read_at(patch, poff, size):
sys.exit(f"{k} is already patched and there is no backup: refusing (stock bytes unknown)")
orig[k] = (region(shard, k)[0], region(shard, k)[1], data)
write_safetensors(backup, orig)
print(f"backup written: {backup} ({os.path.getsize(backup) / 2**30:.2f} GiB)")
src = lambda k, poff, size: read_at(patch, poff, size)
elif mode == "restore":
assert os.path.exists(backup), "no backup"
src = lambda k, poff, size: read_at(backup, region(backup, k)[2], size)
else:
sys.exit("mode: apply | restore | status")

done = skipped = 0
for k, shard, off, size, poff in plan:
want = src(k, poff, size)
if read_at(shard, off, size) == want:
skipped += 1; continue
fd = os.open(shard, os.O_RDWR)
try:
assert os.pwrite(fd, want, off) == size
os.fsync(fd)
finally:
os.close(fd)
assert sha(read_at(shard, off, size)) == sha(want), f"read-back mismatch on {k}"
done += 1
print(f"{mode}: {done} written, {skipped} already in place, all read back OK")

if __name__ == "__main__":
main()
</syntaxhighlight>
{{Source|handle=darkmaniac7|date=2026-10-29|note=lab notes}}

== Credits ==
DeepSeek for the model. Morrowmake for the recipe and the Ampere vLLM fork. LibertAI for the EXL3 2.9 bpw quant. pqhaz
for the heretic ablation of 1017. p-e-w for the Heretic method.

== Related ==
* The base recipe: [[DeepSeek V4.1 Flash on 4x 8 GB (Morrowmake)]]. Other heretic and abliterated variants: [[Quantization on the 170HX]].
* [[Engines]], [[Benchmarks]], [[Recipes]].

== Sources ==
* Ivan's lab notes, 2026-10-29 (public write-up of the recipe).
* The script is [[:File:Heretic_inplace.py]]; its sha256 is shown in the Download box in the Steps section.

{{ImportFooter}}
[[Category:8 GB]]

Template:Download

2026-10-30T10:29:25Z

ImportBot: Wiki lane: Download box shows KB below 1 MB

<includeonly><templatestyles src="Infobox/styles.css" />{{#if:{{#cmpfile:{{{file|{{PAGENAME}}}}}|size}}|{{#ifeq:{{lc:{{{compact|}}}}}|yes|[[Media:{{{file|{{PAGENAME}}}}}|{{{file|{{PAGENAME}}}}}]] ({{#ifexpr:{{#cmpfile:{{{file|{{PAGENAME}}}}}|size}} < 1048576|{{#expr:{{#cmpfile:{{{file|{{PAGENAME}}}}}|size}}/1024 round 1}} KB|{{#expr:{{#cmpfile:{{{file|{{PAGENAME}}}}}|size}}/1048576 round 2}} MB}}, by @{{#cmpfile:{{{file|{{PAGENAME}}}}}|uploader}}, [[:File:{{{file|{{PAGENAME}}}}}|details]]) <code>sha256 {{#cmpfile:{{{file|{{PAGENAME}}}}}|sha256}}</code>|<div class="cmpw-download">
'''Download:''' [[Media:{{{file|{{PAGENAME}}}}}|{{{file|{{PAGENAME}}}}}]] ({{#ifexpr:{{#cmpfile:{{{file|{{PAGENAME}}}}}|size}} < 1048576|{{#expr:{{#cmpfile:{{{file|{{PAGENAME}}}}}|size}}/1024 round 1}} KB|{{#expr:{{#cmpfile:{{{file|{{PAGENAME}}}}}|size}}/1048576 round 2}} MB}}) 
'''Version:''' {{{version|not given}}} 
'''Upstream source:''' {{#if:{{{source|}}}|{{{source}}}|not given}} 
'''sha256:''' {{#cmpfile:{{{file|{{PAGENAME}}}}}|sha256}}{{#if:{{{expected_sha256|}}}|{{#ifeq:{{lc:{{{expected_sha256}}}}}|{{#cmpfile:{{{file|{{PAGENAME}}}}}|sha256}}| (matches the hash published upstream)| (does NOT match the hash published upstream: {{{expected_sha256}}})}}}} 
'''Uploaded by:''' @{{#cmpfile:{{{file|{{PAGENAME}}}}}|uploader}} on {{#time:Y-m-d H:i|{{#cmpfile:{{{file|{{PAGENAME}}}}}|timestamp}}}} UTC
{{#if:{{{notes|}}}| {{{notes}}}}}
</div>}}|File not uploaded yet{{#if:{{{file|}}}|: {{{file}}}}}.}}{{#ifeq:{{NAMESPACENUMBER}}|6|[[Category:Downloads]]}}</includeonly><noinclude>
Download block for hosted binaries, archives and scripts (uploads of sh, py, zip, gz, tgz, xz, run, deb, bin, rom by the
trusted group must carry it on their file page).

The sha256, size, uploader and upload time are read from the stored file by the wiki itself, so a swapped file shows a
different hash at once. Give <code>version</code> and <code>source</code> (the upstream release link); give
<code>expected_sha256</code> when the upstream project publishes one, and the block says whether the hosted file matches.

On a file page:
<pre>{{Download|version=1.2.3|source=https://github.com/OWNER/REPO/releases/tag/v1.2.3|expected_sha256=...}}</pre>
Elsewhere (for example in [[Template:Unlock]]): <code><nowiki>{{Download|file=Example.zip|compact=yes}}</nowiki></code>.
[[Category:Templates]]</noinclude>

File:Heretic inplace.py

2026-10-30T10:28:08Z

ImportBot: heretic_inplace.py (2026-10-29), the lab, MIT

'''heretic_inplace.py''' applies the pqhaz "heretic" FP8 patch to the <code>attn.wo_b</code> weights of the official
DeepSeek V4.1 Flash shards, in place, for engines that read attention weights straight from the official checkpoint.
Only the 38 <code>layers.N.attn.wo_b.weight</code> tensors change (same dtype F8_E4M3, same shape, same offsets); the
FP8 scales are untouched. Three commands: <code>apply</code>, <code>restore</code> and <code>status</code>. Python
standard library only.

{{Download|version=2026-10-29|source=[https://cmp.wiki/wiki/User:Darkmaniac7 Ivan's lab (@darkmaniac7)]|expected_sha256=5c2e6a96b424ba5c6b2983bf06953704f0dd63e51c3beb5ef25e5a73cea44343|notes=Used by [[DeepSeek V4.1 Flash heretic on 4x 8 GB]].}}

== Usage ==
<pre>
heretic_inplace.py apply OFFICIAL_DIR PATCH.safetensors BACKUP.safetensors
heretic_inplace.py restore OFFICIAL_DIR PATCH.safetensors BACKUP.safetensors
heretic_inplace.py status OFFICIAL_DIR PATCH.safetensors BACKUP.safetensors
</pre>
* <code>OFFICIAL_DIR</code>: the official DeepSeek-V4.1-Flash-1017 checkpoint (with <code>model.safetensors.index.json</code>).
* <code>apply</code> first writes an exact byte backup of every original tensor (a safetensors file with the same names),
then overwrites, fsyncs and reads back. It refuses a shard that has more than one hard link, and refuses to run when
a tensor is already patched and there is no backup.
* <code>restore</code> writes the backup back; <code>status</code> counts tensors that are patched, stock (match the
backup) or neither. Both are safe to repeat: a tensor already in the wanted state is skipped.

== License ==
MIT (the file carries no license header).

{{Source|darkmaniac7|2026-10-29|note=lab notes}}

Rumours and claims to verify

2026-10-30T10:12:24Z

Claims made on the cmpunlocker Discord that nobody has reproduced. None of them is a result. Each entry gives the claim, who made it and when (in the credit line), what would settle it, and the board card if there is one. Where another page already covers the claim with its sources, the entry is short and links there.

* {{Status|Theory}} on this page: a claim with no evidence posted and no second person.
* {{Status|Contested}}: people disagree. Both sides are listed in the order they were posted, with no verdict.
* To settle one, post the evidence on Discord with the card variant, driver and method, and move the card on the [https://cmp.wiki/board/ board]. A settled claim moves to the page it belongs on.

Firmware and VBIOS claims appear here only as claims. This wiki does not carry keys, decryption or ways around NVIDIA's firmware protection.

== Memory ==

=== 8 GB card at 80 or 96 GB ===
On 2026-10-09 @ob88594 posted a Xianyu listing photo of cards marked 80G and 96G, whose CUDA count matched 128 SMs. His informant said they were 8 GB cards; later he added that the card in the photo "has not been shipped" and that the third party only sells a 10 GB unlock. A vendor advert quoted by @analyticeth said the 8 GB modification was "still under development, with major breakthroughs already achieved". Nobody posted a card, a dump or a buyer. In the order posted:
* The informant says the marked cards are 8 GB cards. {{Source|handle=ob88594|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558079963129978955}} {{Source|handle=ob88594|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558084426003382275}} {{Source|handle=ob88594|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558114667325423759}}
* In theory an 8 GB card could go to 96 GB. {{Source|handle=wakeupmbrc1|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558172335633211645}}
* The vendor advert's line on the 8 GB card. {{Source|handle=analyticeth|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558168218487623782}}
* Without a signed VBIOS @globalapathy does not see how it would be possible. {{Source|handle=globalapathy|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558682168983818333}}
* @djpandaman: in theory 96 GB on some cards and 80 GB on most; the maximum confirmed on a production 8 GB card is 64 GB. {{Source|handle=djpandaman|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559044323545456671}}
'''What would settle it.''' An 8 GB card (<code><nowiki>10de:20c2</nowiki></code>) showing more than 65024 MiB in nvidia-smi and passing a dense unique-data write and read-back over all of it, with the method posted. 
'''Board.''' D-072 and D-056 (Dev and research), T-029 (CMP testing) on the [https://cmp.wiki/board/ board]. 
More: [[8 GB card#Memory]].

{{Status|Contested}} {{Cards|8 GB}}

=== A screenshot showing 130104 MB (192 GB) on one card ===
A screenshot in the "Unlock 80GB stable ram on 10G version" feature-request channel appeared to show 130104 MB of VRAM, which some read as 192 GB on one card. In the order posted:
* "i thought it was 192g". {{Source|handle=squishysquare|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1534858283138158697/1560151279618101299}}
* The per-stack arithmetic (25.6 or 21.3 GB per stack) makes no sense. {{Source|handle=squishysquare|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1534858283138158697/1560165956494557257}}
* "VRAM 130104 MB= 65024 MiB x2 = 2x 64GB unlocked 8GB model": two unlocked 8 GB cards reported together. {{Source|handle=kio063218|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1534858283138158697/1560618333542293526}}
* "Fake pic." {{Source|handle=reggie7756|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1534858283138158697/1561867918864814234}}
'''What would settle it.''' A single-GPU <code><nowiki>nvidia-smi -q</nowiki></code> from the card in question. For comparison, an unlocked 8 GB card reports 65024 MiB. 
'''Board.''' T-032 (CMP testing) on the [https://cmp.wiki/board/ board]. 
More: [[Memory unlock on the 10 GB card#80 / 96 GB: not real on these dies]].

{{Status|Contested}} {{Cards|both}}

=== 80 GB working on the 10 GB card ===
In the order posted:
* Miséricorde relayed community research that memory above 40 GB "reads and returns meaningful values". {{Source|handle=wakeupmbrc1|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559709514553622549}}
* Some people had cards reading 80 GB, but the memory was unstable. @djpandaman linked a Chinese write-up, "170Hx 10G解锁80G探索" (10G unlock to 80G, an exploration), at [https://blog.kkk.rs/archives/71 blog.kkk.rs]. {{Source|handle=tekkenz|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559048743947341955}} {{Source|handle=djpandaman|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559050324411420762}}
* @colo2442 gets folding (aliasing) in every experiment, including physical accesses that bypass L2, unless a further unlock frees address bit 14. He asked for the serial number of any card said to work above 40 GB. {{Source|handle=colo2442|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559906143373885462}}
* Miséricorde: the "no folding" statement came from community research, not his own tests. {{Source|handle=wakeupmbrc1|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559906356889387049}}
* @lycorascence recalled papers that got 80 GB working on a 10 GB card at lower memory speed; Miséricorde: "they actually were not"; @scallion_9883: "I believe it is aliasing in L2 now also". {{Source|handle=lycorascence|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560782124049760389}} {{Source|handle=wakeupmbrc1|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560782191628259379}} {{Source|handle=scallion_9883|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560782273652195479}}
* @ob88594: the "special initialization" the paper mentions is still missing for a full 10 GB unlock. {{Source|handle=ob88594|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564546224567361578}}
'''What would settle it.''' A dense unique-data write and read-back above 40 GiB on a named 10 GB card (serial posted), with no folding and no Xid. 
'''Board.''' T-026 and T-027 (CMP testing), D-055 (Dev and research) on the [https://cmp.wiki/board/ board]. 
More: [[Memory unlock on the 10 GB card#80 / 96 GB: not real on these dies]].

{{Status|Contested}} {{Cards|10 GB}}

=== 48 GB on most 10 GB cards ===
In the order posted:
* @cuddylac997 posted ten 10 GB cards in one host, "ready to run 48gb on each one of these!", and said a 48 GB mode had not been released "but it can be figured out". {{Source|handle=cuddylac997|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1556837488541311058}} {{Source|handle=cuddylac997|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1557230581346213909}}
* @djpandaman: "48 max on some. most cards 40. looking like around 20%". {{Source|handle=djpandaman|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559042465758060625}}
* Miséricorde listed "48g on some (most cards)" among what the 10 GB card can do. {{Source|handle=wakeupmbrc1|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559705158961864908}}
* @djpandaman: 6 of 30 cards he saw tested could do 48 GB. {{Source|handle=djpandaman|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560920383782260797}}
'''What would settle it.''' gpcprobe's FBP disable and defective readout plus the unlock result for each 10 GB card owners have. 
'''Board.''' T-004 (CMP testing), D-027 (Dev and research) on the [https://cmp.wiki/board/ board]. 
More: [[Memory unlock on the 10 GB card#48 GB (the 6th stack, if it is good)]].

{{Status|Contested}} {{Cards|10 GB}}

=== Unlocked 8 GB memory is failure-prone ===
In the order posted:
* "No amount of software can make up for the fact that this was lower binned and prone to failure memory that nvidia had to fuse off." {{Source|handle=_____josh_____|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556569848069357612}}
* @jjb01957: his card's VRAM runs fine and, apart from speed, no different from his 5090. {{Source|handle=jjb01957|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556571811884310612}}
* Miséricorde: "every card runs on ndiv=68 as minimum". {{Source|handle=wakeupmbrc1|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556575473343922237}}
'''What would settle it.''' Failure statistics: cards, hours in service, memtest error counts. 
'''Board.''' T-030 and T-115 (CMP testing) on the [https://cmp.wiki/board/ board]. 
More: [[8 GB card#Memory]].

{{Status|Contested}} {{Cards|8 GB}}

=== The "defective" HBM stacks are good memory ===
In the order posted:
* A theory @n2dcrypt relayed from another chat: the same stacks are always marked defective because the HBM package height was wrong and they run hotter, so they may not be faulty memory. @globalapathy: at lower voltage and under water they could work, just not optimally. {{Source|handle=n2dcrypt|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558184726261399553}} {{Source|handle=globalapathy|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558185847654842420}}
* Petri Krohn: "Almost every 8GB card has FBP 6 and FBP 11 marked as *defective*. This cannot be true!" He reads it as two stages of disabling. {{Source|handle=petrikrohn_26497|date=2026-10-10|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558302260088545361}}
* @djpandaman: in his experience a part marked defective is truly defective, while a disabled part can be enabled. {{Source|handle=djpandaman|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561028809237602389}}
* @lxtend on 10 GB stacks: "they are mostly good even its labeled as defective". {{Source|handle=lxtend|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562165620693274655}}
'''What would settle it.''' One marked-defective stack enabled and memtested, at reduced clocks if needed. On the 8 GB card nobody has a way to enable it. 
'''Board.''' T-029 and T-133 (CMP testing), D-056 (Dev and research) on the [https://cmp.wiki/board/ board]. 
More: [[8 GB card#Memory]], [[10 GB card#Memory]].

{{Status|Contested}} {{Cards|both}}

=== Most cards reach 1.9 to 2.0 TB/s with HBM tuning ===
@zorg33 believes most cards can reach 1.9 to 2.0 TB/s with HBM fine tuning (he wrote "TH/s"), which he says would scale TP4 decode to 550-600 tok/s. Miséricorde: a 10 GB card with all six stacks would have a 6144-bit bus and "can run 2.5tbps+". No tuned bandwidth figure at that level has been posted. The highest posted so far: 1,741 GB/s on an unlocked 10 GB card at stock, and the NDIV results on [[8 GB card#Memory]]. 
'''What would settle it.''' HBM bandwidth and gpu-burn correctness at NDIV 70 and 73 on several cards; bandwidth on a 48 GB 10 GB card. 
'''Board.''' T-143 and T-028 (CMP testing) on the [https://cmp.wiki/board/ board]. 
More: [[Undervolting and power limits#HBM clock (NDIV) and refresh]].

{{Status|Theory}} {{Cards|both}} 
{{Source|handle=zorg33|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1556935579919187989}} 
{{Source|handle=wakeupmbrc1|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557273045259919401}} 
{{Source|handle=cuddylac997|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1557370302042738759}}

=== "ECC Enabled" after v0.5 means errors are corrected ===
In the order posted:
* @zombielurker: nvidia-smi says ECC is enabled, even on his RTX 3090s, but it corrected none of about 5,000 single-bit errors one card throws in memtest_vulkan; gpu-burn behaved the same. {{Source|handle=zombielurker|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556515369286504489}}
* Ivan's lab notes: the "ECC Enabled" readout comes from cmpunlocker's reporting patch; no corrected-error counter has been shown moving. {{Source|handle=darkmaniac7|date=2026-10-21|note=lab notes}}
* @cute_sc2, arguing the 170HX is no different from an A30 or A100 for serving: "We even have ecc now." {{Source|handle=cute_sc2|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563235845409087609}}
'''What would settle it.''' One corrected DRAM error shown on a counter that is not set by the reporting patch. 
'''Board.''' T-001 (CMP testing), D-032 (Dev and research) on the [https://cmp.wiki/board/ board]. 
More: [[ECC#Does it correct errors? (contested)]].

{{Status|Contested}} {{Cards|both}}

== SM and clocks ==

=== The 8 GB card can go past 74 SMs ===
In the order posted:
* Miséricorde: every RIR entry except the last reads all ones on the 8 GB card, so it cannot be overridden "without signed falcon code". {{Source|handle=wakeupmbrc1|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557273300986765383}} {{Source|handle=wakeupmbrc1|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557273462647558188}}
* @sojun80: "thats just software looking at it and setting a flag in init". {{Source|handle=sojun80|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557273393814835203}}
* @matstatman installed an 8 GB card with 0 defective GPCs that passed the standard 5-minute test. Miséricorde: "if 0 defective then 128"; matstatman: "sooner or later, we will be able to enable them". {{Source|handle=matstatman|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558242733242720267}} {{Source|handle=wakeupmbrc1|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558244852561612811}} {{Source|handle=matstatman|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558245242472239157}}
* @mountains1605: the path is clear for 10 GB cards, not for 8 GB cards. {{Source|handle=mountains1605|date=2026-10-10|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558307001061089391}}
* @replacedriver47: fuses are read and passed on by software, so it is software-unlockable in theory, "but it would require bypassing security mechanisms". {{Source|handle=replacedriver47|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1564590115722895434}}
'''What would settle it.''' An 8 GB card (<code><nowiki>10de:20c2</nowiki></code>) running more than 74 SMs, with the method posted. 
'''Board.''' D-072 and D-084 (Dev and research) on the [https://cmp.wiki/board/ board]. 
More: [[Full SM unlock#Why the 8 GB card cannot go past 74]], [[8 GB card#Limits]].

{{Status|Contested}} {{Cards|8 GB}}

=== OpenGL on unlocked cards ("opengl with ecc") ===
Asked whether OpenGL is actually enabled on these cards, @matstatman said his coding agent had offered to enable it that day: "opengl with ecc, huang level". Nothing was shown afterwards. 
'''What would settle it.''' <code><nowiki>glxinfo</nowiki></code> output or an OpenGL program running on an unlocked 170HX, with driver and patch named. 
'''Board.''' T-021 (CMP testing), D-087 (Dev and research) on the [https://cmp.wiki/board/ board]. 
More: [[Other CMP cards and other NVIDIA GPUs]] (graphics on a 170HX).

{{Status|Theory}} {{Cards|both}} 
{{Source|handle=phoenixone7|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556811290419404862}} 
{{Source|handle=matstatman|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556811828364054529}} 
{{Source|handle=matstatman|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556811981405692056}}

=== RT cores unlocked ("It's done.") ===
The only message in the feature-request channel "Unlock RT cores for CMP cards that have them" is @emogop's "It's done." with no details, link or proof. It may mean the unlock was done or that the request was closed. 
'''What would settle it.''' emogop's explanation, or a ray-tracing workload with numbers on a CMP card. 
'''Board.''' T-022 (CMP testing) on the [https://cmp.wiki/board/ board].

{{Status|Theory}} {{Cards|both}} 
{{Source|handle=emogop|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1549439096072700094/1563775342114639989}}

== PCIe and P2P ==

=== PCIe Gen4 x16 and "A100 PRO" screenshots ===
Screenshots collected in [https://github.com/amoghmunikote/cmpunlocker/issues/9 cmpunlocker issue #9] show (a) a Chinese marketplace listing for an in-person "170hx to A100 PRO" hard-mod service in Chengdu, three cards minimum, 10 GB cards first, with a card reported as an A100-PCIE-40GB with 126 SMs, 40960 MiB, PCIe Gen4 x16 and ECC on; and (b) a tweet showing a card with 65536 MiB at PCIe Gen4 x16 and 300 W. Neither names a method, and no second person has seen such a card. In the order posted:
* @matstatman posted the tweet ("Oh no, more rumors"), then screenshots of screenshots and a further comment on issue #9. {{Source|handle=matstatman|date=2026-10-10|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558556627261595768}} {{Source|handle=matstatman|date=2026-10-10|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558561426619105280}} {{Source|handle=matstatman|date=2026-10-10|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558561741133062186}}
* @matstatman: "I think it is a case of old screenhots being mixed". {{Source|handle=matstatman|date=2026-10-10|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558559268741980282}}
* @port00: "Looks like 8GB version"; @dottoreargus: "and an account created today". {{Source|handle=port00|date=2026-10-10|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558578917068251157}} {{Source|handle=dottoreargus|date=2026-10-10|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558588174643494923}}
* Ivan's notes on issue #9: the listing renames the card's device ID, which the public tools do not do; the issue is still open. {{Source|handle=darkmaniac7|date=2026-10-18|note=lab notes}}
The Chengdu service may be the same as the paid 10 GB unlock below; nothing confirms it. 
'''What would settle it.''' <code><nowiki>lspci -vv</nowiki></code> showing <code><nowiki>LnkSta: Speed 16GT/s, Width x16</nowiki></code> on both ends for a card the poster owns, with the method named. 
'''Board.''' D-065 (Dev and research), T-005 (CMP testing) on the [https://cmp.wiki/board/ board].

{{Status|Contested}} {{Cards|both}}

=== PCIe 4.0, ECC, NVLink and twice the SMs on the 8 GB card ===
In the order posted:
* @endsjeremy: PCIe 4.0 was "pretty definitively off the table without some way to sign the driver". {{Source|handle=endsjeremy|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558697247439593475}}
* @ob88594: there are two separate "8G cracked" reports, a team in Chengdu and someone in this channel. {{Source|handle=ob88594|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558697827461238854}}
* @douya4305: "8g card can also unlock pcie4.0, ecc,nvlink" and "2X sm is on the road"; asked, "right ,just not public". {{Source|handle=douya4305|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559706643380445285}} {{Source|handle=douya4305|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559706873228304415}} {{Source|handle=douya4305|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559707094683361371}}
* Miséricorde: "no", "at least not public", "thats all really rumored". {{Source|handle=wakeupmbrc1|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559706884829880433}} {{Source|handle=wakeupmbrc1|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559707273058586697}}
* @lia_oc: ECC is done in v0.5; the others are not public. {{Source|handle=lia_oc|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559708664175263932}}
* @tarxlazer: "The 8g card of cmp170 unlocks the full core and pcie4. I hope it will come soon." {{Source|handle=tarxlazer|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559908881138982993}}
'''What would settle it.''' An 8 GB card with an 8 or 16 GT/s LnkSta, an active NVLink in <code><nowiki>nvidia-smi nvlink -s</nowiki></code>, or more than 74 SMs. 
'''Board.''' D-072 (Dev and research), T-011 (CMP testing) on the [https://cmp.wiki/board/ board]. 
More: [[8 GB card#Limits]].

{{Status|Contested}} {{Cards|8 GB}}

=== PCIe Gen3 on an 8 GB card, release promised for 2026-12-09 ===
@rrickk420 (Rickcal) said he sees three paths ("RIR, Samsung memory & falcon") and "I already have gen 3 8GB". He would not share it yet because he does not want to fry people's cards, and said he would release it on 2026-12-09 if nothing else came out by then. The next day he said only some cards can do single-fuse Gen3. The same week @djpandaman mentioned that someone said they had Gen3 on an 8 GB card. No numbers, LnkSta or method were posted. 
'''What would settle it.''' The release, or <code><nowiki>lspci -vv</nowiki></code> showing 8 GT/s on an 8 GB card. 
'''Board.''' D-059 (Dev and research) on the [https://cmp.wiki/board/ board]. 
More: [[8 GB card#Limits]] (what the fuse readouts show).

{{Status|Theory}} {{Cards|8 GB}} 
{{Source|handle=rrickk420|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558121601181163732}} 
{{Source|handle=rrickk420|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558122896143155303}} 
{{Source|handle=rrickk420|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558123540425736354}} 
{{Source|handle=djpandaman|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558265701947416597}} 
{{Source|handle=rrickk420|date=2026-10-10|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558607148727017485}}

=== PCIe Gen4 on the 10 GB card ===
@arabus_74064 posted a screenshot of a 170HX at PCIe x16 4.0; @bigptoughneigh said it was a 10 GB card with "All the RiR" done. @djpandaman said he has Gen3 and "validated gen 4 on my plx" (his motherboard is Gen3). @cute_sc2 answered yes when asked whether the 10 GB card can use PCIe 4. Gen3 on the 10 GB card is published and reproduced; Gen4 is not: no 16 GT/s LnkSta and no recipe has been posted. @lxtend has Gen3 confirmed, says Gen4 needs "some tricky way to retrain", and has no Gen4 slot to test it. 
'''What would settle it.''' <code><nowiki>lspci -vv</nowiki></code> showing 16 GT/s x16 on a cap-modded 10 GB card in a Gen4 slot, plus a bandwidth test. 
'''Board.''' T-005 and T-118 (CMP testing), D-028 (Dev and research) on the [https://cmp.wiki/board/ board]. 
More: [[10 GB card#PCIe]], [[PCIe Gen3 on the 10 GB card]].

{{Status|Theory}} {{Cards|10 GB}} 
{{Source|handle=arabus_74064|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556807631165726720}} 
{{Source|handle=bigptoughneigh|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556833016741896336}} 
{{Source|handle=djpandaman|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558112557628133498}} 
{{Source|handle=lxtend|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560186430628831343}} 
{{Source|handle=cute_sc2|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1560422460568899615}}

=== PCIe 5.0 on the 170HX ===
In the order posted:
* The author of the CMP 100-210 unlock repository claimed PCIe 5.0 on the 170HX in a [https://github.com/amoghmunikote/cmpunlocker/issues/9#issuecomment-5607224444 comment on cmpunlocker issue #9]; @68x0 pointed to it: "I wouldn't trust any of this AI slop from this person". {{Source|handle=68x0|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558131626922344510}}
* Amogh (@_j3ns), the cmpunlocker author: "Exactly why I banned them!" {{Source|handle=_j3ns|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558136539966611477}}
'''What would settle it.''' <code><nowiki>lspci -vv</nowiki></code> showing a 32 GT/s link on a 170HX. Nobody has posted one. 
More: [[Other CMP cards and other NVIDIA GPUs#CMP 100HX (100-210)]].

{{Status|Contested}} {{Cards|both}}

=== NVLink working on a 170HX ===
@djpandaman said on 2026-10-12 he was still getting NVLink to work on his 10 GB cards and "it looks like it will". The paid 10 GB unlock was offered with "nvlink for extra" (see below). On 2026-10-23 @bigptoughneigh said NVLink "works fine, but requires a very simple hardware mod (easier than the x16 mod). It's not my finding to share though." No <code><nowiki>nvidia-smi nvlink</nowiki></code> output, photo or method has been posted. @lia_oc (2026-10-22): no NVLink yet, "not even for 10GB that's public"; @ob88594 (2026-10-24): "8G still hasn't been unlocked". 
'''What would settle it.''' <code><nowiki>nvidia-smi nvlink -s</nowiki></code> showing active links on a bridged pair and a P2P bandwidth test over the bridge. 
'''Board.''' D-025 and D-026 (Dev and research), T-011 (CMP testing) on the [https://cmp.wiki/board/ board]. 
More: [[NVLink#Status of the hardware mod]].

{{Status|Theory}} {{Cards|both}} 
{{Source|handle=djpandaman|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1559037159841988619}} 
{{Source|handle=lia_oc|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562930961207922811}} 
{{Source|handle=bigptoughneigh|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1563312993414946827}} 
{{Source|handle=ob88594|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1563650116756447233}}

== Firmware and VBIOS ==

=== Paid 10 GB unlock for about 500 USD in Chengdu ===
Relaying an informant, @ob88594 said a third party sells a paid 10 GB unlock: "$500, get more than A100 40G PCIE, nvlink for extra", in Chengdu. @aaasss1456 said a friend "went to the factory and made a 10g card", that it "displays as an a100" with "8912 cuda core" (a full 128-SM GA100 has 8192), and that it cost nearly 500 USD. @analyticeth quoted the vendor's advert: all changes are permanent inside the card, no unlock software or driver patches are needed, and the card behaves like an original A100. Miséricorde read it as an RIR macro burn. No buyer has posted <code><nowiki>lspci</nowiki></code>, <code><nowiki>nvidia-smi -q</nowiki></code> or a fuse dump from such a card. 
'''What would settle it.''' A buyer posting <code><nowiki>lspci -nn</nowiki></code>, <code><nowiki>nvidia-smi -q</nowiki></code> and a gpcprobe dump of a card that went through the service. 
'''Board.''' D-065 (Dev and research) on the [https://cmp.wiki/board/ board]. 
More: [[10 GB card#Buying]].

{{Status|Theory}} {{Cards|10 GB}} 
{{Source|handle=ob88594|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558116548130906113}} 
{{Source|handle=ob88594|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558162519070216295}} 
{{Source|handle=aaasss1456|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558164230073753630}} 
{{Source|handle=aaasss1456|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558164394951573627}} 
{{Source|handle=analyticeth|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558168182563545140}} 
{{Source|handle=wakeupmbrc1|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558168562542317812}} 
{{Source|handle=aaasss1456|date=2026-10-10|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558296445835026556}} 
{{Source|handle=aaasss1456|date=2026-10-10|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558296562550177795}}

=== Unlocks sold as a service, with cards as payment ===
@ob88594's account of the Chinese market: merchants pay unlockers in cards ("The fewer you break, the higher your reward"), then sell unlocking as a service. The unlock merchants on Xianyu took their service down after someone bought out the capacity, and the 10 GB unlock had circulated since early August among merchants who bought the information, which he says is why unknown buyers took the 10 GB cards. Only his informant photographed an "80G version", and the unlocker gave no details. For the 8 GB card there was "no public information" from the Chinese side. 
'''What would settle it.''' A listing, receipt or buyer report for the service. 
'''Board.''' D-065 (Dev and research) on the [https://cmp.wiki/board/ board].

{{Status|Theory}} {{Cards|10 GB}} 
{{Source|handle=ob88594|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1559044923804745809}} 
{{Source|handle=ob88594|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1559045338587865239}} 
{{Source|handle=ob88594|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1559045761071714396}} 
{{Source|handle=ob88594|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1559047009523081310}} 
{{Source|handle=ob88594|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1559188709918900286}}

=== 20 donor cards, 5 bricked during the 10 GB work ===
In the order posted:
* @ob88594, marked as hearsay: private groups get free hardware from merchants in exchange for early information; "the 10G unlock came about because a merchant gave them 20 cards; 5 were bricked during testing". {{Source|handle=ob88594|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558091916409839727}}
* Miséricorde relayed it in #hardware and guessed they tried enabling defective blocks or stacks. {{Source|handle=wakeupmbrc1|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558111527498686525}} {{Source|handle=wakeupmbrc1|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558111592527175701}}
* @djpandaman does not see how a cold reset would not recover a card: his sixth-stack errors that day always cleared on a cold boot. He agreed that doing unlocks one at a time through RIR can get you into trouble. {{Source|handle=djpandaman|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558111882181611665}} {{Source|handle=djpandaman|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558111963199053878}}
'''What would settle it.''' One of the bricked cards, with what was written to it. 
'''Board.''' T-024 and T-036 (CMP testing) on the [https://cmp.wiki/board/ board]. 
More: [[Driver and unlock failures#Bricked cards during 10 GB development (hearsay)]], [[RIR fuse burn]].

{{Status|Contested}} {{Cards|10 GB}}

=== A private unlock from "a guy with 400 cards" ===
On 2026-10-17, while the channel discussed whether anyone has NVIDIA's signing keys, Miséricorde said a private unlock result he had seen came from "guy with 400 cards" who "doesnt sell", and that "either tool is real or someone got the keys". The regulars answered that nobody on the server has them. @djpandaman: "be cautious, it's easier to fake a screenshot when there's money on the table than to do it legitimately." Which card and what result were not posted. 
'''What would settle it.''' The tool, or its result on a second owner's card. 
'''Board.''' D-065 (Dev and research) on the [https://cmp.wiki/board/ board].

{{Status|Theory}} {{Cards|both}} 
{{Source|handle=wakeupmbrc1|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561027185760805055}} 
{{Source|handle=wakeupmbrc1|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561027322071748679}} 
{{Source|handle=wakeupmbrc1|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561027370603905046}} 
{{Source|handle=djpandaman|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561027460177334314}} 
{{Source|handle=djpandaman|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561027717825036463}}

=== An earlier private "dirty" unlock under NDA ===
@zingy90210 (PJ) said a talk Petri Krohn gave covered NVIDIA's firmware signing, that "Petri, Jon and 3 others managed to do 'dirty' work and unlock it. Think NVIDIA made jon sign an NDA", and that they are now trying to turn their process into a clean unlock. He gave no link to the talk, and nobody corroborated it. Petri Krohn is on the server and can be asked directly. 
'''What would settle it.''' A link to the talk, or Petri Krohn's own account. 
'''Board.''' D-065 (Dev and research) on the [https://cmp.wiki/board/ board].

{{Status|Theory}} {{Cards|both}} 
{{Source|handle=zingy90210|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561265184918474953}} 
{{Source|handle=zingy90210|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561265407153938543}} 
{{Source|handle=zingy90210|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561265556248854569}}

=== A local model re-derived the v0.5 patch ===
In the order posted:
* @exile_1ck: when he asked Claude to install v0.5, it found that his local Qwen 3.8 Flash Next, told to reverse engineer the BIOS with [https://github.com/morluto/rea morluto/rea], had produced the same patch the day before. He added that the model also made Strata faster than he had seen it run unmodified. {{Source|handle=exile_1ck|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557239693043699736}} {{Source|handle=exile_1ck|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557239965161619547}} {{Source|handle=exile_1ck|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557240827267387422}}
* @djpandaman: "did it actually unlock it from scratch or did it just use the ecc branch before it was merged to master branch". eXile: "i am not entirely sure". {{Source|handle=djpandaman|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557240393169379330}} {{Source|handle=exile_1ck|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557240683666866237}}
'''What would settle it.''' The model's diff and session log, compared with the upstream ECC branch. 
'''Board.''' D-066 (Dev and research) on the [https://cmp.wiki/board/ board].

{{Status|Contested}} {{Cards|10 GB}}

=== Unlocks have permanent effects ===
@rrickk420 said on 2026-10-09 that since June his theory has been that someone would "sneak in brick fuse burns" into an unlock. On 2026-10-25 @stcord posted an X post by unixpickle with "Question everything, folks"; @segmond then said he would not unlock anything more until he is sure there are no permanent effects. The post's content is not in the Discord export. For context, the [[Driver unlock]] page states that cmpunlocker flashes and burns nothing, while the [[RIR fuse burn]] on 10 GB cards is permanent by design. 
'''What would settle it.''' The post's actual claim, or a fuse dump taken before and after a plain cmpunlocker install and a cold boot. 
'''Board.''' D-115 (Dev and research) on the [https://cmp.wiki/board/ board].

{{Status|Theory}} {{Cards|both}} 
{{Source|handle=rrickk420|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558124756312653966}} 
{{Source|handle=stcord|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1564038044032434186}} 
{{Source|handle=segmond|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1564044324793221302}}

=== A VBIOS TOCTOU test damaged a card for good ===
@youngju10000 (영쥬) wrote that he "saw in a post" that a VBIOS TOCTOU test caused permanent damage that restoring the original BIOS did not fix. The post was not linked and has not been found in the export. 
'''What would settle it.''' The original post. 
More: [[VBIOS and firmware]].

{{Status|Theory}} {{Cards|both}} 
{{Source|handle=youngju10000|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557647494417088513}}

=== An unlocked VBIOS for the 10 GB card ===
In the order posted:
* @supasnipa360: "hearing its been done for the 10gb variant as well but a harder find it seems due to legal concerns". {{Source|handle=supasnipa360|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561388811123167233}}
* @xanthefin: the unlock makes no VBIOS change in the first place. @globalapathy: someone able to write a VBIOS would not have stopped at 64 GB. {{Source|handle=xanthefin|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561391210906517565}} {{Source|handle=globalapathy|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561391800818733068}}
'''What would settle it.''' The file, compared with the stock 10 GB VBIOS (92.00.66.00.02). 
More: [[VBIOS and firmware#The "64 GB unlocked VBIOS" repos (bogus)]].

{{Status|Contested}} {{Cards|10 GB}}

=== Why driver-loaded VBIOS overrides work (Petri Krohn's explanation) ===
Petri Krohn posted "Ampere VBIOS modding explained", an account of why the driver can hand the GPU's microcontrollers modified VBIOS data. It is an explanation, not a measurement, and nobody has checked it against a dump. 
'''What would settle it.''' A dump that confirms or corrects it. 
'''Board.''' T-016 (CMP testing), D-060 (Dev and research) on the [https://cmp.wiki/board/ board]. 
More: [[VBIOS and firmware#Background: why driver-loaded overrides work (Petri Krohn)]].

{{Status|Theory}} {{Cards|both}} 
{{Source|handle=petrikrohn_26497|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562075696380248065}}

=== A complete 10 GB unlock exists privately ===
On 2026-10-07 Miséricorde said the 10 GB card "can be unlocked into full ga100": 128 SMs, 48 GB, six-stack bandwidth, "nvlink and 4.0 also"; 40 to 48 GB is "legit", 80 GB a "big maybe". The same day @cuddylac997 posted overnight tests of unlocked 10 GB cards, measured 1,741 GB/s, and said "There's no releasing it" and "not every card unlocks the same or in the same way". Since then the 128-SM unlock and Gen3 on the 10 GB card have been published and reproduced (see [[Full SM unlock]] and [[PCIe Gen3 on the 10 GB card]]). The NVLink and PCIe 4.0 parts of the claim have not been shown. 
'''What would settle it.''' See the Gen4 and NVLink entries above. 
'''Board.''' D-073, D-025 and D-028 (Dev and research) on the [https://cmp.wiki/board/ board].

{{Status|Theory}} {{Cards|10 GB}} 
{{Source|handle=wakeupmbrc1|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557244521992163329}} 
{{Source|handle=wakeupmbrc1|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557244574802513951}} 
{{Source|handle=wakeupmbrc1|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557244637893230603}} 
{{Source|handle=wakeupmbrc1|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557244790720962611}} 
{{Source|handle=cuddylac997|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1557367784130875396}} 
{{Source|handle=cuddylac997|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1557368521179275275}} 
{{Source|handle=cuddylac997|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1557461273518547055}}

== Cooling and power ==

=== The 300 W VBIOS burned a card ===
Asked about running the 300 W VBIOS, @xanthefin said a picture of a burned 170HX had already been posted on the Discord, and, from memory, that the PCB is missing power-delivery parts. The picture has not been found in the export. The 300 W VBIOS exists for the 8 GB card only. 
'''What would settle it.''' The original picture and post, with the card's VBIOS and power setup. 
'''Board.''' D-090 (Dev and research) on the [https://cmp.wiki/board/ board]. 
More: [[Power and cabling warnings#The 300 W VBIOS has burned a 170HX]].

{{Status|Theory}} {{Cards|8 GB}} 
{{Source|handle=xanthefin|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561336153515364444}} 
{{Source|handle=xanthefin|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561336277280759879}}

=== An unreleased "high power mode" ===
@matstatman: "I found a high power mode that you can enable, even on 8gb. No idea what it does so will not release." Nothing more has been posted. 
'''What would settle it.''' matstatman's description of the setting and a measurement with it on and off. 
'''Board.''' D-090 (Dev and research) on the [https://cmp.wiki/board/ board]. 
More: [[8 GB card#Limits]], [[Undervolting and power limits]].

{{Status|Theory}} {{Cards|both}} 
{{Source|handle=matstatman|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562174089920258139}}

=== Arctic fans wired onto the stock shroud are quieter ===
@danske1 has heard of people wiring Arctic fans onto the card and that "it's much quieter", but does not know what the wiring involves or how the temperatures compare. Nobody has posted a build. 
'''What would settle it.''' Noise and core and HBM temperatures at a fixed power limit, before and after. 
'''Board.''' T-048 (CMP testing) on the [https://cmp.wiki/board/ board]. 
More: [[Fans and ducts]].

{{Status|Theory}} {{Cards|both}} 
{{Source|handle=danske1|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564217476542365770}} 
{{Source|handle=danske1|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564224983301881968}}

== Recipes and speed ==

=== 4.5M tokens of KV cache for GLM-5.3-Flash on 4 cards ===
In the order posted:
* Miséricorde: "with 4 gpus you have w4a16 + 4.5m kv". {{Source|handle=wakeupmbrc1|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1560673558122987571}}
* @cibernox, running the 4-card recipe daily: "I only have 1.2M". {{Source|handle=cibernox|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1560682309978427494}}
'''What would settle it.''' The vLLM startup line together with KV dtype, layout and maximum sequence count. 
'''Board.''' T-069 (CMP testing) on the [https://cmp.wiki/board/ board]. 
More: [[GLM 5.3 Flash on 4x 8 GB#KV cache and context]].

{{Status|Contested}} {{Cards|8 GB}}

=== 225 tok/s on Qwen 3.8 27B with one card ===
In the order posted:
* @feralzi: "I was able to reach 225 tks on 3.8 27b". {{Source|handle=feralzi|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559796537935142963}}
* @matstatman: "Its dflash and temp set to 0 i think, nothing you want to code with". {{Source|handle=matstatman|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559942424833429586}}
'''What would settle it.''' The same run with and without the draft model, at temperature 0 and at a normal temperature. 
'''Board.''' T-158 and T-034 (CMP testing) on the [https://cmp.wiki/board/ board]. 
More: [[Qwen3.8 27B on 1x 8 GB (W4A16 vLLM)#Measured numbers]].

{{Status|Contested}} {{Cards|8 GB}}

=== Single-card Qwen 3.8 Flash Next numbers on a custom vLLM build ===
In the order posted:
* @exile_1ck posted screenshots of a single 64 GB card running a Q3 quant of Qwen 3.8 Flash Next on a "custom vllm build aimed at the 170hx". {{Source|handle=exile_1ck|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560340926998515827}} {{Source|handle=exile_1ck|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560342257532674060}}
* @xtj7 gets about 90 tok/s decode and 1600 tok/s prefill with Strata on one card at IQ2 without the x16 mod, called eXile's prefill "awfully high" and wondered whether it includes cache hits. @okrasit. asked whether the prefill was reported correctly, @shudza asked for the context size. No answers were posted. {{Source|handle=xtj7|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560350518847479850}} {{Source|handle=okrasit.|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560352574673260585}} {{Source|handle=xtj7|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560352992035868753}} {{Source|handle=shudza|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560371927141326909}}
'''What would settle it.''' The numbers with context size, system RAM and cache hits stated, and the build published. 
'''Board.''' T-077 (CMP testing) on the [https://cmp.wiki/board/ board].

{{Status|Contested}} {{Cards|8 GB}}

=== v0.5 decodes slower than v0.4 ===
In the order posted:
* @reala7096: ECC has no effect on bandwidth. @matstatman: random one-byte writes would suffer. {{Source|handle=reala7096|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556767677866049579}} {{Source|handle=matstatman|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556768044410343445}}
* @mowgli8628: after reinstalling with v0.5 he "can't get past 35 t/s with qwen 3.8 27b", against 60-80 on v0.4, and asks whether ECC is the cause. {{Source|handle=mowgli8628|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561450305529581640}}
'''What would settle it.''' The same model and settings on v0.4 and v0.5, with ECC on and off, on one card. 
'''Board.''' T-003 (CMP testing) on the [https://cmp.wiki/board/ board]. 
More: [[Driver and unlock failures#Performance changed after an update]].

{{Status|Contested}} {{Cards|8 GB}}

=== Broadwell CPUs halve the Qwen Flash recipe numbers ===
In the order posted:
* @segmond reached nowhere near Morrowmake's GLM numbers and put it down to missing x16 links and TP. {{Source|handle=segmond|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1561950054254645291}}
* @nathang6866 (ElectroHobo) got about half of Morrowmake's numbers on the Qwen Flash recipe: "It seems the Broadwell processors cause issues with certain Qwen Flash recipes." {{Source|handle=nathang6866|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1561951080882114701}}
'''What would settle it.''' The same recipe on a Broadwell host and a newer host with the same cards, links and P2P setting. 
'''Board.''' T-065 (CMP testing) on the [https://cmp.wiki/board/ board]. 
More: [[Platforms#Host CPU and RAM]].

{{Status|Contested}} {{Cards|8 GB}}

== Buying ==

=== One card earns up to 7,000 USD a year ===
In the order posted:
* @cute_sc2: "a single cmp 170hx can now earn up to 7k a year in profit alone, you only need to know how", through long-term rental contracts with cheap energy, Pearl mining or serving AI. {{Source|handle=cute_sc2|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563191373841170453}} {{Source|handle=cute_sc2|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563234262038347830}}
* @kellertreppe123: that is a service business, not the card's hardware value, and businesses would rather trust a cloud provider with a track record. {{Source|handle=kellertreppe123|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563235068573655140}} {{Source|handle=kellertreppe123|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563242677926101014}}
'''What would settle it.''' An owner's income and costs per card over several months. 
More: [[Price history and market]].

{{Status|Contested}} {{Cards|both}}

=== Half of all cards are bad ===
In the order posted:
* @_____josh_____: "the cards have a 50% failure rate". {{Source|handle=_____josh_____|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557666958608957521}}
* @lia_oc: "It's nowhere near that high for sure". {{Source|handle=lia_oc|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557693615038275648}}
* @c133 tested five cards, all good; @bigfoot1144 bought 12, all unlock. {{Source|handle=c133|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557769336930967614}} {{Source|handle=bigfoot1144|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557785453850140733}}
* @_____josh_____: the good stock sold earlier and sellers now mix lemons into each shipment. {{Source|handle=_____josh_____|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557793719309308017}}
'''What would settle it.''' A structured survey: cards bought, source, unlock result, HBM error count, tensor-core check. 
'''Board.''' T-115 (CMP testing) on the [https://cmp.wiki/board/ board]. 
More: [[Buying#How often cards are bad]].

{{Status|Contested}} {{Cards|both}}

=== The vouches for Alifond are bot accounts ===
In the order posted:
* @kellertreppe123: Alifond (Huateng) is vouched for by several members here. {{Source|handle=kellertreppe123|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556319764480131215}}
* @_____josh_____: "The multiple guys are their own bot accounts. Don't fall for it." @djpandaman: "this is true tho". {{Source|handle=_____josh_____|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556346381860474891}} {{Source|handle=djpandaman|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556346522562465864}}
'''What would settle it.''' Order reports from long-standing members, with dates and what arrived. 
More: [[Buying#Alifond]].

{{Status|Contested}} {{Cards|both}}

=== Listings promising PCIe 4.0, NVLink, ECC and 80 GB ===
In the order posted:
* An eBay listing showed a 170HX with PCIe 4.0. @con3po7016: "false alarm"; @spectakkular: "PCIe 4.0 is a listing mistake from before the cards were cracked. It's just eBay autofilling listing information". {{Source|handle=con3po7016|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558699238312116325}} {{Source|handle=spectakkular|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558743009380671579}}
* @tugoubxs found a seller whose description promised ECC, PCIe 4.0, NVLink and 80 GB. {{Source|handle=tugoubxs|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559792760477712456}} {{Source|handle=tugoubxs|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559795404076355676}}
* A seller's screenshot read as PCIe Gen4 x16 by @galygious2; @xeax: the field shows x1 Gen1 at idle. {{Source|handle=galygious2|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561264068508262462}} {{Source|handle=xeax|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561265565736370219}}
'''What would settle it.''' Nothing in a listing counts; check the card on arrival. 
More: [[Buying#Scam patterns]], [[Acceptance checklist]].

{{Status|Contested}} {{Cards|both}}

=== Die transplants and cards with no chips ===
@civiloid recalled reports of used-market cards "with no chips", and of a CMP that turned out to carry a die transplanted from the 32 GB A100 variant. No photo or link to the original reports was posted. 
'''What would settle it.''' The original reports or photos. 
More: [[Which card do I have]], [[Buying]].

{{Status|Theory}} {{Cards|both}} 
{{Source|handle=civiloid|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559466233009676352}} 
{{Source|handle=civiloid|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559466533091016737}}

=== A new finding is behind the late-October price jump ===
In the order posted:
* Miséricorde: "seems like someone found something"; a card he bought at 2,380 USD in the CIS market cost him 3,600+ on arrival. {{Source|handle=wakeupmbrc1|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562704071863959565}} {{Source|handle=wakeupmbrc1|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562706859755053077}}
* @ob88594: "No, what I know is that Russians are aggressively purchasing the 8G version in China"; bulk lots of 10 cost 20% more than the regular price. {{Source|handle=ob88594|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562727070851801112}} {{Source|handle=ob88594|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562727235771699293}}
'''What would settle it.''' A published unlock that explains the jump; otherwise it stays a market question. 
More: [[Price history and market]].

{{Status|Contested}} {{Cards|8 GB}}

=== At least 130,000 8 GB cards exist ===
@spectakkular: "there seems to be at least 130,000 of the 8G around the world". No source for the figure was given. 
'''What would settle it.''' A shipment or production figure with a source.

{{Status|Theory}} {{Cards|8 GB}} 
{{Source|handle=spectakkular|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556599044355137557}}

== See also ==
[[Buying]], [[Price history and market]], [[Other CMP cards and other NVIDIA GPUs]], [[8 GB card]], [[10 GB card]], [[Which card do I have]], [[VBIOS and firmware]], [[Status taxonomy]], [[Board how-to]].

{{ImportFooter}}
[[Category:Help]]

RIR fuse burn

2026-10-30T10:12:23Z

ImportBot: The permanent RIR fuse burn that clears disable_sw_override on the 10 GB card, the one write that opens Gen3, full SM and the 6th stack; commands from lixiangwuxian/170hx-rir-tool; Discord Oct 2026.; sources: @_orrorin, @scallion_9883, @lxtend, @djpandaman, @lycorascence, @xeax, @ob88594, @petrikrohn_26497, @aaasss1456, @analyticeth, @wakeupmbrc1, @zorg33; GitHub evanrodgers/cmp-170hx-rir-burn-util, lixiangwuxian/170hx-rir-tool

{{Unlock
|unlocks=RIR fuse burn (clears disable_sw_override)
|variant=10 GB
|driver_version=cmpunlocker-patched driver, or stock nvidia-open 610+
|unlock_build=lixiangwuxian/170hx-rir-tool
|steps_page=RIR fuse burn
|status=Reported
|tested_by=_orrorin
|source=https://github.com/lixiangwuxian/170hx-rir-tool
}}

{{Status|warning}} '''This is a permanent, irreversible fuse write. A wrong address can brick the card. It applies only
to the 10 GB card (10de:2082). Do not do this unless you understand it.'''

== What it is ==

The 10 GB card has 16 empty RIR (Redundancy Information Rows) slots. The 8 GB card's RIR rows were burned at the
factory, so this does not apply to it. Burning '''two''' records clears the <code>disable_sw_override</code> gate fuse.
After that, the volatile software fuse override (<code>EN_SW_OVERRIDE</code>) can be used to enable PCIe
[[PCIe Gen3 on the 10 GB card|Gen3]], the [[Full SM unlock|full 128 SM]] and (on a lucky card) the
[[Memory unlock on the 10 GB card|6th HBM stack]]. The burn by itself unlocks nothing; it only opens the gate.
{{Source|scallion_9883|2026-10-16|https://discord.com/channels/1518634379604136178/1518692084729511967/1560779955393134755}}

Humvee55 runs 20 unlocked 10 GB cards (128 SM, Gen3 x16) and 20 8 GB cards: "there is one fuse and one fuse only needed
... RIR the disable software override fuse. everything else can be done in software ... the SW IFF is volatile on
reboot, so just don't flash any actual FF/IFF and you'll be fine."
{{Source|scallion_9883|2026-10-16|https://discord.com/channels/1518634379604136178/1518692084729511967/1560782021377400924}}

== The tool ==

[https://github.com/lixiangwuxian/170hx-rir-tool lixiangwuxian/170hx-rir-tool] (MIT, by @lxtend / lxwx), a standalone C
tool that mmaps BAR0 and talks to the GA100 fuse block at <code>0x820000</code>. It reads RIR records, applies volatile
SW overrides, and (with two confirmations) burns RIR records. The author's own warning: the project was AI-assisted,
validated only by the listed measurements; review <code>cmd_write_rir</code> in the source before running anything.
{{Source|lxtend|2026-10-10|https://discord.com/channels/1518634379604136178/1518695328008638516/1558470807888461854}}

== The record encoding ==

The group settled on the GA100 '''linear''' layout (an earlier scrambled layout produced a no-op burn):

* Bits [15:2] = 14-bit absolute fuse-bit address, bit 1 = data, bit 0 = enable.
* A RIR can only turn fuse 0s into 1s; bit 1 carries the value and need not be 1.
* Bit 15 is record invalidation (for NVIDIA test mistakes), not an address bit.

The two keystone records are <code>0x0015</code> (row 0, bit 5) and <code>0x0095</code> (row 1, bit 5), written
together as <code>0x00150095</code>; bit 5 is <code>disable_sw_override</code> (PRI copy at abs bit 5, RED copy at abs
bit 37). {{Source|_orrorin|2026-10-10|https://discord.com/channels/1518634379604136178/1518695328008638516/1558460248761831477}}
{{Source|djpandaman|2026-10-10|https://discord.com/channels/1518634379604136178/1518695328008638516/1558467099125612639}}

== Prerequisites ==

From the tool's README:

* Linux with the GPU installed, root.
* Kernel command line <code>iomem=relaxed</code> (the tool cannot read anything without it).
* The '''cmpunlocker-patched driver, or a stock 610+ driver''', despite the tool only using the driver to power the card
on. {{Source|lycorascence|2026-10-20|https://discord.com/channels/1518634379604136178/1518695328008638516/1562150888146083964}}
* If a command reports the DEBUGCTRL RWL bit will not latch, unbind the driver first
(<code>echo <bdf> > /sys/bus/pci/devices/<bdf>/driver/unbind</code>). Moving to an LTS kernel with the
oldest cmpunlocker-supported driver avoids <code>CONFIG_IO_DEVMEM_STRICT</code> blocking access.
{{Source|lycorascence|2026-10-23|https://discord.com/channels/1518634379604136178/1518695328008638516/1563135463106289716}}

== Steps ==

Check first, burn once, then do the rest in software. Commands verbatim from the README:

<syntaxhighlight lang="bash">
# 1. Read-only status (shows RIR slots free and whether the gate fuse is 0)
sudo ./ga100_rir 0000:41:00.0
sudo ./ga100_rir 0000:41:00.0 --dump-rir

# 2. The permanent burn: clears disable_sw_override (PRI + RED), consumes 2 of 16 slots
sudo ./ga100_rir 0000:41:00.0 --write-rir 0 0x00950015

# then cold boot; the burn takes effect after a reboot

# 3. After the gate is open (--status shows "fuse : 0"), volatile overrides (lost on reboot):
sudo ./ga100_rir 0000:41:00.0 --sw-enable
sudo ./ga100_rir 0000:41:00.0 --sw-write gen3 0 # Gen3/Gen4 fuse bits
sudo ./ga100_rir 0000:41:00.0 --sw-write ecc 1 # ECC fuse bit
</syntaxhighlight>

The write burns records targeting <code>disable_sw_override</code> PRI (row 0 bit 5) and RED (row 1 bit 5). The tool
refuses a row whose existing slots are non-zero and differ from the request, saves a before/after backup, and requires
two confirmations (type the row number, then <code>BURN</code>). A plain <code>sudo reboot</code> is enough for 99.9%
of cases; you do not need hot-swap. {{Source|handle=lxtend|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1559461961564033106}}

Register map the tool uses: FUSECTRL <code>0x00820000</code>, FUSEADDR <code>0x00820004</code>, FUSERDATA
<code>0x00820008</code>, FUSEWDATA <code>0x0082000C</code>, EN_SW_OVERRIDE <code>0x00820040</code>, DEBUGCTRL
<code>0x00820060</code> (RWL bit 1), DISABLE_SW_OVERRIDE_STATUS <code>0x00820084</code>, IFF_RECORD
<code>0x00820050</code>. SW-override writes go to the <code>_CP</code> shadow copies, e.g. OPT_GPC_DISABLE_CP
<code>0x0082022C</code>, OPT_NVLINK_DISABLE_CP <code>0x00820688</code>. (From the repo README.)

== Notes ==

* '''Fuse budget:''' the 10 GB card shows 16 free slots; you can write 8 times but one write (the pair) is enough. Burn
consumes 2 slots. {{Source|xeax|2026-10-25|https://discord.com/channels/1518634379604136178/1534370835220004885/1563758670318407802}}
* '''The RIR tool only burns the fuse.''' It is a separate tool from [[Driver unlock|cmpunlocker]]; once the RIR is
overwritten the card unlocks the rest in software according to the research notes, and faults clear on restart.
{{Source|ob88594|2026-10-26|https://discord.com/channels/1518634379604136178/1518695328008638516/1564163555182514197}}
* '''orrorin's burn plan''' (<code>rir_burn_plan.md</code>, AI-drafted): Petri Krohn corrected and completed it: row 0
of the main fuse array reads <code>0x53557c3d</code> and bit 5 is <code>DISABLE_SW_OVERRIDE</code>; row 1 is a
redundant duplicate of row 0 with the same fuse at bit 5; both must be zeroed by RIR records, which is the
<code>0x00150095</code> pair, and after that everything is software.
{{Source|_orrorin|2026-10-09|https://discord.com/channels/1518634379604136178/1518695328008638516/1558179701527154849}} 
{{Source|handle=petrikrohn_26497|date=2026-10-10|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558298536813006952}}
* '''Humvee55's method notes''' (<code>message.txt</code>, 10,097 B, posted earlier in a smaller group): his RIR plus
software-IFF method for the full 10 GB unlock; his advice was to feed it to an LLM to fill the gaps. Feralzi and
Lycorascence used it to reach 126-128 SM. {{Source|scallion_9883|2026-10-16|https://discord.com/channels/1518634379604136178/1518692084729511967/1560780989079228478}}
* '''xeax's notes''' (<code>message.txt</code>, 7,381 B) accompany the 170hx-rir-tool link with the warning not to brick
the card and the fuse-slot write count. {{Source|xeax|2026-10-25|https://discord.com/channels/1518634379604136178/1534370835220004885/1563757491659997316}}
* '''Paid service:''' a third party in Chengdu was reported to unlock a 10 GB card for about 500 USD. {{Source|handle=ob88594|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558162519070216295}} aaasss said a friend had a 10 GB card done at the factory the day before ("8912 cuda core", as posted) and that it was paid software, maybe VBIOS. {{Source|handle=aaasss1456|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558164230073753630}} {{Source|handle=aaasss1456|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558164394951573627}} The vendor's text, quoted by AnalyticETH: all changes are permanent in the card, no third-party unlocking software or driver patches, it identifies as an original A100; the first batch takes 10 GB cards and the 8 GB version is "still under development". {{Source|handle=analyticeth|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558168182563545140}} {{Source|handle=analyticeth|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558168218487623782}} Miséricorde read it as this same RIR macro burn, not a VBIOS change, and asked how it would then identify as an A100 40G. {{Source|handle=wakeupmbrc1|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558168562542317812}} {{Source|handle=wakeupmbrc1|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558168720134774805}} Treat as hearsay.

== Known issues / warnings ==

* {{Status|warning}} '''Targeting the wrong address has a good chance of bricking the card.''' This is not trial and
error; the 1.8 V fuse programming is one-shot. {{Source|djpandaman|2026-10-05|https://discord.com/channels/1518634379604136178/1518692084729511967/1556518823350374452}}
* {{Status|warning}} '''Do not spend RIR rows prematurely.''' A software-only (SW IFF) recipe was shared that does most
of the work without burning; save your slots until more is discovered. There will be an influx of used 10 GB cards
with wasted RIRs and no unlock; check the fuse state before buying one.
{{Source|scallion_9883|2026-10-26|https://discord.com/channels/1518634379604136178/1518695328008638516/1564398787143794831}}
* Enabling defective-marked GPCs/FBPAs does not help; those are genuinely defective. Enable only disabled units, and
mask off the defective TPCs within a defective GPC. {{Source|zorg33|2026-10-22|https://discord.com/channels/1518634379604136178/1518692084729511967/1562809952555503678}}

== Status ==

Burned, read back, survives a cold boot and clears the gate fuse, confirmed by more than one person, so {{Status|Proven}}.
See the confirmation below. The further unlocks it enables each have their own page.

== Related ==

[[PCIe Gen3 on the 10 GB card]], [[Full SM unlock]], [[Memory unlock on the 10 GB card]],
[[Kernel parameters and module options]], [[cmpunlocker forks]]. Hardened all-in-one wrapper:
[https://github.com/evanrodgers/cmp-170hx-rir-burn-util evanrodgers/cmp-170hx-rir-gen3].

{{ImportFooter}}
[[Category:Unlocks]]
[[Category:10 GB]]

Price history and market

2026-10-30T10:12:23Z

ImportBot: Import: dated CMP 170HX price reports and market notes from #suppliers-chat, #general, #hardware and #development-general, @djpandaman, @wakeupmbrc1, @kellertreppe123, @ob88594, @voidgiraffe, @spectakkular, @lenxtroz, @feralzi, @lia_oc, @gnasherrr, @busulle, @_____josh_____, @c133, @markshowa and others

Prices for the [[CMP 170HX]] as members reported them on the Discord, each with the date it was posted. This is not a price list. Most rows are one person's quote, listing or purchase, in the currency that person used; no conversions were added. For what to buy, how to pay and how to check a card, see [[Buying]] and [[Acceptance checklist]].

Names as posted: '''Alifond''' (also written Ailfond, alifond) is the Alibaba volume seller most members mention; @kellertreppe123 says Huateng Technology is the same company under another name. {{Source|handle=kellertreppe123|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563149708606701619}}

== Price table ==
{{Status|Reported}} One row per report, earliest first. "Variant" is what the post or its thread says; "not stated" means the post did not say which card. "Condition" says whether the price was listed, quoted, offered, paid, sold, delivered (shipping and taxes included) or recalled later, and whether the card was cap-modded ([[PCIe x16 capacitor mod]]) or unlocked. A recalled price sits at the period it describes; the Source date is the day it was posted.

{| class="wikitable sortable"
! Date !! Variant !! Price !! Currency !! Where !! Condition !! Reported by
|-
| 2021-09-01 || not stated || 4,299 (MSRP); about 4,700 asked || USD || China, where the card first appeared || launch price, from the 170th Street history and specification pages; @kellertreppe123 recalls "4k at launch" || {{Source|handle=markshowa|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1561324784598384784|repo=https://github.com/amoghmunikote/170th-Street}} {{Source|handle=kellertreppe123|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563126021522329601}}
|-
| 2021-11-25 || not stated || 4,700 || USD || bought for a Linus Tech Tips video || paid || {{Source|handle=markshowa|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1561324784598384784|repo=https://github.com/amoghmunikote/170th-Street}}
|-
| 2022-09 (after the Ethereum Merge) || not stated || 400-500 in China; 300-500 on eBay || USD || secondhand markets || listed; club-170hx gives 250-500 || {{Source|handle=markshowa|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1561324784598384784|repo=https://github.com/amoghmunikote/170th-Street}} {{Source|handle=c133|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562161732137386127|repo=https://github.com/PixelML/club-170hx}}
|-
| 2026 (before the unlock tool) || not stated || 100-300 || USD || mining market || traded as mining cards || {{Source|handle=c133|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562161732137386127|repo=https://github.com/PixelML/club-170hx}}
|-
| 2026 (a couple of months before 10-23, recalled) || not stated || 300 || USD || not stated || "people pleaded to sell this GPU for 300usd" || {{Source|handle=odide_36591|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563141330367021069}}
|-
| 2026-06 (recalled) || 10 GB || 200 each || USD || not stated || paid; @cuddylac997 bought four before the unlock news || {{Source|handle=cuddylac997|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1557383580106227724}} {{Source|handle=cuddylac997|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1557383605830025328}} {{Source|handle=mlx4|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1563753763813068941}} {{Source|handle=mlx4|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1563753787242324010}}
|-
| 2026-07 (mid, recalled) || not stated || 550 each for the first four; passed on 700 each || USD || eBay and Newegg || paid; 12 of 16 later orders were cancelled || {{Source|handle=gnasherrr|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559772189618864129}} {{Source|handle=gnasherrr|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559772869314089103}} {{Source|handle=gnasherrr|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559774430169792584}} {{Source|handle=gnasherrr|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559772811218911383}}
|-
| 2026-07 (day one of the public unlock, recalled) || 8 GB || about 580 each; 800 the next day || USD || not stated || paid two at 580 || {{Source|handle=phoenixone7|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557444473083142235}} {{Source|handle=phoenixone7|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557452853172510792}}
|-
| 2026-07 (same period, recalled) || not stated || 2 at about 580, 2 at 800, 4 at 900 || USD || not stated || ordered eight, received two; the other orders were cancelled as "out of stock" || {{Source|handle=sojun80|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557446517994946622}} {{Source|handle=sojun80|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557446894240792667}} {{Source|handle=sojun80|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557446912930615448}}
|-
| 2026-08 (about a month after the unlock, recalled) || not stated || "the same price as a 3090" || not stated || Alibaba, Alifond || sold || {{Source|handle=spectakkular|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1557651688142409759}}
|-
| 2026-08 to 2026-09 (recalled) || not stated || about 800 early; 1,300-1,400 average || USD || not stated || paid || {{Source|handle=djpandaman|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556256308762775613}} {{Source|handle=djpandaman|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557246623501910027}}
|-
| 2026-08 to 2026-09 (recalled) || not stated || about 1,000 || USD || import quotes || quoted || {{Source|handle=spectakkular|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556256452526604390}}
|-
| 2026-08 to 2026-09 (recalled) || not stated || 1,300; buyers wanted 1,000 at most including shipping and import duties || USD || Alibaba, Alifond || quoted "back in the day"; an EU group buy failed on price expectations || {{Source|handle=cute_sc2|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556343601628184670}} {{Source|handle=cute_sc2|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556327097767690271}}
|-
| 2026-09 to 2026-10-05 (recalled) || not stated || 1,600, then 2,100 || USD || Alibaba seller || waited at 1,600 thinking it was a bluff, paid 2,100 || {{Source|handle=voidgiraffe|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556513056761053325}} {{Source|handle=voidgiraffe|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556513084120760321}}
|-
| 2026-09 (before the October holiday, recalled) || not stated || 2,199 || USD || not stated || "everybody will wish they bought at US$ 2199" || {{Source|handle=persona_80337|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556516640126935102}}
|-
| 2026-10 or earlier (date not given) || 8 GB; 10 GB || 8 GB 800 "way back"; two 10 GB at 1,500 each "when 8Gb was 2500" || USD || not stated || paid || {{Source|handle=tokukarin|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557443092880035932}}
|-
| 2026 (dates not given, posted 10-23) || not stated || 1,000 each for three, 2,100 for the fourth || USD || not stated || paid || {{Source|handle=lia_oc|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563142258394665055}}
|-
| 2026-10-01 || not stated || 1,900 || USD || eBay || sold (screenshot) || {{Source|handle=djpandaman|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559074621154791506}} {{Source|handle=djpandaman|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559075077528616961}}
|-
| 2026-10-04 || not stated || 2,400 || USD || Alibaba, Alifond || quoted || {{Source|handle=cute_sc2|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556208333373972491}}
|-
| 2026-10-04 || not stated || 2,299-2,599 || USD || Alibaba, Alifond || quoted || {{Source|handle=lenxtroz|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556236658322702348}}
|-
| 2026-10-04 || not stated || +300 per card the same evening || USD || Alibaba, Alifond || price increase (screenshot) || {{Source|handle=busulle|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556376077797163119}} {{Source|handle=busulle|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556376129990819843}}
|-
| 2026-10-04 || not stated || "over $2,800" || USD || Alibaba, Alifond || paid by Korean buyers; Korean enquiries got higher quotes, an enquiry in Chinese a lower one || {{Source|handle=artistosu|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556232731103338608}} {{Source|handle=artistosu|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556232941653200937}} {{Source|handle=artistosu|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556238447117860889}}
|-
| 2026-10-04 || not stated || about 1,850 || USD || Xianyu, a large mining operation claiming 2,000 units || quoted before import duties and shipping; the seller wanted USDT || {{Source|handle=voidgiraffe|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556207433670721597}} {{Source|handle=voidgiraffe|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556258101596782593}} {{Source|handle=voidgiraffe|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556987210048213004}}
|-
| 2026-10-04 || not stated || 2,600 from China; 3,000 domestic || USD || Alibaba, Alifond, DDP to the EU; EU domestic || quoted with the cap mod included (posted as "2,6$") || {{Source|handle=kellertreppe123|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556319940942893168}} {{Source|handle=kellertreppe123|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556320536920072225}}
|-
| 2026-10-04 || not stated || about 2,800 || EUR || Austria, a company (the only EU seller found) || listed || {{Source|handle=busulle|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556350644514721793}}
|-
| 2026-10-04 || 8 GB || 2,500 each, lot of 12 || USD || eBay, a US seller || listed || {{Source|handle=mrmannyatx|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556323489185533993}}
|-
| about 2026-10-04 || not stated || 2,150-2,200 || EUR || Alibaba, Alifond, DDP || paid ("3 days ago or so", posted 10-07) || {{Source|handle=quark2world|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557431591209275446}} {{Source|handle=kellertreppe123|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557443994567450702}}
|-
| 2026-10-05 || not stated || 2,599 || USD || Alibaba sellers || quoted; Alifond cancelled an earlier order "due to price increases" || {{Source|handle=voidgiraffe|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556507631986802779}} {{Source|handle=busulle|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556512895150325863}}
|-
| 2026-10-06 || not stated || +500 || USD || Alifond only, per @voidgiraffe || price increase || {{Source|handle=gitanos|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556983137404330015}} {{Source|handle=voidgiraffe|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556984699661062219}}
|-
| 2026-10-06 || not stated || 1,800-1,900 || USD || Xianyu, two sellers || quoted || {{Source|handle=voidgiraffe|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556984655566340129}}
|-
| 2026-10-06 || not stated || about 4,000 each || AUD || eBay, Australia || listed || {{Source|handle=voidgiraffe|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1556921329960091669}}
|-
| 2026-10-06 || two cards in a system || 18,000-20,000 || AUD || a prebuilt dual-card rig, expandable to four || offered; answers called it overpriced || {{Source|handle=truneski|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1556880090485235724}} {{Source|handle=persona_80337|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1556886988962005057}}
|-
| 2026-09-30 to 2026-10-07 || not stated || 2,000-2,100 || USD || Alibaba sellers || offers accepted "last week"; "accepting offers for 2100$" || {{Source|handle=dany0_|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557398141983133879}} {{Source|handle=_____josh_____|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557406879305564193}} {{Source|handle=_____josh_____|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557406900788666459}}
|-
| 2026-10-07 || not stated || 2,100 each, eight cards || USD || eBay || paid || {{Source|handle=locs_locs|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557243532182560810}} {{Source|handle=locs_locs|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557243747631366249}} {{Source|handle=locs_locs|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557243794489868359}} {{Source|handle=locs_locs|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557249750351478805}}
|-
| 2026-10-07 || not stated || 2,375 || USD || eBay, the same seller || offered || {{Source|handle=analyticeth|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557397571083837531}}
|-
| 2026-10-07 || not stated || 2,300-2,600 || USD || eBay US || listed; "more like $2300 by the looks of it" || {{Source|handle=lia_oc|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557366598292217857}} {{Source|handle=monroestreet|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557477281100988559}}
|-
| 2026-10-07 || not stated || 2,700 || USD || not stated || asked "since the ecc unlock" || {{Source|handle=junsulee119|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557365267842211954}}
|-
| 2026-10-07 || not stated || 2,699 || USD || Alibaba, Alifond || "the official price" || {{Source|handle=cibernox|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557431843601649738}}
|-
| 2026-10-07 || 8 GB, unlocked to 64 GB || 3,000 || USD || Czechia || listed || {{Source|handle=dany0_|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557477215170596997}} {{Source|handle=dany0_|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557478329450369176}}
|-
| 2026-10-07 || not stated || 2,180 DDP || USD || a Shenzhen seller, named as xiulianjesen (nobody reported buying there) || quoted || {{Source|handle=kellertreppe123|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557475954887237723}} {{Source|handle=kellertreppe123|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557476041822310521}}
|-
| 2026-10-07 || not stated || 850 || USD || Alibaba listing "LEGIT DEAL For New CMP 170HX" || listed; wire transfer only; see [[#Scam price signals]] || {{Source|handle=forte9000|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557187047746310185}} {{Source|handle=domrockt2|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557250230636904449}}
|-
| 2026-10-11 || listed as 8 GB; PG199-origin cards || 9,999 (about 1,500 USD, as posted); earlier 7,499 || RMB || Taobao, a large store with 1,000 cards || listed; the small print showed "cmppg199hx" origin cards || {{Source|handle=spectakkular|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1558744440066154568}} {{Source|handle=spectakkular|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1558744737626988646}} {{Source|handle=spectakkular|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1558747573596983328}} {{Source|handle=dalzyyy|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1558751494365257729}}
|-
| 2026-10-11 || not stated || about 14,000 || RMB || Taobao || "minimal retail that it goes for" || {{Source|handle=wakeupmbrc1|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1558744892992266241}}
|-
| 2026-10-11 to 2026-10-12 || not stated || 1,700-1,800; 1,750 || USD || China, direct from a miner || quoted; @wakeupmbrc1 warned such a card might be a 32 GB PG199 board || {{Source|handle=spectakkular|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559108621391110216}} {{Source|handle=spectakkular|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559108721693429933}} {{Source|handle=dany0_|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559209751710269634}} {{Source|handle=wakeupmbrc1|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559212333161513035}}
|-
| 2026-10-12 || 8 GB || 13,000 (about 2,000 USD) || RMB || China, buyout price || withdrawn by the poster the next day ("i was mistaking") || {{Source|handle=wakeupmbrc1|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559212438027501701}} {{Source|handle=wakeupmbrc1|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559212461754818672}} {{Source|handle=wakeupmbrc1|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559577423618637857}}
|-
| 2026-10-12 || not stated || 1,800 || USD || a seller who refused video testing || offered; @ob88594: "cheap", likely hidden issues || {{Source|handle=programmer_007|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559190878357033081}} {{Source|handle=ob88594|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559197409509244928}} {{Source|handle=ob88594|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559197725319241802}}
|-
| 2026-10-12 || 8 GB || 2,500+ || USD || general || "you can use this as a base price" || {{Source|handle=ob88594|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559254126087639071}}
|-
| 2026-10-12 || not stated || about 2,500 including shipping and tax; "around 3k now" || USD || not stated || paid, in transit || {{Source|handle=programmer_007|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559261244140167290}}
|-
| 2026-10-12 || not stated || 2,400 || USD || eBay || cheapest seen || {{Source|handle=cannibaltoast.|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559075219115614209}}
|-
| 2026-10-13 || 8 GB || 18,000-19,000 || RMB || China || "Don't see 13k rmb anymore" || {{Source|handle=tony_smartecom|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559576917793841264}}
|-
| 2026-10-13 || 8 GB; 10 GB || 8 GB 17,000-18,000; 10 GB 20,000 || RMB || China; about the same on Goofish || market price || {{Source|handle=wakeupmbrc1|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559703803685503057}} {{Source|handle=douya4305|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559704933568348271}} {{Source|handle=wakeupmbrc1|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559705431155155044}}
|-
| 2026-10-13 || PG199-origin card sold as a 32 GB "170HX ES" || 9,000+ || CNY || China || paid; another member called 9,000-10,000 reasonable, the buyer thought 13,000-14,000 || {{Source|handle=douya4305|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559703704435953665}} {{Source|handle=douya4305|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559704342716485784}} {{Source|handle=tony_smartecom|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559741065215352897}}
|-
| 2026-10-13 || 8 GB, "64GB" || 3,000 || USD || China || listed as 64 GB; plain 8 GB cards much cheaper || {{Source|handle=endbr64|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559437813072527475}} {{Source|handle=bayley_w|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559439559153164409}}
|-
| 2026-10-13 || 8 GB || 3,000-3,500 || USD || Western markets || market price || {{Source|handle=lenxtroz|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559511799831863317}} {{Source|handle=lenxtroz|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559512626055352391}}
|-
| 2026-10-13 || not stated || 3,000 || USD || a member's listing || listed, no bites || {{Source|handle=_orrorin|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559594410851831920}}
|-
| 2026-10-14 || not stated || 2,600 each || USD || US, landed || paid, after fees and shipping || {{Source|handle=gnasherrr|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559770442984591521}}
|-
| 2026-10-14 || not stated || 3,500 || USD || not stated || quotes "jump 1k" while an order was in transit || {{Source|handle=programmer_007|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559771950128173057}}
|-
| 2026-10-14 || not stated || 3,100 each || USD || Alibaba, Alifond || quoted ("ailfond is trolling") || {{Source|handle=voidgiraffe|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559855690535665745}} {{Source|handle=voidgiraffe|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559855710689431553}}
|-
| up to 2026-10-14 || 8 GB || 1,200, 1,250, 1,500, 1,900 || EUR || Alibaba listing "CMP 170HX 8GB to 64GB HBM2e" || paid, four cards in sequence, all Gen2 x16 || {{Source|handle=domrockt2|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559954889873039421}} {{Source|handle=domrockt2|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559960754466201652}}
|-
| 2026-10-14 || not stated || 2,500 || USD || eBay || paid, first card || {{Source|handle=ybryany|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560002882202374156}}
|-
| 2026-10-14 || not stated || 700 || USD || AliExpress || listed, crypto payment only; see [[#Scam price signals]] || {{Source|handle=ybryany|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560001492008566946}}
|-
| 2026-10-14 || 8 GB, listed as "16x PCIe 64GB Unlock" || 1,200 each || USD || Facebook Marketplace || paid 3,000 USD for two; fake delivery, refunded by PayPal; see [[#Scam price signals]] || {{Source|handle=mfj4|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559755491905896563}}
|-
| 2026-10-15 || not stated || at least 3,000 || EUR || eBay || listed || {{Source|handle=reala7096|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1560280102837944341}}
|-
| 2026-10-15 || not stated || about 2,500 USD; 17,000 RMB minimum in DMs || USD; RMB || Xianyu || quoted || {{Source|handle=voidgiraffe|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1560280859871940609}} {{Source|handle=wakeupmbrc1|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1560287541129777206}}
|-
| 2026-10-15 || 8 GB || 2,400 each, four cards || EUR || a member, EU only, free shipping || listed; tested, no cap mod || {{Source|handle=reala7096|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1560406797007978518}} {{Source|handle=reala7096|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1560407401989939203}}
|-
| 2026-10-16 || not stated || 2,390 each || USD || Taobao or Goofish, collected in Horgos || paid; x16 soldered already || {{Source|handle=wakeupmbrc1|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1560567840720035893}} {{Source|handle=wakeupmbrc1|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1560568905661943964}} {{Source|handle=wakeupmbrc1|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1560574159837470723}} {{Source|handle=wakeupmbrc1|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1560814425298968637}}
|-
| 2026-10-16 || not stated || 17,500 each for 10 pieces (about 2,650 USD, as posted) || RMB || China, seller DMs || lowest quote seen || {{Source|handle=wakeupmbrc1|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1560574221678157845}} {{Source|handle=wakeupmbrc1|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1560574306184994848}}
|-
| 2026-10-16 || not stated || 2,800+ || not stated || the poster's local market || asked || {{Source|handle=wakeupmbrc1|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560780409351184387}}
|-
| 2026-10-16 || not stated || "cmp 5K era" on Alifond's own price; its eBay listing still 3,000 || USD || Alifond direct; Alifond on eBay || listed || {{Source|handle=junsulee119|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1560553630988501013}} {{Source|handle=junsulee119|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1560555670183346219}} {{Source|handle=_arcanum_|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1560564436786356295}}
|-
| 2026-10-17 || 10 GB || nothing below 2,500 || USD || eBay || listed || {{Source|handle=feralzi|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560922684693418075}}
|-
| 2026-10-17 || 8 GB || 3,000 lowest, some 4,000 || USD || eBay || listed || {{Source|handle=feralzi|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560922835608936480}} {{Source|handle=feralzi|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560923119265517599}}
|-
| 2026-10-17 || 8 GB; 10 GB || 8 GB 2,500-3,000; 10 GB about 2,000-2,300 || USD || eBay || sold; {{Status|Contested}} the 10 GB figure was questioned as old data || {{Source|handle=djpandaman|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560923688050630698}} {{Source|handle=feralzi|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560923892070223873}}
|-
| 2026-10-17 || 8 GB (two), 10 GB (one) || 200 below eBay || USD || a member, Chicago area || offered || {{Source|handle=vektor_prime|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561140768637325333}}
|-
| 2026-10-18 || not stated || about 2,100 each, four cards || USD || private sale, PayPal Goods and Services, insured || paid; one arrived damaged || {{Source|handle=globalapathy|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561378037684113531}} {{Source|handle=globalapathy|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561380024278581321}}
|-
| 2026-10-18 || not stated || 2,750 plus tax || USD || eBay || listed || {{Source|handle=globalapathy|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561379875397566526}}
|-
| 2026-10-19 || not stated || 1,900 || EUR || a local deal (EU) || offered; unmodded, unlock untested || {{Source|handle=shudza|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1561737931473948823}}
|-
| 2026-10-19 || 8 GB || 100,000 for 18 cards || USD || Facebook, a seller in Tampa || asked || {{Source|handle=ghostinthedatacenter_87281|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1561537939547234387}} {{Source|handle=con3po7016|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1561558835460837388}}
|-
| 2026-10 (several weeks before 10-19) || a built server || about 20,000 ("20g") || not stated || Alifond || advertised; card count not stated || {{Source|handle=endsjeremy|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1561741606401351712}} {{Source|handle=endsjeremy|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1561741656129011713}}
|-
| 2026-10-21 || 8 GB || about 3,000 on average || USD || the poster's local market || market price; nobody selling 10 GB there || {{Source|handle=akkerstone|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562403016215240765}}
|-
| 2026-10-21 || not stated || 3,333 || USD || an Alibaba sales contact || quoted (screenshot) || {{Source|handle=kellertreppe123|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1562454713461645324}} {{Source|handle=kellertreppe123|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1562456101482401930}}
|-
| 2026-10-22 || not stated || "almost 3K a card" || USD || general || market price || {{Source|handle=deejay9983|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562931575966932993}}
|-
| 2026-10-22 || 8 GB || 18,500 regular; 24,000 per card in bulk lots of 10 || CNY || China || orders seen; bulk about 20 % above regular || {{Source|handle=ob88594|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562727235771699293}} {{Source|handle=ob88594|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562727916020695061}}
|-
| 2026-10-22 || 8 GB || up to 3,700 sold out; one bought at 2,380 "arrived for 3600+" || USD || CIS || sold out; paid || {{Source|handle=wakeupmbrc1|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562703971460583425}} {{Source|handle=wakeupmbrc1|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562704046727372893}} {{Source|handle=wakeupmbrc1|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562706859755053077}}
|-
| 2026-10-23 || not stated || 3,600 || USD || China || market price || {{Source|handle=kellertreppe123|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563125212424445965}}
|-
| 2026-10-23 || not stated || 3,000-3,600+ || USD || China, Alifond and similar || listed || {{Source|handle=lia_oc|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563142358089076798}}
|-
| 2026-10-23 || not stated || 2,600-3,000 and up || USD || general || market price || {{Source|handle=lia_oc|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563142258394665055}}
|-
| 2026-10-23 (recalled) || not stated || 2,000 || USD || general || "i remember when 170hx were 2k" || {{Source|handle=amishrakefightr|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563031325747712062}}
|-
| about 2026-10-23 || not stated || 3,199 / 3,099 (two tiers) || USD || Huateng price sheet || listed || {{Source|handle=legitsplit|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1564193868478681099}} {{Source|handle=kellertreppe123|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1564234756764213309}}
|-
| 2026-10-24 || not stated || 14,000 for four || USD || private sale || sold || {{Source|handle=wakeupmbrc1|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1563680799696625785}}
|-
| 2026-10-24 || not stated || about 700 || USD || AliExpress || listed, ETH or BTC only; see [[#Scam price signals]] || {{Source|handle=feralzi|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563557634211053709}} {{Source|handle=feralzi|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563570653213233185}}
|-
| 2026-10-25 || 10 GB || 1,200 || USD || eBay, listed "for parts" || paid; verified working, unlocked to 40 GB || {{Source|handle=programmerboi|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1563709465902059725}} {{Source|handle=programmerboi|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1563753581637537904}} {{Source|handle=programmerboi|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1563753674281582753}}
|-
| 2026-10-25 || not stated || 2,600 || USD || Alibaba, Alifond || cheapest listing; see [[#Listed versus delivered]] || {{Source|handle=manicraft1001|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563890771898138745}} {{Source|handle=manicraft1001|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563909297635729440}}
|-
| 2026-10-25 || 8 GB || 3,300-3,600, plus about 100 USD Alibaba payment fee || USD || international dealers || delivered (shipping and taxes included) || {{Source|handle=kellertreppe123|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563910041487147110}} {{Source|handle=kellertreppe123|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563910715079655578}} {{Source|handle=kellertreppe123|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563910810416185456}}
|-
| 2026-10-25 || not stated || about 2,500 || EUR || Xianyu, legitimate offers || listed, before DDP shipping to Europe || {{Source|handle=kellertreppe123|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563882154004447354}}
|-
| 2026-10-25 || not stated || 4,000+ || USD || EU || "you can still buy it for 4k + dollars" || {{Source|handle=gitanos|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563871185400496229}}
|-
| 2026-10-25 || 8 GB || 3,000 each; 2,800 offered for three || EUR || EU, between members || offered || {{Source|handle=kellertreppe123|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563956341566087339}} {{Source|handle=kellertreppe123|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563965372304990299}}
|-
| 2026-10-25 || not stated, sold liquid-cooled || 3,000 when bought; +500 a week later; 4,300 now || AUD || Sydney, a local seller || paid; current price || {{Source|handle=zingy90210|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563815081333231697}} {{Source|handle=zingy90210|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563816307143475302}} {{Source|handle=zingy90210|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563816325573382197}}
|-
| 2026-10-25 || eight cards || 23,000 for the eight || not stated ("$23k") || an offer to a member || offered; Gen2 x16 cap mod done, factory tested || {{Source|handle=siriusrhi|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563779604039077961}} {{Source|handle=siriusrhi|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563780119426760776}}
|-
| 2026-10-25 || not stated || 16,000+ per card || CNY || China, sourcing cost || "no major mining farm is willing to ship" || {{Source|handle=ob88594|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563957669134471251}}
|-
| 2026-10-26 || 8 GB || 2,500 each for three || USD || EU, between members || offered || {{Source|handle=zingy90210|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1564155721644515460}}
|-
| 2026-10-26 || not stated || past 3,000 || USD || general || "prices of cmp has officially crossed 3k" || {{Source|handle=feralzi|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564130211358838867}}
|}
{{Status|Reported}} A lab research digest of public sources, written before buying, put tested x16 cards at about 2,000-2,700 USD (secondhand figures, not a purchase). {{Source|handle=darkmaniac7|date=2026-10-12|note=lab notes}}

== Trend by month ==
=== Before the unlock ===
{{Status|Reported}} The card launched in 2021 at a 4,299 USD MSRP and was priced at about 4,700 USD when it surfaced in China. After the Ethereum Merge in September 2022 it fell to 400-500 USD on Chinese secondhand markets and 300-500 USD on eBay. {{Source|handle=markshowa|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1561324784598384784|repo=https://github.com/amoghmunikote/170th-Street}} Before the 2026 unlock tool it traded around 100-300 USD as a mining card. {{Source|handle=c133|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562161732137386127|repo=https://github.com/PixelML/club-170hx}} A 10 GB card cost 200 USD before the unlock news. {{Source|handle=cuddylac997|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1557383580106227724}} {{Source|handle=mlx4|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1563753787242324010}}

=== July 2026 ===
{{Status|Reported}} The first buyers after the Reddit post on the unlock paid 550-580 USD per card in mid July; within a day of the post prices were 800 USD, and sellers cancelled many orders (one buyer received 4 of 16, another 2 of 8). {{Source|handle=gnasherrr|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559772189618864129}} {{Source|handle=gnasherrr|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559774430169792584}} {{Source|handle=gnasherrr|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559772811218911383}} {{Source|handle=phoenixone7|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557444473083142235}} {{Source|handle=phoenixone7|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557452853172510792}} {{Source|handle=sojun80|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557446517994946622}}

=== August and September 2026 ===
{{Status|Reported}} Prices climbed from about 800 to about 1,000 USD and then 1,300-1,400 USD on average. {{Source|handle=djpandaman|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556256308762775613}} {{Source|handle=spectakkular|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556256452526604390}} {{Source|handle=djpandaman|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557246623501910027}} Alifond asked 1,300 USD at one point and buyers would not pay more than 1,000 USD all in; @spectakkular says Alifond sold at RTX 3090 prices a month after the unlock. {{Source|handle=cute_sc2|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556343601628184670}} {{Source|handle=spectakkular|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1557651688142409759}} By late September one buyer waited at 1,600 USD and paid 2,100 USD, and 2,199 USD was the price before the October holiday. {{Source|handle=voidgiraffe|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556513056761053325}} {{Source|handle=voidgiraffe|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556513084120760321}} {{Source|handle=persona_80337|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556516640126935102}}

=== 1 to 7 October 2026 ===
{{Status|Reported}} An eBay sale at 1,900 USD on 10-01. {{Source|handle=djpandaman|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559074621154791506}} {{Source|handle=djpandaman|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559075077528616961}} Alifond quoted 2,400 USD on 10-04, then 2,299-2,599 USD, and raised the price by 300 USD per card that evening; on 10-05 Alibaba sellers quoted 2,599 USD and Alifond cancelled an earlier order over the increase. {{Source|handle=cute_sc2|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556208333373972491}} {{Source|handle=lenxtroz|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556236658322702348}} {{Source|handle=busulle|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556376129990819843}} {{Source|handle=voidgiraffe|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556507631986802779}} {{Source|handle=busulle|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556512895150325863}} On 10-06 cards rose about 500 USD more, which @voidgiraffe put down to Alifond alone while two Xianyu sellers still quoted 1,800-1,900 USD. {{Source|handle=gitanos|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556983137404330015}} {{Source|handle=voidgiraffe|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556984699661062219}} {{Source|handle=voidgiraffe|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556984655566340129}} On 10-07 Alifond's official price was 2,699 USD, eBay buyers paid 2,100 USD with listings at 2,300-2,600 USD, and one member quoted 2,700 USD "since the ecc unlock". {{Source|handle=cibernox|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557431843601649738}} {{Source|handle=locs_locs|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557243532182560810}} {{Source|handle=monroestreet|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557477281100988559}} {{Source|handle=junsulee119|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557365267842211954}}

=== 8 to 17 October 2026 ===
{{Status|Reported}} On 10-11 @ob88594 said the price had "surged by another 30%". {{Source|handle=ob88594|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558697983527223327}} On 10-12 he set 2,500 USD and up as the base price for an 8 GB card, while direct-from-miner quotes in China were still 1,700-1,800 USD. {{Source|handle=ob88594|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559254126087639071}} {{Source|handle=spectakkular|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559108621391110216}} {{Source|handle=dany0_|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559209751710269634}} By 10-13 China was at 17,000-19,000 RMB for the 8 GB card and Western markets at 3,000-3,500 USD. {{Source|handle=tony_smartecom|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559576917793841264}} {{Source|handle=wakeupmbrc1|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559703803685503057}} {{Source|handle=lenxtroz|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559511799831863317}} On 10-14 two cards landed at 2,600 USD each, quotes reached 3,500 USD during another buyer's shipping, and Alifond quoted 3,100 USD. {{Source|handle=gnasherrr|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559770442984591521}} {{Source|handle=programmer_007|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559771950128173057}} {{Source|handle=voidgiraffe|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559855710689431553}} On 10-15 eBay showed at least 3,000 EUR. {{Source|handle=reala7096|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1560280102837944341}} On 10-16 Alifond raised its own price ("cmp 5K era") while its eBay listing stayed at 3,000 USD. {{Source|handle=junsulee119|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1560553630988501013}} {{Source|handle=_arcanum_|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1560564436786356295}} On 10-17 sold 8 GB cards on eBay were 2,500-3,000 USD against listings of 3,000-4,000 USD. {{Source|handle=djpandaman|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560923688050630698}} {{Source|handle=feralzi|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560922835608936480}}

=== 18 to 27 October 2026 ===
{{Status|Reported}} A private sale at about 2,100 USD each against 2,750 USD plus tax on eBay (10-18). {{Source|handle=globalapathy|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561380024278581321}} {{Source|handle=globalapathy|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561379875397566526}} About 3,000 USD on average by 10-21 and 10-22. {{Source|handle=akkerstone|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562403016215240765}} {{Source|handle=deejay9983|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562931575966932993}} In China on 10-22 regular orders were 18,500 CNY and bulk lots of 10 were 24,000 CNY per card, @ob88594 reported Russian buyers buying the 8 GB card aggressively, and in the CIS everything up to 3,700 USD sold out; @djpandaman saw no change in the US yet. {{Source|handle=ob88594|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562727070851801112}} {{Source|handle=ob88594|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562727916020695061}} {{Source|handle=wakeupmbrc1|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562704046727372893}} {{Source|handle=djpandaman|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562705738218999869}} China was at 3,000-3,600 USD on 10-23, and Huateng's sheet from about the same day listed 3,199 and 3,099 USD. {{Source|handle=kellertreppe123|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563125212424445965}} {{Source|handle=lia_oc|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563142358089076798}} {{Source|handle=legitsplit|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1564193868478681099}} @busulle saw eBay prices dropping on 10-24; on 10-26 @feralzi wrote that prices had "officially crossed 3k". {{Source|handle=busulle|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563522423767179365}} {{Source|handle=feralzi|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564130211358838867}} The trade-in rate against an RTX PRO 6000 went from about ten 8 GB cards a month earlier to about six with bargaining on 10-25. {{Source|handle=ob88594|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563771839833182250}} {{Source|handle=ob88594|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563773450500448368}}

=== Why prices moved ===
{{Status|Contested}} Explanations offered for the rise, in the order posted. None came with sales data.
* Sellers read the Discord and reprice on unlock news. {{Source|handle=spectakkular|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556232153535217776}} {{Source|handle=quark2world|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556673217140101121}} {{Source|handle=endsjeremy|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558133663303073923}}
* The ECC unlock in cmpunlocker 0.5. {{Source|handle=junsulee119|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557365267842211954}}
* Only weak cards are left and suppliers price in returns. {{Source|handle=_____josh_____|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1562033461387206720}}
* Large mining farms hold most of the supply and charge what they want; or "mostly just greed, there's still lots of supply". {{Source|handle=lia_oc|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563125578939236393}} {{Source|handle=lia_oc|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563141938587369515}}
* Sellers are waiting for the mod to mature and will then sell at 4,000. {{Source|handle=odide_36591|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563141330367021069}}
* A card that earns its price back in two months will not be sold as a 1,000 USD mining card. {{Source|handle=cute_sc2|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563191606197358643}}
* PRL mining made the cards profitable again; see [[#Supply side]]. {{Source|handle=ob88594|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563957367823933502}}
* At 2,500 USD on eBay buyers stopped buying each time, "psychological or just low demand". {{Source|handle=djpandaman|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560923138659844167}}

== 10 GB versus 8 GB ==
{{Status|Contested}} Whether the [[10 GB card]] costs more or less than the [[8 GB card]] changed over time and posters disagreed. In the order posted:
* In July the 10 GB card was worth more because the Reddit post said it could reach 80 GB (recalled). {{Source|handle=gnasherrr|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559774544422768662}}
* 10-07: a buyer paid 1,500 USD each for two 10 GB cards "when 8Gb was 2500"; @wakeupmbrc1 said the 10 GB card was "more expensive than 8gb at that moment". {{Source|handle=tokukarin|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557443092880035932}} {{Source|handle=wakeupmbrc1|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557442737928667157}}
* 10-07 to 10-09: all 10 GB cards disappeared from the market and Xianyu was out of stock "especially the 10G version"; @_____josh_____ said 10 GB sellers were "in delulu land". {{Source|handle=kellertreppe123|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557444599318974566}} {{Source|handle=_____josh_____|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557416561667743888}} {{Source|handle=ob88594|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558077261595410433}} {{Source|handle=wakeupmbrc1|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558098318305792042}}
* 10-12: @ob88594 says unknown buyers in China have been buying the 10 GB card since the unlock information circulated among merchants in early August. {{Source|handle=ob88594|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1559045761071714396}}
* 10-13: @lenxtroz put the 10 GB card 500-800 USD below the 8 GB card; @endbr64 said it is priced "way more higher" because of its other unlock. {{Source|handle=lenxtroz|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559513048421634119}} {{Source|handle=endbr64|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559513274502873161}} {{Source|handle=endbr64|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559513301212471337}}
* 10-13: in China the 10 GB card was 20,000 RMB against 17,000-18,000 RMB for the 8 GB card, about the same on Goofish, while eBay still had the 10 GB card cheaper. {{Source|handle=douya4305|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559704933568348271}} {{Source|handle=wakeupmbrc1|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559703803685503057}} {{Source|handle=wakeupmbrc1|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559705431155155044}} {{Source|handle=froggao|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559705220467007631}}
* 10-16: asked why 10 GB cards were priced below 8 GB cards, @wakeupmbrc1 said "64gb is much more than 40gb" and @cute_sc2 said there was still no simple unlock for the 10 GB card. {{Source|handle=voidgiraffe|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560730489713852597}} {{Source|handle=wakeupmbrc1|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560732867904934009}} {{Source|handle=cute_sc2|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560734214352281621}}
* 10-17: no 10 GB card below 2,500 USD on eBay; sold data of about 2,000-2,300 USD was questioned as old. {{Source|handle=feralzi|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560922684693418075}} {{Source|handle=djpandaman|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560923688050630698}} {{Source|handle=feralzi|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560923892070223873}}
* 10-21: "When I bought my 8g card back in August, everyone was avoiding the 10g versions. Now, nobody is selling them at all in my local market." {{Source|handle=akkerstone|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562403016215240765}}
* 10-27: a seller offered @zagitta a 10 GB card unlocked to 128 SM, 40 GB and PCIe Gen3 for the same price as the 64 GB card he had ordered. {{Source|handle=zagitta|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564683058689613948}}
See [[Which card do I have]] for telling them apart.

== Listed versus delivered ==
{{Status|Reported}} Listings, quotes and what buyers paid often differ.
* On 10-25 Alifond's cheapest listing was 2,600 USD; @wakeupmbrc1 said 2,600 "is not real for 8g", @kellertreppe123 put the "dear price" at 3,300-3,600 USD with shipping and taxes plus about 100 USD Alibaba payment fee, and listings around 3,000 USD were "75% they are out of stock or will scam you". The poster of the 2,600 figure expected extra fees. {{Source|handle=manicraft1001|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563890771898138745}} {{Source|handle=manicraft1001|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563909297635729440}} {{Source|handle=wakeupmbrc1|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563909690914512899}} {{Source|handle=kellertreppe123|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563910041487147110}} {{Source|handle=kellertreppe123|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563910193543381126}} {{Source|handle=kellertreppe123|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563910715079655578}} {{Source|handle=kellertreppe123|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563910810416185456}}
* On 10-16 Alifond's direct price rose while its eBay listing stayed at 3,000 USD. {{Source|handle=junsulee119|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1560555670183346219}} {{Source|handle=_arcanum_|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1560564436786356295}}
* On 10-17 eBay listings for the 8 GB card were 3,000-4,000 USD and sold prices 2,500-3,000 USD; @djpandaman asked whether listings were "actually selling at that price or just boosted listings with no sales". {{Source|handle=feralzi|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560922835608936480}} {{Source|handle=djpandaman|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560922954366193685}} {{Source|handle=djpandaman|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560923688050630698}}
* A member listed cards at 3,000 USD on 10-13 and got no bites. {{Source|handle=_orrorin|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559594410851831920}}
* All-in cost of an Alibaba card on 10-05: "2599 + trade assurance + oh dear treatment + pay all taxes in between + 100 for shipping", more than buying on eBay. {{Source|handle=_____josh_____|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556536760685563945}} {{Source|handle=meatsus|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556543131841859629}}
* Prices moved while cards were in transit: quotes jumped 1,000 USD during one shipment (10-14), and a CIS card bought at 2,380 USD "arrived for 3600+" (10-22). {{Source|handle=programmer_007|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559771950128173057}} {{Source|handle=wakeupmbrc1|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562706859755053077}}
* Sellers cancelled orders after prices rose. {{Source|handle=gnasherrr|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559772811218911383}} {{Source|handle=sojun80|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557446894240792667}} {{Source|handle=busulle|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556512895150325863}}

== Shipping, customs and tax ==
{{Status|Reported}}
* '''Incoterms.''' A DAP quote to the US means the buyer pays customs and about 50 % tariffs; DDP sellers ship with their own forwarder, for example into Germany and on within the EU. {{Source|handle=lenxtroz|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556265856252514367}} {{Source|handle=busulle|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556267198333587529}} {{Source|handle=busulle|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556267914934624328}}
* '''Cap mod included.''' Alifond sold cards already x16 modded, and its 2,600 USD DDP quote to the EU included the cap mod. {{Source|handle=voidgiraffe|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556144791459336227}} {{Source|handle=kellertreppe123|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556319940942893168}}
* '''US to EU.''' About 200-300 USD in transport and customs; many US eBay listings say "May not ship to Germany". {{Source|handle=quark2world|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557101818885050441}} {{Source|handle=humandrone8721_60165|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557108593931714732}}
* '''Inside the EU.''' About 500 EUR in taxes on a card bought within the EU. {{Source|handle=matstatman|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561471786904723507}} Swiss VAT is 8.1 %. {{Source|handle=shirogeek|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561472047652282441}}
* '''China.''' Sales between individuals on Xianyu are tax exempt in China, but the buyer pays import duty or VAT at the destination; a registered business seller adds Chinese VAT, which an export channel might recover (about 13 %). Xianyu itself takes 0.6 %, plus 1 % a month over a limit. {{Source|handle=lia_oc|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556991825422716939}} {{Source|handle=lia_oc|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556991904594264117}} {{Source|handle=spectakkular|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556987478240403477}} {{Source|handle=ob88594|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557026922112876646}} {{Source|handle=ob88594|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557027411596419183}}
* '''Payment fees.''' A credit card costs about 3 % plus 2 % foreign-exchange fee, and Trade Assurance about 3 % more. Visa or Apple Pay came out about 300 EUR above a wire for one buyer. {{Source|handle=matstatman|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556285408659247197}} {{Source|handle=_____josh_____|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556347480944152639}} {{Source|handle=busulle|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556346400567070861}} About 100 USD Alibaba payment fee on a delivered card (10-25). {{Source|handle=kellertreppe123|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563910810416185456}} After a refused shipment Alibaba still tries to take a 3 % transaction fee. {{Source|handle=endsjeremy|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563880264294342711}}
* '''Agents.''' Superbuy adds 5 % to the exchange rate in its foreign-currency estimates, and agents make their margin on exchange rates and shipping. {{Source|handle=spectakkular|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1558747112710209577}} {{Source|handle=spectakkular|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559253481574113341}} @djpandaman's Alibaba agent charges 10 %, and an in-country agent who checks hardware before export also charges about 10 %. {{Source|handle=djpandaman|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559254486164439092}} {{Source|handle=endsjeremy|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563881270079913995}} Taobao forwarding carries a fixed shipping cost, so it pays off on larger orders. {{Source|handle=djpandaman|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563571426307481702}}
See [[Buying#Paying]] and [[Buying#Shipping, customs and tax]].

== China wholesale ==
{{Status|Reported}} 8 GB card prices inside China as posted:
* 10-11: about 14,000 RMB minimum retail on Taobao; a 9,999 RMB listing turned out to be PG199-origin cards. {{Source|handle=wakeupmbrc1|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1558744892992266241}} {{Source|handle=dalzyyy|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1558751494365257729}}
* 10-12: 13,000 RMB "buyout price", withdrawn by the poster the next day. {{Source|handle=wakeupmbrc1|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559212438027501701}} {{Source|handle=wakeupmbrc1|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559577423618637857}}
* 10-13: 18,000-19,000 RMB; 17,000-18,000 RMB. {{Source|handle=tony_smartecom|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559576917793841264}} {{Source|handle=wakeupmbrc1|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559703803685503057}}
* 10-15: 17,000 RMB minimum in seller DMs. {{Source|handle=wakeupmbrc1|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1560287541129777206}}
* 10-16: 17,500 RMB each for 10 pieces. {{Source|handle=wakeupmbrc1|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1560574221678157845}}
* 10-22: 18,500 CNY regular, 24,000 CNY per card in bulk lots of 10. {{Source|handle=ob88594|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562727916020695061}}
* 10-23: 3,600 USD; 3,000-3,600+ USD with Alifond and similar. {{Source|handle=kellertreppe123|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563125212424445965}} {{Source|handle=lia_oc|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563142358089076798}}
* 10-25: sourcing cost 16,000 CNY and up; "At this price, you can't even buy it in China". {{Source|handle=ob88594|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563957669134471251}} {{Source|handle=ob88594|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563958242957332542}}
@djpandaman's rule: the closer to the Chinese source, the cheaper, from eBay down through AliExpress, Alibaba, Taobao and 1688 to Xianyu; Taobao and Xianyu need a forwarder or a contact. {{Source|handle=djpandaman|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563559182064689254}} {{Source|handle=djpandaman|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563559326306541568}} {{Source|handle=djpandaman|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563559402160525505}} {{Source|handle=djpandaman|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563571239279140887}}

== Supply side ==
{{Status|Reported}} @ob88594 says the cards come from mining pools: before August 2026 there was nothing to mine (PRL was not available), so they sold cheaply; PRL made them useful again, upstream supply has been cut off most of the time, and no major mining farm will ship. {{Source|handle=ob88594|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563957367823933502}} {{Source|handle=ob88594|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563957669134471251}} Nobody in China or Hong Kong confirmed this in the export. {{Source|handle=_syn_thetic_|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563971040474828851}} Members' own numbers point the same way: 12 cards mining Pearl at night make about 700 USD a month ("No wonder nobody's selling these cards"), miners are holding their cards, and one owner's cards paid themselves off in half a year. {{Source|handle=reala7096|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563148290185494529}} {{Source|handle=68x0|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1562487053646561292}} {{Source|handle=cute_sc2|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1560326885987328111}} A holder of more than 100 8 GB cards in China finds them hard to sell abroad because eBay's seller threshold is high, and a Xianyu seller claimed 2,000 units. {{Source|handle=newman_08462|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557244096446332991}} {{Source|handle=newman_08462|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557244557119197195}} {{Source|handle=voidgiraffe|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556987210048213004}}

== Scam price signals ==
{{Status|Warning}} Far-below-market prices with crypto, wire or off-platform payment are the pattern behind the scams members hit. Paying one of these sellers means losing the money unless your card issuer reverses it. Details and what to do instead: [[Buying#Scam patterns]].
* '''700 USD on AliExpress, crypto only.''' Raised on 10-14 and again on 10-24, when the listings took only ETH or BTC; @kellertreppe123: "why would someone sell a atleast 3k$ gpu for 700$". @djpandaman: if something from China is cheaper on AliExpress than on Taobao or Xianyu, "something is fishy". {{Source|handle=ybryany|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560001492008566946}} {{Source|handle=feralzi|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563570653213233185}} {{Source|handle=kellertreppe123|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563557826192871538}} {{Source|handle=djpandaman|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563570412921819147}} No retailer sells these cards at 70 % off market. {{Source|handle=galygious|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560003998403272725}}
* '''850 USD on Alibaba, wire only.''' A listing titled "LEGIT DEAL For New CMP 170HX" offered no secure payment and blocked the buyer who asked questions. {{Source|handle=domrockt2|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557250230636904449}}
* '''1,200 USD each on Facebook Marketplace.''' A listing "CMP 170HX 8Gb 16x PCIe 64GB Unlock" took 3,000 USD for two cards, then faked a delivery; PayPal Goods and Services on a credit card refunded it. Another buyer hit by the same pattern was still waiting for a refund. {{Source|handle=mfj4|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559755491905896563}} {{Source|handle=adusts|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559759824344846357}}
* '''Extra money after the sale.''' AliExpress sellers asked buyers for 500 USD more for shipping. {{Source|handle=feralzi|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559773507804467211}}
* '''Google Shopping.''' On 10-27 the low-priced CMP 170HX results, all from China, were called pay-by-crypto scams. {{Source|handle=feralzi|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564745078470086776}} {{Source|handle=matstatman|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564745580272423026}}
{{Status|Reported}} Cheap but not a scam: below-market cards in China are often the ones that fail to unlock, and 9,000-10,000 RMB "new" cards are PG199-origin boards that unlock to 32 GB. A seller offering 1,800 USD on 10-12 refused video testing. {{Source|handle=endbr64|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559437813072527475}} {{Source|handle=bayley_w|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559439559153164409}} {{Source|handle=douya4305|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559703704435953665}} {{Source|handle=programmer_007|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559190878357033081}} {{Source|handle=ob88594|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559197725319241802}} See [[Which card do I have]] and [[Buying#Boards that are not what they seem]].

== Parts and services ==
{{Status|Reported}} Prices of things people bought for these cards.
* '''NVLink bridges''' (for the 10 GB card): 500 RMB before the unlock; a Taobao quote of 780 RMB (about 116 USD) unbranded and 900 RMB (about 135 USD) NVIDIA-branded for the dual-slot 900-53651-0000-000, with no discount at 15, 30 or 50 units; 150 USD plus tax at US retail; 120 USD each on Xianyu. {{Source|handle=dalzyyy|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1557824047981658204}} {{Source|handle=djpandaman|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1557812086174781600}} {{Source|handle=djpandaman|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1557812513868087447}} {{Source|handle=djpandaman|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1557423395627466874}} {{Source|handle=_arcanum_|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1557424485701918784}} See [[NVLink]].
* '''Cap mod as a service''': about 50 USD plus shipping (others charge 50-90), 100 USD per card, 120 and 160 per card at two Canadian shops, 45 USD per card paid, 175 USD per card quoted, 300 AUD for one card, 65 per card for 13 cards, about 900 for 8 cards; about 50 CNY (under 10 USD) in China; 500 USD at a paid service, against under 100 USD for the tools to do it yourself. {{Source|handle=gmzombie|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556124053839020085}} {{Source|handle=ikyo|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556148743575961641}} {{Source|handle=68x0|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556848174449299488}} {{Source|handle=gpmickey|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556865392876453901}} {{Source|handle=gnasherrr|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564484581627789364}} {{Source|handle=danske1|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564531936184115221}} {{Source|handle=cmurrayis|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562968838574702633}} {{Source|handle=reala7096|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562969168737865800}} {{Source|handle=impactic|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562969877751267359}} {{Source|handle=lxtend|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562505061395996804}} {{Source|handle=lxtend|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562505132497838254}} {{Source|handle=globalapathy|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560685405781889145}} {{Source|handle=endsjeremy|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560688687858061566}} See [[PCIe x16 capacitor mod]].
The same Huateng sheet that listed the 170HX at 3,199 / 3,099 USD listed the CMP 90HX and 50HX at 248 USD; see [[Other CMP cards and other NVIDIA GPUs]]. {{Source|handle=legitsplit|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1564193868478681099}} The reported price of a paid 10 GB unlock in China is on [[Rumours and claims to verify]]. Alternatives people priced (A100, V100, RTX PRO 6000) are on [[Buying#Alternatives people priced]].

== See also ==
[[Buying]], [[Buying#Scam patterns]], [[Acceptance checklist]], [[Which card do I have]], [[8 GB card]], [[10 GB card]], [[PCIe x16 capacitor mod]], [[Rumours and claims to verify]], [[Other CMP cards and other NVIDIA GPUs]].

{{ImportFooter}}
[[Category:Buying]]

Other CMP cards and other NVIDIA GPUs

2026-10-30T10:12:22Z

ImportBot: Import: other CMP models (90HX, 50HX, 40HX, 30HX, 70HX, 100-210), the A100 relation, and unlock work on other NVIDIA GPUs, @emogop, @zagitta, @djpandaman, @xeax, @green_dam, @jma1753, @68x0, @endsjeremy, @ob88594, @lenxtroz, @arabus_74064, @grapepepper, @sojun80, @danske1, @petrikrohn_26497, @programmerboi, @scallion_9883, @wakeupmbrc1, @peter643; repos Zagitta/gpu-unlock, JustAResearcher/gpu-unlock-ada, unitypit71/rtx4070tisuper-tensor-unlock, dartraiden/NVIDIA-patcher, mint

'''Scope.''' This page collects what the cmpunlocker Discord said about cards that are '''not''' the [[CMP 170HX]]: the other CMP mining models, the A100 that the 170HX is cut from, and unlock projects for GeForce and other NVIDIA cards. '''Nothing on this page is CMP 170HX unlock work unless the entry says so.''' The wiki is about the 170HX; these notes are here because the questions keep coming, and they are thinner than the 170HX pages. For the 170HX itself start at [[Which card do I have]], [[8 GB card]] and [[10 GB card]]. The Discord export behind this page starts on 2026-10-04, so older talk about these cards is missing.

== Other CMP cards ==
{{Status|Reported}} NVIDIA's open kernel module source lists the other CMP models by PCI device ID: CMP 50HX <code><nowiki>1E09</nowiki></code>, CMP 40HX <code><nowiki>1F0B</nowiki></code>, CMP 30HX <code><nowiki>2189</nowiki></code>, CMP 90HX <code><nowiki>220D</nowiki></code> and CMP 70HX <code><nowiki>248A</nowiki></code>. The CMP 170HX (<code><nowiki>20C2</nowiki></code> and <code><nowiki>2082</nowiki></code>) is not in that table. {{Source|repo=https://github.com/NVIDIA/open-gpu-kernel-modules}}

{{Status|Theory}} On 2026-10-07 a member asked the cmpunlocker maintainer about unlocks for the other CMP models ("I know a number are already out"); there was no answer in the export. {{Source|handle=tekfabii|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557380592155238492}}

=== CMP 90HX ===
The CMP model the Discord talks about most after the 170HX. It is a 10 GB GDDR6X card and a different chip from the 10 GB 170HX; do not confuse the two (see [[Which card do I have#Cards that are not a normal 170HX]]). {{Source|handle=javicabrera_30495|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561394694305353729}} {{Source|handle=xeax|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561397088959336542}}

==== What it is ====
{{Status|Reported}} 
The 90HX is built like an RTX 3080: "3080 which cmp90 is based on has 320W". {{Source|handle=emogop|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559482760140169229}} An unlocked 90HX is 3090-level compute but keeps its 10 GB. {{Source|handle=javicabrera_30495|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561394694305353729}} Another owner puts it at nearly the same performance as a 3080. It is 2.5 slots wide, so plan the spacing: one of his cards is starved of air on an open frame. {{Source|handle=lenxtroz|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559486353299873863}} {{Source|handle=lenxtroz|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559364830538764320}}

==== PCIe: capacitors and the mod driver ====
{{Status|Reported}} 
Like the 170HX, the 90HX ships with the capacitors on the PCIe lines missing. Without them it runs PCIe 2.0 x4; with them x16. @emogop had a local technician fit his. {{Source|handle=emogop|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559478202836066414}} {{Source|handle=emogop|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559470299215306843}} PCIe 2.0 comes through a modified driver; without it his card showed Code 43. The modified driver uses the usual signing, not test signing. {{Source|handle=emogop|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559486745089675306}} {{Source|handle=emogop|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559486827109417034}} {{Source|handle=emogop|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559487111944736780}} Asked on 2026-10-16 whether PCIe 4.0 was unlocked, @giaki3003 thought the highest is still 2.0. {{Source|handle=legitsplit|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1560543342796734537}} {{Source|handle=giaki3003|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1560555451412906066}} @ob88594: "PCIe 3.0 cracking is not yet complete". {{Source|handle=ob88594|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559523492603367525}} For the 170HX version of the capacitor mod see [[PCIe x16 capacitor mod]].

==== Power and VRAM cooling ====
{{Status|Reported}} 
The modified driver also lets you raise the power limit. The ceiling is 300 or 320 W, "apparently it's a hardware limit of that card". GPU temperatures are good; VRAM temperatures are not. {{Source|handle=emogop|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559479712479322173}} {{Source|handle=emogop|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559484427518738514}} {{Source|handle=emogop|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559482760140169229}} With the stock pads the VRAM easily goes past 100 C. @emogop replaced the thermal pads on the VRAM with a copper or aluminium plate, with no insulation layer, and calls the plate mod and the capacitor mod both a must on a 90HX. The plate cost about 9 USD on the Russian AliExpress site; another member found the same part for about 20 USD on the global site. {{Source|handle=emogop|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559464707805417503}} {{Source|handle=emogop|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559465038283280397}} {{Source|handle=emogop|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559475004423405630}} {{Source|handle=emogop|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559477064074141808}} {{Source|handle=lenxtroz|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559476285103800341}}

==== Memory and SMs ====
* {{Status|Reported}} The 90HX has no memory to unlock; the only route is a manual upgrade with newer memory packages. {{Source|handle=programmerboi|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1563897609389604915}} {{Source|handle=programmerboi|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1563897725479555085}} For 20 GB you need a 3090 PCB plus ten more GDDR6X chips soldered on, the same as the RTX 3080 20 GB mod. {{Source|handle=xeax|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561397088959336542}}
* {{Status|Theory}} No SM unlock for the 90HX has been shown. Asked whether it could reach RTX 3080 SM counts, @scallion_9883 answered that GA102 and later consumer Ampere has no RIR (it is "a holdover from turing"), so an unlock would have to go through the floorsweep (FF) path, the same position as the 170HX 8 GB card; @matstatman suggested first looking for disabled GPCs or TPCs. {{Source|handle=emogop|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561040046386057217}} {{Source|handle=matstatman|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561040848395837561}} {{Source|handle=scallion_9883|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561076899701334178}} {{Source|handle=scallion_9883|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561078822290325626}} @emogop was told his card has no RIR records. {{Source|handle=emogop|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561385941124251720}} An AI-written comparison table claimed a 90HX can be modified to all 84 SMs; @emogop had seen no such release, and its author said that row came from his AI and may be wrong. {{Source|handle=emogop|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561313164543655967}} {{Source|handle=xeax|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561366061549625347}} See [[Full SM unlock]] for how the 170HX does it.
* {{Status|Reported}} Tensor rate: the speed-select fuses that cap FP16/BF16 math with FP32 accumulate read <code><nowiki>0x5</nowiki></code> on the 90HX and <code><nowiki>0x1</nowiki></code> on an RTX 3090. {{Source|handle=green_dam|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562186252902469733}} The "free 3090 speedup hack" from Reddit works on a 90HX too (see [[#Tensor rate un-nerf on GeForce cards]]). {{Source|handle=68x0|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562637141438373937}}

==== CUDA support ====
{{Status|Contested}}
* @ob88594: "It seems CUDA calls are not supported and will cause errors". {{Source|handle=ob88594|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559361700669558825}}
* @xnupanic76: "The 90HX works fine for CUDA, I have one in one of my workstations." {{Source|handle=xnupanic76|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559460764195102782}}
* @ob88594 later: performance calls are ineffective and AI performance is much worse than a 3080. {{Source|handle=ob88594|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559523492603367525}}
Board card T-153 on the [https://cmp.wiki/board/ board] asks two 90HX owners for one clean CUDA sample and one llama.cpp benchmark each.

==== Ray tracing and games ====
{{Status|Reported}} 
On 2026-10-16 @emogop reported hardware ray tracing working on the 90HX, with a screenshot of Indiana Jones (a game that needs hardware RT) running; he credits another member and friends with the unlock. {{Source|handle=emogop|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1560503426679316553}} Asked whether performance was still in the RTX 3060 range, @emogop answered that in real games it is closer to a desktop 3070. {{Source|handle=giaki3003|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1560555573605437502}} {{Source|handle=emogop|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1560569644342055065}} Before that, one owner said games were capped at 50 fps. {{Source|handle=lenxtroz|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559486397188935721}}

==== NVLink, GSP and vGPU ====
* {{Status|Reported}} No NVLink: the card has no NVLink fingers ("no splines"), and a bridge would cost more than the card anyway. {{Source|handle=minioadmin|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561654120643829834}} {{Source|handle=scallion_9883|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561813141409759303}} {{Source|handle=matstatman|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561656280114929766}}
* {{Status|Reported}} The GSP-off approach that @zarknoth described for CMP cards (unlock first, then load the driver with GSP firmware disabled) "work well" on the 90HX, and the non-GSP driver can be modified to use vGPU (screenshot, single report). {{Source|handle=zarknoth|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1564547690019160145}} {{Source|handle=green_dam|date=2026-10-28|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1564799215874474065}} {{Source|handle=green_dam|date=2026-10-28|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1564799982962348173}} The 170HX side of this is on [[VBIOS and firmware]].

==== Unlock tools, uses and price ====
* {{Status|Reported}} The Windows unlocks for the CMP 90HX and 50HX run as a UEFI module before the OS starts. @zagitta took the idea for his early-boot Linux module from them, and says his own repo "is all based on the CPM90/50 unlocks". {{Source|handle=zagitta|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563543666553913345}} {{Source|handle=zagitta|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563585750836969533}} The gpu-unlock-ada README credits WildFlash1st/cmp90hx-unlock for its GA102 code path. {{Source|handle=petrikrohn_26497|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563578905913331836}}
* {{Status|Theory}} Asked on 2026-10-19 whether any 90HX unlock supports open-gpu-kernel-modules 615.78.08; no answer in the export. {{Source|handle=riko6253|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561800715045970051}}
* {{Status|Reported}} One member runs Kokoro TTS and Qwen ASR on a 90HX in his second rig. {{Source|handle=68x0|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1559010348013719623}}
* {{Status|Reported}} Price: about 190 USD per card on 2026-10-13, up 40 to 100 USD within days; 248 USD on Huateng's price sheet dated about 2026-10-23. Since a 90HX now costs about as much as an RTX 3080, there is little point unless you already own one. {{Source|handle=lenxtroz|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559486353299873863}} {{Source|handle=lenxtroz|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559882550888103997}} {{Source|handle=legitsplit|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1564193868478681099}} {{Source|handle=lycorascence|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561395662933983263}} More prices on [[Price history and market]].

=== CMP 50HX ===
{{Status|Reported}} Device ID <code><nowiki>1E09</nowiki></code> in NVIDIA's table (above). A Windows UEFI unlock exists for the 50HX, as for the 90HX. {{Source|handle=zagitta|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563543666553913345}} Huateng's price sheet listed the 50HX at 248 USD. {{Source|handle=legitsplit|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1564193868478681099}} {{Status|Theory}} After the consumer tensor unlock made the news, a member asked whether the CMP 50, 70 and 90 should work with it; no answer in the export. {{Source|handle=ju5t5omedude|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563978991323586674}} The Discord export does not state the 50HX's chip or memory.

=== CMP 40HX, 30HX and 70HX ===
* {{Status|Reported}} Device IDs: 40HX <code><nowiki>1F0B</nowiki></code>, 30HX <code><nowiki>2189</nowiki></code>, 70HX <code><nowiki>248A</nowiki></code> (above). The 40HX and 70HX have 8 GB. @djpandaman's worry was that someone would put one in a 170HX shroud and sell it as a "CMP 8GB" card; @dalzyyy answered that the 170HX PCB is outside the PCIe CEM outline and its edge connector lacks the key notch, so a normal card would have to be cut down or a custom PCB made. {{Source|handle=djpandaman|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1558734253372608583}} {{Source|handle=dalzyyy|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1558734798107836516}} {{Source|handle=dalzyyy|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1558735337151537195}} Check that a listing says 170HX: [[Which card do I have]], [[Buying]].
* {{Status|Reported}} dartraiden/NVIDIA-patcher (below) supports the 30HX, 40HX, 50HX, 70HX and 90HX as display GPUs, and for the 30HX and 40HX recommends blacklisting nouveau and disabling GSP firmware after the install. {{Source|handle=xeax|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564777747144769697|repo=https://github.com/dartraiden/NVIDIA-patcher}}
* The export has no posts about the 30HX, 40HX or 70HX chips and no unlock results for them.

=== CMP 100HX (100-210) ===
{{Status|Reported}} 
The CMP 100HX, also listed as the 100-210, is the mining card of the '''GV100''' (Volta) generation, like the V100 and the Titan V. It is not related to the 170HX's GA100. This came up when a member asked whether a Titan V can be unlocked to 16 GB: "the titan V is GV100, A100 is GA100", "so different core". {{Source|handle=c07f|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563459325278814231}} {{Source|handle=endsjeremy|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563499947305992254}} {{Source|handle=endsjeremy|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563500027823919129}} {{Source|handle=c07f|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563500918987685958}} Not every 100HX revision can be modded and you have to test; some have been unlocked, but at V100 prices it is not very lucrative. {{Source|handle=xeax|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563517994955448361}} {{Source|handle=xeax|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563518185599148104}} {{Source|handle=xeax|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563518427652562955}} One member said he had about 60 of them, bought at 110 each. {{Source|handle=backwardsminer|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560216148979490897}} {{Source|handle=backwardsminer|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560216205640339487}} {{Status|Theory}} Whether anyone gets a 32 GB V100 out of a CMP 100, or only 16 GB, was asked and not answered. {{Source|handle=squishysquare|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560161669005582399}} {{Source|handle=squishysquare|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560161717931999305}} The 100HX PCB has a curved cutout at one end, which one member suggested as a mount for a blower and case. {{Source|handle=tugoubxs|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559793702614999052}}

==== The CMP100-210xFULLTENSORSxGEN3x1 unlock ====
{{Status|Contested}}
* @jma1753 owns 24 CMP 100-210 cards (<code><nowiki>10de:1d84</nowiki></code>) and used only the Tensor-only mode of mintoriakamoto/CMP100-210xFULLTENSORSxGEN3x1, without enabling Gen3 or flashing the VBIOS: "a great performance increase at low power", no issues after 5 days. The unlock is not persistent and is applied after each boot. {{Source|handle=jma1753|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558100513931657287|repo=https://github.com/mintoriakamoto/CMP100-210xFULLTENSORSxGEN3x1}}
* @68x0: the same developer claimed PCIe 5.0 on the 170HX in a cmpunlocker issue; "I wouldn't trust any of this AI slop from this person". Amogh (@_j3ns), the cmpunlocker author, replied: "Exactly why I banned them!" {{Source|handle=68x0|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558131626922344510}} {{Source|handle=_j3ns|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558136539966611477}}
What the repo itself says (read, not run): it is cmp100-unlock 1.1.1 (GPL-2.0), a boot-time, volatile Tensor-core and PCIe Gen3 unlock for the CMP 100-210 (GV100, 16 GB HBM2, <code><nowiki>10de:1d84</nowiki></code> or <code><nowiki>10de:1df4</nowiki></code>). Nothing is flashed; a reset or power loss locks the card again. It reports FP16 tensor throughput going from about 6 to 86.7 TFLOP/s and Gen3 at 0.806 / 0.845 GB/s per x1 lane (Gen1 0.194 / 0.214). It was tested only on two <code><nowiki>10de:1df4</nowiki></code> cards that a seller had flashed with a Tesla V100 VBIOS, on the proprietary 550.163.01 driver, and it packages earlier work by Brazzo978 (CmpUnlocker-100-210) and duggasco (CMP100-210). Read the script before running it. Not 170HX work. {{Source|repo=https://github.com/mintoriakamoto/CMP100-210xFULLTENSORSxGEN3x1}}

{{Status|Reported}} One lesson from that repo applies to 170HX hosts that also carry other NVIDIA cards: the <code><nowiki>RMPcieLinkSpeed=0x1</nowiki></code> registry dword is driver-wide and caps every NVIDIA GPU in the host, not only the CMP. {{Source|repo=https://github.com/mintoriakamoto/CMP100-210xFULLTENSORSxGEN3x1}} @ybryany, who runs a 170HX beside an RTX 4080 Super, left the global Gen2 dwords off for the same reason: they would have pulled the 4080 Super down to Gen2. {{Source|handle=ybryany|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1559748433353384017}} See [[Kernel parameters and module options]].

== The A100 and the 170HX ==
The 170HX is a cut-down A100. What the Discord established about the relation, with the details on [[CMP 170HX]] and [[Variant comparison]]:

=== What they share ===
* {{Status|Reported}} '''The die.''' Both are '''GA100'''. NVIDIA built the 170HX from GA100 dies that did not make the A100 bin. {{Source|handle=markshowa|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1561324784598384784|repo=https://github.com/amoghmunikote/170th-Street}} Compute capability is 8.0 (sm_80) on both, so there is no FP8 on the 170HX. {{Source|handle=cibernox|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1560230570225827862}} NVIDIA's open driver lists the GA100 parts it supports as A100, A30 and A800 boards; the 170HX is not among them. {{Source|repo=https://github.com/NVIDIA/open-gpu-kernel-modules}}
* {{Status|Reported}} '''The board.''' The CMPs are A100 PCIe PCBs with a few components left off, possibly with an extra strapping resistor. {{Source|handle=spectakkular|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1545982693903306813/1564563675912740975}} Compared with the A100 PCIe board, the 170HX leaves 5 Vcore VRM phases unsoldered (6 by another count), plus the parts of the 3.3 V NVLink clock generator. {{Source|handle=wingrimez_40467|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562888884558237807}} {{Source|handle=ghostinthedatacenter_87281|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562905010692558939}} Not everything sits in exactly the same place as on the A100. {{Source|handle=_syn_thetic_|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1545982693903306813/1564066836063068191}} Details on [[CMP 170HX#Board and hardware]].
* {{Status|Reported}} '''Heat spreader and water blocks.''' The A100 40 GB and the 170HX have an integrated heat spreader; the A100 80 GB does not, so A100 80 GB water blocks have a raised cold plate and do not fit. {{Source|handle=_arcanum_|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562136014279934004}} @spectakkular's version: the 8 GB 170HX has a heat spreader where the A100 80 GB has none, the 10 GB 170HX and the A100 40 GB both have one, and an A100 40 GB block on an 8 GB card is the likely mismatch. {{Source|handle=spectakkular|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1545982693903306813/1564563675912740975}} Water blocks sold as "RTX A100" blocks fit, since the A100 PCB "is identical to cmp170hx"; 3090 blocks do not. {{Source|handle=gnasherrr|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559792939088093207}} {{Source|handle=gnasherrr|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559793298682683396}} {{Source|handle=gnasherrr|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559793345046249535}} SXM4 A100 heatsinks do not fit either: the boards are vastly different. {{Source|handle=wakeupmbrc1|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560749614171160688}} See [[Water cooling]].
* {{Status|Reported}} '''HBM packages.''' @djpandaman: every GA100 package he knows of, across the 170HX and A100 lines, carries 6 stacks of HBM2e, which he concludes are 16 GB stacks binned by Samsung. {{Source|handle=djpandaman|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559096192036642817}} What that means for each 170HX variant is on [[10 GB card]] and [[8 GB card]].

=== What differs ===
* {{Status|Reported}} '''What NVIDIA locked on the 170HX.''' FP32, FP64 and INT8 throttled (FP16 tensor left alone), SMs cut to 70, memory cut to 8 or 10 GB, PCIe at Gen1 x4, NVLink fused off with its board parts missing, ECC disabled, BAR limited to 64 MiB, no graphics outputs. {{Source|handle=markshowa|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1561324784598384784|repo=https://github.com/amoghmunikote/170th-Street}} What the unlock gets back: [[Driver unlock]], [[Full SM unlock]], [[Gen2 link retrain]], [[PCIe Gen3 on the 10 GB card]], [[ECC]], [[NVLink]].
* {{Status|Reported}} '''Bad HBM blocks.''' The A100 hides bad HBM blocks by itself; on the 170HX owners mark them by hand. {{Source|handle=cute_sc2|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556661094272073809}} See [[Memory errors and ECC]].
* {{Status|Reported}} '''Power.''' The A100 PCIe cannot be undervolted and has a 300 W limit, so a compute-bound job sits at the cap all the time; the 170HX can be undervolted, which @wakeupmbrc1 counts as "like 25% free drain" saved. {{Source|handle=wakeupmbrc1|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559794301708271767}} {{Source|handle=wakeupmbrc1|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559794317130862603}} {{Source|handle=wakeupmbrc1|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559794657305690204}} The A100 PCIe idles at about 22 W at P8 in the screenshots one member found, about what unlocked CMPs reach; he thinks HBM keeps it from going lower. {{Source|handle=robbbbbb7973|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1534543856006332586/1562283459810955378}} See [[Undervolting and power limits]] and [[P-states and idle power]].
* {{Status|Contested}} '''Which A100 bin each variant shares.'''
** @atsasin2126: the 8 GB card has a 4096-bit bus because four HBM2e stacks were enough for its advertised mining rate, and "10g shares the bin with a100 40g, 8g with a100 80g". {{Source|handle=atsasin2126|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560907053567053856}} {{Source|handle=atsasin2126|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560907303102980117}}
** @djpandaman: "then why would a100 80G have 5120". {{Source|handle=djpandaman|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560907372459860060}}
* {{Status|Contested}} '''cp.async on sm_80.''' @zagitta: "cp.async is not on A100 afaik". @phoenixone7: it should be, worth checking. @zagitta then allowed it may have been some other memory-copy feature missing on sm_80 that his assistant hit when porting sm_86 code. Nobody checked the CUDA documentation in the thread; this matters to anyone porting kernels from GA10x to GA100. {{Source|handle=zagitta|date=2026-10-28|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564800385544233031}} {{Source|handle=phoenixone7|date=2026-10-28|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564803908344217743}} {{Source|handle=zagitta|date=2026-10-28|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564804454404853812}}

=== A100 SXM modules ===
* {{Status|Reported}} A100 SXM modules only need 48 V; the converters on the module do the rest. {{Source|handle=dalzyyy|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561419259320602625}} Prices and the Chinese SXM4-to-PCIe conversion cards are on [[Buying#Alternatives people priced]].
* {{Status|Theory}} A member is reverse-engineering the SXM baseboard pinouts to make intermediary boards for A100 and H100 baseboards; another says a vendor already has an SXM4 board laid out. {{Source|handle=programmerboi|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561408480798052533}} {{Source|handle=programmerboi|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561412259832664135}} {{Source|handle=dalzyyy|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561421560156389451}}
* {{Status|Theory}} A 300 W SXM2 A100 module from a self-driving platform, the highest-TDP A100, is now on the used market; whether it works in a DGX-1 was discussed but not tried. {{Source|handle=endsjeremy|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1564429237161820329}} {{Source|handle=endsjeremy|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1564429344439533609}} {{Source|handle=endsjeremy|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1564429403616706602}}

== Engineering samples and single-rank boards ==
{{Status|Warning}} {{Cards|8 GB}} 
Two kinds of card report as an 8 GB 170HX but do not unlock to 64 GB. Full identification details are on [[Which card do I have#Cards that are not a normal 170HX]].
* '''PG199-origin engineering samples''' unlock to 32 GB only. They are PG199 boards reconfigured to 170HX specs; one bought for over 9,000 yuan showed subsystem <code><nowiki>10de:1586</nowiki></code>, board <code><nowiki>699-11001-0109-RC1</nowiki></code> and ES VBIOS 92.00.6D.00.01. {{Source|handle=_arcanum_|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559546208719077477}} {{Source|handle=douya4305|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559698008516337665}}
* '''Single-rank 8 GB cards''' stop at 32 GB, dual-rank cards reach 64 GB. A fake 64 GB unlock on a single-rank card passes <code><nowiki>memtest_vulkan</nowiki></code> but fails a CUDA memtest, so validate with a CUDA-side test. {{Source|handle=c133|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562161732137386127|repo=https://github.com/PixelML/club-170hx}}

== Tensor rate un-nerf on GeForce cards ==
Not 170HX work. GeForce cards run FP16 and BF16 tensor math with FP32 accumulate (and TF32) at half the rate of the matching workstation and data-center cards. The CMP unlock work showed how to lift that cap, and in October 2026 members ported it to GeForce cards. None of these tools touch a 170HX. Details and more numbers are on [[Tools#Related work on other NVIDIA cards]] and [[Cmpunlocker forks]].

=== Why it works ===
{{Status|Reported}} The fuses <code><nowiki>NV_FUSE_OPT_SM_SPEED_SELECT_FMLA32</nowiki></code> and <code><nowiki>NV_FUSE_OPT_SM_SPEED_SELECT_IMLA4</nowiki></code> read <code><nowiki>0x5</nowiki></code> on the CMP 90HX and <code><nowiki>0x1</nowiki></code> on an RTX 3090, and Ada cards appear to carry a similar limit. {{Source|handle=green_dam|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562186252902469733}} {{Source|handle=green_dam|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562186434369159270}} The source is the case study in the unitypit71 repo. {{Source|handle=matstatman|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562201073068941455|repo=https://github.com/unitypit71/rtx4070tisuper-tensor-unlock}} On pro and data-center cards the rate is generally not capped (a T4 "probably already has all it's tensor perf"). {{Source|handle=zagitta|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564761500587917424}} {{Source|handle=zagitta|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564760634963398860}}

=== RTX 3090 and other Ampere cards ===
* {{Status|Proven}} '''RTX 3090.''' @zagitta applied the CMP register technique to his 3090s: the FP16/BF16 to FP32-accumulate MMA path went from 134 to 268.6 TFLOP/s, the same MMA per clock as an A40. {{Source|handle=zagitta|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561183733569167393}} {{Source|handle=zagitta|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561186609582448701}} {{Source|handle=zagitta|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561186986549579797}} @danske1, running the same module on an EVGA RTX 3090 FTW3 (8192 x 8192 x 8192 GEMM, median of 20 iterations x 5 samples): FP16 in, FP32 accumulate 81.95 to 141.07 TFLOPS (+72 %); BF16 81.35 to 145.59 (+79 %); TF32 40.46 to 78.76 (+95 %); FP16 accumulate (about 148) and plain FP32 (about 30) unchanged. {{Source|handle=danske1|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563165669523067072}} {{Source|handle=danske1|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563293585762295871}} {{Source|handle=danske1|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563293742557962313}}
* {{Status|Contested}} '''What it buys in practice.'''
** @zagitta: "a minor unlock for a few % prefill", and only when the engine uses BF16 to FP32 FMA. {{Source|handle=zagitta|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561066240934678559}} {{Source|handle=zagitta|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561876551505551411}}
** A tester on r/LocalLLaMA found it works but makes no inference difference (relayed by @javicabrera_30495). {{Source|handle=javicabrera_30495|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561514841015844927}}
** The gpu-unlock README claims LLM prefill +25 to 55 %, BF16 fine-tuning +25 to 50 % and image generation +30 to 55 %, with decode, INT8/FP8/INT4 and gaming unchanged. {{Source|handle=zagitta|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561189774834802709|repo=https://github.com/Zagitta/gpu-unlock}}
* {{Status|Reported}} '''Other Ampere cards.''' @grapepepper patched his RTX 3090 Ti from Zagitta's repository; @sojun80 un-nerfed a 3060 Ti, 3070, 3070 mobile, 3080 and 3080 Ti in one night. {{Source|handle=grapepepper|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562183666371924070}} {{Source|handle=sojun80|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562322577676967957}}
* {{Status|Reported}} '''The Reddit "free 3090 speedup hack".''' The post "Amazing free 3090 speedup hack, verified works 15% PP, 5% TG for free" also worked on an RTX 3080 20 GB and on a CMP 90HX; its author is reported to be a member of the server. One owner found the inference gain small; another says the gains are real for diffusion models. One user only got it to take effect after unplugging the machine from the wall. {{Source|handle=vektor_prime|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562634821593731132}} {{Source|handle=vektor_prime|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562692329934954496}} {{Source|handle=68x0|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562637141438373937}} {{Source|handle=stcord|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562732562273538140}} {{Source|handle=licensedterrapin|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562700183643361373}} {{Source|handle=djpandaman|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562700803125547071}} {{Source|handle=lenxtroz|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562727278520176672}}
* {{Status|Reported}} '''RTX 3050 6 GB (GA107).''' @arabus_74064's card (18 SMs, sm_86) after the unlock: FP16 to FP32 18.3 to 37.0 TFLOPS, BF16 to FP32 18.2 to 37.0, INT8 72.8 to 74.0 TOPS, plain FP32 8.4 to 8.6. A GEMM correctness check at three shapes and seeds showed zero failures and zero max error. There is no unlock for the 8 GB 3050, which is GA106. The 6 GB card is 70 W, needs no power cable and has DisplayPort. {{Source|handle=arabus_74064|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564404556807409755}} {{Source|handle=arabus_74064|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564432596006342677}} {{Source|handle=arabus_74064|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564417689638670398}} {{Source|handle=arabus_74064|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564418132557439079}} {{Source|handle=arabus_74064|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564587181136412712}}
* {{Status|Reported}} '''Press.''' Tom's Hardware covered the consumer-card port on 2026-10-26 and credited the project properly. {{Source|handle=stcord|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564260527918551104}} {{Source|handle=stcord|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564262619164971129}} In @djpandaman's words, "the compute unlocks from cmpunlocker were ported over to consumer cards". {{Source|handle=djpandaman|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564361831420526685}}

=== Ada, Turing and Blackwell ===
* {{Status|Reported}} '''Ada (RTX 40).''' After the 3090 results, reports came in of an RTX 4070 Ti SUPER and then RTX 4080s unlocked; @grapepepper posted the unitypit71 repo and asked for "a single, safe, unified patch". {{Source|handle=grapepepper|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562182781352550514|repo=https://github.com/unitypit71/rtx4070tisuper-tensor-unlock}} {{Source|handle=grapepepper|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562305166873460766}} {{Source|handle=grapepepper|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562184123790004285}} TOTORONG's AD103 Windows unlocker works ("Can confirm, it does work"). {{Source|handle=zagitta|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1563248053916536933|repo=https://huggingface.co/TOTORONG/AD103_win_unlocker}} {{Source|handle=dottoreargus|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1563314008717791445}} An RTX 4090 was reported unlocked with JustAResearcher/gpu-unlock-ada; @djpandaman: it can be done on AD103 too, and he was attempting AD102; @sevendaysworth unlocked an RTX 4080 FE. {{Source|handle=petrikrohn_26497|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563577439504830544}} {{Source|handle=djpandaman|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563559770307436645}} {{Source|handle=sevendaysworth|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563612387800522785}} The 32 GB AD103 card mentioned with TOTORONG's tool is a hardware memory mod, not fused-off memory. {{Source|handle=armand0e|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1563277857856159929}} {{Source|handle=da6b|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1563285352083357897}}
* {{Status|Theory}} '''Turing (RTX 20).''' On 2026-10-27 @zagitta was porting gpu-unlock to AD102 and TU102 and asked for Turing beta testers: a 2060 should work, TU116 could in theory be supported. As he understands it, LHR used the same speed-select registers with even heavier limits. {{Source|handle=zagitta|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564760826189971559}} {{Source|handle=zagitta|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564760749782605855}} {{Source|handle=zagitta|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564755222226673695}} {{Source|handle=zagitta|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564761840066756712}}
* {{Status|Theory}} '''Blackwell (RTX 50).''' Nothing has been found; the 50 series is "significantly more secure" than the 40 and 30 series, though some specific tensor ops run at about half throughput. {{Source|handle=bigfoot1144|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562848084977786922}} {{Source|handle=bigfoot1144|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562850825355657238}}
* {{Status|Theory}} '''One host with a 170HX and an un-nerfed GeForce card.''' Asked by an owner of one 170HX and two 3090s: @68x0 says it should just work, since the module runs before the NVIDIA driver loads and is gated by device IDs, and the 170HX still needs cmpunlocker; @zagitta says the module is driver-version agnostic and resets the card cleanly before handing it to the NVIDIA driver. Nobody in the thread reported trying it; @lycorascence said an earlier gpu-unlock attempt on his main system "didn't go so well" for his 3090 and CMP, with no details. Board card T-019. {{Source|handle=n3bs|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564289930123812915}} {{Source|handle=68x0|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564290149368729613}} {{Source|handle=68x0|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564291255465148520}} {{Source|handle=zagitta|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564321584070656032}} {{Source|handle=lycorascence|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564767515819773984}}
* {{Status|Theory}} @sojun80 set out to build a generic tool from cmpunlocker that adds every GPU he can, and a more unified driver for the 30 and 40 series; no repo was posted. {{Source|handle=sojun80|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562322921383264289}} {{Source|handle=sojun80|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562323023623749633}} {{Source|handle=sojun80|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562325597219192943}}

== SM and TPC unlocks on GeForce cards ==
{{Status|Theory}} 
The [[Full SM unlock]] exists only for the CMP 170HX so far. {{Source|handle=lia_oc|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1563687445906853900}} On GeForce cards every attempt is a dead end to date:
* @zagitta tried to unlock the last 2 SMs on his 3090s to make a 3090 Ti; by 2026-10-18 all register writes had been dead ends. His EVGA FTW3 has the TPC marked defective, while a cheap Palit reference card only has the last TPC marked disabled. On 2026-10-24 he rated SM unlocks on Ampere and Ada a "very low chance". {{Source|handle=zagitta|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561198485519335496}} {{Source|handle=zagitta|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561199044460806209}} {{Source|handle=zagitta|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561439653339472053}} {{Source|handle=zagitta|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1563687422380744778}}
* There is no RIR on GA102 or on the 40 series, and on a 40-series card the software-override disable does nothing for TPCs. {{Source|handle=zagitta|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564358172246933556}} {{Source|handle=djpandaman|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564477844560814223}} {{Source|handle=djpandaman|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564478027617013901}} {{Source|handle=scallion_9883|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564478177554866380}} Read-only fuse dumps from two RTX 3090s show 41 TPCs / 82 SMs enabled; the disabled TPCs are probably defective, not merely disabled. {{Source|handle=zagitta|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564323744510648351}} {{Source|handle=djpandaman|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564326321159536693}}
* Which consumer chips would have the most to gain if it ever works: on the 30 series the big GA102 goes down the stack past the 3090, on the 40 series AD102 is only on the 4090 and some RTX 4070 Ti SUPER boards (AD102-175-KEF-A1), which @djpandaman thinks have the highest ceiling. "If nvidia disabled TPCs instead of disabling whole GPCs for lower tier cards then there are huge TPC unlocks to be had". {{Source|handle=endsjeremy|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564356315906576446}} {{Source|handle=djpandaman|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564357486247542835}} {{Source|handle=djpandaman|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564358396864499814}} {{Source|handle=djpandaman|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564359951856697438}} {{Source|handle=djpandaman|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564326609987833977}} A 3080 has 16 SMs sitting idle. {{Source|handle=sojun80|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562325305580978298}} The 3080 Ti 20G reads 82 SMs and 10496 CUDA cores, a 320-bit 20 GB version of the 3090 that is only 4 SMs short of a 3090 Ti. {{Source|handle=kill3again|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562372114122805293}} {{Source|handle=sojun80|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562326228319469599}}
* @djpandaman posted a read-only AD102 fuse dump script and asked owners of a 4090, RTX 5000 Ada or RTX 6000 Ada to run it (board card T-091). {{Source|handle=djpandaman|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1564512498743378011}}

'''Telling disabled from defective.''' Start with [[gpcprobe]] ("start with my probe") and read the RIR. {{Source|handle=matstatman|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561293547838111827}} {{Source|handle=xeax|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561271837906968639}} A "NVIDIA CMP & GeForce Consumer Master Matrix" HTML page that lists active SMs per card circulated on 2026-10-18; its author says Gemini wrote it and it may still contain errors (one was spotted in the 50-series rows), so treat it as a list of things to check, not as a source. {{Source|handle=xeax|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561231396293316658}} {{Source|handle=junsulee119|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561237694812659813}} {{Source|handle=xeax|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561238274620522607}} No Windows or EFI tool shows disabled versus defective SMs on GA102 or GA104. {{Source|handle=emogop|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561820615218954351}}

== Memory mods on GeForce cards ==
* {{Status|Reported}} '''RTX 3080 10 GB to 20 GB.''' Only 3080s on the reference PCB (memory pads on the back) can be converted by adding chips. {{Source|handle=endsjeremy|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564356928698585200}} {{Source|handle=endsjeremy|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564357032339968192}} In China the conversion is a systematic project: shops move the 3080 core onto a 3090-type PCB, and the Xianyu sellers of modded 3080 and 4080 cards sell the PCBs too. {{Source|handle=ob88594|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564455261702332497}} {{Source|handle=ob88594|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564455836032696442}} {{Source|handle=ob88594|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564457231410405377}} {{Status|Theory}} Whether cmpunlocker or gpu-unlock applies to a 3080 20 GB was asked and not answered (board card T-105). {{Source|handle=iksboj|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562071405108138087}} A Chinese RTX 3080 20 GB "OEM Turbo" board shows NVLink pads; whether anyone has enabled NVLink on it was asked, no answer. {{Source|handle=dottoreargus|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558068301090005123}}
* {{Status|Theory}} '''RTX 3090 48 GB.''' The only known mod moves the GA102 to an A6000 PCB with GDDR6; nobody knew of a BIOS for a 48 GB 3090 that keeps GDDR6X. {{Source|handle=xeax|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518691940646781070/1561105461556547715}} 48 GB is "only possible on 4090 because there's a leaked vbios with 48gb config". {{Source|handle=zagitta|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561164731824218214}}
* {{Status|Contested}} '''RTX 4090 48 GB.''' A US modding service sells 48 GB 4090s at 5,000 USD.
** @quark2world avoids them: the PCB has poor voltage isolation, and "if something goes wrong takes the core with it". {{Source|handle=djpandaman|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556357979312361573}} {{Source|handle=busulle|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556358689584058470}} {{Source|handle=quark2world|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556358117082800331}} {{Source|handle=quark2world|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556358143154589778}}
** @gpmickey bought his 48 GB 4090 there, talked to the owner and vouches for the service. {{Source|handle=globalapathy|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562185972903579810}} {{Source|handle=gpmickey|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562186248041406555}}
* {{Status|Warning}} '''Back-side VRAM on clamshell cards.''' @gpmickey fried a memory chip on his 48 GB 4090 before learning that the back-side VRAM needs real airflow. Water-cooled back plates exist; his card now sits in an Octominer case with heavy airflow. {{Source|handle=gpmickey|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562183213173182551}} {{Source|handle=gpmickey|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562184017615392791}} {{Source|handle=gpmickey|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562184965977022495}}

== Other NVIDIA data-center cards ==
=== Tesla V100 and Titan V ===
* {{Status|Contested}} '''Is the V100 a real alternative?'''
** The cmpunlocker maintainer: "It's a little old and doesn't have driver support anymore". {{Source|handle=prefix10k|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518691940646781070/1556840363551883376}} {{Source|handle=_j3ns|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518691940646781070/1556852809457205309}}
** @xeax: V100s are great, but use 4 or 8 SXM2 modules with NVLink and an SM70 vLLM fork such as 1CatAI/1Cat-vLLM; without NVLink you lose tensor parallel. {{Source|handle=xeax|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563518645643255910}} {{Source|handle=xeax|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563519176327299192|repo=https://github.com/1CatAI/1Cat-vLLM}} @xanthefin gets 88 tok/s on Qwen 3.6 across two V100s with llama.cpp built from source and a 5-bit quant, and finds a couple of V100s "not far" from one 170HX in some respects, with a tuned pair of 170HX in another league. {{Source|handle=xanthefin|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561337005105746011}} {{Source|handle=xanthefin|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561337146554712207}} {{Source|handle=xanthefin|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561338197798293515}} {{Source|handle=xanthefin|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561339757517078589}}
* {{Status|Reported}} The Titan V is GV100, like the V100; its CMP relative is the 100HX, not the 170HX (above). 16 GB V100s once sold for about 200 USD, which made a Titan V memory unlock pointless. {{Source|handle=endsjeremy|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563499947305992254}} {{Source|handle=endsjeremy|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563500152654921830}} V100s can be driver-patched for gaming. {{Source|handle=xeax|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563518499362574417}}
* {{Status|Theory}} '''A V100 and a 170HX in one host.''' @nathang6866 has had V100s and a 170HX in the same Dell R730 under Proxmox, but did not run one model across them. {{Source|handle=nathang6866|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563727993896177735}} A member asked whether anyone has combined sm70 and sm80 cards (a CMP holding the active weights and KV cache, the rest on V100s) and expects a "driver nightmare"; nobody reported trying (board cards T-064, T-102). {{Source|handle=kellertreppe123|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563603462552293497}} {{Source|handle=kellertreppe123|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1563606209959825440}} {{Source|handle=zingy90210|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1563725158856917057}} Mixing rules for the 170HX are on [[Platforms]].

=== A30 and A30X ===
{{Status|Theory}} The A30 also uses HBM and appears to be the same GA100 with very aggressive harvesting, but with 24 GB; the A30X, which has a high-speed interconnect, might be more interesting. Nobody has checked what memory an A30 really carries: it is "either a dead end or an absolute gemm (either it's actually 24GB or it's 96GB)". {{Source|handle=mfj4|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559388551534350399}} {{Source|handle=programmerboi|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559417309238534227}} {{Source|handle=programmerboi|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559417345988890665}} {{Source|handle=programmerboi|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559417480248561695}} {{Source|handle=programmerboi|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562293858610577540}} {{Source|handle=programmerboi|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562294011509604473}} The A30 uses HBM2 rather than HBM2e, which may matter. {{Source|handle=mrmannyatx|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562304634125811733}} Only A30 listings, no A30X, turned up on eBay. {{Source|handle=c133|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562292323193454654}}

=== P106-090 ===
{{Status|Reported}} A screenshot shows the P106-090 mining card running at PCIe Gen2 x16. {{Source|handle=green_dam|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562504877198807110}}

== Graphics on a 170HX ==
This section is about the CMP 170HX itself.
* {{Status|Reported}} {{Cards|8 GB}} @peter643 got graphics running and found the vertex path used only 40 SMs; he reached 74 SMs by disabling an experimental NVIDIA register that limits some cross-GPC vertex work. Result: about 160 fps in Minecraft with shaders at 1080p, marginally faster than an RTX 3060 12 GB and nowhere near a 3080, at about 60 W. "I guess we need a real SM unlock to get the extra performance." Board card T-151 asks for a second card and the register name. {{Source|handle=peter643|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562209548130062348}}
* {{Status|Reported}} About 20 fps on Linux against 60 fps on Windows on the same card; the poster suspects the open driver throttles it. {{Source|handle=bigptoughneigh|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1560974594695888946}}
* {{Status|Contested}} '''Which graphics APIs work.'''
** One member: there is no DirectX, OpenGL or Vulkan support. {{Source|handle=lenxtroz|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560243206505889843}}
** Another: "vulkan is what the inference runs on". {{Source|handle=honzapat_cz|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560244068309532745}}
** @xeax: "somebody tried yes, it works, its not great because you need pcie bandwith and for the price you can find better gaming hardware". {{Source|handle=xeax|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560248546664517724}}
* {{Status|Reported}} The card has no HDMI or DisplayPort, so output needs another GPU or the iGPU, or frame-buffer copying as Looking Glass does. GA100 has hardware decode and CUDA video processing but no NVENC encoder, and it has no ROPs. {{Source|handle=tugoubxs|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564789898714816563}} {{Source|handle=phoenixone7|date=2026-10-28|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564792971906388030}} {{Source|handle=phoenixone7|date=2026-10-28|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564793143847559170}} {{Source|handle=djpandaman|date=2026-10-28|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564797526085730355}} {{Source|handle=phoenixone7|date=2026-10-28|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564795729904672792}}
* {{Status|Reported}} Tesla cards have been made to game: the Level1Techs "Gaming, on my Tesla" thread worked for P100s, and one member has run a game on a V100. An A100 "wouldnt work out of the box". For botting, P100 and V100 are "perfect for that and dirt cheap". {{Source|handle=darkmaniac7|date=2026-10-28|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564809160233844748}} {{Source|handle=lycorascence|date=2026-10-28|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564809719791489048}} {{Source|handle=xeax|date=2026-10-28|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564810330612174849}} {{Source|handle=wakeupmbrc1|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560249923767894037}}
* Claims about RT cores and OpenGL on unlocked CMP cards have no proof yet; they are listed on [[Rumours and claims to verify]].

== Non-CMP unlock projects posted on the server ==
One paragraph per project, for reference. Each is credited to its owner and to the member who posted it. '''None of them unlocks a CMP 170HX.'''

'''Zagitta/gpu-unlock.''' {{Status|Reported}} A Linux kernel module (version 2.0.0) that removes the half-rate cap on FP16, BF16 and TF32 tensor math with FP32 accumulate on GeForce RTX 30 cards (stable) and RTX 40 and 20 cards (experimental). It loads from the initramfs before the stock NVIDIA driver, writes the tensor rate selectors and resets the card, so there is no patched driver, no VBIOS flash and nothing to redo after a driver update. The README's dense BF16 GEMM numbers: RTX 3060 12 GB 27 to 51 TFLOPS, 3080 10 GB 65 to 113, 3090 75 to 125, 3090 Ti 88 to 157, 4080 104 to 193, 4090 165 to 329 peak; decode, INT8, FP8 and games are unchanged. It is opt-in per card on the kernel command line, GPL-2.0 for the module. Its card table has no GA100 or CMP IDs, so CMP cards are refused. Not 170HX work. {{Source|handle=zagitta|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561189774834802709|repo=https://github.com/Zagitta/gpu-unlock}} {{Source|handle=mrwojaketh|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563529790848372796|repo=https://github.com/Zagitta/gpu-unlock}}

'''JustAResearcher/gpu-unlock-ada.''' {{Status|Reported}} A fork of gpu-unlock (module version 1.1.1, GPL-2.0) that takes the same tensor un-nerf to the RTX 4090 and, behind per-chip opt-in flags, other Ada boards. The README reports FP16 to FP32-accumulate on a 4090 going from 165.6 to 331.6 TF/s instruction rate, while real cuBLAS GEMM gains are much smaller (FP16 +12 to 34 %, BF16 +16 to 20 % at some shapes), and a quantized MoE serving workload on a 48 GB 4090 showed no gain. It credits Zagitta/gpu-unlock, TOTORONG/AD103_win_unlocker and WildFlash1st/cmp90hx-unlock, and explicitly refuses data-center dies. Not 170HX work. {{Source|handle=petrikrohn_26497|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563578905913331836|repo=https://github.com/JustAResearcher/gpu-unlock-ada}}

'''unitypit71/rtx4070tisuper-tensor-unlock.''' {{Status|Reported}} A Korean-language brief and case study, with evidence files but no source code or binaries, for doubling FP16/BF16 to FP32-accumulate and TF32 throughput on one RTX 4070 Ti SUPER (AD103, 66 SMs) from a UEFI pre-boot app. Its Linux numbers: FP16/FP32-accumulate 94.1 to 184.8 TFLOPS, BF16 93.9 to 184.4, TF32 47.0 to 92.2, cuBLAS BF16 90.5 to 179.3; FP16 accumulate, INT8 and FFMA unchanged. The change is volatile (lost on power-off) and the repo says no universal 40-series tool is possible because every chip needs its own assets. It credits the CMP unlock work as prior art and builds on Zagitta/gpu-unlock. No license file. Not 170HX work. {{Source|handle=grapepepper|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562182781352550514|repo=https://github.com/unitypit71/rtx4070tisuper-tensor-unlock}} {{Source|handle=matstatman|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562201073068941455|repo=https://github.com/unitypit71/rtx4070tisuper-tensor-unlock}}

'''TOTORONG/AD103_win_unlocker''' (Hugging Face). {{Status|Reported}} A Windows tensor unlocker for AD103 (RTX 40) cards. @dottoreargus confirmed it works, and @zagitta started porting it into gpu-unlock; gpu-unlock-ada's AD102 support derives from it. Not 170HX work. {{Source|handle=zagitta|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1563248053916536933|repo=https://huggingface.co/TOTORONG/AD103_win_unlocker}} {{Source|handle=dottoreargus|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1563314008717791445}} {{Source|handle=zagitta|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1563314142356701305}}

'''dartraiden/NVIDIA-patcher.''' {{Status|Reported}} A long-running English and Russian project that patches NVIDIA's stock drivers so mining cards bind as display and 3D-capable GPUs: P106, P104 and P102 cards, CMP 30HX, 40HX, 50HX, 70HX, 90HX and 170HX, and a few odd SKUs. On Linux a script patches the blocked-device table in the official <code><nowiki>.run</nowiki></code> installer; on Windows the INF is rewritten and the driver re-signed (self-patching needs Windows test mode, which breaks many anti-cheat systems; the author's prebuilt releases do not). Its NVENC flavour crashes apps on cards without a hardware encoder, which includes the 170HX. No license file. It lists both 170HX device IDs, but it is '''not an unlock''': it does not touch FP32, memory, SMs or the PCIe generation, and on Linux it patches the proprietary module, so it is an alternative to cmpunlocker for graphics use, not a companion. Not 170HX unlock work. {{Source|handle=xeax|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564777747144769697|repo=https://github.com/dartraiden/NVIDIA-patcher}} See also [[Known bad combinations]].

'''mintoriakamoto/CMP100-210xFULLTENSORSxGEN3x1.''' {{Status|Contested}} The CMP 100-210 (GV100) unlock described [[#The CMP100-210xFULLTENSORSxGEN3x1 unlock|above]], with the trust warning. Not 170HX work. {{Source|handle=jma1753|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558100513931657287|repo=https://github.com/mintoriakamoto/CMP100-210xFULLTENSORSxGEN3x1}}

== See also ==
[[CMP 170HX]], [[Which card do I have]], [[Variant comparison]], [[8 GB card]], [[10 GB card]], [[Full SM unlock]], [[Driver unlock]], [[NVLink]], [[ECC]], [[PCIe x16 capacitor mod]], [[Cmpunlocker forks]], [[Tools]], [[Buying]], [[Price history and market]], [[Rumours and claims to verify]].

{{ImportFooter}}
[[Category:Hardware variants]]

CMP 170HX

2026-10-30T10:12:21Z

ImportBot: Import: what the CMP 170HX is, @markshowa, @civiloid, @djpandaman, @cute_sc2, @wakeupmbrc1, @endsjeremy, @c133, @darkmaniac7, @exile_1ck, @wingrimez_40467, @ghostinthedatacenter_87281, @dalzyyy; gap-fill from #general 2026-10-24 (release timeline, credited summary), @petrikrohn_26497

{{Status|Reported}} {{Cards|both}}

The '''NVIDIA CMP 170HX''' is a cryptocurrency mining card built on '''GA100''', the same die as the A100 data-center GPU. NVIDIA sold it in 2021 with most of the chip switched off. Since July 2026 the community has been switching it back on, and an unlocked card is now a 40-64 GB HBM card for local AI at a fraction of an A100's price. It exists in two versions, the [[8 GB card]] and the [[10 GB card]]; see [[Which card do I have]].

== The card ==
{| class="wikitable"
! Property !! Value
|-
| GPU || GA100 (GA100-105F-A1 on the 8 GB card, GA100-105A-A1 on the 10 GB card), TSMC 7 nm, 54.2 billion transistors, 826 mm²
|-
| Compute capability || 8.0 (sm_80, same as A100)
|-
| SMs as shipped || 70 of the die's 128 (4,480 CUDA cores, 280 tensor cores)
|-
| Clocks || 1,140 MHz base, 1,410 MHz boost
|-
| L2 cache || 32 MB
|-
| Memory || HBM2e: 8 GB on a 4096-bit bus (SK hynix) or 10 GB on a 5120-bit bus (Samsung)
|-
| Memory bandwidth (stock, theoretical) || 1.49 TB/s (8 GB) / 1.56 TB/s (10 GB)
|-
| PCIe as shipped || x16 edge connector, Gen1 x4 electrical
|-
| Power input || one EPS12V 8-pin (CPU 8-pin) connector; ships with a 2x PCIe 8-pin to EPS adapter
|-
| Power || 250 W TDP on the stock VBIOS; idle about 30-40 W
|-
| Cooling || passive heatsink, no fan; needs forced airflow
|-
| Display outputs || none
|-
| Form factor || dual-slot PCIe card
|-
| Released || 2021-09-01, original MSRP 4,299 USD
|}
Values from the 170th Street specification page by Amogh (GitHub amoghmunikote), the author of cmpunlocker. {{Source|handle=markshowa|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1561324784598384784|repo=https://github.com/amoghmunikote/170th-Street}} The same site's introduction page gives other SM and bandwidth figures for the variants; the specification page values are used here. Memory vendors: SK hynix HBM2e on the 8 GB card, Samsung HBM2e on the 10 GB card {{Status|Reported}}. {{Source|handle=darkmaniac7|date=2026-10-30|note=site owner, from his own cards}} A read-only two-card fuse study agrees on the vendors. {{Source|handle=exile_1ck|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557384897260294235|repo=https://github.com/ahnguyen17/ga100-fuse-re}} Earlier posts that disagreed on HBM2 versus HBM2e are listed on [[Which card do I have#Memory vendor]].

== Board and hardware ==
* '''A100 PCB with parts left off.''' The board is the A100 PCIe design with fewer components. Compared with the A100 PCIe board it leaves 5 or 6 Vcore VRM phases unpopulated, {{Source|handle=wingrimez_40467|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562888884558237807}} along with resistors on the NVLink bus and the parts of the 3.3 V NVLink clock generator. {{Source|handle=ghostinthedatacenter_87281|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562905010692558939}} The NVLink connector pins themselves are populated and connected to the core. {{Source|handle=cute_sc2|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1534501623471145011/1556562049247485954}}
* '''Out-of-spec edge connector.''' The PCB shape is outside the PCIe CEM spec and the gold fingers lack the key notch on the left. {{Source|handle=dalzyyy|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1558734798107836516}}
* '''Heat spreader.''' The 170HX package has an integrated heat spreader, like the A100 40 GB; the A100 80 GB has none, so A100 80 GB water blocks use a raised cold plate and do not fit. {{Source|handle=_arcanum_|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562136014279934004}} SXM4 A100 heatsinks do not fit either. {{Source|handle=wakeupmbrc1|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560749614171160688}} Under the IHS is a phase-change paste, not solder. {{Source|handle=gnasherrr|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1561442200003416125}} {{Status|Warning}} Some cards have been delidded by accident; the stock heatsink cannot be used on a bare die without making up the lid's thickness, or the die cooks. {{Source|handle=civiloid|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1561522776815439892}}
* '''Fan header.''' The unpopulated fan connector is vestigial: no PWM control and no fan curve in the VBIOS; even the A100 PCIe board has no PWM controller. {{Source|handle=endsjeremy|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562626996268171420}}
* '''Power connector.''' The card has a single EPS12V 8-pin input; the pinout differs from PCIe 8-pin. With the bundled adapter, both PCIe inputs carry current. {{Source|handle=civiloid|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560436414829559809}} A CPU (EPS12V) cable works directly, but its double-width latch will not clip onto the card and must be trimmed. {{Source|handle=civiloid|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558217306167844906}} {{Status|Warning}} Feeding both adapter inputs from one PCIe cable and its pigtail has burned hardware. {{Source|handle=c133|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561551536994132139}} See [[Cooling and power]].
* '''Cooling.''' The cooler is passive and sized for a server's airflow. Without a fan the card overheats even at idle and falls off the bus at 95 C. {{Source|handle=analyticeth|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557491900934791409}} Throttling starts around 76 C. {{Source|handle=zorg33|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562110134271090689}}
* '''No graphics.''' No HDMI or DisplayPort, {{Source|handle=xeax|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564777747144769697}} and GA100 has hardware decode but no NVENC encoder. {{Source|handle=djpandaman|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564781366493577297}}
* '''No FP8.''' The card is sm_80; it has no FP8 or FP4 tensor cores. {{Source|handle=cibernox|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1560230570225827862}}

== PCIe as shipped ==
The card arrives at '''PCIe Gen1 x4''' (about 0.85 GB/s measured) in a x16 slot; <code><nowiki>lspci</nowiki></code> shows <code><nowiki>LnkCap: Speed 2.5GT/s, Width x16</nowiki></code> and <code><nowiki>LnkSta: Speed 2.5GT/s, Width x4 (downgraded)</nowiki></code>. {{Source|handle=c133|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562161732137386127|repo=https://github.com/PixelML/club-170hx}} Two separate locks cause this:
* '''Speed.''' The silicon was never fused to Gen1. The Gen1 limit is a boot-time setting that cmpunlocker bypasses to reach Gen2; Gen3 and Gen4 are limited by real fuses. {{Source|handle=djpandaman|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1557879842152648776}}
* '''Width.''' The AC-coupling capacitors for 12 of the 16 lanes are not fitted, so the link trains at x4. Fitting 24 small 0402 capacitors restores x16. {{Source|handle=markshowa|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1561324784598384784|repo=https://github.com/amoghmunikote/170th-Street}} See [[PCIe capacitor mod]].

== What NVIDIA locked ==
On the stock card:
* '''Compute throttled.''' FP32 about 0.41 TFLOPS (12.99 unlocked), FP64 0.19 (6.44), INT8 1.64 (48.03); FP16 tensor math (49 TFLOPS) was left alone. The FP32 throttle hits fused multiply-add, the core instruction of most compute work. {{Source|handle=markshowa|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1561324784598384784|repo=https://github.com/amoghmunikote/170th-Street}}
* '''SMs cut''' to 70 of 128 by fuses.
* '''Memory size''' limited to 8 GB or 10 GB of the HBM on the package.
* '''PCIe''' at Gen1 x4, as above.
* '''NVLink''' fused off and its board parts left out. '''ECC''' disabled. '''Resizable BAR''' limited to 64 MiB. '''Graphics APIs''': the specification page lists CUDA and OpenCL only.
{{Source|handle=markshowa|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1561324784598384784|repo=https://github.com/amoghmunikote/170th-Street}}
* {{Status|Contested}} '''Graphics in practice.''' Members disagree, in the order posted: one said there is no DirectX, OpenGL or Vulkan support; {{Source|handle=lenxtroz|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560243206505889843}} another answered that Vulkan "is what the inference runs on"; {{Source|handle=honzapat_cz|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560244068309532745}} xeax said somebody tried gaming and "it works, its not great"; {{Source|handle=xeax|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560248546664517724}} peter643 ran Minecraft with shaders at 1080p at about 160 fps and about 60 W after enabling vertex work on all 74 SMs, marginally faster than his RTX 3060. {{Source|handle=peter643|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562209548130062348}} Details: [[Other CMP cards and other NVIDIA GPUs#Graphics on a 170HX]].

'''Why.''' The CMP line was NVIDIA's answer to the 2021 GPU shortage: dedicated mining cards meant to be useless for gaming and general compute, so they would not compete with GeForce or data-center products. The 170HX was the only CMP model NVIDIA built itself, from GA100 dies that did not make the A100 bin. {{Source|handle=markshowa|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1561324784598384784|repo=https://github.com/amoghmunikote/170th-Street}} The A100 hides bad HBM blocks by itself; on the 170HX owners have to mark them by hand at boot (see [[8 GB card#Memory]]). {{Source|handle=cute_sc2|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556661094272073809}} The fuses that enforce the cut are electrical fuses inside the GPU die, not on the board. {{Source|handle=wakeupmbrc1|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1559797674931265647}}

== From mining card to AI card ==
The card surfaced in China on 2021-09-01, mining Ethereum at about 164 MH/s at 250 W for roughly 4,700 USD. The Ethereum Merge on 2022-09-15 ended GPU mining of Ethereum and prices collapsed to 300-500 USD; by 2025 cards sold on eBay for 200-400 USD. A 2023 workaround (turning off FMA contraction) recovered some FP32 speed, and a 2025 paper measured it for LLM inference. {{Source|handle=markshowa|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1561324784598384784|repo=https://github.com/amoghmunikote/170th-Street}} In July 2026 the compute unlock (2026-07-12), the public cmpunlocker release (2026-07-14/15), the memory geometry unlock (2026-07-18) and Gen2 (2026-07-23/24) followed in quick succession. {{Source|handle=zagitta|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559239172202565735|repo=https://github.com/Consensus-Protocol/cmp170hx}} {{Status|Reported}} Petri Krohn's account of the releases, posted 2026-10-24 (a summary of one person's view; see [https://discord.com/channels/1518634379604136178/1518692084729511967/1563596344675803278 Discord]): the proof of concept was described in Jon Pry's Canary paper in mid-June 2026 and was never meant to be released. A "Clean Room" team shared a driverless unlocker on GitHub on 2026-07-12; it unlocked compute only, and within days 170HX prices and the global Pearl hash rate roughly doubled. It did not unlock memory because the memory configuration did not survive a function-level reset (FLR); a version 2 that needed no FLR was ready around 2026-07-18. From 2026-07-15 Russian Telegram channels spread a Chinese unlock, which replaced the Clean Room unlocker in Amogh's cmpunlocker repo; per Petri, a diff showed it was a version of the original proof of concept. He prefers the driverless approach, delivered by a Python script before the drivers load or by UEFI, as easier to understand and maintain than patching the open driver. {{Source|handle=petrikrohn_26497|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563596344675803278}} The unlock reaches the full configuration through a stack overflow in privileged early boot code, sets the card up, then hands over to the normal NVIDIA driver; not everything can be turned on on every card. {{Source|handle=endsjeremy|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564671514169712833}} The compute unlocks were later ported to GeForce cards, which brought press attention to the project. {{Source|handle=djpandaman|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564361831420526685}} The cmpunlocker Discord passed 2,000 members on 2026-10-23. {{Source|handle=_j3ns|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1518675945337389118/1563027187542659178}} Some owners still mine (now Pearl) when the cards are not serving models. {{Source|handle=reala7096|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563148290185494529}}

== The two versions ==
{| class="wikitable"
! !! [[8 GB card]] !! [[10 GB card]]
|-
| PCI ID || 10de:20c2 || 10de:2082
|-
| Unlocks to || 64 GB, 74 SMs, Gen2 || 40 GB (48 GB on some), up to 128 SMs, Gen3
|-
| Why || more memory || RIR fuse records unused, so most fuses can be overridden
|}
Full table: [[Variant comparison]]. How to tell them apart: [[Which card do I have]].

== See also ==
[[Start here]] · [[Unlocks]] · [[Driver unlock]] · [[Recipes]] · [[Platforms]] · [[Cooling and power]] · [[Troubleshooting]] · [[Buying]] · [[Glossary]]

{{ImportFooter}}
[[Category:Hardware variants]]
[[Category:8 GB]]
[[Category:10 GB]]

Buying

2026-10-30T10:12:20Z

ImportBot: Import: buying guide: 8 GB vs 10 GB, prices, named sellers, scams, payment, shipping; @kellertreppe123, @djpandaman, @spectakkular, @wakeupmbrc1, @endsjeremy, @_____josh_____, @matstatman, @globalapathy, @gnasherrr, @voidgiraffe, @ob88594, @lia_oc, @lenxtroz, @sojun80; repos PixelML/club-170hx, dev-boz/cmp170hx-testsuite, evanrodgers/cmp-170hx-rir-burn-util; lab notes; gap-fill from #general 2026-10-23 to 10-26: @feralzi, @kellertreppe123, @froggao, @phoenixone7, @djpandaman,

{{Status|Reported}} {{Cards|both}}

Every CMP 170HX on the market is a used ex-mining card. In October 2026 prices moved every week, a share of the cards sold were broken, mislabelled or never shipped, and several buyers in the Discord lost money to scams. This page collects what those buyers learned. It is written for someone about to buy their first card.

Named sellers and suppliers, with what buyers reported about them, are under [[#Sellers and suppliers]]. Reports age fast; ask in #suppliers-chat on the Discord before you buy.

== Short version ==
* Know what a listing is before you pay. <code><nowiki>10de:20c2</nowiki></code> is the 8 GB card, <code><nowiki>10de:2082</nowiki></code> the 10 GB card, and some "170HX" boards only reach 32 GB. See [[Which card do I have]] and [[#Boards that are not what they seem]].
* Pay with something your own bank can reverse: a credit card, or PayPal Goods and Services funded by a credit card. Do not pay a stranger by crypto, wire, gift card or PayPal Friends and Family. See [[#Paying]].
* Buy where a return is possible, and run the tests inside the return window. Do not solder the x16 cap mod before the tests pass.
* Ask the seller for text output from the exact card you will get (serial number, memory test log), not a video.
* Test the card on arrival with memory, tensor-core and real-workload tests. A quick memory test alone misses known faults. See [[Acceptance checklist]] and [[Testing and burn-in]].
* A price far below the going rate, "brand new" cards, or a listing that promises PCIe 4.0, NVLink or 80 GB are the usual signs of a scam or of a 32 GB board. See [[#Scam patterns]].
This list summarises the sections below, which carry the sources.

== 8 GB or 10 GB ==
What each card gives with public tools, late October 2026. Details and how to tell them apart are on [[Which card do I have]] and [[Unlocks]].
{| class="wikitable"
! !! 8 GB card !! 10 GB card
|-
| PCI ID || <code><nowiki>10de:20c2</nowiki></code> || <code><nowiki>10de:2082</nowiki></code>
|-
| Memory after [[Driver unlock|cmpunlocker]] || 64 GB || 40 GB; 48 GB only on cards whose sixth memory stack is not defective
|-
| SMs || 74 with cmpunlocker v0.5 || 74 public; more after a RIR fuse burn, per card
|-
| PCIe || Gen2 after the unlock; x4 stock, x16 with the cap mod || Gen3 after a RIR fuse burn; the public burn tool does not support Gen4
|-
| Fuse headroom || no usable RIR records || 16 free RIR records, unless a previous owner used them
|}
The RIR burn tool for the 10 GB card refuses the 8 GB card because that SKU has no free RIR records, and states Gen4 is not supported. {{Source|handle=hezz1891|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564222043363352576|repo=https://github.com/evanrodgers/cmp-170hx-rir-burn-util}}. About 6 of 30 10 GB cards that @djpandaman saw tested could do 48 GB. {{Source|handle=djpandaman|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560920383782260797}} 48 GB needs the sixth memory partition to be non-defective. {{Source|handle=wakeupmbrc1|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561025802890514616}}

How people choose:
* Take the 10 GB card if you want tensor parallel or a faster interconnect. Take the 8 GB card if pipeline parallel is fine, or if you want to bet on a fuller unlock later. {{Source|handle=djpandaman|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561022003840815218}} {{Source|handle=djpandaman|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561022209097596990}}
* Do not mix the two in one tensor-parallel group unless you can tune around the Gen2 bottleneck. {{Source|handle=djpandaman|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561023025204174859}} In tensor parallel a 64 GB card and a 40 GB card behave like two 40 GB cards and run at the speed of the slower one. {{Source|handle=wakeupmbrc1|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564683926838972438}} {{Source|handle=wakeupmbrc1|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564683952453722136}} VRAM is the bottleneck in most workloads. {{Source|handle=phoenixone7|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564689147447218227}}
* @c133 runs both: 8 GB cards for KV cache room, 10 GB cards for faster ComfyUI video and audio work. {{Source|handle=c133|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561022589516775577}} The 10 GB card is the better pick for training and image or video generation. {{Source|handle=wakeupmbrc1|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559705487975514153}}
* For labs: buy for what the cards do today, not for a rumoured unlock. @djpandaman treats the 10 GB card as 40 GB, 80 SM, PCIe 4.0 x16 and the 8 GB card as 64 GB, 74 SM, PCIe 2.0 x16. {{Source|handle=djpandaman|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560008841817497732}}
{{Status|Contested}} The PCIe 4.0 figure for the 10 GB card is not what the public tools deliver (Gen3 after a fuse burn, see above); @daveedcoles asked about it in the same thread. {{Source|handle=daveedcoles|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560095147780218892}}

=== Buying a used 10 GB card ===
* Read the fuses before you pay. @dottoreargus expects 10 GB cards with spent RIR records and no unlock to reach the used market. {{Source|handle=dottoreargus|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562149898311180342}} The read-only commands of [[170hx-rir-tool]] and [[gpcprobe]] show the RIR state and which units are disabled or defective.
* The number of defective GPCs varies per card. @matstatman: "1 defective is pretty good", "0 defective is god mode". {{Source|handle=matstatman|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1557485484891050108}} {{Source|handle=matstatman|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1557485522488655984}} @ghostinthedatacenter_87281 checked these counts before buying and found two 10 GB cards with no defective GPC. {{Source|handle=ghostinthedatacenter_87281|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558157875715772506}}
* Paid hardware unlocks. A friend of @aaasss1456 had a 10 GB card unlocked at a factory in China for nearly 500 USD; it now identifies as an A100. {{Source|handle=aaasss1456|date=2026-10-10|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558296445835026556}} {{Source|handle=aaasss1456|date=2026-10-10|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558296562550177795}} @wakeupmbrc1: "thats rir macro burn". {{Source|handle=wakeupmbrc1|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558168562542317812}} {{Status|Theory}} @con3po7016 asked whether anyone had shipped cards from the US to a contact in China for such an unlock; nobody had. {{Source|handle=con3po7016|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518691940646781070/1558261468439253033}}

=== Boards that are not what they seem ===
{{Status|Warning}} Some "170HX" cards only reach 32 GB after the unlock.
* '''PG199-origin boards.''' Cards sold as "new" 170HX are often PG199 boards reconfigured to 170HX specs, which unlock to 32 GB. {{Source|handle=_arcanum_|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559546208719077477}} {{Source|handle=boz._.|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559558065915830433}} @douya4305 bought one for more than 9,000 yuan. It reported device <code><nowiki>10de:20c2</nowiki></code> and subsystem <code><nowiki>10de:1586</nowiki></code>. {{Source|handle=douya4305|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559698008516337665}} A normal 8 GB card has board part number <code><nowiki>900-11001-0108-000</nowiki></code> in <code><nowiki>nvidia-smi -q</nowiki></code>. {{Source|handle=zefrench6961|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1561765346833076396}} Check the board part number and VBIOS version before paying 170HX prices. The full list of tells is on [[Which card do I have]].
* '''Tesla-origin cards in a cheap listing.''' The Taobao store shop35050154, a large store with good ratings, listed many "170HX 8GB" cards at 9,999 RMB (just under 1,500 USD). The small print said they were PG199-origin cards. {{Source|handle=spectakkular|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1558744440066154568}} {{Source|handle=dalzyyy|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1558751494365257729}}
* '''Single-rank cards.''' Single-rank cards stop at 32 GB after the unlock; 3 of 4 cards one buyer bought were dual-rank. memtest_vulkan passed on a single-rank card that reported 64 GB, while a CUDA memory test failed past 32 GB. {{Source|handle=c133|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562161732137386127|repo=https://github.com/PixelML/club-170hx}}.
* '''Salvaged and transplanted chips.''' Salvaged 32 GB chip cards are on the market. {{Source|handle=lycorascence|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560003306045308960}} @civiloid recalls fake cards with no chips, and one CMP whose die had been transplanted from the 32 GB A100. {{Source|handle=civiloid|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559466233009676352}} {{Source|handle=civiloid|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559466533091016737}}
* '''Other CMP models.''' Check that a listing says 170HX and not only "CMP 8GB". {{Source|handle=djpandaman|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1558734002565816451}}

== What to ask a seller for ==
Seller videos prove little. Sellers send a video with many terminals and fast tab switching, with nothing that ties the card in the video to the card you get. {{Source|handle=_____josh_____|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556346781594558586}} Many reuse the same video. {{Source|handle=matstatman|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1558799367614242950}} Ask for text from the exact card and a written statement:
* the <code><nowiki>nvidia-smi -q</nowiki></code> output with the serial number, and the memory test report as a text file. {{Source|handle=globalapathy|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556312875726012448}}
* a statement in writing that the card was tested and works. @boz._.: "pictures and videos are useless". {{Source|handle=boz._.|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1558800440832041043}}
* a test of the tensor cores, not only memory. Some cards pass memory tests while their tensor cores return garbage without any error. {{Source|handle=_____josh_____|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557667556746207255}} Stay away from sellers who refuse full tests that include tensor-core output; @_____josh_____ says this includes Alifond, which "won't test the exact cards you are buying". {{Source|handle=_____josh_____|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557668203209953351}} {{Source|handle=_____josh_____|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557668265784901634}} "Anything that refuses to test has issues." {{Source|handle=ob88594|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559254126087639071}}
* a tensor throughput number from [[mmapeak]] or a PyTorch GEMM benchmark. {{Source|handle=jimtjames|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1558871079395663902}}
* the card's InfoROM black box from <code><nowiki>blackbox.py</nowiki></code> ([[gpcprobe]]): power-on hours and the logged Xid errors. @globalapathy said @matstatman's tool saved him from buying bad cards; only one of the batch was good. {{Source|handle=globalapathy|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562131178524250145}}
* for a 10 GB card, the [[gpcprobe]] readout and the RIR state (see above).

Reading a seller's numbers:
* <code><nowiki>gpu-burn -tc</nowiki></code> at about 83 TFLOPS is normal: that is TF32 tensor throughput. BF16 or FP16 should give 150 to 200 TFLOPS. {{Source|handle=jimtjames|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1558871079395663902}} A seller's clpeak run showing 83 to 84 TFLOPS on its tensor stress line raised the same question. {{Source|handle=golden_panda_97088_61593|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1558801363377455225}}
* A seller who quoted 1,800 USD and refused video testing was judged suspicious; at that price there "shouldn't be any memory errors". {{Source|handle=ob88594|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559197409509244928}} {{Source|handle=programmer_007|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559216554472644750}}

Listing text that should stop you:
* {{Status|Warning}} Claims that the card unlocks ECC, PCIe 4.0, NVLink and 80 GB. That was a seller's description. {{Source|handle=tugoubxs|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559795404076355676}} Of these only ECC is in the public cmpunlocker v0.5. {{Source|handle=lia_oc|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559708664175263932}} Stable 80 or 96 GB on a 10 GB card would need internal Samsung keys. {{Source|handle=wakeupmbrc1|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559705725696086072}}
* "PCIe 4.0" on eBay listings is autofill from before the cards were cracked, which is also why those listings do not say 64 GB. {{Source|handle=spectakkular|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558743009380671579}} {{Source|handle=spectakkular|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558743042330988606}} A seller screenshot showing "PCIe 4.0 x16" described the slot; the card itself was at x1 Gen1. {{Source|handle=xeax|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561264948468912210}} {{Source|handle=xeax|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561265565736370219}}
* "Brand new, never inserted." No new cards exist; sellers clean and relabel used ones. {{Source|handle=chris0chris0chris|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559504312105705553}} {{Source|handle=chris0chris0chris|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559506222082949155}}
* Product photos that are AI-generated, even from a seller with 9 years on the platform. {{Source|handle=con3po7016|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559963922285727826}} {{Source|handle=endsjeremy|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559965235316654212}}

== Prices as reported ==
Prices are in the currency the poster used. They are reports from buyers and observers on the date shown, not a price list. Check current sold listings before you buy. The eBay seller research page (Terapeak, sold tab) shows real sales but needs a seller account. {{Source|handle=quark2world|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556377602418151445}} {{Source|handle=quark2world|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556377662597894331}} Some say sellers can skew sold prices after the sale. {{Source|handle=djpandaman|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557249275044565013}}

{| class="wikitable sortable"
! Date !! Where !! Card !! Price !! Source
|-
| before August 2026 || mining market || 8 GB || about 100 to 300 USD as mining cards || {{Source|handle=c133|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1562161732137386127|repo=https://github.com/PixelML/club-170hx}}.
|-
| before the unlock news || not stated || 10 GB || 200 USD each, 4 cards || {{Source|handle=cuddylac997|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1557383580106227724}}
|-
| mid to late July 2026 || eBay || 8 GB || 550 USD each, first 4 cards; 12 of 16 later orders cancelled || {{Source|handle=gnasherrr|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559772189618864129}} {{Source|handle=gnasherrr|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559772811218911383}}
|-
| first day of the public unlock || not stated || 8 GB || about 580 USD each; 800 a day later || {{Source|handle=phoenixone7|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557444473083142235}} {{Source|handle=phoenixone7|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557452853172510792}}
|-
| August to September 2026 || various || 8 GB || about 800 to 1,400 USD || {{Source|handle=djpandaman|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556256308762775613}} {{Source|handle=spectakkular|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556256452526604390}}
|-
| 2026-10-01 || eBay US, sold || 8 GB || 1,900 USD || {{Source|handle=djpandaman|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559075077528616961}}
|-
| 2026-10-04 || Xianyu, one seller (wanted payment in USDT), quote || not stated || about 1,850 USD, not including import duties or shipping || {{Source|handle=voidgiraffe|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556207433670721597}} {{Source|handle=voidgiraffe|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556258101596782593}}
|-
| 2026-10-06 || Xianyu, two sellers, quote || not stated || 1,800 to 1,900 USD || {{Source|handle=voidgiraffe|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556984655566340129}}
|-
| 2026-10-04 to 10-07 || Alibaba, Ailfond (Alifond) || 8 GB || 2,400 USD, then 2,299 to 2,599, then 2,699 on 10-07; an order was cancelled at the increase || {{Source|handle=cute_sc2|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556208333373972491}} {{Source|handle=lenxtroz|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556236658322702348}} {{Source|handle=busulle|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556512895150325863}} {{Source|handle=cibernox|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557431843601649738}}
|-
| 2026-10-05 || Alibaba || 8 GB || buyer waited at 1,600, paid 2,100 USD || {{Source|handle=voidgiraffe|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556513084120760321}}
|-
| early October 2026 || Alibaba, DDP to the EU || 8 GB || about 2,150 to 2,200 EUR including the cap mod || {{Source|handle=quark2world|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557431591209275446}} {{Source|handle=kellertreppe123|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557443994567450702}}
|-
| 2026-10-07 || eBay US || 8 GB || 2,100 USD paid; listings 2,300 to 2,600; offers of 2,000 accepted the week before || {{Source|handle=locs_locs|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557249750351478805}} {{Source|handle=monroestreet|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557477281100988559}} {{Source|handle=_____josh_____|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557406879305564193}}
|-
| 2026-10-04 to 10-07 || Austria (a company), Czechia || 8 GB || about 2,800 EUR; 3,000 USD unlocked to 64 GB || {{Source|handle=busulle|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556350644514721793}} {{Source|handle=dany0_|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557477215170596997}}
|-
| 2026-10-06 || eBay Australia || 8 GB || about 4,000 AUD || {{Source|handle=voidgiraffe|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1556921329960091669}}
|-
| 2026-10-12 || China, direct from a miner, quote || 8 GB || 1,700 to 1,800 USD; another quote 1,750 USD || {{Source|handle=spectakkular|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559108621391110216}} {{Source|handle=dany0_|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559209751710269634}}
|-
| 2026-10-13 || China || 8 GB / 10 GB || 8 GB 17,000 to 19,000 RMB; 10 GB 20,000 RMB; about the same on Goofish || {{Source|handle=wakeupmbrc1|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559703803685503057}} {{Source|handle=tony_smartecom|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559576917793841264}} {{Source|handle=douya4305|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559704933568348271}} {{Source|handle=wakeupmbrc1|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559705431155155044}}
|-
| 2026-10-13 || Western markets || 8 GB || 3,000 to 3,500 USD || {{Source|handle=lenxtroz|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559511799831863317}}
|-
| 2026-10-14 || US, landed || 8 GB || 2,600 USD after fees and shipping; quotes reached 3,500 while an order was in transit || {{Source|handle=gnasherrr|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559770442984591521}} {{Source|handle=programmer_007|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559771950128173057}}
|-
| up to 2026-10-14 || Alibaba, one buyer || 8 GB || 1,200, 1,250, 1,500 and 1,900 EUR for four cards in sequence || {{Source|handle=domrockt2|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559960754466201652}}
|-
| 2026-10-14 || eBay || 8 GB || 2,500 USD for a first card || {{Source|handle=ybryany|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560002882202374156}}
|-
| 2026-10-15 || eBay EU; Xianyu || 8 GB || at least 3,000 EUR; Xianyu about 2,500 USD || {{Source|handle=reala7096|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1560280102837944341}} {{Source|handle=voidgiraffe|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1560280859871940609}}
|-
| 2026-10-16 || Taobao or Goofish, collected in Kazakhstan || 8 GB, x16 modded || 2,390 USD; China DM offers 17,500 RMB for 10 pieces (about 2,650 USD) || {{Source|handle=wakeupmbrc1|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1560567840720035893}} {{Source|handle=wakeupmbrc1|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1560574221678157845}} {{Source|handle=wakeupmbrc1|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1560574306184994848}}
|-
| 2026-10-17 || eBay US || both || 8 GB sold at 2,500 to 3,000; 8 GB listings 3,000 to 4,000; nothing below 2,500 for 10 GB || {{Source|handle=djpandaman|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560923688050630698}} {{Source|handle=feralzi|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560922835608936480}} {{Source|handle=feralzi|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560922684693418075}}
|-
| 2026-10-18 || private sale; eBay || 8 GB || 2,100 USD each privately; eBay 2,750 USD plus tax || {{Source|handle=globalapathy|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561380024278581321}} {{Source|handle=globalapathy|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561379875397566526}}
|-
| 2026-10-22 || China || 8 GB || 18,500 RMB regular; 24,000 RMB per card for bulk lots of 10 || {{Source|handle=ob88594|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562727916020695061}} {{Source|handle=ob88594|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562727235771699293}}
|-
| 2026-10-22 || CIS || 8 GB || bought at 2,380 USD, arrived costing 3,600+ USD; no change in the US yet || {{Source|handle=wakeupmbrc1|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562706859755053077}} {{Source|handle=djpandaman|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562705738218999869}}
|-
| 2026-10-23 || China || 8 GB || 3,000 to 3,600+ USD || {{Source|handle=lia_oc|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563142358089076798}} {{Source|handle=kellertreppe123|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563125212424445965}}
|-
| 2026-10-24 || private sale || 8 GB || four cards for 14,000 USD; eBay prices dropping || {{Source|handle=wakeupmbrc1|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1563680799696625785}} {{Source|handle=busulle|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563522423767179365}}
|-
| 2026-10-25 || international dealers, delivered || 8 GB || 3,300 to 3,600 USD including shipping and taxes, plus about 100 USD Alibaba payment fee || {{Source|handle=kellertreppe123|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563910041487147110}} {{Source|handle=kellertreppe123|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563910715079655578}} {{Source|handle=kellertreppe123|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563910810416185456}}
|-
| 2026-10-25 || Xianyu || not stated || about 2,500 EUR for legitimate offers, before DDP shipping to Europe || {{Source|handle=kellertreppe123|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563882154004447354}}
|-
| 2026-10-25 || EU, between members || 8 GB || buyers offered 2,500 USD to 2,800 EUR per card || {{Source|handle=kellertreppe123|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563965372304990299}} {{Source|handle=zingy90210|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1564155721644515460}}
|-
| about 2026-10-23 || Huateng price sheet || not stated || 3,199 and 3,099 USD (two tiers) || {{Source|handle=legitsplit|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1564193868478681099}}
|-
| 2026-10-19 || Facebook, a seller in Tampa || 8 GB || 18 cards, asking 100,000 USD for the lot || {{Source|handle=ghostinthedatacenter_87281|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1561537939547234387}} {{Source|handle=con3po7016|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1561558835460837388}}
|-
| 2026-10-23 || recalled || not stated || "i remember when 170hx were 2k" || {{Source|handle=amishrakefightr|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563031325747712062}}
|-
| 2026-10-24 || general || not stated || at least 3,000 USD for a real card (said of the 700 USD AliExpress listings, see [[#AliExpress and shopping search]]) || {{Source|handle=kellertreppe123|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563557826192871538}}
|-
| 2026-10-25 || Sydney, local seller || not stated, sold liquid-cooled || 3,000 AUD when bought; up 500 a week later; 4,300 AUD on 2026-10-25 || {{Source|handle=zingy90210|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563815081333231697}} {{Source|handle=zingy90210|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563816307143475302}} {{Source|handle=zingy90210|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563816325573382197}}
|-
| 2026-10-25 || offer to a member || 8 cards, Gen2 x16 cap mod done, factory tested || 23k for the eight (in $, currency not stated) || {{Source|handle=siriusrhi|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563779604039077961}} {{Source|handle=siriusrhi|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563780119426760776}}
|-
| 2026-10-26 || general || not stated || past 3,000: "prices of cmp has officially crossed 3k" || {{Source|handle=feralzi|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564130211358838867}}
|-
| 2026-10-22 || general || not stated || "almost 3K a card now" (DeeJay) || {{Source|handle=deejay9983|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562931575966932993}}
|-
| 2026-10-21 || one member's local market || 10 GB || none for sale: in August "everyone was avoiding the 10g versions", now "nobody is selling them at all" (akkerstone) || {{Source|handle=akkerstone|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562403016215240765}}
|}
A holder of more than 100 8 GB cards in China said they are hard to sell abroad because eBay's seller threshold is now high. {{Source|handle=newman_08462|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557244096446332991}} {{Source|handle=newman_08462|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557244557119197195}}

=== Disputed prices ===
{{Status|Contested}} '''10 GB versus 8 GB price.''' On 2026-10-13 one member put the 10 GB card 500 to 800 USD below the 8 GB card; another said it costs much more because of its extra unlock. {{Source|handle=lenxtroz|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559513048421634119}} {{Source|handle=endbr64|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559513274502873161}} The same week the two cost about the same on Goofish while eBay still had the 10 GB card cheaper. {{Source|handle=wakeupmbrc1|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559705431155155044}} {{Source|handle=froggao|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559705220467007631}}

{{Status|Contested}} '''Listed versus delivered price, 2026-10-25.''' Alifond's cheapest 170HX listing was 2,600 USD (and 900 USD DDP for a V100). {{Source|handle=manicraft1001|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563890771898138745}} @kellertreppe123 put the real price at 3,300 to 3,600 USD with shipping and taxes included, plus about 100 USD Alibaba payment fee. {{Source|handle=kellertreppe123|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563910041487147110}} {{Source|handle=kellertreppe123|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563910810416185456}} The 2,600 USD listing was called "not real" for the 8 GB card; the poster agreed extra fees would likely follow. {{Source|handle=wakeupmbrc1|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563909690914512899}} {{Source|handle=manicraft1001|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563909297635729440}} Listings around 3,000 USD were judged likely out of stock or a scam. {{Source|handle=kellertreppe123|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563910193543381126}}

=== Why prices moved ===
* Prices follow the unlock news. Bridges went from 500 RMB to 780 to 900 RMB after the unlock. {{Source|handle=dalzyyy|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1557824047981658204}} One buyer's seller dragged out the order and raised the price twice while news broke. {{Source|handle=zaknafar|date=2026-10-10|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558485097324355665}}
* Sellers read the Discord. {{Source|handle=spectakkular|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556232153535217776}} "This discord seems to have an effect on price fixers actions in the market." {{Source|handle=endsjeremy|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558133663303073923}}
* {{Status|Reported}} Mining pulled cards back: before August nothing profitable could be mined on them, then PRL mining made them profitable again, no major farm is willing to ship, and the sourcing cost in China rose to 16,000 CNY or more per card (2026-10-25). {{Source|handle=ob88594|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563957367823933502}} {{Source|handle=ob88594|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563957669134471251}} Nobody confirmed this from inside China. {{Source|handle=_syn_thetic_|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563971040474828851}}

=== Rules of thumb ===
Opinions, not market data.
* {{Status|Contested}} GPUs settle at about 20 USD per GB of VRAM at end of life, and the 170HX should be 30 to 40 USD per GB, so about 1,920 to 2,560 USD. {{Source|handle=endsjeremy|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556991737887457322}} Others say VRAM pricing is not linear. {{Source|handle=spectakkular|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556992415699705929}}
* {{Status|Contested}} A 170HX is worth about two RTX 3090s. {{Source|handle=voidgiraffe|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1562124790699917354}} Or 1.5 once failure rates are counted. {{Source|handle=_____josh_____|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1562353525474856963}}
* {{Status|Theory}} An AI estimate posted on 2026-10-25 put a 64 GB card at about 1,200 to 1,800 USD in a normal market without the unlock hype and PRL mining. {{Source|handle=con3po7016|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563964577228660917}}
* {{Status|Contested}} Wait or buy? On 2026-10-04 @_____josh_____ said prices would halve within weeks because sellers were chasing lost sales. {{Source|handle=_____josh_____|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556348040552390657}} {{Source|handle=_____josh_____|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556352983208435783}} Others said demand was lower but cards still sold, and that sellers would rather sell 10 cards at 3,000 than 100 at 1,000. {{Source|handle=sojun80|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556355349110587443}} {{Source|handle=quark2world|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556355513565061262}} Prices kept rising through October (see the table).

=== Alternatives people priced ===
A 40 GB A100 on eBay at 3,500 USD. {{Source|handle=deejay9983|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1557539223987425315}} A 40 GB A100 SXM4 module at about 2,300 to 2,500 USD plus a conversion board, which needs a 48 V supply. {{Source|handle=programmerboi|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559616380544880741}} {{Source|handle=_arcanum_|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559546557202694144}} Four 32 GB V100 SXM2 cards plus an NVLink board for about 3,000 EUR (128 GB). {{Source|handle=kellertreppe123|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563563502398996493}} Two unlocked 170HX instead of four RTX 3090s for one or two agents: the 170HX runs inference at about 200 W per card. {{Source|handle=wakeupmbrc1|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556699128015225016}} 80 GB A100 SXM4 modules at about 6,000 EUR before VAT from European refurbishers such as bargainhardware.eu (AIS on the US west coast was named as a major refurbisher), and 40 GB SXM4 modules at about 2,500 USD on eBay (2026-10-23 and 10-24). {{Source|handle=cute_sc2|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563266480076754976}} {{Source|handle=cute_sc2|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563316374871474319}} {{Source|handle=endsjeremy|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563288540970881155}} {{Source|handle=kellertreppe123|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563467928886714410}} {{Source|handle=intervitens|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563470430566883329}} An eBay listing offered 600 racks of 32 40 GB A100s, so more A100s are coming to market. {{Source|handle=c133|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564284093774954561}} Used workstation cards rose too: an RTX A2000 12 GB at 800 USD. {{Source|handle=lenxtroz|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518691940646781070/1560105391495446579}}

{{Status|Contested}} '''Chinese "A100 SXM4 to PCIe" cards on eBay.''' One view: an SXM4 module on a conversion board, without NVLink, at about 2,500 USD plus 800 to 1,000 USD for the board, against 4,000 to 6,000 USD for a real A100 PCIe. {{Source|handle=djpandaman|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1518691940646781070/1557891258846810168}} {{Source|handle=djpandaman|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1518691940646781070/1557892095266529342}} The other: the GPU is removed from the SXM module, reballed and soldered onto a new A100 PCIe board, where only the device ID gives it away. {{Source|handle=petrikrohn_26497|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1518691940646781070/1557900473044832259}}

More data points from 2026-10-24 to 10-26:
* A large A100 server lot appeared on eBay (@froggao totted it up at 1.2 PB of system RAM and 384 TB of VRAM); @con3po7016 called about 6,500 USD per card plus the hardware not a bad price, and @theg9483 expects the market to be flush with cards soon. {{Source|handle=theg9483|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563685018688032809}} {{Source|handle=froggao|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563685335139877045}} {{Source|handle=froggao|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563685491591618752}} {{Source|handle=con3po7016|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563689431800610827}}
* An SXM4 baseboard was listed at about 10,000 USD. Single SXM4-to-PCIe adapters exist, but they are expensive too. @kellertreppe123 expects 40 GB A100s to become e-waste soon; @xeax: that could take a while, since even V100s have risen in price. {{Source|handle=kellertreppe123|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564010177449959495}} {{Source|handle=kellertreppe123|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564010272727769158}} {{Source|handle=xeax|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564012234575716485}} {{Source|handle=xeax|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564012641029062666}} {{Source|handle=kellertreppe123|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564022954516414597}} {{Source|handle=xeax|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564077860858110045}}
* In China (@ob88594): an A100 80 GB costs 80,000 to 90,000 CNY (about 12,000 USD) and "no one would even glance at that price"; an 8x Gaudi 2 server costs about 300,000 CNY (about 45,000 USD). For Gaudi 2, only a single-card OAM adapter has been handled properly so far, without the interconnect, and open-source optimization roughly approaches A100 performance. {{Source|handle=ob88594|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564114731344728135}} {{Source|handle=ob88594|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564122703470796881}} {{Source|handle=ob88594|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564123046212665418}}
* '''V100.''' 16 GB V100s once sold for about 200 USD, with affordable SXM baseboards (@endsjeremy); prices have risen since (@xeax). @xeax recommends V100s as 4 or 8 SXM2 modules with NVLink and [https://github.com/1CatAI/1Cat-vLLM 1CatAI/1Cat-vLLM], an SM70-focused vLLM: without NVLink you cannot do tensor parallel, so inference is slower. V100s can also be driver-patched for gaming. {{Source|handle=endsjeremy|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563500152654921830}} {{Source|handle=endsjeremy|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563500366501253143}} {{Source|handle=xeax|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563518499362574417}} {{Source|handle=xeax|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563518645643255910}} {{Source|handle=xeax|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563519176327299192|repo=https://github.com/1CatAI/1Cat-vLLM}} {{Source|handle=xeax|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563532958520836192}} In #development-general @lia_oc called a 32 GB V100 SXM "realistically" the next best value after the CMP, though four of them only reach 128 GB; @ob88594 answered that the core issue is that the V100 "cannot organize enough VRAM on a single node". {{Source|handle=lia_oc|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1563693760997625980}} {{Source|handle=lia_oc|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1563693807403401268}} {{Source|handle=ob88594|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1563775601863827457}}
* '''A100 SXM4 40 GB in the UK.''' About 2,400 GBP, cheaper than an 8 GB 170HX but with 24 GB less VRAM; a retail card, but not as easy to run (@lia_oc, 2026-10-24). {{Source|handle=lia_oc|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1563694679050944573}} {{Source|handle=lia_oc|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1563694714497278084}}
* '''Renting instead.''' Unlocked CMPs were offered for rent on Lium at about 200 USD per month. {{Source|handle=feralzi|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563665260043304971}} {{Source|handle=feralzi|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563665348241264641}}

=== Selling an RTX PRO 6000 for CMPs? ===
{{Status|Contested}} @siriusrhi considered selling two RTX PRO 6000 Max-Q cards, whose price had doubled locally (about a 60,000 AUD budget), for four or more CMP 170HX to run DeepSeek V4.1 Flash or GLM 5.3 Flash. He runs GLM 5.3 Flash on SGLang with an EXL3 quant and 8 x 524K contexts. {{Source|handle=siriusrhi|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563770912912703541}} {{Source|handle=siriusrhi|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563779899439980756}} The answers, in the order posted:
* @shirogeek: first look at what people get from Maya and Strata; if the claims hold, more VRAM buys only a low single-digit percentage of speed. {{Source|handle=shirogeek|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563771461976465460}}
* @ob88594: read the open-source 170HX projects on GitHub and their published numbers; that is what you get for 20 to 50 % of the price, so decide whether you accept it. A month earlier one RTX PRO 6000 traded for ten 8 GB 170HX; now about six, with bargaining. {{Source|handle=ob88594|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563771551621582849}} {{Source|handle=ob88594|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563771839833182250}} {{Source|handle=ob88594|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563773450500448368}}
* @segmond: he would not sell a Pro 6000 for CMPs; the 6000 would crush the CMP if people put the same effort into tuning inference for it. {{Source|handle=segmond|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563771590385344624}} {{Source|handle=segmond|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563781071022071859}}
* @wakeupmbrc1: a Pro 6000 is about 20k and trades for 6 to 7 CMPs, which beat it "in anything"; a single CMP has about the same memory bandwidth as a Pro 6000 (he puts them at about 1.9 and about 2 TB/s). {{Source|handle=wakeupmbrc1|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563773536923951149}} {{Source|handle=wakeupmbrc1|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563773611813376062}} {{Source|handle=wakeupmbrc1|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563781328594280449}} {{Source|handle=wakeupmbrc1|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563781633633689684}} {{Source|handle=wakeupmbrc1|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563781707755425904}}
* @munisix owns Pro 6000 Max-Q cards but rarely uses them since he got seven 170HX running well; the CMPs are much harder to cool quietly (see [[Fans and ducts#Noise]]). {{Source|handle=munisix|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563785243050246289}} {{Source|handle=munisix|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563785635771457578}}

== Where people buy, and how it went ==
=== eBay ===
* eBay gives the strongest buyer protection: 30-day returns, and eBay sides with the buyer. {{Source|handle=sojun80|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560020015363653743}} {{Source|handle=froggao|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560022342602723490}} Make sure the item can be returned at all, preferably for free. {{Source|handle=endsjeremy|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560021560658497588}} By 2026-10-12 @djpandaman would just buy on eBay. {{Source|handle=djpandaman|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559056771916632179}}
* Sellers cancelled when prices rose. One buyer ordered 8 cards from several sellers and got 2: "out of stock" liars. {{Source|handle=sojun80|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557446517994946622}} {{Source|handle=sojun80|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557446912930615448}} @gnasherrr ordered through eBay and some through Newegg: "And those got cancelled". {{Source|handle=gnasherrr|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559773576742178827}} {{Source|handle=gnasherrr|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559773663929172040}} {{Source|handle=gnasherrr|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559773680144482327}}
* Many US listings do not ship to Germany. {{Source|handle=humandrone8721_60165|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557108593931714732}} From the US to the EU expect 200 to 300 USD in transport and customs. {{Source|handle=quark2world|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557101818885050441}}
* Sellers report the reverse scam: buyers who return rocks and still get refunded. {{Source|handle=ybryany|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560023096876990478}}

=== Alibaba ===
* {{Status|Contested}} '''Trade Assurance.''' Some always buy with it. {{Source|handle=kellertreppe123|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563879546036420730}} Others say suppliers game it: a claim keeps your money inside Alibaba, suppliers pressure you to cancel the order yourself, and the platform still tries to keep its fee. {{Source|handle=endsjeremy|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563879946655629416}} {{Source|handle=endsjeremy|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563880264294342711}} One buyer found Trade Assurance no help and got the money back by a chargeback with his bank. {{Source|handle=kellertreppe123|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563880468913324054}}
* '''Quotes.''' A quote is nominally fixed for 10 days, but "we will raise the price later so buy now" is a bluff. {{Source|handle=spectakkular|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556253834635120703}} {{Source|handle=spectakkular|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556253966495649876}} Sellers pretend not to understand fees or specs to keep the quote vague. {{Source|handle=spectakkular|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556254395908366410}} Different sales reps quote different prices and haggling works. {{Source|handle=spectakkular|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556231389018587136}} {{Source|handle=spectakkular|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556231559034708043}} Unknown buyers get higher quotes; never confirm you would accept an earlier price. {{Source|handle=spectakkular|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556232842797645905}} {{Source|handle=spectakkular|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556236251038744628}} Buyers from Korea were quoted higher; a friend asking in Chinese got a lower quote. {{Source|handle=artistosu|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556232731103338608}} {{Source|handle=artistosu|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556238447117860889}} A repeat customer got a 55 USD discount. {{Source|handle=cibernox|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556268333563646076}}
* '''Resellers.''' A reseller may sit on your order hoping to find stock after his own supplier raised the price. {{Source|handle=djpandaman|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556254518893608991}} Some vendors list stock they do not have and source it on the fly. {{Source|handle=c133|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560929577147174933}} Most excuses for delays are lies. {{Source|handle=artistosu|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556184774547079231}}
* '''Refunds.''' A seller-cancelled order refunded in full, after a 30-day wait. {{Source|handle=skirtchaser|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556356786129211493}} {{Source|handle=skirtchaser|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556357012902780939}} A wire takes 7 to 10 days each way, so a wire refund takes about twice as long. {{Source|handle=djpandaman|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556344505991569550}}
* {{Status|Warning}} '''Payment stuck.''' @fnerdman's 8-card order from the seller of the Alibaba listing "170HX-B300-Turbo-GDDR6X-384Bit", paid by T/T, sat for two weeks in the "supplier must confirm payment" state although the money had arrived. {{Source|handle=fnerdman|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1561262045083467788}} An earlier lot of 48 he had locked in with that seller never shipped. {{Source|handle=fnerdman|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1561261621924462593}} @adusts: "this seems to be the same seller using multiple different accounts". Search the Discord before buying from any Alibaba merchant. {{Source|handle=adusts|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1561260328405434449}} {{Source|handle=adusts|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1561260748326576139}}
* '''One buyer's results.''' @boz._. bought 10 cards through Alibaba from several suppliers; only Alifond was not a scam, and it refunded a card with bad HBM. The suppliers he names are under [[#Sellers and suppliers]]. {{Source|handle=boz._.|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563148969498910773}}
* '''Condition.''' Cards from Alifond arrived very dirty, with thermal pads missing on the back of the PCB and on the side components, although Alifond does the cap mod before shipping. {{Source|handle=_syn_thetic_|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563953029353443489}} {{Source|handle=_syn_thetic_|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563971432869007443}} @kellertreppe123 called the quality horrendous: his Alifond card had a bent bracket, oxidation and a screw rusted off, likely from a water-curtain cooling installation, and his cards had about 3,000 hours on them. {{Source|handle=kellertreppe123|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1561782970262757537}} {{Source|handle=kellertreppe123|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1561815759640854679}} {{Source|handle=kellertreppe123|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563126021522329601}} Outside corrosion means the board may be corroding too. {{Source|handle=wakeupmbrc1|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1561814886223450345}} Plan to clean, repad and repaste such cards; see [[Cooling and power]].
* '''Contact harvesting.''' After one quote request on Alibaba, @kellertreppe123 got three emails from different addresses. {{Source|handle=kellertreppe123|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1561354201928437933}} @djpandaman: "Joshua keeps texting my WhatsApp which is exclusively for family and friends". {{Source|handle=djpandaman|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1561377958512427146}}
* '''Excuses.''' @landontg's Alibaba seller, recommended by @redpandamining, stalled because uploaded documents had not been reviewed by Alibaba "since it is a holiday"; @voidgiraffe said the seller did not look like any Ailfond rep he had talked to. {{Source|handle=landontg|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556184552861597778}} {{Source|handle=landontg|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556186065310720001}} {{Source|handle=voidgiraffe|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556186872261116005}}

=== Xianyu (Goofish) and Taobao ===
* '''The price ladder.''' @djpandaman: the closer you buy to the Chinese source, the cheaper it gets. From most to least expensive: eBay, AliExpress, Alibaba, Taobao and 1688, then Xianyu. He goes no further than Taobao: Xianyu is too niche and he has found little there he would not buy on Taobao, though others use it. Taobao and Xianyu need a third-party forwarder or a contact to ship abroad; forwarding has a fixed shipping cost, so the savings outpace it only as the order grows. {{Source|handle=djpandaman|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563559182064689254}} {{Source|handle=djpandaman|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563559242533830837}} {{Source|handle=djpandaman|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563559263526326365}} {{Source|handle=djpandaman|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563559282081792062}} {{Source|handle=djpandaman|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563559326306541568}} {{Source|handle=djpandaman|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563559402160525505}} {{Source|handle=djpandaman|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563570896713810114}} {{Source|handle=djpandaman|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563570977097654396}} {{Source|handle=djpandaman|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563571239279140887}} {{Source|handle=djpandaman|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563571426307481702}}
* @ob88594: Xianyu has everything, and there is a good chance a listing comes with a water-cooling package. {{Source|handle=ob88594|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563440650781986887}}
* Lower prices exist, but you need a proxy, sellers will not run tests, and they cancel or do not ship. {{Source|handle=lia_oc|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557366797735567446}} {{Source|handle=lia_oc|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557366811018797060}}
* Xianyu is a used market. Sales between individuals are tax exempt in China; you pay import duty or VAT at your destination. A registered business seller adds Chinese VAT. {{Source|handle=lia_oc|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556991825422716939}} {{Source|handle=lia_oc|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556991904594264117}} The platform takes 0.6 percent. {{Source|handle=ob88594|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557026922112876646}}
* {{Status|Warning}} A large share of Xianyu requests to deal off the platform are scams. {{Source|handle=ob88594|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557027411596419183}} A seller offering a much lower price wanted payment in USDT. {{Source|handle=voidgiraffe|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556207433670721597}} Anonymous payment is "perfect for scammers". {{Source|handle=matstatman|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556267990285025284}}
* Most foreign-facing sellers are middlemen who buy on Xianyu and resell on eBay. {{Source|handle=ob88594|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556307441422041149}}
* {{Status|Warning}} Buying agents such as Superbuy, and Goofish forwarding, have no GPU test bench. One buyer's CMP cards bought that way arrived dead. {{Source|handle=kellertreppe123|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563880995692740689}} {{Source|handle=kellertreppe123|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563881100261072907}} For other goods they work well. {{Source|handle=lia_oc|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559255557162930197}} Agents earn on the exchange rate and shipping; negotiate with the seller first and have the agent use that price. {{Source|handle=spectakkular|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559253481574113341}} {{Source|handle=spectakkular|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559254307746877625}} @spectakkular's guess: agents negotiate a discount with the seller after you submit the order, before they place it (which is why placing takes them ages), and keep the spread. @djpandaman had a Taobao order from Bykski (fittings, pumps) discounted about 40 percent off the listed price once it was in the cart, and does not know whether Superbuy would have passed that discount on. {{Source|handle=spectakkular|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559253569037795460}} {{Source|handle=spectakkular|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559253739326541905}} {{Source|handle=djpandaman|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559253788798353580}} Superbuy adds 5 percent to the exchange rate in its estimates, and its cache shows old listing prices. {{Source|handle=spectakkular|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1558747112710209577}} {{Source|handle=spectakkular|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1558747573596983328}}
* {{Status|Theory}} A local tech agent in China who checks hardware before export, for about a 10 percent fee. At least one member uses one; nobody named one or reported results. {{Source|handle=endsjeremy|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563881270079913995}} {{Source|handle=endsjeremy|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563882730356211813}} @djpandaman buys through an Alibaba agent and thinks its 10 percent fee is too high. {{Source|handle=djpandaman|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559254486164439092}}
* In person: Huaqiangbei in Shenzhen is unlikely to have them openly. {{Source|handle=_arcanum_|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559917884858437663}} {{Source|handle=daveedcoles|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1560046244712161362}} @wakeupmbrc1 orders through Taobao or Goofish to Horgos and collects the cards there. {{Source|handle=wakeupmbrc1|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1560814425298968637}}
* Buying on Xianyu directly avoids tariffs and is cheaper than AliExpress, but even a member with that access called it a hassle. {{Source|handle=gnasherrr|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1564072211210309663}} {{Source|handle=gnasherrr|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1564072307398549616}}

=== AliExpress and shopping search ===
{{Status|Warning}} AliExpress 170HX listings are scams: "always has been, always will be". {{Source|handle=djpandaman|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559055093196787753}} Sellers there messaged buyers asking for an extra 500 USD for shipping. {{Source|handle=feralzi|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559773507804467211}} A 700 USD listing that asked for crypto only was raised on 2026-10-14. {{Source|handle=ybryany|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560001492008566946}} Any seller who asks you to move to WhatsApp and pay only in crypto is a red flag; you give up all buyer protection. {{Source|handle=galygious|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560003998403272725}} Cheap 170HX results on Google Shopping are pay-by-crypto scams. {{Source|handle=matstatman|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564745580272423026}} {{Source|handle=feralzi|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564745945592365077}}

{{Status|Warning}} '''700 USD listings that take only ETH or BTC (2026-10-24).''' @feralzi found many AliExpress listings for the CMP 170HX at about 700 USD, one of them the top Google result when searching for the card. Asked by @froggao whether the sellers just ask for crypto, he confirmed they accept only ETH or BTC. Real cards cost at least 3,000 USD at the time, and @phoenixone7 and @djpandaman agree these listings are almost certainly scams; AliExpress is flooded with them. @djpandaman's rule of thumb: if something from China is cheaper on AliExpress than on Taobao or Xianyu, something is fishy. Do not pay these; buy where a return is possible and pay by a method your own bank can reverse (see [[#Paying]]). {{Source|handle=feralzi|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563557488291483668}} {{Source|handle=feralzi|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563557634211053709}} {{Source|handle=kellertreppe123|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563557826192871538}} {{Source|handle=feralzi|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563558429979840523}} {{Source|handle=froggao|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563560974240452820}} {{Source|handle=phoenixone7|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563569994242068693}} {{Source|handle=phoenixone7|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563570059786592297}} {{Source|handle=djpandaman|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563570412921819147}} {{Source|handle=feralzi|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563570653213233185}}

=== Local and in person ===
* Run a test unlock, or a test script, from a bootable Linux USB stick before you pay. {{Source|handle=dottoreargus|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1558734152365244528}} {{Source|handle=dottoreargus|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1558740283620069378}} A local 8 GB card at 700 EUR is a good buy if it powers on. {{Source|handle=djpandaman|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1558734751194415165}}
* For an untested local card, check it is not the 32 GB version; the quick check is to run the unlock. {{Source|handle=dottoreargus|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1561740074851377288}} {{Source|handle=matstatman|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1561748072608833609}}
* Some sellers prefer cash in person over eBay because of chargeback scams. {{Source|handle=hamuki|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563966366804082762}} {{Source|handle=kellertreppe123|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563966457535135927}}

== Sellers and suppliers ==
What members reported about named sellers in October 2026. Each line is what the poster said, with the source; it is not a recommendation. Members' own sales are at the end.

=== Alifond ===
Also written Ailfond, ALiFond and Fond. Most October buyers in the Discord dealt with this seller.
* '''Names and storefronts.''' "Vinsen alifond is basically Huateng Technology just a different name" (@kellertreppe123). {{Source|handle=kellertreppe123|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563149708606701619}} "huantang is alifond in hong kong, I'd choose that version of the company to deal with" (@endsjeremy). {{Source|handle=endsjeremy|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563879545378046054}} Cards carry an "aliiphone" / "Aliifond" sticker, the same sticker found on the eBay listings from ALISE EXPRESS (@lenxtroz, @matstatman). {{Source|handle=matstatman|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559131917322813480}} {{Source|handle=lenxtroz|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559133326445510757}} Some say a very large eBay seller is "the same seller as alibabas alifond" (@djpandaman). {{Source|handle=djpandaman|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560925669792161794}}
* '''Buying direct.''' "alifond can be contacted directly via alise operations", bypassing eBay and other fees, paying by PayPal or credit card (@_syn_thetic_). {{Source|handle=_syn_thetic_|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563953029353443489}} @endsjeremy found the site, aliseoperations.com; there is not much in its US-based store. {{Source|handle=endsjeremy|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563955783756947497}} {{Source|handle=endsjeremy|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563956488396087473}} On 2026-10-23 @kellertreppe123 posted its AliExpress listing ("selling for 'cheap' on aliexpress still"), added "but i am not trusting this anymore", and expects them to "keep the money for a while and refund". {{Source|handle=kellertreppe123|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563296129792213072}} {{Source|handle=kellertreppe123|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563296203129626677}} {{Source|handle=kellertreppe123|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563297127726063800}}
* '''Prices.''' The early-October quotes are in [[#Prices as reported]]. About 2,600 USD while Xianyu sellers quoted 1,800 to 1,900; when cards jumped about 500 USD on 2026-10-06, @voidgiraffe: "its just ailfond". {{Source|handle=voidgiraffe|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556984655566340129}} {{Source|handle=voidgiraffe|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556984699661062219}} @spectakkular: if Ailfond believed 2,600 was the real value they would buy up the domestic 1,800 stock; they price on what customers are willing to pay. {{Source|handle=spectakkular|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556986499956998230}} {{Source|handle=spectakkular|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1557651688142409759}} A repeat customer got 55 USD off. {{Source|handle=cibernox|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556268333563646076}} Different Ailfond sales reps quoted different prices, and buyers from Korea were quoted higher. {{Source|handle=spectakkular|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556231559034708043}} {{Source|handle=artistosu|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556232731103338608}} Same price for both variants on eBay (@rrickk420). {{Source|handle=rrickk420|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558099746822955092}} On 2026-10-16 "alifond updated their price" (@junsulee119), while "their ebay listing is still 3k" (@_arcanum_). {{Source|handle=junsulee119|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1560555670183346219}} {{Source|handle=_arcanum_|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1560564436786356295}} On 2026-10-25: 900 USD DDP for a V100 and 2,600 USD for a 170HX (@manicraft1001), disputed in [[#Disputed prices]]. {{Source|handle=manicraft1001|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563890771898138745}} Several weeks before 2026-10-19 it advertised a built 170HX server for about "20g" (@endsjeremy). {{Source|handle=endsjeremy|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1561741606401351712}} {{Source|handle=endsjeremy|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1561741656129011713}}
* '''What buyers reported.''' Cards came already x16 modded (@voidgiraffe). {{Source|handle=voidgiraffe|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556144791459336227}} "they won't test the exact cards you are buying" (@_____josh_____). {{Source|handle=_____josh_____|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557668265784901634}} Against that, @landontg posted the pre-shipment video ALiFond sent him: "a video from ALiFond before they ship to me". {{Source|handle=landontg|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558105787979792455}} "Alifond told me they were testing 80/96, I thought it was a joke", about 10 GB cards (@matstatman). {{Source|handle=matstatman|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558097618079457364}} {{Source|handle=matstatman|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558097655161163827}} @landontg received a video from ALiFond of his cards running before they shipped. {{Source|handle=landontg|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558105787979792455}} @programmer_007's card hit 85 C with the fan at full speed; the fan "came with alifond package". {{Source|handle=programmer_007|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560252819938742313}} {{Source|handle=programmer_007|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560254486847557764}} Shipping was good, but the cards were "absolutely filthy" with thermal pads missing (@_syn_thetic_); "quality of them was horendous" (@kellertreppe123). {{Source|handle=_syn_thetic_|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563953029353443489}} {{Source|handle=kellertreppe123|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563958215052632115}} @kellertreppe123's Alifond card arrived with a bent bracket, oxidation and a rusted screw. {{Source|handle=kellertreppe123|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1561782970262757537}} {{Source|handle=kellertreppe123|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1561814395649269950}} @adusts waited "like a straight month" for an Alifond shipment. {{Source|handle=adusts|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1561261384686379029}} @boz._. got a refund through Alibaba for a card with bad HBM, and found Alifond "the only one that wasnt a scam" of his Alibaba suppliers. {{Source|handle=boz._.|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563148969498910773}} Alifond programmed @peter643's PEX88096 switch board for 4x x4 bifurcation but would not share the firmware, citing an NDA. {{Source|handle=peter643|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557518262659711000}} {{Source|handle=peter643|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557729337409544384}} It also sells an SXM NVLink board for V100s. {{Source|handle=kellertreppe123|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563568328000409661}}
* {{Status|Contested}} '''Vouches.'''
** "alifond huatang or what they are called are vouched from multiple guys here"; 2.6k USD DDP with the capacitor mod is acceptable (@kellertreppe123, 2026-10-04). {{Source|handle=kellertreppe123|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556319764480131215}} {{Source|handle=kellertreppe123|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556319940942893168}}
** "The multiple guys are their own bot accounts. Don't fall for it" (@_____josh_____); "this is true tho" (@djpandaman). {{Source|handle=_____josh_____|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556346381860474891}} {{Source|handle=djpandaman|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556346522562465864}}
** "id trust shenzen creative technology or alifond" (@kellertreppe123, 2026-10-24). {{Source|handle=kellertreppe123|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563568261449392351}}

=== Maggy Zhou (Alibaba sales rep) ===
* @sojun80 ordered from her about 2021 and again two months before 2026-10-11: "still good yea she's the miner's pick has been for a while". {{Source|handle=sojun80|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1558895447832137849}} {{Source|handle=sojun80|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1558895375329533993}}
* @finishtilt14 bought from her about two years earlier on a mining YouTuber's recommendation, but "since summer its been such a russian roulette to buy from anyone". {{Source|handle=finishtilt14|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1558895103404150867}}
* "Maggy is the goat" (@spectakkular). {{Source|handle=spectakkular|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1558884608467279987}} @kellertreppe123 likes her "but shes not giving me the dear price"; later "Maggie Zhou is also vouched from what i read", and he expected V100s "from maggie". {{Source|handle=kellertreppe123|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1558884524610289745}} {{Source|handle=kellertreppe123|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563149708606701619}} {{Source|handle=kellertreppe123|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563519065010479135}}
* Another rep named in the same thread: "shoutout Guiyu" (@djpandaman). {{Source|handle=djpandaman|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556256644365815942}}

=== Alibaba suppliers named in @boz._.'s results ===
{{Status|Warning}} @boz._. reports, from 10 cards bought through Alibaba (2026-10-23): {{Source|handle=boz._.|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563148969498910773}}
* '''Phat Trading Company / CONG TY TNHH DUC''': "blatant scammers, profile now removed from alibaba".
* '''Emma Lin / Shenzhen Yige Gangbeng Technology Co., Ltd.''': "took my money and sat on it a couple weeks then said they can't get stock and refunded".
* '''Lilian Lilian / Xi'an Qujiang New District Reicha Microelectronics Product Sales Department''': "tried to sell me 32gb stock, delays, tried every excuse to cancel". @kellertreppe123 also reports "do not buy from them" about this seller, with two chat screenshots (2026-10-11). {{Source|handle=kellertreppe123|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1558876886279655549}}
* '''Adolph ZhuGe / Shenzhen Qianbao Technology Co., Ltd.''': "waiting on stock", "stock was defective", "just heaps of delays then eventually offered a refund".
Suppliers members said they would trust: Shenzhen Creative Technology (@kellertreppe123) {{Source|handle=kellertreppe123|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563568261449392351}}; Shenzhen Suqiao Intelligent Technology Co., Ltd. ("Add ... to the list", @lenxtroz). {{Source|handle=lenxtroz|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563773785553903659}}

=== Other sellers and listings ===
* '''xiulianjesen (Shenzhen).''' @kellertreppe123 got "2180$ with ddp" on 2026-10-07 and asked whether anyone had bought there; on 2026-10-26 he asked again about "xulianjiesen". No one answered with an experience. {{Source|handle=kellertreppe123|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557475954887237723}} {{Source|handle=kellertreppe123|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557476041822310521}} {{Source|handle=kellertreppe123|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1564239471241592953}}
* '''Huateng price sheet''' about 2026-10-23, posted by @legitsplit: 170HX 3,199 and 3,099 USD, 90HX and 50HX 248 USD, V100 32 GB PCIe 725 USD, 4090 48 GB 4,718 USD. {{Source|handle=legitsplit|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1564193868478681099}}
* '''"LEGIT DEAL For New CMP 170HX"''' (Alibaba, 850 USD): see [[#Scam patterns]].
* '''"170HX-B300-Turbo-GDDR6X-384Bit"''' (Alibaba): see the T/T payment report under [[#Alibaba]].
* '''Superbuy''' (buying agent): see [[#Xianyu (Goofish) and Taobao]].
* '''gpulab.net''' (US): lists the x16 mod as a service at about 500 USD. {{Source|handle=globalapathy|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560685405781889145}}

=== Members selling cards, kits and services ===
Offers posted in October 2026, as posted; they are not current listings.
{| class="wikitable"
! Member !! Offer !! Date !! Source
|-
| @reala7096 || 4x 8 GB, tested, no x16 mod, 2,400 EUR each, free shipping in the EU only || 2026-10-15 || {{Source|handle=reala7096|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1560406797007978518}} {{Source|handle=reala7096|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1560407401989939203}}
|-
| @vektor_prime || 2x 8 GB (confirmed working with cmpunlocker) and 1x 10 GB, Chicago area, 200 USD under eBay || 2026-10-17 || {{Source|handle=vektor_prime|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561140768637325333}}
|-
| @matstatman, @cmurrayis || 8 GB at 5,500 USD and 5,000 USD each || 2026-10-19 || {{Source|handle=matstatman|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1561684616124043295}} {{Source|handle=cmurrayis|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1561692940378701877}}
|-
| @port00 || eBay Australia listing 237134840669; one card cap-modded; cash buyers save the eBay fees || 2026-10-21 to 10-22 || {{Source|handle=port00|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1562367810880020570}} {{Source|handle=port00|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1562885518558105611}}
|-
| @hamuki, @solada_28598 || 3x and 2x 8 GB, EU || 2026-10-25 to 10-26 || {{Source|handle=hamuki|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1563947431324811417}} {{Source|handle=solada_28598|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1564165288755462185}}
|-
| @colo2442 || 8x SlimSAS i8 cables plus PCIe x16 adapters, Europe or Germany || 2026-10-06 || {{Source|handle=colo2442|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1557026698015277067}}
|-
| @squishysquare || 3D-printed shrouds, fans and power cables as a ready-to-go kit (dual and quad), by DM. @ikyo bought the quad version; the EPS cables that came with his PSU did not work with it || 2026-10-04 || {{Source|handle=squishysquare|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1556149327943180339}} {{Source|handle=ikyo|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1556149597301243936}}
|-
| @gmzombie || x16 cap mod through an eBay listing, about 50 USD plus shipping, discount for several cards || 2026-10-04 || {{Source|handle=gmzombie|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556114029674504244}} {{Source|handle=gmzombie|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556124053839020085}}
|-
| @tokukarin || offers the cap mod service; did all his own cards || 2026-10-04 || {{Source|handle=tokukarin|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556143083807187005}}
|-
| @ikyo || knows someone who last quoted 100 USD per card for the cap mod || 2026-10-04 || {{Source|handle=ikyo|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556148743575961641}}
|-
| @neapopa || "i'd supply the caps and ask for $50" || 2026-10-27 || {{Source|handle=neapopa|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564539130241617953}}
|}

== Paying ==
"Always buy hardware by means that will let you charge back locally with your own bank." {{Source|handle=endsjeremy|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559776681315799103}}

@mfj4's ranking, from safest to most "gone". He wrote it with an AI from his own experience and asks you to take it with a grain of salt. {{Source|handle=mfj4|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559781204390187091}} {{Source|handle=mfj4|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559781323839770705}}
# Credit card through PayPal Goods and Services
# Debit card through PayPal Goods and Services
# A real Alibaba Trade Assurance order on a credit card
# Affirm or another "pay in 4" service
# A seller's "order link" on any site
# Alipay transfers, PayPal Friends and Family, Zelle, wire, crypto, gift cards
Debit card chargebacks exist under Visa's rules but are weaker, and the money is out of your account while you wait. {{Source|handle=mfj4|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559780482017927250}} {{Source|handle=adusts|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559780016215298141}} Never use PayPal Friends and Family with a seller. {{Source|handle=mfj4|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559782369609654334}}

Costs of the safer options: about 3 percent credit card fee plus 2 percent foreign exchange fee {{Source|handle=matstatman|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556285408659247197}}, and about 3 percent for Trade Assurance. {{Source|handle=_____josh_____|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556347480944152639}} One quote was about 300 EUR higher by Visa or Apple Pay than by wire. {{Source|handle=busulle|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556346400567070861}} "That extra 2-3% you pay for credit card is a life saver for charge back." {{Source|handle=djpandaman|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556347163645313207}} A US wire takes 7 to 10 days and cannot be stopped once sent. {{Source|handle=djpandaman|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556344172774948880}} Some members pay suppliers they trust in USDT, which gives no recourse. {{Source|handle=sojun80|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556344583594573966}}

For parts, contacting a supplier directly for a combined order got @_syn_thetic_ about 140 USD per water block, with discounts even on a small order: "just always use paypal and credit card". {{Source|handle=_syn_thetic_|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1545982693903306813/1563734136701722645}} {{Source|handle=_syn_thetic_|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1545982693903306813/1563742052766720062}}

== Shipping, customs and tax ==
* Check the incoterm on every quote. DAP to the US means you pay customs and about 50 percent tariffs on arrival, though it is usually the fastest. {{Source|handle=lenxtroz|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556265856252514367}} {{Source|handle=lenxtroz|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556266593212698674}} A DDP order to the EU went through the seller's own shipper into Germany and then on. {{Source|handle=busulle|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556267198333587529}} {{Source|handle=busulle|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556267914934624328}}
* EU: about 500 EUR in taxes on a card bought inside the EU. {{Source|handle=matstatman|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561471786904723507}} Swiss VAT is 8.1 percent. {{Source|handle=shirogeek|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561472047652282441}} There are few ex-mining cards in the EU because electricity was too expensive to mine. {{Source|handle=busulle|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556352130967932980}}
* Buying agents can put a lower value on the customs declaration, and will by default. Superbuy under-declared a package for @spectakkular; he made them redeclare it at full value. If you want the full value declared, tell the agent. {{Source|handle=spectakkular|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559254024052678727}} {{Source|handle=spectakkular|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559255234658836561}}
* When @wakeupmbrc1 offered to act as a forwarder near the Chinese border, @spectakkular's view was that a domestic middleman (one in your own country) is better, because then you have legal protection. {{Source|handle=wakeupmbrc1|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559255242476884063}} {{Source|handle=spectakkular|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559255637664210945}}
* If a quote from China includes Chinese tax, an export channel could recover about 13 percent. {{Source|handle=spectakkular|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556987478240403477}}
* Shipping damage: one of four cards bought by PayPal Goods and Services with shipping insurance arrived in a box with a hole and a bracket bent about 30 degrees. It had shown proof of life and unlock before shipping and was no longer detected on PCIe. He filed a shipping insurance claim and would not know the outcome for about two weeks. {{Source|handle=globalapathy|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561378037684113531}} {{Source|handle=globalapathy|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561380398091735112}} {{Source|handle=globalapathy|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561381357920452681}} {{Source|handle=globalapathy|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561381534022238223}} Reballing a die this size is a job for a repair shop. {{Source|handle=_orrorin|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561383811860922522}}

== Scam patterns ==
{{Status|Warning}} Patterns members ran into, with what happened.
* '''Fake tracking.''' An Alibaba seller built a fake tracking website and tracking number and stretched the Alibaba dispute twice; Alibaba sided with the seller despite the evidence. Only a credit card chargeback recovered the money. {{Source|handle=djpandaman|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556347272445431809}} {{Source|handle=djpandaman|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557447533096214549}}
* '''A box of metal plates.''' @darkmaniac7 received a sealed multi-card order, bought on eBay, that contained metal plates instead of cards. The parcel came from Hong Kong through a forwarder that had repacked it. The shipping label declared a different item and about half the weight the parcel really had. He filmed the unboxing in one continuous take from the sealed box, kept the delivery camera footage, weighed the parcel, and opened an eBay Money Back Guarantee case ("not as described"). He kept all messages on eBay and refused partial refunds; a card chargeback was held back as the fallback because filing one closes the eBay case. The case was still open when this page was written. {{Source|handle=darkmaniac7|date=2026-10-26|note=lab notes}}
* '''Fake delivery to someone else.''' @mfj4 paid 3,000 USD by PayPal Goods and Services on a credit card for two cards from a Facebook Marketplace listing, "CMP 170HX 8Gb 16x PCIe 64GB Unlock", 1,200 USD each. The seller talked shop and said they modded cards locally. After three weeks of delays the chat moved from Facebook to Gmail, and the FedEx delivery photos showed someone else's door; the seller would not send a picture of the label. After he filed an Item Not Received claim, a new tracking number showed "delivered" to another address in his town. PayPal refunded him the same day. His lessons: Goods and Services on a credit card, never Friends and Family; a seller who will not screenshot the label is your answer; screenshot carrier delivery photos the day they post; file the claim before the fake "delivered" scan; export the chat, because your address in writing matters. {{Source|handle=mfj4|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559755269477503098}} {{Source|handle=mfj4|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559755491905896563}} {{Source|handle=mfj4|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559759094993256499}} @adusts says the pattern is common: a friend of his was hit the same way, with a fake UPS tracking number and payment through a checkout link the seller supplied. {{Source|handle=adusts|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559758229251301499}} {{Source|handle=adusts|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559759824344846357}} {{Source|handle=adusts|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1559760074417766531}}
* '''Far below market, crypto or wire only.''' An Alibaba listing titled "LEGIT DEAL" at 850 USD took wire transfer only and blocked the buyer after questions. {{Source|handle=domrockt2|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557250230636904449}} AliExpress listings at about 700 USD on 2026-10-24 took only ETH or BTC. {{Source|handle=feralzi|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563570653213233185}} See also [[#AliExpress and shopping search]].
* '''Cancel or reprice after the news.''' See [[#eBay]] and [[#Why prices moved]].
* '''Extra money after payment.''' Demands for more shipping money after the purchase. {{Source|handle=feralzi|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559773507804467211}} E1.S drive cages from AliExpress, Alibaba and Taobao followed the same pattern: every seller asked for more money after purchase or claimed the item was broken. {{Source|handle=cute_sc2|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564388866360869066}}
* '''"New" cards and 32 GB boards.''' See [[#Boards that are not what they seem]].
* '''Reused test videos.''' See [[#What to ask a seller for]].
* {{Status|Contested}} '''Vouches.''' Whether the many vouches for Alifond are real is disputed; see [[#Alifond]].
* '''No Trade Assurance.''' @artistosu reports the seller in his screenshot is a scammer, and @spectakkular says the same seller refused Trade Assurance; the name is only in the screenshot. {{Source|handle=artistosu|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556258881489870850}} {{Source|handle=spectakkular|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556272932655992873}} @djpandaman reports that a seller shown in two of his screenshots (one person, two accounts) "owes me 2 grand". {{Source|handle=djpandaman|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556258294006284351}} {{Source|handle=djpandaman|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1556258639977783296}}
* '''Parts too.''' A PLX switch board seller with all-positive reviews and good communication sent a defective board twice; it shorted when the CPU power connectors were plugged in. {{Source|handle=lubakmanqk|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562912202896179281}} {{Source|handle=lubakmanqk|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1563122360251457646}} {{Source|handle=lubakmanqk|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1563125645213433957}}

== How often cards are bad ==
{{Status|Contested}}
* @_____josh_____: the cards have a 50 percent failure rate, the good stock sold earlier, and sellers now mix lemons into shipments. {{Source|handle=_____josh_____|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557666958608957521}} {{Source|handle=_____josh_____|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557793719309308017}}
* Others: 5 of 5 good {{Source|handle=c133|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557769336930967614}}, 12 of 12 bought a month before the leak {{Source|handle=bigfoot1144|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557785453850140733}}, 4 of 4 {{Source|handle=cibernox|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557795179883266082}}; "nowhere near that high". {{Source|handle=lia_oc|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557693615038275648}} @ghostinthedatacenter_87281 returned one bad 8 GB card. {{Source|handle=ghostinthedatacenter_87281|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557383069386932296}}
* @civiloid: the overall failure rate reported in the Discord is about 20 percent. {{Source|handle=civiloid|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559465371696898182}}
* Cheap 8 GB cards in China are often the ones that failed to unlock. Known faults: HBM memory errors, GSP that cannot initialize, engineering-sample versions. {{Source|handle=bayley_w|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559439559153164409}} {{Source|handle=ob88594|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559444362893594626}} One member's first card had hundreds of memory errors, too many to work around. {{Source|handle=replacedriver47|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559469519016042608}}
* Resellers of mining cards usually do not test; refunds for bad units are built into their margins. {{Source|handle=spectakkular|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557693668859576382}}

What to do with a card that fails is on [[Testing and burn-in]] and [[Troubleshooting]].

== The x16 cap mod ==
Stock cards lack the AC-coupling capacitors on 12 of 16 PCIe lanes and train at x4; the cap mod restores x16. It only changes transfer speed. If you may return the card, test it before soldering. {{Source|handle=boz._.|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1558098091574562848|repo=https://github.com/dev-boz/cmp170hx-testsuite}}. Some cards are sold with the mod done. {{Source|handle=voidgiraffe|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556144791459336227}} {{Source|handle=wakeupmbrc1|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1560568905661943964}}

What people paid to have it done:
* 45 USD per card at a local microsoldering shop in California, found by searching Yelp for "microsolder" and calling around; he supplied the 0402 capacitors. {{Source|handle=gnasherrr|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562489999650324684}} {{Source|handle=gnasherrr|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562495213241372673}} {{Source|handle=gnasherrr|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562496346970267659}}
* About 50 CNY in China. {{Source|handle=lxtend|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562505132497838254}}
* A local shop asked 175 USD per card with the capacitors supplied, and would not guarantee the card would be "repaired". {{Source|handle=danske1|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564531936184115221}} {{Source|handle=danske1|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564538706407202928}}
* gpulab.net lists the mod as a service at about 500 USD; the tools to do it yourself cost under 100 USD. {{Source|handle=globalapathy|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560685405781889145}} {{Source|handle=endsjeremy|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560688687858061566}}
How to do it is on [[Unlocks]].

== Other parts people bought ==
{| class="wikitable"
! Part !! Price reported !! Date !! Source
|-
| PEX88096 PCIe switch boards || 3 boards with cables and risers for 1,200 CAD (about 850 USD) || 2026-10-22 || {{Source|handle=gpmickey|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562945228627775619}} {{Source|handle=gpmickey|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1562945533230714892}}
|-
| PEX88096 board on Goofish || about 1,300 RMB, untested by the poster || 2026-10-16 || {{Source|handle=dalzyyy|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1560649525549342921}}
|-
| NVLink bridge, dual slot (900-53651-0000-000) || Taobao quote 780 RMB unbranded, 900 RMB NVIDIA branded, no volume discount; US retail 150 USD plus tax; about 500 RMB before the unlock || 2026-10-07 to 10-08 || {{Source|handle=djpandaman|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1557423395627466874}} {{Source|handle=djpandaman|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1557812086174781600}} {{Source|handle=djpandaman|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1557812513868087447}} {{Source|handle=dalzyyy|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1557824047981658204}}
|-
| DDR4 ECC RDIMM || about 3 to 3.5 USD per GB (2400/2666); 64 GB 2933 at 230 to 280 EUR || 2026-10-06 || {{Source|handle=zorg33|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1556933316773417021}} {{Source|handle=quark2world|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1557020821069766680}}
|-
| DDR4 ECC RDIMM || 32 GB 2400 at 150 USD; 32 GB 3200 at 220 AUD; "no cheap ddr4, nothing, anywhere" || 2026-10-25 || {{Source|handle=mlx4|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1563806897923166349}} {{Source|handle=zingy90210|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1563828279432192151}} {{Source|handle=endsjeremy|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564203933952639018}}
|-
| DDR4 RDIMM, 256 GB (8x 32 GB 2933) || 1,724.68 AUD || early October 2026 || {{Source|handle=globalapathy|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1560658925970522134}}
|-
| DDR4 from local decommissioned servers || 960 GB (60x 16 GB 2666) for 300 USD; used DIMMs bring bad sticks || 2026-10-12 || {{Source|handle=djpandaman|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559218863143653377}} {{Source|handle=sojun80|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559228691282657433}}
|-
| EPYC platform || 7742 with board and 256 GB 2933 for 1,200 USD (mid 2025); EU board alone about 1,100 EUR now || 2026-10-21 || {{Source|handle=froggao|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562282964153278586}} {{Source|handle=rh3dai|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562486078110441494}}
|-
| EPS-to-EPS cables (Australia) || Amazon or PC Case Gear, then trim with a Dremel to fit; @danske1 bought 8 with a Gigabyte chassis from eBay AU item 800469481794, which ships from China || 2026-10-27 || {{Source|handle=zarquon3157|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564587334882697299}} {{Source|handle=danske1|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564601521927233633}} {{Source|handle=danske1|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1564601803629269015}}
|-
| PEX88096 per-slot bifurcation || needs custom switch firmware; the procedure and files are on an oshwhub project page; Alifond preloaded it on @peter643's board but would not share it (NDA); only about 8 bytes seem to change || 2026-10-07 to 10-08 || {{Source|handle=peter643|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557534181284913273}} {{Source|handle=peter643|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557729337409544384}}
|-
| Tyan S8030GM2NE board || about 3,000 yuan new in box; @djpandaman bought his from the Taobao shop 苏锐服务器 (shop_id 69496519) || 2026-10-12 || {{Source|handle=djpandaman|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559225895837892779}} {{Source|handle=djpandaman|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559225914041172010}} {{Source|handle=djpandaman|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559252378216173701}}
|-
| E1.S 4 TB drives (Intel NVMe) || 8 for 2,000 total on AliExpress from a seller with 2 reviews; the first seller was a scam. That is about 16 USD per TB; @civiloid puts new NVMe at about 100 USD per TB or more (the cheapest he ever saw was about 45 USD per TB for QLC in 2023) and says E1.S being rarer than U.2/U.3 does not matter much || 2026-10-15 to 10-23 || {{Source|handle=civiloid|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560424461562290271}} {{Source|handle=civiloid|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560424578390564887}} {{Source|handle=civiloid|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560425041408163953}} {{Source|handle=cute_sc2|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1563314564307615886}} {{Source|handle=cute_sc2|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1563450654591287340}}
|}
Where to look for cheap DDR4: used workstations often hide cheap DDR4 ECC (@kellertreppe123); DDR3 ECC is the fallback, depending on how desperate you are (@xeax); @petrikrohn_26497 calls DDR4 unobtainable now. {{Source|handle=kellertreppe123|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563544624209858652}} {{Source|handle=xeax|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563550390115631165}} {{Source|handle=petrikrohn_26497|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563699481915166821}}

Water blocks, fans and power supplies are on [[Cooling and power]]. Boards and servers are on the platform pages.

== Checking a card on arrival ==
Follow the [[Acceptance checklist]]. Test inside the return window, and keep the evidence.

== See also ==
* [[Acceptance checklist]]
* [[Testing and burn-in]]
* [[Which card do I have]]
* [[Unlocks]]
* [[Cooling and power]]
* [[Troubleshooting]]
* [[Tools]]

{{ImportFooter}}
[[Category:Buying]]
[[Category:8 GB]]
[[Category:10 GB]]

10 GB card

2026-10-30T10:12:13Z

ImportBot: Import: everything for the 10 GB card, @lxtend, @djpandaman, @wakeupmbrc1, @ob88594, @scallion_9883, @lycorascence, @colo2442, @lia_oc, @feralzi, @programmerboi, @ghostinthedatacenter_87281, @zorg33; gap-fill from #general 2026-10-22 to 10-26: @djpandaman, @xeax, @_orrorin, @ob88594, @feralzi

{{Status|Reported}} {{Cards|10 GB}}

The 10 GB card is the [[CMP 170HX]] with PCI ID '''10de:2082''' and Samsung HBM2e. It has less memory than the [[8 GB card]] after unlock, but its RIR fuse records are unused, which opens a path to most of a full GA100: up to '''128 SMs''', PCIe Gen3 and more. Plan on '''40 GB''' of memory; 48 GB is a lottery. Not sure which card you have? See [[Which card do I have]]. New owner? Start with [[Start here#10gb]].

== At a glance ==
{| class="wikitable"
! !! Stock !! cmpunlocker only !! After the RIR burn and driver work
|-
| Memory || 10 GB || '''40 GB''' (40960 MiB) || 40 GB; 48 GB if the sixth stack is healthy
|-
| SMs || 70 || 74 || up to 128, per card (112, 122 and 128 seen)
|-
| PCIe || Gen1 x4 || Gen2 x4 || Gen3 (validated); Gen4 reported, not public; x16 needs the [[PCIe capacitor mod]]
|-
| ECC || off || on || on
|-
| NVLink || fused off || none || not public; needs a board-level mod
|-
| Windows || no || via the A100 40G / A800 40G driver || same
|}
Unlock geometry per the cmpunlocker constants. {{Source|handle=rh3dai|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1555480078089986138/1557643237282553956|repo=https://github.com/amoghmunikote/cmpunlocker}} The 10 GB card has 16 unblown RIR rows, which allow a full GA100 configuration while stable memory stays at 40 or 48 GB. {{Source|handle=wakeupmbrc1|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557244477805039738}} Unlocked 10 GB cards land at 112, 122 or 128 SMs. {{Source|handle=wakeupmbrc1|date=2026-10-27|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564684153704939573}} A 10 GB card now equals an A100 40G PCIe with more SMs. {{Source|handle=ob88594|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1563057728887328779}} Each number carries its status and sources in the sections below: 40 GB and the post-burn SM and Gen3 results are reproduced by several owners, 48 GB is one-card-in-five, 80 or 96 GB is disputed.

== Unlock results ==
Details and steps: [[Driver unlock]] and [[Unlocks]].

=== Step 1: cmpunlocker (same as the 8 GB card) ===
With the cmpunlocker repo a 10 GB card gets 40 GB and a few extra SMs; unlocking the whole card takes real legwork. {{Source|handle=lycorascence|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560779282609868911}} v0.5 gives +4 SMs and ECC on both variants. {{Source|handle=lia_oc|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562930836892815483}} Driver 615.71.09 works with v0.5 on 10 GB cards. {{Source|handle=68x0|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1556730977898987531}}

=== Step 2: the RIR burn ===
{{Status|Warning}} '''This is permanent.''' It burns two of the card's 16 RIR fuse records and cannot be undone. Read [[RIR fuse burn]] first.
* What it does: two RIR records, 0x0015 and 0x0095, clear the DISABLE_SW_OVERRIDE fuse (170hx-rir-tool writes them to RIR row 0 as the word 0x00950015); after that, SMs, PCIe speed and the sixth stack can be overridden in software. lxwx confirmed the record pair on a card on 2026-10-11. {{Source|handle=lxtend|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558763952391987312}} In mrpandagod's words: a 2-record burn that allows the SM unlock, PCIe 3.0/4.0 and the sixth stack on some cards. {{Source|handle=djpandaman|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1559036839988564061}}
* Tool: 170hx-rir-tool (lxwx, MIT) burns the records and dumps the fuses; it needs <code><nowiki>iomem=relaxed</nowiki></code> and root. {{Source|handle=lxtend|date=2026-10-10|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558470807888461854|repo=https://github.com/lixiangwuxian/170hx-rir-tool}} It also needs the cmpunlocker-patched driver (or a 610+ driver) loaded. {{Source|handle=lycorascence|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562150888146083964}} To unbind just the CMP without taking down other GPUs, write to that GPU's sysfs unbind path instead of unloading the driver. {{Source|handle=c133|date=2026-10-18|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561486821597122706}}
* {{Status|Proven}} Burned and working for several owners: after lxwx's card, GhostInTheDatacenter on 2026-10-19 ("Finally!!!" with a screenshot), {{Source|handle=ghostinthedatacenter_87281|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561875502824816832}} orrorin on 2026-10-20 ("we did it boys" with a screenshot; the text names no link speed or SM count). {{Source|handle=_orrorin|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562092588779970703}}
* {{Status|Warning}} Getting the packing wrong wastes records or bricks the card. Targeting the wrong address has a good chance of bricking. {{Source|handle=djpandaman|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556518823350374452}} An earlier attempt with a different encoding (0x15011401) changed nothing and wasted a row. {{Source|handle=lxtend|date=2026-10-10|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558327472724906107}}
* '''Do you need to burn at all?''' {{Status|Contested}} In the order posted:
** mrpandagod: going from 74 to 80 SMs needed no fuse override; 80 to 122 definitely did. {{Source|handle=djpandaman|date=2026-10-10|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558525921391280143}}
** OB88594: the 10G card only needs the software overlay and no writes to other RIRs. {{Source|handle=ob88594|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1564167897989910609}}
** Humvee55: a recipe plus software IFF was shared in #general; use that and do not waste RIR slots. {{Source|handle=scallion_9883|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1564398787143794831}} Earlier he posted his RIR and software-IFF notes (a 10 KB text file) for an owner who had burned the override fuse but could not finish the unlock; Feralzi fed them to his agent and reached 126 SMs. {{Source|handle=scallion_9883|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560780989079228478}} {{Source|handle=feralzi|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560870337162256425}} {{Source|handle=feralzi|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560903933323382805}}

=== SMs ===
Details: [[Full SM unlock]].
* mrpandagod took one card from 74 to 80, 94, 108 and then 122 SMs. {{Source|handle=djpandaman|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558261887014019184}} lxwx got 6 more by overriding OPT_TPC_DISABLE, {{Source|handle=lxtend|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1559195004734541988}} then all 128 SMs at full clock on 2026-10-17. {{Source|handle=lxtend|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1560981128578338927}} Feralzi reached 126. {{Source|handle=feralzi|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560903933323382805}} Waypoint enabled every SM not marked defective. {{Source|handle=waypoint3642|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561019622021398548}} Humvee55 runs 20 cards at 128 SMs and Gen3 x16. {{Source|handle=scallion_9883|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560775497091383469}}
* '''Defective GPCs.''' GPCs marked defective really are defective. {{Source|handle=zorg33|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562809952555503678}} You can still enable a defective GPC if you mask off the defective TPCs inside it. {{Source|handle=djpandaman|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562815857124450335}} Colo let an agent A/B test SM pairs and disabled only the faulty ones; one card runs 126 tested SMs. {{Source|handle=colo2442|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562811083369218079}}
* '''How far a given card goes.''' {{Status|Contested}} Details on [[Full SM unlock#How many SMs a 10 GB card reaches]]. In the order posted:
** xeax: a 10 GB card can enable every SM that is not defective, up to 128 if you are very lucky; the work is per card: unlock it with the RIR tool, test which locked parts work, then build a custom mask for that card. {{Source|handle=xeax|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563888198101377075}} {{Source|handle=xeax|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564047417069019208}}
** orrorin: both of his 10 GB cards stop at 80 SMs; anything above 80 failed a real model load, also with the other locked GPC. {{Source|handle=_orrorin|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563925584365486112}} {{Source|handle=_orrorin|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563944054738128980}}
** OB88594: more than 100 SMs is very common, so this should be an operating error; xeax: more likely heavily binned dies. {{Source|handle=ob88594|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563941999982288929}} {{Source|handle=xeax|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563944285269926040}}
* {{Status|Reported}} '''Xid 109 at 128 SMs.''' With defective GPCs enabled, a workload crashed with Xid 109 CTX SWITCH TIMEOUT; {{Source|handle=lxtend|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561006327952580661}} the fix was to disable the enabled-defective GPCs one at a time until stable; {{Source|handle=wakeupmbrc1|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561015848297299999}} disabling GPC1 fixed it. {{Source|handle=lxtend|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561081134287163555}}

=== PCIe ===
Details: [[PCIe Gen3 on the 10 GB card]].
* '''Gen3.''' lxwx had Gen3 working on 2026-10-12 (his slot is x4, so Gen3 x4 equals Gen1 x16 bandwidth). {{Source|handle=lxtend|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1559144212333600800}} A wrapper tool validated Gen3 at boot on two 40 GB cards with a 30-minute stress test and no errors. {{Source|handle=hezz1891|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564222043363352576|repo=https://github.com/evanrodgers/cmp-170hx-rir-burn-util}}
* '''Gen3 how-to (summary of lxwx's guide).''' For the 10 GB card (10de:2082) on open kernel modules 615.71.09. Steps, in short:
*# Burn the two RIR records with 170hx-rir-tool so the software-override gate opens (see Step 2 above).
*# Build the driver with the guide's patch: a probe-time fuse override that clears the two Gen3-disable fuses, plus a Gen3 register sequence run after GSP boot.
*# Load it with <code><nowiki>options nvidia NVreg_RegistryDwords="RmForceEnableGen2=1;RMPcieLinkSpeed=0x5;CmpGen3=1" cmp_fuse_gen3=0</nowiki></code>.
*# Train the link one step at a time, Gen1 to Gen2 to Gen3, with the guide's speed tool and script.
*# Accept it only when <code><nowiki>lspci -vv</nowiki></code> shows <code><nowiki>LnkSta: Speed 8GT/s</nowiki></code> on both ends and a load test gives no Xid or AER errors.
*: <code><nowiki>cmp-pcie-speed 2</nowiki></code> drops back to Gen2 at runtime. One Gen3 transition took a card off the bus until a power cycle. Only 10de:2082 was validated. Full guide: [https://github.com/lixiangwuxian/170hx_tips/blob/main/Gen3_unlock_en.md Gen3_unlock_en.md]. {{Source|handle=lxtend|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561646019870064710|repo=https://github.com/lixiangwuxian/170hx_tips}}
* '''Gen4.''' mrpandagod has Gen3 and validated Gen4 behind a PLX switch. {{Source|handle=djpandaman|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1558112557628133498}} The 10 GB card can actually use PCIe 4. {{Source|handle=cute_sc2|date=2026-10-15|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1560422460568899615}} No public Gen4 recipe exists yet. Without the capacitor mod his Gen4 attempts kept falling back to 8.0 GT/s. {{Source|handle=djpandaman|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1557882288698687630}}
* '''Width.''' x16 at any generation needs the [[PCIe capacitor mod]]. {{Source|handle=lxtend|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560914210811150400}}

=== Windows ===
The unlock works on Windows on the 10 GB card with the A100 40G or A800 40G driver. {{Source|handle=wakeupmbrc1|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558781758974197783}} A screenshot of a working 10 GB unlock on Windows was posted on 2026-10-16. {{Source|handle=arabus_74064|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1560559342212882462}}

== Memory ==
Details: [[Memory unlock on the 10 GB card]].
* '''Layout.''' 20 of 24 FBPA active (5120-bit) with 1 GiB dies; ceiling 48 GiB. {{Source|handle=matstatman|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562128904007843850|repo=https://github.com/matstatman/gpcprobe}} Every one of six cards bigfoot tested had exactly two defective FBPs. {{Source|handle=bigfoot1144|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558172581696381011}}
* {{Status|Proven}} '''40 GB''' is where the unlock lands and where most cards stop. {{Source|handle=zorg33|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557343927336697877}} {{Source|handle=wakeupmbrc1|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557420925941710921}} {{Source|handle=programmerboi|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1563753581637537904}}
* {{Status|Reported}} '''48 GB''' needs the sixth FBP to be good, {{Source|handle=wakeupmbrc1|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561025802890514616}} about 1 card in 5: mrpandagod put it near 20%, {{Source|handle=djpandaman|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559042465758060625}} 6 of 30 cards he saw tested could do it, {{Source|handle=djpandaman|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560920383782260797}} and gpulover gives 20% or less. {{Source|handle=artistosu|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1564127408305479803}} Check yours with gpcprobe before you count on 48 GB ([[Which card do I have#Check the memory layout]]).
* '''How often is the sixth stack usable?''' {{Status|Contested}} In the order posted:
** bigfoot: all six of his 10 GB cards have the last stack marked defective. {{Source|handle=bigfoot1144|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561796223017681007}}
** Lycorascence: the last stack on his card is marked disabled, not defective. {{Source|handle=lycorascence|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561854738473943041}} He also described the card as having "16/16 fuses" with the GPCs only disabled; that count came from gpcprobe's RIR checker, since he could not dump the RIR itself, and mrpandagod questioned it on those grounds. {{Source|handle=lycorascence|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562142123925577872}} {{Source|handle=lycorascence|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562142491497472041}} {{Source|handle=djpandaman|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562144754777460791}} {{Source|handle=lycorascence|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562145000421335134}}
** lxwx: defective-labelled stacks are mostly good anyway (untested). {{Source|handle=lxtend|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562165620693274655}}
* '''80 or 96 GB.''' {{Status|Contested}} Not achieved; cards that read 80 GB were unstable. {{Source|handle=tekkenz|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559048743947341955}} In the order posted:
** The extra capacity is aliasing (folding) unless address bit 14 is freed by a further unlock. {{Source|handle=colo2442|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559906143373885462}}
** The apparent capacity is aliasing in L2. {{Source|handle=scallion_9883|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560782273652195479}}
** The stacks are binned 16 GB HBM2e and the upper half would need Samsung vendor codes. {{Source|handle=djpandaman|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560892095739469847}}
** Full summary: [[Which card do I have#80 GB on the 10 GB card]] and [[Memory unlock on the 10 GB card]].
* '''Memory vendor.''' {{Status|Reported}} Samsung HBM2e (the 8 GB card uses SK hynix). {{Source|handle=darkmaniac7|date=2026-10-30|note=site owner, from his own cards}} Earlier posts disagreed on HBM2 versus HBM2e for these Samsung stacks; they are listed under the fact on [[Which card do I have#Memory vendor]].
* '''Bandwidth.''' {{Status|Theory}} With all six stacks the bus is 6144-bit, which could pass 2.5 TB/s, or 3 TB/s if Samsung memory overclocks like Hynix; untested. {{Source|handle=wakeupmbrc1|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557273045259919401}} Measured: an unlocked 10 GB card reached 1,741 GB/s at full stock. {{Source|handle=cuddylac997|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1557370302042738759}} clpeak on mrpandagod's 122-SM 40 GB card measured 1.68 to 1.82 TB/s global memory bandwidth; full results on [[Benchmarks#Compute and memory peaks]]. {{Source|handle=djpandaman|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563170579643760770}}
* '''Temperature.''' The 10 GB memory runs a few degrees warmer than the 8 GB at the same idle power (41 C versus 37 C after a repaste, both near 33 W). {{Source|handle=ghostinthedatacenter_87281|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559651382816936108}} It has two more half stacks active, so that is expected. {{Source|handle=colo2442|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1559599442166812784}}

== Limits ==
* '''Power.''' {{Status|Reported}} Above 80 SMs the card hits its power cap and memory clocks drop. mrpandagod's 122 SM card throttled even with the core locked at 1,095 MHz. {{Source|handle=djpandaman|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559236914391949484}} The cap triggers at 82 SMs, the moment an SM on a new GPC is enabled, and memory is forced to 1,100 MHz. {{Source|handle=djpandaman|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1559579981951008799}} Self-reported power becomes unreliable at that point (400 W+ readings on a 250 W VBIOS). {{Source|handle=colo2442|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562819353144066111}} {{Status|Contested}} Where it starts: xeax's (untested) sweep README treats power readings that jump above about 90 SMs as a telemetry artifact; {{Source|handle=xeax|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562869594794754209}} mrpandagod answered the same day that the wattage issues start after 80 SMs, not 90, "just when you enable an SM on a disabled GPC". {{Source|handle=djpandaman|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562878833416212491}} {{Status|Warning}} On 2026-10-23 mrpandagod's 122-SM card spiked briefly to about 400 W during benchmarks with the power limit at 250 W; he was not sure whether the value was measured or calculated. xeax, who is weighing whether to fit the 6 MOSFETs missing from his card, fears overloading the VRM. Safe limits for fully SM-unlocked cards are not known; see [[Power supplies and cabling#PSU sizing]]. {{Source|handle=xeax|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563220557363814480}} {{Source|handle=djpandaman|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563222404627431497}}
* '''Raising the limit.''' {{Status|Contested}} Approaches differ, in the order posted:
** Give the driver a truncated 8 GB unlocked VBIOS; this reached 300 W. {{Source|handle=bigptoughneigh|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556320331457761301}}
** Run 128 SMs with neither extra power phases nor a limiter: swap in the 300 W curve from the 8 GB overclock VBIOS. {{Source|handle=scallion_9883|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560793685116067925}}
** Undervolt first; beyond that, a shunt mod with the missing power phases fitted. {{Source|handle=wakeupmbrc1|date=2026-10-16|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1560717127802036260}}
** The no-flash VBIOS loader raised TDP to 300 W on drivers 610 and 615 and works with the Gen3 unlock. {{Source|handle=lxtend|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1562103260490240172}}
* '''NVLink''' ([[NVLink]]). Not public, not even for 10 GB. {{Source|handle=lia_oc|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562930961207922811}} One member says it works with a very simple hardware mod that is not his to share. {{Source|handle=bigptoughneigh|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1563312993414946827}} The missing parts are power phases and the NVLink clock circuit; {{Source|handle=globalapathy|date=2026-10-24|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1563572516910534657}} the U11 clock generator (GS7612S5MA-R) is not fitted. {{Source|handle=onemillionkates|date=2026-10-05|link=https://discord.com/channels/1518634379604136178/1534501623471145011/1556788730717675702}} Compatible bridges: PNY RTXA6000NVLINK-KIT, PNY RTXA6000NVLINK3S-KIT, NVIDIA 900-53651-0000-000. {{Source|handle=djpandaman|date=2026-10-06|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557070037209317407}} NVLink on PCIe A100-class cards links pairs only. {{Source|handle=endsjeremy|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1557823170738651217}}

== What it is good for ==
* The 10 GB card is the better buy for training and image or video generation. {{Source|handle=wakeupmbrc1|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559705487975514153}} For LLMs, VRAM is the bottleneck for most users, so trading 8 GB cards for 10 GB cards is not worth it. {{Source|handle=lia_oc|date=2026-10-22|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562931544371372094}}
* Few recipes are written for 40 GB cards yet. Mountains started collecting them. {{Source|handle=mountains1605|date=2026-10-10|link=https://discord.com/channels/1518634379604136178/1528826330454429706/1558315106926989363}} Examples: Qwen 3.8 Flash Next (iq3_s) with Strata on one 40 GB card, where moving from x4 to x16 mainly improved prefill; {{Source|handle=exile_1ck|date=2026-10-04|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1556430705146462309}} GLM 5.3 Flash 4-bit EXL3 across two 64 GB cards, one 40 GB card and an RTX 3080 20GB. {{Source|handle=vektor_prime|date=2026-10-14|link=https://discord.com/channels/1518634379604136178/1518695289278566450/1560023669416402965}} See [[All recipes]] and filter by 10 GB. Feralzi runs Nanbeige4.3-33B (dealignai's uncensored Q6_K GGUF) with about 200K context on a single 40 GB card at 27 tok/s while still tuning; see [[Recipes#10 GB card]]. {{Source|handle=feralzi|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564092405026660406}} {{Source|handle=feralzi|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1564114097694445662}}
* '''Measured peaks at 122 SMs''' (clpeak; stock power settings by the owner's account, not double-checked): FP32 21.9 TFLOPS, FP16 tensor 312 TFLOPS, INT8 tensor 605 TOPS, cuBLASLt BF16 GEMM 308 TFLOPS. Full table: [[Benchmarks#Compute and memory peaks]]. {{Source|handle=djpandaman|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563170579643760770}} {{Source|handle=djpandaman|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1563221594401407107}}
* Mixing a 40 GB and a 64 GB card works with a per-card unlock profile; fine for PP over Gen2, too slow for TP. {{Source|handle=djpandaman|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557238098662793267}}
* Compute: one unlocked 10 GB card mines 250 TH at 250 W on Pearl, against about 165 TH for akkerstone's 8 GB card with the core locked at 1,170 MHz. {{Source|handle=lxtend|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562401508354433085}} {{Source|handle=akkerstone|date=2026-10-21|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562403464015773721}}

== Known issues ==
Details: [[Troubleshooting]], [[Xid errors]], [[Driver and unlock failures]].
* {{Status|Warning}} '''Overheats in minutes without airflow.''' A new card clocked out in under 5 minutes with no cooling and showed in <code><nowiki>lspci</nowiki></code> but not in nvidia-smi. {{Source|handle=programmerboi|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1563704621388529725}} See [[Cooling and power]].
* '''Dead on arrival: VBIOS ROM reads 0xFFFF.''' GSP init fails with "did not find valid ROM signature"; suspected bad SPI flash, reflash with a hardware programmer. {{Source|handle=youngju10000|date=2026-10-08|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1557643001566728233}}
* '''Dead GPC blocks boot.''' On a card whose software-override gate is fused shut, a bad GPC6 blocks firmware boot, which blocks the PLM unlock, which blocks the RIR burn that would fix it. Unresolved. {{Source|handle=exile_1ck|date=2026-10-11|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558927475600392303}}
* '''One card stays at Gen2 in a multi-card box.''' lxwx traced it to a physically damaged on-die PCIe controller on one card; the other three ran Gen3 together. {{Source|handle=lxtend|date=2026-10-19|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1561811130291200154}}
* '''Link retraining broke on kernel 7.2.11.''' Fixed by rolling back the kernel and NVIDIA driver after the RIR burn. {{Source|handle=lycorascence|date=2026-10-23|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1563134117753651281}}

== Buying ==
Details: [[Buying]].
* Dump the fuses before paying for a used 10 GB card: cards with wasted RIR records and no unlock are expected on the used market. {{Source|handle=dottoreargus|date=2026-10-20|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1562149898311180342}}
* Reported prices: about 200 USD per card before the unlock news; {{Source|handle=cuddylac997|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1557383580106227724}} all 10 GB cards had vanished from listings by 2026-10-07; {{Source|handle=kellertreppe123|date=2026-10-07|link=https://discord.com/channels/1518634379604136178/1528513735575081070/1557444599318974566}} in China the 10 GB card cost about 20,000 RMB on 2026-10-13, more than an 8 GB card, because it is a fully unlockable GA100; {{Source|handle=wakeupmbrc1|date=2026-10-13|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1559705027709509685}} one sold "for parts" on eBay for 1,200 USD worked and unlocked to 40 GB. {{Source|handle=programmerboi|date=2026-10-25|link=https://discord.com/channels/1518634379604136178/1534370835220004885/1563753581637537904}}
* '''Paid unlock services in China.''' {{Status|Contested}} Hearsay, not verified on the Discord. A third party was said to sell a permanent 10 GB unlock for about USD 500 (Chengdu), pitched as more than an A100 40G PCIe, with NVLink extra. {{Source|handle=ob88594|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558114667325423759}} {{Source|handle=ob88594|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558116548130906113}} {{Source|handle=ob88594|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1558162519070216295}} The card then identifies as an A100 with no driver patches; Miséricorde reads it as an RIR macro burn. {{Source|handle=wakeupmbrc1|date=2026-10-09|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1558168562542317812}} The unlocking merchants on Xianyu were swamped and took the service down. {{Source|handle=ob88594|date=2026-10-12|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1559045761071714396}} The Xianyu seller offering a permanent unlock to A100 says only a few cards can reach 48 GB, and days before launching the service he had asked lxwx to sell his 10 GB cards back at market price. {{Source|handle=lxtend|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560911159681359913}} {{Source|handle=lxtend|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1560912845359681670}} Be careful with private unlock claims: a screenshot is easier to fake than a result when money is involved, and nobody has NVIDIA's production keys. {{Source|handle=djpandaman|date=2026-10-17|link=https://discord.com/channels/1518634379604136178/1518692084729511967/1561026808177229920}}

== See also ==
[[8 GB card]] · [[Variant comparison]] · [[CMP 170HX]] · [[Unlocks]] · [[Platforms]] · [[Glossary]]

{{ImportFooter}}
[[Category:Hardware variants]]
[[Category:10 GB]]

Full SM unlock/Confirmation 1

2026-10-30T10:02:54Z

ImportBot: GhostInTheDatacenter reached 128 SM on a 10 GB card, reproducing the RIR-plus-software method.; sources: @ghostinthedatacenter_87281, @68x0

{{Confirmation
|page=Full SM unlock
|confirmed_by=ghostinthedatacenter_87281
|date=2026-10-19
|cards=10 GB
|result=Reproduced
|numbers=128 SM on a 10 GB card, shown in screenshots (the posts carry no SM number in text); started from 170hx-rir-tool.
|notes=mrpandagod and lxwx established the 10 GB SM unlock; GhostInTheDatacenter reproduced it ("Finally!!!" with a screenshot on 2026-10-19, a second screenshot on 2026-10-26), as did orrorin and Waypoint. The route through the RIR burn is 68x0's line ("You can unlock more SMs with the RIR burn"), which GhostInTheDatacenter confirmed ("Exactly"). {{Source|ghostinthedatacenter_87281|2026-10-19|https://discord.com/channels/1518634379604136178/1518695328008638516/1561875502824816832}} {{Source|handle=ghostinthedatacenter_87281|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1564100458023358584}} {{Source|handle=68x0|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1564103821922275432}} {{Source|handle=ghostinthedatacenter_87281|date=2026-10-26|link=https://discord.com/channels/1518634379604136178/1518695328008638516/1564103887009484901}}
}}

{{ImportFooter}}
[[Category:Confirmations]]