#EVGA PRECISION X CRASHING GPU DRIVERS#
#EVGA PRECISION X CRASHING GPU FULL#
#EVGA PRECISION X CRASHING GPU SERIES#
#EVGA PRECISION X CRASHING GPU WINDOWS#

#EVGA PRECISION X CRASHING GPU WINDOWS#

The game’s executable tossed out a D3DDRED2 error, which caused Windows to spawn a LiveKernel 141 (generic hardware component failure) event. Brad Chacos/IDGĪfter letting the crash sort out, I popped open Microsoft’s Event Viewer to see what errors occurred. Precision X1 revealed that at that moment, the GPU clock speed hits 2025MHz, then plummets when the game locks up. About two-thirds of the way into the benchmark, there’s a scene where the camera swoops through a courtyard filled with people. Popping open EVGA’s excellent Precision X1 software, I found that the benchmark mostly ran at 2010MHz, and worked just fine while doing so.

#EVGA PRECISION X CRASHING GPU FULL#

(Our GeForce RTX 3080 review includes full test system details.) Other games work fine even HZD works fine at 4K but it always crashes at 1440p, and so hard that it takes out GPU-Z, too.Īs affected users have said in multiple forum posts, the crashing appears tied to the GPU clock speed. On the all-POSCAP FTW3, using Nvidia’s original 456.38 drivers, the Horizon Zero Dawn benchmark consistently crashes at 1440p resolution on our test system. My pre-production EVGA FTW3 comes packed with POSCAPs and nary an MLCC module in sight, unlike the models you can actually buy. But after all the ruckus I decided to poke at my pre-production POSCAP sample to see if I could get it to misbehave reliably. I’d shelved reviewing this FTW3 because EVGA told me they’d be shipping me a new one that matches the configuration buyers received. And yes, I could get it to crash repeatedly while gaming. The cards you can buy should be fine.īut what do you know: I just so happen to have one of those early pre-production FTW3 samples with six POSCAPs. They delayed the card to include an MLCC array to ensure stability. To be absolutely clear in case you missed it: EVGA is not shipping FTW3 cards with an all-POSCAP setup, which couldn’t pass real-world testing.

#EVGA PRECISION X CRASHING GPU SERIES#

EVGA GeForce RTX 3080 XC3 series with 5 POSCAPs + 10 MLCC solution is matched with the XC3 spec without issues.” There were no 6 POSCAP production EVGA GeForce RTX 3080 FTW3 boards shipped.īut, due to the time crunch, some of the reviewers were sent a pre-production version with 6 POSCAP’s, we are working with those reviewers directly to replace their boards with production versions. It took almost a week of R&D effort to find the cause and reduce the POSCAPs to 4 and add 20 MLCC caps prior to shipping production boards, this is why the EVGA GeForce RTX 3080 FTW3 series was delayed at launch.

“During our mass production QC testing we discovered a full 6 POSCAPs solution cannot pass the real world applications testing. (Again, read our RTX 3080 crashing guide to learn the difference between POSCAP and MLCC capacitors.) Here’s what product manager Jacob Freeman said in an EVGA statement: EVGA’s hotly anticipated RTX 3080 FTW3 graphics card was delayed because the original configuration exclusively used POSCAP capacitors potentially tied to the crashing issues. If you read our guide to the RTX 3080 crashing issues, you’ll know that EVGA somewhat confirmed Igor’s analysis that the type of capacitor used can affect performance. The EVGA RTX 3080 FTW3 cards you can buy include different capacitors than my pre-production version you can see it includes MLCC arrays between the black, rectangular POSCAPs on the rear of the GPU. The graphics card that never launched EVGA

#EVGA PRECISION X CRASHING GPU DRIVERS#

The new 456.55 Game Ready drivers indeed puts an end to that, but it looks like it does so by slightly limiting the maximum GPU Boost clock speed. I have a custom GeForce RTX 3080 brimming with an 1all-POSCAP configuration that reliably crashed in Horizon Zero Dawn with the older, original 456.38 drivers.

Evga precision x crashing gpu