Fallout 4

Fallout 4

View Stats:
Mattno Apr 20, 2017 @ 7:07pm
Random Crashes
I have been playing Fallout 4 for a while and had no problems. Recently I have random crashes to my desktop without any errors messages. I have viewed other fourms on this but didnt fully understand them. I would like to know how to fix this problem to fully enjoy the Fallout experience.

My specs are
GeForce GTX 1060 3GB
Intel Core I5-4430
16 GB Ram
Fully updated Nvidia drivers
< >
Showing 1-14 of 14 comments
HEXEN Apr 20, 2017 @ 8:09pm 
No mod-list = no service.
ronr42 Apr 21, 2017 @ 6:41am 
First, the game for many players does randomly CTD. There will usually not be any crash report.

Crashing when fast traveling, going through load doors or when exiting your Pip-Boy, try unchecking all the autosave functions.

Verify the integrity of the game files.

Lower Shadow Distance to medium and Godrays off. The shadows in this game run off your CPU not your GPU.

Because of all the achievements you have with only 96 hours in the game, I assume you have NO mods installed. If you have mods and the Achievement mod, please list all your mods in the correct NMM plugin load order.
sdack Apr 21, 2017 @ 7:24am 
Originally posted by ronr42:
First, the game for many players does randomly CTD. There will usually not be any crash report.
One can get the occasional crash, but it requires playing for very long hours and it won't happen more than once every 100h of game time. That's my experience.

The only reliable way for me to crash the vanilla game is to use the workbench with the "X+" mods that drop from some of the Mechanist robots. There seems to be a reproducible bug in there, that can crash the game. But it takes a lot of weapons and modding before it gets trigger. Once it does can one crash it repeatedly, but one can also avoid it by modding a different mod into the slot first and then going for the X+ mod. I believe this has got something to do with some early weapons having buggy mods, which then clash with the mods by the Mechanist DLC.

The amount of crash reports here on the forum are also fairly low considering that 20k players are playing the game each day. Some reports are to be expected due to buggy drivers, unstable hardware and of course mods. Even then I'd say the number of crash reports here are still fairly low. As it's getting warmer on the Northern hemisphere will we see more heat-related issues on this forum...

What it means is that I would first check that you're not using any mods. Then check that the crash isn't reproducible, meaning, remember the exact steps it took you to cause the crash and repeat them 3-4 times. If you get it to crash reproducibly, well, you've found a bug (not necessarily in the game though, but can be driver-related as well).

Then verify your game files:
https://support.steampowered.com/kb_article.php?ref=2037-QEUH-3335

If you think verification itself is faulty then delete the appcache/ folder in the Steam directory and try again.

If you think it could be a hardware issue then use AMD OverDrive's stability testing or Prime95 together with FurMark and stress test your hardware for a couple of hours. Also watch the temperatures on CPU and GPU as well as the fan speeds.
Last edited by sdack; Apr 21, 2017 @ 7:27am
Mattno Apr 21, 2017 @ 8:30am 
Thanks guys, I have no mods installed and have verified my files without any missing ones. I also have no DLC yet
ronr42 Apr 21, 2017 @ 1:40pm 
Originally posted by Mattno:
Thanks guys, I have no mods installed and have verified my files without any missing ones. I also have no DLC yet

Have you tried just unchecking the autosave functions yet?
ronr42 Apr 21, 2017 @ 1:50pm 
Originally posted by sdack:
Originally posted by ronr42:
First, the game for many players does randomly CTD. There will usually not be any crash report.
One can get the occasional crash, but it requires playing for very long hours and it won't happen more than once every 100h of game time. That's my experience.

The only reliable way for me to crash the vanilla game is to use the workbench with the "X+" mods that drop from some of the Mechanist robots. There seems to be a reproducible bug in there, that can crash the game. But it takes a lot of weapons and modding before it gets trigger. Once it does can one crash it repeatedly, but one can also avoid it by modding a different mod into the slot first and then going for the X+ mod. I believe this has got something to do with some early weapons having buggy mods, which then clash with the mods by the Mechanist DLC.

The amount of crash reports here on the forum are also fairly low considering that 20k players are playing the game each day. Some reports are to be expected due to buggy drivers, unstable hardware and of course mods. Even then I'd say the number of crash reports here are still fairly low. As it's getting warmer on the Northern hemisphere will we see more heat-related issues on this forum...

What it means is that I would first check that you're not using any mods. Then check that the crash isn't reproducible, meaning, remember the exact steps it took you to cause the crash and repeat them 3-4 times. If you get it to crash reproducibly, well, you've found a bug (not necessarily in the game though, but can be driver-related as well).

Then verify your game files:
https://support.steampowered.com/kb_article.php?ref=2037-QEUH-3335

If you think verification itself is faulty then delete the appcache/ folder in the Steam directory and try again.

If you think it could be a hardware issue then use AMD OverDrive's stability testing or Prime95 together with FurMark and stress test your hardware for a couple of hours. Also watch the temperatures on CPU and GPU as well as the fan speeds.


Never have done large amounts of weapons modding at one time. First time I've heard of that type of crash.Thanks.

The random crashing sticks in my mind more because I used to get it before I had any mods. First 350 hours after the game released was vanilla. Albeit most of that time was before the game got patched much. Played vanilla through the 1.4 patch and started modding just before 1.5.


When I get the random crashes now, they are actually far and few between. I get more of the endless load screen when fast traveling from a few particular locations back to a settlement. Figure that is probably caused from a combination of a ton of saves, uGrids at 11 and maybe a mod I have. Only have 53 active mods and 90% are build menu mods. No mods that change anything outside of a settlement.

Edit; I get the occasional endless load screen even when FT to a settlement I don't have anything built on. Not just Spectacle Island and Somerville where I have a S Storm of things built and decorating done.
Last edited by ronr42; Apr 21, 2017 @ 2:07pm
sdack Apr 21, 2017 @ 2:11pm 
Originally posted by ronr42:
Never have done large amounts of weapons modding at one time. First time I've heard of that type of crash.Thanks.
I am guessing it has to do with some of my loot going back to before 1.7 was released. It might not be visible with a new play-through after 1.9. I've read that some of the weapon mods had typos in their internal naming, which is why I can see identical mods not actually stacking. Hence, replacing a mod on an early weapon with a different mod first before using the X+ mod seems to be a reliable work-around. I've also only mention this here, because it is really the only bug I know and it's not even an issue.

It's cool that you can use plenty of mods with uGrids 11 and still only get the occasional long load times.
Last edited by sdack; Apr 21, 2017 @ 2:40pm
ronr42 Apr 21, 2017 @ 2:23pm 
Thanks for the additional info on the modded weapon CTD.

Yeah, with uGrids at 11 and over 1k hours in on my first playthrough, I'm Real careful about what mods I download and what changes they make to the Commonwealth. When someday I start a second playthrough, I may gamble a little more with mods that make more game changes/Commonwealth changes. For now, Im a Happy Camper. :)
Mattno Apr 21, 2017 @ 2:59pm 
ronr42 I did the graphics setting changes and I haven't gotten an CTD so far
Mattno Apr 21, 2017 @ 3:00pm 
Btw thanks guys for the help
ronr42 Apr 21, 2017 @ 3:02pm 
You're welcome, glad you figured it out.
Ordeiberon Jun 28, 2018 @ 5:03am 
Not sure if that was the complete fix, but I turned shadows down to medium and disabled godrays and lens flare (it bugged me) and played for several hours without crash. This was after crashing every 5 minutes yesterday. Thanks.
Madnbad Jul 8, 2018 @ 6:17pm 
Originally posted by sdack:
Originally posted by ronr42:
First, the game for many players does randomly CTD. There will usually not be any crash report.
One can get the occasional crash, but it requires playing for very long hours and it won't happen more than once every 100h of game time. That's my experience.

The only reliable way for me to crash the vanilla game is to use the workbench with the "X+" mods that drop from some of the Mechanist robots. There seems to be a reproducible bug in there, that can crash the game. But it takes a lot of weapons and modding before it gets trigger. Once it does can one crash it repeatedly, but one can also avoid it by modding a different mod into the slot first and then going for the X+ mod. I believe this has got something to do with some early weapons having buggy mods, which then clash with the mods by the Mechanist DLC.

The amount of crash reports here on the forum are also fairly low considering that 20k players are playing the game each day. Some reports are to be expected due to buggy drivers, unstable hardware and of course mods. Even then I'd say the number of crash reports here are still fairly low. As it's getting warmer on the Northern hemisphere will we see more heat-related issues on this forum...

What it means is that I would first check that you're not using any mods. Then check that the crash isn't reproducible, meaning, remember the exact steps it took you to cause the crash and repeat them 3-4 times. If you get it to crash reproducibly, well, you've found a bug (not necessarily in the game though, but can be driver-related as well).

Then verify your game files:
https://support.steampowered.com/kb_article.php?ref=2037-QEUH-3335

If you think verification itself is faulty then delete the appcache/ folder in the Steam directory and try again.

If you think it could be a hardware issue then use AMD OverDrive's stability testing or Prime95 together with FurMark and stress test your hardware for a couple of hours. Also watch the temperatures on CPU and GPU as well as the fan speeds.

lol bethesda brigade coming in strong. every time i search about crashes/make a report people like come in and mention how the issue doesnt happen to them/"its not at all common!" maybe give the OP help first then shill later, we dont need your anecdotes
Nite69 Jul 8, 2018 @ 6:37pm 
its a bethesda game, so expect CTD's on and off, thats why I quicksave often
< >
Showing 1-14 of 14 comments
Per page: 1530 50

Date Posted: Apr 20, 2017 @ 7:07pm
Posts: 14