Page MenuHomeFeedback Tracker

experimental 0.56
Closed, ResolvedPublic

Description

I get this application error memory could not be read, when exiting the game:
See from bmp file. {F31714}

Details

Legacy ID
2599428566
Severity
None
Resolution
Fixed
Reproducibility
Have Not Tried
Category
Game Crash

Event Timeline

rgobeli1 set Category to Game Crash.May 11 2015, 7:15 AM
rgobeli1 set Reproducibility to Have Not Tried.
rgobeli1 set Severity to None.
rgobeli1 set Resolution to Fixed.
rgobeli1 set Legacy ID to 2599428566.May 8 2016, 10:34 PM

Hi rgobeli1,

Sorry to hear about your trouble.

To begin with, please try having a look at the troubleshooting steps in the following forum post: https://support.steampowered.com/kb_article.php?ref=1274-uohk-5653

If the steps in the forum post above do not help, please try out the following steps:

  1. Download and install Microsoft Visual C++ 2010 Redistributable Package: http://www.microsoft.com/en-us/search/result.aspx?q=vcredist%202010&form=DLC
  2. Restart your pc.
  3. Download and install Visual C++ Redistributable Packages for Visual Studio 2013: http://www.microsoft.com/en-us/search/result.aspx?q=vcredist%202013&form=DLC
  4. Restart your pc.
  5. Launch DayZ (run both Steam and DayZ as administrator if needed).

Regards,
JStewart

I tried most things in the above links. I even reloaded the Visual C++ packages. It still does the crash when I exit the game. It may be based on the Alt tab to windows. It continues to crash on exit even after the game is restarted, if the alt tab is not done the second time. The only time it does not crash on exit is after a windows reboot and the alt-tab is not used.

Do you by any chance have any crash dumps in your "C:\Users\<Name>\AppData\Local" folder?

Alright, I'll close your ticket then. In case you encounter any further problems, please feel free to submit a new ticket.

Regards,
JStewart

It looks like this last patch has fixed my issue.
Thanks

Fouley added a subscriber: Fouley.May 8 2016, 10:34 PM
Fouley added a comment.Jun 5 2015, 4:49 PM

Yes I had the same issue and it got fixed now.