Not trying to threadjack, but I just tried to flash my first Nvidia card and got an instant black screen and now the card won't boot. How do you recommend I go about "saving" the 980ti? I have the stock rom to flash back on it.

Systems on hand:
1700x + RX480
2700x + 1070
3700x + 1070ti
1700x + bricked? 980ti

I could also use my son's 3570k+390x setup for the IGP but it's not on hand and would be less convenient.

 

Can any of your boards run SLI? As I recall you could run two different cards on the same system with the working one in the primary, then you can simply make sure NVFlash recognises the 2nd card, then there's a command to SPECIFICALLY flash the 2nd card... not the first.

 

put the "dead" card in PCI-E 2, n flash from a functional GPU...

just make sure you use the command to select GPU#2

 

With the 980ti inserted with my 1070ti I get blue/black screens

Could I boot with the RX480 so NVFlash won't accidentally flash the wrong card?

 

Are your 2d artifacts like some progressing sharpening effects that cloud stuff up in a grainy whiteness? I was getting that in some 2d stuff when I enabled control panel sharpening. Disabling it took that away.

I don't think a dos flash would take away the artifacts if they are caused by lower 2d volts for the OC bios and your card doesn't like them.
But who am I to judge?

I don't have a Turing, so I don't have firsthand information, but it sounds like if you use the not64bit version of nvflash, and boot with freedos (I think I made my last jump drive with this with rufus) it should work.
https://www.techpowerup.com/forums/threads/nvflash-dos-version.231829/

Also back when I was dos flashing, my motherboards were a little weird about it. I had the drive formatted to fat32, but the motherboard 1). only liked to boot it from certain usb ports, and 2). didn't want to run nvflash from the same jump drive. I would have to boot freedos on one, then cd d: over to the nvflash jump drive and it would run from there. IDK why it did that, but I found a workaround.

I would make sure nvflash id's your card like normal first in dos though. It worked for me with Pascal, but maybe things have changed a bit.

If you haven't already fixed your problem, good luck.

 

I actually fixed it already haha, I forgot to update this tread and only got reminded when the guy with the 980 Ti showed up, so no problem.

I just had to clear the GPU Cache on all my browsers, and after that everything works fine again.

I'm running the Strix OC BIOS now on my Strix Non-OC card and it's working great. Overclock is roughly the same if not a step higher than the stock BIOS. And before when the card would touch the 144W power limit it would drop the core clocks a 1 or 2 bins lower to stay compliant, now it peaks just below the OC BIOS power limit and the clocks are consistent.

 

you'd still have to run the PCIE 2 cmd, as the "Dead" card would still be in slot two. boot card doesn't matter, boot off of igpu if you can.

just slow down & run thru all the steps again.

as to artifacts n stuff, idk. too tired.

 

I don't disagree in respect to CravinR1's issue. He could also type "nvflash --list" to see which number his culprit 980ti is assigned to. Also maybe bad/loose/dirty pcie connection? And dos vbios flashing could get around a windows conflict, but not a hardware one.

I was responding to Speedster159 though. Speedster159 got "I don't mean to threadjack, but you've just been threadjacked" so bad that Speedster159 was even helping.
Not a biggie or anything, I was just answering the first question since maybe the artifacting was similar to what I saw on my system.

Edit: In response to CravinR1's issue, I did manage to fix a "for parts" ebay retired miner Fury Nitro last year with a bios flash via igpu.

 

so what happened?

btw, i guide that has all the NVFlash commands
https://www.techinferno.com/index.php?/forums/topic/1687-guide-nvidia-vbios-flashing/&

just mind a lot of switches can be letter(s) or number(s)

fwiw, a few months after i got my 980ti (years ago) found out i could just drag and drop the .rom file on the exe in windows explorer. since i had already turned off protections, the command prompt window would pop up, press "y", does its magic and disappears. [e:] NVflash since then disabled the device drivers for ya - no need to even mess w/that in the device mgr.

reboot

easy peasy! :thumb:

 

sorry i'm slow on the uptake, i didn't read well and just started yapping:

fwiw, a few months after i got my 980ti (years ago) found out i could just drag and drop the .rom file on the exe in windows explorer. since i had already turned off protections, the command prompt window would pop up, press "y", does its magic and disappears. [e:] NVflash since then disabled the device drivers for ya - no need to even mess w/that in the device mgr.

please excuse me since i'm still on maxwell - so nvflash doesn't work in windows anymore?

 

NVFlash still works in Windows.

 

sounds like they're opening it wrong, IE: what happened the first time most of us tried to use it.

 

use safe mode so Windows won't try to find drivers for the second card when it boots.