Looks like your USB hub is causing the issues. I suggest updating your USB and chipset drivers in Device Manager.
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Jonathan\Desktop\033110-16894-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x83648000 PsLoadedModuleList = 0x83790810
Debug session time: Tue Mar 30 20:13:59.455 2010 (GMT-4)
System Uptime: 0 days 0:00:18.922
Loading Kernel Symbols
...............................................................
..............................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {c0000005, 8df04e3f, 8b51f4e0, 8b51f0c0}
Probably caused by : hidusb.sys ( hidusb!HumCallUSB+1b4 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8df04e3f, The address that the exception occurred at
Arg3: 8b51f4e0, Exception Record Address
Arg4: 8b51f0c0, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
+9e
8df04e3f f6461c40 test byte ptr [esi+1Ch],40h
EXCEPTION_RECORD: 8b51f4e0 -- (.exr 0xffffffff8b51f4e0)
ExceptionAddress: 8df04e3f
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 6772746f
Attempt to read from address 6772746f
CONTEXT: 8b51f0c0 -- (.cxr 0xffffffff8b51f0c0)
eax=00000000 ebx=862d05d0 ecx=862d05d0 edx=00000000 esi=67727453 edi=862d06d0
eip=8df04e3f esp=8b51f5a8 ebp=8b51f7dc iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
8df04e3f f6461c40 test byte ptr [esi+1Ch],40h ds:0023:6772746f=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: STRING_DEREFERENCE
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 00000000
EXCEPTION_PARAMETER2: 6772746f
READ_ADDRESS: GetPointerFromAddress: unable to read from 837b0718
Unable to read MiSystemVaType memory at 83790160
6772746f
FOLLOWUP_IP:
hidusb!HumCallUSB+1b4
82b50978 817d0803010000 cmp dword ptr [ebp+8],103h
FAILED_INSTRUCTION_ADDRESS:
+1b4
8df04e3f f6461c40 test byte ptr [esi+1Ch],40h
BUGCHECK_STR: 0x7E
LOCK_ADDRESS: 837adf60 -- (!locks 837adf60)
Resource @ nt!PiEngineLock (0x837adf60) Available
WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.
WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.
1 total locks
PNP_TRIAGE:
Lock address : 0x837adf60
Thread Count : 0
Thread address: 0x00000000
Thread wait : 0x0
LAST_CONTROL_TRANSFER: from 82b50978 to 8df04e3f
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
8b51f7dc 82b50978 8704c5f4 8704c2a0 00000000 0x8df04e3f
8b51f80c 82b50dbb 00000103 8704c2a0 8704c5f4 hidusb!HumCallUSB+0x1b4
8b51f82c 82b50e97 8704c3a0 0000000b 00000001 hidusb!HumGetDescriptorRequest+0xd7
8b51f864 82b4f53d 8704c3a0 8704c5f0 00000000 hidusb!HumGetDeviceDescriptor+0x45
8b51f880 82b547ee 8704c3a0 00000000 8704c710 hidusb!HumInitDevice+0x1b
8b51f8b0 82b5b377 8704c3a0 86436e28 86436e28 hidusb!HumPnP+0x184
8b51f8c4 82b6470d 8704c3a0 86436e28 86436f44 HIDCLASS!HidpCallDriver+0x3f
8b51f8ec 82b66a10 8704c3a0 86436e28 86436e28 HIDCLASS!HidpCallDriverSynchronous+0x3b
8b51f90c 82b64805 8704c458 86436e28 86436e28 HIDCLASS!HidpStartDevice+0x56
8b51f928 82b649a3 8704c458 86436e28 8704c458 HIDCLASS!HidpFdoPnp+0x8b
8b51f944 82b5bb54 8704c458 00000000 86436e28 HIDCLASS!HidpIrpMajorPnp+0x5b
8b51f960 836844bc 0004c3a0 0000001b 86436f4c HIDCLASS!HidpMajorHandler+0xc8
8b51f9b0 837f0d60 00000000 8686f030 8704c338 nt!IofCallDriver+0x63
8b51f9cc 8365c475 8b51f9fc 8365bb64 8704c338 nt!PnpAsynchronousCall+0x92
8b51fa30 837f6bdc 8365bb64 8704c338 8704ad48 nt!PnpStartDevice+0xe1
8b51fa8c 837f6aa5 8704c338 00000024 00000000 nt!PnpStartDeviceNode+0x12c
8b51faa8 837ef8a1 00000000 00000000 87040388 nt!PipProcessStartPhase1+0x62
8b51fca4 837e961a 86b40548 87040388 8b51fcd0 nt!PipProcessDevNodeTree+0x188
8b51fcd8 8365bf7c 837abe80 854bca70 837825bc nt!PiProcessReenumeration+0x74
8b51fd00 836b5f2b 00000000 00000000 854bca70 nt!PnpDeviceActionWorker+0x224
8b51fd50 8385666d 00000001 af772e5a 00000000 nt!ExpWorkerThread+0x10d
8b51fd90 837080d9 836b5e1e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: hidusb!HumCallUSB+1b4
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hidusb
IMAGE_NAME: hidusb.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc868
STACK_COMMAND: .cxr 0xffffffff8b51f0c0 ; kb
FAILURE_BUCKET_ID: 0x7E_BAD_IP_hidusb!HumCallUSB+1b4
BUCKET_ID: 0x7E_BAD_IP_hidusb!HumCallUSB+1b4
Followup: MachineOwner
---------
Quote