Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\032811-16781-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02c59000 PsLoadedModuleList = 0xfffff800`02e96e50
Debug session time: Mon Mar 28 08:06:32.390 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:17.578
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
...............................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff80002fba6ae, fffff880031bda48, fffff880031bd2b0}
Probably caused by : ntkrnlmp.exe ( nt!CmpDelayDerefKCBWorker+d6 )
Followup: MachineOwner
---------
2: 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: fffff80002fba6ae, The address that the exception occurred at
Arg3: fffff880031bda48, Exception Record Address
Arg4: fffff880031bd2b0, 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!CmpDelayDerefKCBWorker+d6
fffff800`02fba6ae 4038ae380b0000 cmp byte ptr [rsi+0B38h],bpl
EXCEPTION_RECORD: fffff880031bda48 -- (.exr 0xfffff880031bda48)
ExceptionAddress: fffff80002fba6ae (nt!CmpDelayDerefKCBWorker+0x00000000000000d6)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000b38
Attempt to read from address 0000000000000b38
CONTEXT: fffff880031bd2b0 -- (.cxr 0xfffff880031bd2b0)
rax=fffffa8003aa5bb0 rbx=0000000000000000 rcx=fffff8a00321bd98
rdx=00000000000003bd rsi=0000000000000000 rdi=fffff8a00321bcc0
rip=fffff80002fba6ae rsp=fffff880031bdc80 rbp=0000000000000001
r8=fffff8a000dccde8 r9=000000001b748b3f r10=fffff8a000a044a8
r11=fffffa8003aa5b60 r12=fffff80002eceee0 r13=fffff80002ecef40
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
nt!CmpDelayDerefKCBWorker+0xd6:
fffff800`02fba6ae 4038ae380b0000 cmp byte ptr [rsi+0B38h],bpl ds:002b:00000000`00000b38=??
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: 0000000000000b38
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f010e0
0000000000000b38
FOLLOWUP_IP:
nt!CmpDelayDerefKCBWorker+d6
fffff800`02fba6ae 4038ae380b0000 cmp byte ptr [rsi+0B38h],bpl
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff80002cd6961 to fffff80002fba6ae
STACK_TEXT:
fffff880`031bdc80 fffff800`02cd6961 : fffff800`02fba5d8 fffff800`02e6e5f8 fffffa80`03aa5b60 00000000`00000000 : nt!CmpDelayDerefKCBWorker+0xd6
fffff880`031bdcb0 fffff800`02f6c7c6 : 00000000`00000000 fffffa80`03aa5b60 00000000`00000080 fffffa80`03a2b9e0 : nt!ExpWorkerThread+0x111
fffff880`031bdd40 fffff800`02ca7c26 : fffff880`02f64180 fffffa80`03aa5b60 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031bdd80 00000000`00000000 : fffff880`031be000 fffff880`031b8000 fffff880`031bd9f0 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!CmpDelayDerefKCBWorker+d6
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4cc791bd
STACK_COMMAND: .cxr 0xfffff880031bd2b0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_nt!CmpDelayDerefKCBWorker+d6
BUCKET_ID: X64_0x7E_nt!CmpDelayDerefKCBWorker+d6
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\032711-29625-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02c04000 PsLoadedModuleList = 0xfffff800`02e41e50
Debug session time: Sun Mar 27 10:27:03.718 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:16.906
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
.................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff80003003c31, fffff88002faf7d8, fffff88002faf040}
Probably caused by : ntkrnlmp.exe ( nt!WmipFindISinGEbyName+c1 )
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: fffff80003003c31, The address that the exception occurred at
Arg3: fffff88002faf7d8, Exception Record Address
Arg4: fffff88002faf040, 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!WmipFindISinGEbyName+c1
fffff800`03003c31 460fb70409 movzx r8d,word ptr [rcx+r9]
EXCEPTION_RECORD: fffff88002faf7d8 -- (.exr 0xfffff88002faf7d8)
ExceptionAddress: fffff80003003c31 (nt!WmipFindISinGEbyName+0x00000000000000c1)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff88002faf040 -- (.cxr 0xfffff88002faf040)
rax=0000000000000000 rbx=fffff8a00016f068 rcx=fffff8a0018bbcf8
rdx=fffff8a000108442 rsi=0000000000000000 rdi=0000000000000044
rip=fffff80003003c31 rsp=fffff88002fafa10 rbp=fffff8a00019c340
r8=0000000000000052 r9=0053075ff7144318 r10=0000000000000000
r11=fffff88002dd5180 r12=fffff88002fafa70 r13=fffff8a0018bbcf8
r14=0000000000000001 r15=000000000000005a
iopl=0 nv up ei pl nz ac po cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010217
nt!WmipFindISinGEbyName+0xc1:
fffff800`03003c31 460fb70409 movzx r8d,word ptr [rcx+r9] ds:002b:0052ffff`f8a00010=????
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 fffff80002eac0e0
ffffffffffffffff
FOLLOWUP_IP:
nt!WmipFindISinGEbyName+c1
fffff800`03003c31 460fb70409 movzx r8d,word ptr [rcx+r9]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff80003014f1f to fffff80003003c31
STACK_TEXT:
fffff880`02fafa10 fffff800`03014f1f : fffff8a0`018b005a fffff8a0`018bbcf8 00000000`00000000 fffff800`02d07b1b : nt!WmipFindISinGEbyName+0xc1
fffff880`02fafa50 fffff800`03085649 : fffff8a0`018bbcf8 fffffa80`05f05208 fffff8a0`018bbcf0 00000000`000007ff : nt!WmipMangleInstanceName+0x7f
fffff880`02fafab0 fffff800`0309f211 : 00000000`00000050 00000000`00000028 fffffa80`000000fc fffffa80`05f0527c : nt!WmipBuildInstanceSet+0x239
fffff880`02fafb30 fffff800`0309f496 : fffff8a0`0016d208 00000000`000000fc 00000000`000000fc 00000000`00000000 : nt!WmipAddDataSource+0xd1
fffff880`02fafbc0 fffff800`0309ff41 : 00000000`00000000 00000000`00000000 00000000`00002000 00000000`000002cc : nt!WmipProcessWmiRegInfo+0x96
fffff880`02fafc20 fffff800`030cc7ec : fffffa80`04f7d8a0 fffff800`02e195f8 fffffa80`03aa7680 fffff8a0`01886500 : nt!WmipRegisterOrUpdateDS+0x101
fffff880`02fafc80 fffff800`02c81961 : fffff800`030cc790 fffff800`02f6e920 fffffa80`03aa7680 00000000`00000000 : nt!WmipRegistrationWorker+0x5c
fffff880`02fafcb0 fffff800`02f177c6 : 00000000`00000000 fffffa80`03aa7680 00000000`00000080 fffffa80`03a2b9e0 : nt!ExpWorkerThread+0x111
fffff880`02fafd40 fffff800`02c52c26 : fffff880`02d64180 fffffa80`03aa7680 fffff880`02d6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02fafd80 00000000`00000000 : fffff880`02fb0000 fffff880`02faa000 fffff880`02faf830 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!WmipFindISinGEbyName+c1
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4cc791bd
STACK_COMMAND: .cxr 0xfffff88002faf040 ; kb
FAILURE_BUCKET_ID: X64_0x7E_nt!WmipFindISinGEbyName+c1
BUCKET_ID: X64_0x7E_nt!WmipFindISinGEbyName+c1
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\033011-26687-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02c66000 PsLoadedModuleList = 0xfffff800`02ea3e50
Debug session time: Wed Mar 30 04:35:44.218 2011 (UTC - 4:00)
System Uptime: 0 days 0:01:18.406
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41790, fffffa8001669dd0, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33906 )
Followup: MachineOwner
---------
3: kd>
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa8001669dd0
Arg3: 000000000000ffff
Arg4: 0000000000000000
Debugging Details:
------------------
BUGCHECK_STR: 0x1a_41790
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: avgtray.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002d49f9e to fffff80002cd6740
STACK_TEXT:
fffff880`074b0648 fffff800`02d49f9e : 00000000`0000001a 00000000`00041790 fffffa80`01669dd0 00000000`0000ffff : nt!KeBugCheckEx
fffff880`074b0650 fffff800`02d180da : 00000000`00000000 00000000`030effff fffffa80`00000000 fffffa80`04fa7b30 : nt! ?? ::FNODOBFM::`string'+0x33906
fffff880`074b0810 fffff800`02cd5993 : ffffffff`ffffffff fffff880`074b0ad0 fffff880`074b0ad8 fffffa80`00008000 : nt!NtFreeVirtualMemory+0x5ca
fffff880`074b0900 fffff800`02cd1f30 : fffff800`02f65fe7 fffffa80`04fa7b30 fffffa80`06366920 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
fffff880`074b0a98 fffff800`02f65fe7 : fffffa80`04fa7b30 fffffa80`06366920 00000000`00000000 00000000`00000000 : nt!KiServiceLinkage
fffff880`074b0aa0 fffff800`02fb9953 : 00000000`02ff0000 00000000`00000000 00000000`00000000 fffffa80`04a2ae60 : nt!RtlFreeUserStack+0x27
fffff880`074b0ad0 fffff800`02fbd41d : fffff880`00000000 00000000`02fee800 00000000`7efd5000 00000000`00000000 : nt!PspExitThread+0x7c3
fffff880`074b0b90 fffff800`02fbd659 : fffffa80`06366920 00000000`00000000 fffffa80`06366920 00000000`7efd5000 : nt!PspTerminateThreadByPointer+0x4d
fffff880`074b0be0 fffff800`02cd5993 : fffffa80`06366920 fffff880`074b0ca0 00000000`7efd5000 fffffa80`0636db80 : nt!NtTerminateThread+0x45
fffff880`074b0c20 00000000`7791fbea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`02fee808 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7791fbea
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+33906
fffff800`02d49f9e cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+33906
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4cc791bd
FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33906
BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33906
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\033111-25593-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02e19000 PsLoadedModuleList = 0xfffff800`03056e50
Debug session time: Thu Mar 31 07:46:24.062 2011 (UTC - 4:00)
System Uptime: 0 days 0:01:08.296
Loading Kernel Symbols
...............................................................
................................................................
...
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41790, fffffa80013b7cb0, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33906 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa80013b7cb0
Arg3: 000000000000ffff
Arg4: 0000000000000000
Debugging Details:
------------------
BUGCHECK_STR: 0x1a_41790
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: smss.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002efcf9e to fffff80002e89740
STACK_TEXT:
fffff880`04bc28c8 fffff800`02efcf9e : 00000000`0000001a 00000000`00041790 fffffa80`013b7cb0 00000000`0000ffff : nt!KeBugCheckEx
fffff880`04bc28d0 fffff800`02e5cc13 : ffffffff`00000000 00000000`0028ffff fffffa80`00000000 fffffa80`03afa060 : nt! ?? ::FNODOBFM::`string'+0x33906
fffff880`04bc2a90 fffff800`0316cabf : fffff8a0`03746060 00000000`00000001 00000000`00000000 fffffa80`03afa060 : nt!MmCleanProcessAddressSpace+0x62f
fffff880`04bc2ae0 fffff800`0314595b : 00000000`00000000 00000000`00000001 000007ff`fffdd000 00000000`00000000 : nt!PspExitThread+0x92f
fffff880`04bc2ba0 fffff800`02e88993 : fffffa80`054ba360 00000000`00000000 fffffa80`03afa001 fffffa80`03afa060 : nt!NtTerminateProcess+0x25b
fffff880`04bc2c20 00000000`77bcf97a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0028fe78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77bcf97a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+33906
fffff800`02efcf9e cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+33906
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4cc791bd
FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33906
BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33906
Followup: MachineOwner
---------