Random reboots, error reporting calls it BSOD, next gen hardware

I haven't had time to look at all of the files, but you have 2 dump files, both blaming the Graphics driver.

Code:

BugCheck 116, {fffffa8018cf6390, fffff8800fdd6d1c, ffffffffc000009a, 4}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+98bd1c )
Followup: MachineOwner
---------

If you are overclocking the CPU or GPU, please set everything back to default values. Also, please go into BIOS and give me the values of the +12V, +5V and +3.3V readings.

Have you been monitoring the temps of your CPU and GPU especially during gaming or heavy work loads? if not olease start doing so. I believe Asus has a GPU utility that will do that as well as enable a custom fan profile to keep the temps lower. If you don't have a CPU temp program, I use Core Temp to monitor CPU temps.

I may suggest you reinstall the drivers by going to Nvidia.com and using the latest WHQL version. I believe there is a newer one than what you have. However, I don't believe the version is causing your crashing problems. Try using this tutorial to reinstall the drivers. NVIDIA Drivers - Avoid Problems If you are using 3 monitors you may use the 3D vision drivers. The point is, if you don't use it, don't install it. But the procedure will ensure you of the cleanest install you can get.

Let us know how that works out for you. As far as your hardware I don't notice any incompatibilities at a quick glance. And, I'm sure you know, you are not the first person to have problems with watch Dogs.

If you would, please let us know the BIOS values and try the newer drivers, using the linked method and let us know if it makes any difference for you.

Since I've got a triple display deal going on, I have the ability to leave monitoring programs running during play and watch them. I'll check the voltages and make another post. I'd check with AIDA when under load and when unloaded (older supplies could vary, I don't know about new ones...) but it won't show 12V.

I have nothing overclocked, all BIOS settings are at defaults except for the SATA is configured for RAID0.

The BIOS is probably the most important one and you will get more accurate results from bios. But, you can't get the bios results while playing, so we have to rely on software. Just be sure to have only one monitoring program at a time running. Sometimes when 2 programs are reading the same sensor, you will get inaccurate results.

That report said the exact same thing as the other 2 did. I don't know why your 3.3V dropped, but even with the drop, it was still within ATX standards. Try to update the driver going by that tutorial and see if that makes a difference. How old is this build, and did you have this problem from the start? is there any activity you can do that will make it BSOD right away? Let me know and I'll get back with you tomorrow, or someone else may jump in shortly.

In this case, perhaps we can isolate things better by running Driver Verifier.

Please do the following:

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
Driver Verifier - Enable and Disable

Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.

I recommend creating a system restore point before turning on driver verifier:
System Restore Point - Create

If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
Safe Mode

If you mean the new technology, I think not. Usually new technology has some issues until they have had time to work out the problems with bios updates and driver issues, but it is rarely to this extent. I know I went through it with my system, but it was usually bios settings didn't set to what you set them to and a lot of software hadn't caught up to the newer chipsets and things such as that. But, it usually does not involve BSODs. Your problem thus far seems to be graphics related. All of your dump files point to the graphics driver, which can also be the card itself too. Have you received any messages that the driver has crashed and recovered? The card is not that new and the drivers have had plenty of time to mature. I will check your board QVL list and see if you need a bios update for your CPU. The encoding is usually pretty stressful on the CPU, but depending on exactly what you were doing, could put some of the work on the GPU too. Have you run all of the Windows updates? if not, check again and see if there are more updates for your rig. Also, when you first installed the motherboard drivers, did you do it from the driver DVD or did you download them from Asus web site? The web site will have more up to date drivers than what was on the disk.

I have never run SLI, but in my experience with Graphics problems, it comes down to the Drivers, PSU, the board or the card itself. It is possible one of your cards are bad. We'll try some other things before we start pulling cards though.

I checked the QVL list and a bios update is not required for your CPU. If you would, please download CPUz, if you don't already have it, and post screenshots of the CPU, mainboard, memory and SPD tabs. The SPD tab is listed by dim slots and can be selected which slot from a drop down list in the upper left portion of the window. I only need the dim slots that are populated with ram.

I'll post more tomorrow when you have tried the things I and Golden have suggested.