Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
Report this post
what error do you get in the windows log (windows key + r, type in eventvwr and return, look at the 'application logs' for the errors thrown) for the access violation specifically the faulting module(s) if any?
CPU is a 7950X and its not overclocked and uses an AIO.
The DMP file that was generated from the game shows the following when using the !analyze -v function:
It would indicate from my research that this is the cause:
The error you're encountering with helldivers2.exe is identified as an access violation with the following details:
Exception Code: c0000005
Exception Type: Access violation
Specific Error: Attempt to write to address 0000000000000000, which indicates a null pointer write.
Causes:
Null Pointer Dereference:
The program is attempting to write data to a memory address that is NULL or 0. In C++, this often happens when a pointer that has not been initialized or has been explicitly set to NULL is used without checking if it's valid.
Code Bug or Memory Corruption:
There might be a bug in the helldivers2.exe where it's using a pointer that has been incorrectly set to NULL or has become NULL due to memory corruption.
Incompatible or Incorrect Software Version:
The game might be crashing due to an incompatibility with the system or because of using an outdated or corrupted version of the software.
Driver or System Issues:
Although less likely, issues with graphics drivers or other system-level components can sometimes result in such errors by causing unexpected behavior in memory management or pointer handling.
Suggested Solutions:
Check for Updates: Ensure that Helldivers 2 is up to date. Developers often release patches to fix such bugs. Check the game's official channels or posts found on X for any recent hotfixes or updates related to crash fixes.
Memory Checks: Run memory diagnostic tools to check if your RAM is functioning correctly, as memory corruption can lead to null pointer issues.
Debugging and Code Review: If you have access to the source code or are in contact with developers, review the code around the crash site for any pointer misuse or uninitialized variables.
System Configuration: Verify that your system settings are compatible with the game's requirements. Issues with Windows updates or hardware drivers might need addressing.
Reinstallation: Sometimes, reinstalling the game can resolve issues if they are caused by corrupted game files.
This error indicates a problem that requires attention from either the user in terms of system checks or from the developers for a code fix. If you're not the developer, your options are somewhat limited to updating, checking system integrity, and waiting for a patch or developer response.
The exception code is a garden variety windows bug code that appears on about 90% of all crashes and has next to none analysis value.
I've put my system through testing using multiple diagnostic tools. I used Memtest86 and Karhu for RAM checks, and MemtestCL alongside Memtest_vulkan for GPU testing, all of which ran successfully for 8 hours. My CPU was solid under stress from Cinebench 2024 and PRIME95.
All drivers, including the chipset, are current, and nothing is overclocked. Others facing similar mid-game crashes have mentioned the same error code in the Windows Event Manager. While not every mission is affected, the issue is common enough to remind you that you might lose up to 40 minutes of progress unexpectedly during a mission, which is annoying.
so that's not all settings at default.
>ram overclocked to 6000mhz
>memory access violation
it might be just a coincidence.
I believe that gameguard will throw an exception if anything operates outside its parameters. but we'll know when you test that, too.
It's within the system's parameters. My DDR5 RAM modules are rated for 6000MHz, but to achieve this speed, you must enable EXPO; without it, your memory will only operate at half its specified speed and this is the only game that crashes randomly.
https://www.gskill.com/community/1502239313/1722321351/G.SKILL-Announces-Ultra-Low-Latency-DDR5-6000-CL28-DDR5-Memory-Kits
This is similar to XMP with Intel.
bye bye!
lol okay then, "bye bye"
Despite several updates to GeForce drivers, the problem persists. I'm unsure of the exact cause, but it might be due to conflicts with the anti-cheat software. Regardless, the game should function without requiring us to tweak hardware or software settings. We also encountered the reinforcement bug recently, where a fellow Helldiver couldn't be reinforced, a problem that was known more than nine months ago. This doesn't give me much confidence that the developers will address these crashes soon, especially since they might not see it as affecting enough players to warrant attention. There's talk that uninstalling and reinstalling nProtect, which automatically reinstalls upon launching the game, could help. I've experienced this issue across multiple PCs with different configurations and hardware, yet the problem remains consistent.
https://store.steampowered.com/news/app/1549250/view/6456498378615365698
Use this
https://steamcommunity.com/sharedfiles/filedetails/?id=3235564264
if the issue persists share a DxDiag report