May 12th, 2012· Update: updated gpu monitoring code with memory usage (when available)
· Update: GPU-Z 0.6.2 and GPU Shark 0.6.3
· Update: ZoomGPU 1.8.3 (GPU monitoring library) with support of latest GTX 690 and GTX 670
· Bugfix: in gpu monitoring, max value of GTX 600 power was not saved
· Bugfix: minor bugs fixed in score submission
· Bugfix: gpu monitoring thread was not stopped when FurMark initialization failed
· Bugfix: gpu monitoring xml report was not well-formed (closing tag missing)
April 20th, 2012· New: added list of detected GPUs in the main interface.
· New: stress test options are now in the settings box.
· New: support of NVIDIA GeForce GTX 680 (clock speeds and power monitoring).
· New: support of latest AMD Radeon (HD 7900, HD 7800 and HD 7700) cards.
· New: added resolutions 4096×1152 and 6144×1152 for 2048×1152 monitors.
· New: display of the true clock of the GPU when available (NVIDIA only).
· Update: GPU monitoring moved in a separate system thread.
· Update: GPU data monitoring report updated (Log GPU data in Settings box).
· Update: minor changes in the way GPU monitoring information is displayed.
· Update: ZoomGPU 1.8.2 (GPU monitoring library).
· Update: GPU-Z 0.6.0 and GPU Shark 0.6.1
December 21st, 2011· New: support of latest NVIDIA GeForce and AMD Radeon cards (ZoomGPU 1.6.1).
· New: added new benchmark: the burn-in benchmark (1920×1080 only, duration:15 min). Goal: best score with the lowest GPU temperature.
· New: user can now submit a score with a login.
· Update: GPU-Z 0.5.6 and GPU Shark 0.5.4
· Change: removed the /gtx500ocp checkbox.
· Bugfix: fixed a deadlock that hung FurMark sometimes at the end the tests.
July 4th, 2011· Maintenance release.
· Improved score submission.
· Updated the number of window resolutions available.
· Change: updated with the latest version of ZoomGPU (support of recent NVIDIA GeForce and AMD Radeon graphics cards).
· Bugfix: spikes in temperature graphs are now filtered. See here for more information: FurMark and Spikes in Temperature Monitoring Graphs.
· Change: minimizing window is no longer possible in windowed benchmark mode.
· Removed the FurMark 1.7.0 mode.
February 25th, 2011· New: support of all latest GeForce GTX 500 and Radeon HD 6000 Series…
· New: added /gtx500ocp checkbox for GPU-Z to disable GTX 500 OCP (over current protection).
· New: GPU-Z 0.5.1 and GPU Shark 0.4.1 are now embedded in FurMark.
· New: added programmble GPU temperature alarm. When GPU temperature exceeds a threshold, an alarm sound is played.
· New: added warming-up step to benchmarking.
· New: improved OSD (on-screen display data) readability (key V).
· New: added GPU monitoring in 3D window.
· New: added GPU-Z full GPU power consumption data (power, voltage and current) if available.
· New: caution message displayed before every burn-in test.
· New: score submission is now limited to two presets: Preset:1080 and Preset:720.
· New: increased graphics workload.
· New: added animated background image option based on iq’s code.
· New: added animated camera option with multiple furry torus.
· New: two burn-in modes are now available: normal burn-in mode and Xtreme burn-in mode
· Bugfix: spikes in temperature graphs are now filtered.
· Bugfix: many minor bugs
April 20th, 2010· New: different scoring web pages for version 1.7.0 and 1.8.2+.
· New: option to enable FurMark 1.7.0 compatibility mode.
· New: support of latest Radeon HD 5000 and GeForce GTX 400 series.
· New: display of GPU and memory clocks (even if GPU-Z is not started).
· Change: improved temperature graphs readability.
February 4th, 2010· New: now all options are available in benchmarking mode: Xtrem Burning (XB), postfx (FX) and displacement mapping (DM).
· New: added new effet (displacement mapping) on the fur rendering.
· New: GUI translation is done with XML files in the localization folder.
· New: added hotkeys: P to enable/disable post fx rendering, T to enable/disable temperature graphs rendering.
· New: gpu temperature is now exported in xml and csv formats.
· New: twitter submission displays a login dialog box to tweet your score.
· Change: the fur rendering workload has been increased to produce more heat.
· Change: improved temperature graphs readability.
· Change: updated with the latest version of ZoomGPU for graphics hardware detection.
January 7th, 2009· New: added a GPU temperature monitoring graph in stability test mode.
· New: added a checkbox to enable post-processing effect in stability test mode. Post-processing effect shader is loaded from the file post-processing-fx.xml. So if you know GLSL programming, you can customize this effect shader. See on Geeks3D.com for a complete tutorial.
· New: added OpenGL 3.0 support. If OpenGL 3.0 is detected, the rendering is done via an OpenGL 3.0 context.
· New: added new interface translations. See FurMark Interface Translations @ oZone3D.Net Forums
· for more details.
· New: added start and end GPU temperatures logging in benchmark mode.
· Change: little interface reorganization to better handle translations with long text blocks.
November 24th, 2008· New: added GPU temperature log facility. If enabled, a log file (gpu-temperature.xml) is generated (in Stability Test mode only) to log degrees celcius and fahrenheit as well as elapsed time.
· New: benchmark results can be logged in a file (FurMark-Scores.txt). This feature is useful in command line when starting multiple tests. See Run-Multiple-Tests.bat for an example.
· New: added a postprocessing pass in Stability Test mode to make the test more intensive.
· New: in benchmarking mode, score is returned to Windows. Useful for command line scripts.
· New: startup dialog box is available in several languages. If you want to translate FurMark, feel free to send the translated xml file (see gui-english.xml in FurMark folder for an example). Of course, your credits will be added on FurMark's homepage). Current translations: english, french, chinese (traditional and simplified) and german.
· New: added key F9 to make a screenshot (windowed or fullscreen but in Stability Mode only).
· New: added checkbox for Xtreme Burning Mode.
· Change: Xtreme Burning mode is more gpu-intensive...
· Bugfix: improved OpenGL rendering context to support new ForceWare 180.xx series.
· Bugfix: the QXSGA 2560x2048 resolution was not operational.
June 26th, 2008· New: added full QXSGA mode: 2560x2048.
· New: added an extreme burning mode for stability test. This mode available in command line: /xtreme_burning Launch FurMark-Xtreme-Burning.bat.
· New: added command line parameters (see the start-Benchmark-Standard-Mode.bat file for parameters list). Now you can control FurMark's resolution, msaa level, CPU affinity, etc., using command line. This new feature has been added to allow FurMark to be used with OCCT
· Change: time in score dialog box is now in milliseconds.
· Change: improved driver detection.
· Known issue: under Vista with ForceWare graphics drivers (tested with 169.28 and 175.16), if the desktop resolution is equal to benchmark selected resolution, the swith back from fullscreen mode to windowed mode (at the end of the benchmark) fails and the user can't see the score dialog box. This issue has not been observed with Catalyst or S3 graphics drivers
Find us on Google+
