Code:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a4c000 PsLoadedModuleList = 0xfffff800`02c89e50
Debug session time: Thu Nov 25 19:15:20.424 2010 (GMT-5)
System Uptime: 0 days 0:29:37.907
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : PCIIDEX.SYS ( PCIIDEX!BmFlush+25 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
OVERLAPPED_MODULE: Address regions for 'nvlddmkm' and 'nvlddmkm.sys' overlap
EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.
FAULTING_IP:
+5c54952f01a5dae4
00000000`00000000 ?? ???
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x1E
PROCESS_NAME: System
CURRENT_IRQL: 2
EXCEPTION_RECORD: fffff88002ffb6c8 -- (.exr 0xfffff88002ffb6c8)
ExceptionAddress: fffff80002a1fe8d (hal!memcpy+0x00000000000000bd)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME: fffff88002ffb770 -- (.trap 0xfffff88002ffb770)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=6d61726170206563 rbx=0000000000000000 rcx=00fef88006209020
rdx=ff01000002a61000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a1fe8d rsp=fffff88002ffb908 rbp=0000000000000002
r8=0000000000001000 r9=0000000000000080 r10=909090007325203a
r11=00fef88006209000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
hal!memcpy+0xbd:
fffff800`02a1fe8d 488941e0 mov qword ptr [rcx-20h],rax ds:8000:00fef880`06209000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002ab446e to fffff80002abc710
STACK_TEXT:
fffff880`02ffa7b8 fffff800`02ab446e : 00000000`00000010 fffff880`02ffa9d0 fffff880`02ffaf30 fffff800`02ae9668 : nt!KeBugCheck
fffff880`02ffa7c0 fffff800`02ae240d : fffff800`02ccab7c fffff800`02c04e84 fffff800`02a4c000 fffff880`02ffb6c8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02ffa7f0 fffff800`02ae9a90 : fffff800`02c0bb14 fffff880`02ffa868 fffff880`02ffb6c8 fffff800`02a4c000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02ffa820 fffff800`02af69ef : fffff880`02ffb6c8 fffff880`02ffaf30 fffff880`00000000 00000000`00000002 : nt!RtlDispatchException+0x410
fffff880`02ffaf00 fffff800`02abbd82 : fffff880`02ffb6c8 00fef880`06209000 fffff880`02ffb770 00000000`00001000 : nt!KiDispatchException+0x16f
fffff880`02ffb590 fffff800`02aba68a : 00000014`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`02ffb770 fffff800`02a1fe8d : fffff800`02a05e15 fffff880`06206000 00000000`00000002 fffffa80`0444f940 : nt!KiGeneralProtectionFault+0x10a
fffff880`02ffb908 fffff800`02a05e15 : fffff880`06206000 00000000`00000002 fffffa80`0444f940 00000000`00001000 : hal!memcpy+0xbd
fffff880`02ffb910 fffff800`02a0569a : fffffa80`04575810 00000000`00001000 fffffa80`046f0f80 00000000`00004000 : hal!HalpDmaSyncMapBuffers+0x1bd
fffff880`02ffb9c0 fffff800`02a0883f : fffffa80`04575810 00ff0000`00000000 fffffa80`046f0f80 00000000`00007000 : hal!HalpDmaFlushScatterTransfer+0xae
fffff880`02ffba10 fffff800`02a077d5 : fffffa80`06a59640 00ff0000`00000000 00000000`00007000 fffffa80`0444f940 : hal!IoFlushAdapterBuffers+0xaf
fffff880`02ffba50 fffff880`00fc4199 : fffffa80`06a595a0 fffffa80`046eb1b0 fffffa80`06a595a0 fffffa80`044a4b40 : hal!HalPutScatterGatherList+0x85
fffff880`02ffbab0 fffff880`00e0c43b : 00000000`00000000 00000000`00000001 fffff800`02ab8123 00000000`00000009 : PCIIDEX!BmFlush+0x25
fffff880`02ffbae0 fffff880`00e0c0ec : fffffa80`0430c1a0 00000000`00000000 fffffa80`0430c1a0 fffffa80`06a595a0 : ataport!IdeProcessCompletedRequests+0x123
fffff880`02ffbc10 fffff800`02ac7bfc : fffff880`02fd3180 0000000a`59a62ef4 fffffa80`0430c050 fffffa80`0430c118 : ataport!IdePortCompletionDpc+0x1a8
fffff880`02ffbcd0 fffff800`02ac4eea : fffff880`02fd3180 fffff880`02fddfc0 00000000`00000000 fffff880`00e0bf44 : nt!KiRetireDpcList+0x1bc
fffff880`02ffbd80 00000000`00000000 : fffff880`02ffc000 fffff880`02ff6000 fffff880`02ffbd40 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
PCIIDEX!BmFlush+25
fffff880`00fc4199 4883a3e003000000 and qword ptr [rbx+3E0h],0
SYMBOL_STACK_INDEX: c
SYMBOL_NAME: PCIIDEX!BmFlush+25
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: PCIIDEX
IMAGE_NAME: PCIIDEX.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc114
FAILURE_BUCKET_ID: X64_0x1E_PCIIDEX!BmFlush+25
BUCKET_ID: X64_0x1E_PCIIDEX!BmFlush+25
Followup: MachineOwner
---------
Debug session time: Thu Nov 25 21:02:16.673 2010 (GMT-5)
System Uptime: 0 days 0:01:40.593
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck FE, {5, fffffa8004fa81a0, 10de077c, fffffa800508cc50}
Probably caused by : usbehci.sys ( usbehci!EHCI_sMode_PollEndpointSlot+67 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 0000000000000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
using a physical memory address that was not allocated by
the USBport driver.
Arg2: fffffa8004fa81a0, Device extension pointer of the host controller
Arg3: 0000000010de077c, PCI Vendor,Product id for the controller
Arg4: fffffa800508cc50, Pointer to Endpoint data structure
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xFE
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff88003e2fe4e to fffff80002a8f740
STACK_TEXT:
fffff880`02dfca18 fffff880`03e2fe4e : 00000000`000000fe 00000000`00000005 fffffa80`04fa81a0 00000000`10de077c : nt!KeBugCheckEx
fffff880`02dfca20 fffff880`03e5dfdf : 00000000`ce00b180 fffffa80`04fa96a0 fffffa80`0508cee0 00000000`00000000 : USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x18a
fffff880`02dfca60 fffff880`03e5dba4 : fffff880`031d2080 fffffa80`053b56a0 fffffa80`0508cee0 fffff880`02dfcb01 : usbehci!EHCI_sMode_PollEndpointSlot+0x67
fffff880`02dfcaf0 fffff880`03e62a71 : fffffa80`0508cc50 fffffa80`04fa81a0 00000000`00000000 00000000`00000000 : usbehci!EHCI_PollPerAsyEndpoint+0x84
fffff880`02dfcb70 fffff880`03e03e8b : 00000000`00000002 fffffa80`04fa81a0 00000000`00000000 00000000`00000000 : usbehci!EHCI_PollEndpoint+0x41
fffff880`02dfcbb0 fffff880`03e089b1 : 00000000`00000000 00000000`00000004 fffffa80`0508ca10 fffffa80`04fa8050 : USBPORT!MPf_PollEndpoint+0x9b
fffff880`02dfcbe0 fffff880`03e14043 : fffffa80`04fa81a0 00000000`00000000 fffffa80`0000000e 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x7c1
fffff880`02dfcc40 fffff880`03e04f89 : fffffa80`04fa8050 00000000`00000000 fffffa80`04fa8a02 fffffa80`04fa8a10 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x1af
fffff880`02dfcca0 fffff800`02a9abfc : fffff880`02dd4180 fffffa80`04fa8a10 fffffa80`04fa8a28 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`02dfccd0 fffff800`02a97eea : fffff880`02dd4180 fffff880`02ddefc0 00000000`00000000 fffff880`03e04db0 : nt!KiRetireDpcList+0x1bc
fffff880`02dfcd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
usbehci!EHCI_sMode_PollEndpointSlot+67
fffff880`03e5dfdf 4533c9 xor r9d,r9d
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: usbehci!EHCI_sMode_PollEndpointSlot+67
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: usbehci
IMAGE_NAME: usbehci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc06
FAILURE_BUCKET_ID: X64_0xFE_usbehci!EHCI_sMode_PollEndpointSlot+67
BUCKET_ID: X64_0xFE_usbehci!EHCI_sMode_PollEndpointSlot+67
Followup: MachineOwner
---------
Debug session time: Thu Nov 25 16:22:56.543 2010 (GMT-5)
System Uptime: 0 days 0:19:07.400
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck DA, {504, fffff6fc400299b8, 1, 5337}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+b43b )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_PTE_MISUSE (da)
The stack trace identifies the guilty driver.
Arguments:
Arg1: 0000000000000504, Type of error.
Arg2: fffff6fc400299b8
Arg3: 0000000000000001
Arg4: 0000000000005337
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xDA
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80002b2de11 to fffff80002ad5740
STACK_TEXT:
fffff880`031169d8 fffff800`02b2de11 : 00000000`000000da 00000000`00000504 fffff6fc`400299b8 00000000`00000001 : nt!KeBugCheckEx
fffff880`031169e0 fffff800`02ae55e4 : 00000000`00000000 fffff800`02c8a720 00000000`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0xb43b
fffff880`03116af0 fffff800`02ae8df5 : fffffa80`03973b30 00000000`00000008 00005349`000c6680 00000000`00000001 : nt!MiEmptyPteBins+0x10d
fffff880`03116b40 fffff800`02ae9eb4 : 00000000`00000008 00000000`00000001 fffffa80`03973b30 fffff800`02ae90cb : nt!MiAdjustPteBins+0x29
fffff880`03116b80 fffff800`02aea173 : 00000000`00000008 fffff880`03116c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x40
fffff880`03116bd0 fffff800`02d79c06 : fffffa80`03a09ae0 00000000`00000080 fffffa80`03973b30 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`03116d40 fffff800`02ab3c26 : fffff880`02d63180 fffffa80`03a09ae0 fffff880`02d6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03116d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+b43b
fffff800`02b2de11 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+b43b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
FAILURE_BUCKET_ID: X64_0xDA_nt!_??_::FNODOBFM::_string_+b43b
BUCKET_ID: X64_0xDA_nt!_??_::FNODOBFM::_string_+b43b
Followup: MachineOwner
---------
Debug session time: Thu Nov 25 17:23:48.019 2010 (GMT-5)
System Uptime: 0 days 0:50:14.502
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
.....
Unable 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
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff88004b8f319, fffff8800391eec8, fffff8800391e730}
Probably caused by : nvlddmkm.sys ( nvlddmkm+38d319 )
Followup: MachineOwner
---------
3: 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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88004b8f319, The address that the exception occurred at
Arg3: fffff8800391eec8, Exception Record Address
Arg4: fffff8800391e730, 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:
nvlddmkm+38d319
fffff880`04b8f319 4439410c cmp dword ptr [rcx+0Ch],r8d
EXCEPTION_RECORD: fffff8800391eec8 -- (.exr 0xfffff8800391eec8)
ExceptionAddress: fffff88004b8f319 (nvlddmkm+0x000000000038d319)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff8800391e730 -- (.cxr 0xfffff8800391e730)
rax=fffffa800442c8f0 rbx=fffffa8005af9610 rcx=ff00fa8004049d20
rdx=0000000000000000 rsi=fffffa8005acc000 rdi=0000000000000001
rip=fffff88004b8f319 rsp=fffff8800391f108 rbp=fffffa8005ada840
r8=00000000ff00e052 r9=00000000c1d00780 r10=fffff8800391f170
r11=fffff8800391f0e0 r12=0000000000000006 r13=0000000000000000
r14=0000000000000001 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
nvlddmkm+0x38d319:
fffff880`04b8f319 4439410c cmp dword ptr [rcx+0Ch],r8d ds:002b:ff00fa80`04049d2c=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
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: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc30e0
ffffffffffffffff
FOLLOWUP_IP:
nvlddmkm+38d319
fffff880`04b8f319 4439410c cmp dword ptr [rcx+0Ch],r8d
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff88004bf123b to fffff88004b8f319
STACK_TEXT:
fffff880`0391f108 fffff880`04bf123b : fffffa80`05af9610 fffffa80`05ada840 fffffa80`05acc000 fffffa80`05acc000 : nvlddmkm+0x38d319
fffff880`0391f110 fffffa80`05af9610 : fffffa80`05ada840 fffffa80`05acc000 fffffa80`05acc000 fffff880`0391f170 : nvlddmkm+0x3ef23b
fffff880`0391f118 fffffa80`05ada840 : fffffa80`05acc000 fffffa80`05acc000 fffff880`0391f170 fffff880`04a155a5 : 0xfffffa80`05af9610
fffff880`0391f120 fffffa80`05acc000 : fffffa80`05acc000 fffff880`0391f170 fffff880`04a155a5 00000000`00000000 : 0xfffffa80`05ada840
fffff880`0391f128 fffffa80`05acc000 : fffff880`0391f170 fffff880`04a155a5 00000000`00000000 00000000`00000001 : 0xfffffa80`05acc000
fffff880`0391f130 fffff880`0391f170 : fffff880`04a155a5 00000000`00000000 00000000`00000001 00000000`00000006 : 0xfffffa80`05acc000
fffff880`0391f138 fffff880`04a155a5 : 00000000`00000000 00000000`00000001 00000000`00000006 00000000`00000001 : 0xfffff880`0391f170
fffff880`0391f140 00000000`00000000 : 00000000`00000001 00000000`00000006 00000000`00000001 fffffa80`05acc000 : nvlddmkm+0x2135a5
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nvlddmkm+38d319
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4cb9dd0e
STACK_COMMAND: .cxr 0xfffff8800391e730 ; kb
FAILURE_BUCKET_ID: X64_0x7E_nvlddmkm+38d319
BUCKET_ID: X64_0x7E_nvlddmkm+38d319
Followup: MachineOwner
---------