Skip to main content Start reading the article


NVIDIA graphic cards control utility


NVIDIA graphic cards control utility.

Author: Christian Roderfeld


Updated: 2013-11-28

Reguired.NET Framework 2.0

Version BETA
– inspector now always requires admin rights since nvidia decided
to accept all overclocking actions just in an elevated process
enviroment for drivers R325 and above. 🙁

– changed MDPS startup to make use of TaskScheduler instead of shortcut
– changed “Create Startup Shortcut” feature for clock startup to make use
of TaskScheduler too ( rightclick “Create Clocks Shortcut” )
(you have to remove your old startup shortcuts manually)

– added lod bias adjustment for OpenGL
to avoid black edges in some games while using MSAA (R320.14+)
– added OverrideDefault property to CustomSettingNames structure
– added total card power level (normalized) to sensor monitoring (R314+)
– changed MDPS to run always in legacy mode but with enabled “add by gpu process” feature
– fixed overclocking panel was expanded by default
– fixed divide by zero bug for some mobile kepler cards BETA
– added support for overvoltage (GK110)
– added support for temperature target (GK110)
– enabled and improved estimated max boost for GK110
– added CLI parameter “-setIlumination” for logo brightness control (GTX 690, TITAN; SLIBRIDGE)
– added CLI parameters for overvoltage and temperature target
– improved high dpi layout for driver settings
– updated setting constants and names xml for driver R313
– removed dirty workaround for delete profile driver bug, is fixed since R310
– fixed low resolution gui glitch for bitvalue editor
– improved hex input parsing HOTFIX
– possible bugfix for low resolution GUI glitch in setting profiles
– improved max boost detection for kepler cards
– added CLI parameter “-skipMaxBoostTest” to disable max boost detection
– added CLI parameter “-disableScan” for profile settings
– added new profile helper while dragndrop exe file and no profile is found (take care you not just took the launcher)
– removed (DX9) postfix for LOD bias setting, its supported for DX10+ too since driver r310
– clock domains reworked, fixed some 304.xx issues on kepler
– switched shader to gpu clock for monitoring default selection
– updated some setting constants for 302.xx drivers
– fixed wrong bandwidth calculation for GDDR3
– added invalid bios detection
– added some vendorids
– finally fixed trilinear optimization setting 1 = off / 0 = on
– changed prerenderlimit setting for 0 (is now app controlled since 300.xx)
– minor changes in default value handling
– updated some settings constants for 300.xx drivers
– added CLI param “-restartDisplayDriver” (Vista/Win7 only)
– added memory bandwidth calculation to memory buswidth display
– fixed baseclock range out of bounds in some cases
– workaround for strange vcore offset on negative base clock offset
– replaced mem usage display by pci-e interface info on main gui
– added max boost clock estimation
– added “+” sign for offset values
– added small startup delay for MDPS tray start
– fixed restoreAllPStates to work for offsets as well
– added adaptive vsync flag to custom settings (for 300+ drivers)
– added FXAA to custom settings (for 300+ drivers) (Beta)
– fixed highest voltage offset step was not selectable
– added new functions for voltage and clock reading (Beta)
– fixed home profile button do not work as expected on 300.xx drivers
– added current bus usage to monitoring
– added current power consumption level to monitoring and main gui (kepler only)
– fixed current voltage reading for kepler
– added support for base/boost clock reading (kepler)
– added support for base clock offset (kepler)
– added support for memory clock offset (kepler)
– added support for voltage offset (kepler)
– added support for power target (kepler)
– added CLI params for base, memory, voltage offsets and power target
– fixed MDPS for kepler (no need anyway)

NVIDIA Inspector

NVIDIA Inspector

NVIDIA Inspector

1 Comment

# Avatar andressergio,

Guys, I Always you your tool for OC, for me is the most accurate i found as overclocker. Why don’t you put an apply all OC when you have multi GPU, i’m runing QUAD SLI and have to set one by one. I’m pleased to donate .

Thanks a lot

Leave a Reply