CRASHING IS MOSTLY BECAUSE OF THE SETTINGS! TRY THESE!

[Leatherface24]

If you're Crashing right at the title screen, Try this out

https://steamcommunity.com/app/553850/discussions/0/4206994023681686368/?ctp=2

*FINAL EDIT***

No more crashes. Arc does not crash any games for me no matter how much I tried. Its the settings. I think the Arc stupidity may have been a dev created theory at this point, posting in the forums as regular players to give them an excuse.

I have proven without a shadow of a doubt for myself that the settings I posted here never result in crashes. I have recreated the crashes now by going with all high or ultra settings and with global illumination and bloom turned on.

Thats whats killed my sessions, not arc, ever. Try these settings below and confirm they work or dot work for you as well. THANK YOU to all that helped here. Youre all truly awesome to have done so!!


*EDIT* confirmed after 10 Missions; Arc not once has crashed the game for me. Not a single time. Graphic and Resolution settings I had with no crashed are:

Motion Blur 100% and off - No issue
Depth of field On
Bloom - On = Crash, Off no crash
Sharpness 0.75
Texture Quality- High
Object Quality Detail-Medium
Render Distance- Medium
Shadow Quality- Low
Particle Quality - Low
Reflection Quality - Medium
Space Quality-Low
Ambient Occlusion- On
Screen-Space Global Illumination- OFF. On= Crash
Terrain Quality- medium
Volumetric fog Quality- Medium
Volumetric Clouds Quality-Medium
Lighting Quality- Medium
Anti- aliasing - On

*EDIT* Not using Ultra settings or anything passed 1440p seems to either eliminate or seriously cut down on crashes.


Ryzen 5800 3dx
Sapphire Nitro + 7900 XTX
Asus B550 F Wifi II Motherboard
Trident ddr4 3600 64gb memory
Corsair 1000W platinum Psu.
Everything stock, latest drivers, no overclocks anywhere, fresh windows 11 install, all up to date drivers, zero rgb software.

I literally cannot play one single round without crashing.

Legion Go, stock settings

I can get though about 8 missions with zero crashes.

I'm making as something productive here, not to complain. If we can aggregate this, it may help get this all resolved a hell of a lot faster and not return....hopefully.

***PLEASE KEEP THIS ON TOPIC AND POST SPECS AND PERFORMANCE EXPERIENCE IN GAME. ARC WEAPONS ARE NOT THE REASON THE CRASHES ARE HAPPENING SO MUCH****

Use a program like GPU-Z or something else to monitor whats happening on your setup if anything is overheating or being over driven so to speak while you play. If it does crap out, you can see if its your rig or indeed the game.

[Dragova]

Originally posted by Zander:

Originally posted by Valerium:

The developers literally said it was the arc thrower also I personally have NOT CRASHED ONCE in a mission when i wasn't using arc thrower, when I did use arc thrower crash EVERY game within 10 minutes.

yea, exactly, me too in like 40 missions. 0 crashes without arc, 100% crashes with arc.
I guess people can crash for other reasons, but don't know whats going on in this thread.

I've gone out of my way yesterday to play a whole session on my strongest system to use every arc weapon for the mission. I couldn't get it to crash yet a few days ago, when playing difficulty 7 with other people, it crashed on the last 10 minutes of the timer. I keep thinking it has to do more with network and the number of enemies spawning and dying.

[Doko]

Originally posted by Drag-ova:

Well said. I know I sound like a huge blow hard and understand that I can be quite condescending. And I apologize to everyone's efforts here. They're not in the wrong. I've been there before as far as trying to solve problems on my end as far as this hobby goes, and I feel like the people who build us fun games could really put more effort into their work. These days seems like they'd rather get us to fight eachother.

It's fine mon, just some folks can have misunderstandings with situations like these (I just wanted to give a heads up, and I myself can sound it too).

I do feel like at the end of the day, using an engine that reached EoLS back in 2018 was not the best idea, and using a bloated anti-cheat and P2P connection type doesn't help either.

Tbh I'm actually glad to talk to someone that isn't like the rest of the board out there, because outside this thread it's like any other thread you see on /V/ or at worst, /b/, where it's the same info, the same topic, the same spam, the same bait, all of it nonsensical and mind numbing.

[Doko]

Originally posted by Drag-ova:

Originally posted by Zander:

yea, exactly, me too in like 40 missions. 0 crashes without arc, 100% crashes with arc.
I guess people can crash for other reasons, but don't know whats going on in this thread.

I've gone out of my way yesterday to play a whole session on my strongest system to use every arc weapon for the mission. I couldn't get it to crash yet a few days ago, when playing difficulty 7 with other people, it crashed on the last 10 minutes of the timer. I keep thinking it has to do more with network and the number of enemies spawning and dying.

Now that I think about this a little more, has anyone on this entire board even made mention of checking their ports and/or forwarding?. All I've seen are graphics/display settings and hardware specs.

I can't do anything for mine since I'm technically on shared internet.

[lethargicpillow]

Sooooo. I did some digging.
1. Initial exact crash code was: INVALID_POINTER_READ_c0000005
And I've remembered something. The same issue was (and maybe still is) with a Horizon port on PC. Limiting FPS from native 144 to 60 for Helldivers in NVIDIA settings solved it.
2. Next crash codes were: NULL_CLASS_PTR_WRITE_c0000005, NULL_CLASS_PTR_READ_c0000005 with bloom and global ilu on. Turning them off gave no effect.
While investigating, I've stumbled on this Reddit thread: https://www.reddit.com/r/Helldivers/comments/1ana9wc/amd_7000_series_crash_solution/
Tried -use-d3d11 launch option. No crashes now, so this combo solution works for me.

P.S. All graphics settings are on ultra.
No crashes now lol. Console framerate-to-memory issues for us, mere PC mortals.

UPD: bloom and global illumination on finally led to crash. So turn them off.

[Leatherface24]

Originally posted by Zander:

Originally posted by Valerium:

The developers literally said it was the arc thrower also I personally have NOT CRASHED ONCE in a mission when i wasn't using arc thrower, when I did use arc thrower crash EVERY game within 10 minutes.

yea, exactly, me too in like 40 missions. 0 crashes without arc, 100% crashes with arc.
I guess people can crash for other reasons, but don't know whats going on in this thread.

Turn off bloom and global illumination settings, then use the settings in the 1st post of this discussion and tell me if arc weapons crash your game anymore. Please try it and let us know. This isnt a challenge but me being sincere here. Id love all of us to be able to play with no crashes and further narrow down why theyre happening. Thanks man

[Leatherface24]

Originally posted by Drag-ova:

Originally posted by Doko:

Yeah but for everyone you think is stupid for doing X/Y, chances are super high there's gonna be someone else who thinks the same to you. This is why I roll my eyes at Youtubers and journos who think they got it all figured out, who think they know business being sound or not, and well no, it's just greed, and we're built like that, it's not f*ckin deep lads.

Even code monkeys can be wrong, or worse than another code monkey, playing that game is a losing one at best.

Like I know the devs dun goofed. I know their choice of anti cheat is an absolute bare bones last thought in their back of their minds, and the fact they decided to keep rolling with an engine that stopped support since 2018. All we have currently is to test samples and settings to make temporary workarounds, that's really all we are trying to do in this thread, just to allow us to continue playing the game.

Like ever since this game came out, I knew something was incredibly fishy when the patch notes barely talked or touched upon performance, or the known woes of Game Guard. But you see, a good chunk of this board isn't into nitty details like that, and you can see it via the sea of threads that go nowhere, that just whine about X/Y gun not working and so on.

You, me and a few others may as well be the only techies in this game's forum board that know something's not actually right, but not many are going to care, they only care for solutions, which is why they're willing to put together a test bed, since the devs have been radio silent on performance for the entire month.

Well said. I know I sound like a huge blow hard and understand that I can be quite condescending. And I apologize to everyone's efforts here. They're not in the wrong. I've been there before as far as trying to solve problems on my end as far as this hobby goes, and I feel like the people who build us fun games could really put more effort into their work. These days seems like they'd rather get us to fight eachother.

Originally posted by Drag-ova:

Originally posted by Doko:

Yeah but for everyone you think is stupid for doing X/Y, chances are super high there's gonna be someone else who thinks the same to you. This is why I roll my eyes at Youtubers and journos who think they got it all figured out, who think they know business being sound or not, and well no, it's just greed, and we're built like that, it's not f*ckin deep lads.

Even code monkeys can be wrong, or worse than another code monkey, playing that game is a losing one at best.

Like I know the devs dun goofed. I know their choice of anti cheat is an absolute bare bones last thought in their back of their minds, and the fact they decided to keep rolling with an engine that stopped support since 2018. All we have currently is to test samples and settings to make temporary workarounds, that's really all we are trying to do in this thread, just to allow us to continue playing the game.

Like ever since this game came out, I knew something was incredibly fishy when the patch notes barely talked or touched upon performance, or the known woes of Game Guard. But you see, a good chunk of this board isn't into nitty details like that, and you can see it via the sea of threads that go nowhere, that just whine about X/Y gun not working and so on.

You, me and a few others may as well be the only techies in this game's forum board that know something's not actually right, but not many are going to care, they only care for solutions, which is why they're willing to put together a test bed, since the devs have been radio silent on performance for the entire month.

Well said. I know I sound like a huge blow hard and understand that I can be quite condescending. And I apologize to everyone's efforts here. They're not in the wrong. I've been there before as far as trying to solve problems on my end as far as this hobby goes, and I feel like the people who build us fun games could really put more effort into their work. These days seems like they'd rather get us to fight eachother.

Youre awesome for that. If we all got along like this after an initial disagreement, things would be so much better

[Silverlight]

Originally posted by lethargicpillow:

Sooooo. I did some digging.
1. Initial exact crash code was: INVALID_POINTER_READ_c0000005
And I've remembered something. The same issue was (and maybe still is) with a Horizon port on PC. Limiting FPS from native 144 to 60 for Helldivers in NVIDIA settings solved it.
2. Next crash codes were: NULL_CLASS_PTR_WRITE_c0000005, NULL_CLASS_PTR_READ_c0000005 with bloom and global ilu on. Turning them off gave no effect.
While investigating, I've stumbled on this Reddit thread: https://www.reddit.com/r/Helldivers/comments/1ana9wc/amd_7000_series_crash_solution/
Tried -use-d3d11 launch option. No crashes now, so this combo solution works for me. Even with bloom and global ilu on. For the rest of you, the whole set of recommendations might help.

No crashes now lol. Console framerate-to-memory issues for us, mere PC mortals.

I didn't have the words , but I had a suspicion framerate may be the issue and I locked mine too

[Leatherface24]

Originally posted by lethargicpillow:

Sooooo. I did some digging.
1. Initial exact crash code was: INVALID_POINTER_READ_c0000005
And I've remembered something. The same issue was (and maybe still is) with a Horizon port on PC. Limiting FPS from native 144 to 60 for Helldivers in NVIDIA settings solved it.
2. Next crash codes were: NULL_CLASS_PTR_WRITE_c0000005, NULL_CLASS_PTR_READ_c0000005 with bloom and global ilu on. Turning them off gave no effect.
While investigating, I've stumbled on this Reddit thread: https://www.reddit.com/r/Helldivers/comments/1ana9wc/amd_7000_series_crash_solution/
Tried -use-d3d11 launch option. No crashes now, so this combo solution works for me. Even with bloom and global ilu on. For the rest of you, the whole set of recommendations might help.

No crashes now lol. Console framerate-to-memory issues for us, mere PC mortals.

Awesome, thanks for sharing this. Not everyone has the same causes so this one may help some

[lethargicpillow]

Originally posted by Leatherface24:

Originally posted by lethargicpillow:

Sooooo. I did some digging.
1. Initial exact crash code was: INVALID_POINTER_READ_c0000005
And I've remembered something. The same issue was (and maybe still is) with a Horizon port on PC. Limiting FPS from native 144 to 60 for Helldivers in NVIDIA settings solved it.
2. Next crash codes were: NULL_CLASS_PTR_WRITE_c0000005, NULL_CLASS_PTR_READ_c0000005 with bloom and global ilu on. Turning them off gave no effect.
While investigating, I've stumbled on this Reddit thread: https://www.reddit.com/r/Helldivers/comments/1ana9wc/amd_7000_series_crash_solution/
Tried -use-d3d11 launch option. No crashes now, so this combo solution works for me. Even with bloom and global ilu on. For the rest of you, the whole set of recommendations might help.

No crashes now lol. Console framerate-to-memory issues for us, mere PC mortals.

Awesome, thanks for sharing this. Not everyone has the same causes so this one may help some

You're welcome. Basically those guys came to the same solution as us here with additional adjustments.

[Dragkna]

Nope even with those setting no bloom or global illumination it can still freeze for me when using the Arc Thrower.

[Leatherface24]

Originally posted by Dragkna:

Nope even with those setting no bloom or global illumination it can still freeze for me when using the Arc Thrower.

Check post #220. Perhaps that will help you but thank you so much for trying the settings out

[Aethrys]

Originally posted by Leatherface24:

I think the Arc stupidity may have been a dev created theory at this point, posting in the forums as regular players to give them an excuse.

Lolwut.

No, they posted it in the discord.

Originally posted by Baskinator:

We have identified the cause of the freezes many players have been experiencing, and we're in the process of building a patch to fix it that should be ready to deploy early next week. In the meantime, we advise against using the Arc Thrower, Arc Shotgun, and Tesla Tower as those appear to be linked to the issue.

Thank you for your continued patience!

[lethargicpillow]

Originally posted by Dragkna:

Nope even with those setting no bloom or global illumination it can still freeze for me when using the Arc Thrower.

Well, my experience now says that Arrowhead seriously messed something up with memory allocation/access. Nothing can be done for sure on our end, as each of us has their own hardware combo. You can look up your own crash logs, maybe something else will come out of it.

[lethargicpillow]

UPD: bloom and global illumination turned on finally led to crash. Arc weapons did not, but I'll test some more.

[Pctechnik]

Originally posted by BR1 DELTA-237:

3080ti i core 7 3699 dollar computer.....

crashes on startup

every

single

time.

it didn't before

now it does.

$3700? Bro, you got ripped.