• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

Can't override PCI Subsystem ID with -6

videovillain

New Member
Joined
Jan 5, 2020
Messages
5 (0.00/day)
Hello all,

I'm really stuck right now. I am trying to revert my vbios for my GTX 980m but I keep getting this issue:

image.thumb.png.f21e49368c2528528cbdd20ed70958bd.png

Any thoughts?
Here is the comparison:

image.png.098cbb243191e307eda7f0bf9320e4f6.png

I originally did the opposite, replacing the 84.04.67.00.11 with the 84.04.2F.00.79 with no issues.
But now that I am going back, it will not let me.

Thank you all for your help!
 
If anyone knows anything it would sure be helpful!

Extra info in case it is useful:
  • The 84.04.2F.00.79 VBIOS is the available one from techpowerup's collection
  • The 84.04.67.00.11 VBIOS is the original from my Sager P870DM-G laptop with dual SLI GTX 980m
  • Neither .rom has been altered by me at all.
 
You are probably going to have to contact Sager to get the laptops original bios and flash that. Laptops are really picky when it comes to bios, most are all in one and when you change it sometimes does not want to go back.
 
You are probably going to have to contact Sager to get the laptops original bios and flash that. Laptops are really picky when it comes to bios, most are all in one and when you change it sometimes does not want to go back.
Pretty likely tho Sager if anyone would be less likely to use OEM specific BIOS as most others do.
 
You are probably going to have to contact Sager to get the laptops original bios and flash that. Laptops are really picky when it comes to bios, most are all in one and when you change it sometimes does not want to go back.
I have the original bios though, would it be different coming from Sager? I doubt it since I backed up the VBIOS when I first got the computer.
And flashing it shouldn't be an issue as long as the PCI subsystem ID mismatch would simply be ignored right? Could this be a hardware thing? Like, should I move the GPU to a different slot and force the PCI ID to be re-initiated? I could try that but I'd rather not because it would involve removing the heat-sink and then reapplying the thermal paste, etc.
 
Something changed the subsystem ID, which is why it is failing. The bios is looking for that specific id and it fails because it cannot find it in the system. So either the bios changed it or you did by accident when you did the flash. I am sure someone here has done laptop flashes before, maybe @eidairaman1 can help. But your best bet is contact Sager and follow what they say. I guess a better question to ask is, is the laptop currently running the way it is? If it is running fine with the other bios, I would leave it alone.
 
We are not responsible for bricking.

Use this

If it doesnt work then use this

Or this
 
If it doesnt work then use this

YUSSS!!!!!! This one worked with -6 after using --protectoff

Awesome, thank you so much!


I guess a better question to ask is, is the laptop currently running the way it is? If it is running fine with the other bios, I would leave it alone.
It didn't work at first but I finally got it working, but there were two cards and after turning SLI back on, it was getting some wonky issues and some games couldn't run anymore, so I needed to flash one to the other. I figured going back to the original was the best option.


The whole purpose of this was because the computer kept shutting down at 92C for one of the cards and I noticed that one card had it's temp limit set to 101C and the other at 92C and I wanted to make them both 101 somehow.

So now I'm back to square one with that, but at least they are both back to the original bios! YAY!

Thanks everyone!
 
I am gravedigging this thread due to having the same issue and being unable to resolve it.

I have downloaded the apps above but no luck as documented below.

Background-

I flashed the vbios of Alienware a51m on my rog zephyrus gx701gxh. Both laptops have rtx2080 max-q, although the a51m has higher clock speeds hence this unfortunate experiment.

After flashing the vbios, the gpu does not get detected regardless of how many times i try to reinstall the drivers.
Device Manager reports Code 43, Dxdiag says that the GPU has been turned off by windows. Nvidia control panel does not even startup when I try opening it.
I thus need to revert to previous vbios.

At first GPUZ returned this result (doesn't this mean that the system DOES recognize the GPU?):
1619759012822.png


After trying to update the nvidia drivers (from 466.11 to 466.26) to see if things would change (they didn't), GPUZ does not identify the GPU anymore:
1619759075453.png


Upon trying to flash the previous vbios, i receive an ID mismatch error.

So i downloaded the nvflash64 version that ignores mismatched GPU IDs: https://www.techpowerup.com/download/nvidia-nvflash-with-board-id-mismatch-disabled/
Then i ran the -6 command;
Result was still GPU mismatch:
1619759179698.png


Even if i try running the --protectoff command and then the -6 command the same as above happens;

Any way to overcome this?

Thanks in advance!
 
Upon trying to flash the previous vbios, i receive an ID mismatch error.
Then i ran the -6 command;
Result was still GPU mismatch:

You messed up SUBSYS ID and device ID (1e90 vs. 1ed0)
You would need a yet older NVFLASH version that supports -5 (--overridetype), but idk if these older versions can flash Turing.
 
how to use it? TPW only offers win10 version to download
Hello all,

I'm really stuck right now. I am trying to revert my vbios for my GTX 980m but I keep getting this issue:

image.thumb.png.f21e49368c2528528cbdd20ed70958bd.png

Any thoughts?
Here is the comparison:

image.png.098cbb243191e307eda7f0bf9320e4f6.png

I originally did the opposite, replacing the 84.04.67.00.11 with the 84.04.2F.00.79 with no issues.
But now that I am going back, it will not let me.

Thank you all for your help!

 


Ше
This version was made at jan 31 2020, when 30xx series (ampere) was not around at all. So even if it works with older models such as 9xx, 10xx 20xx series - no joy on latest hardware.
 

Attachments

  • 1629687868900.png
    1629687868900.png
    8.8 KB · Views: 515
  • 1629688160279.png
    1629688160279.png
    6.6 KB · Views: 574
has anyone found a version of NVFlash with -5 command (non DOS/UEFI) that works for RTX 20xx ?
 
There was one with ID checks bypassed for AMPERE which was posted in some buried thread here a few months ago, to allow laptop users to crossflash to a higher TDP Bios of the same family.
Based on 5.670.0. I can't find the original thread or discussion however.

 
There was one with ID checks bypassed for AMPERE which was posted in some buried thread here a few months ago, to allow laptop users to crossflash to a higher TDP Bios of the same family.
Based on 5.670.0. I can't find the original thread or discussion however.


Hi, this version doesnt work either, "GPU missmatch"

tested on RTX 3060

does anyone have a source code of nvflash?
 
has anyone found a version of NVFlash with -5 command (non DOS/UEFI) that works for RTX 20xx ?
Hey man, if you're still having trouble with flashing it back with NVFlash, you might need to try hardware flashing it instead. Look for the SPI chip on your GPU board, check if that's supported by Flashrom, and use a CH341 and the right clip to flash the BIOS. It's how people flashed modified notebook BIOSes because the system blocks unsigned firmwares from being flashed in software.
 
Hi, this version doesnt work either, "GPU missmatch"

tested on RTX 3060

does anyone have a source code of nvflash?
use -A or else try different bios

Hey man, if you're still having trouble with flashing it back with NVFlash, you might need to try hardware flashing it instead. Look for the SPI chip on your GPU board, check if that's supported by Flashrom, and use a CH341 and the right clip to flash the BIOS. It's how people flashed modified notebook BIOSes because the system blocks unsigned firmwares from being flashed in software.
just try using "nvflash -A bios.rom"
This version looks vanilla to me byte0by-byte but still works.
There was one with ID checks bypassed for AMPERE which was posted in some buried thread here a few months ago, to allow laptop users to crossflash to a higher TDP Bios of the same family.
Based on 5.670.0. I can't find the original thread or discussion however.

 
Last edited:
use -A or else try different bios


just try using "nvflash -A bios.rom"
This version looks vanilla to me byte0by-byte but still works.
-A does the same error, GPU Device ID mismatch,

i am gonna try to patch this last nvflash to bypass the Device ID checker

finally ive patch the 5.670.0 to bypass the Device ID

successfully downgraded 2504 to 2503

1631129439580.png


but now the driver doesnt detect it (470.05)
remain as generic display adapter

updates will follow...
 
-A does the same error, GPU Device ID mismatch,

i am gonna try to patch this last nvflash to bypass the Device ID checker

finally ive patch the 5.670.0 to bypass the Device ID

successfully downgraded 2504 to 2503

View attachment 216043

but now the driver doesnt detect it (470.05)
remain as generic display adapter

updates will follow...
10DE:2503 > RTX 3060 Normal (Mining Rate unlocked)
10DE 2504 > RTX 3060 LHR (Mining Rate Limited)

Even both is RTX 3060 but is different revision Chip, and consider both is different card, you cannot cross flash both card BIOS
 
@morphyx could you share the patched version of nvflash?

Also have a rtx3060 and versions I found so far dont work. Just want fan-stop on the card.
 
Back
Top