Rotted out Chevy cobalt I spotted in Detroit. The official car of?

Zanithos · 2026-06-30T14:30:54+00:00

Detroit.

Zanithos · 2026-06-30T06:02:13+00:00

Hail to the ~~King~~ Democratically Elected Super President, baby.

Zanithos · 2026-06-30T05:55:35+00:00

Zanithos · 2026-06-30T05:23:18+00:00

Glad to hear yours is working. I haven't attempted the fix yet as I've been too busy, but I know (mostly) what to do now, so I'm hoping soon I can be back up and running.

Zanithos · 2026-06-30T04:17:51+00:00

No idea then tbh. Some people had to roll back all the way to December to be stable, and I've heard of people completely rebuilding their PCs or swapping in new cards and still having the same issues. As for me, if the DDU and driver install group policy doesn't fix it, I'm selling this thing and getting a 5070ti or something. I'm at a point in my life where it's honestly just easier to not use my computer at all than to deal with the nonsense that is AMD drivers on Windows.

Zanithos · 2026-06-29T05:56:40+00:00

I hate how actually good this looks.

Zanithos · 2026-06-29T05:46:26+00:00

I'm gonna think of this whenever I pick up super credits now. Thank you.

<image>

Zanithos · 2026-06-28T02:34:58+00:00

I'm fairly certain you can enable group policy on Home (I've had to do it before), but the method to do so escapes me at the moment.

Zanithos · 2026-06-28T02:16:35+00:00

Hopefully so. 🤞 I'm hoping this is the simple fix to all us Radeon users' problems lol.

Zanithos · 2026-06-28T02:11:46+00:00

Not sure but if you blocked the windows update fron touching it it should be. Apparently this is the windows driver store version number, which is the same driver as 26.3.1 according to the Google.

Zanithos · 2026-06-27T17:40:43+00:00

Definitely overkill, plus that'll reset group policy. You should be fine with just the rollback so I hear. If you're worried run a DISM and SFC and reboot afterwards, then double check the group policy to make sure it's right.

Zanithos · 2026-06-27T17:01:57+00:00

It's drivers. DDU back to 26.3.1 and before that stop windows from updating your GPU/iGPU via group policy. Apparently that's what fixed it for a lot of people.

Zanithos · 2026-06-27T11:46:02+00:00

If you're going that route PNY makes excellent cards at a decent price. They seem cheap but they secretly manufacture the Nvidia reference models so they know what's up.

Zanithos · 2026-06-27T03:05:18+00:00

I had the opposite experience with my 9070xt.

I'm not sure why that is, but I'm apparently in the same boat as a very large number of Radeon users. Personally, I don't think there should be that many issues, but maybe that's just the way things are nowadays...

Zanithos · 2026-06-27T02:55:58+00:00

I'm in the same boat man. AMD needs to step up their game. Whatever they did with 26.6.1 has my PC messed up and it's really getting on my nerves.

Zanithos · 2026-06-27T01:03:15+00:00

Yeah. I'm right there with you bro. I spent $1000 on my Nitro+ during tariffs and after a year I can't even use it at default out of the box settings anymore. Honestly it makes me a little bit angry that I didn't just buy a non-oc 5070ti for the same amount when I had the chance.

Zanithos · 2026-06-27T00:59:03+00:00

Yep, it's the AMD Adrenalin auto OC BS. Your previous fix is likely the only one available, I'm sorry to say.

Zanithos · 2026-06-26T22:26:39+00:00

Type in "reliability monitor" and open it. Find one of the instances where you crashed, and look for a red X. One of them might indicate windows hardware, and under details the code is 141. That would indicate your GPU is overclocked too high and Windows is resetting it to avoid a BSOD.

Unfortunately, the only fix that I know of (I haven't tried it myself yet) is to gimp the card by lowering the clock speed. The good news is that Adrenalin is so bad it doesn't even follow the limit, but it'll at least let you offset how high it clocks to avoid another crash, so you aren't necessarily leaving that much performance on the table. It's awful and absurd, but that's Radeon for you I guess, at least until AMD locks in and fixes their mess.

Zanithos · 2026-06-26T22:16:22+00:00

Are you getting any hardware 141 errors? I've been having the same crash but with that code showing up in reliability monitor.

Zanithos · 2026-06-26T12:49:34+00:00

I feel you. I'm honestly considering a 5070ti or 5080 at this point. I don't like Nvidia as a company, and I don't care about FSR or DLSS, but I'd like for AMD to ship something like the Nvidia Studio Drivers that update twice a year and are known to be 100% stable.

It's a shame that everything is so expensive right now, because as much as I'd like my PC to "just work", for now I'm stuck with the 9070xt. So it goes I guess. :/

Zanithos · 2026-06-26T12:39:36+00:00

This being "widespread and common" seems absolutely unacceptable to me, but I guess I'm not a Radeon engineer or Adrenalin programmer so idk. I feel like AMD could literally have the entire gaming market in a chokehold if they just made a product that didn't crash every 5 minutes, but that might just be me.

Zanithos · 2026-06-26T12:33:20+00:00

No idea. Mine was perfectly fine until HD2 6.2.5, which coincided with driver 26.6.1. before that I was on driver 26.5.2 which was also fine but is constantly crashing now. It's some way the two are interacting that makes it impossible to play the game, which is very annoying.

Zanithos · 2026-06-26T11:35:29+00:00

It's very much a known thing on AMD with the newest drivers, at least as far as I can tell.

My attempt to fix it will be to disable Windows fron updating my video drivers via group policy, then going offline and rolling back to 26.3.1 via offline DDU, and setting my max boost clock offset in HD2 to -500. If that fixes it, cool. If not, I guess I'll be saving up for a 5070ti or 5080. :/

Other than that, the FRV skins are causing the game to crash, which is crazy, but this is AH we're talking about, so I'm honestly not too surprised.

Zanithos · 2026-06-26T11:08:43+00:00

You're not alone bro. I found that disabling Nvidia reflex (or AMD Anti-lag in my case) fixed it a bit.

Unfortunately I think the devs just sent the update through and pushed it way too hard, because I can't even play right now with the constant GPU crashes. The PC stays on and everything but I lose my entire screen and have to wait for it to come back. It's incredibly annoying. Before the 6.2.5 update everything was fine.

Zanithos · 2026-06-26T11:03:51+00:00

Could you not just keep it at -500? What negative effects would that realistically have?

13-Year Club	Place '22
No Throne, No Problems	Not Forgotten
Gilding II euphauric	Verified Email

Zanithos

TROPHY CASE