News Posts matching #Crash

Return to Keyword Browsing

RTX 3080 Crash to Desktop Problems Likely Connected to AIB-Designed Capacitor Choice

Igor's Lab has posted an interesting investigative article where he advances a possible reason for the recent crash to desktop problems for RTX 3080 owners. For one, Igor mentions how the launch timings were much tighter than usual, with NVIDIA AIB partners having much less time than would be adequate to prepare and thoroughly test their designs. One of the reasons this apparently happened was that NVIDIA released the compatible driver stack much later than usual for AIB partners; this meant that their actual testing and QA for produced RTX 3080 graphics cards was mostly limited to power on and voltage stability testing, other than actual gaming/graphics workload testing, which might have allowed for some less-than-stellar chip samples to be employed on some of the companies' OC products (which, with higher operating frequencies and consequent broadband frequency mixtures, hit the apparent 2 GHz frequency wall that produces the crash to desktop).

Another reason for this, according to Igor, is the actual "reference board" PG132 design, which is used as a reference, "Base Design" for partners to architecture their custom cards around. The thing here is that apparently NVIDIA's BOM left open choices in terms of power cleanup and regulation in the mounted capacitors. The Base Design features six mandatory capacitors for filtering high frequencies on the voltage rails (NVVDD and MSVDD). There are a number of choices for capacitors to be installed here, with varying levels of capability. POSCAPs (Conductive Polymer Tantalum Solid Capacitors) are generally worse than SP-CAPs (Conductive Polymer-Aluminium-Electrolytic-Capacitors) which are superseded in quality by MLCCs (Multilayer Ceramic Chip Capacitor, which have to be deployed in groups). Below is the circuitry arrangement employed below the BGA array where NVIDIA's GA-102 chip is seated, which corresponds to the central area on the back of the PCB.

RTX 3080 Users Report Crashes to Desktop While Gaming

A number of RTX 3080 users have been reporting crashes to desktop while gaming on their newly-acquired Ampere graphics cards. The reports have surged in numerous hardware discussion venues (ComputerBase, LinusTechTips, NVIDIA, Tom's Hardware, Tweakers and Reddit), and appear to be unlinked to any particular RTX 3080 vendor (ZOTAC, MSI, EVGA, and NVIDIA Founders Edition graphics cards are all mentioned).

Apparently, this crash to desktop happens once the RTX 3080's Boost clock exceeds 2.0 GHz. A number of causes could be advanced for these issues: deficient power delivery, GPU temperature failsafes, or even a simple driver-level problem (though that one seems to be the least likely). Nor NVIDIA nor any of its AIB partners have spoken about this issue, and review outlets failed to mention this happening - likely because it never did, at least on samples sent to reviewers. For now, it seems that manually downclocking the graphics card by 50-100 MHz could be a temporary fix for the issue while it's being troubleshooted. An unlucky turn of events for users of NVIDIA's latest and greatest, but surely it's better to face a very slight performance decrease in exchange for system stability.

AMD Releases the Radeon Adrenalin Edition 20.2.2 Drivers

AMD today released version 20.2.2 of their Radeon Adrenalin Edition driver suite. The new version brings with it support for the launch of Zombie Army 4: Dead War, so users can experience the latest and greatest performance available for AMD graphics cards on the new release.Perhaps more importantly, the new release also features a number of fixes for Black Screen errors in a number of scenarios and games, of which much has already been written over the internet. There are still a number of instances where black screens can occur listed on AMD's "Known Issues" checklist for this driver release, however, so make sure to check the release notes to see if this driver looks to fix your particular scenario. Of course, you're likely always better off updating to this latest driver version.
DOWNLOAD: AMD Radeon Adrenalin Edition 20.2.2 Drivers

Worldwide Markets Feel Jolt of Tencent's Epic $143 Billion Stock Crash

Tencent Holdings, China's second most valuable tech firm after Alibaba, was mauled at the markets Tuesday (31/07), with its share value dropping 25 percent from its January peak. This translates to a stunning USD $143 billion (yes, billion) in investor wealth being wiped out. The crash has had a domino effect on tech stocks worldwide, as FANG block member Facebook lost an equally stunning $136 billion in market value, over the past three trading sessions. Apparently, buzzwords of the season such as AI and big-data aren't proving enough to keep investors interested in tech stocks as many are beginning to question the stability of the tech industry. All eyes are now on Tencent's August 15 release of its Q2-2018 financial results.

NVIDIA's 384.76 Drivers Crash Watch Dogs 2 on Startup

Users beware: if you've updated your NVIDIA drivers to the recently released 384.76 version and intend to play Watch Dogs 2, you might have a hard time doing so. Reports have surfaced that the latest NVIDIA drivers, which bring support to the "Rise Up" open-beta of "Lawbreakers" as well as support for "Spiderman: Homecoming - a VR Experience.", break startup on Ubisoft's game.

The issue doesn't appear to be listed on NVIDIA's 384.76 release notes (not even on the PDF), so it seems this issue largely flew under NVIDIA's radar. But if you've had problems with Wash (sorry, Watch) Dogs 2, be sure to check if you have the latest 384.76 drivers installed. That could be the source of the problem. Our own resident W1zzard himself ran into this problem, but no amount of steampunk wand waving was able to fix the issue. However, a fresh install of NVIDIA's previous driver release (382.53) should let you go out to San Francisco again.

Edit: The issue is related to Ansel and can be fixed by starting C:\Program Files\NVIDIA Corporation\Ansel\Tools\NvCameraConfiguration.exe and selecting the "disabled" option at the bottom of the window.
Return to Keyword Browsing