VBIOS Flashing and Safety Procedures:Always make a VBIOS backup, before start messing with your VBIOS!!
You can do this with GPU-Z: http://www.techpowerup.com/downloads/SysInfo/GPU-Z/
or with Nvidia Flash Tool[under windows]: http://www.techpowerup.com/downloads/2133/NVFlash_5.118_for_Windows.html
command line to take a VBIOS backup:
nvflash.exe -b org.rom [ENTER]
command line to flash your modified VBIOS from cmd:
nvflash.exe -4 -5 -6 mod.rom [ENTER]
Where:
org.rom is the name of your original VBIOS
mod.rom is the name of your modified VBIOS, you can replace it if needs with your name,
but file extension must end to .rom [etc: another example: mybios.rom or similar]
Before start flashing your VBIOS:
* Close all applications that are currently running and can be closed!
* Close especially any Antivirus Scanners and any other resident scanners!
Those steps are need to prevent and avoid VBIOS update interruption.
DO NOT TURN OFF OR REBOOT MACHINE DURING THE FLASH PROCESS!!!!!
A bad flash will probably turn your VGA into an unusable state.
When something goes wrong during the VBIOS update like:
Lost electric power, PC crash or reboot
That will stop your machine from booting!
IF this happened you have to perform a VBIOS recovery.Miscellaneous:Q.: How do i turn off the robot voice mentor? [as i don't want such]
A.: You can mute the Tuner once is running from your mixer. The changes will be remembered for next Tool's usage.
F.A.Q:Q.: I can't start the Tool, i've received followed error on start attempt. How i can fix it?
A.: As mention in the error message itself, you need to log-in in your Windows with account who has administrative rights.
Once done, the error will no longer occur.
Q.: How can i check my VBIOS properties before change them?
Q.: I've maded the desired changes and customised my VBIOS with the Tuner,
but how can i verify that's done properly?
Q.: How i can check that my VBIOS is healthy before modification?
Q.: How i can check that my VBIOS is healthy after modification?
A.: You can click on "VBIOS-Z Report" to check and verify current VBIOS parameters.
It will shows current states based on your current modifications [or if you haven't modified anything yet, will shows VBIOS original parameters],
along with healthy status.[
OK/
Not OK]
Examples:
Loading original VBIOS file:
and executing scan report 1st:
VBIOS-Z Report engaged:
closing the report and proceed with VBIOS modification, for example let's modify GPU core freq.,
by clicking on Core Tune.
Core Tune engaged:
[Let's say we want to set 900MHz core speed.]
All is done very simple, very quick and very easy. Everything is done automatically.
All you need is to enter desired new core speed, the Tuner will do the rest with all necessary changes.
Closing this thread and executing VBIOS-Z Report again after our modifications:
And we check that our desired new core speed is now applied,
and that all others related parameters changed respective.
We also see that the BIOS is healthy as expected and now we can save and flash our modified VBIOS.
[If you want to modify more stuffs, just go to main screen and adjust others desired parameters, when its done you can save your VBIOS]
Example if something is wrong with VBIOS image, [i've damaged the vbios image with sense then scan it with the tuner]
scan engine will report it and you can read it along will turn to red background:
If you receive such red background color[you also can read the VBIOS is corrupted] by any chance,
you shall not flash your VBIOS with this image.
Q.: I just want to check VBIOS-Z report, without to do any modification over the VBIOS image. Is this possible?
A.: Yes, when you click on "Save & Exit" button you will be asked if you want to save VBIOS changes to your image or not.
If you answer will "No", original scanned VBIOS image with regardless modified or not will be keep intact as is.
[Etc: Even with changes done over it, they will be ignored and they will be not written to the VBIOS image]:
If you want to save your changes, then you should answer with "Yes", then will receive an final message:
Q.: I've modified my VBIOS Image, but i noted that after the modification my VBIOS Image size is now changed.
Is this a normal?
Should i concern about anything?
I've re-scanned my modified VBIOS image with changed size with Tuner's "VBIOS-Z Report" and its still shows a green light.
Can i proceed and flash it?
Why this happened and why the size its changed after the modification?
A.: Yes, its a normal and there is nothing to worry about. As long its shows green light its OK to proceed with VBIOS flash.
This VBIOS size change can occur in some cases[not all] when VBIOS image is saved by GPU-Z.
Tuner will auto detect if there is a padding issue while scanning the VBIOS image and will auto correct it,
and will save modified VBIOS image with new geometry based on his original expected size.
Q.: Is there a Digital Signature that the Tuner uses?
A.: Yes, the Tuner uses a Digital Signature
Q.: Is it necessary to run VBIOS-Z report either when i load my BIOS or after i made a modification over it?
A.: Nope, its optional, but its recommended to execute the report to check your VBIOS parameters after the modifications[before 'Save & Exit'] and also to ensure that your VBIOS is healthy.
Q.: When i start some of Tuner's threads the main interface is halted. Is this a normal?
A.: Yes, its a normal. Its require to prevent parallel workers to run at the same time.
Etc: when some of the workers is engaged, all others cannot be started until the worker which is currently in progress is finished.
Q.: I've started a thread to make an VBIOS modification, but i clicked the wrong thread.
Can i exit from this thread without made any modifications?
A.: Yes, you can. When user input is requested, answer with "Q" or "q" and press ENTER.
This will abort current operation.
Example:
Q.: How can i check the parameter before i change it without executing VBIOS-Z report?
A.: Just go directly to what you want to modify, the co-respond thread will detect and show you current detected value before asking to enter your newest desired value(s)
Q.: Is there any shortcuts that can be used from the main interface?
A.: Yes, they are as follows:
"R" ==> VBIOS-Z Report
"C" ==> Core Tune
"M" ==> Memory Tune
"F" ==> FAN Tune
"V" ==> Voltage Tune
"A" ==> Max Voltage Limit
"P" ==> Power Control
"X" ==> Save & Exit
Q.: Seems i hit my GPU core OC limit for my mobile video card. Can you do something more?
A.: You can try Alternative asynchronized GPU clock booster instead, when you hit the wall/limit of GPU core OC.
This can help you to fine tune your GPU freq. and to drain the maximum potential from it.
[Pickup Mode 2 when asked, when you execute GPU core adjust for your mobile GPU]
More details about newest feature added:
The newest alternative GPU clock booster is only available for Mobility Series.
It can help you to fine tune your GPU clocks and to reach the maximum OC potencial of your GPU.
The newest mode is known as Mode 2 [Asynchronized], and will appear when you go for GPU core adjust.[only when you adjust Mobility VBIOS]
For example when you reach say 800MHz for GPU core, [with normal Synchronized mode 1]
and say further 810MHz is unstable, at this point you can try to boost it to 810MHz but by using Mode 2 instead.
Then to retest. If become stable you can continue above by using Mode 2.
Which one will be fastern Mode 1 or Mode 2 GPU core adjust?
If we are talking about the same GPU frequency, Mode 1 should perform fastern.
In Mode 2 GPU boost, its possible to reach higher GPU core frequency compared to mode 1.
Best use Combined mode. I.e.:
From Original BIOS:
Start GPU core adjust with Mode 1 [Synchronized],
until you reach unstable state.
Mode 1 booster automatic adjust GPU core along with LTC and XBAR frequency,
by using the same ratio as is original VBIOS and to keep it synchronized GPU core frequency.
By using this mode should bring you best peformance.
Let's say we hit the wall with Mode 1 booster [vbios: mod1.rom]
Then we continue modify from our progress from vbios: mod1.rom,
but using Mode 2 booster instead and to apply the new higher GPU core frequency.
And to retest.
Mode 2 booster is adjusting GPU core frequency only, keep it asynchronized with LTC and XBAR frequency.
So if LTC and XBAR frequency is holding back the main GPU core frequency,
this mode will help you to drain the maximum from GPU core.
Resulting in mod2.rom [comes from mod1.rom]
By combining Mode 1 booster, [until hit the wall] then continie with Mode 2 booster,
we can opimize our GPU at maximum potencial of GPC, LTC and XBAR frequency.
Q.: When i turn on or reboot my computer, my Kepler based graphic card become annoying noisily like Jet Fighter takeoff.
Is there any way to make it quiet or/and to control it by desired way?
A.:Yes, run FAN adjust thread, then choose Mode3 [Configure boot Fan Duty PWM] and set your FANs to desired levels when they works outside Windows.[not controlled by VGA driver]
This adjustment also will affect cards equipped with Dust Removal Technology.
So keep in mind that setting the FANs Duty to too low value may cause Dust Removal Technology to has not much effect,
due not enough turbulence to perform dust cleanup when FANs perform reversal spin.
Sample usage:
Let's say that we want to apply the followed values for our 570GTX card:
[check VBIOS-Z report before modification]
1st: We want to set Load voltage to 1062mV
2nd: We want to adjust FAN speed as followed: min: from 40 to 24, max: from 80 to 100
3th: We want to extent the max voltage limit Load voltage from 1.1V to 1.175V
4th: We want to adjust and apply memory clock from 1050MHz[real] (4200 effective) to 1070MHz[real] (4280 effective)
5th: We want to set core clock from 786MHz to 809MHz
[check VBIOS-Z report after modification, to ensure that desired paraters are now applied and we can see how it will effect all other parameters along with calculated new performance settings based on our newest VBIOS modification and also verify and ensure that VBIOS integirity is OK before save and flash our custom and modified VBIOS]
Here we go:
Tuner's Features:* Full automatic, very quick and easy to use
* Support 3D[underload] core clock adjusting
* Support 3D[underload] core voltage adjustment
* Support 3D[underload] core max voltage adjustment
* Support FAN adjustment
* Support 3D[underload] memory clock adjusting
* Special support for Mobility Series, allow P0,P1,P8 states modifications
* Can detect, calculate, supply information about:
- current checksum
- calculated checksum
- automatic correct checksum per each thread
- detect VBIOS images
- detect VBIOS structure
- self correct VBIOS image if needs
- can repair damaged VBIOSes checksums [etc: load vbios image with bad checksum, Tuner can auto fix it]
- detect and supply info about Image Build Date
- detect and supply info about Version ID
- detect and supply info about Modification Date
- detect and supply info about image geometry
- detect and supply info about active P0 State
- detect and supply info about FAN min/max values
- detect and supply info about 3D underload voltage [2 modes: vary in range, or enforced one]
- detect and supply info about max 3D underload voltage
- detect and supply info about GPU chip and video card itself
- detect and supply info about Image File Version[Only on MSI graphic cards{when detected, detection is automatically}]
- detect and supply info about SS Dynamic Ratio
- detect and supply info about L2 Cache Clk Crossbar Sync
- detect and supply info about Core clock
- detect and supply info about Processor Cluster clock
- detect and supply info about LTC2 Frequency
- detect and supply info about XBAR2 Frequency
- detect and supply info about Real Memory Clock
- detect and supply info about DDR5 Memory Clock
- calculate and supply info about VBIOS Memory Bandwidth
- calculate and supply info about VBIOS Texture Fillrate
- calculate and supply info about VBIOS Pixel Fillrate
- calculate and supply info about VBIOS FLOPS
- calculate and supply info about VBIOS Fermi L2 Cache Bandwidth
- supply info about Fermi L2 Cache Size
* can proceed MSI's Power Editions
* support special DCII VBIOS images with EPU extension [both with and without padding]
* VBIOS-Z Style:
{We can check and see the performance of the video card based on VBIOS scan,
without having the card front of us and also we can modify desired parameters and to see how they will affect the performance without flashing the card or when don't have the card which belong this VBIOS}
* Auto determine, calculate and adjust LTC2 Freq., XBAR2 Freq. and Processor Cluster Freq. based on our newest desired GPU core clock speed.
Current Supported VGAs VBIOSes:Nvidia Graphics cards from Fermi Series:
[635M used in ASUS K75VJ-TY087H is
NOT Supported]
Nvidia Graphics cards from Kepler Series:
Note: Kepler mobiles are not supported!Eventually they can be added later in time, but for now they are not supported.
For updated info check
*** below.
***Partially supported models: [in build process]
: Allow memory adjusting for all P-States.
Note: Only FAN adjust feature[See *** below for details] are supported for Kepler's vBIOS for now.
More features can be added with further versions. EDIT: Voltage adjust and power control has been also added:
* Add voltage adjust for supported Kepler GPUs [available at voltage tune]
* Add power control for supported Kepler GPUs [available at power control]
-Board Power (default/max)
-Power Target (100%/max)
+ calc. and shows power Limit % in real time before apply desired changes.EDIT2: Add Memory frequency adjustment for Kepler supported cards for states [P0,P2,P5,P8]
EDIT3: Add Core Management support for Kepler's GPU:
- Configure P-State Maximum Frequency [Sub domains auto applied based on desired frequency]
- Configure Maximum Voltage Frequency [Sub domains auto calculated with 26MHz steps and applied based on desired frequency]
- Configure Essential P-State (Default clock, Boost clock, domain 3[when Turbo Boost is ON])
[chooses auto determinate based on P-State and Voltage Frequency, domain 4 auto adjust depend of Boost state]
- Configure 3D Boost and Turbo Boost [N/A For GTX TITAN]
***Support advanced FAN adjust features for Kepler:
-
Configure Fan speed range in (%) -
Configure Fan speed range in (RPM) -
Configure boot Fan Duty PWM in (%)Supported OS:XP, Vista, Windows 7 [all kind of sub versions]
Both
32-bit and
64-bit OS versions.
Change logs:
Version has been updated [ 0.12c ==> 0.18e ]:Changes:
- Add voltage[load & max voltage] read/write support for latest and special MSI's 580 Lightning VBIOSes above version 130
Version has been updated [ 0.18e ==> 0.33f ]:Changes:
- Updated VBIOS-Z Report Engine
- Fixed issue: Tuner cannot work in Vista/Windows7 if UAC is Enabled, caused an error "A referral was returned from the server."Version has been updated [ 0.33f ==> 0.56p ]:Changes:
- Add support for GTX 570M
Version has been updated [ 0.56p ==> 0.75s ]:Changes:
- Add support for GTX 570M [secondary different general type]
- Add support for GTX 560M [2 different general types]
Version has been updated [ 0.75s ==> 0.83x ]:Changes:
- Add voltage adjustment support for 560M
- Add alternative GPU clock booster for Mobility Series
Version has been updated [ 0.83x ==> 0.92a ]:Changes:
- Allow P1 state clocks modifications for mobility Series for cases:
- 560M[Type1, Type2], 570M[Type1, Type2] in both Synchronized[GPC,LTC,XBAR] & Asynchronized [GPC only] GPU Clocks adjust.
- 560M[Type1, Type2], 570M[Type1, Type2] Memory Clock adjust.
- 560M[Type1, Type2], 570M[Type1, Type2] Voltage adjust auto apply to both P1/P0 states.
- Extend voltage limit for 570M[Type1, Type2] to 920mVVersion has been updated [ 0.92a ==> 1.07f ]:Changes:
- Updated VBIOS-Z Engine
- Updated appearance [cosmetic corrections]
- Allow P8 core clocks modifications for 570M [Type1, Type2]
- Limit LTC and XBAR clocks domains in P8 state when is used Synchronized mode to 598MHz with regard less of GPC clock.
- P1 and P0 voltages for 570M [Type1, Type2] now can be controlled separately
- Allow P8 voltage modification for 570M [Type1, Type2]
- Allow P8 memory clock adjustment for 570M [Type1, Type2]
- Improved handle method for 570M [Type1, Type2] & 560M [Type1, Type2]
- Allow P1 and P0 separate voltages control for 560M [Type1, Type2]
- Allow P12 and P8 voltages adjustment for 560M [Type1, Type2]
- Implement Self Update Feature [Tuner now can self update when a newest further version is released]
Version has been updated [ 1.07f ==> 1.09h ]:Changes:
- Add support for new kind of VBIOS image for 570M [70.24.32.00.04(GT780DX/GTX570M/3GB DDR5)]Version has been updated [ 1.09h ==> 1.11j ]:Changes:
- Fixed issue introduced in version 1.09h[from yesterday] cannot modify voltage for [70.24.32.00.04(GT780DX/GTX570M/3GB DDR5)]
Version has been updated [ 1.11j ==> 1.12k ]:Changes:
- Support experimental[non standard] vBIOS 570M image[a variable of type1]
Version has been updated [ 1.12k ==> 1.13p ]:Changes:
- Add support for GTX 460M [2 different general types]
Version has been updated [ 1.13p ==> 1.14s ]:Changes:
- Add support for GTX 580MVersion has been updated [ 1.14s ==> 1.16x ]:Changes as simple as possible without too much details, just essential: [like in prevision recent change logs]
- Update GTX 580M: Add support for secondary and different general vBIOS type.
- Add support for GT 555M, 2 different general vBIOS types.
Version has been updated [ 1.16x ==> 1.17a ]:Changes as simple as possible without too much details, just essential: [like in prevision recent change logs]
- Update GTX 560M:
* Allow P8 frequency modifications [voltage is already available]
* Add support for another and different general vBIOS type of 560M
- Allow P8 and P12 frequency and voltage modifications for 560GTX-Ti
- Add support for GT 635M
Version has been updated [ 1.17a ==> 1.19d ]:Changes as simple as possible without too much details, just essential: [like in prevision recent change logs]
- Reduce low freq. limit from 100MHz to 20Mhz [Usefull for P12 freq. modifications]
- Add support for 560GTX-Ti 448
[recently released card, such as: [example for msi's representative cards: N560GTX-448 Twin Frozr III Power Edition, N560GTX-448 Twin Frozr III Power Edition/OC]]
Version has been updated [ 1.19d ==> 1.20f ]:Changes as simple as possible without too much details, just essential: [like in prevision recent change logs]
- Add Support for GTX 470M + auto correct GPU-Z's dump issue if and when needs.
[auto remove unnecessary padding when such exist in vbios image when saved with GPU-Z]
- Update GTX 460M: Add support for 3th different general vBIOS type.
Version has been updated [ 1.20f ==> 1.25g ]:Changes as simple as possible without too much details, just essential: [like in prevision recent change logs]
- Add Support for GTX 670M
- Add Support for GTX 675MVersion has been updated [ 1.25g ==> 1.26k ]:Changes as simple as possible without too much details, just essential: [like in prevision recent change logs]
- Update GTX 560M[Type1,Type2]: Allow P12 clock modifications
- Add Support for GTX 560SE
Version has been updated [ 1.26k ==> 1.27n ]:Changes as simple as possible without too much details, just essential: [like in prevision recent change logs]
- Update GTX 580M[Type1,Type2]:
* Allow P12 clock and voltage modifications
* Allow manual LTC and XBAR clocks input[linked together, one input will update them both] for P8 and P12 statesFor P0 and P1 states, they works as for all others, i.e, depend of choose:
In Synchronized mode: LTC and XBAR clocks will be automatically calculated and updated based on their ratio,[keeping the same ratio] and based on user GPC clock input.
In Asynchronized mode: Only GPC will be modified depend of user input. LTC and XBAR clocks will remain as is.
Version has been updated [ 1.27n ==> 1.28s ]:Changes as simple as possible without too much details, just essential: [like in prevision recent change logs]
- Update GTX 580M: Add support for newest release different vBIOS type 3
- Update 560GTX-SE: Add support for vBIOS type 2
- Other tool optimization
Version has been updated [ 1.28s ==> 1.29t ]:Changes as simple as possible without too much details, just essential: [like in prevision recent change logs]
- Update GTX 570M related to all vbios types[1,2,3]:
* Allow P12 clock and voltage modification
* Improve P8 and P12 core clock modification, allow manual synchronized[one value will update both of them] LTC and XBAR clock adjustment [along with GPC clock with separate clock selection] as ratio between GPC to LTC & XBAR is too high to follow.Version has been updated [
1.29t ==> 1.30u ]:
- Update 560GTX-Ti: Add support for newest vbios type.
Version has been updated[user request] [
1.30u ==> 1.31x ]:
- Update 560GTX-Ti 448: Add support for newest vbios type.
Version has been updated [
1.31x ==> 2.33a ]:
- Update self update module
- Add support for various Kepler VGA's, include support for Hybrid UEFI vBIOSes.
Supported Kepler units:
* GTX 680 [4 different general types]
* GTX 670 [2 different general types]
* GTX 660 Ti
* GTX 660 [2 different general types]
Note: Only FAN adjust feature[See *** below for details] are supported for Kepler's vBIOS for now.
More features can be added with further versions.
***
- Add advanced Kepler's FAN adjust features:
1 Configure Fan speed range in (%)
2 Configure Fan speed range in (RPM)
3 Configure boot Fan Duty PWM in (%)Version has been updated [
2.33a ==> 2.35d ]:
* Improve tool performance
* Update boot Fan Duty PWM to add support for 660Ti new type GB variable.
* Adjust low FAN limit to 5%
* Add voltage adjust for supported Kepler GPUs [available at voltage tune]
* Add power control for supported Kepler GPUs [available at power control]
-Board Power (default/max)
-Power Target (100%/max)
+ calc. and shows power Limit % in real time before apply desired changes.Version has been updated [
2.35d ==> 2.36f ]:
* Add Memory frequency adjustment for Kepler supported cards for states [P0,P2,P5,P8]
Version has been updated [
2.36f ==> 2.37g ]:
* Add support for GTX 660 OEM
* Change minimum boot Fan Duty PWM to 10% [when operating outside Windows]
Version has been updated [
2.37g ==> 2.40k ]:
* Add support for new vbios type variable of GTX 680
* Add support for Quadro 4000M
* Add Core Management support for Kepler's GPU:
- Configure P-State Maximum Frequency [Sub domains auto applied based on desired frequency]
- Configure Maximum Voltage Frequency [Sub domains auto calculated with 26MHz steps and applied based on desired frequency]
- Configure Essential P-State (Default clock, Boost clock, domain 3[when Turbo Boost is ON])
[chooses auto determinate based on P-State and Voltage Frequency, domain 4 auto adjust depend of Boost state]
- Configure 3D Boost and Turbo Boost
Version has been updated [
2.40k ==> 2.41s ]:
* Fixed issue: Unable to read clocks and voltage correctly for Zotac 680 GTX
Version has been updated [
2.41s ==> 2.42t ]:
* Updated self update module
* Add support for GTX 650 Ti
* Add support for GTX TITAN
* Allow minimum FAN 0%
Version has been updated [
2.42t ==> 2.43w ]:
* Fixed update issue, at some machines sometimes cannot find the new version. [cache issue]
Version has been updated [
2.43w ==> 2.44x ]:
* Update GTX 670M: Add support for 2 new vbios types, used in system BIOS [not in dedicated card bios]
Version has been updated [
2.44x ==> 2.45a ]:
* Update GTX 670M: Add support for 2 more new vbios types[legacy], used in system BIOS [not in dedicated card bios]
* Update GTX 650 Ti:
- Add support for new vbios type
- Improve core boosting
- Improve compatibility with future vbios types
* Update GTX 670: Add support for new vbios type with GOP Support.Version has been updated [
2.45 ==> 2.46b ]:
* Update GTX 660 Ti: Add support for new vbios type with GOP Support.
* Update GTX 660: Add support for new vbios type.
* Update GTX 680: Add support for new vbios type.
* Modify descriptions for some items for better clarify.
* Update GTX TITAN:
- Allow P-State voltage modifications.
- Add addiction experimental test voltages [1225mV,1237mV,1250mV] for those who want to try and test it.
- Adjust boot FAN duty range.
* Update certain modules to cause less false alerts for some too sensitive AVs
* Update Kepler Core Management:
- Applied new boosting rules
- Update boosting tables
- Extent region range of allowed selection
- Improve performance
* Add initial support for GTX 780M [allow memory clock adjust for all P-States]Version has been updated [
2.46b ==> 2.47c ]:
* Update GTX 680:
- Add support for new vbios type with GOP support
- Add support for new vbios type
- Improve compatibility with future vbioses
* Add support for GTX 460
* Add support for GTX 780
* Add support for GTX 770 [2 different general types]
* Update GTX 780M: Add support for new general type.
***********************************
Svet's VBIOS Tuner is available on donation:
>>> 
<<<
Once donation is done, the Tool will be e-mailed to the co-respond person,
who also will gain donation free further versions{updates} of the Tuner.
[etc. this donation is need only once per person]
[if someone wish to donate further, it can be done directly from Tool's main interface where can be set a custom donation amount]***********************************
Further released Tuner's versions will be available via tool's self update feature:
Best Regards,
Svet
NOTE:
All modifications which you do are entirely at your own risk!
Author
Topic: Svet's Fermi/Kepler VBIOS Tuner - [ver: 2.47c] (Read 131864 times)
Official Site