Midgame CTD after ~10minutes in.

[dontplay21]

So recently I reinstalled Fallout 4 and now I am getting CTDs randomly(sometimes when entering interior cell). Sometimes after 1 minute in, other times more, but always in the first 10 minutes or so.No mods installed.

My rig:

AMD FX-6100 Six-Core Processor

Nvidia GeForse GTX 1050ti

8gb Ram

Game installed on SSD.

 

I have played without problems on this computer before for long periods of time few months ago and last year. I have already tried to switch between Fullscreen and Windowed mode, blocking Fallout 4 connection trough firewall, updating drivers, visualc++,net framework, directx. Nothing helps. I reinstalled it several times. Used F4SE too with no succes. Deleted all the Creation Club mods too, no help.

 

Asking for you help.

Edited November 17, 2018 by dontplay21

[lavarob]

Overclocked graphics card to unstable levels? Overclocked cpu to unstable levels? Is there a lot of stuff running in the background when you play or is your SSD full? - your setup isn't the most "high tech" so things like that could be taken to account. Some of those might not matter but those are things I try to avoid to minimize any stupid bs happening in the hardware level.

 

When you uninstalled FO4 did you delete the file folder? The steam uninstaller only removes the recognized game files and If you didn't, the mod files in my own experience should still be there.

Edited November 17, 2018 by lavarob

[dontplay21]

Overclocked graphics card to unstable levels? Overclocked cpu to unstable levels? Is there a lot of stuff running in the background when you play or is your SSD full? - your setup isn't the most "high tech" so things like that could be taken to account. Some of those might not matter but those are things I try to avoid to minimize any stupid bs happening in the hardware level.

 

When you uninstalled FO4 did you delete the file folder? The steam uninstaller only removes the recognized game files and If you didn't, the mod files in my own experience should still be there.

No, I did not overclock anything. Nothing running in backround, outside of Msi Afterburner and Steam. And I checked for old mod files, so it was a clean installation. SSD had free 100gb space after install. It might be a hardware problem, but I have played Fallout 4 on even weaker rig(4gb ram, 1gb Vram), not going over 35fps, but it was stable, so I think my current rig should be fine, considering it worked perfectly before.

Edited November 17, 2018 by dontplay21

[dontplay21]

Found a reason for CTD's myself. Not enough RAM, so I enabled swap file to fix the issue.

[JimmyRJump]

Found a reason for CTD's myself. Not enough RAM, so I enabled swap file to fix the issue.

Swap File will only slow down the game as it uses a portion of whatever SSD/Hard Drive you have on your rig. Both are much slower than RAM. Have a look at ENBoost to try and use some system RAM as Video RAM. Not much to play with here, but it's worth a shot.

 

A 1050ti has 4GB of V-RAM, plus 8GB of system RAM is 12GB in total. You can set the enblocal.ini to 8GB under [MEMORY]. Also set the ForceVideoMemorySize= to true.

[dontplay21]

 

Found a reason for CTD's myself. Not enough RAM, so I enabled swap file to fix the issue.

Swap File will only slow down the game as it uses a portion of whatever SSD/Hard Drive you have on your rig. Both are much slower than RAM. Have a look at ENBoost to try and use some system RAM as Video RAM. Not much to play with here, but it's worth a shot.

 

A 1050ti has 4GB of V-RAM, plus 8GB of system RAM is 12GB in total. You can set the enblocal.ini to 8GB under [MEMORY]. Also set the ForceVideoMemorySize= to true.

 

So I turned off swap file and enabled ForceVideoMemorySize, but thats was not enough. I can load into interior cell, but get CTD when trying to load into exterior. First I thought that 8gb might be too much, so I lowered to 4gb, but still nothing changed, so I turned swap file back on.

[JimmyRJump]

 

 

Found a reason for CTD's myself. Not enough RAM, so I enabled swap file to fix the issue.

Swap File will only slow down the game as it uses a portion of whatever SSD/Hard Drive you have on your rig. Both are much slower than RAM. Have a look at ENBoost to try and use some system RAM as Video RAM. Not much to play with here, but it's worth a shot.

 

A 1050ti has 4GB of V-RAM, plus 8GB of system RAM is 12GB in total. You can set the enblocal.ini to 8GB under [MEMORY]. Also set the ForceVideoMemorySize= to true.

 

So I turned off swap file and enabled ForceVideoMemorySize, but thats was not enough. I can load into interior cell, but get CTD when trying to load into exterior. First I thought that 8gb might be too much, so I lowered to 4gb, but still nothing changed, so I turned swap file back on.

 

The 8GB setting is to make the gamle use 8GB overall of the available RAM, both GPU and system. The max you could go is 9GB because you need 3GB for the operating system. If the game crashes with the enblocal.ini set to 8GB then there's more going on than insufficient RAM.

[MarkusTay]

Could be a bad sector on the RAM itself... that happened to me once. It won't show up all the time - only in memory-intensive apps that get to that bad sector eventually. There should be some memory-testing freeware on the Net somewhere (its a longshot, but like I said, it happened to me).

[JimmyRJump]

Could be a bad sector on the RAM itself... that happened to me once. It won't show up all the time - only in memory-intensive apps that get to that bad sector eventually. There should be some memory-testing freeware on the Net somewhere (its a longshot, but like I said, it happened to me).

Only mechanical hard drives are devided into sectors. RAM is devided into three areas; the rack, the stack and the address but the separate chips are seen as a whole and data gets constantly moved. That's why RAM or nand flash/solid state drives don't need defragmenting. When one of the chips on a DIMM is faulty then the whole DIMM is faulty and most of the time your system reboots or slows down severely within hours to minutes. When a RAM error causes a game to crash, you'd most probably get a BSOD too... Easiest way to test without involving any software is boot the system with one DIMM at time and see how the computer runs.

 

First thing to do is simply reseat the RAM modules. It could be that a DIMM isn't properly clicked into its slot or dust has gotten in the way and there's bad contact. For more extensive testing, use MemTest86.