Suddenly Unable to Start Game

Community Support
1

So, as of today, I’m completely unable to get Boundless to work at all. It just crashes immediately. Doesn’t even generate a crash log. I’m at a loss. I’ve reinstalled Boundless, Steam, and tried updating and reinstalling various redist. Nothing seems to work. I’m super frustrated because it happened suddenly, without warning. Did I just pay for this game to have it be literally unplayable now?

1 Like
2

Could you give us some details of your setup? What cpu, gpu, and os are you running?

1 Like
3

Windows 10, I7-5820 3.3ghz CPU, Radeon r9 290 GPU. I’m fairly convinced its software. I just have no idea what changed between the 27th and the 28th that all of the sudden the game crashes immediately upon trying to start.

1 Like
4

do you see the grey screen with the text? or does it crash before that

1 Like
5

If the game refuses to start then it’s most likely a missing dependency:

  1. Try manually installing the dependencies which Steam should have downloaded to the following locations:

    C:\Program Files (x86)\Steam\SteamApps\common\boundless_CommonRedist\DotNet\4.51\NDP451-KB2872776-x86-x64-AllOS-ENU.exe`

C:\Program Files (x86)\Steam\SteamApps\common\boundless_CommonRedist\vcredist\2015\vc_redist.x64.exe

  2. Make sure your graphics drivers are fully up to date.

  3. Try temporarily disabling your antivirus.

2 Likes
6

If there is a log file in %LOCALAPPDATA%\Turbulenz\Boundless\ can you share that?

The live game was not updated in that period which should narrow it down to a change on your system, eg a windows update, or it could be some of the local data that is corrupted, eg \chunkcache data in the same folder as the logs.

[Edit] I missed the line about not writing a crash dump. Can you see if windows is logging anything “Run the Event Viewer app, in there look under Windows Logs -> Application”.

1 Like
7

If the error message is “Cannot connect to steam”… One of our group had a similar issue solved by launching from steam instead of from a shortcut.

Hth.

1 Like
8
  1. Make sure Steam is running.
  2. Make sure you have the latest version of Steam installed. (It’s possible to not get their auto updates.)
  3. Launch Boundless from Steam.

Is a Boundless log created?

1 Like
9

Boundless doesn’t have a log, but I was able to use the event viewer to find a windows log:

  • System

    • Provider

    [ Name] Application Error

    • EventID 1000

    [ Qualifiers] 0

    Level 2

    Task 100

    Keywords 0x80000000000000

    • TimeCreated

    [ SystemTime] 2017-09-29T18:56:28.539990300Z

    EventRecordID 71651

    Channel Application

    Computer **********

    Security

  • EventData

    boundless.exe
    0.0.0.1
    59c1345e
    unknown
    0.0.0.0
    00000000
    c0000005
    000000017fff0004
    1284
    01d33954a791297c
    E:\Program Files (x86)\SteamLibrary\steamapps\common\Boundless\boundless.exe
    unknown
    601cbedc-181f-4df7-9984-e544507cdd81

Faulting application name: boundless.exe, version: 0.0.0.1, time stamp: 0x59c1345e
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000000017fff0004
Faulting process id: 0x1284
Faulting application start time: 0x01d33954a791297c
Faulting application path: E:\Program Files (x86)\SteamLibrary\steamapps\common\Boundless\boundless.exe
Faulting module path: unknown
Report Id: 601cbedc-181f-4df7-9984-e544507cdd81
Faulting package full name:
Faulting package-relative application ID:

  • System

    • Provider

    [ Name] Windows Error Reporting

    • EventID 1001

    [ Qualifiers] 0

    Level 4

    Task 0

    Keywords 0x80000000000000

    • TimeCreated

    [ SystemTime] 2017-09-29T18:56:31.768874600Z

    EventRecordID 71652

    Channel Application

    Computer ************

    Security

  • EventData

    120842613843
    4
    APPCRASH
    Not available
    0
    boundless.exe
    0.0.0.1
    59c1345e
    StackHash_7e29
    0.0.0.0
    00000000
    c0000005
    PCH_E9_FROM_ntdll+0x00000000000A5C34

    C:\Users\ **** \AppData\Local\Temp\WER9150.tmp.WERInternalMetadata.xml C:\Users\ **** \AppData\Local\Temp\WER9CCB.tmp.appcompat.txt
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_boundless.exe_d25ae6fc6814341c64852e3fb48bd0c7ac80d725_31612a42_3b5f9d75

    0
    601cbedc-181f-4df7-9984-e544507cdd81
    1
    6219eee06e10f37f58488f5838377933

Fault bucket 120842613843, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: boundless.exe
P2: 0.0.0.1
P3: 59c1345e
P4: StackHash_7e29
P5: 0.0.0.0
P6: 00000000
P7: c0000005
P8: PCH_E9_FROM_ntdll+0x00000000000A5C34
P9:
P10:

Attached files:
C:\Users\ ***** \AppData\Local\Temp\WER9150.tmp.WERInternalMetadata.xml
C:\Users\ ***** \AppData\Local\Temp\WER9CCB.tmp.appcompat.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_boundless.exe_d25ae6fc6814341c64852e3fb48bd0c7ac80d725_31612a42_3b5f9d75

Analysis symbol:
Rechecking for solution: 0
Report Id: 601cbedc-181f-4df7-9984-e544507cdd81
Report Status: 1
Hashed bucket: 6219eee06e10f37f58488f5838377933

1 Like
10

As for the crash itself, steam opens the program window but doesn’t get to the gray background part, it just crashes immediately. I tried running the redists and it seems that I already have all of them installed.

1 Like
11

I was hoping it would say there was a dmp file in the Windows Error Reporting (WER) folder but that does not seem to be the case. To diagnose it we need the call stack or a dump file. You don’t happen to have Visual Studio or similar installed?

Do you have any streaming or other apps that might interact (eg that add an overlay) with the game installed?
D3DGear was crashing the game at start up. If so try disabling them. Also if your on the Beta version of Steam try the default version.

1 Like
12

I was able to get it working. Seems as though something in msi afterburner was causing issues. At first I couldn’t get it to start with afterburner on, though I could start the game and then afterburner when it was already running. I updated my afterburner to the beta version and now no issue. Thanks a ton for the help!

3 Likes