i am still crashing since #53 stress test update, ive recently found out about another guy having the same issue as mine, i have tried several things such as rolling back my video driver, reinstalling the game, verifying integrity of the game, launching as admin, removing launch parameters, trying different launch parameters and compatibility options, the game works fine on experimental branch, but will crash at launch in stress-test since update #53, help pls
- Operating System
- Windows 10 x64
If you remove the contents of your C:\Users\*username*\Documents\DayZ folder, does the issue still persist? And if so, will -nocharmenu solve the issue? Also, are there any .mdmp files being created in your appdata folder?
Hey, i have tried deleting the Dayz Folder in Documents, no help, and also, no, -nocharmenu in launch parameters didn't solve it. And no, the only filed generated when the game crashes seems to be theses .RPT files, even if i launch "Dayz (with logs)" :/
i've created this topic on reddit and found some people that seems to have the same issue, also i said and tried some stuff that's in the topic:
Thank you for the update windstride.
Were there any recent Windows updates on your computer prior to the issue starting to occur? And has the issue started to occur with the release of the stress test 53 version or were you able to play the stress test 53 previously?
No, actually, i blocked my system from updating, my windows can't update, because in one of the updates my ethernet driver got screwed up and my internet would lose connection constantly, couldn't find a way to fix it, had to rollback and block updates. You think that could cause the issue? A bit outdated version of windows 10. But answering your other question: Yes, i am certain that the issue started with the release of #53 update, i could play before that, and i can still play on experimental branch.
Yes, this has indeed been the issue which was causing the crashes for certain users and has been fixed with yesterdays Experimental release. I am going to set this ticket as Resolved now, but feel free to submit another one in case you run into any issues in the future.