2013/07/04 13:36:40
William
KILLER_K

More the likely it will have it. But you can do a easy fast check with the Nvidia control panel.

Q. How can I tell what version I firmware I currently have?
A. There are multiple ways to do this, one way is to right click on desktop and go to NVIDIA control panel. Click on Help, then System Information. Scroll to the bottom of the Details window and it will show your "Video BIOS version". It will be listed as EXAMPLE: 80.04.31.00.72. The numbers in bold identify the version number.


 
Mine says 80.04.5C.00.70 So I guess it's good to go.
2013/07/04 17:28:26
KILLER_K
You are 100% correct. Have fun with your new video card.
 
William
Mine says 80.04.5C.00.70 So I guess it's good to go.


2013/07/13 05:16:18
1wayjonny
Hello,
 
This is because your 570 was Nvidia Fermi card, the 600 series is Kepler. Nvidia has enabled a terrible auto overclocking scheme which limits the cards ability to run a steady mhz and its always jumping around.
 
You can fix this by using nvidia inspector and putting the GFX in a custom power mode and you can set the mhz and power etc manually. This will immediately eliminate the microstutter you see with your 600 series.
 
Just remember when your done playing the game you have to return the GFX to the normal power mode other wise your card will be running the higher clockspeed unltil you retun the mode or reboot.
 
This is very help thread here: http://www.overclock.net/t/1267918/guide-nvidia-inspector-gtx670-680-disable-boost-fixed-clock-speed-undervolting
 
My settings for my 670 4GB SuperClocked is below:
 
Overlcock:
nvidiaInspector.exe -setBaseClockOffset:0,0,125 -setMemoryClockOffset:0,0,500 -setpowertarget:0,122 -setVoltageOffset:0,0,187500 -setGpuClock:0,2,1171 -setMemoryClock:0,2,3504 -forcepstate:0,2
 
Return:
nvidiaInspector.exe -forcepstate:0,16
 
 
Hope this helps many!
 
 
 
luckyirishlad

Hi
Any advice would be very much appreciated
Was just wondering if its worth updating my gpu bios
I am running on a 1156 mb and i am now getting slight stuttering within a few games and is very annoying...
The card i had in before a 570 was running fine np in any game but now since my gfx upgrade i am getting slight stuttering.i have also noticed the power monitor graph in evga precision is fluctuating up and down a lot.

Part Number: 02G-P4-3677-KR
Part Desc: EVGA GeForce GTX 670 FTW SIG2
bios 80.04.4B.00.70

I have since defaulted my cpu back to stock
uninstalled nvidia drivers ect ect
placed 570 back in to check and all was fine back to 670 and problem arised again
i know its not the psu... be quite 650w 80 plus gold
mb bios fully updated
all drivers updated

Ta sy


2013/07/13 07:54:41
johnerz
Like all the updates, they are only needed if you are having any issues.
 
My 670 2 GB FTW, is over a year old on the original bios, rock solid @ 1306/6610 - Power +130, Core +99, Memory +200
 
24/7 it is a folder
2013/07/25 08:56:56
etoko
Is there currently a more up to date UEFI firmware for the 
02G-P4-2670-KR - EVGA GeForce GTX 670? 
I am running 80.04.4B.00.F0.
 
2013/07/25 09:56:52
KILLER_K
I will just email JacobF for this information.
2013/08/05 10:44:58
feniks
wow, 5C BIOS for 670? I am still using 4B, missed that update. will try it soon after work.
 
edit: requested uefi version of this vbios from tech support.
2013/08/05 21:56:58
error-id10t
When you get the EFI version and disable CSM in BIOS, can you check event log and see if you get the below error - for me this happens during/straight after reboot, doesn't cause any issues but it's there. I asked this before but nobody responded - it goes away as soon as I enable CSM so the old ROMs run.
 
The description for Event ID 14 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\Video3

CMDre 00000000 00000080 00000000 00000005 0000001d

2013/08/05 22:08:43
feniks
running 5C UEFI vBIOS here on 670 2gb ref in SLI under UEFI mode with win8 x64. I do not see such event in Logs at all. i actually filtered whole logs in either app or system sub-menu and I never had it on any driver ranging from 314.x through 320.18 up to 320.49 whql (currently used). I did use driver removal and then Driver Fusion cleaner recently for both nvidia display and physx at some point when troubleshooting other issues (VSYNC related and PSU related after all), maybe you could try that too, not that it did help me, because I haven't had such issue ever (had others LOL) ... at least it can't hurt
 
As per my first impression with 5C vBIOS, I think it really improved my card(s) stability, dialed up 1 notch higher on OC that was formerly unstable in Tomb Raider (display crashes) and so far so good, smooth as butter, but I haven't played for long yet... Geothermal Caverns are kinda repulsive LOL!
 
error-id10t

When you get the EFI version and disable CSM in BIOS, can you check event log and see if you get the below error - for me this happens during/straight after reboot, doesn't cause any issues but it's there. I asked this before but nobody responded - it goes away as soon as I enable CSM so the old ROMs run.

The description for Event ID 14 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\Video3

CMDre 00000000 00000080 00000000 00000005 0000001d



2013/08/09 17:41:39
error-id10t
Thanks for taking a look. I've tried the usual uninstaller and now tried this also
 
https://forums.geforce.com/default/topic/550192/geforce-drivers/display-driver-uninstaller-ddu-v4-1/
 
Still there though.
 
One of the threads there were talking about memory leaks and TDRs after 36 hours + then someone mentioned this error code 14 also. I honestly think it's the 32x drivers just giving that error for some reason now. I haven't tried 314.x though.. that would confirm it either way.

Use My Existing Forum Account

Use My Social Media Account