Tuesday, September 19th 2023

FurMark 2.0 Launching This Month

The Geeks3D team has been working quietly on a new version of FurMark, a highly popular benchmarking application as used by many in the enthusiast overclocking community. The GPU stress test and benchmarking tool is set to receive its first major upgrade (public release) since 2007, although a beta version has been made available to download since December 2022—accessible via the Geeks3D Discord group. A late August update had the beta reaching a new milestone in version 2.0.10—fixing various bugs, expanding GPU support and adding more resolution options.

The new version of FurMark supports OpenGL or Vulkan graphics APIs, and its three preset benchmark options include 1080p, 1440p, and 2160p resolutions. Users can also customize parameters for different graphical and resolution settings. A results database is already active, but Tom's Hardware notes that it consists of data submitted by beta users, thus it does not log: "results from the previous version of the app." The development team has teased a loose later this month launch window for FurMark 2.0 in public form.
Version 2.0.10 features and bug fixes include:
  • Fixed Radeon RX 6850M XT name (XT was missing)
  • Added support for AMD Radeon PRO W7900, PRO W7800, PRO W7600 and PRO W7500
  • Added support for AMD Radeon RX 7900 GRE
  • Added support for NVIDIA GeForce RTX 4060 Ti 16 GB
  • Added support for Intel Arc A570M, Arc A530M, Arc Pro A60M and A30M
  • (Windows) updated with GPU Shark 2 2.0.12
  • Updated with GeeXLab 0.53.0 libs
Sources: Techspot, Geeks 3D FurMark V2, Tom's Hardware
Add your own comment

7 Comments on FurMark 2.0 Launching This Month

#2
N/A
It is not detected. A lower power state is forced by perfcap reason pwr limit.
Posted on Reply
#4
AnotherReader
N/AIt is not detected. A lower power state is forced by perfcap reason pwr limit.
If the reason was the pwr limit, then why is gaming power draw higher than Furmark? I'm not saying it's a bad thing; Furmark is nigh useless.
Posted on Reply
#5
R-T-B
N/AIt is not detected. A lower power state is forced by perfcap reason pwr limit.
Pretty much the same thing though. A heavy power load is detected, it ends in a throttle. Potato potato. Sure it's not detecting it's signature or anything but that doesn't change the fact that it's a pretty useless utility.
Posted on Reply
#7
chrcoluk
2.0 of the GPU destroyer? why use this tool?
Posted on Reply
May 21st, 2024 12:01 EDT change timezone

New Forum Posts

Popular Reviews

Controversial News Posts