Page MenuHomeFeedback Tracker

Experimental 0.61.136887 - Client lockup when using vehicles
Acknowledged, NormalPublic

Description

Three times now - once with a sedan, twice with the hatchback - after several minutes of driving the client has become unresponsive, requiring a forced shutdown. Anyone else experienced this and able to shed some light? I've put ~8 hours into this experimental so far and whilst it might be coincidence, the only crashes I've experienced have been whilst driving.

Details

Severity
None
Resolution
Open
Reproducibility
Always
Operating System
Windows 10 x64
Operating System Version
Home
Category
Game Freezes
Steps To Reproduce

Find a vehicle and drive for a while!

Additional Information

i7 950 @ 3.5Ghz
10GiB 1066Mhz DDR3
256Gib SSD
Radeon 7870 2GB
DayZ x64

Event Timeline

Geez changed the task status from New to Need More Info.Jan 3 2017, 4:29 PM
Geez added a subscriber: Geez.

Hello Mithrawndo and thank you for the report.
When the issue occurs for you the next time, can you keep an eye on your CPU usage and let us know if there are any changes in the usage from your usual gameplay? Also if you are using any third party program which is able to show the FPS, does the FPS drop to 1 when the client becomes unresponsive? And have you also experienced such issue on foot?
Regards,
Geez

I can confirm I've not experienced the issue on foot (~10 hours gameplay) and I've only experienced the issue using the 64 bit client (~6 hours gameplay).

CPU/memory usage were not abnormal; around 30% CPU use and peaking at ~65% memory use.

I'm using the steam overlay to see FPS, and when the client locks up the FPS counter shows what I'd expect: Around 30FPS in large cities and in excess of 80FPS in quiet, remote areas. The lockup is instantaneous and I'm unable to use ctrl-shift-esc to open task manager, alt-enter to window the application or shift-tab to open the steam overlay. Ctrl-alt-del allows me to logout, restoring shell access.

I'm inclined to think this graphic related, so for reference I'm running Radeon 16.6

Mithrawndo added a comment.EditedJan 17 2017, 3:38 AM

Around another 12 hours in and I've been able to confirm this bug popping up on the 32 bit client and can confirm it's been seen - albeit far less frequently - on foot too.

What information can I provide to help you track this little bugger down?

Geez changed the task status from Need More Info to Acknowledged.Jan 17 2017, 9:28 AM

Thank you Mithrawndo.
We are aware that this particular issue occurs and it is scheduled for a fix.
Regards,
Geez