Fallout 4 Rebooting my computer? : Fallout 4

» Sun Nov 29, 2015 4:52 pm

I just wanted to know if the following sequence is happening to anyone else.

I run Fallout 4 but cannot currently leave Vault 111. Anytime during the tutorial portion inside Vault 111 my computer will just randomly reboot, not crash but reboot. First thing I thought was maybe my hardware is overheating, so I check it while I'm playing GPU is around 58-60C which is normal (I think), CPU is under 40C, all my fans are running fine. I try other games like Skyrim with mods, New Vegas heavily modded, and stress test with Rome II and nothing like the random reboot happens.

PC build:

i7 4770k @3.50GHz

Nvidia GX 770 Lastest Drivers installed

16gb RAM

1tb HDD

Windows 10 64bit

I've done a number of tests to try and pinpoint what might be causing this.

I changed my settings from high to medium then low, turning off god rays and the different elements in the options checklist. Reboots still occurred.

I thought maybe I have corrupt save data? Tried reinstalling after deleting saves and verifying cache. Still reboots.

I opted for the latest beta build 1.2 hoping that would fix it. Still reboots.

Also when I check Event Viewer there's nothing stating an error other than the reboots causing Windows to not shut down properly.

I've had people tell me that Windows 10 might be an issue, but at the same time I've had friends play Fallout 4 fine on Windows 10.

So either my hardware is failing somehow (which I doubt since it's only a year old) or there's something specifically causing my computer to crash while I play but to prevent damage to hardware the computer reboots instead of crashing to desktop.

Any help or information regarding this would be most appreciated

» Sun Nov 29, 2015 8:44 pm

I'd check the temperature on your motherboard RAM if i were u.

If the temperature gets too high on your RAM, it will just cut the power on the ram, which is like hitting the reset button on your Computer.

» Sun Nov 29, 2015 11:28 am

Computers only hard reset when there is a fault with hardware. It's a failsafe to prevent damage to the board, or worse case to prevent an electrical fire.

Smell the inside of your machine and see if it smells melted. That's not always going to be the case, but worth doing.

» Sun Nov 29, 2015 4:11 pm

If you are not overclocking, enter the BIOS and make sure RAM voltage is not higher than it should be. !!!

It could be a defective RAM, although a defective motherboard can cause this as well. That's the worse scenario.

However all your other games working fine.

The usual symptom of memory problems is that Windows displays the Blue Screen of Death.

As odd as it sounds, the most time if memory doesn't operate correctly the most likely cause is a overloaded PSU or a most likely cause is system overheating.

Even, so I would begin with testing the memory modules, if you thing Ram is the culprit.

-------------

You can use: http://www.memtest86.com

If you run the testings, configure Memtest86 to do deep testing and multiple loops. Let it run overnight, and log the results.

Note the addresses where errors occurred. If errors occur at the same address or nearby addresses, it's more likely that the module is defective.

If the errors occur at random addresses, it's more likely that the problem is the PSU or you have high system temperatures.

--------------

So, If the errors occur at the same or nearby adresses, pull the modules out.

First ground yourself, by touching your metal case frame or the PSU.

Remove and reinstall all your memory modules and see that they are seated properly. Also before that clean the memory modules contacts.

Take a banknote (a clean one for better results). The harshness of that banknote will clean the contacts without damaging them. !!!

---------------

Another trial and error method is, if your system has more than one memory module installed - remove one module to see if that solves the problem.

If you have more than two modules use them in pairs (at firts) and run the game again.

And lastly If you have another system (or maybe a system from a friend), install the memory there. If it runs there, the problem is almost certainly not the memory. !!!