Starfield Crashing when fast travelling

[a2raya]

Game just started crashing more now when i fast travel.. i tried FSR off and same bs. over 8 years in the making and this is what Bethesda can offer..

[Threinfhir]

Just started with me too. Level 124, play time of 11d 20h 59m, been happening about a week now. Happens on both Xbox and PC (don't even own on Steam) when I fast travel via scanner. Been zipping around Serpentis System engaging ships and it's now crashing to desktop almost every time I travel. Again, both on Xbox and PC, no warning or error. Quite annoying, anybody else having this or should I start a massive email campaign to Beth?

[AoD_lexandro]

Update your systems.

Microsoft released a new version of windows. Windows updates that are waiting in the background are known to cause random CTD's as it tries to give you an "alert" to restart and can crash the graphics driver.

Also if you are an AMD user update to the the new driver released today. It has more stability and better frame pacing for this game.

[billlcarr]

Just started happening to me as well. I was traveling around Serpentis, and twice now when using the scanner to travel to a different planet, it crashed to desktop at the point just before you load into the new area.

[billlcarr]

Originally posted by AoD_lexandro:

Update your systems.

Microsoft released a new version of windows. Windows updates that are waiting in the background are known to cause random CTD's as it tries to give you an "alert" to restart and can crash the graphics driver.

This isn't random. It only happens when you travel using the scanner, and it always happens at the exact same point. The only thing random about it is that it doesn't happen EVERY time you travel (at least for me).

[JeanLoop]

Hello

I have over 500 hours of gameplay.
I have freezes of varying length, sometimes even the screen remains blocked (and I use BES to limit the freezes).
It must be said that my machine is at a minimum (GTX 1060 6GB, 16 GB ram, I5 4690).

But, never during these 500 hours, I have a crash returning to the desktop.

For several days, however, fast travel or landing at an outpost causes a crash with a return to the desktop and the game becomes unplayable.
After several attempts by reloading previous saves, I understood that the game becomes unplayable when the size of the saves reaches 50MB (which is inevitable, the size of the saves always increases).

In my case I got out of it by jumping into the unit, a new new game plus part reducing the size of the saves to 3 or 6MB. But it was not my intention to start again with a new game + anymore.

(Sorry for my bad English)

[Gonzo850]

Verify integrity of game files after updates.

[billlcarr]

Originally posted by Xenophobe:

disable 'save on travel' and see if it helps, it's a classic game engine bug.

Already have all "save on" options disabled

[Baalzebul]

Started having this same kind of thing happen to me starting a few days ago. At first I thought it was a bug, because the game crashed about every 5-10 load screens. Especially bad when fast travelling. After updating my AMD drivers and completing a windows update that was running in the background, I thought this would fix the crashing issues. I was wrong. Now, the game is even WORSE than before I updated my software. Now, instead of just crashing when loading a new scene or fast travelling,, the game is now just crashing at any random spot at any time for no apparent reason.

There's really no playing the game at this point. Even if I try and do a quick-save after every mission or transaction, the game has crashed on quick-save as well.

The only thing I can do at this point is verify my game files and try and see if that fixes the problem. If it doesn't, then I'm out of options until Bethesda decides to try and fix this issue.

[billlcarr]

I loaded up the most recent DMP file into WinDBG and found this:

0x1eb0 0x0 Starfield!Scaleform::System::HasMemoryLeaks+0x2c4b810 (00007ff6`a5d03310) Main

and this:

EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ff69ef4e23c (Starfield!agsSetDisplayMode+0x000000000023855c)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 0000000000000000
Attempt to write to address 0000000000000000

PROCESS_NAME: Starfield.exe

WRITE_ADDRESS: 0000000000000000

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000001

EXCEPTION_PARAMETER2: 0000000000000000

Maybe someone here with more knowledge than me can say whether this has any significance.

[_oBSOLEte_]

Originally posted by Xenophobe:

if you're on windows 11, it could be one of their updates breaking things again ... or a gpu driver update breaking things again ... or, if you're in the starfield beta, bethesda breaking things again ... so many methods of breakage.

OPs post date is 9 september...

[billlcarr]

Originally posted by Xenophobe:

@billlcarr

You may have some corrupted system files. Windows updates can cause issues like this at times. Run these windows tools as follows:

Thanks, will do

[decimus28]

Originally posted by billlcarr:

I loaded up the most recent DMP file into WinDBG and found this:

0x1eb0 0x0 Starfield!Scaleform::System::HasMemoryLeaks+0x2c4b810 (00007ff6`a5d03310) Main

and this:

EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ff69ef4e23c (Starfield!agsSetDisplayMode+0x000000000023855c)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 0000000000000000
Attempt to write to address 0000000000000000

PROCESS_NAME: Starfield.exe

WRITE_ADDRESS: 0000000000000000

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000001

EXCEPTION_PARAMETER2: 0000000000000000

Maybe someone here with more knowledge than me can say whether this has any significance.

So bad news on this. The function/code pointed too at
Offset 0x23855c
From Starfield!agsSetDisplayMode
(the dump appears to be Starfield 1.7.36.0 version, which has this offset) is known to cause crashes in relation to saves. Usually saves that have been played for a while. None of the beta fix the issue yet. Good news is new saves will fix it(until it somehow triggers again). Those saves can be shared if you want someone else to have the fun of triggering the crash on their own system.

[billlcarr]

Originally posted by decimus28:

So bad news on this.

So are you saying this is a known issue? Is Bethesda aware of it?

And if you mean starting a new game fixes it, that's not a fix lol

I've opened a ticket with them and provided my DMP files, by the way. Fingers crossed.

[decimus28]

I have reported it too but the more the better. I've gone over 40 or so dumps with the exact issue and done some debug tracing with it. Always the same line of code.

[billlcarr]

Originally posted by decimus28:

I have reported it too but the more the better. I've gone over 40 or so dumps with the exact issue and done some debug tracing with it. Always the same line of code.

Thank you!