Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\031811-45848-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 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0x82650000 PsLoadedModuleList = 0x8279a850
Debug session time: Fri Mar 18 04:36:16.114 2011 (UTC - 4:00)
System Uptime: 0 days 0:06:52.408
Loading Kernel Symbols
...............................................................
................................................................
......
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 8287a682, 87b178f0, 0}
Probably caused by : ntkrpamp.exe ( nt!ObpWaitForMultipleObjects+14e )
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: 8287a682, The address that the exception occurred at
Arg3: 87b178f0, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
OVERLAPPED_MODULE: Address regions for 'igdkmd32' and 'igdkmd32.sys' overlap
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!ObpWaitForMultipleObjects+14e
8287a682 8b4110 mov eax,dword ptr [ecx+10h]
TRAP_FRAME: 87b178f0 -- (.trap 0xffffffff87b178f0)
ErrCode = 00000000
eax=00000000 ebx=855d8798 ecx=00000000 edx=84708808 esi=84708808 edi=a73dc180
eip=8287a682 esp=87b17964 ebp=87b17bc8 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!ObpWaitForMultipleObjects+0x14e:
8287a682 8b4110 mov eax,dword ptr [ecx+10h] ds:0023:00000010=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 8287a503 to 8287a682
STACK_TEXT:
87b17bc8 8287a503 00000040 87b17c90 00000001 nt!ObpWaitForMultipleObjects+0x14e
87b17d18 8268e1ea 00000040 001741c0 00000001 nt!NtWaitForMultipleObjects+0xcd
87b17d18 779570b4 00000040 001741c0 00000001 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
006afab0 00000000 00000000 00000000 00000000 0x779570b4
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ObpWaitForMultipleObjects+14e
8287a682 8b4110 mov eax,dword ptr [ecx+10h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!ObpWaitForMultipleObjects+14e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce78a09
FAILURE_BUCKET_ID: 0x8E_nt!ObpWaitForMultipleObjects+14e
BUCKET_ID: 0x8E_nt!ObpWaitForMultipleObjects+14e
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\032011-19094-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 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0x8284d000 PsLoadedModuleList = 0x82997850
Debug session time: Sun Mar 20 06:34:21.780 2011 (UTC - 4:00)
System Uptime: 0 days 0:38:56.886
Loading Kernel Symbols
...............................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 82a9310f, 93a7fc2c, 0}
GetPointerFromAddress: unable to read from 829b7718
Unable to read MiSystemVaType memory at 829971a0
GetPointerFromAddress: unable to read from 829b7718
Unable to read MiSystemVaType memory at 829971a0
GetPointerFromAddress: unable to read from 829b7718
Unable to read MiSystemVaType memory at 829971a0
Probably caused by : ntkrpamp.exe ( nt!ObpCloseHandleTableEntry+28 )
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: 82a9310f, The address that the exception occurred at
Arg3: 93a7fc2c, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
GetPointerFromAddress: unable to read from 829b7718
Unable to read MiSystemVaType memory at 829971a0
GetPointerFromAddress: unable to read from 829b7718
Unable to read MiSystemVaType memory at 829971a0
GetPointerFromAddress: unable to read from 829b7718
Unable to read MiSystemVaType memory at 829971a0
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!ObpCloseHandleTableEntry+28
82a9310f 837b7400 cmp dword ptr [ebx+74h],0
TRAP_FRAME: 93a7fc2c -- (.trap 0xffffffff93a7fc2c)
ErrCode = 00000000
eax=93865b40 ebx=00000000 ecx=00000000 edx=85d34b28 esi=85d34b28 edi=85dd5d48
eip=82a9310f esp=93a7fca0 ebp=93a7fcdc iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
nt!ObpCloseHandleTableEntry+0x28:
82a9310f 837b7400 cmp dword ptr [ebx+74h],0 ds:0023:00000074=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: sidebar.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82a9302e to 82a9310f
STACK_TEXT:
93a7fcdc 82a9302e 9227b170 93865b40 85dd7728 nt!ObpCloseHandleTableEntry+0x28
93a7fd0c 82a933c8 85dd7728 85dd5d01 021df340 nt!ObpCloseHandle+0x7f
93a7fd28 8288b1ea 000005a0 021df340 77b470b4 nt!NtClose+0x4e
93a7fd28 77b470b4 000005a0 021df340 77b470b4 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
021df340 00000000 00000000 00000000 00000000 0x77b470b4
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ObpCloseHandleTableEntry+28
82a9310f 837b7400 cmp dword ptr [ebx+74h],0
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!ObpCloseHandleTableEntry+28
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce78a09
FAILURE_BUCKET_ID: 0x8E_nt!ObpCloseHandleTableEntry+28
BUCKET_ID: 0x8E_nt!ObpCloseHandleTableEntry+28
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\031911-31496-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 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0x82801000 PsLoadedModuleList = 0x8294b850
Debug session time: Fri Mar 18 22:15:19.321 2011 (UTC - 4:00)
System Uptime: 0 days 0:06:06.428
Loading Kernel Symbols
...............................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
....
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 00000003, the pool freelist is corrupt.
Arg2: 915c44e8, the pool entry being checked.
Arg3: 915c44e8, the read back flink freelist value (should be the same as 2).
Arg4: 915c40e8, the read back blink freelist value (should be the same as 2).
Debugging Details:
------------------
BUGCHECK_STR: 0x19_3
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 8292335f to 82923996
STACK_TEXT:
807fea28 8292335f 8411e140 00000000 ffff7fff nt!ExDeferredFreePool+0x336
807fea90 82fe1e69 903e0ca0 6e664d46 807feaac nt!ExFreePoolWithTag+0x8a4
807feaa0 82fe1eb9 903e0ccc 807feac4 82fe2282 fltmgr!FltpFreeFileNameInformation+0x17
807feaac 82fe2282 903e0ccc 84f43008 859dfac8 fltmgr!FltReleaseFileNameInformation+0x2b
807feac4 82fe2311 859dfac8 00008000 ffffffff fltmgr!DeleteNameCacheNodes+0xfe
807feae0 82fe57af 84f43008 859dfac8 859dfb08 fltmgr!FltpFreeNameCacheList+0x17
807feafc 82fe59b4 859dfac8 8976cb30 00000000 fltmgr!CleanupStreamListCtrl+0x37
807feb10 82a811e1 859dfacc 965e9a9e 00000000 fltmgr!DeleteStreamListCtrlCallback+0x5a
807feb50 86cce89c 8976cb30 8976ca40 8976cb30 nt!FsRtlTeardownPerStreamContexts+0x13a
807feb6c 86cbf0b5 00000705 8976ca68 8976ca40 Ntfs!NtfsDeleteScb+0x214
807feb84 86c429e2 842898d8 8976cb30 00000000 Ntfs!NtfsRemoveScb+0xc5
807feba0 86cce2d7 842898d8 8976ca40 00000000 Ntfs!NtfsPrepareFcbForRemoval+0x62
807febe4 86c3e2cb 842898d8 8976cb30 8976ccd8 Ntfs!NtfsTeardownStructures+0x68
807fec0c 86cd2331 842898d8 8976cb30 8976ccd8 Ntfs!NtfsDecrementCloseCounts+0xaf
807fec6c 86cd6414 842898d8 8976cb30 8976ca40 Ntfs!NtfsCommonClose+0x4f2
807fed00 8287eaab 00000000 00000000 841a89e8 Ntfs!NtfsFspClose+0x118
807fed50 82a0af5e 00000000 965e9c5e 00000000 nt!ExpWorkerThread+0x10d
807fed90 828b2219 8287e99e 00000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ExDeferredFreePool+336
82923996 cc int 3
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!ExDeferredFreePool+336
FOLLOWUP_NAME: Pool_corruption
IMAGE_NAME: Pool_Corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: Pool_Corruption
FAILURE_BUCKET_ID: 0x19_3_nt!ExDeferredFreePool+336
BUCKET_ID: 0x19_3_nt!ExDeferredFreePool+336
Followup: Pool_corruption
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\032011-17113-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 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0x8284f000 PsLoadedModuleList = 0x82999850
Debug session time: Sun Mar 20 11:37:27.292 2011 (UTC - 4:00)
System Uptime: 0 days 2:52:58.274
Loading Kernel Symbols
...............................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 82a91360, a87bc8e8, 0}
Probably caused by : ntkrpamp.exe ( nt!CmpGetNameControlBlock+107 )
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: 82a91360, The address that the exception occurred at
Arg3: a87bc8e8, 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:
nt!CmpGetNameControlBlock+107
82a91360 3b01 cmp eax,dword ptr [ecx]
TRAP_FRAME: a87bc8e8 -- (.trap 0xffffffffa87bc8e8)
ErrCode = 00000000
eax=2a5738f7 ebx=a87bc9a0 ecx=74655350 edx=1710291e esi=7465534c edi=87a0f000
eip=82a91360 esp=a87bc95c ebp=a87bc980 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!CmpGetNameControlBlock+0x107:
82a91360 3b01 cmp eax,dword ptr [ecx] ds:0023:74655350=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: firefox.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82ad48ae to 82a91360
STACK_TEXT:
a87bc980 82ad48ae 0000004c 017bc9b7 8e9d38ec nt!CmpGetNameControlBlock+0x107
a87bc9b8 82a7e76c 8d3bc9c8 0025e8e8 925cfd28 nt!CmpCreateKeyControlBlock+0x4e8
a87bcb48 82a75ac5 aaaf8a68 8419f3c0 842e7d20 nt!CmpParseKey+0xa1e
a87bcbc4 82a85ed6 00000810 a87bcc18 00000040 nt!ObpLookupObjectName+0x4fa
a87bcc20 82a83e07 0e24f2a8 8419f3c0 00000001 nt!ObOpenObjectByName+0x165
a87bcd00 82a60af5 0e24f398 00020019 0e24f2a8 nt!CmOpenKey+0x1f4
a87bcd1c 8288d1ea 0e24f398 00020019 0e24f2a8 nt!NtOpenKeyEx+0x18
a87bcd1c 773970b4 0e24f398 00020019 0e24f2a8 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0e24f2e8 00000000 00000000 00000000 00000000 0x773970b4
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!CmpGetNameControlBlock+107
82a91360 3b01 cmp eax,dword ptr [ecx]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!CmpGetNameControlBlock+107
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce78a09
FAILURE_BUCKET_ID: 0x8E_nt!CmpGetNameControlBlock+107
BUCKET_ID: 0x8E_nt!CmpGetNameControlBlock+107
Followup: MachineOwner
---------