Starfield crashing while in BUILD MODE. Same issue on two computers.

[Unexpected Outcome]

So, something new. So far I've uninstalled the game three times, deleted the 5 mods I had from Nexus, on Vortex, and disabled and in some cases deleted every single mod I had from CC.
Even without a single mod, the game suddenly crashes when I delete an object while in build mode. Puzzling and frustrating.

Everything was running fine yesterday and then today, WHAM, problems. Bios and
Graphics driver is up to date, Windows is up to date, Security isn't blocking the game, validated files too. Even tried uninstalling and reinstalling Steam, cleared all the files I could find, first.


Even made sure that I'm not running overlays, or other programs, and dusted the laptops vents to make sure the air flow was sufficient.
I'm not especially good at rooting around in program files or anything, so I'd be lost if I have to move stuff around or change anything significant.
Have no idea why this is happening.
Computer is an Asus G 18 rtx 4080 , 2 tb, 32 gb. i9

Also have an Alienware M18 R, same specs as the Asus. Starfield is installed but wasn't played in over 4 months. Totally vanilla game, No Nexus/Vortex or CC ever installed.
In this instance Starfield freezes as soon as I enter build mode. Otherwise the game runs just fine, offline as usual.

I figure that I'm probably the only one having this issue, but maybe someone would have an idea of what might be going on.

[Vlad 254]

Ok so you had mods installed and then something changed, maybe you added one lately or removed one. I'm not sure what all you have there or I should say had. So with everything removed you not only have data baked into your saves (which is normal) and most likely have some lingering files (which can happen anytime you remove mods).

Do this but follow everything in the guide:
https://steamcommunity.com/sharedfiles/filedetails/?id=3199872428
Take your time it's much easier than it may look.

[Unexpected Outcome]

Ok, I did everything possible. Followed the guide, removed files, removed Steam, reinstalled the vanilla version, and the game is freezing in build mode when in an outpost building, On ship or standing outside at outpost, game crashes as soon as I delete an object. .
Something other than my game files, or my computers is at fault.

[Corinze]

If both laptops are 13th or 14th gen CPUs, you would most likely beneficent from the new bios updates for 600 and 700 series boards.

[Unexpected Outcome]

Originally posted by Corinze:

If both laptops are 13th or 14th gen CPUs, you would most likely beneficent from the new bios updates for 600 and 700 series boards.

I just updated the BIOS on both the other day. There's nothing else available to change.

[Corinze]

The game should be purring on those specs. It is really odd the issue you have going.

[pike]

turn off steam cloud for the game , when you reinstall it validate files it's being returned to it's broken state most likely

[Unexpected Outcome]

Originally posted by pike:

turn off steam cloud for the game , when you reinstall it validate files it's being returned to it's broken state most likely

Thank you I appreciate your input.
I've done the uninstalling and reinstalling the game several times, I also did the same with Steam entirely. Tried everything with Steam Cloud both off and on, more than once. Still no improvement. My Alienware never used Steam Cloud and wasn't synced to the game I ran on the Asus, And it too is crashing. Have validated the files at least six times, nothing unusual is flagged on either device.
Graphics were double checked, used the Bethesda Support guide to make sure that I'm not missing something, it's all normal.
This is bizarre.

update: Decided to give it one more try, made sure that Steam Cloud was off and uninstalled the game. Made sure that all creations were removed via the Bethesda support site, poked around files and had no idea what I was looking at, deleted something. Reloaded the game, without cloud ( thank you Pike) deleted a bunch of saves and progress in the game, Logged into my Bethesda account and made sure that I removed every single creation mod that I had used, went back about two weeks in my saves and gave it a go.
IT WORKED!!! A lot of ground to cover, but still I'm happy just to not crash at this point! Was also able to reinstall Vortex and my Nexus mods, and now everything seems to be back to normal.

[pike]

to not loose your progress in the future you can make a clean save by sleeping for 48hrs , that resets the cells in the game , at least that's how i would do it in past bethesda games, i havent had to do it in starfield so i cant say for certain if it still works,
oh and , keep steam cloud off

[Vlad 254]

Originally posted by Unexpected Outcome:

Originally posted by pike:

turn off steam cloud for the game , when you reinstall it validate files it's being returned to it's broken state most likely

Thank you I appreciate your input.
I've done the uninstalling and reinstalling the game several times, I also did the same with Steam entirely. Tried everything with Steam Cloud both off and on, more than once. Still no improvement. My Alienware never used Steam Cloud and wasn't synced to the game I ran on the Asus, And it too is crashing. Have validated the files at least six times, nothing unusual is flagged on either device.
Graphics were double checked, used the Bethesda Support guide to make sure that I'm not missing something, it's all normal.
This is bizarre.

update: Decided to give it one more try, made sure that Steam Cloud was off and uninstalled the game. Made sure that all creations were removed via the Bethesda support site, poked around files and had no idea what I was looking at, deleted something. Reloaded the game, without cloud ( thank you Pike) deleted a bunch of saves and progress in the game, went back about two weeks and gave it a go.
IT WORKED!!! A lot of ground to cover, but still I'm happy just to not crash at this point!

You skipped section 4 of the guide. As pike pointed out that is important. I'm glad you got it worked out. Enjoy my man.

[Unexpected Outcome]

Hi Vlad, I didn't skip it, but yes I only have a C drive on the Asus, and I'll be honest, I'm 66 and lucky if I manage to do anything without causing a calamity. I was scared to move any file, because I don't know what's safe to touch and what isn't.
Re Steam Cloud, I didn't know that there is also a steam cloud setting in the main settings. I was using the one in I think properties, the drop down where you validate game files. Apparently that wasn't the right one.
But I do and did, appreciate your input and guide. Thank you

I did notice that there are files that you and Bethesda identified that I can't find in this computer, I found them on my Alienware, but not this Asus. A mystery.

[Unexpected Outcome]

Originally posted by Corinze:

The game should be purring on those specs. It is really odd the issue you have going.

Yeah, Both the Asus and the Alienware are fantastic, and I usually never encounter problems. That's what really threw me off.
I had added one new mod to my Asus game from the Creation page, and that's when it all fell apart. BUT I never had mods on my Alienware, so I'm not sure why I had the same problem there. Something I can figure out later I guess.

[Unexpected Outcome]

Originally posted by pike:

to not loose your progress in the future you can make a clean save by sleeping for 48hrs , that resets the cells in the game , at least that's how i would do it in past bethesda games, i havent had to do it in starfield so i cant say for certain if it still works,
oh and , keep steam cloud off

Thank you!! I will do that .

[Bandit]

I've had the same, or similar problem at a few outposts over the years. I was never able to repair the problem, so I just abandoned those outposts.

I think the problem is caused by a bugged outpost. When you go into build mode code is likely loaded in anticipation of you deleting, creating, and moving stuff. If the data, possibly a database, where that information goes is corrupt, the code cannot complete those steps in a way that the software can't handle, and kaboom.

They need to add code to inspect, and repair issues with the outpost data record.