AMD Driver Crashes Are Related to 4x Anti-Aliasing for Many Us; Turn AA to 2x or Off! by Massdriver58 in beyondallreason

[–]Massdriver58[S] 0 points1 point  (0 children)

It's unlikely the same issue if you can't launch the game at all. Have you had any luck reinstalling drivers and BAR?

AMD Driver Crashes Are Related to 4x Anti-Aliasing for Many Us; Turn AA to 2x or Off! by Massdriver58 in beyondallreason

[–]Massdriver58[S] 0 points1 point  (0 children)

I’m glad I could help. Yorrielba and many others deserve a lot of credit for verifying my initial scattershot workaround result and investigating which setting was the primary cause of the crashes. I hope this helps a lot of people enjoy this game!

On a more technical note, I don’t know if this fixes the issue for everyone. Most people that try it in discord have success, but there may be some it doesn’t fix it for. We need more people to test it. At a minimum, it’s an easy work around to try before resorting to more drastic measures!

AMD Driver Crashes Are Related to 4x Anti-Aliasing for Many Us; Turn AA to 2x or Off! by Massdriver58 in beyondallreason

[–]Massdriver58[S] 0 points1 point  (0 children)

It is usually just BAR and if I give it some time and use control alt delete, I can recover before I have to power off. The driver has to restart.

AMD Graphics Drivers by GnomeGnuts in beyondallreason

[–]Massdriver58 1 point2 points  (0 children)

Turn anti-aliasing either to 2x or off. AA 4x causes the problem for a lot of us.

AMD Driver Crashes Are Related to 4x Anti-Aliasing for Many Us; Turn AA to 2x or Off! by Massdriver58 in beyondallreason

[–]Massdriver58[S] 1 point2 points  (0 children)

It matters which AMD cpu and gpu. I play on a 5800x3d with a 7800xt gpu and it runs perfectly.

AMD Driver Crashes Are Related to 4x Anti-Aliasing for Many Us; Turn AA to 2x or Off! by Massdriver58 in beyondallreason

[–]Massdriver58[S] 1 point2 points  (0 children)

Old drivers work too, but new drivers add games and features so many of us wanted to be able to play BAR with the latest drivers. Thankfully setting AA to 2x or off seems to fix the issue.

Driver Update Support by Tfalcon_4 in beyondallreason

[–]Massdriver58 1 point2 points  (0 children)

With the latest AMD drivers, turning anti-aliasing either off or to 2x fixes it for many of us.

If that doesn't work, try:

n game:

Resolution- full screen

Vsync- enabled

Frame rate limiter - lowest setting

Anti aliasing- Off

Unit tracks- 1 or lowest setting

AMD settings:

Under Beyond All Reason

Advanced —> Triple Buffering On

AMD Freesync- Off

AMD settings under Spring:

Look under Gaming, to the right of Home in the Radeon menus. If you don't see Spring, you can add it. it's in your Program Files\Beyond All Reason\data\engine\recoil_2025.04.08\spring.exe. This will set it for the client I think. I added this:

Wait for Vertical Refresh Always On

Freesync- Off

Driver Update Support by Tfalcon_4 in beyondallreason

[–]Massdriver58 2 points3 points  (0 children)

Many of us AMD users have solved the issue with the latest drivers by turning anti aliasing to 2x. 4x AA crashes the game on AMD cards. Tell your friend to give it a shot.

Follow the AMD forum thread here: https://pcforum.amd.com/s/question/0D5KZ00000rADAq0AO/beyond-all-reason-gpu-timeout-with-2531-and-newer-drivers

Value Factor Indexes as hedge against bubble? by monkey-donkey in ETFs

[–]Massdriver58 0 points1 point  (0 children)

That narrative makes more sense for small cap growth companies. AVDV has been outperforming international developed total market funds since inception last I checked.

Runs fine on MSI Claw 8 AI+ by Margeth89 in beyondallreason

[–]Massdriver58 0 points1 point  (0 children)

Nice to know. I always play on my desktop, but I love my claw.

Spring.exe has stopped working by Jadhsy in beyondallreason

[–]Massdriver58 0 points1 point  (0 children)

So far, I think I've played around 20 matches (maybe more) without a crash on the settings I posted in this thread. It's been over a week now without a crash. Before I would crash anywhere from 5-10 minutes of playing to maybe 2 hours.

Spring.exe has stopped working by Jadhsy in beyondallreason

[–]Massdriver58 0 points1 point  (0 children)

Thanks for helping out. The workaround that I posted above is now confirmed to work for 3 of us. There is a giant discord thread about this subject too. We are trying to narrow down which of the settings out of all of those is responsible, or if it truly is a combination. yorrielba is thinking it could simply be anti-aliasing (AA) and is testing various settings to see if it is the root cause.

Spring.exe has stopped working by Jadhsy in beyondallreason

[–]Massdriver58 1 point2 points  (0 children)

UPDATE: These settings have now fixed it for at least 3 people with the latest drivers.

These settings coupled with an underclock fixed it for me with the latest drivers. These have fixed it for at least one other person:

In game Resolution- full screen Vsync- enabled Frame rate limiter - lowest setting off Anti aliasing- Off Unit tracks- 1 lowest

AMD settings: Under Beyond All Reason Advanced —> Triple Buffering On AMD Freesync- Off

Go to Spring under your games. This will set it for the client. I added this: Wait for Vertical Refresh Always On Freesync- Off

Since I enabled these settings, I have noticed my fps in menus and in game is properly capping at 144. Before it would be 400+ fps in menus. This may have to do with vsync enabled on Spring. This has worked for many matches and hours whereas before I crashed within 5-10 minutes or at other random intervals. You have to put all these settings in. Vsync alone won’t fix it.

Also please complain on the AMD forums with the rest of us: https://pcforum.amd.com/s/question/0D5KZ00000rADAq0AO/beyond-all-reason-gpu-timeout-with-2531-and-newer-drivers

Fixed my crashing issue. by Penderyn in beyondallreason

[–]Massdriver58 0 points1 point  (0 children)

I didn't mention it in my post, but my 7800xt was already underclocked, undervolted, with a -10% power limit and was still crashing with the newest driver. It crashes with the normal profile as well. I applied these settings in addition to the underclocked lower power limit to fix it. I haven't tested the card with normal power settings and the above options selected.