Jump to content

Recommended Posts

DaiaBu   

Hello all,

 

Bit of an odd one this. Whilst playing this morning, my game crashed back to the desktop, but there was no error, or any sign that it was going to crash (freezing, stuttering, etc) - it just closed down instantly and with no warning, as though I'd hit Alt+F4. I had probably been playing about 20 minutes or so. I restarted no problem, and rejoined the same server. All seemed well, then after about another 10-15 minutes, exactly the same thing happened. 

 

I restarted again and cleared my app data (haven't done that since the update). Joined a different server, and was able to play for a good couple of hours, so I figured it was just a data issue. But then, about 10-15 minutes into an Insurgency round of Chora, it happened again - just as the SL was throwing an incendiary into the cache in front of me.

 

I have kept the log file from the second time it happened, and from the most recent time. In both cases, it appears to have been a fatal error relating to "Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address...."

 

I am running an overclocked CPU, however it appears to be completely stable. It's done a couple of Prime95 runs with no issue, and the temperature maxed out at 70 degrees while playing - warm, but nothing to worry about, and it hit higher peaks while running Prime for longer periods with no issues or errors.  

 

If it's of any relevance, the first crash happened on Chora, and the second was Logar Valley. Between those crashes I played full rounds on both Operation First Light and Narva - I only mentioned that in case perhaps there's an asset in the desert maps which might have caused the failure. 

 

Anyone have any ideas? I've saved the log files in case they are any use. Below are extracts from the final part of each log where the Unhandled Exception was recorded.

Happy to share the full log files if needed.

 

System specs:

CPU: Intel i7 3770K 3.5GHz (OCed to 4.2GHz @ ~1.170v)

GPU: Radeon RX480

RAM: 8Gb Kingston DDR3 @ 1600MHz

Mobo: Asus P8Z68-V

Running on Windows 10 64bit @ 1920x1080p. Performance is generally good (~50FPS)

Using ReShade with a SweetFX filter, but have been using this for months with no adverse effects. 

 

Any help appreciated.

 

 

First occurrence:

Spoiler

[2017.07.22-10.39.26:606][752]LogSquad: [CHAT Game] Russian Ground Forces has won the match!
[2017.07.22-10.39.31:694][142]LogSquad: [CHAT All] murica
[2017.07.22-10.39.37:916][636]LogSquad: [CHAT All] gg
[2017.07.22-10.39.39:865][794]LogSquad: [CHAT Game] [ KSA ]FMA.68 has disconnected.
[2017.07.22-10.39.44:908][116]LogThreadingWindows:Error: Runnable thread TaskGraphThreadNP 2 crashed.
[2017.07.22-10.39.44:908][116]LogWindows:Error: === Critical error: ===
[2017.07.22-10.39.44:908][116]LogWindows:Error: 
[2017.07.22-10.39.44:908][116]LogWindows:Error: Fatal error!
[2017.07.22-10.39.44:908][116]LogWindows:Error: 
[2017.07.22-10.39.44:908][116]LogWindows:Error: Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x00000005
[2017.07.22-10.39.44:908][116]LogWindows:Error: 
[2017.07.22-10.39.44:908][116]LogWindows:Error: squad.exe
[2017.07.22-10.39.44:908][116]LogWindows:Error: squad.exe
[2017.07.22-10.39.44:908][116]LogWindows:Error: squad.exe
[2017.07.22-10.39.44:908][116]LogWindows:Error: squad.exe
[2017.07.22-10.39.44:908][116]LogWindows:Error: squad.exe
[2017.07.22-10.39.44:908][116]LogWindows:Error: squad.exe
[2017.07.22-10.39.44:908][116]LogWindows:Error: squad.exe
[2017.07.22-10.39.44:908][116]LogWindows:Error: squad.exe
[2017.07.22-10.39.44:908][116]LogWindows:Error: KERNEL32.DLL
[2017.07.22-10.39.44:908][116]LogWindows:Error: ntdll.dll
[2017.07.22-10.39.44:908][116]LogWindows:Error: ntdll.dll
[2017.07.22-10.39.44:908][116]LogWindows:Error: 
[2017.07.22-10.39.44:908][116]LogWindows:Error: Crash in runnable thread TaskGraphThreadNP 2
[2017.07.22-10.39.44:991][116]LogExit: Executing StaticShutdownAfterError
[2017.07.22-10.39.44:991][116]LogWindows: FPlatformMisc::RequestExit(1)
[2017.07.22-10.39.44:991][116]Log file closed, 07/22/17 11:39:44
 

 

Second occurrence:

Spoiler

[2017.07.22-13.10.20:718][926]LogSquad: [CHAT Game] Villain has connected.
[2017.07.22-13.10.22:481][ 15]LogSquad: [CHAT ServerMessage] We are Recruiting - over 18's only - www.rustyinplaces.org
[2017.07.22-13.10.40:518][905]LogSquad: [CHAT Game] [H.9] x-A.Hofer-x ♥ Squad has disconnected.
[2017.07.22-13.10.43:275][965]LogWindows:Error: === Critical error: ===
[2017.07.22-13.10.43:275][965]LogWindows:Error: 
[2017.07.22-13.10.43:276][965]LogWindows:Error: Fatal error!
[2017.07.22-13.10.43:276][965]LogWindows:Error: 
[2017.07.22-13.10.43:276][965]LogWindows:Error: Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x3842b313
[2017.07.22-13.10.43:276][965]LogWindows:Error: 
[2017.07.22-13.10.43:276][965]LogWindows:Error: squad.exe
[2017.07.22-13.10.43:276][965]LogWindows:Error: squad.exe
[2017.07.22-13.10.43:276][965]LogWindows:Error: squad.exe
[2017.07.22-13.10.43:276][965]LogWindows:Error: squad.exe
[2017.07.22-13.10.43:276][965]LogWindows:Error: squad.exe
[2017.07.22-13.10.43:276][965]LogWindows:Error: squad.exe
[2017.07.22-13.10.43:276][965]LogWindows:Error: squad.exe
[2017.07.22-13.10.43:276][965]LogWindows:Error: squad.exe
[2017.07.22-13.10.43:276][965]LogWindows:Error: squad.exe
[2017.07.22-13.10.43:276][965]LogWindows:Error: squad.exe
[2017.07.22-13.10.43:276][965]LogWindows:Error: squad.exe
[2017.07.22-13.10.43:276][965]LogWindows:Error: squad.exe
[2017.07.22-13.10.43:276][965]LogWindows:Error: squad.exe
[2017.07.22-13.10.43:276][965]LogWindows:Error: squad.exe
[2017.07.22-13.10.43:276][965]LogWindows:Error: squad.exe
[2017.07.22-13.10.43:276][965]LogWindows:Error: squad.exe
[2017.07.22-13.10.43:276][965]LogWindows:Error: squad.exe
[2017.07.22-13.10.43:276][965]LogWindows:Error: squad.exe
[2017.07.22-13.10.43:276][965]LogWindows:Error: squad.exe
[2017.07.22-13.10.43:276][965]LogWindows:Error: squad.exe
[2017.07.22-13.10.43:276][965]LogWindows:Error: squad.exe
[2017.07.22-13.10.43:276][965]LogWindows:Error: squad.exe
[2017.07.22-13.10.43:277][965]LogWindows:Error: squad.exe
[2017.07.22-13.10.43:277][965]LogWindows:Error: squad.exe
[2017.07.22-13.10.43:277][965]LogWindows:Error: KERNEL32.DLL
[2017.07.22-13.10.43:277][965]LogWindows:Error: ntdll.dll
[2017.07.22-13.10.43:277][965]LogWindows:Error: ntdll.dll
[2017.07.22-13.10.43:277][965]LogWindows:Error: 
[2017.07.22-13.10.43:467][965]LogExit: Executing StaticShutdownAfterError
[2017.07.22-13.10.44:059][965]LogWindows: FPlatformMisc::RequestExit(1)
[2017.07.22-13.10.44:059][965]Log file closed, 07/22/17 14:10:44

 

Share this post


Link to post
Share on other sites
DaiaBu   

Oh, apologies - just after posting this, I see someone else has posted a thread with almost the exact same symptoms as me:

http://forums.joinsquad.com/topic/28355-crashing-with-no-error-message/

 

Should I instead just forward all this to the email in that thread ([email protected]), along with my log files?

Perhaps if this is affecting other users there might be something to investigate for the devs.

 

Apologies if I've broken the rules by posting a similar issue, not sure how I missed the other thread :/

Edited by DaiaBu

Share this post


Link to post
Share on other sites
beginna   

Hello and welcome to Squad @DaiaBu,

 

4 hours ago, DaiaBu said:

Apologies if I've broken the rules by posting a similar issue, not sure how I missed the other thread :/

Don't worry. - All good.
If someone got an issue, it's better to create a new thread. - Easier to keep track. ;)

 


 

unfortunately I cannot really help you here... :/

it needs more investigation.

this line from the log file is probably for troubleshooting interesting:

Quote

[2017.07.22-10.39.44:908][116]LogWindows:Error: Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x00000005

 

 

 

In order to get the latest log file including the crash:

  1. delete all files and folders in the Logs-folder (C:\Users\USERNAME\AppData\Local\Squad\Saved\Logs)
  2. reproduce the crash    
  3. upload the latest created log file to eg. http://www.tinyupload.com/
  4. upload the latest created UE4Minidump.dmp inside the UE4CC-* folder
  5. share links here

 

 

most importantly: please contact [email protected]

  • describe your problem (e.g. copy&paste first post)
  • mention the EXCEPTION_ACCESS_VIOLATION issue
  • attach both files (alternatively add download links of the two files)
  • add link to this thread

maybe add, that a few other guys get an almost similar looking message in the log file. the address is different:

Quote

[...]Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x00000***

 

FYI
Link to threads with similar line in the log file:

http://forums.joinsquad.com/tags/exception_access_violation/

Share this post


Link to post
Share on other sites
Odin   
5 minutes ago, DaiaBu said:

Thanks beginna.

 

Link to my latest log file:

http://s000.tinyupload.com/?file_id=72338842725051782838

 

And to the .dmp file:

 http://s000.tinyupload.com/?file_id=06557334621385887743

 

I will forward all of the above details to the Squad support email and link to this thread.

Many thanks for your help :)


Thanks. I will get someone to take a look at these. 

Share this post


Link to post
Share on other sites
Ingram   

+1

 

Same thing happens to me almost every game... hope you find and fix this annoying crash!

 

i7-7700k @4.6Ghz

GTX 1060*OC

16GB DDR4 3200Mhz

Edited by Ingram

Share this post


Link to post
Share on other sites
DaiaBu   

Just an update, but I have a suspicion that this might be due to the overclock.

 

Yesterday afternoon, I decided go for a clean install, see if that would help - I uninstalled from Steam, made sure everything was deleted (any SweetFX/Reshade files, etc) then did a fresh download/install. Whilst I was in the menu setting up my controls, the game crashed out again, in exactly the same manner. However, no log file was created. I then had it happen again after about 10-15 minutes in the firing range. Then again, only a few minutes after joining a server - "Unhandled Exception" in the log.

 

Despite the fact that my system is otherwise stable, I went into the BIOS and upped the CPU voltage a fraction to 1.2v.

Restarted Squad, joined a server and played for 1-2 hours without any problem whatsoever.

 

It isn't absolutely conclusive as the pattern to crashing appeared to be fairly random anyway, but I will continue to monitor stability over the next few weeks to see if this solves the problem. It might be worth checking with other users who experienced the same thing, to see if they are also running overclocked systems.

 

Like I said, might not be the cause, but worth adding to the investigation notes. 

Share this post


Link to post
Share on other sites
Ingram   
On 7/24/2017 at 5:00 AM, DaiaBu said:

Just an update, but I have a suspicion that this might be due to the overclock.

I had just crashed after 15-20 minutes on Gorodok (full server) today and got fed up and decided to come back to here and saw your post!^ I decided to try returning my overclocked components to stock.  Ive had a serious GPU overclock for over 4+ months with increased voltage.

 

It was only about 7 days ago I overclocked my i7-7700k from stock 4.2Ghz to 4.6Ghz. I've had this issue for months which is why I'm going to try GPU stock first, but it did get WAY WORSE after overclocking my CPU.

--------------------------------------

 

This is a major noticeable change for me! I'm able to play a game longer than 30 minutes after returning my GPU to stock. I will report back to see if any crashes happen--- and try returning my CPU to stock if it does.

 

  • Edit: 1 hour into the game and still no crashes (played on the Narva for about 30+ minutes) which is highly unusual.
  • Editx2: 2 hours into the game and still not a single crash (Chora map) I rarely make it this far without crashing.
  • Editx3: Starting Al Barash now... I'm almost convinced the crashes are related to overclocking... will try switching servers after I hit my third hour.
  • Editx4: Third hour hit... this game is a long one and im going to finish it up (20+ mins more) and try another server.
  • Editx5: 3 hours 40 minutes logged and no crashes... but I'm going to take a break and if I get the same results the next time I play on a different server after a computer restart, then I will be 100% convinced it was overclocking related. This is very bizarre since I usually rip my hair out and just stop trying to play by this point.
  • Editx6: Tried another server and I'm 1H 30m in (2 different maps) and no crashes... (Huge step up from 15-30 minute match crashes) I'm going to try again later today after a full computer restart... but it really does seem like my overclocked GPU was affecting my constant crashes. I feel very thankful to the OP right now as I would've never thought my overclock was affecting Squad in such a negative way.
  • Editx7: It's the next day and my computer has restarted... I'm already 1 hour in for an Al Asbrash match with no crashes! I'm pretty sure my issue has been fixed! =) My CPU happens to have a voltage of 1.2+ like OP which is probably stopping me from crashing on the CPU side.

 

This is just... weird AF... but I accept it so long as I don't crash anymore.

giphy.gif

 

Edited by Ingram
Edit updates (No more crashes!)

Share this post


Link to post
Share on other sites
19 hours ago, Ingram said:

I had just crashed after 15-20 minutes on Gorodok (full server) today and got fed up and decided to come back to here and saw your post!^ I decided to try returning my overclocked components to stock.  Ive had a serious GPU overclock for over 4+ months with increased voltage.

 

It was only about 7 days ago I overclocked my i7-7700k from stock 4.2Ghz to 4.6Ghz. I've had this issue for months which is why I'm going to try GPU stock first, but it did get WAY WORSE after overclocking my CPU.

--------------------------------------

 

This is a major noticeable change for me! I'm able to play a game longer than 30 minutes after returning my GPU to stock. I will report back to see if any crashes happen--- and try returning my CPU to stock if it does.

 

  • Edit: 1 hour into the game and still no crashes (played on the Narva for about 30+ minutes) which is highly unusual.
  • Editx2: 2 hours into the game and still not a single crash (Chora map) I rarely make it this far without crashing.
  • Editx3: Starting Al Barash now... I'm almost convinced the crashes are related to overclocking... will try switching servers after I hit my third hour.
  • Editx4: Third hour hit... this game is a long one and im going to finish it up (20+ mins more) and try another server.
  • Editx5: 3 hours 40 minutes logged and no crashes... but I'm going to take a break and if I get the same results the next time I play on a different server after a computer restart, then I will be 100% convinced it was overclocking related. This is very bizarre since I usually rip my hair out and just stop trying to play by this point.
  • Editx6: Tried another server and I'm 1H 30m in (2 different maps) and no crashes... (Huge step up from 15-30 minute match crashes) I'm going to try again later today after a full computer restart... but it really does seem like my overclocked GPU was affecting my constant crashes. I feel very thankful to the OP right now as I would've never thought my overclock was affecting Squad in such a negative way.

 

This is just... weird AF... but I accept it so long as I don't crash anymore.

giphy.gif

 

Odd, my GPU isn't overclocked and I'm still crashing at least once every two matches, and I just completely reinstalled Windows (including all programs). Was heartbroken when it didn't work.

Share this post


Link to post
Share on other sites
Ingram   
12 minutes ago, Simplicity said:

Odd, my GPU isn't overclocked and I'm still crashing at least once every two matches, and I just completely reinstalled Windows (including all programs). Was heartbroken when it didn't work.

Since your GPU wasn't overclocked did you try the OPs CPU method? as it so happens my overclock that's currently in place has a voltage above 1.2.

 

On 7/24/2017 at 5:00 AM, DaiaBu said:

Just an update, but I have a suspicion that this might be due to the overclock.

 

Despite the fact that my system is otherwise stable, I went into the BIOS and upped the CPU voltage a fraction to 1.2v.

Restarted Squad, joined a server and played for 1-2 hours without any problem whatsoever.

 

Share this post


Link to post
Share on other sites
Ingram   
1 hour ago, Simplicity said:

Odd, my GPU isn't overclocked and I'm still crashing at least once every two matches, and I just completely reinstalled Windows (including all programs). Was heartbroken when it didn't work.

Instead of it being overclocking related... what if its more directly a voltage related problem? Try upping your voltage (whether you have stock or overclocked CPU) above 1.2v like the OP.

 

@Simplicity I hope you manage to find a solution to fix your crashes... looking at your own topic it is similar to me and OP and may be overclocking/voltage related too.

 

@DaiaBu Thank you for making this thread and bringing up the potential issue... a real fix is rare to find on these forums.

Edited by Ingram

Share this post


Link to post
Share on other sites

After doing some intense research (Google) I found that the  EXCEPTION_ACCESS_VIOLATION reading address 0x00000*** refers to an error that happens when a program tries to use memory normally reserved for other processes. This is speculation, but maybe overclocking the CPU causes Squad to try and use memory it's not supposed to.

Share this post


Link to post
Share on other sites

I found this on an Unreal Engine web page..could this be it?   Link: https://answers.unrealengine.com/questions/550053/exception-access-violation-reading-address-0x00000-1.html

Anti-Malware Scanners impacting two Executables

We have discovered that a few anti-malware scanners are detecting two of our unreal engine executables (UnrealBuildTool.exe and IPhonePackager.exe) as malware and are deleting\quarantining it. This will potentially impact developers using the executables.  We are actively working to fix the false positives and apologize for any inconvenience. 

 

Share this post


Link to post
Share on other sites
DaiaBu   
On 25/07/2017 at 11:56 PM, Ingram said:

Instead of it being overclocking related... what if its more directly a voltage related problem? Try upping your voltage (whether you have stock or overclocked CPU) above 1.2v like the OP.

 

@Simplicity I hope you manage to find a solution to fix your crashes... looking at your own topic it is similar to me and OP and may be overclocking/voltage related too.

 

@DaiaBu Thank you for making this thread and bringing up the potential issue... a real fix is rare to find on these forums.

 

No problem :)

 

Just as a bit of an update, the game has been rock solid stable ever since I upped the core voltage to 1.200v. Played it several times over the last week, sometimes for 2-3 hours...not a single crash :)

 

One of the guys from Squad support replied to my email last week and asked me to try a few things, so before I did so tonight, I reverted my CPU voltage back to 1.170v, as it was when I encountered the problem initially.

 

The result? Three crashes to desktop in quick succession when attempting to get into the Firing Range (in fact, one occurred just loading to main menu). The first one gave me an actual critical error, the next two occurred as before - crash to desktop cleanly, no error, "unhandled exception" in the log file.  Went back to BIOS, upped CPU voltage back to 1.200v - straight away, game loaded into the Firing Range with no crash whatsoever.

 

Pretty confident that this is a CPU undervoltage issue.

 

On 28/07/2017 at 8:34 PM, Simplicity said:

After doing some intense research (Google) I found that the  EXCEPTION_ACCESS_VIOLATION reading address 0x00000*** refers to an error that happens when a program tries to use memory normally reserved for other processes. This is speculation, but maybe overclocking the CPU causes Squad to try and use memory it's not supposed to.

 

Yes, this makes sense. I've seen similar errors in on Window's BSODs on overclocked systems before. It was unusual in my case though as the PC seemed stable at the lower voltage...Prime95 ran for ages and generated no errors, it was only Squad that seemed to crash. 

Edited by DaiaBu

Share this post


Link to post
Share on other sites
Ingram   

Update: 40+ hours logged in Squad with zero crashes since setting my GPU to stock and CPU remains over 1.2v

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×