Jump to content
Bash

[Solved] The Memory Cannot Be Read [@launch not when closing]

Recommended Posts

Last 3 days I have not been able to launch squad.  Tried every step of a clean install on multiple drives to no avail.  After researching on the forums I found the same issue persisted for awhile when people were CLOSING the game.  This issue occurs when I LAUNCH the game.  I get the "Loading" screen but after it fills no splash screen with the "Squad" logo.  32GB's of RAM never even bumps.  Windows Event Logs doesn't show any additional information about this specific error.  Any help would be greatly appreciated!

FYI mods I am aware of the following similar posts that contain no working fix:  
 
http://forums.joinsquad.com/topic/13222-the-memory-could-not-be-written/
http://forums.joinsquad.com/topic/12349-memory-could-not-be-written/
http://forums.joinsquad.com/topic/13064-expected-not-an-issue-squadexe-the-memory-could-not-be-written/?hl=memory

http://forums.joinsquad.com/topic/13064-expected-not-an-issue-squadexe-the-memory-could-not-be-written/

 

 

squaderr.JPG

Capture.JPG

Share this post


Link to post
Share on other sites

[LauncherProgress] 100%
[LauncherFinished] Result: 0 Message: EasyAntiCheat successfully loaded in-game
customSplashScreen::aboutToQuit

so the launcher launches fine w/ EAC.  figured it's a hardware issue but wanted to check. 

Share this post


Link to post
Share on other sites

well ****.  it was EAC.  Added the following file locations to TrendMicro's Exceptions list and the game works fine.  Was not a hardware/system issue.  
find the following files under the Steam\steamapps\common\Squad... directory.

Capture.JPG

Share this post


Link to post
Share on other sites
On 09/30/2017 at 4:16 AM, Bash said:

 it was EAC. Added the following file locations to TrendMicro's Exceptions list and the game works fine. [...]

Thx for letting us know.

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

×