PC Reboots

[Rosh]

When playing Sanctus Reach on my PC in 4K my PC reboots after a few seconds.
If I play the game via remote desktop on a tablet or laptop in lower resolution it works fine for hours.

My PC is watercooled with 2 Titans in SLI.

At first I suspected something like overheating or power issues, but I checked the power, temps etc... and all is fine. Voltages are in range, temps stay under 40C on CPU, NB and GPUs.
Any heat of power issues would be recorded on the main board and would result in a post error, but I am not getting those.

http://pastebin.com/cXg31Xna DXDiag
http://pastebin.com/gBaahwRC Error.log
http://pastebin.com/qAtqj86N Error_Trace.txt

If you have any suggestions...

[zakblood]

i also run a overclocked pc, with no issue,

Could you please attach a DxDiag report file to your message / reply?

Please attach a DxDiag report fie.
How to get a DxDiag report file:

1. Click on "START" (on Windows 8/10 press “Windows key” and the “R” key at the same time)
2. Click "run" (skip this step on Windows 8/10)
3. Type in "dxdiag" and click "OK"
4. Check through the tabs and perform all tests
5. Click "Save all Information..." and save the text file to a location of your choice
6. Attach the file to your message

then at least i can say it 's not this or that, and rule that out etc, then try something else

[pipfromslitherine]

Rebooting does sound like a heat issue though. Hmmm. Try adding the line

FPSLIMIT 100

to your USER.TXT file and see if the issue stops. If so then try reducing the value until you have a reasonable framerate with no crashes. Is your PC running any clock-management drivers (power saving)?

Cheers

Pip

[Rosh]

Thanks, I will adjust the user.txt and see if it brings anything.

I am pretty sure it is not temperature related. I had the ASUS tools and Afterburner record the values for temperatures and voltages and nothing showed. Compared them right after the crash as well and all was good.
I have all power saving disabled on my machine, it is built for speed, performance and silence 

Thanks,

R.

[Rosh]

It looks like adding the FPS limit solved the problem