Helldivers 2

1852 readers

41 users here now

Welcome to the Helldivers 2 Community on the Fediverse.

Links

Galactic War Status

Rules

Be kind to other Citizens of Super Earth
No discussion of cheats or bug exploits.
Posts or comments with leaked / unreleased info must be clearly labelled. Example: Use [Spoiler] in the title or spoiler tag in comments.
No spam or advertising (YouTube, Twitch, etc)

founded 8 months ago

MODERATORS

[email protected]

Patch Notes 01.000.300 (store.steampowered.com)

submitted 6 months ago* (last edited 6 months ago) by [email protected] to c/[email protected]

52 comments fedilink hide all child comments

Detailed Discord Patched notes from Discord

Adding comment from Wolfrasin for better visibility.

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

[–] vikingtons 2 points 6 months ago (1 children)

For now, the most effective method to preventing this issue is to limit core clocks on NV31 to about 2500 MHz.

I believe this is under the known issues for Adrenalin

[–] Heavybell 2 points 6 months ago* (last edited 6 months ago) (1 children)

I set mine to 2555 because of Star Citizen (and Ratchet & Clank, but I finished that game a while ago), so I've had no issues with HD2 since the first week or so of release. Can confirm it works.

[–] vikingtons 1 points 6 months ago (1 children)

Interesting, were rachet and clank + star citizen also failing in the same way (intermittent TDRs or system shutdown) with default gfx core clocks?

[–] Heavybell 1 points 6 months ago (1 children)

In my case it manifested as a graphics driver crash. This would bring down anything that was using the GPU: the game, discord, Windows DWM.

Someone on SC`s forums did a bunch of research and eventually suggested the clock limit, which has solved all my SC, HD2, R&C issues and most of my War Thunder issues (though that one still silently deletes itself from RAM occasionally, but I think that's just War Thunder).

Here's the post, if you're interested: https://robertsspaceindustries.com/spectrum/community/SC/forum/50174/thread/high-end-amd-gpu-crashing-possibly-resolved-we-nee

[–] vikingtons 2 points 6 months ago (1 children)

Sorry, I take a bunch of acronyms for granted. TDR = timeout detection / recovery.

Did the bug report tool suggest there was a timeout in each of those cases?

[–] Heavybell 2 points 6 months ago (1 children)

I forget, it's been a while. I want to say yes, but the screen would freeze for several seconds before the GPU driver reset in my case, so that seems like a legitimate timeout to me. I had tried increasing the timeout in the past to fix these issues, before I found this method.

While testing I did confirm using OpenHardwareMonitor that the GPU core frequency would spike above 3100Mhz before crashing, as the thread describes. Setting the max to 2550 seems to prevent this happening.

[–] vikingtons 2 points 6 months ago

Thank you for the info!