- MSI AFTERBURNER DISPLAY CPU TEMP FULL
- MSI AFTERBURNER DISPLAY CPU TEMP SOFTWARE
- MSI AFTERBURNER DISPLAY CPU TEMP SERIES
Nothing new or special about that, that’s why we have RMA. If you have a card with issue # 1, your card may fail at any given time when stressed.
MSI AFTERBURNER DISPLAY CPU TEMP SERIES
At least one or more Gigabyte bios versions for the RTX 3000 series cards reportedly has a faulty/buggy bios fan curve causing fan issues that in some cases could potentially result in gpu overheating Some cards (from any manufacturer) can have defective components (that’s nothing new or special) This means that we most probably have two separate things, sometimes occurring at the same time: In cases such as this, hardware getting bricked without having overheating issues is obviously faulty, some component on the card just fails and the card dies. The GPU never exceeded 50% load and stayed under 60C* temperature for the majority of the time and it still crashed and got bricked. My 3080ti was bricked tonight while constantly being monitored via MSI Afterburne with a custom fan profile set and FPS capped at 60.
However, there have been people reporting that while they had been constantly monitoring their gpu via MSI Afterburner with a custom fan profile applied, FPS capped at 60, and GPU never exceeded 50% load and 60 degrees Celcius temperature for the majority of the time, it still crashed and got bricked:ģ080ti bricked after playing Technical Support If you have a Gigabyte RTX 3000 series card and you’re facing gpu overheating issues randomly, that seems to be the only workaround, at least for now. The solution to the problem is either applying a custom fan curve with MSI Afterburner before running a game, thus bypassing the Gigabyte bios fan curve (recommended way), or flashing a compatible BIOS for the same card from another vendor (eg ASUS) on your Gigabyte card (unorthodox way). Gigabyte sadly haven’t released an updated bios version that resolves the fan issues with their RTX 3000 series cards.
MSI AFTERBURNER DISPLAY CPU TEMP SOFTWARE
So, as it turned out, in our case the issue is related to a fan controller malfunction resulting in the card overheating.Īfter some more digging, we have found that the culprit is most probably the Gigabyte bios for the RTX 3000 series AT LEAST PARTLY, and while the issue seems to trigger as a combinational result of several factors (possibly due to software conflict with some other program, like rgb software, etc), it is most probably related to at least one or more Gigabyte bios versions for the RTX 3000 series cards, as it is known to cause fan issues in some cases, here is a reddit post from 3 years ago for reference: Reddit - Dive into anything We installed the card in a different system to test it further, and the issue didn’t occur on its own, so we tried to replicate the issue artificially by setting the gpu fan manually to run at 41% and voila: The abnormal behavior occurred again!
MSI AFTERBURNER DISPLAY CPU TEMP FULL
In plain words, for some unknown reason, even if the card was under full load, the fan controller was acting as if the card was still in idle state, so the fans wouldn’t spin as the temps got higher and higher and the gpu was throttling, decreasing its operating frequency all the way down to just 300MHz, trying to avoid frying itself due to overheating. In fact, as we found out later after testing, the Gigabyte RTX 3080Ti has fans that practically cut off completely at 41% speed. But this time we had one more clue that made everything obvious: the gpu fans were running at just 41%, which is way too low. So, we went in the settings and set the fan speed to be visible in the UI.Ī couple of days later, possibly out of coincidence, the card started exhibiting the same abnormal behavior in other games as well and not just Diablo 4. Then we watched the video again, and noticed that we had forgotten to set MSI Afterburner to display the card’s fan speed while running the game. Another commenter suggested that this might be a fan related issue, but at first we (wrongly) didn’t believe this might be a possible cause. One of the commenters in the comment section suggested that this might be caused due to an overloaded memory rail and even posted a technical video explaining why this might be the case.Īfter the first open beta weekend, we went back to playing various other games, like Hogwarts Legacy for example and the issue didn’t occur since. We had never seen something like that, this just didn’t make sense.
0 kommentar(er)
