johnbl :
your nvidia graphics driver stopped responding to windows directx, directX tried to tell the card to restart and the cards driver failed to respond so directx called a bugcheck.
you have to find out why the driver/card failed to respond. you have two nvidia dirvers
\SystemRoot\system32\DRIVERS\nvlddmkm.sys Mon May 19 16:08:44 2014
C:\Program Files\NVIDIA Corporation\NvStreamSrv\NvStreamKms.sys Thu May 22 09:43:14 2014
I would disable the nvstreamkms.sys I think it is a driver that will allow you to stream you game video to other devices in real time. I think you can stop the service when are not actually using it and see if it solves your problem.
also, a steaming driver will depend on proper functions in the network driver. You have a real networks SystemRoot\system32\DRIVERS\Rt64win7.sys Thu Mar 04 05:42:52 2010
that is very old and most likely the nvidia streaming driver is hitting bugs in the old real networks driver (even if you are not streaming at the time) you might find that your overall problem will be fixed if you find a proper update to
rt64win7.sys (2010 is pretty old)
notes:
BIOS date 8/24/2010
BIOS version F2
motherboard Gigabyte Technology X58-USB3
cpu info:
Socket Designation Socket 1366
Processor Type Central Processor
Processor Family 01h - Other
Processor Manufacturer Intel
Processor ID a5060100fffbebbf
Processor Version Intel(R) Core(TM) i7 CPU
Processor Voltage 8ah - 1.0V
External Clock 133MHz
Max Speed 4000MHz
Current Speed 3200MHz
Note: you might also want to check for a BIOS update from gigabyte, the BIOS will set up the electronics on your motherboard and there can be mistakes in the electronics that get fixed with BIOS patches.
note: you might also want to disable /remove
\SystemRoot\system32\DRIVERS\voxaldriverx64.sys Mon Jan 27 19:46:51 2014
depending on what it is (video capture tool?) it could be causing the video adapter delay that leads to the bugcheck from directx. (just a guess)
Hi there,
thanks for all the great info.
I updated my BIOS to the latest stable version, and while that seems to have improved the situation briefly/minimally, both crash types still happen.
I've updated my network card and disabled streaming services, along with deleting the voxal drivers and uninstalling it.
However, I'm still getting the same errors.
One note - someone else mentioned to me to look at voltages on my PC - I don't understand this myself, but on CPUID, all thew voltages appear normal: +3.3 is 3.360, +5 is 5.053, etc. Except for 2 details - +12 moves between 1.2 and 3.6, and -5 is around -1.2 - -1.6. I don't understand these figures myself, but that difference sounds as a though it may be relevant?