Kod: Zaznacz cały
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [E:\Mini110310-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18267.x86fre.vistasp2_gdr.100608-0458
Machine Name:
Kernel base = 0x81e02000 PsLoadedModuleList = 0x81f19c70
Debug session time: Wed Nov 3 20:27:28.644 2010 (GMT+1)
System Uptime: 0 days 7:06:21.757
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 81ea9119, 956e4984, 0}
Probably caused by : fltmgr.sys ( fltmgr!FltpCompleteRequest+2d )
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: 81ea9119, The address that the exception occurred at
Arg3: 956e4984, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
FAULTING_IP:
nt!IopfCompleteRequest+3d
81ea9119 803f16 cmp byte ptr [edi],16h
TRAP_FRAME: 956e4984 -- (.trap 0xffffffff956e4984)
ErrCode = 00000000
eax=c000000a ebx=00000000 ecx=b5add60a edx=0000000b esi=b5add6f8 edi=00000000
eip=81ea9119 esp=956e49f8 ebp=956e4a1c iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!IopfCompleteRequest+0x3d:
81ea9119 803f16 cmp byte ptr [edi],16h ds:0023:00000000=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: hpqtra08.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 8077a4d7 to 81ea9119
STACK_TEXT:
956e4a1c 8077a4d7 956e4a3c 8077a524 b5add6f8 nt!IopfCompleteRequest+0x3d
956e4a24 8077a524 b5add6f8 00000000 00000000 fltmgr!FltpCompleteRequest+0x2d
956e4a3c 8077ac84 adef97c8 b5add6f8 00000000 fltmgr!FltpSynchronizeIoCleanup+0x44
956e4a64 8078d643 956e4a84 00000000 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x32e
956e4ab0 81e469c6 84c23020 85988008 b7621e94 fltmgr!FltpCreate+0x2a1
956e4ac8 820411d7 b0521407 b72e62a4 84cc3368 nt!IofCallDriver+0x63
956e4b98 8202f60c 84cc3380 00000000 b72e6200 nt!IopParseDevice+0xf61
956e4c28 8203cba4 00000000 956e4c80 00000040 nt!ObpLookupObjectName+0x5a8
956e4c88 820422de 0012eff4 00000000 8203c401 nt!ObOpenObjectByName+0x13c
956e4cfc 82008077 0036bfc4 80100000 0012eff4 nt!IopCreateFile+0x63b
956e4d44 81e4cc7a 0036bfc4 80100000 0012eff4 nt!NtOpenFile+0x2a
956e4d44 774d5e74 0036bfc4 80100000 0012eff4 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012f038 00000000 00000000 00000000 00000000 0x774d5e74
STACK_COMMAND: kb
FOLLOWUP_IP:
fltmgr!FltpCompleteRequest+2d
8077a4d7 5d pop ebp
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: fltmgr!FltpCompleteRequest+2d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: fltmgr
IMAGE_NAME: fltmgr.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 49e01907
FAILURE_BUCKET_ID: 0x8E_fltmgr!FltpCompleteRequest+2d
BUCKET_ID: 0x8E_fltmgr!FltpCompleteRequest+2d
Followup: MachineOwner