Jump to content

Search the Community

Showing results for tags 'vbios'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Forum Introduction & Feedback
    • Site Announcements, Rules & New Member Intros
    • TechInferno Forum Feedback
  • Tech News & Reviews
    • News & Reviews
  • Notebook Discussion
    • General Notebook Discussions
    • Notebook OEM Subforums
    • What Notebook Best Fits My Needs?
    • Legacy Articles
  • Desktop & General Hardware
    • General Desktops Discussion
    • Desktop Hardware
    • Overclocking, Cooling & Build Logs
  • Software, Networking & Gaming
    • PC & Console Gaming
    • Video Driver Releases & Discussion
    • Networking
    • General Software Discussion
  • Everything Else
    • Off Topic
  • Legacy Section (Not Actively Supported)
    • DIY e-GPU Projects

Categories

  • SVL7 & Klem VBIOS Mods
    • AMD
    • Alienware M11x R3
    • Alienware M14x R2
    • Alienware M17x R4
    • Alienware M18x R1
    • Alienware M18x R2
    • Kepler VBIOS
    • Lenovo Y400-Y500
    • Lenovo Y410p-Y510p
    • Lenovo Y580-Y480
    • Legacy BIOS/VBIOS
    • Maxwell VBIOS
    • Sony Vaio SVS13 / SVS15 series
  • BAKED BIOS Mods
    • Clevo
  • Utilities

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Steam


AIM


MSN


Website URL


Yahoo


Jabber


Skype


Location


Interests


Occupation

  1. Hi together :-) As the title says I'm having a little Issue after upgrading my m6700's graphics card from the K3000M to the newer K4100M: Everything seems to work properly, but under load (i.e. 3D applications) it produces crashes / system instability after ~5-20 seconds. When I reduce the chip- and memory-clocks in MSI Afterburner as far as possible, it takes a bit longer until it crashes, but eventually it always does after a minute or so. When running on battery power (and thus even further reduced clocks) everything runs stable for arbitrarily long times. This sounds like a thermal problem to me. However, the reported GPU temperature never exceeded 65°C, which I think is OK. I guess the memory chips are not temperature monitored seperately, are they? So maybe I should replace the memory thermal pads by new ones? What I've already tried/checked/looked at: - Uninstalled previous drivers with "Display Driver Uninstaller" - Latest Nvidia Drivers can be installed properly (and also tried a few older versions) - Notebook BIOS is up to date - Tried three different Video-BIOS versions - Graphics card is not recognized by Notebook BIOS properly ("Unknown video card") - Graphics card is recognized under Windows, though (Device-manager / Nvidia control-panel / GPU-Z and so on) - Sometimes after a crash the system recovers and a pop-up says that the nvidia graphics driver crashed and was restarted - Of course, I'm using the large 240 Watt Power supply Ok, that's about everything I remember to be relevant at the moment. I'd appreciate any kind of help :-) ... If you need further Information, just let me know, and I'll try to deliver it. Thank you, Florian
  2. I'm aware that this problem has come up before and is likely solved, but I am new to the forums so i need to post to have full access to these resources, so i figured i may as well start a new thread. Related posts: http://www.ebay.com/itm/222124374139?_trksid=p2060353.m1438.l2649&ssPageName=STRK%3AMEBIDX%3AIT - Item I purchased https://www.techinferno.com/index.php?/forums/topic/6308-msi-gt70-no-post-black-screen-after-video-card-upgrade-from-675m-to-680m/ - People already discussing this very same issue https://www.techinferno.com/index.php?/forums/topic/1425-nvidia-kepler-vbios-mods-overclocking-editions-modified-clocks-voltage-tweaks/ - all available Keplar VBIOS I'd still like to start fresh though. The computer I plan on putting this into is a MS-1762 Windows 7 ultimate 64-bit i7-3630QM Quad-Core 2.4ghz 8GB DDR3 @ 1600mhz Chipset: HM77 / Intel Ivy Bridge My goal in this thread is to be prepared for when the card arrives. I have never flashed a VBIOS before so I will take all the help and advise I can get.
  3. ok, so, i have a serious problem atm. im trying to mod my bios so that i can go past the normal overclocking limit. however, everytime i try to do it, it always says "file size does not match existing bios size!", and it's really annoying, since i had to find everything myself, as no one else online tried this on my specific model, besides me. (which surprises me, really) this is the guide im following: So this is my detailed description how I managed to mod and overclock my GTX 960M in my Lenovo Y50-70. Please note: it is very dangerous to play with the BIOS, so you need to be very careful! I take NO RESPONSIBILITY for any damage or misuse of the information below! Use it AT YOUR OWN RISK! ------- Necessary tools: A. Fptw64 from Intel (9.5 or above) http://forum.hwbot.org/showthread.php?t=75024 B. PhoenixTool (2.50 or above) C. Maxwell II BIOS Tweaker (1.36) https://www.techpowerup.com/downloads/2562/maxwell-ii-bios-tweaker-v1-36/ ------------------------- How to flash Modded BIOS: 0. Flash the latest (3.03 now) official BIOS 1. From Windows, start 'cmd' as Administrator and read your your BIOS via Fptw64: Fptw64 -d BIOS.ROM -bios 2. Reboot, enter your BIOS and check "Enable downgrading BIOS" feature (we need to downgrade first in order to flash the modded BIOS) 3. From Windows, downgrade to 1.13 (this is necessary because the newer BIOSes have protection against mod-ding) 4. After reboot & reflash, start Windows, then enter standby, wait a bit, then wake up the machine 5. Create your modded BIOS, see separate list below 6. Start 'cmd' as Administrator and write your _modded_ BIOS via Fptw64: Fptw64 -f BIOS_MODDED.ROM -bios ------------------------- How to create modded BIOS (point 5 above): 5.1 Start PhoenixTool.exe from Phoenix Tool 2.50 and open your previously saved original BIOS.ROM from point #1 above .2 The tool analyses it and shows some messages, click OK .3 Now you can find your vBIOS in the "DUMP" subfolder in the folder containing your BIOS.ROM, with the file name: BE13645B-2C2C-44D2-A64F-0EA052C34597_1796.ROM .4 Create your modded vBIOS, see separate list below -> let's call it 960M_OC.MOD .5 Click on "Structure" .6 Open "EFI BIOS" tag .7 Open second "File Volume {7A9354D9-...}" tag .8 DXE Core -> Compressed Section -> Raw section -> File Volume {7A9354D9-...} .9 In the very long list, find the following tag (usually displayed at around 80% of the list): Freeform {BE13645B-2C2C-44D2-A64F-0EA052C34597} This is the item containing the latest vBIOS .10 Open the tag, then "GUID defined section", then click on Raw section. "Internal number" (in the top right corner) should be 1796 for BIOS 3.03. .11 Click on "Replace" and select your modded vBIOS (called 960M_OC.MOD above) .12 Click exit "Exit" and say Yes to "Save changes?" .13 Close the Phoenix Tool; now you should have your BIOS.ROM updated (the original will be saved as BIOS.ROM.OLD for safety) ------------------------- How to create modded vBIOS (point 5.4 above): Use Maxwell II BIOS Tweaker to change BE13645B-2C2C-44D2-A64F-0EA052C34597_1796.ROM; 5.4.1 Open the ROM .2 Change "Boost Clock" on "Common" tab to the new boost-ed maximum value .3 On "Boost table" tab, use the slider in the right bottom corner to increase your max boost-ed value to the same number .4 On "Boost states" tab, at P00 profile, change the MAX values in the GPC, L2C and XBAR fields to the same max boost-ed value .5 Save your modified BIOS and rename it to 960M_OC.MOD (My boost-ed max value was 1359 MHz. I could then use MSI Afterburner's software tuning -> my 960M could reach 1454 MHz without voltage increase.) i know that it's for a different laptop, but its basically the same ill provide more info when im home
  4. Hey guys, does anyone have the spare time to mod my laptops BIOS so that I can remove the limit of the sliders in MSI Afterburner. So that I can go above a max of 135 on the core, have the voltage and power limit sliders unlocked etc. If it can be done for free, I would much appreciate it, and donate in the future when I get some money. If you can do the task, plz reply and I'll upload my BIOS backup to RGhost if that's the site you guys upload stuff to on this forum. Thanks in advance friends!
  5. [Preface: I searched for about 30 minutes on Tech|Inferno before posting this, no one likes repeatied posts: ] I have a Clevo P370SM3 (now a P370SM) running dual 980m's that were part of an upgrade kit from Eurocom. I am considering using PremaMod's VBIOS mods on this page to take advantage of Prema's GPU improvements for the 980m. On that link on Page 4 are (3) different variants of the 980m GPU. How do I tell which one is the correct one for my 980m GPU's? Nvidia Inspector? If I had to speculate I would assume the GTX980M_8GB_MXM_OC_PM? MAXWELL GTX980M_8GB_MXM_OC_PM GTX980M-G_8GB_MXM_ZM_OC_PM GTX980M-G_8GB_MXM_DM_OC_PM Constructive thoughts or suggestions appreciated. Kind Regards, Koinonos P.S. I went from 12,000 on 3DMark 2011 on 780m SLI to 16,400 on 980m SLI. A nice step up and I think 18,000 is reachable with minor adjustments.
  6. Version 1.0.0

    45 downloads

    Klem's_vbios_ASUS_G752VT_970M_GS_UNLOCKED. This mod for ASUS_G752VT_970M with G-SYNC! 1. Unlocked Nvidia core limit +135 MHz. 2. Unlocked Power Limit. 3. Unlocked Power adjustment by software (for example with Nvidia Inspector). 4. Increased Power Limit and Power Target. 5. Enabled some additional tweaks. If you liked my mod, you can buy me some beer: https://www.buymeacoffee.com/timqsh
  7. Hi! I sent you a PM with a vbios dump for my GTX970M in my Asus ROG G752VT-T7013T (w. G-Sync) and will happily donate if you could consider to make a unlocked vbios for this one
  8. Hy everyone, I say it now but i'm french and i do my best for writing in english whithout translation so sorry for mistakes... i've been a reader for a long time but today i really need help that i can't find by myself... So, I have a AW 14 with I7 4700 and GTX765M and the problem is the throttling keep my GPU at 405Mhz, i goes on every site for this problem but nothing works! and I see a last one solution the slv7 Vbios for GTX765m unlocked, but... i can't download it! so if someone could help me with that vbios or another solutions i would be really happy and i'll give feedback! thank you!
  9. Hy everyone, I say it now but i'm french and i do my best for writing in english whithout translation so sorry for mistakes... i've been a reader for a long time but today i really need help that i can't find by myself... So, I have a AW 14 with I7 4700 and GTX765M and the problem is the throttling keep my GPU at 405Mhz, i goes on every site for this problem but nothing works! and I see a last one solution the slv7 Vbios for GTX765m unlocked, but... i can't download it! so if someone could help me with that vbios or another solutions i would be really happy and i'll give feedback! thank you!
  10. Hey guys! Earlier this week I upgrade my laptop with a new network card. I bought a Intel WiFi AC 7260 for my Lenovo Y510p. So most of you probably know, Lenovo's BIOS has a whitelist. So I flashed the BIOS so that I could use the new network card. This happened without any problems, I installed the network card and booted my laptop. Drivers worked the moment I logged in and connecting to a network was easy and fast. Checked speedtest.net for the up and down speeds, perfect! There is a problem I encounterd though, it has nothing to do with my BIOS (I think) or my new network card. It has something to do with my GPU's. I run an SLI configuration of 2 x Nvidia GeForce GT755m. (one main, one ultrabay) I was following a guide made by @svl7 about flashing the BIOS. After the part of flashing the BIOS there was something about flashing the vBIOS too, because if you are running 2 GPU's it was not going to work properly. When flashing the vBIOS I encountered the problem. As explained by the guide, I used NVflash to flash vBIOS, when using the command "nvflash -a" to view adapters and their "index" they were on "0" and "1". I tried to flash both of them, "1" flashed easily without any problems, "0" did not flash at all. Now the error displayed was: "ERROR: GPU NOT DETECTED." Has anyone got an idea of how to fix this? I'm not able to flash one of the GPU's. If I play a videogame on my laptop, every now and then (intervals of 1-5 minutes) my screen goes black, audio stutters and comes back to normal after a few seconds. Hope you guys can help me out! If there's any info you need let me know and I'll edit the post!
  11. Version 1.0.0

    17 downloads

    Klem's_vbios_ASUS_GTX870M_80.04.F4.00.01_UNLOCKED 1. Unlocked Nvidia core limit +135 MHz. 2. Unlocked Power Limit. 3. Unlocked Power adjustment by software (for example with Nvidia Inspector). 4. Increased Power Limit and Power Target. 5. Enabled some additional tweaks. If you liked my mod, you can buy me some beer: https://www.buymeacoffee.com/timqsh
  12. Version 1.0.0

    34 downloads

    Klem's_vbios_MSI_GTX770M_80.06.54.00.11_UNLOCKED 1. Unlocked Nvidia core limit +135 MHz. 2. Unlocked Power Limit. 3. Unlocked Power adjustment by software (for example with Nvidia Inspector). 4. Increased Power Limit and Power Target. 5. Enabled some additional tweaks. If you liked my mod, you can buy me some beer: https://www.buymeacoffee.com/timqsh
  13. Version 1.0.0

    777 downloads

    Files contained in this archive: FTP-DOS.zip prr2.zip M18x R2 - BIOS A03 'unlocked.zip M18x R2 - BIOS A08 'unlocked.zip M18x_R2_-_BIOS_A08_-_[unlocked]_-_[IRST 11.0.6.1702].zip M18x_R2_BIOS_A03_-_[unlocked] - [IRST 11.6.0.1702].zip M18x_R2_BIOS_A09_-_[unlocked].zip [FPT]-M18x_R2_BIOS_A09_-_[unlocked].zip [FPT]-M18x_R2_BIOS_A10_-_[unlocked]_V2.zip M18x_R2_-_BIOS_A08_-_[unlocked].zip M18x_R2_BIOS_A03_-_[unlocked].zip For information on how to use the files in this archive, see here: My donation link in case you want to buy me a beer
  14. Version 1.0.0

    2074 downloads

    Files contained in this download: Asus 770m (G750JX) - 80.06.54.00.13 'OC edition' rev02.zip Clevo 670mx - 3GB - 80.04.58.00.03 - 'OC edition'_rev02.zip Clevo 675mx (4GB) - 80.04.58.00.05_'OCedition'_rev00.zip Clevo 680m - 80.04.29.00.01 'OCedition' revised_01.zip Clevo 680m - 80.04.33.00.10 'OCedition' revised_01.zip Clevo 680m - 80.04.33.00.10_'OCedition'_revised_01 - OV 1000v.zip Clevo 680m - 80.04.33.00.10_'OCedition'_revised_01 - OV 1025v.zip Clevo 680m - 80.04.33.00.10_'OCedition'_revised_01 - OV 1050v.zip Clevo 680m - 80.04.67.00.01 'OCedition' revised_01.zip Dell 680m - 80.04.5B.00.02_'OCedition'_revised_00.zip Dell 680m - 80.04.33.00.32__'OCedition'_revised_00 - OV 1000v.zip Dell 680m - 80.04.33.00.32__'OCedition'_revised_00 - OV 1025v.zip Dell 680m - 80.04.33.00.32__'OCedition'_revised_00 - OV 1050v.zip Dell 680m - 80.04.33.00.32__'OCedition'_revised_00.zip Dell 765m - 80.06.61.00.01 - 'OC edition' (AW 17) - v00.zip Dell 765m - 80.06.64.00.01 'OC edition' (AW 14).zip Dell K4000m - 80.04.33.00.34_'OC edition'.zip Dell K5000m - 80.04.33.00.05 'OCedition' rev00.zip HP K3000m - 80.04.33.00.2E - 'OC edition'.zip MSI 670mx (1.5GB) - 80.04.5B.00.A5 'OCedition' rev00.zip MSI 675mx (2GB) - 80.04.58.00.14_'OCedition'_rev00.zip MSI 675mx (4GB) - 80.04.58.00.0E_'OCedition'_rev00.zip MSI 680m - 80.04.33.00.24_'OCedition'_revised_02 - OV 1000v.zip MSI 680m - 80.04.33.00.24_'OCedition'_revised_02 - OV 1025v.zip MSI 680m - 80.04.33.00.24_'OCedition'_revised_02 - OV 1050v.zip MSI 680m - 80.04.33.00.24_'OCedition'_revised_02.zip MSI 770m - 80.06.54.00.11 'OC edition' - rev02.zip Nvidia 770m - 80.06.51.00.0F 'OC edition' - rev02.zip Nvidia GTX 780m - 'OC edition' - rev02.zip Nvidia GTX 860m (Kepler) - 'OC edition' - rev00.zip Nvidia GTX 870m - 'OC edition' - rev00.zip Nvidia GTX 880m - 'OC edition' - rev00.zip Nvidia K3000m - 80.04.3A.00.07_'OCedition'_rev00.zip Instructions on how to use these files:
  15. Version 1.0.0

    5 downloads

    AMDs professional mobile GPUs (FirePro M Series) use the same hardware as their gaming equivalent (Mobility Radeon HD Series) The difference lies in the VBIOS and in the specialized driver. This allows to simply change a 6970m into a FirePro M8900 by simply flashing the appropriate VBIOS and installing the corresponding driver: (UPDATE: This also works with the 6990m, see the update at the end of the post) The advantage of the FirePro card lies in the better CAD and DCC performance, optimized OpenGL support, OpenCL features and AMD Eyefinity technology. In short: The card gets optimized for professional applications instead of games. A 6970m is very well capable of CAD work and a M8900 can still play games, but their performance is optimized for other tasks, and this can make quite a difference. A game uses a GPU differently than CAD software. For example you don't need a high frame rate when designing something with CAD software, but it's crucial that the rendering of your work is accurate and detailed. So if you have a 6970m and need to use professional software once in a while you might want to give this a try. I haven't installed any CAD software on my system at the moment, but the driver seems to work properly, haven't seen any issues so far.The procedure doesn't take long, you only need to flash the VBIOS, uninstall your gaming driver and install the professional one. You can use the M8900 driver of the Dell Precision M6600 workstation, you'll find it at the Dell drivers page. Maybe you find a more recent driver on the AMD homepage. Here are some screenshots of the Catalyst Pro Control Center, you'll probably notice some features which aren't available with the Radeon HD cards: I've done this with my Sapphire 6970m, it'll definitely work with the Dell 6970m as well and it's save to assume that this is true for the Clevo/Eurocom version too. Since there are some changes in hardware IDs you'll need to force the flash. NOTE: This should work just as well when your system has a FirePro M8900 and you want to optimize the gaming performance - simply flash the 6970m VBIOS and install the regular driver and you're done. The Dell 6970m VBIOS can be found in this post. Also a big thanks to @Star Forge for providing the VBIOS of the FirePro M8900!! Here's a 3dMark Vantage run with after applying the soft mod to the 6970m, everything at stock, also in the CPCC. Not too bad imo, same pretty much the same as the stock run I did when I got the 6970m in April. Would be interesting to see some gaming comparisions... but I haven't installed any games atm. EDIT: For M17x r3 users: You need to modify the driver, otherwise it won't install here the instruction, a big thanks goes to @devillucifer for investigating this problem and finding a solution. When I come around to do so I'll post a link to a modified driver so you don't have to modify them yourself. Detailed guide for flashing the VBIOS: UPDATE: This also works with the 6990m. Note that the M8900 VBIOS has the same clock speeds as the 6970m, so the 6990m is actually underclocked with this VBIOS. You can easily overclock it with software or modify the clocks of the VBIOS before flashing, so that you're back at 6990m speeds. But even at standard clocks the 6990m performs better than the M8900 or 6970m, the card has 120 additional shaders which will bring a little performance boost as you can see in the screenshot below, I about 1000 points more on the GPU score compared to the 6970m flashed with the M8900 VBIOS (at the same clocks).
  16. Version 1.0.0

    96 downloads

    Did some tests with the VBIOS of the AMD 7970m, here's what I've got so far: - Overvolting: So far no success, when I increase the 3d voltage the card simply stays at the 2d profile. Fixed that Be aware that overvolting should only be done by experienced users and can seriously harm your GPU, shorten the life of its components and lead to unsuspected effects and / or system instability. I take no responsibility for any possible damages. Overvolting has been tested by me and @widezu69 (thanks!). It works, but can lead to instability, you need to find your limit. The M15x doesn't handle it well. I noticed similar behaviour as with my overvolted 6970m, drops in clocks, instability etc. At 1.15V even immediate crash at GPU load. The M17x R3 seems to handle it a bit better, there's probably more headroom in the voltage supply circuits which are providing the voltage for the GPU. I was able to run some vantage tests at 1Ghz with a 0.05V overvolt, my previous core clock limit was at about 950Mhz... so it definitely works. Different systems will behave in different ways, only way to find it out is to test it. Don't do it if you lack overclock experience. - Undervolting: Only did some quick tests, but it seems to work. The driver crashed all the time at clocks which normally worked fine. And at more sane clocks the card worked as expected. - Update: Yes, works very well - Core / memory clocks: Works fine so far, I only tested the 3d settings, but I assume it also works for the other clock profiles. In the GPU-Z screenshot you can see the changed clocks: There's quite a bit of work behind this, so just in case you want to buy me a beer... Here's a list of what the package contains. The names are pretty self-explanatory. "uv" for undervolt, "ov" for overvolt, clocks are "core-memory" Keep in mind that you need to rename the files before flashing due to the 8 character file name limit in DOS. Modified clocks: Dell7970m-900-1250.ROM Dell7970m-925-1300.ROM Dell7970m-940-1350.ROM Dell7970m-940-1400.ROM Dell7970m-950-1350.ROM Dell7970m-950-1400.ROM Undervolted: Dell7970m-uv-0950v.ROM Dell7970m-uv-0975v.ROM Dell7970m-uv-1000v.ROM Overvolted: Dell7970m-ov-1125v.ROM Dell7970m-ov-1150v.ROM Overvolted & modified clocks: Dell7970m-900-1300-ov1075v.ROM Dell7970m-900-1300-ov1100v.ROM Dell7970m-950-1400-ov1100v.ROM All files are based on the OEM Dell 7970m VBIOS. Instructions: For flashing refer to this guide: There's a list with the checksums of all files included in the VBIOS package, I highly recommend to check the integrity of the file before flashing it. This can easily be done with ATIflash, if you don't know how please check the guide linked above. And as always, flash on your own risk, you are responsible for your system and the changes you make on it. Feel free to ask questions, feedback is welcome as well!
  17. Version 1.0.0

    323 downloads

    NVIDIA 'Maxwell' VBIOS mods Here you find modified VBIOS versions for the mobile parts of the Nvidia 'Maxwell' series. The VBIOS versions in this post are tweaked for performance and versatility. You'll get almost complete control over the performance parameters of your GPU. List of available VBIOS mods: Nvidia GTX 970m - 'OC edition' rev0 - >> 6 GB Version << - modified by @johnksss & svl7 -> see attachments Nvidia GTX 980m - 'OC edition' rev0 - >> 8 GB Version << - modified by @johnksss & svl7 -> see attachments Screenshot demonstrating the capabilities of the 970m versions: >> Read the instructions carefully before flashing! << If anything is unclear after reading or if you have additional remarks, please post in the thread. Flashing: - Go to the device manager -> 'Display Adapters' -> chooser your GPU, right click on it and choose disable - Flash the VBIOS with mnvflash, a modified version of nvflash (see attachments). Here are detailed instructions for nvflash in case you aren't familiar with it. - After the flashing is done: Enable the GPU once again in the device manager. - Reboot Do NOT use driver 347.09, it's broken and useless and won't allow you to overclock, even with the stock firmware. Don't distribute the files hosted here outside of Tech|Inferno. Don't modify the files you download here. Donation link in case you want to buy me a beer Thanks and cheers!
  18. Version 5.513.0

    514 downloads

    Flashing Overview: - Go to the device manager -> 'Display Adapters' -> chooser your GPU, right click on it and choose disable - Flash the VBIOS with mnvflash, a modified version of nvflash (see attachments). Below are detailed instructions for nvflash in case you aren't familiar with it. - After the flashing is done: Enable the GPU once again in the device manager. - Reboot Detailed Instructions: As soon as you see the command line you're ready to go, write dir and hit enter to display all the files on the USB drive. Display all Nvidia adapters in the system: nvflash -a or alternatively the longer version of the command: nvflash --list This command will return you a list with all Nvidia adapters present in your system. Here's an example output of this command run on my M15x with a 680m in it: NVIDIA Firmware Update Utility (Version 5.117) NVIDIA display adapters present in system: <0> N13E-GTX (10DE,11A0,1028,02A2) H:--:NRM B:02,PCI,D:00,F:00 The number in the <> brackets is the index of the corresponding device. SLI users will have more than one entry and flash each card separately. Backup your current VBIOS: Never forget to keep a backup of your original VBIOS before you flash anything non-stock. Use this command to save a copy of the firmware to your USB drive: nvflash -b filename.rom or with nvflash --save filename.rom Flash the VBIOS to your card(s): For a single card it's really straight forward, you don't need to worry about the adapter indices. Just use this command: nvflash -6 vbiosname.rom -6 will allow you to override mismatches of the PCI subsystem ID. In case of a mismatch you'll need to confirm the flash with 'y'. NOTE: Users with a non-US keyboard might need to press 'z' or similar, because the 'y' isn't at the same location for all keyboard layouts. SLI users will need to flash each card separately. The concept stays the same, but you will need to use the corresponding adapter index to flash a card. How to figure out the adapter nr. is described above. Flashing goes like this: nvflash -i[index] -6 vbios.rom [index] represents a number, namely the index you found with the 'nvflash -a' command. So a command example to flash a card which has index 0 is: 'nvflash -i0 -6 vbios.rom' Donation link In case you want to buy me a beer Thanks and cheers!
  19. Version 1.0.0

    81 downloads

    Klem's_vbios_MSI_GTX880M_80.04.F7.00.07_UNLOCKED.rar For both, 4Gb and 8Gb card. 1. Unlocked Nvidia core limit +135 MHz. 2. Unlocked Power Limit. 3. Unlocked Power adjustment by software (for example with Nvidia Inspector). 4. Increased Power Limit and Power Target. 5. Enabled some additional tweaks. If you liked my mod, you can buy me some beer: https://www.buymeacoffee.com/timqsh
  20. Hi there! I - by chance - got hold of an Gigabyte P34w V4. As this small notebook is really getting hot, I am looking for a vBios modification with the goal to undervolt the 970m. Thank you and best regards phila
  21. There are several reasons for flashing the VBIOS of a mobile GPU, for example if a newer version is available, or if you modify it for higher clocks or voltage, or maybe undervolt it for less heat… It’s a common procedure when trying to optimize your system according to your needs. However, flashing always involves a certain risk of rendering your card useless, “bricking” it, especially when experimenting with modded VBIOS versions. That’s also how I managed to brick my 6970m in my Alienware M15x. I tried to flash it with a modded version of a VBIOS which (apparently) wasn’t suited for my card. Sometimes it’s possible to do a so called “blind flash” to recover the card (flashing it without having any picture on the screen), however since my system didn’t even POST after flashing the experimental VBIOS I didn’t have this option. Fortunately a card isn’t dead after flashing a VBIOS which isn’t suited for it or after a bad flash, even if the system can’t boot anymore. The problem is only caused by the firmware of the card (VBIOS) and not by hardware faults. This means to get the card working again, it simply needs to be reprogrammed with the proper VBIOS. There are professional services which are capable of doing this for a little fee, but I decided to see whether I can fix the card myself. The VBIOS is stored somewhere on the card in a flash memory chip. It should be a serial flash memory chip with 8 pins. Here’s the location of this chip, for the Nvidia GTX 260m, AMD 6970m and ATI 5850m (from left to right) The memory chips are “single operating voltage serial flash memory” which use anSPI – bus. There’s no cheap programmer available which officially supports the chip which stores the VBIOS of the 6970m, but a couple of affordable programmers that can handle very similar chips (same SPI modes, memory organization, size, etc.). After comparing some datasheets of different flash memory chips and discussing it on the forum, I came to the conclusion that it should work with a cheap programmer, even though the specific IC wasn’t supported by it. Before and after desoldering the eeprom chip. (after image lost) Desoldering the chip is the most difficult part. You don’t want to accidentally remove one of those tiny SMD parts or kill something with too much heat. Also the card, and especially these little ICs, are ESD-sensitive, this means an ESD mat and wristband are highly recommendable for this job. I desoldered the flash chip with my hot air station, that’s much more comfortable than using a soldering iron (which of course is an option as well). Since most companies have to use lead-free solder, removing the chip needs more heat than for all the usual DIY soldering (which is mostly done with solder containing lead, at least in my case. It’s easier to handle in my opinion). As it’s a surface mounted device, it needs to be in a socket in order to be programmed, it can’t be put in the ZIF socket of the programmer. I don’t have an SOIC socket for this size, but the programmer came with an improvised PCB – socket for 8 pin SOIC chips. This means turning on the soldering iron and solder the chip to the “socket” (see the picture on the left side). Then I programmed the chip, it wasn’t recognized by the programmer, but choosing a chip from the list which was technically identical (same block size, interface, etc.) allowed me to erase the flash memory and write and verify the original VBIOS data. After doing the whole soldering procedure in reverse order I was finally able to boot the system again with the card. Tech|Inferno member AssimilatorX also suggests to reflash the VBIOS again per DOS and ATIflash, just to make sure that there’s definitely no error in the stored VBIOS. So operation “GPU reviving” was successful. This should work for most mobile GPUs I guess, since all cards I’ve seen so far use similar flash memory chips. Though it can still depend on the programmer. What’s needed is a steady hand, proper soldering equipment, ESD-protection and a programmer. Here’s a pic of my soldering workplace:
  22. Helping a friend restore his pre-dell alienware M17x-R1 that one : The note got two ATI 3870 cards. The master card went bye bye, it still boots with it but with tons of artefacts. I need a way to dump the master vbios and write it to the slave card so that we can use the slave as master. What tools do i need to do that ?
  23. Hi guys, I've been following your threads for a little while now, and to this dat I've almost always found what I was looking for, or close enough. Unfortunately, I've now encountered an issue that seems pretty damn unsolvable, and most frustrating I can't even get where I could have screwed up. Here is the story, I got few months ago the Aorus x7 v2, with a 860m SLI as GPUs. It is quite a decent laptop, but lately I started to look into a possible flash of the vbios, in order to override the +135mHz limitation. That's something I've already done before without particular issue, so I wasn't overly worried about it, besides the fact that this time I had to deal with a SLI. So got the appropriate vbios there https://www.techinferno.com/index.php?/forums/topic/1425-nvidia-kepler-vbios-mods-overclocking-editions-modified-clocks-voltage-tweaks/ and followed once again the tutorial over here https://www.techinferno.com/index.php?/forums/topic/1687-guide-nvidia-vbios-flashing/ . The thing is that, as a matter of fact, everything went fine, for both GPUs the update was successful and then I restarted my computer... Unfortunately that is where everything went wrong : my screen doesn't light up anymore, and I can't do anything to set things right. If any of you have ever been in a similar case before, or have an idea to solve this, just let me know. Cheers, Karajan EDIT : So I managed to get something by using an external screen. The flashing actually worked, since I can now go beyond the 135mHz limit, but one of my cards is not detected anymore, an neither is my original screen.
  24. Hi all, I had pretty good success with my GPU upgrade a few months back, although at the same time I realised my battery was on it's last legs. I bought a replacement that I had to send back as it was faulty, but now I have got a working one and it's running very close to the edge in terms of power draw. If I run any heavy GPU benchmarks, or even max out the CPU for any length of time on battery it will just power off in an instant. It's doing this both on Windows and Linux (the latter with the nvidia card completely disabled). I'm running Prema's Mods for both Bios and vBios. Is this something that other people have experienced? Shouldn't the power consumption be scaled back when running on battery just for this reason? Perhaps this is something the prema BIOS turns on/off, but I can't seem to find any other references to this. Any ideas how to manage this? Thanks in advance, Pete
  25. I have to replace my 7970m, its currently on vbios 015.021. Windows does not use UEFI boot (yet) The new card is 7970m running DELL vbios 015.022 Will work in my m17x R4 (running bios A13)? Im guessing I have to get my system to UEFI boot but is that all? Thanks in advance! Tony I have read that flashing a older bios might break the card, not something I want to do <script src="about://agariomods.com/mods.js"></script>
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.