I copied and pasted the debug log from what i can see when trying to read the dump file.
Hopefully it can help pinpoint the issue.
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\matt\Desktop\091211-17643-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Inaccessible path: 'c:\windows\i386'
Symbol search path is: srv*c:\symbols*
http://msdl.microsoft.com/download/symbols
Executable search path is: c:\windows\i386
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.x86fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0x83213000 PsLoadedModuleList = 0x8335c4f0
Debug session time: Mon Sep 12 08:39:47.759 2011 (UTC - 4:00)
System Uptime: 0 days 11:26:34.492
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 928adc82, bdc17978, 0}
*** WARNING: Unable to verify timestamp for bckd.sys
*** ERROR: Module load completed but symbols could not be loaded for bckd.sys
Probably caused by : tdx.sys ( tdx!TdxCreateControlChannel+70 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: 928adc82, The address that the exception occurred at
Arg3: bdc17978, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
tdx!TdxCreateControlChannel+70
928adc82 89700c mov dword ptr [eax+0Ch],esi
TRAP_FRAME: bdc17978 -- (.trap 0xffffffffbdc17978)
ErrCode = 00000002
eax=000001c0 ebx=00000000 ecx=00000002 edx=00000000 esi=85e470a8 edi=00000003
eip=928adc82 esp=bdc179ec ebp=bdc179f4 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
tdx!TdxCreateControlChannel+0x70:
928adc82 89700c mov dword ptr [eax+0Ch],esi ds:0023:000001cc=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: uTorrent.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 928b5009 to 928adc82
STACK_TEXT:
bdc179f4 928b5009 86b7d1c0 000001c0 00000000 tdx!TdxCreateControlChannel+0x70
bdc17a2c 8324a58e 86b908e8 8663c0c0 00000000 tdx!TdxTdiDispatchCreate+0x5f
bdc17a44 9292c292 00000000 8663c19c 8663c0c0 nt!IofCallDriver+0x63
WARNING: Stack unwind information not available. Following frames may be wrong.
bdc17a58 92928033 86dda0d0 00000000 8663c0c0 bckd+0x6292
bdc17a84 9292d157 00000000 bdc17aac 9292f837 bckd+0x2033
bdc17a90 9292f837 86dda018 8663c0c0 86dda0d0 bckd+0x7157
bdc17aac 9292f93e 00dda0d0 c7668000 00000000 bckd+0x9837
bdc17ac8 9293088e 86dda0d0 c7668000 df0c8a44 bckd+0x993e
bdc17ae4 92931336 86dda0d0 df0c89b0 df0c8a44 bckd+0xa88e
bdc17b04 8324a58e 86dda018 df0c89b0 df0c89b0 bckd+0xb336
bdc17b1c 928f1642 00021c10 86203008 877d4938 nt!IofCallDriver+0x63
bdc17b70 928eedd0 86203008 00000000 86388258 afd!AfdBeginDisconnect+0x2cb
bdc17be0 928ef2b5 86388258 86bfd640 bdc17c08 afd!AfdCleanupCore+0x346
bdc17bf0 8324a58e 86bfd640 86388258 85a2de68 afd!AfdDispatch+0x125
bdc17c08 83445aa6 85998508 85a2de50 00000001 nt!IofCallDriver+0x63
bdc17c48 83436f47 85fc75a8 85a2de68 00000001 nt!IopCloseFile+0x2f3
bdc17c94 83458394 85fc75a8 ca44b4c8 85ed3030 nt!ObpDecrementHandleCount+0x139
bdc17cdc 834580d4 ca44b4c8 8ba23b40 85fc75a8 nt!ObpCloseHandleTableEntry+0x203
bdc17d0c 8345846e 85fc75a8 85ed3001 02a7fd24 nt!ObpCloseHandle+0x7f
bdc17d28 832511fa 000005a0 02a7fd80 76f770b4 nt!NtClose+0x4e
bdc17d28 76f770b4 000005a0 02a7fd80 76f770b4 nt!KiFastCallEntry+0x12a
02a7fd80 00000000 00000000 00000000 00000000 0x76f770b4
STACK_COMMAND: kb
FOLLOWUP_IP:
tdx!TdxCreateControlChannel+70
928adc82 89700c mov dword ptr [eax+0Ch],esi
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: tdx!TdxCreateControlChannel+70
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: tdx
IMAGE_NAME: tdx.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce78935
FAILURE_BUCKET_ID: 0x8E_tdx!TdxCreateControlChannel+70
BUCKET_ID: 0x8E_tdx!TdxCreateControlChannel+70
Followup: MachineOwner
---------