Hello fsmith.
Intel(R) USB 3.0 eXtensible Host Controller Driver is failing here.
Code:
fffff880`033fed68 fffff880`040fb414Unable to load image \SystemRoot\system32\DRIVERS\iusb3xhc.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for iusb3xhc.sys
*** ERROR: Module load completed but symbols could not be loaded for iusb3xhc.sys
iusb3xhc+0x49414
And this driver is somehow old.
Code:
fffff880`040b2000 fffff880`04177000 iusb3xhc T (no symbols)
Loaded symbol image file: iusb3xhc.sys
Image path: \SystemRoot\system32\DRIVERS\iusb3xhc.sys
Image name: iusb3xhc.sys
Timestamp: Mon May 21 12:51:40 2012 (4FB9ED04)
CheckSum: 000CA061
ImageSize: 000C5000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Update it from https://downloadcenter.intel.com/default.aspx
Asmedia XHCI drivers are very old, too.
Code:
fffff880`04d23000 fffff880`04d87000 asmtxhci (deferred)
Image path: \SystemRoot\system32\DRIVERS\asmtxhci.sys
Image name: asmtxhci.sys
Timestamp: Thu Nov 03 08:30:22 2011 (4EB203C6)
CheckSum: 0006C541
ImageSize: 00064000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Update the driver and firmware from http://station-drivers.com/page/asmedia.htm
Intel(R) 82579V Gigabit Network Connection driver is also failing.
Code:
fffff880`033fe338 fffff880`04c60f1fUnable to load image \SystemRoot\system32\DRIVERS\e1c62x64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for e1c62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e1c62x64.sys
e1c62x64+0x20f1f
But this is not really old.
Code:
fffff880`04c40000 fffff880`04cbc000 e1c62x64 T (no symbols)
Loaded symbol image file: e1c62x64.sys
Image path: \SystemRoot\system32\DRIVERS\e1c62x64.sys
Image name: e1c62x64.sys
Timestamp: Thu Feb 21 10:44:02 2013 (5125AD1A)
CheckSum: 0008277C
ImageSize: 0007C000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
So it may not be a driver failure itself. Still, first try to update the driver from https://downloadcenter.intel.com/default.aspx. Also, BitDefender sometimes causes network blockage. At least as a test, uninstall BitDefender. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one.
The display driver is also failing there.
Code:
fffff880`033fec10 fffff880`07322a28Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
nvlddmkm+0x51ca28
And it is the latest.
Code:
fffff880`06e06000 fffff880`078e7000 nvlddmkm T (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
Image name: nvlddmkm.sys
Timestamp: Mon May 13 00:39:45 2013 (518FE8F9)
CheckSum: 00AB6DED
ImageSize: 00AE1000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
3: kd> lmvm e1c62x64
The latest version of nvidia display driver is sometimes buggy. You may try to roll it back to an earlier one that worked good there. Follow Driver Rollback
Also, do some tests.
Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark
Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.
Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.
Let us know about the wattage of your PSU. And let us know the results of the tests; let us know how it is working after applying those changes.
_____________________________________________________________________________________
BSOD ANALYSIS:
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : hardware ( USBPORT!USBPORT_EndpointFromHandle+26 )
Followup: MachineOwner
---------