Downloads:

1,196

Downloads of v 1.20.7.0:

253

Last Update:

05 Jul 2019

Package Maintainer(s):

Software Author(s):

  • jeGX

Tags:

admin gpu freeware stress test performance cpu hardware

Furmark

This is not the latest version of Furmark available.

1.20.7.0 | Updated: 05 Jul 2019

Downloads:

1,196

Downloads of v 1.20.7.0:

253

Maintainer(s):

Software Author(s):

  • jeGX

Furmark 1.20.7.0

This is not the latest version of Furmark available.

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install Furmark, run the following command from the command line or from PowerShell:

>

To upgrade Furmark, run the following command from the command line or from PowerShell:

>

To uninstall Furmark, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade furmark -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade furmark -y --source="'STEP 3 URL'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Ensure furmark installed
  win_chocolatey:
    name: furmark
    state: present
    version: 1.20.7.0
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'furmark' do
  action    :install
  version  '1.20.7.0'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: furmark,
    Version: 1.20.7.0,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller furmark
{
   Name     = 'furmark'
   Ensure   = 'Present'
   Version  = '1.20.7.0'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'furmark':
  provider => 'chocolatey',
  ensure   => '1.20.7.0',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install furmark version="1.20.7.0" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 08 Aug 2019.

Description

FurMark is a very intensive OpenGL benchmark that uses fur rendering algorithms to measure the performance of the graphics card. Fur rendering is especially adapted to overheat the GPU and that's why FurMark is also a perfect stability and stress test tool (also called GPU burner) for the graphics card.

FurMark requires an OpenGL 2.0 compliant graphics card: NVIDIA GeForce 6 (and higher), AMD/ATI Radeon 9600 (and higher), Intel HD Graphics 2000/3000 or a S3 Graphics Chrome 400 series with the latest graphics drivers.

Command line

FurMark has a GUI or Graphical User Interface but also offers command line parameters. With command line parameters you can control more precisely how FurMark is launched and most of all you can launch multiple times FurMark with different paramaters and log all results in a single result file. This feature is useful for graphics cards reviews and graphics drivers tests.
That said, let’s see the parameters.

  • /nogui : does not display the startup GUI.
  • /nomenubar : does not display the menu bar in windowed mode.
  • /noscore : does not display the final score box
  • /fullscreen : starts FurMark in fullscreen mode
  • /width : specifies the screen width – Default: 1280
  • /height : specifies the screen height – Default: 1024
  • /msaa : specifies the MSAA level – Default: 0
  • /run_mode : specifies the run mode: 1 for benchmark, and 2 for stability test – Default: 1
  • /contest_mode : 1 to enable the contest mode or 0 to disable it – Default: 0 – Contest mode allows an online score submission.
  • /max_time : specifies the benchmark max time (run_mode=1) in milliseconds – Default: 60000
  • /max_frames : specifies the benchmark max number of frames (run_mode=1) – Default: -1 (-1 means that max_frames is not used).
  • /app_process_priority : specifies FurMark process priority – Default: 32 (NORMAL_PRIORITY_CLASS) – See Win32 API for possible values.
  • /app_cpu_affinity : specifies FurMark main thread CPU affinity – Default: 1 (first CPU core)
  • /rendering_cpu_affinity: specifies FurMark rendering thread CPU affinity – Default: 2 (second CPU core).
  • /xtreme_burning : sets FurMarks in a mode that overburns the GPU…
  • /log_temperature: writes GPU temperature to file (gpu-temperature.xml). This feature is useful for overclocking. FurMark 1.5.0+
  • /log_score : writes benchmak’s result to file (FurMark-Score.txt). FurMark 1.5.0+
  • /disable_catalyst_warning : disable warning message box when Catalyst 8.8+ is detected. See here and here for more information. FurMark 1.5.0+
@echo off
echo Call Test 1...
call FurMark.exe /width=640 /height=480 /msaa=4 /max_time=60000 
/nogui /nomenubar /noscore /run_mode=1 /log_score 
/disable_catalyst_warning
echo Test 1 complete OK.
echo Call Test 2...
call FurMark.exe /width=1024 /height=768 /msaa=4 /max_time=60000 
/nogui /nomenubar /noscore /run_mode=1 /log_score 
/disable_catalyst_warning
echo Test 2 complete OK.
echo Call Test 3...
call FurMark.exe /width=1280 /height=1024 /msaa=4 /max_time=60000 
/fullscreen /nogui /nomenubar /noscore /run_mode=1 /log_score 
/disable_catalyst_warning
echo Test 3 complete OK.
pause

screenshot


legal\LICENSE.txt
Geeks3D FurMark - GPU stress test and OpenGL benchmark.
Copyright (C) 2007-2019 Geeks3D, All rights reserved.
https://geeks3d.com/furmark/

****************************************************************
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, 
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES 
OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND 
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT 
HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, 
WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING 
FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE 
USE OR OTHER DEALINGS IN THE SOFTWARE.
****************************************************************

Permission is granted to anyone to use this software 
for any purpose, excluding commercial applications, 
and to redistribute it freely, subject to the following 
restrictions:

1. The origin of this software must not be misrepresented; 
   you must not claim that you wrote the original software.

2. This software is a freeware, it cannot be sold or rented.

3. - Websites: you can copy and distribute it freely as long
     as you add a backlink to the source post at Geeks3D.com
     or a backlink to https://geeks3d.com/furmark/
   - CDROM/DVDROM or other kind of BUNDLES (graphics cards, etc.): 
     please contact the author at [email protected]

4. This notice may not be removed or altered from any distribution.



----------------- Geeks3D PRO Pack ---------------------
To use FurMark in a commercial context, visit this page:

http://www.ozone3d.net/g3dpp/

or send an email at [email protected]
legal\VERIFICATION.txt
VERIFICATION

Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

Package can be verified like this:

1. Go to

   x32: https://geeks3d.com/dl/get/606

   to download the installer.

2. You can use one of the following methods to obtain the SHA256 checksum:
   - Use powershell function 'Get-FileHash'
   - Use Chocolatey utility 'checksum.exe'

   checksum32: 04D28D4CA876D4E2CA36EF25502C35B10EB30354A1A097FA08EBC4E0BC79D22A

Using AU:

   Get-RemoteChecksum

File 'license.txt' is obtained from the installation dialog.   
tools\chocolateyInstall.ps1
$ErrorActionPreference = 'Stop'

$toolsDir      = Split-Path $MyInvocation.MyCommand.Definition

$packageArgs = @{
  packageName    = 'furmark'
  fileType       = 'exe'
  file           = gi $toolsDir\*.exe
  silentArgs     = '/VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP-'
  validExitCodes = @(0, 1223)
  softwareName   = 'Geeks3D FurMark *'
}
Install-ChocolateyInstallPackage @packageArgs
rm $toolsDir\*.exe -ea 0

$packageName = $packageArgs.packageName
$installLocation = Get-AppInstallLocation $packageArgs.softwareName
if (!$installLocation)  { Write-Warning "Can't find $packageName install location"; return }
Write-Host "$packageName installed to '$installLocation'"

Register-Application "$installLocation\$packageName.exe"
Write-Host "$packageName registered as $packageName"
tools\Furmark_1.20.7.0_setup.exe
md5: 5AD720579BBF9DF6B13B0C18305ED78C | sha1: B94C07D44CD983C97198228F8D73EDE4E8F8F2EC | sha256: 04D28D4CA876D4E2CA36EF25502C35B10EB30354A1A097FA08EBC4E0BC79D22A | sha512: 8B7CF9FED3000F956B985578185F55FD05C4B5609BCDF8CAA23CC52C2BDB5E570B87EF274D79A7BF37BF2D0F429DDF2EEA3DCFFBE8D5D4DF77B7498B9DEECC23

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
Furmark 1.20.8.0 571 Friday, August 23, 2019 Approved
Furmark 1.20.7.0 253 Friday, July 5, 2019 Approved
Furmark 1.20.6.0 141 Friday, June 7, 2019 Approved
Furmark 1.20.5.0 90 Friday, May 24, 2019 Approved
Discussion for the Furmark Package

Ground Rules:

  • This discussion is only about Furmark and the Furmark package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Furmark, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus