I believe this wasn't exported when it was first created, possibly due to an issue with the link between UE and Jira. Excellent to hear it's resolved though :)

I've not had the opportunity to load the map myself as I've been kept busy with other duties but also that the save files need to be opened in Unity and as we're currently working on a Beta version I do not have access to it (while the code team does.).

Either way it's best to get a more expert view on these issues and although the issue might be in the map (fairly unlikely as we'd see it affecting more users) it would still require resolution by code. :)

Hmmm this truly is bizarre, in the absence of obvious hardware faults it's difficult to say what might be happening. If this was a hardware issue as Scott & Stefan surmised then you would expect to see similar results when the PC is placed under strain and as you've demonstrated this appears to not be the case.

One question that hasn't been asked yet is how exactly is your PC rebooting. I.e. Are you seeing a graceful reboot where Windows attempts to shut your programs down one by one or does it simply power down immediately and then start back up? If it's the latter then it would imply that nothing is sending a signal to windows to restart but rather something is causing black screen crash which could still imply hardware faults.

Another hardware test you could run is dumping memtest86 onto removable media and booting it to do a full in-depth test of your memory beyond that which is the Windows diagnostic tools are capable of. You could also try looking for some hard disk diagnostic tools, perhaps straight from the manufacturer as they often offer free tools.

Eliminating a hardware issue would seem to imply some form of Software or OS level issue exists, perhaps an unusual interaction between some other software on your PC and WFTO? It might be worth trying to disable anything else that is running at the time of WFTO and running the game then, or even something deeper in the OS itself. For that I'd suggest the following:

1. Ensure all your drivers are up to date including unusual ones like network drivers etc.
2. Try everything in this article: General Crash Troubleshooting just in case. Including uninstalling and reinstalling the game entirely.
3. Check to see if other Unity based games suffer from similar issues for you
4. Disable all other application that are running alongside WFTO and Steam including Anti Virus
5. Disable all unnecessary device drivers via the device manager, disable as much as you can until only the bare necessities are running. See if you get the same result.
6. As an extreme measure consider a second bootable partition or hard drive with a clean install of Windows just for testing purposes.

Sorry for all this hassle, really wish we could get you in the game but this demonstrates one of the worst aspects of PC Gaming so many moving parts that could interact to create unusual results, now we just have to try and eliminate variables until we find the root cause.

Cool keep us informed :) Just to be aware we might have fixed it internally so if you like you can give it a go when the next patch is out.

Thanks for keeping up on these reports we're still investigating :)

From what I can tell this is slated for review for the next major patch at least. Can't say exactly when it'll get another look by the coders but there's a small chance it might get a look into sooner.

Reopening as per comment above. This still affects clients in Multiplayer.