Geeks3D's own release post says a year between FurMark versions is likely the first such gap in nearly two decades. The post is dated 2 November 2026, and VideoCardz covered it on 4 November.
What "support" means here
Most of the GPU additions are database entries. FurMark can now identify these chips by name and report them correctly. That is not the same as a new benchmark tuned for each chip, and it doesn't validate anyone's performance claims.
That distinction matters most for RTX Spark. VideoCardz points out that the release notes do not explicitly confirm native Windows on ARM support, even though RTX Spark recognition is now included. Recognition of the hardware does not prove a native ARM64 Windows build exists.
RTX Spark N1X: what was added
The changelog lists support for NVIDIA RTX Spark N1X Blackwell GPUs in 6144-core and 5120-core versions. VideoCardz describes the platform as Grace ARM CPU cores combined with integrated Blackwell graphics and unified LPDDR5X memory. It reports the larger configuration as a 20-core CPU with 6,144 CUDA cores. The smaller one is reported as 18 CPU cores with 5,120 CUDA cores. Those platform specifications come from VideoCardz. I didn't find a separate NVIDIA document to confirm them.
VideoCardz also recalls an earlier report of a Redditor running FurMark on an ASUS ProArt P16 with the 5,120-core chip at a retail store. That run reportedly reached about 123 FPS at 1080p on an earlier FurMark build. It is an anecdote, not a controlled benchmark. It also predates this update, so the new database entry neither caused nor validated that number.
Other GPUs added
The release notes list these additions:
- AMD: Radeon RX 9050 and RX 9050 4G, plus the Radeon AI PRO R9700S and R9600D.
- Intel: Arc Pro B70 and B65.
- NVIDIA GeForce: the RTX 5070 (GB203) and the RTX 5050, 5060, 5070, 5070 Ti and 5080 Laptop GPUs.
- NVIDIA workstation: RTX PRO 6000D, RTX PRO 5000 72GB Blackwell, RTX PRO 4000 Blackwell, RTX PRO 4500 Blackwell and RTX PRO 2000 Blackwell.
- Moore Threads: the MTT S50, S30, S10, S1000, S2000, S4000 and X300.
The notes also add partner-card names, such as the GIGABYTE RTX 5090 INFINITY, SAPPHIRE RX 9070 GRE Pulse, MSI RTX 5090 Lightning Z and PowerColor RX 9070 XT Reva. Separately, FurMark now drops the VRAM size from partner model names.
Changes for Windows users
- Hotspot and memory temperatures: On Windows, the GPU-Z output window now shows GPU core hotspot and memory temperatures. This is a display addition, and the readings come through the bundled GPU-Z component. The bundled components are updated to GPU-Z 2.71 and GPU Shark 2.11.
- Intel Arc usage readings: The notes say GPU usage readings for Intel Arc GPUs are improved on Windows.
- Long-test timer: Elapsed render time now displays in a DAYS HH:MM:SS format. Elapsed and maximum times now use 64-bit variables. This is aimed at long stress-test sessions.
- New command-line options: Windows gains
--allow-screen-saver,--allow-power-monitorand--allow-sleep-mode. The notes name them without explaining their behavior. Check the official command-line documentation before relying on them in automated test scripts. - Interface and visuals: There is a new animated fire background, a 1920×720 resolution option and a demo-controlled anti-aliasing option. Geeks3D's post shows the new background running on a GeForce RTX 5070.
Fixes and platform notes
- Multi-monitor input bug: Geeks3D fixed an OpenGL bug with a fullscreen MSAA window. On systems with several screens connected to the same graphics card, mouse and keyboard input wasn't processed. The notes say single-monitor systems were not affected.
- Linux crash: A crash when reading the current DPI scaling value is fixed. It should now work with Wayland compositors. The Linux folder-opening link now uses
xdg-openinstead ofcaja. - Downloads: Builds are offered for win64 (zip and installer), win32 (zip), Linux x86_64 and Linux arm64. VideoCardz reports the Linux builds need GLIBC 2.36 (x86_64) and 2.41 (ARM64).
- Related editions: Geeks3D's ROG Edition page also lists a 2.11.0.4 ASUS FurMark ROG build.
Practical takeaways
- If you're testing a new RTX Spark laptop, an RX 9050 or an Arc Pro card, update first. Older FurMark builds may identify these GPUs incorrectly or not at all.
- Don't assume the Windows download runs natively on ARM64 hardware. Test it, and treat any result as unofficial until Geeks3D says more.
- Stress tests push GPUs hard. Watch the new hotspot and memory temperature readouts during long runs, especially on thin laptops.
I could not check VideoCardz's wording against every line of Geeks3D's changelog. The details above match the Geeks3D release post where the two overlap.