Attachment 854272 Details for Bug 1056982 – mem_dump debug info

mem_dump debug info

0x19-debug.txt (text/plain), 4.81 KB, created by CongLi on 2014-01-23 09:53:06 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: CongLi

Created: 2014-01-23 09:53:06 UTC

Size: 4.81 KB

patch

obsolete

>
>Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
>Copyright (c) Microsoft Corporation. All rights reserved.
>
>
>Loading Dump File [C:\Users\Administrator\Desktop\0x19.dmp]
>Kernel Summary Dump File: Only kernel address space is 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 (4 procs) Free x64
>Product: Server, suite: TerminalServer DataCenter SingleUserTS
>Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830
>Machine Name:
>Kernel base = 0xfffff800`01659000 PsLoadedModuleList = 0xfffff800`0181ddd0
>Debug session time: Fri Jan 24 07:02:18.609 2014 (UTC + 8:00)
>System Uptime: 0 days 0:00:37.515
>Loading Kernel Symbols
>...............................................................
>..............................................
>Loading User Symbols
>PEB is paged out (Peb.Ldr = 000007ff`fffdf018).  Type ".hh dbgerr001" for details
>Loading unloaded module list
>....
>*******************************************************************************
>*                                                                             *
>*                        Bugcheck Analysis                                    *
>*                                                                             *
>*******************************************************************************
>
>Use !analyze -v to get detailed debugging information.
>
>BugCheck 19, {20, fffff8800516f960, fffff8800516f980, 5020104}
>
>Page a88f3 not present in the dump file. Type ".hh dbgerr004" for details
>Page a910b not present in the dump file. Type ".hh dbgerr004" for details
>Probably caused by : mountmgr.sys ( mountmgr!QueryPointsFromMemory+130 )
>
>Followup: MachineOwner
>---------
>
>3: 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: 0000000000000020, a pool block header size is corrupt.
>Arg2: fffff8800516f960, The pool entry we were looking for within the page.
>Arg3: fffff8800516f980, The next pool entry.
>Arg4: 0000000005020104, (reserved)
>
>Debugging Details:
>------------------
>
>Page a88f3 not present in the dump file. Type ".hh dbgerr004" for details
>Page a910b not present in the dump file. Type ".hh dbgerr004" for details
>
>BUGCHECK_STR:  0x19_20
>
>POOL_ADDRESS:  fffff8800516f960 Paged pool
>
>DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
>
>PROCESS_NAME:  ServerManagerLa
>
>CURRENT_IRQL:  0
>
>LAST_CONTROL_TRANSFER:  from fffff8000178c46a to fffff800016b3450
>
>STACK_TEXT:  
>fffffa60`04f48708 fffff800`0178c46a : 00000000`00000019 00000000`00000020 fffff880`0516f960 fffff880`0516f980 : nt!KeBugCheckEx
>fffffa60`04f48710 fffffa60`009ebdb8 : fffffa80`04306e30 fffffa60`04f488b0 fffffa80`04306e20 00000000`41746e4d : nt!ExDeferredFreePool+0x9e3
>fffffa60`04f487c0 fffffa60`009ec212 : fffffa80`0527b750 fffffa80`04306e20 00000000`00000000 fffffa60`04f488b0 : mountmgr!QueryPointsFromMemory+0x130
>fffffa60`04f48890 fffffa60`009ef5b0 : fffffa80`051c60e0 fffffa80`04306e20 fffffa80`051c6010 fffffa80`052baa00 : mountmgr!MountMgrQueryPoints+0x242
>fffffa60`04f488e0 fffff800`01915b1e : fffffa80`052baa40 00000000`000000ee fffffa80`051c60e0 00000000`00000001 : mountmgr!MountMgrDeviceControl+0x24c
>fffffa60`04f48a10 fffff800`0191e586 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x5be
>fffffa60`04f48b40 fffff800`016b2ef3 : fffff880`0562e520 00000000`025cee48 00000000`025cee44 fffff800`00000004 : nt!NtDeviceIoControlFile+0x56
>fffffa60`04f48bb0 00000000`77c76d8a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
>00000000`025cee88 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77c76d8a
>
>
>STACK_COMMAND:  kb
>
>FOLLOWUP_IP: 
>mountmgr!QueryPointsFromMemory+130
>fffffa60`009ebdb8 b80d0000c0      mov     eax,0C000000Dh
>
>SYMBOL_STACK_INDEX:  2
>
>SYMBOL_NAME:  mountmgr!QueryPointsFromMemory+130
>
>FOLLOWUP_NAME:  MachineOwner
>
>MODULE_NAME: mountmgr
>
>IMAGE_NAME:  mountmgr.sys
>
>DEBUG_FLR_IMAGE_TIMESTAMP:  47919871
>
>FAILURE_BUCKET_ID:  X64_0x19_20_mountmgr!QueryPointsFromMemory+130
>
>BUCKET_ID:  X64_0x19_20_mountmgr!QueryPointsFromMemory+130
>
>Followup: MachineOwner
>---------
>

Actions: View

Attachments on bug 1056982: 854272 | 861292 | 869957 | 870243 | 870244