Restarts computer

  • updated
  • Completed - Resolved

Just installed the game. Tried first play through of Campaign and around the first wave of enemy coming in, my computer reboots.

Game Version:
Steam Public
CMDR Bill Paxton

I tried multiple times, and it just reboots every time, can't get past the very beginning of the campaign without it causing my computer to reboot.


War for the Overworld Launcher Log.txt

Windows 7 Pro 64bit
Intel i7-4790K
GeForce 980 Ti (driver 373.06)

Samsung 850 Pro SSD

CPU hottest 44C
GPU hottest 81C

WFTO Build 1.4.2f9

Tried "Verify Integrity of Game Cache" in Steam Local Files tab.

Just played almost 3 hours of Battlefield 4 with no problems today.

Other games I have installed that have no issue are the new Doom, Elite Dangerous, XCOM 2, Civilization V, Wolfenstein the New Order, and FarCry Primal. All these games run Flawless.

Don't believe it to be a hardware problem.

Stefan Furcht
  • Under Review

Hello CMDR,
such issues are normally not caused by games itself but by an issue with the hardware configuration, which only occur when the system is under full load.
A shutdown either happens, when the PSU can not supply enough power for all the installed devices or when the cooling is not working to full extent, which can cause an emergency shutdown because of overheating.

When the PSU is too weak one can only get a better one or disable/remove power hungry devices.
Cooling issues are either caused by dusty fans not able to cool as good as usual or by overclocking the system while cooling is not strong enough.

WftO can be quite affording depending on how large maps you play for how long and how big you build.
Your rig looks like a real monster which should have no issues handling the game,
but if PSU or cooling is not strong enough it can run into issues even easier than with less powerful hardware.
It is also hard to compare with the mentioned games as you can go big or small in WftO.
However I have never heard of such problems with the campaign, which is not too heavy in terms of CPU/GPU load.

Did you look into Windows Event Viewer if there are any errors which explain the shut down?
(Type "eventvwr" in run/search bar, under "Windows Logs" -> "System" and "Application", look for red log entries at the exact time it did shut down)

Does it give any pointers?

CMDR Bill Paxton

My Power Supply is a Corsair HX 850.

So I uninstalled the game and re-installed. Got through the 1st tutorial of the campaign. Much farther than I had ever gotten before. Started the 2nd part of the campaign and when the good guys broke through the wall, I summed a rally and then used a lightning spell and the game crashed my computer to a hard reboot.

The event view for Windows Logs / Application shows the following at time 11:44:06:

  • Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

The Windows Logs / System shows two items that occurred at time 11:44:05:

  • A timeout was reached (30000 milliseconds) while waiting for the Origin Web Helper Service service to connect.
  • The Origin Web Helper Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.

These are all the items with "Error" at the time of the crash reboot.

Scott Richmond Programmer & Producer
  • Not a Bug

You probably won't find much of use in any logs - If the PC is hard rebooting like you're suggesting then you've got some fairly serious hardware issues. WFTO does stress a number of components which often causes bad hardware to have problems. Take a look at this guide to troubleshoot further:

CMDR Bill Paxton

From your perspective it may look like a hardware issue, but when you see from my view where I play on this computer almost every day and many gaming sessions for hours on end with no problems except when trying to play WFTO, it seems like a specific game problem to me. I'm more than willing to try and figure this problem out as I am a fan of this game and would love to see it work. Will run some Prime95 torture tests and the Windows Memory tester. I will let you know of the results.

In the last few days I have played quite a bit of Battlefield 4 with no problems whatsoever. You can see my battle reports here, look under section "Latest Reports":

One round lasted a full hour before the round ended and the next map loaded:

I have logged 2378 hours of gameplay (hours played shown in Steam) in the game Elite Dangerous (which I recently quit playing), and you can even see some of my past recorded PvP gameplay on my youtube channel here:

I also have 166 hours (Steam report) logged in XCOM2 as an example which is a game played from a similar perspective, looking down on your units from above. I haven't seen any problems playing StarCraft 2 either for that matter which also has that game perspective.

If this computer had "Serious" hardware issues, I'm sure it would have shown up while playing some of these other games as well. Will post tests results soon. :-)

CMDR Bill Paxton

Windows Memory Diagnostic test result:

CMDR Bill Paxton

Prime 95 - 2HR run, Zero Errors:

Scott Richmond Programmer & Producer

One test you're not covering is what happens when both CPU and GPU are under load - Try running Prime95 and Furmark at the same time.

Lee "Noontide" Moon
  • Pending Customer
CMDR Bill Paxton
Quote from Scott Richmond

One test you're not covering is what happens when both CPU and GPU are under load - Try running Prime95 and Furmark at the same time.

I just uploaded two videos to my Youtube channel of me playing Battlefield 4 last night. Recorded with Shadowplay. Pretty sure that exercises both CPU and GPU. Check them out:

I will also try your suggestion, as I said, I'm willing to do what we can to try and figure out why WFTO doesn't work properly. Will post the results later. :-)