FurMark 1.21.0 Released (Updated: 1.21.2.0)


FurMark 1.21, stress test session

 
A new version of FurMark, the popular GPU burn-in utility, is available.

1 – Release highlights

FurMark 1.21.0

FurMark 1.21 adds the support of AMD Navi GPUs (Radeon RX 5700, RX 5600 and RX 5500) with the monitoring of essential sensors (core usage, core temperature, power consumption, fan speed). The log file is now stored in user’s temporary folder (usually C:\Users\USERNAME\AppData\Local\Temp\). The benchmark scores are now submitted to a new online database available HERE. The old database at ozone3d.net will still accept submissions during the next months from previous versions of FurMark, but will be put in read only mode later this year. GPU Shark and GPU-Z have been updated to their latest versions.

 

FurMark 1.21.1

FurMark 1.21.1 is a maintenance release that fixes and updates the support of GPU-Z: the VDDC sensor has been replaced by GPU Voltage and power consumption sensors (in Watts) have been added.

FurMark 1.21.1 + GPU-Z info + Radeon RX 5700

 

FurMark 1.21.2

FurMark 1.21.2 is a maintenance release that updates the support of GPU-Z with the display of the Board Power Draw sensor.

FurMark 1.21.2 + GPU-Z info + GeForce RTX 2070

 

2 – Download



You can download FurMark from the following link:

FurMark 1.21.2.0 (win32 installer)

To ensure the integrity of your download, you can verify the following checksum values / hashcodes (a tool like H4shG3n can help you):
 
FurMark_1.21.2.0_Setup.exe hash codes:
- file size => 12192665 bytes
- MD5       => 52f8d487522614dddb262268f68fb31e
- SHA1      => 0bad14bacfa5d63b3033766f7c2eb6786764489a
- SHA256    => 593bcb8c4bbd772a247704ab5e82b4bb04c039f8014a7b5b04e1e48bf498d751

Previous versions:

 
Useful links:


FurMark logo - GPU stress test

3 – Changelog

Version 1.21.2.0 - 2020-06-03
+ added the display of GPU-Z Board Power Draw in Watts.
! minor bugfixes in the submit score process.
! updated: GPU-Z 2.32
! updated: GPU Shark 0.17.1.0
! updated: ZoomGPU 1.26.1 (GPU monitoring library)


Version 1.21.1.0 - 2020-03-23
+ added the display of GPU-Z Power Consumption and 
  Chip Power Draw (AMD) in Watts.
! updated GPU-Z sensor name: "VDDC" -> "GPU Voltage".
! updated: GPU-Z 2.30
! Log file back in FurMark's folder.


Version 1.21.0.0 - 2020-01-23
+ added support of AMD Navi GPUs.
+ added support of AMD Radeon RX 5500 XT and RX 5600 XT.
+ added support of GeForce RTX 2060 with TU104 GPU and
  GeForce GTX 1650 SUPER.
+ updated reporting of graphics drivers for Radeon graphics cards.
+ new online database.
! Log file is now stored in user's temp folder.
! updated: GPU Shark 0.16.1.0
! updated: GPU-Z 2.29
! updated: ZoomGPU 1.25.1 (GPU monitoring library)


FurMark with all GPU tools





15 thoughts on “FurMark 1.21.0 Released (Updated: 1.21.2.0)”

  1. JeGX Post Author

    Yes it’s a false positive. Probably caused by the installer (inno setup). I’m trying another installer…

    1. JeGX Post Author

      Just tested on a RTX 2070, res: 1024×768, windowed mode.
      – no postfx: 253 FPS
      – postfx: 250 FPS
      small drop in perfs which is normal.
      What is your GPU / driver ?

  2. Neo

    I have a RTX-5000 mobile , when doing GPU stress test I pressed the space key and the donuts was gone, I noticed the core frequency VDDC raised and the fps increased significantly to around 2500. I wonder is this the normal test mode or not? ( the machine screamed loudly).

    1. JeGX Post Author

      Yes the SPACE key allows to render or not the donut. When the donut is not rendered, the scene is simpler and core clock speed is set to the max by NV driver. I added this long time ago to test the performance of the VGA cooler if I’m not wrong…

  3. saltinbank

    JegX tu confirmes que les drivers nivida passe dans un autre power mode j’ai ma rtx 2060 qui bloque à 80W au lieu de 90 est elle ralentit à 1ghz au lieu de 1750/1850 mhz ?

    trop bizarre ducoup temp stagne à 53C et ça fait du yoyo entre 700 mhz et 1ghz max 🙁
    j’arrive pas à la stresser :'(

    1. JeGX Post Author

      Oui les drivers nv diminuent la frequence du core et limitent surement d’autres parametres quand furmark fonctionne. As-tu essayé de pousser la power target à fond? Genre +120%TDP ?

  4. Andy_wang

    Hi, I am using furmark to stress test my workstation.
    How should I set the resolution? I have a 4K(3840*2160) screen.

    I had ran it under different resolution, well, with certain resolution (1K, 2K) I could hear louder sharp noise, coil whine maybe.
    But, in extreme low resolution(lower than 1K ) or high resolution(4K or larger), the noise disappears. Interesting!
    Wish someone knows why.

Leave a Reply to Neo Cancel Reply

Your email address will not be published. Required fields are marked *