PC Specs:

- Windows 10 Pro 64-bit *Build 10586* (Fully updated)

- i7-2600 @ 3.40GHz (8 CPUs)

- 12g RAM

- Mobo: MSI h61m-p31/w8 (Bios V3.6 *latest*)

- DirectX Ver. 12

- XFX AMD R9 280x BDBT

o Bios - 015.044.000.010 (Latest, just confirmed w/ manufacturer)

o AMD Latest Suite – Cnext (Latest)

o Driver – 15.30.1025.1001 (Latest) *Beta*

o Default Settings (optimal)

- Game – Fallout 4 V. 1.2.37.0

o V. Settings

§ AntiA – TAA

§ Anisotropic Filtering – 16 samples

§ Detail – “Ultra”

Issue: After initiating the game either from launch menu or directly through .exe, the game will load without issue. Game will play without ANY issue at all, for roughly 2-3 mins and then will switch to a black screen, at which will lose video signal to monitor. HARD REBOOT REQUIRED, in order to operate PC again. This occurs from loading a saved game. However, if I start up a new game, I’m able to play for 1-2 hours and then the issue will present itself again, as described. It’s more than frustrating, and I’ve seen that many others that can relate. The issue seems to be prevalent across the board, with respects to GPU’s.

Attempted solutions (failed):

- Complete clean install Windows 10 OS

- Reset PC/GPU Bios

- Rollback prior drivers

- Complete reinstall of game

- Launch game directly from .exe

- Various .ini tweaks preferences

- Troubleshoot usb devices, only using xbox one controller (wired), using xbox one (wireless) w/ new adapter, using only keyboard/mouse

- DLL fixer

- I’ve even tried reinstalling windows 8.1, no luck

- And more, I just can’t remember the rest.

Comments: This is the only game that does this to my PC. There’s absolutely no reason why this is causing complete video signal loss. All other games work without any issue (on max settings: BF4, Star wars, GTA5, etc). I’ve reached out to Microsoft, MSI, & AMD…all of which unofficially concurred that the error is related to F4.

What else am I missing here?

Note – Fortunately, I have a punching bag to wear out…

Tried running Fallout4.exe as Windows 7 compatibility?

You're making new manual saves correct? Dont rely on quicksave alone.

When did a clean reinstall of windows did you try fo4 immediately (after essential drivers)?

What does your event viewer say? http://windows.microsoft.com/en-us/windows/open-event-viewer#1TC=windows-7

Look under WIndoes logs folder and check both sys and app logs.

Any overclocking? CPU/GPU??

Yes, I have tried both windows 8 & windows 7 compatibility w/ administrator privileges. No success.

I have not been making manual saves. I've only used quicksave. To be honest, I can't see this being the issue but its worth troubleshooting. I'll give it a try tonight.

Yes, I was able to conduct a shell test with no success. In this case (which consumed my saturday afternoon), I reinstalled windows, and downloaded essential drivers. I then used the original driver, and progressed through 9-10 other versions, for the gpu starting at 13.9, 14.1, etc. Each time, a fresh install was conducted (I was sure to find the right one, but absolutely no change).

Checked the logs, nothing out of the ordinary was reported, no sign of video failure, nothing...only notes the improper reboot, as was necessary once the game crashes.

No overclocking, at all. Everything is default.

Try a different cable, even if it sounds stupid. Any DVI cable?

This sounds VERY similar to the issue I am suffering at the moment. Only exception being that now, since this has happened with FO4, other games now crash the PC in a similar way.

Never rely on quicksave alone. There are people who get corrupt saves. I can tell you it happens in these games.

Always make new manual saves. This way you can revert back to one in case the quicksave gets bad.

Very strange problem indeed. If it is graphic card issue (overheat ,etc) if should affect other games as well.. To eliminate the possibility of save issue, is it possible to post the save that crashes (2-3mins into the game)? We can test it on our setup.