P770DM-G prema vBios Board ID mismatch

So I've tried to flash prema's vbios before for the 980m-gsync but kept getting some sort of error. I was too busy troubleshoot the error back then but now I'm at it again. So after trying again I got this message:

ERROR: Board ID mismatch

Did a quick search on the internet and didn't find anything so I thought I'd ask around first before bothering Prema. If anyone could help it would be appreciated.

I've tried Prema's GTX980M-G_8GB_MXM_DM_OC_PM_v2 vbios and the old version that I still had.

I added a screen shot with HWIDs and the error:

 

That's a ZM revision card (same thing can be used in DM/ZM, but it needs a different vBIOS).
Use the GTX980M-G_8GB_MXM_ZM_OC_PM_v2 version v2 vBIOS.

 

Yes you have to be really careful to get the right BIOS/VBIOS to prevent ending up with a brick

 

I contemplated about allowing nvflash to cross-flash for a while and only have as single version for ZM and DM, but then people would start cross-flashing all kinds of other stuff and brick things in the process.
So finally decided that it is safer to just offer two vBIOS versions, so that nothing can go wrong.

 

Sensible idea, if you had the ignore command on the flasher it could lead to a lot of bricked systems

 

@Prema Thanks for the response. Its just I read something similar in the comments section of your vBios page. The persons's user name was DM and he tried using the ZM vbios and ended up not getting any signal to the monitor (you mentioned something about his bios being old and left a link to a bios) and had to reflash blind to stock. Eventually he set it in for service so I don't know if he managed to get the modded vbios working. So I'm just wondering if that might happen to me also. I got the PC back in november and haven't updated the bios at all.

 

He was hoping to get g-sync by cross-flashing his card with another version of nvflash and bricked the card...

Don't worry, just use the supplied packages and make sure you see the VERY BRIEF successful message at the end before rebooting and you will be fine.

 

success!! confirmed with nvidia inspector. Thank you Prema. hopefully I can get a good overclock with my 83% asic card

 

Wait, why would flashing a different 980m vBIOS brick your GPU, but crossflashing a 970m on a 980m wouldn't and vice versa (I believe that's what you told me via email a while back? Unless I am mistaken, or you mean a soft brick? I would love any insight about this - your information is always excellent and highly appreciated.

 

In the OPs case they used a ZM-G model GPU in a DM-G model system, so he couldn't use the DM-G vBIOS. Those cards could also be cross-flashed.

Flashing a 970M to 980M or doing anything along the lines bricks it.
If you flash a g-sync vBIOS to the same model non-g card will not brick but card, but the DM system BIOS will detect the attempted fraud and in return disable all video out-put. An entirely useless feature as the driver would't allow you to use g-sync even if you would still have screen output.

 

I m the DM man. Firstable there is a idea from prema: my modded nvflash always flash if the gpu true. thats wrong. I read a few days ago a guy flashed the g version on non g system and dear prema's flasher allowed it. I didnt any cross flash because dm version never completed and after reboot I flash the zm bum. if you want to save your card. dont reset cmos because if u loose your uefi boot option your windows never able to boot because its return the legacy. guess how many people save their cards? zero.
https://www.techinferno.com/index.p...oot-blind-flash-a-non-booting-gpu-in-windows/
when the flash completed zm-g and prema's perfect flasher I didnt see a succesful message but the cmd screen closed it self. I didnt see any error msg. if you come there dont reboot man just dont. my warranty is perfect but I dont know yours. I respect prema and all of his works but I asked some questions when my device come back I want to be sure flash again safety is there a different flasher expect for the vbios folder because its not safe for flash again. He never answer my questions

 

As much as I can understand that you are searching for someone to blame, it is NOT possible to cross-flash any GPU with my NVFLASH:

Spoiler

The only way my NVFALSH would allow that is if someone already cross-flashed the GPU BEFORE using my version...in that case you could't even use the proper vBIOS version any longer as again it would NOT allow us to cross-flash it back.
A cross-flash requires to ignore the board ID and I haven't enabled that in NVFLASH.

There are dozens of people that are using blind-flash to recover from certain bricks. @Mr. Fox alone did it 3 times in the last 2 days...
Usually people without problems just don't post.

------------------------------------------------------------

Some reseller are selling their systems with my work without permission and then sending their customer to me for support.
Other devs, that I never even heard of, making ******** claims behind my back, that I would be using their work.
The donations from the public free mods is close to zero while the downloads are in the 100k region...
I even have people whom I shared non-public mods with for free not even saying 'thank you', hacking my branding out of the BIOS and start posting as if its their own effort.

I have literary thousands of unanswered PMs & mails from people that EXPECT service for something that they grabbed for free...
My gmail has crossed it's 15GB free limit with emails alone...I am trying to help wherever I can, but it's not an easy task.

 

I get it man. just I wanted to trust flash again I said I respect you and works but nobody shouldnt brick device like me I want this. Mr.fox, the moderator has a prema bios right? and if he do cmos reset can you save his gpu blind and legacy? there is a post here your nvflasher:
ok I cant find the link but you know about gtx 970m and 970m g version. why mr.fox brick his device and eject the bios battery and save his card on a video and you maybe add this video your recovery topic. People believe you and I believe you but they are afraid.
If I said something to upset you I m so sorry man.

 

Mr. Fox is always busy testing the next generation of Mods...

If the Windows was installed in EUFI and did a CMOS reset, then the user would have to blindly re-enable the same in BIOS before proceeding with the blind-flash.
That is indeed a problem on old systems (all current ones default to UEFI) as that key combo would be different for each system/BIOS.
For those user a legacy Windows live boot usb would be the better solution.

And please don't take the things I wrote personal, it has very little to do with you.
There is just a lot more behind the scenes I have to deal with to be able to make these mods possible for you guys...why do you think svl7 left the scene after releasing his last vBIOS with brick code...surely not because people appreciated the hard work he did.

 

okay man but you know this is necessery. some people maybe save their gpu and alot of like me couldnt. if anybody got time enough to do this please say them. a working video guide would be nice. I will try again your vbios if I can be little more calm. whatever happens if I failed can we save my device together ha?

 

Holy ****, did not know it was this bad. Isnt it possible to encrypt the BIOS mods so that they cant be opened in any modding tools without decryption ?
I know Sony does something similar with their BIOS.

 

By bricking a 980m or 970m by cross-flashing the opposite vBIOS do you mean soft-brick (can be blind-flashed back to working again) or do you mean hard-brick (requires desoldering/replacement/etc)?

Damn, people are so ****ty I can't believe it. That's why I'm very glad I was able to donate a decent amount of money to you over the past year or two for all the help and useful things you have provided me. I would have no qualms if you made your mods paid-only but then people might end up leaking them, I dunno...

Just know there are tones of people in this community who appreciate everything you do.

 

Yes Nvidia have learned not to leave portions of the core actually still there, also trying to activate part of the memory bus that does not exist will never go well.

 

Damn, people. I'm always very glad to donate for thing I use. Without people like you... Forget high performing laptops!!

 

The thing is people buy the laptops and expect a level of service from the reseller (this is reasonable) then they expect the work of people like Prema to be covered under that (this is not reasonable).

This is why I always remind people to at least leave some beer money if I point to it, but people tend to just take these things and then complain about it.

It's the same reason I did not release details of the hardware mod to increase memory voltage, people would break things and then expect me to fix it.

 

Wow @Prema Makes me want to go donate just for the hell of it, and I haven't even used your Bios yet.

Actually headed there now to make a donation just because i can, and i know I will eventually use your BIOS


**** Sent

 

He is a nice guy to have around for the community that's for sure

 

Prema is King.
One of the best guys i ever met online! One of these days i will pay him a trip to my country just so we can go out and drink some beers!

 

That sounds like a fun meet up

 

So, what is the big difference if any between a ZM and DM card? is one better than the other?

My card says device ID 10DE-1618 , So what VbioI use? Neither the ZM or DM say they match so I'm not willing to even attempt t.

 

It is impossible for the bundled flash package to flash the wrong version...so no worries.
Either way try the DM-G version first if you have a DM system and ZM-G if you are a ZM system owner.

 

OK, I used the DM version, and it said saving and writing, then went blank and came back. So I assume it worked. GPU-Z does not show anything different. how do I know it completed properly?

 

After a reboot check the vBIOS revision, the Mod is named 'C1' for 'Clevo One'!
Use NVIDIA Inspector for OC.

 

Revision says A1

 

If that is after a reboot then it didn't flash.
Disable driver manually (some driver don't play nice) and repeat the flash.
Make sure you see the VERY brief message to reboot after the flash, before actually rebooting.
Then again re-enable the driver manually in device manager on the next fresh boot.

 

Still shows Revision A1, after it says its saving and writing, i see it say verifying and the rest happens too fast to see what its saying before the cmd window disappears.

 

A1 is the board revision, check the bios revision, it should read 84.04.88.00.C1. Check the picture. Maybe that is the problem? Now I have the 970M but you should see .C1 on your bios version.

 

Prema, you are an amazing fellow with talents I could only dream of having. Thank you for your hard work.

 

Sweet, yup it worked. Thanks @steberg @Prema

 

Send Prema a donation, I'm sure he will appreciate it! The least you can do for all his hard work!

 

I totally agree. Already did before I even used his BIOS.

 

A good advice!! Rep added