Game keeps crashing with no warning, any advise?

been playing the game since before xmax of 2019. For so reason, the last week or so, I have experiancing alot of game crashes, mostly (but not always) when I’m inside my base and/or in a player town. Never happens on Exo planets. Haven’t had the issues when going on hunts or mining for gems, etc.

The game simply crashes, with no warning. No popup. Nothing. When I relaunch the game, it tells me there was a crash dump file and do I want to send it… I click yes, and logging it works 100% fine. if i stay in my base or around a town/city … within 10-20mins, it crashes again.

I have completely uninstalled and deleted the game, reinstalled, and same issue. I have confirmed all my video drivers are up to date. I don’t know what else to try. the crash dump file issue to be in binary or similar, as i can’t read it like a log. the log file that is generated shows the following…

[2020-05-03 06:30:25.444] [INFO] WebSocket closed for sanctum(id:4294967295)
[2020-05-03 06:30:26.099] [INFO] > ClientTrustedSystem::OnEntityBecameTrusted: id:8560579 is now trusted on 52183505.875000
[2020-05-03 06:34:28.841] [INFO] Got ClosedStorage Data (use2_t0_1(id:28):id:3855) w/ 543B
[2020-05-03 06:34:56.917] [INFO] c:\users\autobuild.jenkins\workspace\boundless-win64-deploy\native\src\core\tzprocess.cpp:148 (turbulenz::sMinidumpCallback) Process crashed and minidump was written to C:\Users\temil\AppData\Local\Turbulenz\Boundless\tblz_crashdump_891d9fed_f63a6a7b-3577-4e64-98b8-2aa953e1f9a1.mdmp

i can send over the crashdump file, but not sure if that should go here, or if there is anything private to not send here. please advise.

You got problems with other games?
Sounds to me like some overheating issue or so ?

nope, no other PC issues, no other game issues. run Ark, warframe, etc… with no problems. All temp settings are registering fine and no overheating alerts on the Motherboard ,video card, etc. have both liquid cooling CPU and GPU, so highly doubt it’s an overheating issue. also, the fact that it crashes only when i’m in the base or a town, randomly… sometimes it can be within 10mins… sometimes 30-40 …

one thing i noticed (could just be coincidence) is that it only started happening after the last 2 un-anounched patches the devs pushed out, the ones that came after all the spark changes and all. the next day, started having the issue… and ever since.

just fyi, i’m an IT specialist and network operations supervisor by trade, so I ran it through everything I could think of.

2 Likes

Any big farm around you ?

Thanks for sharing the crash dumps - we’ll look at them to see if there is a consistent issue. Please keep sending them.

A few things to help us track down the issue:

  1. If you start the game and just leave it sitting there doing nothing (for ~20 minutes) does it still crash?

  2. Also please open the F1 debug options, and open the Memory graph. Does this “keep going up” as you play? If so, it would suggest there is a memory leak. (You could also look at the Windows process manager / memory thingy.)

(The recent 2 patches were server only changes.)

sometimes yes, sometimes no. For example, when I first submitted this ticket, it was right after I got back from an exo-planet for about 3hrs (with no issues before or during that planet run). I got back to base, and within 5mins, game closed with no warning. I reopened the game, went through portal to base … didn’t go anywhere ese and just Alt-Tabed to goto the Forum to see if anyone else had similar issues was it was really getting anoying … and within 4-5 mins (still in sanctuary) I noticed the game had closed/crashed, again with no warning. so first was after exo, then second was in mins, less then 5mins after.

however, right now, I am siting in my base …for a solid 10+ mins, with no issues at all, Alt-tabed, typing this message and can hear the music, so I know the game is still running and didn’t close out, so it’s hard to answer this question really.

right now, the memory graph shows a flat line at 2306.32mb … no increase, no decrease … simply a flat line, however right now, no issues either… I’ll move it around and get it to fit somewhere while I play and keep an eye on it and will report back tomorrow as i’m heading to be shortly, being 4:42 am :slight_smile:

1 Like

The thing we’re trying to determine is:

  1. Does the game crash when you’re doing nothing, or
  2. Does the game crash in response to an action you’re made in the game.

The memory graph isn’t growing then there isn’t a memory leak. (Obviously memory is allocated and released as you play / move between worlds, etc.)

The only guaranteed crash I know of is this:
Buy plots with cubits
Cancel out of the animation
Run through an open portal immediately

Odds are low, but did you do this perhaps?

My game crashed three times yesterday. It happened in dodgebombs… each time I died in the lava. Many bombs were flying. I don’t think I was alone in this happening. I’m on PS4…

Confirmed, today, 3 times the game crashed on me (all 3 were while i’m in my base. Some people would say, get out of the base then and try it, so I did… went out into the wild… waited 10-15mins. no crash. went to 3 different worlds and there capitals with alot of structures, etc. waiting idle for 10-15mins, no crash. went back to my base, waited 10-15mins idle, crashed within that time. Logged back in, sat idle for 10-15mins, no crash (so it’s not 100% consistant)

Confirmed the memory log in and out of game doesn’t have any huge spikes. it’s either pretty much stable line or it’s a slight spike as i move to new areas for maybe 5-10secs, then it flat lines again as the new number. when siting idle in the areas testing this, and when the crash happens… there is absolutely no jump in memory allocation logged … in the mem graph or windows mem graph either, it’s nice and stable.

Would it help if I pasted the dumpcrash file to here for ya?

here is a snippet of the crash from the log… seeing some errors and warning, but these are not consistent between crashes.

[2020-05-03 15:42:15.452] [INFO] Same world: use2_t0_1(id:28)
[2020-05-03 15:42:15.452] [INFO] [use2_t0_1(id:28)] making portal 'id:35201 + Ps:?p>M:0’to ‘28’ active
[2020-05-03 15:42:15.452] [INFO] [use2_t0_1(id:28)] making portal 'id:35321 + ps:?p>M:0’to ‘28’ inactive
[2020-05-03 15:42:15.452] [INFO] Discarding dstRequiredChunks, dst world no longer available
[2020-05-03 15:59:28.114] [WARN] Resetting fog loading distance due to extreme drop (dev teleported?)
[2020-05-03 15:59:31.361] [WARN] Failed to build mesh: use2_t0_1(id:28)(id:28), lod 0, -124,-59
[2020-05-03 15:59:31.361] [WARN] Failed to build mesh: use2_t0_1(id:28)(id:28), lod 0, -124,-60
[2020-05-03 15:59:31.361] [WARN] Failed to build mesh: use2_t0_1(id:28)(id:28), lod 0, -124,-61
[2020-05-03 15:59:31.361] [WARN] Failed to build mesh: use2_t0_1(id:28)(id:28), lod 0, -125,-60
[2020-05-03 15:59:31.361] [WARN] Failed to build mesh: use2_t0_1(id:28)(id:28), lod 0, -125,-61
[2020-05-03 15:59:31.412] [WARN] Failed to build mesh: use2_t0_1(id:28)(id:28), lod 0, -128,-60
[2020-05-03 15:59:31.427] [WARN] Failed to build mesh: use2_t0_1(id:28)(id:28), lod 0, -128,-61
[2020-05-03 15:59:31.428] [WARN] Failed to build mesh: use2_t0_1(id:28)(id:28), lod 0, -129,-60
[2020-05-03 15:59:31.429] [WARN] Failed to build mesh: use2_t0_1(id:28)(id:28), lod 0, -128,-62
[2020-05-03 15:59:31.429] [WARN] Failed to build mesh: use2_t0_1(id:28)(id:28), lod 0, -129,-61
[2020-05-03 15:59:31.545] [WARN] Failed to build mesh: use2_t0_1(id:28)(id:28), lod 0, -139,-59
[2020-05-03 15:59:31.545] [WARN] Failed to build mesh: use2_t0_1(id:28)(id:28), lod 0, -143,-44
[2020-05-03 15:59:31.844] [WARN] TimestampBoost changed for use2_t0_1(id:28). was 0.250000, now 0.125000
[2020-05-03 15:59:32.014] [WARN] Resetting fog loading distance due to extreme drop (dev teleported?)
[2020-05-03 15:59:46.660] [WARN] TimestampBoost changed for use2_t0_1(id:28). was 0.125000, now 0.250000
[2020-05-03 15:59:47.660] [WARN] TimestampBoost changed for use2_t0_1(id:28). was 0.250000, now 0.125000
[2020-05-03 15:59:47.843] [WARN] TimestampBoost changed for use2_t0_1(id:28). was 0.125000, now 0.250000
[2020-05-03 15:59:53.410] [WARN] TimestampBoost changed for use2_t0_1(id:28). was 0.250000, now 0.125000
[2020-05-03 16:00:05.685] [WARN] TimestampBoost changed for use2_t0_1(id:28). was 0.125000, now 0.250000
[2020-05-03 16:00:33.443] [INFO] [use2_t0_1(id:28)] making portal 'id:35201 + Ps:?p>M:0’to ‘28’ inactive
[2020-05-03 16:00:33.443] [INFO] Discarding dstRequiredChunks, dst world no longer available
[2020-05-03 16:00:50.041] [INFO] Got ClosedStorage Data (use2_t0_1(id:28):id:3854) w/ 403B
[2020-05-03 16:00:52.091] [INFO] Got ClosedStorage Data (use2_t0_1(id:28):id:3853) w/ 1678B
[2020-05-03 16:04:25.100] [INFO] HandleDeletedWorld(222) Byap>A#Sus*~maraDth7RY;dyhO{#mMKtDSEgpc)
[2020-05-03 16:04:25.100] [ERROR] failed to get world data (???(id:222))
[2020-05-03 16:04:49.765] [INFO] Got ClosedStorage Data (use2_t0_1(id:28):id:3855) w/ 501B
[2020-05-03 16:05:38.064] [INFO] Recording static attribute component archetype Block:8013387609888467272. Total = 8
[2020-05-03 16:06:08.248] [INFO] c:\users\autobuild.jenkins\workspace\boundless-win64-deploy\native\src\core\tzprocess.cpp:148 (turbulenz::sMinidumpCallback) Process crashed and minidump was written to C:\Users\temil\AppData\Local\Turbulenz\Boundless\tblz_crashdump_891d9fed_5834d9d8-ddef-4ef4-bc4f-551b36355765.mdmp

here is the system specs from the log…

[2020-05-03 15:39:25.155] [INFO] c:\users\autobuild.jenkins\workspace\boundless-win64-deploy\native\src\core\win\winsysteminfo.cpp:430 (turbulenz::GetSystemInfo) SystemInfo:
[2020-05-03 15:39:25.155] [INFO] c:\users\autobuild.jenkins\workspace\boundless-win64-deploy\native\src\core\win\winsysteminfo.cpp:431 (turbulenz::GetSystemInfo) cpuDescription : Intel(R) Core™ i9-9900K CPU @ 3.60GHz
[2020-05-03 15:39:25.155] [INFO] c:\users\autobuild.jenkins\workspace\boundless-win64-deploy\native\src\core\win\winsysteminfo.cpp:432 (turbulenz::GetSystemInfo) cpuVendor : GenuineIntel
[2020-05-03 15:39:25.155] [INFO] c:\users\autobuild.jenkins\workspace\boundless-win64-deploy\native\src\core\win\winsysteminfo.cpp:433 (turbulenz::GetSystemInfo) numPhysicalCores : 8
[2020-05-03 15:39:25.155] [INFO] c:\users\autobuild.jenkins\workspace\boundless-win64-deploy\native\src\core\win\winsysteminfo.cpp:434 (turbulenz::GetSystemInfo) numLogicalCores : 16
[2020-05-03 15:39:25.155] [INFO] c:\users\autobuild.jenkins\workspace\boundless-win64-deploy\native\src\core\win\winsysteminfo.cpp:435 (turbulenz::GetSystemInfo) ramInMegabytes : 32701
[2020-05-03 15:39:25.155] [INFO] c:\users\autobuild.jenkins\workspace\boundless-win64-deploy\native\src\core\win\winsysteminfo.cpp:436 (turbulenz::GetSystemInfo) frequencyInMHz : 3600
[2020-05-03 15:39:25.155] [INFO] c:\users\autobuild.jenkins\workspace\boundless-win64-deploy\native\src\core\win\winsysteminfo.cpp:437 (turbulenz::GetSystemInfo) architecture : x86_64
[2020-05-03 15:39:25.155] [INFO] c:\users\autobuild.jenkins\workspace\boundless-win64-deploy\native\src\core\win\winsysteminfo.cpp:438 (turbulenz::GetSystemInfo) osName : Windows 10 Pro
[2020-05-03 15:39:25.155] [INFO] c:\users\autobuild.jenkins\workspace\boundless-win64-deploy\native\src\core\win\winsysteminfo.cpp:439 (turbulenz::GetSystemInfo) osVersionMajor : 6
[2020-05-03 15:39:25.155] [INFO] c:\users\autobuild.jenkins\workspace\boundless-win64-deploy\native\src\core\win\winsysteminfo.cpp:440 (turbulenz::GetSystemInfo) osVersionMinor : 2
[2020-05-03 15:39:25.155] [INFO] c:\users\autobuild.jenkins\workspace\boundless-win64-deploy\native\src\core\win\winsysteminfo.cpp:441 (turbulenz::GetSystemInfo) osVersionBuild : 9200
[2020-05-03 15:39:25.155] [INFO] c:\users\autobuild.jenkins\workspace\boundless-win64-deploy\native\src\core\win\winsysteminfo.cpp:442 (turbulenz::GetSystemInfo) userLocale : en_US

and while we are at it, temp monitors in CPUID, MSI Dragon Center, and Intel Performance Monitor all show same temps of min 35c and max 56c … which don’t exceed the max temp of 80+ for my vid card (GTX 2080 Super Hybrid) … When playing ark, etc… I get up to around 61c, and never have an issue.

I have confirmed that there is no overclocking for anything in any software or bios settings (just to rule that out).

Ohh, and I have 3 other players that I play with in the same factory/base I have that this seems to keep happening in…and none of them have the same issue I’m having. 3 of them play on PC and 1 plays on PS4.

anything you else you from me, let me know. I can play the game, but it’s really getting anoying when I’m having to re-login every few mins at random.

EDIT :: to answer the person asking, I have what I consider a small farm, maybe 500 plots in front of my base, but that’s the largest farm within visual range that I’m aware of.

Also, my base doesn’t have any lava, and didn’t die during the times this happens. Also not throwing any bombs, etc. .so don’t think it’s related to what Ginabean mentioned, also she is on PS4, I’m on PC… not sure if that’s a factor, even though others on PC and PS4 can be in my base with no issues.

Location of your beacon + world?

World :: Trior
Location :: 740N -2,098E

to add to all the previous, not sure if this is coincidental ,but since the last game crash… I always unplugged my Oculus Rift S from my PC, since it is hardware registered in the system as a mic and technically considered an added monitor (somewhat) … I figured, why not… So far, no game crash since unplugging that, however it doesn’t always do it so not sure, don’t think it’s enough data collected so far, but I’ll keep you updated if it happens again.

well, seems that unpluging my VR headset didn’t have anything to do with it. Game Crash still happened, but this time it happened in the middle of “Illuminati” town … I wasn’t even in my base, so i’m thinking it’s not my base specific. here is the ending snippet of the log file.

[2020-05-03 18:46:23.646] [INFO] WebSocket closed for sanctum(id:4294967295)
[2020-05-03 18:46:24.362] [INFO] > ClientTrustedSystem::OnEntityBecameTrusted: id:8709507 is now trusted on 52227664.500000
[2020-05-03 18:49:49.382] [INFO] Got ClosedStorage Data (use2_t0_1(id:28):id:3855) w/ 497B
[2020-05-03 18:50:02.705] [INFO] tip.mMsg
[2020-05-03 18:53:09.942] [INFO] Got ClosedStorage Data (use2_t0_1(id:28):id:3852) w/ 674B
[2020-05-03 18:58:52.447] [INFO] [use2_t0_1(id:28)] making portal 'id:35201 + Ps:?p>M:0’to ‘28’ active
[2020-05-03 18:58:54.067] [INFO] Same world: use2_t0_1(id:28)
[2020-05-03 18:58:54.067] [INFO] [use2_t0_1(id:28)] making portal 'id:35321 + ps:?p>M:0’to ‘28’ active
[2020-05-03 18:58:54.067] [INFO] [use2_t0_1(id:28)] making portal 'id:35201 + Ps:?p>M:0’to ‘28’ inactive
[2020-05-03 18:58:54.067] [INFO] Discarding dstRequiredChunks, dst world no longer available
[2020-05-03 18:58:58.124] [INFO] [use2_t0_1(id:28)] making portal 'id:35321 + ps:?p>M:0’to ‘28’ inactive
[2020-05-03 18:58:58.124] [INFO] Discarding dstRequiredChunks, dst world no longer available
[2020-05-03 19:00:50.527] [INFO] c:\users\autobuild.jenkins\workspace\boundless-win64-deploy\native\src\core\tzprocess.cpp:148 (turbulenz::sMinidumpCallback) Process crashed and minidump was written to C:\Users\temil\AppData\Local\Turbulenz\Boundless\tblz_crashdump_891d9fed_55259189-53cd-42e9-a347-6820224b334a.mdmp

I apologize in advance if this isn’t relevant but a similar thing happened to me–random crashes at random times, often in town or in base, on MacOS. Starting only on Apr 28 8pm EST.

Something I also found is that if I pressed the ` key to free the mouse and then esc quickly in succession that often caused a crash but who knows. I eventually just gave up and downloaded the game on PC.

Below I copy paste a part of the error log:

Error Log
Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       EXC_I386_GPFLT
Exception Note:        EXC_CORPSE_NOTIFY

Thread 0 Crashed:: MainThrd  Dispatch queue: com.apple.main-thread
0   boundless.dylib               	0x0000000104535ce6 unsigned long std::__1::__hash_table<std::__1::__hash_value_type<unsigned long, std::__1::function<void ()> >, std::__1::__unordered_map_hasher<unsigned long, std::__1::__hash_value_type<unsigned long, std::__1::function<void ()> >, std::__1::hash<unsigned long>, true>, std::__1::__unordered_map_equal<unsigned long, std::__1::__hash_value_type<unsigned long, std::__1::function<void ()> >, std::__1::equal_to<unsigned long>, true>, std::__1::allocator<std::__1::__hash_value_type<unsigned long, std::__1::function<void ()> > > >::__erase_unique<unsigned long>(unsigned long const&) + 6
1   boundless.dylib               	0x00000001045358c9 turbulenz::particlesystem::ParticleGeometry::Unregister(unsigned long) + 25
2   boundless.dylib               	0x0000000104567964 turbulenz::particlesystem::ParticleRenderable::~ParticleRenderable() + 52
3   boundless.dylib               	0x0000000104567a7e turbulenz::particlesystem::ParticleRenderable::~ParticleRenderable() + 14
4   boundless.dylib               	0x00000001044ff22b turbulenz::SceneNode::~SceneNode() + 267
5   boundless.dylib               	0x000000010438c2bf turbulenz::boundless::renderer::occlusion::Node::~Node() + 31
6   boundless.dylib               	0x00000001035f0bfd turbulenz::boundless::ParticleInstanceUserData::~ParticleInstanceUserData() + 45
7   boundless.dylib               	0x0000000104536bba turbulenz::particlesystem::ParticleInstance::~ParticleInstance() + 42
8   boundless.dylib               	0x00000001045495b8 turbulenz::particlesystem::ParticleManager::Update(turbulenz::particlesystem::ParticleManagerScene&, float) + 120
9   boundless.dylib               	0x0000000103577347 turbulenz::boundless::GameEffectManager::Update(float, double) + 263
10  boundless.dylib               	0x0000000103613595 turbulenz::boundless::GameWorldManager::UpdateGameWorld(turbulenz::boundless::GameWorld&, float, turbulenz::boundless::ChunkDestroyParams&, bool) + 437
11  boundless.dylib               	0x00000001035943cb turbulenz::boundless::GameManager::UpdateGame() + 2363
12  boundless.dylib               	0x0000000103f933ba turbulenz::boundless::GamestatePlaying::Update() + 138
13  boundless.dylib               	0x0000000103f9188f turbulenz::boundless::GamestateManager::Update() + 47
14  boundless.dylib               	0x000000010338d5e3 turbulenz::boundless::Application::UpdateGame() + 483
15  boundless.dylib               	0x000000010338d28b turbulenz::boundless::Application::Update() + 299
16  boundless.dylib               	0x0000000103384c5d turbulenz::boundless::Application::MainStateLoop() + 397
17  boundless.dylib               	0x0000000104681cbf turbulenz::RunLoop::Tick() + 127
18  boundless.dylib               	0x0000000104632922 turbulenz::Platform::Tick() + 34
19  boundless.dylib               	0x0000000104602f34 turbulenz::ApplicationBase::Tick(unsigned long long*) + 212
20  boundless.dylib               	0x0000000104606463 -[NativeEntryView animate:] + 99
21  com.apple.Foundation          	0x00007fff2bf53739 __NSFireTimer + 83
22  com.apple.CoreFoundation      	0x00007fff29de9014 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20
23  com.apple.CoreFoundation      	0x00007fff29de8c87 __CFRunLoopDoTimer + 1095
24  com.apple.CoreFoundation      	0x00007fff29de878a __CFRunLoopDoTimers + 346
25  com.apple.CoreFoundation      	0x00007fff29ddfd5b __CFRunLoopRun + 2427
26  com.apple.CoreFoundation      	0x00007fff29ddf153 CFRunLoopRunSpecific + 483
27  com.apple.HIToolbox           	0x00007fff290c9d96 RunCurrentEventLoopInMode + 286
28  com.apple.HIToolbox           	0x00007fff290c9b06 ReceiveNextEventCommon + 613
29  com.apple.HIToolbox           	0x00007fff290c9884 _BlockUntilNextEventMatchingListInModeWithFilter + 64
30  com.apple.AppKit              	0x00007fff2737aa73 _DPSNextEvent + 2085
31  com.apple.AppKit              	0x00007fff27b10e34 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 3044
32  gameoverlayrenderer.dylib     	0x00000001032fd71e -[NSApplication(SteamOverrideNextEvent) steamhooked_nextEventMatchingMask:untilDate:inMode:dequeue:] + 76
33  com.apple.AppKit              	0x00007fff2736f885 -[NSApplication run] + 764
34  com.apple.AppKit              	0x00007fff2733ea72 NSApplicationMain + 804
35  libdyld.dylib                 	0x00007fff51c37015 start + 1

hey James, just checking if anyone had time to look at the crashdump file to see what is the cause to the repeat crashes?

I sent you a PM about it. Please give the request a try and report if it helps.

1 Like

When it was happening to me, I was on Trior, as well. Not in iLLumiNaughty, but on the planet.