Re: 帮忙分析dump file，张老师在就更好了
Windows内核调试
帮忙分析dump file，张老师在就更好了
Will.Wong
2014-10-21, 14:20 下午
是在run 3Dmark ice storm时蓝屏
Microsoft (R) Windows Debugger Version 6.3.9600.17200 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [J:\G70-80\ics_storm_BSOD\MEMORY.DMP]
Kernel Bitmap Dump File: Full address space is available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*c:\websymbol* http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\websymbol* http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17236.amd64fre.winblue_gdr.140714-1919
Machine Name:
Kernel base = 0xfffff801`17a0a000 PsLoadedModuleList = 0xfffff801`17cd4350
Debug session time: Mon Oct 20 20:31:40.393 2014 (UTC + 8:00)
System Uptime: 0 days 10:03:22.291
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
...........................................
Loading unloaded module list
.........................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41287, 0, 0, 0}
*** ERROR: Symbol file could not be found. Defaulted to export symbols for nvwgf2umx.dll -
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::AllocateSmallAllocation+145 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041287, An illegal page fault occurred while holding working set synchronization.
Parameter 2 contains the referenced virtual address.
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
BUGCHECK_STR: 0x1a_41287
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: 3DMarkICFWorkl
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre
TRAP_FRAME: ffffd000b18d8890 -- (.trap 0xffffd000b18d8890)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000fffffffff
rdx=fffff6fb7da00000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80117a6205e rsp=ffffd000b18d8a20 rbp=0000000004c59000
r8=fffff6fb40000130 r9=00000000ffffffff r10=0000000000000011
r11=0000000000000020 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!MiCommitExistingVad+0x5ae:
fffff801`17a6205e 897c2438 mov dword ptr [rsp+38h],edi ss:0018:ffffd000`b18d8a58=00000000
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80117b7e9e7 to fffff80117b5dca0
STACK_TEXT:
ffffd000`b18d8748 fffff801`17b7e9e7 : 00000000`0000001a 00000000`00041287 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffd000`b18d8750 fffff801`17b67f2f : 00000000`00000001 00000000`00000380 00000000`c1d04c00 ffffd000`b18d8890 : nt! ?? ::FNODOBFM::`string'+0x10837
ffffd000`b18d8890 fffff801`17a6205e : 00000000`00000000 00000000`00000000 00000000`00000001 ffffe001`0ddd4468 : nt!KiPageFault+0x12f
ffffd000`b18d8a20 fffff801`17dea5bc : ffffe001`0d955360 00000000`00000001 ffffd000`b18d8e30 00000000`00000404 : nt!MiCommitExistingVad+0x5ae
ffffd000`b18d8b40 fffff801`17b694b3 : ffffd000`0c007082 ffffd000`0c007082 ffffd000`9ddb7000 00000000`00000801 : nt!NtAllocateVirtualMemory+0x46c
ffffd000`b18d8d40 fffff801`17b61900 : fffff800`c8457295 ffffc001`633e9d58 ffffc001`633f8960 ffffc001`633a3600 : nt!KiSystemServiceCopyEnd+0x13
ffffd000`b18d8f48 fffff800`c8457295 : ffffc001`633e9d58 ffffc001`633f8960 ffffc001`633a3600 00000000`00000010 : nt!KiServiceLinkage
ffffd000`b18d8f50 fffff800`c844f118 : ffffd000`9ddb7000 00000000`00020000 00000000`00001000 ffffe001`0efa6900 : dxgmms1!VIDMM_PROCESS_HEAP::AllocateSmallAllocation+0x145
ffffd000`b18d9010 fffff800`c84509e7 : 00000000`00000000 00000000`00020000 00000000`00000001 00000000`000007ff : dxgmms1!VIDMM_PROCESS_HEAP::Allocate+0x90
ffffd000`b18d90b0 fffff800`c8451ca0 : ffffe001`0e994000 ffffc001`629267b0 ffffd000`9ddab320 ffffc001`5cd3c6a0 : dxgmms1!VIDMM_GLOBAL::OpenLocalAllocation+0x147
ffffd000`b18d9150 fffff800`c84501e3 : ffffc001`6aee7e60 ffffc001`6298a520 ffffc001`6298a520 ffffc001`61abd450 : dxgmms1!VIDMM_GLOBAL::OpenOneAllocation+0xc0
ffffd000`b18d9240 fffff800`c88dd713 : ffffc001`632163f0 ffffc001`621456b0 ffffc001`62aa8000 00000000`00000001 : dxgmms1!VIDMM_GLOBAL::OpenAllocation+0xb7
ffffd000`b18d92a0 fffff800`c88dcb9d : ffffc001`00000000 ffffd000`b18d9b10 ffffd000`b18d9860 ffffd000`b18d95b0 : dxgkrnl!DXGDEVICE::CreateVidMmAllocations<_DXGK_ALLOCATIONINFO>+0x2d3
ffffd000`b18d9380 fffff800`c88dc431 : ffffc001`00000799 00000000`00136201 ffffd000`b18d9b70 00000000`00000700 : dxgkrnl!DXGDEVICE::CreateAllocation+0x56d
ffffd000`b18d9a90 fffff801`17b694b3 : ffffe001`112b0480 ffffc001`62aa8000 ffffc001`62aa8000 ffffc001`62aa8000 : dxgkrnl!DxgkCreateAllocation+0x391
ffffd000`b18d9c00 00007ff8`4c9b138a : 00007ff8`4c9c257b 00000000`001362e0 00000000`00136788 00000000`00000001 : nt!KiSystemServiceCopyEnd+0x13
00000000`00136208 00007ff8`4c9c257b : 00000000`001362e0 00000000`00136788 00000000`00000001 00000000`00000000 : GDI32!NtGdiDdDDICreateAllocation+0xa
00000000`00136210 00007ff8`46dec3f6 : 00000000`00136830 00000000`01bb2db8 00000000`01c2db90 00000000`00000000 : GDI32!D3DKMTCreateAllocation+0x5b
00000000`001362c0 00007ff8`20c398c5 : 00000000`00000000 00007ff8`2070a838 00000000`000001d0 00007ff8`4cecb3b2 : d3d11!NDXGI::CDevice::AllocateCB+0xb2
00000000`00136490 00000000`00000000 : 00007ff8`2070a838 00000000`000001d0 00007ff8`4cecb3b2 00000000`00020000 : nvwgf2umx!NVAPI_Thunk+0x11f75
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgmms1!VIDMM_PROCESS_HEAP::AllocateSmallAllocation+145
fffff800`c8457295 448bf8 mov r15d,eax
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: dxgmms1!VIDMM_PROCESS_HEAP::AllocateSmallAllocation+145
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 53183e46
IMAGE_VERSION: 6.3.9600.17041
BUCKET_ID_FUNC_OFFSET: 145
FAILURE_BUCKET_ID: 0x1a_41287_dxgmms1!VIDMM_PROCESS_HEAP::AllocateSmallAllocation
BUCKET_ID: 0x1a_41287_dxgmms1!VIDMM_PROCESS_HEAP::AllocateSmallAllocation
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x1a_41287_dxgmms1!vidmm_process_heap::allocatesmallallocation
FAILURE_ID_HASH: {0dba43bd-ed66-b892-314d-f9c5856ddfde}
Followup: MachineOwner
---------
1: kd> !process
PROCESS ffffe0010efa6900
SessionId: 2 Cid: 1280 Peb: 7ff5ffffc000 ParentCid: 1268
DirBase: 21b489000 ObjectTable: ffffc001622b1940 HandleCount: <Data Not Accessible>
Image: 3DMarkICFWorkload.exe
VadRoot ffffe001117a5780 Vads 119 Clone 0 Private 4786. Modified 6586. Locked 2240.
DeviceMap ffffc0015c12de00
Token ffffc00162aa7060
ElapsedTime 00:00:02.774
UserTime 00:00:00.000
KernelTime 00:00:00.000
QuotaPoolUsage[PagedPool] 295160
QuotaPoolUsage[NonPagedPool] 15472
Working Set Sizes (now,min,max) (8938, 50, 345) (35752KB, 200KB, 1380KB)
PeakWorkingSetSize 10120
VirtualSize 174 Mb
PeakVirtualSize 174 Mb
PageFaultCount 34664
MemoryPriority BACKGROUND
BasePriority 8
CommitCharge 10555
Job ffffe00109056620
THREAD ffffe001112b0480 Cid 1280.09d0 Teb: 00007ff5ffffd000 Win32Thread: fffff90143e0d390 RUNNING on processor 1
THREAD ffffe001098a4080 Cid 1280.0810 Teb: 00007ff5ffffa000 Win32Thread: fffff9014404b010 WAIT: (UserRequest) UserMode Non-Alertable
ffffe001098a06d0 Semaphore Limit 0x7fffffff
THREAD ffffe0011106d480 Cid 1280.061c Teb: 00007ff5ffff8000 Win32Thread: 0000000000000000 WAIT: (UserRequest) UserMode Non-Alertable
ffffe00109500ab0 NotificationEvent
THREAD ffffe0010ff09880 Cid 1280.033c Teb: 00007ff5ffff6000 Win32Thread: fffff90140876b60 WAIT: (UserRequest) UserMode Non-Alertable
ffffe00109500ab0 NotificationEvent
THREAD ffffe00112cdf080 Cid 1280.0494 Teb: 00007ff5ffff4000 Win32Thread: 0000000000000000 WAIT: (UserRequest) UserMode Non-Alertable
ffffe0011289bb90 NotificationEvent
THREAD ffffe001124b3500 Cid 1280.09c8 Teb: 00007ff5ffece000 Win32Thread: 0000000000000000 WAIT: (UserRequest) UserMode Non-Alertable
ffffe0011289bb90 NotificationEvent
THREAD ffffe0011175b880 Cid 1280.00e8 Teb: 00007ff5ffecc000 Win32Thread: fffff90143e4f010 WAIT: (UserRequest) UserMode Non-Alertable
ffffe001129b2210 NotificationEvent
Re: 帮忙分析dump file，张老师在就更好了
格蠹老雷
2014-10-22, 20:33 下午
建议使用verifier开启内核池验证，然后再重现
Re: 帮忙分析dump file，张老师在就更好了
Thomson
2014-10-24, 15:35 下午
能把dump上传上来吗？