Overclock.net - An Overclocking Community - Reply to Topic
Thread: How To Flash A Different BIOS On Your 1080 Ti. Reply to Thread
Title:
Message:

Register Now

In order to be able to post messages on the Overclock.net - An Overclocking Community forums, you must first register.
Please enter your desired user name, your email address and other required details in the form below.
User Name:
If you do not want to register, fill this field only and the name will be used as user name for your post.
Password
Please enter a password for your user account. Note that passwords are case-sensitive.
Password:
Confirm Password:
Email Address
Please enter a valid email address for yourself.
Email Address:

Log-in


  Additional Options
Miscellaneous Options

  Topic Review (Newest First)
01-18-2020 11:53 PM
doomsdaybg
Quote: Originally Posted by KedarWolf View Post
To fix the Chrome issue I had to delete all the Chrome folders in Program (x86) and the appdata local and roaming folders, then reinstall Chrome.
I have same problem with reflashing BIOS and black screen in Chrome, but only delete one folder here: AppData\Local\Google\Chrome\User Data and delete ShaderCache folder. Black screen gone, and all other stuff is safe. At least this worked for me with no losing anything.
01-17-2020 10:30 PM
KedarWolf
Quote: Originally Posted by kithylin View Post
I had this issue too. I flashed to the FTW3 bios on my 1080 Ti just recently (yay higher stable overclock!) and I just edited the chrome shortcut to put: --disable-gpu at the end after the " and it works fine.

This is confusing because despite what the word is I still see gpu utilization in chrome (with this flag on) when browsing script-heavy websites and specifically when watching youtube in 4K I see the video core portion of the GPU get utilized too.

So it doesn't actually disable gpu acceleration.. but it works for me. I tried DDU and everything.

From what I think with my long years experience with windows (I'll date myself here.. my first computer ran MS-DOS before windows 1.0 existed.. I still have it in the other room) I believe modern windows some how "Bonds it's self" to what ever driver you first install in the OS after a clean install. And then once you run on that install nothing can completely remove it. Not even DDU. DDU only removes the portions of the driver that won't conflict with other installs but something deep inside windows still keeps portions of the first driver package you first installed when you first loaded the OS on the computer somewhere. I haven't tried it yet but I suspect the only way to get this "chrome black screen" issue to resolved is to completely re-install windows. Which I won't be doing for a long time unless necessary.. I just did that the week after black friday 2019 with my ryzen build.
To fix the Chrome issue I had to delete all the Chrome folders in Program (x86) and the appdata local and roaming folders, then reinstall Chrome.
01-17-2020 10:27 PM
KedarWolf
Quote: Originally Posted by kithylin View Post
Unfortunately we can not flash any bios back to the cards that has been modified in any way. Nvidia doesn't allow it and to the best of my knowledge (I may be wrong here) but no one has cracked a way to do this with software yet. We're only cross-flashing bios's from other cards that have different attributes right now. Either they don't know how to crack it by now or just no one cares because the 1000 series are "Old Cards" now.
You can flash back to your card's original BIOS and even 'lock' the BIOS again so it looks like it was never ever modified. Somewhere in the thread I wrote instructions exactly how to do it.
01-15-2020 05:34 PM
kithylin
Quote: Originally Posted by ylpkm View Post
Thanks for replying. Welllll sheeeuuut... I already had to reinstall windows like 4 times in the past 2 months due to hardware upgrades, testing Raid 0 (wasnt worth raiding ssd's on ryzen, infact it hurt my read performance quite a bit, even with cache enabled) and unstable ram overclocks (which I learned to use a throwaway ssd install to test so I don't lose whole instances).

I was actually thinking something similar to your thoughts. Maybe either windows or the nvidia drivers check the card info and if there is a mismatch between bios details and physical hardware, it borks. So maybe a reinstall could remedy it, or maybe modifying the rom to say its still a gigabyte aorus, gigabyte board/model etc, or maybe a checksum issue? (guide to adjust checksum values:http://www.xtremesystems.org/forums/...-bios-checksum).
Unfortunately we can not flash any bios back to the cards that has been modified in any way. Nvidia doesn't allow it and to the best of my knowledge (I may be wrong here) but no one has cracked a way to do this with software yet. We're only cross-flashing bios's from other cards that have different attributes right now. Either they don't know how to crack it by now or just no one cares because the 1000 series are "Old Cards" now.
01-15-2020 04:30 PM
ylpkm
Quote: Originally Posted by kithylin View Post
I had this issue too. I flashed to the FTW3 bios on my 1080 Ti just recently (yay higher stable overclock!) and I just edited the chrome shortcut to put: --disable-gpu at the end after the " and it works fine.

This is confusing because despite what the word is I still see gpu utilization in chrome (with this flag on) when browsing script-heavy websites and specifically when watching youtube in 4K I see the video core portion of the GPU get utilized too.

So it doesn't actually disable gpu acceleration.. but it works for me. I tried DDU and everything.

From what I think with my long years experience with windows (I'll date myself here.. my first computer ran MS-DOS before windows 1.0 existed.. I still have it in the other room) I believe modern windows some how "Bonds it's self" to what ever driver you first install in the OS after a clean install. And then once you run on that install nothing can completely remove it. Not even DDU. DDU only removes the portions of the driver that won't conflict with other installs but something deep inside windows still keeps portions of the first driver package you first installed when you first loaded the OS on the computer somewhere. I haven't tried it yet but I suspect the only way to get this "chrome black screen" issue to resolved is to completely re-install windows. Which I won't be doing for a long time unless necessary.. I just did that the week after black friday 2019 with my ryzen build.
Thanks for replying. Welllll sheeeuuut... I already had to reinstall windows like 4 times in the past 2 months due to hardware upgrades, testing Raid 0 (wasnt worth raiding ssd's on ryzen, infact it hurt my read performance quite a bit, even with cache enabled) and unstable ram overclocks (which I learned to use a throwaway ssd install to test so I don't lose whole instances).

I was actually thinking something similar to your thoughts. Maybe either windows or the nvidia drivers check the card info and if there is a mismatch between bios details and physical hardware, it borks. So maybe a reinstall could remedy it, or maybe modifying the rom to say its still a gigabyte aorus, gigabyte board/model etc, or maybe a checksum issue? (guide to adjust checksum values:http://www.xtremesystems.org/forums/...-bios-checksum).
01-15-2020 01:53 PM
kithylin
Quote: Originally Posted by ylpkm View Post
Flashed Gigabyte 1080ti Aorus 11g to the FTW3kingpinfix and upon rebooting chrome shows up as a black box. I ran the power limit.bat right after flash and it updated the value. After reboot, I tried to reapply and it says unable to pull power limit for gpu XXXXXX. stopping due to previous errors. So I DDU and reinstall, same thing. I try to flash the Strix rom, same chrome issue. Reflash back to F3P(what I had before) and the power limit bat runs fine and chrome runs fine. Reflash back to FTW3kingpinfix, both issues are back. I remove the driver, and windows automatically installs 432.00 (driver version in device manager 26.21.14.3200) this lets me run the power limit bat, but chrome is still black, starting chrome with --disable-gpu lets me use chrome.

Has anyone had this issue? Know of any fixes that would let me run chrome with hardware acceleration and be able to use the newest drivers?
I had this issue too. I flashed to the FTW3 bios on my 1080 Ti just recently (yay higher stable overclock!) and I just edited the chrome shortcut to put: --disable-gpu at the end after the " and it works fine.

This is confusing because despite what the word is I still see gpu utilization in chrome (with this flag on) when browsing script-heavy websites and specifically when watching youtube in 4K I see the video core portion of the GPU get utilized too.

So it doesn't actually disable gpu acceleration.. but it works for me. I tried DDU and everything.

From what I think with my long years experience with windows (I'll date myself here.. my first computer ran MS-DOS before windows 1.0 existed.. I still have it in the other room) I believe modern windows some how "Bonds it's self" to what ever driver you first install in the OS after a clean install. And then once you run on that install nothing can completely remove it. Not even DDU. DDU only removes the portions of the driver that won't conflict with other installs but something deep inside windows still keeps portions of the first driver package you first installed when you first loaded the OS on the computer somewhere. I haven't tried it yet but I suspect the only way to get this "chrome black screen" issue to resolved is to completely re-install windows. Which I won't be doing for a long time unless necessary.. I just did that the week after black friday 2019 with my ryzen build.
01-15-2020 10:36 AM
ylpkm Flashed Gigabyte 1080ti Aorus 11g to the FTW3kingpinfix and upon rebooting chrome shows up as a black box. I ran the power limit.bat right after flash and it updated the value. After reboot, I tried to reapply and it says unable to pull power limit for gpu XXXXXX. stopping due to previous errors. So I DDU and reinstall, same thing. I try to flash the Strix rom, same chrome issue. Reflash back to F3P(what I had before) and the power limit bat runs fine and chrome runs fine. Reflash back to FTW3kingpinfix, both issues are back. I remove the driver, and windows automatically installs 432.00 (driver version in device manager 26.21.14.3200) this lets me run the power limit bat, but chrome is still black, starting chrome with --disable-gpu lets me use chrome.

Has anyone had this issue? Know of any fixes that would let me run chrome with hardware acceleration and be able to use the newest drivers?
01-11-2020 12:46 PM
bernek I dont run into power limits ... what is this "FTW3 KingPin Fix BIOS" ?
01-11-2020 07:54 AM
bernek
Quote: Originally Posted by KedarWolf View Post
Lightning Z BIOS will brick your card and unless you have a second GPU or onboard video you won't be able to flash it back.

Only the AMP Extreme BIOS in OP works with normal cards, all other AMP Extreme BIOS's don't work right.
Thanks !

Can you tell me what Kingpin FIX FTW3 has that regular FTW3 doesnt ? or what is the difference ?

I'm on EVGA FTW3 now... This one: https://www.techpowerup.com/vgabios/...i-11264-180309

L.E. flashed it myself looking for differences
01-11-2020 02:58 AM
KedarWolf
Quote: Originally Posted by bernek View Post
I know that but thanks for trying to help. I'm saying that the vcore doesn't "comply" with what I set for a specific point. Anyway I've decided to try quite a few other bioses and see what works best in my scenario.

So far tested ASUS XOC, ASUS STRIX, EVGA FTW3 ... plan on testing Lightning Z and Zotac AMP Extreme (this one has the highest power allowance from all except XOC).

Offtopic:

One annoying thing that I can't be sure of that I've found so far is some annoying microstuttering but I think its related to GSYNC and GPU Scaling somehow ... (I use both rendering at 3264x1836 upscaling to 4K). 1080TI in this case is not the perfect 4K candidate so I have to render lower res then upscale to 4K. I've tried display scaling and works but Sharpening works best with GPU scaling.
Lightning Z BIOS will brick your card and unless you have a second GPU or onboard video you won't be able to flash it back.

Only the AMP Extreme BIOS in OP works with normal cards, all other AMP Extreme BIOS's don't work right.
This thread has more than 10 replies. Click here to review the whole thread.

Posting Rules  
You may post new threads
You may post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off