Page MenuHomeFeedback Tracker

When launching game, black screen appears for approx. 3 seconds, then "game has stopped working" appears
Closed, ResolvedPublic

Description

When launching the game, it crashes.
I am using a laptop with attached specs:

http://imgur.com/jwSifW7

It is a laptop with two graphics cards (built in and the AMD 7970M)
When using the built in intel card, games opens and runs,
But when using Catalyst Control Center and switching the game to run with the 7970M, the game will launch to the black screen, then crash. {F29341} {F29342}

Details

Legacy ID
305711770
Severity
None
Resolution
Fixed
Reproducibility
Always
Category
Game Crash
Steps To Reproduce

Launching the game when using the AMD 7970M graphics card

Event Timeline

pearsauces set Category to Game Crash.
pearsauces set Reproducibility to Always.
pearsauces set Severity to None.
pearsauces set Resolution to Fixed.
pearsauces set Legacy ID to 305711770.May 8 2016, 3:45 PM
komin added a subscriber: komin.May 8 2016, 3:45 PM

Problem is caused by switch from Intel to AMD during launch of the game. Its most probably fault of Intel driver which cant handle that change. We cant really do anything about it. Its Intels problem which can be solved by different drivers.

In CCC try to set all settings for DayZ in Application profiles to Low.

Thanks for the response, however the game works fine with the intel graphics card, its the AMD graphics card that causes the crash.

Also all other games work fine with the drivers I have so I dont want to up or down grade them.

I have a USB mouse attached I shall try to launch the game without it and let you know.

Finally which settings in CCC do you suggest changing, barring in mind again that all other games work fine.

komin added a comment.Jan 21 2014, 1:51 PM

Your problem could be caused by multiple things:

  1. The most likely one is that problem is in your Intel drivers (this is source of crash). People had same problem in other games (e.g. http://forum.ea.com/eaforum/posts/list/9745301.page or http://community.logos.com/forums/t/77633.aspx) and solved it by downgrading their drivers.

Try to upgrade your drivers to newest version (https://downloadcenter.intel.com/default.aspx) or downgrade them to version in the links.

  1. It can be USB conflict. If you have integrated web cam, or another attached USB devices, try to deactivate/detach them and run game without them.
  1. It can be caused by settings in Catalyst Control Center. Try to change them and then run the game.
komin added a comment.Jan 20 2014, 3:34 PM

This issue was processed by our team and is being looked into. We thank you for your feedback.

Please keep the issue monitored to see when it is fixed.

h3X added a subscriber: h3X.May 8 2016, 3:45 PM
h3X added a comment.Jan 19 2014, 11:24 PM

When I launch the game, I get the black screen, and a windows "wait" cursor appears. This stays until the loading screen with red bar appears (about 1 minute). Since this often appears when applications stop responding, I think it may be related to this problem.

I have the exact same problem, I have a laptop with built in intel graphics card and an AMD Radeon HD 7730 graphics card.

Under the catalyst control center setting DayZ to high performance (ie use the amd graphics card) the game will not launch get error message of DayZ has stopped working a second or two after clicking play in steam.

If I set CCC to performance (ie use the built in graphics card) the game works fine.

I have attached the files from appdata

Please let us know in note section if you are still able to reproduce this issue in latest Development build.

If so, please send us DxDiag and files from this folder: "C:\Users\<Name>\AppData\Local\DayZ\"

Can you pack the files in winrar and upload it somewhere?
When the *.rar will be smaller than 2.097k, you can attach it here. Thank you.

For future reporting please refer to "How to guide" http://feedback.dayzgame.com/how-to-user.html

Hey guys,

please try reproducing the problem on the latest development build. We have done some adjustments on our end that might help with this problem.

Cheers!