4080 nvflash board id mismatch error

[Ntme9]

Hello, I have a MSI 4080 Ventus OC and I am trying to flash the msi trio bios to it, but I keep getting this error. I have tried 10+ different bios including a one-month older (October) bios for the EXACT same model card and keep getting this error. Only the identical (November) bios for this card will push through. Anyone got any ideas? Thanks

OK solved, two things to try if you run into this. Check to make sure the SKU and the compile date of the bios you are using is as close as possible and also power down your computer for a few minutes after you disable the gfx card in device manager. Then power back up and give the bios with the matching SKU a try.

 

[Siman00]

Getting the same thing... even with the -6 command that's supposed to override the flag, guess the programmer messed it up again... I can't get anything to flash over regardless of date... I really wish they would remove the damned protection on nvflash, if people are flashing the bios they already have accepted the chance to brick the GPU... I like it asks if you want to override it and then it doesn't do it...

WARNING: Firmware image PCI Subsystem ID (19DA.1688)
does not match adapter PCI Subsystem ID (10DE.167A).
WARNING: None of the firmware image compatible Board ID's
match the Board ID of the adapter.
Adapter Board ID: 0431
Firmware image Board ID: 0432

You are intending to override PCI Subsystem ID.
Are you sure you want to continue?
Press 'y' to confirm (any other key to abort): y
Overriding the PCI Subsystem ID mismatch.

NOTE: Exception caught.
Nothing changed!



ERROR: Board ID mismatch.

 

[Don1376]

Getting the same thing... even with the -6 command that's supposed to override the flag, guess the programmer messed it up again... I can't get anything to flash over regardless of date... I really wish they would remove the damned protection on nvflash, if people are flashing the bios they already have accepted the chance to brick the GPU... I like it asks if you want to override it and then it doesn't do it...PG139 SKU 360 VGA BIOS

Same cards? We believe we found the problem with Ntme9's issue. He finally got it to flash. There's a PG139 SKU 360 VGA BIOS that's the one on my card and there's a PG139 SKU 362 VGA BIOS that's a month newer and matched the one on his card. You can run "nvflash 64 --version" to find out if you have the 360 or 362 bios. I believe he said he found the 362 bios in the unverified bios section on TPU. It doesn't come up on a regular search. Hope this helps.

And the protection is there for a reason. It may have just saved you a card.

 

[eidairaman1]

Just cool it, nothing to gain from bios flashing your shiny new toys other than a big headache, the tool is there telling you to stop doing it.

 

[Don1376]

Just cool it, nothing to gain from bios flashing your shiny new toys other than a big headache, the tool is there telling you to stop doing it.

I gained plenty from it and it's part of the hobby. I don't remember seeing anywhere where they told me to stop doing it. Why would they offer the software and bios database to do it. Sounds like someone is a bit jealous maybe.

 

[eidairaman1]

I gained plenty from it and it's part of the hobby. I don't remember seeing anywhere where they told me to stop doing it. Why would they offer the software and bios database to do it. Sounds like someone is a bit jealous maybe.

Nope, I just handle 95% of bios recovery ops here.

 

[Siman00]

Just cool it, nothing to gain from bios flashing your shiny new toys other than a big headache, the tool is there telling you to stop doing it.

I verified the date or the project id is the same, 360. The chip SKUs are also the same. TBH I don't care if it gets bricked or not, that's also a part of why I'm doing it... My thing though I guess comes from my Unix background. The administrator should have the say regardless of the possible outcome. The damning thing for me is the check and it still doesn't do it. If it's not going to do it why then put the check in the code...

 

[Don1376]

Nope, I just handle 95% of bios recovery ops here.

That's pretty cool, and thank you for your time and effort you put in doing so. Is having to help so many with bios recoveries what caused you to be so salty about trying to flash a bios on one's own card instead of trying to assist? I have never found it to be a headache with any of my cards I've flashed. Only like 5 or 6. It's always gave me satisfaction in doing so, I've learned something new every time, and I get a little more out of the money I spent for my shiny new toy. If I brick it, it's my own fault. If I were to do so and I asked for help, you don't have to help if it upsets you or causes you a big headache. I mean no disrespect, I just don't understand your first comment on a forum that's here for people to ask for help, when none of it is totally true.

I verified the date or the project id is the same, 360. The chip SKUs are also the same. TBH I don't care if it gets bricked or not, that's also a part of why I'm doing it... My thing though I guess comes from my Unix background. The administrator should have the say regardless of the possible outcome. The damning thing for me is the check and it still doesn't do it. If it's not going to do it why then put the check in the code...

Sorry, was hoping that would work for you. My ventus 3 took the 360 SKU no problem. The suprimx and triox bios files both flashed without a problem for me.

 

[the54thvoid]

In the past, certain vendors released cards that could benefit hugely from BIOS flashing (I e. Kingpin cards from EVGA, I owned one).

I think the member didn't think there was a substantial benefit from flashing BIOS on the cards you mentioned. I'd imagine the Ventus has a weaker power limit, and possibly weaker VRM. Therefore flashing would yield insignificant improvements.

Our of curiosity, what improvements have you gained?

 

[phanbuey]

so since turing they've disabled the ability to flash lower power limited card variants to higher ones. There were 2 versions of the 2080ti - the A1 and A2 and nothing i did would allow me to flash the a2 version beyond a certain power limit. You may have to keep looking to see if some board partner like palit released a higher wattage bios for your board, unfortunately.

It's an artificial lock, but I was never able to figure out how to bypass it ( I did find a better bios eventually though.)

 

[Colddecked]

In the recent past, bios modding (maxwell, polaris, 1st gen navi) and flashing (pascal) gave decent gains, but cards now are pretty much maxed out and respond better to uv/oc anyways. But again, if people understand the risks and are experienced in flashing, and bricking their 1300+ dollar cards for ~5% performance gains compared to manual oc/uv is an acceptable risk, the more power to them.

 

[Don1376]

In the past, certain vendors released cards that could benefit hugely from BIOS flashing (I e. Kingpin cards from EVGA, I owned one).

I think the member didn't think there was a substantial benefit from flashing BIOS on the cards you mentioned. I'd imagine the Ventus has a weaker power limit, and possibly weaker VRM. Therefore flashing would yield insignificant improvements.

Our of curiosity, what improvements have you gained?

For one piece of mind because my card isn't limited at 320watts and can run as a card that, at time of purchase, would of been an additional $200. My card now boost to max 3090mhz, average 3060mhz while staying under 66c. Instead of little over 2700mhz like it was before. Just very easily gave it an additional 50watts to play with and I'm pretty sure it'll last just fine for the year I own it, if I own it that long. I know it's a overpriced card, no doubt, I like new tech, and enjoy overclocking even if for minimal gains. I'm very happy with it and only cost me $350 out of pocket for it, after selling my 3090 with waterblocks for $950. This card is way faster, overclocks way better, runs at same max temp my 3090 on water did, and using 80 less watts doing so. I feel it was a worthwhile flash. Made me happier.

I basically gained an additional 200mhz over prior OC, and it now boosts higher having a little extra power available. Don't feel like doing the math to see what % that is, it's late.

 

[Don1376]

About a 7% gain from flashing.

 

[Colddecked]

About a 7% gain from flashing.

Good to see flashing still gives that extra bit of free performance. The good thing is that there's usually a way to recover your card, they are tough to brick. Nowadays just more interested in efficiency and making things last longer but always good to know the option is still available.

 

[eidairaman1]

In the past, certain vendors released cards that could benefit hugely from BIOS flashing (I e. Kingpin cards from EVGA, I owned one).

I think the member didn't think there was a substantial benefit from flashing BIOS on the cards you mentioned. I'd imagine the Ventus has a weaker power limit, and possibly weaker VRM. Therefore flashing would yield insignificant improvements.

Our of curiosity, what improvements have you gained?

I could understand flashing a cheaper card but these no, 7% is not worth it, tell me when there is say a 20% gain. And on another note majority coming here didn't know wtf they were doing and shouldn't be doing it to begin with. The only fool proof way to flash any gpu is by using a SPI flasher.

The addage is: IF IT AIN'T BROKE DON'T FIX IT

 

[Don1376]

I could understand flashing a cheaper card but these no, 7% is not worth it, tell me when there is say a 20% gain. And on another note majority coming here didn't know wtf they were doing and shouldn't be doing it to begin with. The only fool proof way to flash any gpu is by using a SPI flasher.

The addage is: IF IT AIN'T BROKE DON'T FIX IT

Agree, but nvflash is pretty good about not letting you flash a wrong rom file. Not that you can't with all the modded versions out there. I know what I'm doing and know how to use SPI flash. I use to recover bricked car ecus using SPI. And 7% gain, was worth it to me. I'd do it even for less because I enjoy just being able to do it. I do agree though, if you don't have any knowledge or experience flashing it's not worth trying.

 

[eidairaman1]

Agree, but nvflash is pretty good about not letting you flash a wrong rom file. Not that you can't with all the modded versions out there. I know what I'm doing and know how to use SPI flash. I use to recover bricked car ecus using SPI. And 7% gain, was worth it to me. I'd do it even for less because I enjoy just being able to do it. I do agree though, if you don't have any knowledge or experience flashing it's not worth trying.

Amdvbflash is extremely good at stopping someone from flashing too lol. Anyways some cards get so buggered up that SPI is the only way

 

[SagerDanger]

Sneaking in here to see if I can piggy back...

Ages ago I bought a Sager NP9873, with GTX 1080 MXM. That card supported G-Sync, and the laptop screen is G-Sync. The card died, and I managed to get my hands on another GTX 1080 MXM, buttttt this one doesn't support G-Sync, even though I was guaranteed it would.

It came with this vBIOS:
86.04.56.00.2E

I flashed this one:
86.04.2A.00.2D

And low and behold, G-Sync was enabled and worked fine! But, I had an error where my mem clock was locked at 405mhz, so with some (read as a ton) of trial and error, I was able to flash back to the OG vBIOS. It didn't recognize the mem as GDDR5X from Micron, but all of the GTX 1080 MXM's use GDDR5X from Micron, sooooo...

Sager actually sent me a cute little list of the vBIOS's for these cards, and which ones are G-Sync compatible.

​	P870DM2/3(-G)	P870KM1	P7XXDM2/3(-G)	P870TM	P750TM
GTX 1080	86.04.2A.00.2C	86.04.56.00.2E	86.04.2A.00.2A	86.04.80.00.20	86.04.80.00.23
No G-Sync			86.04.39.00.1B
			86.04.56.00.29
GTX 1080-G	86.04.2A.00.2D	86.04.56.00.2D	86.04.2A.00.2B	86.04.80.00.21	86.04.80.00.24
Yes G-Sync			86.04.39.00.1C
			86.04.56.00.2A

My actual laptop model is the P870DM2/3(-G), hence why I tried to flash 86.04.2A.00.2D. BUT the new card is 86.04.56.00.2E, which is a P870KM1, so I am convinced that 86.04.56.00.2D will work, BUT I CAN'T GET IT TO FLASH UGH.

I have tried:
NVFLASH 5.590 PATCHED
NVFLASH 5.792
NVFLASH 5.287
NVFLASH Simplified for OEM for Sager, it was 5.2 something or other
And on all of these I have tried virtually every combination of turning protection of, -A, -4, -5, -6, and -r.

Any advice would be appreciated.