Buildapc

3849 readers

62 users here now

founded 2 years ago

MODERATORS

Lemmenmo

So how bad are the 3090 memory issues? (self.buildapc)

submitted 1 year ago by justaveg to c/buildapc

4 comments fedilink hide all child comments

I'm not ready to upgrade yet but I'm just wondering how bad the 3090 memory issues are, and what can reasonably be done about it. I asked once before and the response was basically "there aren't really any good options to deal with it", but I have a hard time believing that some heatsinks wouldn't take care of the issue. So I guess, what are my options? Is the 3090 so bad that I should just avoid it?

you are viewing a single comment's thread
view the rest of the comments

[–] thantik 9 points 1 year ago* (last edited 1 year ago) (1 children)

3090 "Memory Issue"? Care to ... maybe elaborate?

Edit: Since OP doesn't seem to care about informing us of what these "Memory Issues" supposedly are, I went and searched it up myself:

The issue specifically pertains to the 24GB of GDDR6X memory on the RTX 3090. Some users reported problems related to the memory modules, such as crashes, artifacts, and even complete system failures under certain conditions. These issues were often observed when the card was put under extreme loads, particularly during tasks like gaming, rendering, or mining cryptocurrency.

NVIDIA addressed this problem through a BIOS update that limited the card's memory allocation in specific scenarios to prevent the issues from occurring. This BIOS update essentially restricted the use of certain types of workloads that were known to trigger the problem. This solution, while effective in preventing further occurrences of the memory issues, also limited the card's capabilities in some scenarios.

[–] justaveg 2 points 1 year ago (1 children)

Basically because half the memory is on the back of the card(and isn't cooled adequately), it can overheat and cause stability issues or maybe even kill the ram.

[–] thantik 1 points 1 year ago

lol, I had edited my reply JUST as you replied...what a coincidence!

There was a bios update that solves the issue. It's considered resolved.