Frequent Crashes / Endless Crashing - Please Help!

Support and Bug Reports
210

Update:

I’ve still never really had a game related crash and I’m 60 hours in.

My friend who crashes every 5 minutes changed out ALL of his ram and he played a few hours on SP and then we played about 4 hours MP with zero crashes and he said it ran much better overall. I know it’s not a lot of time to “verify” a fix, but it’s a significant difference since I was not exaggerating the “every 5 minutes”.

I still think it’s a code issue that probably happens with certain combinations of ram types and/or amounts. I know the armchair scientists will say no, but having ram is common between all console and PC hardware.

1 Like
211

Yeah just played 8 min and it send me straight back do desktop

My ram is 6 days old so guess that wont be the prob :slight_smile:

1 Like
212

I died 7 hours into my new permadeath save when fatfingering my inventory while dodging rockets… Perfectly fine gameplay through Archipelago and down Kåleby omw to Torsbergs. No crashes at all yet.
I might continue this guy eventhough he died just to see if/when the crashing starts.

1 Like
213

I didnt need a reply pal , i know the score i have been here since launch you have been here 4 days so unless you are a secret dev why are you going around the forum like a Moderator with assurance that you know more than our main Mod :point_right: . @Zesiir is the goto guy so when he assure us we know all is well . i was adding to a bug report of the crashes on ps4 so the devs can see every console and pc affected in one place , thanks anyhow @RighteousTheory im assured you mean well :rofl::+1: , i had to ask >> you said further up the posts ‘’ We apologize for your experience ‘’ , who is ’ WE ’ ? ,

3 Likes
214

The game was unplayable when it first came out and is still more or less in the same condition six months later. I came back cause I saw the dlc and said to myself, “well hey now, there’s dlc. Avalanche must have pulled it together, right on!” WRONG. The devs said in a previous post that this issue is a “small handful of people”. Spoiler alert: this community is a small handful of people.
There’s no update coming till next year (devs stated in their post) and it seems criminal to sell an unplayable product, even at a discounted price. They add one tiny little change to the game and the entire system seemingly disintegrates. The devs should be more careful not adding things willy nilly in the game, to ensure this repeated offense doesn’t continue. So many people are picking up this game then refunding it because of the state its in.

2 Likes
215

I’m on PS4 and have always had very frequent crashes while playing multiplayer. It’s unfortunate because it’s making me not want to play the game anymore. Hopefully they get it resolved soon.

1 Like
216

Since June the Development team has done an amazing job IMO. Lots of fixes, new FREE content & a very low cost DLC. That said the new (for me) crashing in single player & yesterday in MP that (again for me) started with the last update is very annoying & since it happens so much when I am streaming/promoting the game it is embarrassing. I do believe in this team even though they have been silent since the update on these new (for me & some others) crashes (I am chalking it up to the Holidays for now).

Thanks,
SPP

1 Like
217

So, from having being crash free for weeks, it started again today. On both occasions, it was after prolonged fights that involved almost every single enemy type in the game at once; seekers, runners, hunters, tanks and of course a bunch of ticks, in great numbers (only one tank).

Since I was playing solo, the fights would last aprox 10 minutes, with lots of kiting and taking snapshots. First location was Hjalmars stuga in the Mountains region, second location was on Himfjäll, up on the plateau between Gäddön safehouse and Himarvet.

Both locations are notorious for spawning a shitload of enemies at once on occasions, and when this happens I think there’s a higher chance for these crashes to occur.

1 Like
218

That is exactly what I thought. Thanks, doctor.

If your RAM is stable on your platform, and you can make sure with tools such as HCI Memtest, then it is stable with GZ. Please don’t post any guesswork here. People suffering from game crashes have enough on their plate already.

2 Likes
219

Amen, I feel your pain. I have the same issue, and there are a lot of others, from all the comments that I’ve read, who have the same problem. I guess we all have “crappy rigs” that can’t run the game, right. For a problem to be this widespread, you can’t just pass it off on the customer’s computer. That is like saying my electric power keeps going out because there are birds on the power lines.

2 Likes
220

I have had only a handful of inexplicable crashes (that are not related to my “own doing”) in 284 hours of playing since I started in August.

I tried the Alpine DLC for an hour or 2 at the end of November but I haven’t really been playing (recreationally) since because other pressing occupations.

So a couple of days ago I finally had the time and I thought it would be a nice warmup to go on a Tank/Rival killing spree before diving further into the Alpine DLC.
(And also because I -still- don’t have that darned 5* AG5 (I’m actually starting to doubt its existence). Edit: never mind. I actually got it the night after posting this. I should complain more often it seems … :stuck_out_tongue_winking_eye:

So off I went on my standard FNIX-Tank-run around the map … and after 15 minutes the crashing spree started. Here are the session durations (in minutes):

Day 1: 15, 6, 9, 2.5, 17, 2, 19, 10, 69, 25, 19, 30. (12 CTD’s in 3h44m)
Day 2: 24, 22, 25, 14, 8, 5, 5. (7 CTD’s in 1h43m)

As some have said before, it indeed seems to be related to the spawning of rivals.

Every time I got killed by a FNIX Tank’s mortar attack: instant crash.
Every time I killed a FNIX Harvester: instant crash.
When I got killed by a FNIX Hunter: instant crash.
The game also crashed one or 2 times without a fight going on whatsoever (maybe I crossed a region border and triggered a rival spawn?).
The game even crashed one time only seconds after I re-spawned.

Levels throughout the regions were something like 1, 3, 8, 10 and 11 and regardless of the region I was in, it was a crash fest.

But … when I killed a FNIX Tank: no crash and also no Rival.

That was weird. In all cases when the game crashed it was in the (usual or actual) vicinity of a FNIX Tank.

So I started to avoid the FNIX Tank hot spots and fast traveled to the edges of the regions where the lower level machines roam and where I don’t go during my standard FNIX-Tank-run.

I had myself deliberately killed by some military class Runners and guess what … that Runner turned into a Rival. I went to all regions and had myself killed by military/prototype machines (and the Proto Tank at the start of South Coast). After that, I played for another hour and Rivals spawned like usual again and I had no crash at all.

Today I resumed my regular FNIX-Tank-run for almost 3 hours and Rivals spawned all over the map, including FNIX Tank Rivals. (Although I have to say I go at them right away and I don’t wait for more Rivals to spawn).

The game actualy did crash twice, however, in a slightly different way. The game froze at the moment I shot off the second weapon of a Tank (1x Prototype and 1x Apocalypse) and it took a couple of seconds before it actually CTD’s. However, I also shot off the weapons of several FNIX Tanks and nothing weird happened.

I have absolutley no idea if this is consistent or predictable on the long run (or even at all) but maybe it’s an idea to try out.

Needless to say that there is something very buggy going on on multiple levels.

1 Like
221

Lately, I’ve started to try and save progress in the middle of fights if I think the game might crash, and I think it may work, but would need more people try it out.

What I do is simply shuffle something around in the inventory during fights. The game should save whenever you’re doing something in the inventory, and with that, should save progress, so that you don’t have to start a fight vs a tank all over again.

From the little testing I’ve done so far, it seems to work, but as I said, would like it if someone else could try this method out.

222

So, another observation. Using the method described above, I had an apoc tank saved in a state where it had 11% health left. The tank was located near Damfallet in the Mountains region. Region score at the time was ~3500 or so, and it had one active rival @ lvl 1 in the region.

So, I when I killed this tank, the game would crash. Started up again, went out from safehouse Älgstugan, and went straight to Damfallet to see if the tank was still there, and sure enough, it was, and still at 11%. Killed it again - crash.

Repeated another couple of times and the game would crash every single time I killed this tank. This would happen I’d guess five or six times in a row.

Decided to head to another location, killed a seeker (in another region), then returned to the tank yet again. Killed it, and this time the game didn’t crash.

For me, the crashing is very consistent, in that it ONLY happens after having killed something. I wonder how many times I could have repeated the above cycle and have the game crash - indefinitely?

223

I’ve seen quite a few reports saying it crashed after the weapons were knocked off a tank. I’ve seen it too, though the tank immediately tried to start to run at us. I don’t think it had a good path.

1 Like
224

Try what out, what is your conclusion? I got a little lost in the middle part.

1 Like
225

So I installed some Windows updates today. Both were security related and one was to do with .Net. That’s pretty much the only change in my system. Today I’m getting a whole lot of BEX64 crashes now which don’t get caught by Crash Reporter. I’m not sure if the Windows updates may have something to do with it or not… of course… because this game seems to have some kind of flaw that just causes all kinds of weird memory related problems and of course BEX64 is related to the DEP system which is supposed to stop applications which try to write to protected memory locations. I’ve also got a nVidia driver-related service error that crashed the game which I haven’t seen for a couple of weeks. There was just one day when I got a bunch of them and then I never saw it again until today. I have the latest nVidia driver installed. I always use DDU to install new drivers as well so everything is always clean and shiny. I removed and reinstalled the .Net system since it could have some implications but no dice there either. It is so strange how this game finds so many reasons to crash but the one thing they almost all have in common is being related to memory violations. As for the parts of the game that trigger it is seems to be almost always related to Rival spawning or leveling, machine spawning/being destroyed, or interacting with an object such as opening a door/loot box/looting a machine. I can hang out in areas without machines for hours generally but when I get to a place they are supposed to be, or spawn, and there is a white noise burst instead of a machine appearing, problems lie ahead. Very frustrated that I can’t get any play time in yesterday or today due to the insane crashes. Clearing out all the Rivals a few days ago got me a lot of play time but now that area experience levels are rising and rivals are starting to spawn and level the crashes are ubiquitous. I just hate spending all my ammo on battles with big machines and crashing before I can reach their metal corpses to loot them.

226

Oh wait… there is one more thing that’s changed. I bought the DLC. I haven’t actually gone to the DLC area yet though so I’m not sure if unlocking that has contributed to the terrible crashing epidemic.

1 Like
227

Ok SkEyE, I made it here to report. I’ll post my issues shortly.

1 Like
228

Annnnndddddddd done.

230

Ghost sounds, Seeker exhaust flames, floating Fuel Cells (the ones that are supposed to actually be attached to machines), displaced gas tank flames, invisible guns (when shot off), invisible Runners (which actually move vegetation), duplicate attachments, reload bugs, etc, etc.

Of course, I may as well be (completely) wrong but I have a “feeling” it has something to do with “sub object pointers/references” which are not being handled correctly.

For example:
Maybe they are forgotten to be deleted from the machine entity (but are still being processed by the “render engine”) resulting in “lost” sub objects such as floating jets, ghost sounds, etc.
Or some object gets deleted and then accessed, resulting in access violations (or null pointer exceptions).
Or some object is “forgotten” to be attached (or to late) resulting in non-solid ground, floating Fuel Cells, etc.

But again. It’s just how it “feels” to me and it could just a as easily be as far from the truth as you can possibly imagine (which is often the case with programming). :slight_smile:

About that running … sometimes they come charge at you with blistering speed (as if you press fast forward on the running animation) without warning. Scared the crap out off me multiple times. :grimacing:

To stay out off the vicinity of FNIX Tank (or high level Machines in general, even) hot spots and try killing (or be killed by) lower tear machines. My FNIX Tank run consists of doing a nice circular trip around (several of) these locations:

Spoiler alert!
  • Stenmyra,
  • Anl 118 Färela
  • St. Maria Church
  • Muskudden Port Complex
  • F23 Överby Air Base
  • Kaptensvillan
  • Kyrkhöjden
  • Östervik Industriområde
  • Lennart’s Marin AB
  • Granhygget
  • Lövnäs
  • Alby Church

So, try to avoid this “circle” of locations. In stead, go to the centre of the island (south-west of the big lake for example) or to the south/west coast area’s and see if you get Rivals to spawn normally without crashing.

No idea if it will work for others (since there are obviously multiple causes for the crashes) but it seemed to have worked for me. At least for now, that is. :slight_smile:

3 Likes