Get the Probe.

How to run it

1. Install

   Run 1401-Probe-Setup.exe. Windows will show a blue “Windows protected your PC” box because the installer isn’t signed yet. Click More info, then Run anyway.

2. Scan from Windows first

   Open 1401 Probe, click Scan this PC from Windows (about 3 minutes), then Start the Windows scan. It only reads. When it says Done, the scan is on your Desktop as 1401-windows-scan-….zip: click Open the upload page and drag it onto the Card Reader.

   Windows can’t see inside the chips, so the USB stick scan below is the one that matters most. Please do both.

3. Make the stick

   Open 1401 Probe and click Make the scanner USB stick.

   • If BitLocker is on, click Pause BitLocker for 3 restarts first. Otherwise Windows will ask for your recovery key later.
   • Plug in the stick, pick it, tick the box, and click Erase and make the stick.

4. Turn Secure Boot off and boot the stick

   In the app, click Restart into BIOS setup. Find Secure Boot (usually under Boot or Security), set it to Disabled, then save and exit.

   As the PC starts, press the boot-menu key and pick the USB stick marked UEFI:

   ASUS	F8	MSI	F11
   Gigabyte	F12	ASRock	F11
   Dell	F12	HP	F9
   Lenovo	F12	Acer	F12

   Choose 1401 Probe - scan this computer. It starts by itself after 5 seconds.

   It asks once about Wi-Fi, Bluetooth and Ethernet. They are included unless you press N within 30 seconds. It loads only your chips’ drivers for about a minute, records each chip’s firmware version and what it can do, switches every radio off the moment it starts, and removes the drivers again. It never goes online, and it never records the networks around you or the devices paired with yours.

5. Let it scan

   It takes about 5 to 20 minutes. The last steps test your graphics card and watch each graphics and audio driver start (NVIDIA cards get NVIDIA’s own driver), and the screen may flicker or go black for up to 10 minutes. That’s normal, so leave it running. Those steps are the ones we need most.

   When it says DONE, the computer turns itself off.

   Stuck? If nothing happens for 15 minutes, hold the power button. Your report is already saved. Boot the stick again and pick the normal scan: it skips the step that froze and finishes the rest. If it freezes again, pick safe scan.

6. Put your settings back

   Turn the PC on, go into BIOS setup (usually Del or F2), set Secure Boot back to Enabled, then save and exit.

   Start Windows, open 1401 Probe and click I already scanned - find my report. It checks Secure Boot and BitLocker for you and offers to turn BitLocker back on.

7. Send us the report

   In 1401 Probe, click Show both files. The stick’s REPORTS folder has two files with the same name, one .zip and one .txt:

   Z790-AORUS_i7-13700K_RTX4070_2026-09-25_a3f1.zip
Z790-AORUS_i7-13700K_RTX4070_2026-09-25_a3f1.txt

   Drag both onto the 1402 Card Reader on the front page and click Send. Keep the report ID it prints.

Is it safe?

Want to check the download? In PowerShell: Get-FileHash .\1401-Probe-Setup.exe should print the SHA-256 above.

No Windows PC?

The stick image on its own. Unzip it and write 1401-probe.img to a USB stick with balenaEtcher, or Rufus in DD mode. Then follow steps 3–6 (turn Secure Boot back on in your BIOS yourself).

SHA-256 35edfb7500a86a6a7052454ce64be5a0b9b94731f1390073847c23232187eb15

On Linux? 1401-probe-linux.py makes the stick for you: run python3 1401-probe-linux.py. It checks the image, lists USB sticks only, asks you to confirm, writes and verifies the stick. After the scan, python3 1401-probe-linux.py --report copies your report off the stick.

On a Mac? 1401-probe-mac.sh does the same from macOS: run bash 1401-probe-mac.sh (it lists external USB sticks only, never your Mac's disk), then bash 1401-probe-mac.sh --report after the scan.

Scan the Mac itself (a real Mac or a Nullintosh): bash 1401-probe-mac.sh --scan. No password, about a minute. It records the processor, graphics, displays, Wi-Fi, Bluetooth, sound, USB, storage, battery and the drivers macOS loaded, leaves out serials, addresses, network names, paired devices and names, and puts one .zip on your Desktop to send us.

Free software, GPL-3.0 · Source code

Version history

Every version stays up, byte for byte, with its SHA-256, here and on GitHub. Use the newest one unless we asked you not to.

2.2.0 · 2026-10-13 · current

The whole machine, from every side: the stick, Windows, and macOS.

• New: scan from Windows. The app scans the PC from Windows in about 3 minutes: processor, graphics, displays, firmware tables, Wi-Fi, Bluetooth, network, sound, battery and every device with its IDs and driver.
• New: scan a Mac. bash 1401-probe-mac.sh --scan scans a Mac or Nullintosh.
• Wi-Fi and Bluetooth chips in depth: each chip's firmware version, what it can do, and the Bluetooth controller's version and features. Now included by default; press N at the question to skip.
• Processors: the chip's family name (Tiger Lake, Vermeer, Granite Ridge...), power and turbo limits, frequency and sleep-state tables, and the timer speed measured.
• Intel integrated graphics: what Linux's driver reports about the GPU and a snapshot of its display registers, the state a macOS driver for it has to reproduce.
• Older NVIDIA cards (Kepler: GTX 600/700, Quadro K, Tesla K): NVIDIA's own 470 driver is back on the stick, so these cards get the same driver trace as newer ones.
• The Mac and Linux tools are now on the GitHub release (the links above were broken).

The downloads at the top of this page.

2.1.0 · 2026-10-11

Every graphics card and integrated GPU now counts, old and new, whatever the brand. This is how NullMoth learns the GPUs macOS has never supported: Intel Iris Xe and Arc, Radeon RX 7000 and 9000, Ryzen AI, and older cards too.

• New last step: a GPU test. Linux's own graphics drivers run a short compute test and an off-screen drawing test on each GPU and check every result. Nothing is shown on the screen. The report gets what each driver told the GPU to do, which is what a macOS driver for that GPU has to do the same way.
• Every GPU is scanned and traced, not only the NVIDIA, AMD and Intel ones already supported.
• Same safety: drives stay read-only, nothing leaves the computer, and a hung test turns the PC off and is skipped next time. The stick is about 80 MB larger.

1401-Probe-Setup.exe · 500.6 MB · SHA-256 4a323cda564e382c22a7536183611b7294e9ffc14bf0b36bd6fe1d373929d87f

1401-probe-img.zip · 500.5 MB · SHA-256 a68b2ff4943d72fc3de2432af21195b66b8a78402526aeafca7dbbe7ac7d041b

SHA256SUMS.txt · on GitHub

2.0.2 · 2026-10-09

For laptops that froze in the last step. If 2.0.1 froze on your PC, make the stick again with 2.0.2.

• No more freezes in the last step. Every driver test there now runs under the automatic power-off the graphics test already had: if one hangs, the PC turns itself off and the next start skips it. The HDMI audio of an NVIDIA card that is not driving the screen is no longer tested; it hung RTX 4050 laptops.
• A freeze while listing PCI devices no longer loses the graphics card. Before, every later scan skipped all of PCI and the report had no GPU in it.

1401-Probe-Setup.exe · 426.8 MB · SHA-256 88999308fc5213e923d9e5c9c6c1843e0cfb752284c70fca92c55af0f03b3034

1401-probe-img.zip · 427.4 MB · SHA-256 f3af812b123f3ea3bebfc867ccbff96378b77cb578db5d4bd4e6e33de4e93b4c

SHA256SUMS.txt · on GitHub

2.0.1 · 2026-10-09

Fixes the errors some of you saw on 2.0.0.

• Driver trace errors fixed. 2.0.0 printed “Bad file descriptor” / “write to closed file” in the last step and stalled about a minute per device. The trace reader now stops cleanly.
• NVIDIA’s own driver now actually loads in the trace (2.0.0 could not take the card from nouveau while it drove the screen).
• Instructions everywhere match the scan, and 1401-probe-linux.py makes the stick from Linux.

1401-Probe-Setup.exe · 426.7 MB · SHA-256 eaf420397d432195571c2b9fcf90a73712a5908156f573a18ba4fa01dbdc402d

1401-probe-img.zip · 427.4 MB · SHA-256 dd054d8c40f34ad97efb1594cea4bc3fed1e8b2f8660236bb3c3ba73d9b6a468

SHA256SUMS.txt · on GitHub

2.0.0 · 2026-10-08

The probe now maps the whole machine, down to how each driver talks to its hardware, so the installer can build the right setup for your exact PC.

• Full system map. Which GPU drives each screen and the laptop panel, switchable-graphics hints, GPU features (architecture, CUDA level, RT and tensor cores), PCIe slots, memory modules (no serials), storage ports and modes, fans and sensors, USB roles, touchpad and keyboard bus, CPU core layout and the firmware memory map.
• Build report. The stick also writes a Report.json in the format the EFI builder reads.
• Driver trace. At the end, each graphics and audio driver is restarted while the kernel records every register read and write it makes. NVIDIA cards get NVIDIA’s own driver for their generation (610 for Turing and newer, 580 for Maxwell/Pascal/Volta; Kepler and older use nouveau for now). The screen may go black for a few minutes.
• Wi-Fi, Bluetooth and Ethernet: your choice. The stick asks at the start (default no). Press Y and it loads only your own chips’ drivers, records them starting, switches each radio off and removes them again.
• Traces are redacted like the rest of the report and capped at 40 MB.

1401-Probe-Setup.exe · 426.7 MB · SHA-256 655f616cfe439ebc24c4939193dc9374a19944cea2744d28dfabe9628e4e8ba0

1401-probe-img.zip · 427.4 MB · SHA-256 5fa27706e95f03da47851be9c4f00fb368ca9c36eee2de73b8ae94ad291fa59d

SHA256SUMS.txt · on GitHub

1.0.1 · 2026-09-26

Fixes from the first round of test reports. Thanks to everyone who ran 1.0.0.

• A freeze no longer loses the rest of the scan. Before it touches a piece of hardware, the probe writes the name of that step to the stick. If the PC locks up, start the stick again: it skips the one step that froze and finishes everything else, and the report says what it skipped.
• The PCI scan runs one device at a time, so a freeze points at one device instead of taking the whole stage with it. Every device’s IDs are saved first.
• Laptop graphics BIOS. Laptops with a second GPU often leave the card’s memory decoding off, so 1.0.0 couldn’t read its VBIOS or chip ID. The probe now turns decoding on for that one read and puts it back right after.
• Graphics driver data is read once per GPU instead of three times, and every file the driver didn’t give us is recorded with the reason.
• Reports are sealed. Each report has a seal.json with the SHA-256 of every file and a keyed check over that list, so we can tell a report straight off the stick from one changed afterwards. Nothing is sent anywhere and nothing in the report changes.

1401-Probe-Setup.exe · 181.5 MB · SHA-256 99e9be8c84f20df90db314a912bd9abd20cc91da333288c28492396cc0c605d8

1401-probe-img.zip · 181.0 MB · SHA-256 2ec5fa8262ecc3361987e89b4528789f6fcd7973d1250ff493f9bbdd1f656f19

SHA256SUMS.txt · on GitHub

1.0.0 · 2026-09-25

First public release.

1401-Probe-Setup.exe · 181.5 MB · SHA-256 bd9450093f3c78d0ac6d8183d5a75781937102c877f05d2f912774907b900c26

1401-probe-img.zip · 180.9 MB · SHA-256 98477679a8a6ba4d14b7b10ee7af58fde35d48f0f1c47dae514c3187e6c53d2a

SHA256SUMS.txt · on GitHub