Exitcode 1061 (unrestorable lost device)

From Egosoft Wiki
Revision as of 16:58, 15 August 2022 by Ketraar (talk | contribs)

You landed on this page because the game detected a runtime crash.

The issue occurred because the game ran into a lost device condition and failed to restore the device.

Requesting further support

We are currently trying to understand the exact conditions which trigger this problem for affected users, so we can provide further details on this page. If you want to support us with that and get an analysis of why this happens in your situation, please send an email to prioritysupport@egosoft.com (Subject: Exitcode 1061). In the mail attach the crash dump (see this page for an explanation on how to locate the file) as well as the dxdiag and vulkaninfo (explained on this wiki entry).

Technical background

If something goes wrong with the graphics device, the driver issues a reset of the device. This triggers the 'lost device' condition in the game. Before 3.00 Beta 1 this resulted in a crash to desktop. As of 3.00 Beta 1 we try to restore the access to the device when this happens. Usually, this succeeds and the game continues. However, there are possible situations where this can fail and the game won't be able to regain access to the device. For further technical details regarding the lost device issue, please refer to Exitcode 222-231, 1028 (Access to physical device lost).

Issue History

While the underlying trigger (device reset) could happen in any version of the game, this crash is specific to where this new fall-back handling which was added in 3.00 Beta 1 fails. Therefore, the affected version is set to 3.00 Beta 1, even though the same situation would have resulted in a crash even with older version.

Before X4 3.20 affected players ended up on the general graphics engine issues troubleshooting page or weren't redirected to the troubleshooting page at all (for example when running the game in full screen). Between 3.20 Beta 3 and 3.30 players running into this issue were no longer redirected to any troubleshooting page.

On 2020-09-10 (aka: after 3.30 was released) we investigated this condition and set up this troubleshooting page, so affected players are now properly directed to this troubleshooting page.

Go to Exit Codes Table