Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x83244000 PsLoadedModuleList = 0x8338c810
Debug session time: Wed Oct 27 06:05:44.166 2010 (GMT-4)
System Uptime: 0 days 1:55:40.633
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {2f3, 2, 1, 8328434d}
Probably caused by : bthport.sys ( bthport!RefObj_UpdateRefHistory+18 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 000002f3, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 8328434d, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 833ac718
Unable to read MiSystemVaType memory at 8338c160
000002f3
CURRENT_IRQL: 2
FAULTING_IP:
nt!__InterlockedIncrement+5
8328434d f00fc101 lock xadd dword ptr [ecx],eax
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: 807e1850 -- (.trap 0xffffffff807e1850)
ErrCode = 00000002
eax=00000001 ebx=83210700 ecx=000002f3 edx=00000000 esi=86483e70 edi=82f7daa8
eip=8328434d esp=807e18c4 ebp=807e18cc iopl=0 nv up ei pl nz ac pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010216
nt!__InterlockedIncrement+0x5:
8328434d f00fc101 lock xadd dword ptr [ecx],eax ds:0023:000002f3=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 8328434d to 8328a82b
STACK_TEXT:
807e1850 8328434d badb0d00 00000000 50485442 nt!KiTrap0E+0x2cf
807e18c0 82f78db6 86483e70 807e18f4 82f78fca nt!__InterlockedIncrement+0x5
807e18cc 82f78fca 86483e70 00000087 82f7c13a bthport!RefObj_UpdateRefHistory+0x18
807e18f4 82f4563d 86483e70 86483e58 00000087 bthport!RefObj_ReleaseEx+0x28
807e1918 82f456be 864cab68 864b60f4 88241008 bthport!HCI_CompleteAclRdHciPkt+0x59
807e1930 82f6858e 864caad8 00000000 88241008 bthport!HCI_CompleteAclRdChain+0x52
807e1954 82f79077 02241008 88241014 807e19c8 bthport!L2CapCon_Destroy+0x84
807e196c 82f4e501 00000000 82f5178c 00000b15 bthport!RefObj_ReleaseEx+0xd5
807e198c 82f51aff 8801d228 807e19c8 c000009d bthport!HCI_CxnDrainMoveList+0x41
807e19f0 82f51bc1 880dc008 0201d228 0dc40208 bthport!HCI_HandleDisconnectionComplete+0x373
807e1a14 82f4969a 880dc008 00000000 88165ac8 bthport!Fn_EVENT_DisconnectionComplete+0x39
807e1a6c 82f57d9e 880dc008 00000000 88165ac8 bthport!HCI_DoCmdCompletion+0x2a2
807e1a94 82f607c0 880dc008 88165ac8 83210700 bthport!HCI_ProcessAsynchronousEvent+0x70
807e1ab8 82f60d29 880dc008 85923008 880e26e0 bthport!HCI_ProcessEventAtDPC+0xfc
807e1adc 82f3f122 020dc008 85923008 00000006 bthport!HCI_ProcessMpBip+0xe5
807e1af0 82f2c5d9 85923008 832107a0 880f9350 bthport!BTHPORT_RecvMpBip+0x38
807e1b0c 82f31910 880e26e0 88165ac8 00000006 BTHUSB!BthUsb_EventTransferComplete+0x87
807e1b64 82f31d13 880e2b08 807e1b80 880dcdcf BTHUSB!UsbWrapWorkRoutine+0xce
807e1b8c 832acb33 880e2b08 880dcca8 01000003 BTHUSB!UsbWrapInterruptReadComplete+0x11d
807e1bd0 90db0868 83284354 889de178 00000000 nt!IopfCompleteRequest+0x128
807e1c00 90db1178 851a8710 880dcca8 880f9280 USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x6e0
807e1c2c 90db49af 86c10028 86c100f0 86c10a98 USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x33b
807e1c54 90daed18 86c10028 86c10a98 86c10002 USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xbc
807e1c78 832ac3b5 86c10aa4 86c10002 00000000 USBPORT!USBPORT_Xdpc_Worker+0x173
807e1cd4 832ac218 807c5120 807ca800 00000000 nt!KiExecuteAllDpcs+0xf9
807e1d20 832ac038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xd5
807e1d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38
STACK_COMMAND: kb
FOLLOWUP_IP:
bthport!RefObj_UpdateRefHistory+18
82f78db6 48 dec eax
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: bthport!RefObj_UpdateRefHistory+18
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: bthport
IMAGE_NAME: bthport.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc882
FAILURE_BUCKET_ID: 0xA_bthport!RefObj_UpdateRefHistory+18
BUCKET_ID: 0xA_bthport!RefObj_UpdateRefHistory+18
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {c0000005, 83287897, 8b127b38, 8b127710}
Probably caused by : afd.sys ( afd!AfdFreeConnectionResources+45 )
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: 83287897, The address that the exception occurred at
Arg3: 8b127b38, Exception Record Address
Arg4: 8b127710, 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:
nt!PspReturnQuota+25
83287897 8b3e mov edi,dword ptr [esi]
EXCEPTION_RECORD: 8b127b38 -- (.exr 0xffffffff8b127b38)
ExceptionAddress: 83287897 (nt!PspReturnQuota+0x00000025)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000100
Attempt to read from address 00000100
CONTEXT: 8b127710 -- (.cxr 0xffffffff8b127710)
eax=00000080 ebx=00000400 ecx=00000001 edx=00001edf esi=00000100 edi=00000080
eip=83287897 esp=8b127c00 ebp=8b127c1c iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!PspReturnQuota+0x25:
83287897 8b3e mov edi,dword ptr [esi] ds:0023:00000100=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
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: 00000100
READ_ADDRESS: GetPointerFromAddress: unable to read from 8337e718
Unable to read MiSystemVaType memory at 8335e160
00000100
FOLLOWUP_IP:
afd!AfdFreeConnectionResources+45
8e8a97a2 83660c00 and dword ptr [esi+0Ch],0
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from 83437a36 to 83287897
STACK_TEXT:
8b127c1c 83437a36 00000080 00000000 00000001 nt!PspReturnQuota+0x25
8b127c3c 834379ac 00000400 000000f8 850d4040 nt!PsReturnSharedPoolQuota+0x21
8b127c68 8343778d 885850f8 885850e0 00000000 nt!ObpFreeObject+0x213
8b127c7c 8327ef60 00000000 00020000 88585180 nt!ObpRemoveObjectRoutine+0x5e
8b127c90 8327eed0 885850f8 8e8a97a2 88585180 nt!ObfDereferenceObjectWithTag+0x88
8b127c98 8e8a97a2 88585180 8e897ea8 8e89f3e9 nt!ObfDereferenceObject+0xd
8b127cac 8e889795 88585180 885851f8 8e897ea8 afd!AfdFreeConnectionResources+0x45
8b127cc4 8e89e75c 88585180 8b127cec 8e88929e afd!AfdFreeConnectionEx+0xd6
8b127cd0 8e88929e 885851f8 865100d8 8649ef08 afd!AfdFreeConnection+0x1d
8b127cec 83436815 8649ef08 00000000 850d6798 afd!AfdDoWork+0x51
8b127d00 83283f3b 865100d8 00000000 850d6798 nt!IopProcessWorkItem+0x23
8b127d50 834246d3 00000001 a374a225 00000000 nt!ExpWorkerThread+0x10d
8b127d90 832d60f9 83283e2e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: afd!AfdFreeConnectionResources+45
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: afd
IMAGE_NAME: afd.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bbf62
STACK_COMMAND: .cxr 0xffffffff8b127710 ; kb
FAILURE_BUCKET_ID: 0x7E_afd!AfdFreeConnectionResources+45
BUCKET_ID: 0x7E_afd!AfdFreeConnectionResources+45
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 81f93174, a61c7670, 0}
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+158174 )
Followup: MachineOwner
---------
0: 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: 81f93174, The address that the exception occurred at
Arg3: a61c7670, 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:
nvlddmkm+158174
81f93174 3b480c cmp ecx,dword ptr [eax+0Ch]
TRAP_FRAME: a61c7670 -- (.trap 0xffffffffa61c7670)
ErrCode = 00000000
eax=6a0e75f9 ebx=8651ad30 ecx=108550b6 edx=18000000 esi=00000000 edi=00000000
eip=81f93174 esp=a61c76e4 ebp=a61c76e4 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nvlddmkm+0x158174:
81f93174 3b480c cmp ecx,dword ptr [eax+0Ch] ds:0023:6a0e7605=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: Civ4BeyondSwor
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 8235e2dc to 81f93174
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
a61c76e4 8235e2dc 18000000 108550b6 a61c770c nvlddmkm+0x158174
a61c76fc 82363758 4c44444d 18000000 108550b6 nvlddmkm+0x5232dc
a61c7724 81f6343d 850e4008 8651ad30 008338b1 nvlddmkm+0x528758
a61c782c 81f65f2a 8651ad30 00000000 00000000 nvlddmkm+0x12843d
a61c78b4 81ef5f0a 00000000 85474008 a61c78f4 nvlddmkm+0x12af2a
a61c78d0 81ef7172 a61c78f4 85474008 85474008 nvlddmkm+0xbaf0a
a61c78e4 81e85626 a61c78f4 85185260 c1d00781 nvlddmkm+0xbc172
a61c798c 81e87646 caf003e5 00000000 854c6a08 nvlddmkm+0x4a626
a61c79ac 81e62df6 85185260 00000000 00000000 nvlddmkm+0x4c646
a61c79fc 823a6574 a61c7a9c 832236ee a61c7a9c nvlddmkm+0x27df6
a61c7a18 828e0779 85474008 823a654c a963d208 nvlddmkm+0x56b574
a61c7a44 828df514 85474008 a61c7a9c a963dc40 dxgkrnl+0x25779
a61c7abc 828dd481 00000000 00000000 9719f8f8 dxgkrnl+0x24514
a61c7ae4 828df95e 00000001 00000000 00000000 dxgkrnl+0x22481
a61c7b08 828dfd6e 00000000 00000000 ad68b388 dxgkrnl+0x2495e
a61c7b64 828e0594 a61c7b98 00000001 24912973 dxgkrnl+0x24d6e
a61c7d28 8329844a 0ef4fee0 0ef4fef0 776564f4 dxgkrnl+0x25594
a61c7d28 776564f4 0ef4fee0 0ef4fef0 776564f4 nt!KiFastCallEntry+0x12a
0ef4fef0 00000000 00000000 00000000 00000000 0x776564f4
STACK_COMMAND: kb
FOLLOWUP_IP:
nvlddmkm+158174
81f93174 3b480c cmp ecx,dword ptr [eax+0Ch]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nvlddmkm+158174
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4c379162
FAILURE_BUCKET_ID: 0x8E_nvlddmkm+158174
BUCKET_ID: 0x8E_nvlddmkm+158174
Followup: MachineOwner
---------