Page MenuHomeFeedback Tracker

[Primary Report] Windows Error Message
Closed, ResolvedPublic

Description

Had a CTD with the following Windows error message:

Dayz.exe Application Error
The instruction at 0x004a17d7 referenced memory at 0x79cf9000. The memory could not be written. {F31060} {F31061} {F31062} {F31063} {F31064} {F31065} {F31066}

Details

Legacy ID
3490851011
Severity
None
Resolution
Fixed
Reproducibility
Unable To Reproduce
Category
Error Message
Steps To Reproduce

Only happened once. As yet, can not reproduce.

Event Timeline

BleedoutBill set Category to Error Message.
BleedoutBill set Reproducibility to Unable To Reproduce.
BleedoutBill set Severity to None.
BleedoutBill set Resolution to Fixed.
BleedoutBill set Legacy ID to 3490851011.May 8 2016, 9:35 PM
BleedoutBill edited a custom field.
Bohemia added a subscriber: MASOU.Feb 23 2015, 3:53 PM
Geez added a comment.Feb 23 2015, 4:19 PM

Hello BleedoutBill and thank you for your report.
Please try deleting contents of C:\Program Files (x86)\Common Files\BattlEye and verifying the Steam data. Report back if this has helped and if the issue persists, attach contents of your C:\Users\*USERNAME*\AppData\Local\DayZ folder to this ticket.
Regards,
Geez

Per your request, I deleted the contents of C:\Program Files (x86)\Common Files\BattlEye

I have attached the crash report files, but the minidump file was over the maximum file size to upload. Therefore, I compressed it with the 7zip utility. I hope that this doesn't cause any inconvenience.

Per Eugen's note from earlier today, I have added the -dologs launch parameter. The only other launch parameter that I am currently using is -oldui.

I will try to reproduce the crash and report back.

Thanks for your help!

EDIT: I forgot to mention that I verified the integrity of the local game files and that checked out OK.

I just had another CTD, but with a different error message:
The Instruction at 0x04a15d2 Referenced Memory at 0x0f3d0000. The Memory could not be read.

I have uploaded fresh copies of the report and dump files. The new ones have a "_2" appended to the name of the file. Again, the minidump file is compressed with 7zip. If gzip, bzip2, tar, or something else is more convenient, please advise.

Even compressed, my minidump is getting too large to upload to your site. I will have to archive the current one and have the game generate a new one from scratch.

Rostas added a subscriber: Rostas.May 8 2016, 9:35 PM

I have the same problem. I will try to delete what you said.

I just had another CTD, but with a different memory location:
The Instruction at 0x04a15d2 Referenced Memory at 0x104200000. The Memory could not be read.

I have uploaded fresh copies of the report and dump files. The new ones have a "_3" appended to the name of the file. I have compressed the minidump file with zip.

Geez added a comment.Feb 26 2015, 11:34 AM

Hello BleedoutBill.
Thank you for the crash dumps, we will analyze them and report back to you.
Regards,
Geez

I had this problem occur only after the 0.54 update, never before, so far only happened once when I was running. I have now added the -dologs start parameter and will send in report if it happens again.

Geez added a comment.Feb 26 2015, 3:23 PM

Hello Bleedoutbill.
We have analyzed the crashdumps and confirmed this is an issue we are aware of. The issue has been scheduled for a fix.
Regards,
Geez

moeb1us added a subscriber: moeb1us.May 8 2016, 9:35 PM

hey geez, I have added my logs as well. getting similar error messages and CTDs every 20-30 minutes. Mine is the Dayz-logs.7z

You have my beans Geez!

Geez added a comment.Mar 13 2015, 5:44 PM

Hello BleedoutBill.
The issue has been fixed internally and should be fixed on Steam soon.
Regards,
Geez