It’s time for a new version of FurMark. With this very cold winter we currently have, only FurMark can bring you the heat you need! Here are the main changes of this new release:
- A monitoring graph for GPU temperature is now available in Stability Test mode. This graph allows you to see the GPU temperature evolution for the last 16 minutes (1000 seconds to be exact). The graph displays the minimum, maximum and current temperatures.
- The use of an OpenGL 3.0 rendering context. Currently, only NVIDIA provides an OpenGL 3.0 driver and all videocards from GeForce 8 to the latest GeForce GTX 2xx support this new version of OpenGL. I didn’t add new OpenGL 3.0 functionnalities in FurMark rendering code. The OpenGL 3.0 rendering path uses the same functions than OpenGL 2.1 rendering path. So why an OpenGL 3.0 rendering context? Just to see if it works in the real world, if it improves performance, if it has not compatibility problem. In a word, it’s more a test than a killer-feature! Of course, if the graphics system does not support OpenGL 3.0, the OpenGL 2.1 path is used. If you have an OpenGL 3.0 capable graphics card, you can test the difference between both rendering context using the /no_gl3_ctx parameter in command line. This parameter forces the use of an OpenGL 2.1 context.
- Post-Processing Pass. I added a checkbox that allows the user to enable or disable the post-processing pass (default: disabled). The post-processing pass adds an additional processing to the final image and allows to increase GPU workload in the pixels processing. Furthermore, the post-processing effect is now fully programmable. You can then code you own post-processing effect. The post-processing effect is available in the post-processing-fx.xml file in FurMark’s folder. I will publish shortly a complete programming tutorial about this new feature but now, if you have some knowledge of GLSL (the OpenGL shading language), you can tweak this effect file. Do not hesitate to send me feedbacks if you code a cool effect. I will post it as well as your credits!
- you can use optimized profiles for Enemy Territory: Quake Wars and available in NVIDIA and ATI graphics drivers. These profiles enable SLI and Crossfire.
- you bypass the FurMark detection included in the Catalyst graphics driver (see here and here).
- 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.
- ForceWare 181.00 and OpenGL 3.0
- Know FurMark’s Command Line Parameters
- The First Review of 55nm GeForce GTX 260 With FurMark
- InfraRed Photo Shows which Part of Your HD 4870 is Hot While Running FurMark
- One of the most active forums about FurMark @ techPowerUp!
- thanks to Levent for the turkish translation
- thanks to Nuke for the russian translation
- thanks to David Legrand, Stefan and shadow for their beta-tests.
Remark: in FurMark’s folder you will find two executables: FurMark.exe and etqw.exe. etqw.exe is just a copy/paste of FurMark renamed in etqw. Why etqw? Just because it’s one of the most popular OpenGL applications. Using etqw.exe offers two advantages:
I think most of the important things about this new release have been said. If you have feedbacks, please them hereunder in the comments (recommended) or use this forum.
You can download FurMark 1.6.0 here:
FurMark 1.6.0 ChangeLog:
Last thing. Using FurMark can be dangerous for your graphics cards (I shouldn’t say it if I want to spread FurMark). Here is a funny but serious extract from thermalright.com (thanks Stefan for the link!):
“In our lab tests we have discovered that when running Furmark to test for temperature, it tends to show results that would never be achieved in any circumstances (under normal running or overclocking). Running Furmark is highly risky therefore we do not recommend running this program for tests. This program pushes the VGA card to the point of maxing out, beyond limit and will burn out any cooler, stock or after market coolers after long period of testing. Even running games such as Far Cry 2 and GTA 4 extensively for long hours, the temperatures would never reach what Furmark’s excruciating tests put out.
Furthermore, it is crucial to have a 12cm fan installed running at 1600 RPM. This will ensure enough airflow to not only the HR-03 GTX heatsink body but also to the VRM heatsink plate. If you would like to run software to test for heatsink’s
temperature stability, we strongly recommend ATI Tools.
That would be funny one day to see graphics cards with this certification:
FurMark related links:
15 thoughts on “FurMark 1.6.0 Available NOW!”
Pingback: FurMark 1.6.0 Available Now - Expreview.com
Pingback: [TCM]FurMark 1.6.0 is up for grabs - Overclock.net - Overclocking.net
The minimun isn’t updating during the test.
I have a m9600gt.
The fist temperature is 68°C, when the fan is running, the temperature discreases to 66°C and the minimun isn’t 66 but always 68.
Sorry for my bad english
Okay, I will update the minimum temperature in the next version. I didn’t think this situation could occur 😀
Your english is totally understandable, mine is not better.
During the stabilitity test with my Sapphire 4870 512mb (stock)
my system just shut down.
any idea’s ??
4gb corsair 4-4-4-12
black power 500watt psu
Antec twelve hundred
Hello everyone, I have tested with FURMARK on a computer with a GTX280 and QUADCORE INTEL PROCESSOR works amazingly well, only opened to correct the issue of minimum temperature … long live FURMARK… nostop 😉
Sorry for my bad English too
Pingback: ASUS GeForce GTX 295 Temperature With FurMark | The Geeks Of 3D
New build :
I7 920 (2.67 ghz) stodk speed
Gigabyte X58 DS4 mobo
3 Ghz ddr3 tri-channel, 1333
2 – 1TB Barracuda HD (raid 0)
Asus 4850 x2
1680 x 1050 = 4306 o3Marks
Avg fps = 144
Max temp 73 degrees on first card (hottest)
HAHAHAH! It drew so much current from my outside UPS power supply the alarms were going off. Still cool (not overheated) GPU’s tho.
Neat tester. Can’t wait to start overclocking.
* stock speed
* 3 GB mem
I’m a goob. lol
CRYSIS running for 2 hours heats it up pretty good.
(Win XP SP3)
I tested one thing, for fun first, then for actual testing.
I own a Sapphire Radeon HD 4850, one of their reference card – with a tweaked BIOS (I set the fan to start sooner and to spin higher at a given temperature).
One thing is, I mainly run under Linux; since the OpenGL stack provided by Ati/AMD is the same under Windows and Linux, and Wine maps WGL to GLX directly, performance impact on Windows OpenGL programs running under Linux/Wine is close to null; I ran FurMark on my setup.
Well, it works; I get very comparable results under both Windows and Wine with FurMark, framerate- and temperature-wise (you can use aticonfig –odgt to get temperature readings on recent Ati hardware) as long as I set the driver to not switch on v-sync by default. Thus, my following questions:
– could a native Linux version of FurMark be done? While Wine doesn’t show any slowdown in my case, there could still be some.
– is it possible to add a “disable v-sync” OpenGL call?
Im strongly not recommended to use this app for stress test on GPU, its killed my HD4870 x2 (original setting) after 3mins of testing. So be careful guys!!
Pingback: Cooler Master’s PSU Used To Start a Car! | The Geeks Of 3D
Pingback: Thermalright Does Not Like FurMark… | The Geeks Of 3D
Pingback: Normality of SLI - Page 5 - Overclock.net - Overclocking.net
Pingback: FurMark 1.7.0: The Bad Boy of Graphics Cards Utilities is Back! | The Geeks Of 3D - 3D Tech News
Comments are closed.