Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Important Important
    • Resolution: Unresolved
    • Affects Version/s: 3.00 Beta 1
    • Fix Version/s: None
    • Labels:

      Description

      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 a mail to crash@egosoft.com with the subject set to "X4-506 - 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 page).

      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 X4-275.

      Issue history

      While the underlying trigger (device reset) could happen in any version of the game, this crash is specific to where this new fallback 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 (X4-2) or weren't redirected to the troubleshooting page at all (f.e. when running the game in fullscreen).
      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.

        Issue Links

          Activity

          Hide
          added a comment -

          Ignore it. 90% caused by overclocking.

          Show
          added a comment - Ignore it. 90% caused by overclocking.
          Hide
          added a comment -

          Target switch only Stations

          Show
          added a comment - Target switch only Stations
          Hide
          added a comment -

          Standard system, AMD 5500 XT, AMD R5 3600, 32 Gigs of RAM, MSI B550, no overclocking. Getting this Crash since today (STEAM). Last played around November 2020, no Problems at that Time. Updated Drivers, seems crash needs longer to appear after that. Appears 5-15 Minutes into the Game.
          Reproducable. Pretty much kills the usability for me :/

          Show
          added a comment - Standard system, AMD 5500 XT, AMD R5 3600, 32 Gigs of RAM, MSI B550, no overclocking. Getting this Crash since today (STEAM). Last played around November 2020, no Problems at that Time. Updated Drivers, seems crash needs longer to appear after that. Appears 5-15 Minutes into the Game. Reproducable. Pretty much kills the usability for me :/
          Hide
          added a comment -

          Crash during station building, was adding Swamp plant to my mini drug plex,and it crashed.
          AMD Ryzen 5 1600X, AMD Radeon 5700, 16GB RAM, Gigabyte B350, no overclocking.

          Show
          added a comment - Crash during station building, was adding Swamp plant to my mini drug plex,and it crashed. AMD Ryzen 5 1600X, AMD Radeon 5700, 16GB RAM, Gigabyte B350, no overclocking.
          Hide
          added a comment -

          Intel i7-3930K, AMD 5700XT, 644GB Ram, No Overclocking.
          X4 is not the only game my 5700XT has had issues with. This happens today quite infrequently .
          When I first got the card, happened almost daily. Most effective fix, if you have an AMD card and use Windows 10, DISABLE FAST BOOT. And AMD has been quite diligent with driver updates.

          TLDR: Disable Fast Boot in Windows 10 and keep drivers up to date.

          Show
          added a comment - Intel i7-3930K, AMD 5700XT, 644GB Ram, No Overclocking. X4 is not the only game my 5700XT has had issues with. This happens today quite infrequently . When I first got the card, happened almost daily. Most effective fix, if you have an AMD card and use Windows 10, DISABLE FAST BOOT. And AMD has been quite diligent with driver updates. TLDR: Disable Fast Boot in Windows 10 and keep drivers up to date.

            People

            • Assignee:
              Stefan Hett (Inactive)
              Reporter:
              Stefan Hett (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated: