Display Driver Crashing and Blue Screens

bugcheck 0x116 VIDEO_TDR_ERROR
means that the directx did not get a response from the video driver and attempted to reset the hardware and did not get a response in 30 seconds. So it figured the hardware failed and called a bugcheck to shut the system down.

anything in the system that prevents directx from getting a response can cause this.
I have see it happen because of firmware in solid state drives, old broken USB drivers, as well as mis configured audio drivers, as well as bugs in graphics drivers and in graphics hardware. Even heat related problems for the GPU can cause timing changes that mess up the electronics.

anyway, the best way to approach the problem is:
-update the BIOS or if it is up to date, reset it to defaults. A update will fix bugs and select better defaults and remove overclocking.
-update your USB drivers for your CPU chipset, for intel get them here:https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=20775
for external usb 3.0 chipsets get them from your motherboard vendors website.

-if you use a USB wireless ethernet card, update the driver.
-if you have a current nvidia graphics card, update the Ethernet driver so streaming will not get choked up because of ethernet driver bugs. It will also rebuild the database of hardware settings it sends to windows. Failure to do this may result in windows waiting for a response on hardware that is not there. IE, it is told you have a GPU with one set of settings then PNP detects a GPU with a different set of settings and assumes you have two GPUs. Fine until it tries to get a response from the first phantom GPU and bugchecks.
- if you use software overclocking of the CPU or GPU uninstall it until you figure out the problem.
- if your GPU is factory overclocked, use software to underclock the GPU by 50 or 100Mhz
(or maybe overclock your PCI-e bus to match the overclocked card)
- if you have a very old SSD over 2 years old, update the firmware.
- if you have a old SSD check the smart data in the drive with crystaldiskinfo.exe

anyway, that is some ideas. if you continue to get the bugcheck, you can try to reinstall directx on your system
I have see problems where a old driver delayed directx from getting its info. If you reinstall directx on windows 7 it would get first crack at the interrupts. (last driver installed gets first access on chained interrupts)

failing that, you need to change the memory dump type to full or kernel (not minidump) run verifier.exe and set some debug flags, reboot and wait until you get another bugcheck. put the new memory dump on a server and post a link.