Jump to content

Photo

Fallout 4 crash to desktop in specific area


  • Please log in to reply
8 replies to this topic

#1
TOExHEAD

TOExHEAD

    Newbie

  • Members
  • Pip
  • 11 posts

I am getting CTD's if I fast travel or walk near a specific area on the map. I got it a few days ago once and decided to fix it later, assuming it was a bug with a weapon mod I had recently installed. Today I got many more CTD's when trying to complete a quest in relatively the same area. I did what I thought would help me discover what the issue was, so IO started disabling many esp files with nexus mod manager and eventually all of them to find that I was still getting the CTD's. I am not sure but if I disable all my esp's I believe all I am left with are textures, meshes, sounds etc and I don't see how any of those would cause these CTD's. I will try removing some of those I have newly installed in the recent couple weeks but will be difficult because nexus mod manager does not add most files like textures, meshes, sounds, etc, and I have to add them manually. And because it does not add them when installing mods, it does not remove them.

     I am just wondering if there are any steps I could take to discover what the issues is, like a way to generate crashlogs, methods of further troubleshooting, and eliminating things that are not the issue so I don't waste my time investigating them.

Attached File  Fallout 4 CTD map small.jpg   199.8KB   26 downloads



#2
Royhr

Royhr

    Old hand

  • Premium Member
  • 631 posts

Well your game saves may be corrupted somehow. CTDs are a pain is the ass. I've encountered this sort of thing myself and have pulled my hair out trying to figure it out. But then after I started a new game for whatever other reasons, mainly just to start a different playthru, whenever I returned to the areas I was encountering CTDs I didn't have the issues any longer even though I was running basically the same mod set.  As I said CTDs can be a pain to figure out.



#3
speedynl

speedynl

    Faithful poster

  • Supporter
  • PipPipPipPip
  • 1,515 posts

for a quick test to see if its your saves, back up your saves, start a complete new game, open console type tmm 1, fast travel to the location that cause ctd, no ctd means your save is corrupt



#4
TOExHEAD

TOExHEAD

    Newbie

  • Members
  • Pip
  • 11 posts

for a quick test to see if its your saves, back up your saves, start a complete new game, open console type tmm 1, fast travel to the location that cause ctd, no ctd means your save is corrupt

It seems starting a new save no longer creates the crash. i was hoping it was one of my mods causing it and not  a corrupt save. I had CTD's in the past after installing a weapon mod or something, and said weapon being spawned in the world like on an NPC or something caused my game to crash because I had forgotten to install the textures and meshes or something. I am later going to try a clean install and see if the same save gets a CTD, but that won't be soon because my internet is very slow and it would take allot of time.



#5
dandiersphinx

dandiersphinx

    Regular

  • Supporter
  • PipPip
  • 87 posts

Are you using any interface mods?
 
Because I had crashes in the same area and it was because of my Interface mod that was incompatible with the Mechanist Lair map marker.
That map marker only starts crashes after I was done with Automatron quest and got the Mechanist Lair unlocked.

 
If it's the same for You then You might want to try 
 
County Crossing Crash Fix


Edited by dandiersphinx, 05 April 2016 - 09:22 PM.


#6
TOExHEAD

TOExHEAD

    Newbie

  • Members
  • Pip
  • 11 posts

Are you using any interface mods?
 
Because I had crashes in the same area and it was because of my Interface mod that was incompatible with the Mechanist Lair map marker.
That map marker only starts crashes after I was done with Automatron quest and got the Mechanist Lair unlocked.

 
If it's the same for You then You might want to try 
 
County Crossing Crash Fix

Thanks a lot for the suggestion, I will try it right away.



#7
TOExHEAD

TOExHEAD

    Newbie

  • Members
  • Pip
  • 11 posts

 

Are you using any interface mods?
 
Because I had crashes in the same area and it was because of my Interface mod that was incompatible with the Mechanist Lair map marker.
That map marker only starts crashes after I was done with Automatron quest and got the Mechanist Lair unlocked.

 
If it's the same for You then You might want to try 
 
County Crossing Crash Fix

Thanks a lot for the suggestion, I will try it right away.

 

Yes this mod fixed the issue 100%. It did break a map replacer mod I had installed but that is a way better option than having a portion of the map crash my game. Thank you so much!



#8
TOExHEAD

TOExHEAD

    Newbie

  • Members
  • Pip
  • 11 posts

For some reason now though, even though I uninstalled my pipboy map mod, the map markers are completely misaligned with the map, which appears to be smaller then them.

 

Nvm, resolved


Edited by TOExHEAD, 06 April 2016 - 04:33 AM.


#9
EnigManic

EnigManic

    Old hand

  • Supporter
  • PipPipPip
  • 846 posts

Do you use mods? Your save file may not be corrupt.

 

Turn off Steam cloud sync and then make a new character. Bare with me a minute.. Once you leave Vault 101, use console commands (COC) to jump to one of the locations where the game crashed to desktop. Does the game still crash? If not, the other save file is indeed corrupt.

 

If you still get a CTD at certain locations even when using a different character then mods are the problem. Here are the steps to fix it:

 

1 - Disable and uninstall all mods.

 

2 - Uninstall Fallout 4.

 

3 - Check the Fallout 4 folder (Steam/SteamApps/common/Fallout 4) and make sure it's empty. The problem was that you had orphaned files in the Data folder from previously uninstalled mods.

 

4 - After ensuring the Fallout 4 folder is empty, reinstall the game.

5 - Install ONLY the mods you were using when you got the CTD. Optionally, you can try skipping mods for now.

 

6 - Load your save. You may get a warning message about missing mods. Use console commands (COC) to jump to one of the locations where the game crashed to desktop. Problem solved!






Page loaded in: 0.698 seconds