"Your GPU runs AI at half speed": a Windows version that arrived 8 days late and got 1832 stars in 11 days

Late October 2026, a Linux kernel module told the world that GeForce users' AI performance was locked at half speed at the factory, and that writing a few registers doubles it. The original author doesn't do Windows. 8 days later, a Chinese repo calling itself a student interest project with classmates merged RTX 20/30/40 across three generations, desktop and laptop, Windows and Linux, into one USB stick: plug in, boot, unlock, enter the system. It arrived late, but became the standard answer for "how do Windows users do this": 11 days, 1832 stars, 171 forks, 14k downloads. How it got its stars, and whether you can still grab this spot, is covered here.

One tweet with 100k impressions, and 62 stars before it

Oct 30 22:59 (UTC), the gaming news account @Pirat_Nation with 375k followers posted:

Nvidia RTX 20, 30 and 40-series GPUs can now unlock their full AI performance thanks to a new UEFI-level tool.

("NVIDIA RTX 20, 30, and 40 series GPUs can now unlock full AI performance with a new UEFI-level tool.") By 11-06, the tweet had 103k impressions, 2173 likes, and 1140 bookmarks.

Before that, the repo had been up for 4 days with only 62 stars (daily snapshots from 10-28). After the tweet, 10-31 VideoCardz and Wccftech followed, and 11-01 Tom's Hardware ran a long-titled piece: "Open-source USB tool unlocks NVIDIA's half-speed AI limit on Windows, up to 16% FP65 gain, covers RTX 20, 30, and 40 desktops and laptops." The star curve matches exactly: 10-31, then 170,11-01, then 580,11-02, then 991 (+411 in a single day, the peak), 11-03, then 1361, and after that it fell back to around 100 per day.

The author posted a Show HN once, got 2 points and 0 comments. The stars didn't come from the author pushing; media chasing a breaking story found it on their own (inference: no sign the author pitched the press).

What it is

A UEFI program written in Rust, GPL-2.0. You copy it onto a FAT32 USB stick, boot from the stick, and it runs a chain of firmware handoffs before the NVIDIA driver loads. It changes the tensor-core throttle bit, reads it back to confirm, then auto-boots into your original Windows or Linux. No VBIOS flash, no disk changes, power off and it returns to stock. You re-plug the stick on every cold boot.

The first line of the README is "Your GeForce is running AI at half speed — this tool fixes it before the driver loads," and the next line is a Chinese-community meme: "Shocking! Jensen's knife can be reversed???" The benchmark numbers it gives: FP16 / BF16 / TF32 tensor throughput up to about 2.6×, image and video generation 14–75% faster, local LLM prefill up to 19% faster and decode only 5%. Per-card numbers are clearer: one RTX 3060 image generation went from 1.20 to 1.94 it/s, and one RTX 4080 FP16 went from 100 to 185 TFLOPS. RTX 50 series is not supported.

The demand was lit by someone else

It didn't discover this. Oct 18, Zagitta/gpu-unlock created the repo, disclosing that GeForce's "FP32 accumulate" tensor path is clamped to half speed and can be opened by changing registers. 10-24 hit HN (351 points), and over the next four days stars rose from 462 to 11.7k, now over 17k. Pro cards and data-center cards sell that slice of performance, and NVIDIA won't unlock it for GeForce.

The catch is that the original is a Linux kernel module, and the author says plainly in the README: "I don't run windows and don't plan to maintain it." Most people running Stable Diffusion, ComfyUI, or local LLMs on their own machines use Windows, and many use laptops. The topic hooked them, but they couldn't use it.

Over the following week, a pile of ports appeared on GitHub, nearly all one library per card:

It's not the first Windows version. windows-GPU-UNLOCK came 6 days earlier and has the original author's endorsement, but in the last 7 days it gained only about 630 stars, while this one gained 1718.

Why this one and not the other ports

One USB stick covers everything. Others are "4090 uses this library, 3080 uses that one"; this one is a single script that auto-detects the GPU generation, auto-downloads and verifies the NVIDIA firmware, and builds the USB. The media headline captures exactly this point: Tom's Hardware writes "covers RTX 20, 30, and 40-series desktops and laptops".

The risk is explained well enough that people dare to try. A GPU costs thousands, and ordinary players fear bricking it. It repeats four things: no VBIOS flashing, fully reversible on power-off, every write is read back and verified, errors get logged to the USB stick. The README also says that if you get a black screen, "don't retry in the same session; fully power off and remove the USB stick." The Chinese promo video title even carries the words "(low risk)."

The numbers are plentiful enough for media to quote directly. The README has a per-card compatibility matrix, dozens of user before-and-after comparisons, and an interactive "theoretical unlock ceiling" ladder chart. The "up to 75%" in the Wccftech headline and Tom's "up to 65%" both come from here.

The author really knows hardware and can fix the edge cases. The author says they've spent years modding, repairing, and rewriting cards' BIOS, and has handled several hundred NVIDIA cards. In 11 days they shipped 31 releases, half of them diagnostic builds. Issues like X99 boards failing to boot with CSM enabled, Thunderbolt ports, and lock-loss after sleep got fixed one by one, and each fix credits the person who reported the bug. The ratio of forks and stars to about 1:11,32 open issues tells you the people showing up are actually tinkering with their own cards.

Real users came from Bilibili; stars came from English media

In Oct 27, Bilibili UP host "小飞小飞允许起飞" (about 6000 followers) posted a video titled "[Open source] GPU performance boosted to 195.5%! World-first, full-platform NVIDIA GPU unlock tool (low risk)". The README calls it a "project promo video" (my inference: made by someone close to the author). It reached 11-06:207k plays, 3113 comments, and 9175 favorites.

This video brought in the first real users. Before any press coverage, the first two official releases had already been downloaded about 940 times. The comments turned into a "benchmark report" board: someone posted 3090 running Qwen-Image, cutting each image from about 60 seconds to 22 seconds; someone posted 4080 laptop FP16 going from about 57 to 80 TFLOPS; someone said it broke after 3090 sleep and wake. The author gathered these into a compatibility table in the README, with each entry linked to its comment and a screenshot hash, and explained why: "They may not be able to access GitHub because of related restrictions, so we helped collect and share their results."

But that group doesn't star repos. When the 10-28 video was already trending, the repo had only 62 stars. The stars came from 10-30 to 11-02 English media and X. Each side handled one job: the Chinese video answered "is anyone really using it, does my card work," and the English media delivered the stars.

Can you still get in on this?

That exact spot is already taken. The "Windows one-click" version is done, and a "GUI that bundles all the scattered libraries" 11-03 has already been posted on r/LocalLLaMA, with several other Windows versions out there too. Momentum is fading as well: its daily growth dropped from 411 on 11-02 to 106 on 11-06.

Few open spots remain, and they're all hard:

• RTX 50 series. The docs state that on Blackwell the gate requires higher privileges to write, and all three write attempts were dropped. Whoever pulls it off creates the next news wave, but it may simply not be doable.
• A tool that measures how much faster it actually is. Users most often ask "did I unlock it, and how much faster is my workflow really?" This project's diagnostic tool is buried in the release page and gets false-flagged by antivirus software. A cross-platform, one-click before-and-after report that you can share with the community is a much lower bar, and it could reach every user of every unlock tool in this wave.
• After NVIDIA blocks it. The README currently says lock-loss is usually a motherboard reset, not the driver fighting back. Once a driver or firmware update starts blocking it, the whole category cools off together.

If it were you

C. This repo can't be followed directly. It rode an event others ignited, its position rests on UEFI and GPU firmware reverse-engineering that few people can do, and it's already covered by a dozen outlets with copycat integrations out there. What's worth taking is the playbook, not the project.

Who it's for: developers who understand low-level hardware, firmware, or drivers and have several cards to test on, or people who want to find a spot like "the usable version after an original hit" and are willing to watch trends closely.

Who it's not for: anyone who hasn't worked with UEFI and GPU firmware (there's nothing here you can knock out in an evening with AI; a mistake means someone's GPU goes black); anyone with only one card who can't run compatibility checks; anyone worried about warranty and legal disputes over modifying hardware limits.

How to do it, from easiest to hardest:

1. Copy the playbook for the next event: watch for projects that suddenly blow up on HN and GitHub because the original "only supports X platform." The platform the original author explicitly won't support (Windows, Mac, phones, a certain country's network environment) is the gap. Entering a week late can still catch the media's second wave. The key is one tool covering every model, not another single-model port.
2. Build a companion during this wave: make a cross-platform before-and-after unlock benchmark that measures real SD image generation and local LLM inference times, and generates a shareable card with one click. You don't touch firmware, so there's no brick risk, and every unlock tool's users become your users.
3. Tackle RTX 50: only worth considering for people already in this circle who have real 50-series cards and have done firmware reverse-engineering.

How to get users: Follow this playbook. Cold-start on Chinese video platforms to get real users and hands-on feedback, and put numbers and "low risk" in the titles. Turn the hands-on results from the comments into a compatibility table with sources in the README; media loves to quote that. Don't worry if Hacker News doesn't take off. The people who actually star the repo are hardware media and big X news accounts, and they'll find it on their own while following this story. Ship one release a day for the launch week and answer issues the same day.

Deadline: Get companion tools out before this wave of hype dies down, roughly by November. Daily new stars have already dropped to a quarter of their peak.

Where the call goes wrong: ① NVIDIA blocks it in a driver or firmware update, the unlock tools all break, and companion tools go unused with them; ② if your test tool doesn't pull 100 stars in a month, users only wanted the "unlock" button, not the numbers that come after; ③ someone got it working on RTX 50, which means this line still has a third wave. Re-evaluate it.

Data and sources

• GitHub: physicsdolphin/nv-uefi-unlocker README (Chinese and English), acknowledgments, release list; daily star/fork snapshots (10-28 to 11-06); release download counts (11-06).
• Original and ports: Zagitta/gpu-unlock README FAQ; GitHub pages and star counts for windows-GPU-UNLOCK, gpu-unlock-ada, turing-unlock, etc. (around 11-06).
• Hacker News: Zagitta's original post, 351 points / 83 comments (10-24); this project's Show HN, 2 points (10-28).
• X: @Pirat_Nation post from 10-30, public metrics pulled 11-06.
• Bilibili: BV1d6xN66ECM, views, comments and favorites pulled 11-06; hands-on comments sourced from comment links collected in the README.
• Media: Notebookcheck (10-30), VideoCardz, Wccftech (10-31), Tom's Hardware (11-01), TechPowerUp, Frandroid (11-02), etc.
• Copycats: integrated GUI thread on r/LocalLLaMA (11-03, secondhand, details unverified).