one thing is for sure EVGA has some great marketing, if this was some other brand all the Ytubers has already jumped on this. Only Jayz did a video to blame the game lol

jaketeck
Interesting. These boards have shunt resistors and power monitoring all over the place. I suspect that there may be a path that doesn't have power monitoring and that this game somehow maxes that path which leads to the failure. I'm reading through the entire thread now, has anyone inspected the failed cards yet?
 

StanJarensky3
For what it's worth, RTX 3080 owners are also reporting this. I had something very similar happen to me while playing FFXIV on my 3080 FTW3 Ultra so I'm assuming it's a similar problem. Theoretically, setting a maximum FPS globally should stop whatever application/game from drawing obscene amounts of power during unlocked loading screens, right? I'm about to RMA my 3080 to EVGA today but in the meantime, I'll be setting a global FPS cap to my monitor's maximum refresh rate. 

 
I think my 3080 was having a similar issue when playing RE:Village 

Ok this is going to be messy.
 
I keep trying to tell people this but not many people listen to me.  But the few who do actually go "hmm...interesting."
There is MORE than one power limit on the card, boys.
Not only that, the shunt resistors only shunt the INPUT RAILS that are fed from the main power rails to the main chips.
However there are more shunt resistors than there are main input rails.
On an 2x8 pin card, there's
 
1) 8 pin #1
2) 8 pin #2
3) GPU Chip Power (CPU Core NVVDD Input Power (sum))
4) PCIE Slot Power
5) MVDDC (FBVDD) / memory power
6) PWR SRC (Power Plane Input Source Power)
 
Shunt #6 is bizarre because the SRC chip not only has its own power limit (Most cards set this to 150W at 100% TDP slider and 175W at whatever TDP is the max slider position, which then becomes normalized past 100% to scale from 150W to 175W), but the SRC actually has several of its own power limits which equal the # of 8 pins (!).  The SRC power limit controls the maximum power that can be pulled from an 8 pin.  This is DIFFERENET from the individual 8 pin power limits!  The individual 8 pin power limits combined with PCIE Slot Power control the TDP VALUE when you add them.  The SRC value however does NOT.  The SRC value controls the max allowed from an 8 pin before a "TDP Normalized%" power throttle happens.
 
Even more bizarre is that the SRC power rail itself changes depending on the power coming from all the other shunts.  If you do a shunt mod and you shunt a rail with poor soldering and bad contact, SRC may show LESS watts at full load than at idle.  It can actually end up showing 0 watts at full load.  This may also cause MVDDC (memory power) to also show 0 watts at full load.  If you fail to shunt SRC, it may end up reaching its own power limit and throttling the entire card (VIA TDP Normalized%) or it can cause another rail to skyrocket (not a true reading btw) e.g. causing 8 pin #1 to report 175W and 8 pin #2 to report 80W, which triggers another power limit.
 
And these are just the shunts.  There are more sub-rails, SOME of which when "summed" together, add up to one of the primary rails, and some which report only to "TDP Normalized" and are not exposed via NVAPI (but might be accessible via I2C with Elmor's EVC2X).  All of the "Input" rails shown in HWinfo64 (both primary and secondary) respond to shunt mods.  None of the "Output" rails respond to shunt mods.  However MSVDD, NVVDD and PLL power rails also do not respond to shunt mods but ARE reported to TDP Normalized based on a "default" and "maximum" value.
I'm not talking about voltage rails.  I'm talking about the main power rails themselves which feed them.
 
MSVDD drawing too much power relative to what MSVDD voltage is supposed to allow will report a high "TDP Normalized" power draw (with respect to TDP%) and cause GPU effective clocks to drop, relative to requested clocks.  NVVDD drawing too much power relative to what NVVDD voltage (this is internal voltage, not VID--MSI Afterburner only supports setting VID) caused outright Power limit throttle by TDP normalized (without effective clocks dropping first).
 
Here is what MSVDD's unreported power limit does to TDP Normalized.
 
Path of Exile: 400W TDP (Shunt mod: Slider set to 58% TDP).
 
1) Shadows + Global Illumination Quality: High.  TDP=400W, 58% on TDP slider)
(Notice TDP Normalized %, TDP%, board power draw and the clocks).
 
https://i.imgur.com/FLAITFL.png
 
2) Shadows + GI = Ultra (TDP = 400W, 58% slider)
https://i.imgur.com/joz3YCc.png
 
Notice the difference in clocks and TDP Normalized, even though total board power remains the same.
 
3) Shadows + GI : High, 800W TDP, 150 mhz core, windowed, TDP=114%
 
https://i.imgur.com/pO3sPMg.jpg
 
4) Shadows + GI: High, 800W, 150 mhz core, fullscreen, TDP=114%
 
https://i.imgur.com/C853Rg5.png
 
5) Shadows + GI High, 800W TDP, 90 mhz core, fullscreen, TDP=114%
 
https://i.imgur.com/nUnQJC7.png
 
6) Shadows + GI: Ultra, 800W TDP, +150 core clock (danger!), TDP=114%
(Fullscreen).
 
https://i.imgur.com/EmvAsiD.png
 
I couldn't run this very long.  I've black screened + 100 % screaming fans before from doing this at that TDP unless I lowered the clocks.
 
7) Shadows + GI: Ultra, 800W TDP (windowed), TDP=114%
https://i.imgur.com/0yWpWTM.png
 
Please compare the TDP Normalized difference between the windowed Ultra and High tests.
 
Notice that on the Ultra tests, the clocks and voltages are being throttled due to a high TDP Normalized even though total TDP is nowhere near 114% (hovering around 87% or so).
But look in hwinfo.  Only the VID (NVVDD) is being throttled.  SRAM voltage (MSVDD) is not being throttled.  1.013v NVVDD Vs 1.094v MSVDD.
 
TDP Normalized starts throttling the clocks when any individual rail (in this case it's the unreported MSVDD / NVVDD rails!) exceeds 108%.  It starts mildly throttling the clocks.
 
Superposition 4k custom / Timespy Extreme has had TDP Normalized go up to 119% with some massive clock throttling.  However neither of these programs managed to black screen 100% fan the shunt modded FE Card (at most it just crashes the driver).
 
But POE + Ultra + 800W TDP has managed to hard crash the power phases (past 90 mhz core clock overclock) because the MSVDD rail just gets overloaded with the power draw going way past 600W with temps past 75C.  Card didn't die though but it was scary.
 
What I'm curious of is if New World is doing something similar.  If it is, TDP Normalized should be able to report something being way higher than it should.
 

elvnmagi
So is there a way they could update firmware to put a ceiling on that draw by default?  Or are you saying it's not reporting properly so it can't be fixed to throttle properly for default settings and therefore will always be weak to specific game engine/dev code induced stress scenarios?

You can't.
It's like furmark.
Notice when you run furmark, the clocks throttle a large amount even though the power draw is maxed?
Have you tried renaming furmark.exe to UnrealTournament.exe?
 
(please don't do this if you value the life of your card.  I don't even know if this works anymore.  It DID work in windows XP drivers).

elvnmagi
someone on the reddit thread for this .. in r/neworldgame "Did the New World Beta brick your gpu?" ..  vaguely recalled that this happened when starcraft 2 was released back in 2010 so I looked it up:
 
( from bit-tech dot net  august 3, 2010 )
 
 StarCraft 2 doesn't limit framerates

"StarCraft 2 is apparently causing overheating issues on some systems, literally frying graphics cards thanks to the lack of a framerate cap in some areas of the game. Fortunately, Blizzard has issued a temporary fix for the problem until a patch can be rolled out via Battle.net.

According to the problem occurs at the main menu, where the lack of a framerate limit allows hardware to max out, potentially failing permanently.

"Certain screens make your hardware work pretty hard," Blizzard said via its .

"Screens that are light on detail may make your system overheat if cooling is overall insufficient. This is because the game has nothing to do so it is primarily just working on drawing the screen very quickly."

Blizzard's current solution is to tell customers to go to Documents\StarCraft II Beta\variables.txt and add the following lines, replacing the final integers with the desired value.

frameratecap=60
frameratecapglue=30

Some fans have voiced outrage that such a big and obvious bug, one potentially capable of destroying entire systems, slipped through to the release version. As Dailytech points out though, Blizzard isn't entirely to blame and even a maxed out GPU will only overheat that quickly if it already has cooling problems. "

this wasn't starcrafts fault, the driver corresponding to the game had a fan stop bug on upgrade installs that wasn't present for new installs.
 
https://www.zdnet.com/art...ll-your-graphics-card/
 

the_Scarlet_one

Meguas2
 Software shouldn't be able to kill GPUs, so it's not new world.  GPUs should be able to work at 100% load without their OCP tripping or even worse blowing fuses.  This is going to come down to either Nvidia's OCP not being fast enough to catch spikes or some other flaw imho.  But I won't jump to conclusions as people that know a lot more than I do about this subject will do their investigations and we will find out.

Have you ever heard of Furmark? Did you know furmark, a software, was KNOWN to kill GPU’s?

only because the power delivery was substandard for the requirements of the total board power usage.

Governator
I've read through this entire thread and found it to be very interesting to say the least, curious if this has affected anyone who's water cooling.

considering one of the videos was a Hybrid, figure it out.

Governator

squall-leonhart

Governator
I've read through this entire thread and found it to be very interesting to say the least, curious if this has affected anyone who's water cooling.

considering one of the videos was a Hybrid, figure it out.

Sorry, I should've been more specific I was referring to full coverage custom loops, active backplates etc.

wouldn't make a difference, the component blowing isn't touched by any blocks and its a excessive current event not a thermal one.

I watched the livestream today and they patched it. They were playing it on a 3090 FTC 3.

RogueMaster

Jlc015
I watched the livestream today and they patched it. They were playing it on a 3090 FTC 3.

Which stream, and who patched what?

The only patch I'm aware of is for NW, and all that was done was to limit framerates in menu screens, unless that changed since yesterday.

Serious question, BTW..  I have a 3090, and my brother is wanting me to play with him. I don't dare go near it without a little more certainty that I'm not going to fry the card.
 

You shouldn't be worried. Your card is gonna fry sooner or later. The sooner the better IMO, unless EVGA were able to create a software patch or RMA every customer in case the fix couldn't be done via software patch. As I said before EVGA need to properly address this issue or another game in the future will inevitably fry FTW3 3090s

@roguemaster, EVGA Weekly, Jacob said that the new New World patch fixed it, and they played for a while. No issues with the fps spiking and they ensured that they were doing RMA's for those affected.

Well after watching that video, it seems to me it was indeed the game causing the issue and they have patched it BUT it was causing the problem due to some sort of manufacturing defect in the EVGA card.

tyranus7

Jlc015
@roguemaster, EVGA Weekly, Jacob said that the new New World patch fixed it, and they played for a while. No issues with the fps spiking and they ensured that they were doing RMA's for those affected.

So EVGA is blaming the game? oh my god, lol... well good luck in the future to those with a FTW3 3090

Blame game? oh stahp!

well i mean the game is the thing that patched and it got fixed, so, i feel like its the games fault, but i havnt been able to score a 3090 yet. Got a 3070 ti. Missed the step up window i guess. I think step up for 3090 is a long wait anyways right?

There is nothing wrong with the game. Maybe your card got worked over?

 
i have a rtx 3090 ftw ultra. I constantly have no more pictures on the monitor and the fans run at 100% .. sometimes I can play new world for 5 minutes, sometimes it runs for 15 minutes. after that my pc always starts normally
I have the same bug with GTA 5.
It's certainly not the game itself. What can I still do with this scrap card, should I return or will this error be fixed again at some point? It's just ridiculous, I'll never buy EVGA again. 

And from something I spotted on Twitter here ya go>  https://www.youtube.com/watch?v=rpvsaedeeqg