this post was submitted on 17 Jul 2024
93 points (97.9% liked)
Games
16796 readers
557 users here now
Video game news oriented community. No NanoUFO is not a bot :)
Posts.
- News oriented content (general reviews, previews or retrospectives allowed).
- Broad discussion posts (preferably not only about a specific game).
- No humor/memes etc..
- No affiliate links
- No advertising.
- No clickbait, editorialized, sensational titles. State the game in question in the title. No all caps.
- No self promotion.
- No duplicate posts, newer post will be deleted unless there is more discussion in one of the posts.
- No politics.
Comments.
- No personal attacks.
- Obey instance rules.
- No low effort comments(one or two words, emoji etc..)
- Please use spoiler tags for spoilers.
My goal is just to have a community where people can go and see what new game news is out for the day and comment on it.
Other communities:
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I think it's fairly simple. They push the chips way too hard at factory settings (whether set by the motherboard manufacturer, or even Intel's 253 watts (?) PL1 and PL2 is completely crazy) and these high limits were clearly what they wanted reviewers to benchmark these chips on.
At these levels of power most chips degrade very quickly (in a matter of weeks or a few months) and so they eventually start producing errors.
It's horrible that Intel is waiting so long when they should cut their losses, recall and refund all 1(3/4)000K(F/S) CPUs and either release a fixed version under a new name that reviewers can re-benchmark or stop selling these SKUs altogether.
I highly, highly doubt they'll find a cheap fix that doesn't significantly degrade performance.
If you watch the video from level1techs and the follow up from gamersnexus, you can hear them talk about how this is not something microcode can fix, its not only a power issue, its a design issue. With all of the out of video mem and compression bugs I would look into the memory controller. This also seems to be a smaller fix into itself, they show that some were able to get their machines up and running again once they shot the memory down to the lowest clock (4800 MT I think it was) that the DDR5 could do, and this seems to still be a bandaid and the systems will just outright die soon after, but you might be able to get in your order for RMA before it does.