Premiere pro fried my graphics card (NO... known bad card)

First off let me just start by saying, im most definitely sure this could end in a lawsuit with Adobe and nvidia. I am not the only one this exact situation happened to.

So I originally had a 3,000 dollar pc, which started to really slow down after a year but before that worked buttery smooth with premiere pro. It eventually got to the point where I got rid of that pc and got a brand pc through NZXT the most expensive one you could get for around 5,000 dollars, 4090 graphics card, 64 gb ram, an amazing motherboard, and an i9 processor with a water cooled cpu. Then not even two weeks in boom, had lag problems, would get the not responding error EVERYTHING I dealt with on my previous pc, on the new one and I had it for not even two weeks. But here's the catch now two months down the line, I don't know if premiere pro and nvidia just aren't getting along anymore or what, but I see both companies to blame here, now my graphics card is fried, and i have talked to 4 other people that this same exact thing has happened to either once or twice, We receive an error from premiere quoting "hardware error" and then after that our screen starts flashing uncontrollably even after we turn the pc off and back on again. 

and before you ask YES I have been on the phone with Adobe four different times have had them take over my computer it will be good for maybe a day, and boom it's back to the same problem.

I recommend Adobe and nvidia figure out something soon here before it makes a big problem for both companies. Your talking thousands of dollars of peoples money for that one component because either Adobe or nvidia whoever it is can't get they're things together, but I put both companies to blame here. My 5,000 power house of a pc should not feel like a snail in premiere pro and cause my graphics card to fail, and nvidias graphics card shouldn't be failing that fast especially being one of the newest graphics card they have released. 

but AS I SAID I am not the only one who this same exact issue has happened to, and the other people have all different types of graphics cards so whose to blame here? I'm putting bets on Adobe.