Question Game Fried GPU -- Need Advice on Bios Flash

[Pandawaffle]

I played the new Jump Ship Demo and it ruined my GPU–I was not the only one. Now any game that pushes the GPU to 100% usage crashes within minutes. So I am on a quest to restore the card to how it worked a week ago.
The first thing I tried was DDU & fresh installing the latest drivers. This did not fix the problem.
The next step I have been looking at is to flash the GPU’s bios. I haven’t done this before and I hear this process can backfire, so I wanted to be sure I have prepared correctly:
The card in question is an NVIDIA GeForce RTX 2070, I have attached an image of its readout on GPU-Z.
I have saved a copy of the current bios using GPU-Z.
I downloaded NVIDIA flash from TechPowerUp and copied the x64 version to a folder on my C drive.
I have downloaded this bios from TechPowerUp to flash it with.
The main source I followed was this video.
My mobo does have onboard graphics which I can fall back on in case this fails.
Can I get some feedback on wether this seems like a rational step and if I have prepared correctly?

Spoiler: Example Crash Error Logs

DrvSetContext failed functionality indeterminant
(pid=18812 cncmd.exe 64bit)

Faulting application name: helldivers2.exe, version: 1.8.32436.0, time stamp: 0x6846ab7b
Faulting module name: ntdll.dll, version: 10.0.26100.4061, time stamp: 0x1d4ecf98
Exception code: 0xc0000026
Fault offset: 0x000000000008fcbf
Faulting process id: 0x4BBC
Faulting application start time: 0x1DBDA75EA42D6E6
Faulting application path: L:\Program Files (x86)\steamapps\common\Helldivers 2\bin\helldivers2.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 4eecb306-5294-4c01-a03d-68d8814ccdc4
Faulting package full name:
Faulting package-relative application ID:

https://imgur.com/a/u95b8sh

 

[CountMike]

I played the new Jump Ship Demo and it ruined my GPU–I was not the only one. Now any game that pushes the GPU to 100% usage crashes within minutes. So I am on a quest to restore the card to how it worked a week ago.
The first thing I tried was DDU & fresh installing the latest drivers. This did not fix the problem.
The next step I have been looking at is to flash the GPU’s bios. I haven’t done this before and I hear this process can backfire, so I wanted to be sure I have prepared correctly:
The card in question is an NVIDIA GeForce RTX 2070, I have attached an image of its readout on GPU-Z.
I have saved a copy of the current bios using GPU-Z.
I downloaded NVIDIA flash from TechPowerUp and copied the x64 version to a folder on my C drive.
I have downloaded this bios from TechPowerUp to flash it with.
The main source I followed was this video.
My mobo does have onboard graphics which I can fall back on in case this fails.
Can I get some feedback on wether this seems like a rational step and if I have prepared correctly?

Spoiler: Example Crash Error Logs

DrvSetContext failed functionality indeterminant
(pid=18812 cncmd.exe 64bit)

Faulting application name: helldivers2.exe, version: 1.8.32436.0, time stamp: 0x6846ab7b
Faulting module name: ntdll.dll, version: 10.0.26100.4061, time stamp: 0x1d4ecf98
Exception code: 0xc0000026
Fault offset: 0x000000000008fcbf
Faulting process id: 0x4BBC
Faulting application start time: 0x1DBDA75EA42D6E6
Faulting application path: L:\Program Files (x86)\steamapps\common\Helldivers 2\bin\helldivers2.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 4eecb306-5294-4c01-a03d-68d8814ccdc4
Faulting package full name:
Faulting package-relative application ID:

https://imgur.com/a/u95b8sh

Unless that new BIOS has some change that prevents that from happening, there's no use flashing sane one again.
It's highly unlikely that any game OR OS can change anything in GPU BIOS, It's more likely you have problems with overheating due to the age so you may want to undervolt it for now until that can fixed. Once it starts overheating it just gets worse fast.
When updating/flashing BIOS most important is to match it with VRAM type even for same GPU make, they often change VRAM even for same model.

 

[Pandawaffle]

Unless that new BIOS has some change that prevents that from happening, there's no use flashing sane one again.
It's highly unlikely that any game OR OS can change anything in GPU BIOS, It's more likely you have problems with overheating due to the age so you may want to undervolt it for now until that can fixed. Once it starts overheating it just gets worse fast.
When updating/flashing BIOS most important is to match it with VRAM type even for same GPU make, they often change VRAM even for same model.

I've monitored GPU-Z when I crash and it consistently has my average GPU temp ~68*C and the hottest spot on the GPU being 80*C. So I don't think its overheating--also because those errors seem to be memory related. I did run memtest just to be sure and it's not my RAM.
I am seriously convinced it was the game because I started having the issue only after playing it and numerous other people have reported similar issues.
If not the bios -- what other part of the card could have been corrupted by the game? I am looking for ways to reset the card to how it was a week ago assuming a piece of software somehow corrupted it.

 

[Ralston18]

Simply stop playing the "demo".

The link you included used the word "beta". Basically a software test version that is provided to those who are willing to take the risks of code that is not ready for general release and use.

You are the proverbial testing "guinea pigs".

Hopefully there will be a viable fix for you and others affected.

Unfortunately if the version did indeed "brick" the GPU to where the GPU is no longer fully operational then there is not much that you can do.

Likely all somewhere in the EUA's fine print etc. that you, by default, accepted when you downloaded, installed, and ran the game's software.

And be wary of any fixes you may come across. They could make matters worse.

 

[Tolis_GR]

It could be just a coincidence and your psu is just giving up, especially if you stressed it with an unoptimized game, maybe you can try your gpu in another system first