Anytime I play the game, it runs anywhere from a few seconds to ~15 minutes before my computer will just randomly restart itself. I have tried a multitude of things, turning the graphics all the way to low(even though it auto detects to be set to high), I ran it in beta mode(when that was a thing), I've re-installed the game twice now, both to my SSD and my Hard Drive. I don't suffer any kind of lag in game, or any performance issues while I'm playing, it is just it make my computer restart.

My initial thought was that it was my PSU becoming over heated and my computer shutting down due to safety measures, but yesterday I was playing for 4 hours straight with no problems at all, granted I was on edge the whole time because I was expecting it to shut down at any moment(so I truly didn't get to enjoy the game). It did end up shutting down after ~4 and 1/2 hours. After actually being able to play it for a decent amount of time without it shutting down my computer has begun to make me doubt it is a PSU issue.

I'm at a complete loss about what to do or even what to guess the issue could be. I sent in a ticket to Bethesda Support the night I started to encounter the issue. I've yet to receive any word back from a support tech. So I figured I should post here to see if anyone has come across the same issue with this game, or with another and has any idea on how to help my situation.

Forgot to post my dxidiag

Check your Event Viewer for further information regarding the crash.

The only thing that I am picking up from the event viewer is it saying my computer shut down randomly. I can't derive any information from it, as to the cause of it.

Be default, Windows is set up to reboot your machine on a driver issue, which of course wipes the event viewer for the problem that caused the machine to reboot in the first place.

So, you may have to update your drivers, and if you have an Nvidia, you do have to update the drivers.

As for stopping your machine from rebooting, and hence being able to troubleshoot the issue, go into Advanced System Properties and uncheck the box that forces the PC to reboot on driver issues. It's under Troubleshooting IIRC

Also, if you have Asus GamerOSD running, disable that. In fact, remove it from your system. It causes problems with all kinds of games and the ability to change game resolution on the fly is not all that needed a feature.

My Nvidia driver is up to date (currently on 358.91). I don not have Asus GamerOSD running, or installed. And as for the auto reboot, the settings have already been set to not allow auto reboot and to create an event log. It appears as though one is not showing, for whatever reason that could be.

Another thing that I forgot to mention, was that it seems that the crashes mainly happen when I am inside of a "Sub-World" (i.e., a building, cave, or "instance") A weird thing to note about this is the fact that this does not always happen. I have cleared and gone through multiple "instances/sub-worlds" without having any problems. When I was playing for ~4 hours straight, I was mostly in the outside world(Commonwealth), the crash did end up happening while I was in the Commonwealth. But as I said before, I've noticed that it mostly happens when I am instanced.

I'm having this same issue and I've pretty much drawn the same conclusions; it appears to not be temperatures because for one, I've monitored them fairly closely even before this issue and they're always well within normal ranges. Immediately after the reboots, I checked as well, still looked fine. Two, I played for about 4.5 hours straight without a problem.

My PSU is under a year old and is a Corsair HX750. More than enough power for my single 970 setup. And overall, my system has been otherwise stable. As well, just like you said, I can't get any decent information from Event Viewer and so on either.

Finally, I've pinpointed my crash to one exact interior and can reproduce it 100% reliably. The Concord Speakeasy. If I stay there for more than... About 45-60 seconds, it will reboot. I've not explored much, because of this issue, but I don't seem to have this occur in the Sanctuary Hills/Concord world region or any interiors located there except the Speakeasy, even when staying in other places for much more extended periods of time. This also occurred both before and after the latest patch.

My specs (on mobile so I can't get a dxdiag right now):
OS: Win 8.1
CPU: i7 2600k @ stock 3.4 GHz
GPU: EVGA GTX 970 (358.91 Drivers)
RAM: 12GB 1333MHz
PSU: Corsair HX750
Mobo: Asus P8P67 Pro
Storage: 2x 7200RPM HDDs

Playing this on mixed medium/high settings mostly, couple ultras, but well below the full Ultra settings the game suggested. Also another strike against overheating. I have no other bugs, CTDs, lag, stutter, graphical errors or really anything. Solid 60fps. Game runs so well for me aside from this.

Another update. I'm 90% sure that it has something to do with going into an "instanced" area. Right after I posted my last message, I decided to hop on and play. I said "what the hell, might as well try it" I was playing for about an hour and a half on HIGH settings, with no problems whatsoever. However this time was spent entirely in the CommonWealth(open world) and not going inside any building(sub-world). I figured I would test it for science, and as soon as I entered a building, I got about 30 seconds into it before my computer shut down and restarted.

Again, I pulled up the event log, and there is no information about what is causing the shut down. Even with making sure to have my settings set to not allow for an auto reboot, my system still appears to allow that to happen.

Does yours appear to only be when you are inside the Concord Speakeasy "instance" or is it when you enter any kind of "instance"?

Mine only seems to occur inside the Speakeasy. I cleared out the Mole Rat Den, another building in Concord, and the Museum of Freedom entirely without problems. (And of course the vault at the start) I probably spent 25 minutes in the Museum for example. But I haven't explored further than Concord due to this issue, so other interiors/instances may cause it too.

Edit: I also cleared out the Civic Access tunnels.

Funny, just as I had reloaded the game due to the previous crash before my last post. I was walking around in the CommonWealth, and my system rebooted. So now I'm not sure what to think.

Turn off automatic restart under the Settings button of the Startup and Recovery section of the Advanced tab of System Properties. You should get a blue screen rather than automatically restarting at that point which may give a clue regarding the crash.

Automatic restart has been turned off. My system will still automatically restart though.

So you're not getting a blue screen that you manually have to restart your system from? That's the strangest thing I've ever heard.

Just as an aside, why in the world is there a MentalHealth.gov link at the bottom of the page?

No, my system will just shut off and then restart. No warning signs, no preemptive measures that I seem to be able to take before it reboots.

And the link is most likely because Bethesda knows what they do to their consumers. (^:

HA! well, the only thing I can think of to narrow this down is to first try to eliminate a possible software conflict. Turn off as many startup programs as you can, turn off and restart your computer, only start Steam and run FO4. See how that goes.

Sorry do budge in like this,
Honestly this is the most ridiculous thing i have ever read.

In my 26 years of experience in computers knowing software as well as hardware... faulted drivers would never reboot your system.
it would crash the software and restart the software, if it can't run properly it would just neglect it and error it to the user.
as example; when your Graphic's driver would crash your screen would go black and then back to normal windows will show a message that the driver crashed. This in fact is result of faulty drivers.

As for computer restarting, it can be a handful of things.
One of the well known issues is temperatures so keep an eye on this. stay away from 85 degree's. anything over that has potential to restart.

But yet one of the most common and yet not well known issues is the CL-CC-Tram-TL latency timings on your Ram, if your Ram has the wrong clock speeds that your computer can't keep up with during heavy load such as running Fallout 4, it would Reboot your system without warning.
This has to do with safety features on your motherboard and the brand doesn't even matter its pretty much mobo's & ram.
The solution to this would be running memtest86 for about 20 hours straight and it will tell you exactly what is wrong.
for temps i'd recommend doing a 8 hour prime95 run to see how "hot" the whole system gets.

And to be fair if you have no or little knowledge to this i'd highly recommend bring it to an expert,
other solutions is to do Bios update for your motherboard.

If your computer restarts without warning its 99% sure hardware related the 1% is otherwise a virus which would forcefully reboot the system but then you would always see it shut down.

This is pretty much all the information i can suggest.

TL;DR

• Run prime95 to check temps (i might be old on this but 85 degrees absolute max on CPU anything above will damage it.)
• Do a full Memtest86 to see if your ram is 100%
• Update motherboard bios.

Most importantly make sure there is no DUST in your computer, Dust holds heat and blocks airflow this is your Pc's worst enemy.
even when you think your water cooling has no dust make sure there is no dust in the radiator.

?most of these things speak for themselves anyways.

Tollvik,

Quickly looking over your Dxdiag,

Your system runs at stock, i presume you haven't changed anything.
Nothing seems overclocked and nothing seems to be out of the ordinary.

i don't know what type of cooling you have if its stock cooler that comes with cpu and if its full of dust or not.
Neither do i know if your Motherboard is in "Turbo" mode which is default on some motherboards for AMD.
which causes exactly these types of problems as you are describing; Because it tries to overclock your system when it feels it needs to but then crashes itself and reboots without warning.

If you want my help i'm going to need a bunch more information.
such as,

1. Motherboard + version(if its a revision or not) & what version of the bios its loading under.
2. what type of cooling do you use?
3. when is the time of purchase of your system and when is the last time you cleaned it?
4. what profile does the Ram show under in the bios does it show 1333mhz? or is it adjusted?
5. How old is your SSD? and how many times did you remove big files? what brand is it and have you ever had other troubles with your SSD?
   have you ever did a health check on it?

and if you would like we might continue this through a more direct chat.
in my personal experience this isn't a game issue it sounds like hardware issue, either heat related, Ram or motherboard forcing OC mode.
either way its fixable, if you are willing to take the effort for it.

This has been an ongoing issue with Bethesda games since at least Morrowind. It's typically a software conflict.

This sounds like PSU, but in case if the game was fine... Try to terminate all useless processes, there are lot of software(crapware) which have negative impact on to games because hooks in to graphics, this is very popular annoying problem. Older drivers may help, same as new, this, khm, depends. And just want to mention one thing - game render have bug which normally crash old drivers, may be it still affect something internally and you have what you have. From other side, Win7 just restore driver instead of restart PC or anything else hardcoe. Grab OCCT stress test and run it for CPU and GPU both about an hour to find out if it's hardware.

PS: once i've seen similar behavior because of errors on hdd. it's exoctic case, but check it's surface entirely and fix bad sectors if found.

For starters just try to have a look inside and make sure there a airflow through the cpu cooler, if it looks clean enough then let that be for now.

i don't know the amount of airflow through your system and and i don't know how fast the dust builds up so this is why i would ask you to just at least check if there is a layer of dust grab a tooth pick and try to take it out to see the thickness of it.
if this is not the case there little to no dust then i'm convinced we can neglect heat issues, and at the same time Ram issues since everything is pretty much stock it should have no problems.

as for the motherboard it seems to be fine, i would recommend updating the bios at least once to a newer version it can increase performance.

i'm afraid this might be an actual case of faulty Power Supply Unit, and the reason why is because...

Everything in your system checks out so far,

i doubt you have heat issues since your Cpu cooler is overkill But... then again if you have like 12 to 20 fans in your case and you have too much airflow in your system it svcks dust by the second and it all sums it up right at your Cpu.

Since most of the settings are stock, and i know the Asus Crosshair series everything should be perfectly in order regardless of Ram.

Samsung is very good in making SSD's so i doubt that be the issue. none the less its possible to do a simple health check to be 100% sure.
the older mechanical drives they don't encounter the issues i had in mind so it should be all in working order.
as ENBseries mentions these cases are extremely rare.

Now you did mention... that you moved back home, this might be a long shot but can you please check every single cable from PSU to Motherboard and just press them a bit tighter.
its possible during the move that one of the cables might have gotten a bit looser but the chances are minuscule.

you could indeed stress your system for couple of hours and see if it has the same behavior as in game.
So again i think ENBseries is correct.
OCCT is a fine tool to stress full system; if it has the same behavior as in-game then it has a big chance its psu.

So my advice,

• a quick look over your system to check if there isn't a layer of dust blocking airflow.
• a quick check to see if all cables are 100% correctly plugged in an not a tiny bit loose.
• possible health check on hard drives.
• Update bios, 2201 latest or higher, this would improve system stability chances are small but still possible...
  there have been since 1302, at least 7 different bios updates surrounding "system stability" and such.
  Most of these things are just to be safe, the chances are extremely small that these could be the potential problem, however there is still a possibility...
  
• Stress the system to create the same scenario to see if it restarts without warning.
  

Good luck!

The question that I keep getting stuck on, is how can this be a hardware issue when I'm still able to play the game for extended periods of time? That's what just doesn't make sense to me. If I was not able to play at all I could understand, or if I was only every able to get to a certain end point. But the inconsistency with which I'm crashing is just mind boggling.

The thing is, how are this many people having this same issue at the same time?

What is the game doing that is conflicting so badly with either Windows, the PSU, or the RAM?

The game ran fine before the patch/windows update.

After...same issue. Random complete re-boots. This is WITH the re-boot on error unchecked...its over-riding the Windows setting.

Also, I did stress the heck out of my system yesterday, let it run at 100% CPU, RAM load, and 4500fps for about 2 hours. Temps barely went above 40c with water-cooling, and no crashes.

Does yours tend to do the reboots more often when you are "instanced" I've had it reboot a couple times today while I was in the Open World. But every time I go inside a building I get a crash.

And same with the temps, I've been monitoring them right before crashes and there isn't anything out of the ordinary.

My reboots happen completely randomly, but I can kind of force it by quick-saving 3-4 times in a 5 minute period. On about the 4th quicksave, just hitting it will reboot the computer. I've been out in the open (exploring towns and getting junk for my settlements), but it doesn't seem to matter at all.

I rolled back Windows to 2 weeks ago, but that didn't fix the issue. Currently I'm "acquiring" an un-patched version of the game to check if it really was the patch that did it.

Windows and the game both patched at the same time Tuesday evening when I foolishly decided to take a break from playing, so no telling which did it for sure. I had played about 20+ hours without a glitch before that.

I have literally tried everything else. Completely reinstalled my system, absolutely latest bios and drivers, rolled back drivers all the way to June (audio and video), set my system to baseline and then underclocked, tried every tweak and gimmick and random voodoo every forum knucklehead has come up with. Nothing is working here, it overrides Windows settings and forces a reboot. I'm running a brand new, top of the line system...from what I've seen, everyone with this problem has the most diverse hardware specs imaginable, so there's no way to pin it on any particular chipset or hardware config.

If they'd just let us roll back that last patch I could test it without resorting to nuclear options...somehow it never occurred to them they might break something.