Trying to dianose a CTD at start of the game.

[GrndZero]

Let me preface this by saying I am using MO2 for modding needs, on an AMD Ryzen system with a 2070RTX card. Nothing wrong hardware wise. I had been playing a heavily modded play thru and decided to try something different. I "removed" all my mods and started over with a select few that I always play with.

I was initially using the alternate startup but anytime I got close to Vault 111 or Sanctuary it would CTD. I looked at some F4SE logs and couldn't find anything so I decided to just blank out all mods and start the game from the Steam Launcher with a brand new save. I an get through the intro and get running out of the house, as soon as I get near the bridge to cross the creek, it crashes. I checked file integrity through Steam and it found some errors, fixed them and started the game back up, still crashing in the same spot. What I thought was a mod issue is now just a game issue. Short of nuking the game and reinstalling it, has anyone else run into the bridge that cause F4 to just crash there?

[HadToRegister]

Are you sure you have absolutely EVERYTHING from every mod removed?

Also, did you at any time edit your Fallout4.ini file for any of the mods?
Perhaps there's a setting in there that's wrong.

Or your FalloutCustom.ini etc.

[G4M3W1NN3R]

the Guranteed causes of Proximity based Crashe are:

 

1. Deleted Navmesh - (1 mods deletes it, another mod puts something in same location, instant CTD in proximity to the affected area)

 

2. Corrupted Mesh file(s). not limited to proximity, this will cause an Instant CTD when encountering a corrupted mesh, and Inspecting a weapon or armor or workshop item that has a corrupted mesh, such as vieiwing in the Pip Boy, Workbenches, and Workshop etc

 

i also believe their is potential that broken precombines can also cause CTDs. which would of course also be a proximity based crash, due to being location based.

 

 

however their are many possible causes for location Based Crashes, especially Sanctuary as it is a problematic location, just like Red Rocket and Abernathy farm. all 3 is what people call the triangle of death because their prone to issues.

 

1 thing that is clear, it is Extremely Likely that it will be a mod that causes these CTDs, and that could be due to Conflicts or the mods were Not Installed/Un-Installed Correctly

 

 

either of these could apply in your situation, so i am going to assume your mods are definitely not gone. their is potentially traces left behind.

 

 

the only time i have ever had sanctuary crash on me, was caused by a mod (dont know what mod it was though) and that was quite a long time ago, since using my new mod setup i have never had sanctuary crash on me, but ever since that ctd a long time ago, which was repeatable, i always save before entering sanctuary, in fact i always save before entering any interior cell or location, especially modded places.

[StormWolf01]

You've already got really good people working with ya on this, and they've covered the usual suspects.

I can however, contribute something that MIGHT at least, let you play, from the beginning. https://www.nexusmods.com/fallout4/mods/28562 Skip Prewar. Basically what it does, is after you do your CC, you talk to Codsworth, and that zooms you off into the Cryopod, and starts the scene with leaving the vault. However, it already equips you with your spouse's wedding ring, and renders their cryopod inanimate. Just a small thing really, but yeah...that's intentional, not a bug.

Like I said, that's not a fix to your problem, but maybe a bypass, so that you can at least still play on new characters.

Now, one thing that I WILL mention, is that I've found a bug with that mod. If you do player.unequipall from the console or a bat command, SOMETIMES, it won't let you talk to codsworth. IN which case, open your options list, and choose to load the initial save right after you finish your character, and try again.

 

I'm hoping that this will work in the meantime. Hopefully the problem is localized to PREwar sanctuary, and not POSTwar sanctuary. If it is in post war too, you'll probly crash as soon as you leave the vault.

 

Edit- I also just wanna add, I make dated backups of my game installation folder, after every 3 or 4 mods added. And sometimes add a text file of what mods I'd added since the last backup. As well as copies of my savegames every couple of days. It's a good habit to get into, when you mod games as heavily or as often as a lot of us do. :wink:

It makes reinstallation really easy. Overwrite EVERYTHING! :D

Edited November 4, 2019 by StormWolf01

[GrndZero]

I might have to give that mod a try the skip mod. I completely uninstall FO4, deleted the folder, updated video drivers as there was an update a couple days ago. I reinstalled the game and did nothing else, straight from the launcher and it is still crashing in the same spot. I am guessing I can delete all stuff in my "My Games" folder of FO4 and the game will just remake all of those files.

 

**Append

Completely redid the game with new .ini's

I initialized a new game with Mod Organizer again since I knew the mods were not what was causing my CTD. Started with Start Me Up and put my starting place as Ten Pines Bluff, I did notice one thing that I had noticed before. I knew right when I was going to crash, this time no where near Sanctuary, I heard a sound skipping noise and knew it was going to cause a lock. Turns out I might want to look into a sound driver possibly.

 

**Append II

Sure as s#*!, it was the sound drivers. I had updated something last week but it apparently was not affecting the game I had already going, off the top of my head, other than the video card drivers I do not remember what it would have been other than some MSI stuff possibly. Updated sound drivers and went back into the game and it plays just fine. Glad I paid attention to that slight sound glitch.

[GrndZero]

Yeah, scratch all that, still crashing. Now its just at different times. Its funny as I can tell when I am going to crash as I am getting a weird audio stutter.

[StormWolf01]

Ah dammit Grndzero, ya got my hopes up there! I thought you'd found it. I'm really sorry that now it's not fixed.

That's interesting tho. And it makes me wonder if the stutter is a symptom, not a cause. I wonder that, because when I was playing on the PS4, when the sound would start to glitch, you could tell that a memory error had just occured. Meaning, that the next time that you went to save a game, it would tell you that there wasn't enough memory for the savegame, regardless of how much HDD space you had left. And the game had just corrupted your current save.

On the Playstation, there was several causes of that, including, but not limited to, Creation Club content. (Let me PAY you to make my game crash, thank you Bethesda!)

Breaking precombines was also another source of it. Mods that will scrap anything and everything.

But I dunno if that's true on the PC or not. I've been avoiding that stuff because...previous experience. So I dunno or not.

 

If it is your sound drivers, a way to test it would be to try a playthrough with your sound card disabled. If it's the culprit, sound cards can be found for dirt cheap nowadays, assuming that you aren't on a laptop.

[G4M3W1NN3R]

Yeah, scratch all that, still crashing. Now its just at different times. Its funny as I can tell when I am going to crash as I am getting a weird audio stutter.

 

just it case it is audio based:

 

right click on the Speaker in your Taskbar - Click on Playback Devices - Click on Speakers, then Properties - click on Advanced Tab - Click on Default Format Drop Down Box, and change to *16 Bit 44100 (CD Quality)*

 

Un-Supported Audio Format Quality can Cause Games to Crash if the Format is Different to the 16 Bit 44100 (CD Quality)

 

it is Very Likely that the cause for the CTD is Audio Based

 

which can either be Caused by:

 

Un-Supported Audio Format (doing the above will fix that)

 

Soudcard Issues (sound card might have dust which can cause problems, can also be incorrectly seated, connectors might have become loose etc etc)

 

Sound Card Drivers - (Open Control Panel - Device Manager - Sound - See if their is any Exclamation Marks *!* next to Sound)

 

 

Visual Stutter = Memory Based Issue (Vram or System Ram, and Can also be HDD)

 

Audio Stutter = Audio Based Issue, which is very likely something to do with the Sound Card, Audio Playback, or Drivers

[GrndZero]

My speaker were set to Studio Quality so I lowered them down and thought it going to start working but alas, crashed yet again. I think I might just have to saw screw it for the time being, play some Outerworlds or something. A shame as I really like modding.

[xlghostlx]

Did u removed weapon debris? that make the games crash on the new RTX