Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- Microsoft (R) Windows Debugger Version 10.0.10586.567 AMD64
- Copyright (c) Microsoft Corporation. All rights reserved.
- Loading Dump File [D:\050316-4375-01.dmp]
- Mini Kernel Dump File: Only registers and stack trace are available
- ************* Symbol Path validation summary **************
- Response Time (ms) Location
- Deferred SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
- Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
- Executable search path is:
- Windows 10 Kernel Version 10586 MP (8 procs) Free x64
- Product: WinNt, suite: TerminalServer SingleUserTS
- Built by: 10586.212.amd64fre.th2_release_sec.160328-1908
- Machine Name:
- Kernel base = 0xfffff803`17a15000 PsLoadedModuleList = 0xfffff803`17cf3cd0
- Debug session time: Tue May 3 13:52:18.756 2016 (UTC + 2:00)
- System Uptime: 5 days 3:36:59.431
- Loading Kernel Symbols
- ...............................................................
- ..........WARNING: em042_64 overlaps em008_64
- ......................................................
- ...........................................................
- Loading User Symbols
- Loading unloaded module list
- ..................................................
- *******************************************************************************
- * *
- * Bugcheck Analysis *
- * *
- *******************************************************************************
- Use !analyze -v to get detailed debugging information.
- BugCheck 10E, {17, ffffe00040628000, 0, ffffffffc00002b6}
- Probably caused by : dxgmms2.sys ( dxgmms2!VIDMM_GLOBAL::RestoreFromPurge+15ad2 )
- Followup: MachineOwner
- ---------
- 3: kd> !analyze -v
- *******************************************************************************
- * *
- * Bugcheck Analysis *
- * *
- *******************************************************************************
- VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
- The video memory manager encountered a condition that it can't recover from. By crashing,
- the video memory manager is attempting to get enough information into the minidump such that
- somebody can pinpoint what lead to this condition.
- Arguments:
- Arg1: 0000000000000017, Unexpected system command failure.
- Arg2: ffffe00040628000
- Arg3: 0000000000000000
- Arg4: ffffffffc00002b6
- Debugging Details:
- ------------------
- DUMP_CLASS: 1
- DUMP_QUALIFIER: 400
- BUILD_VERSION_STRING: 10586.212.amd64fre.th2_release_sec.160328-1908
- SYSTEM_MANUFACTURER: ASUS
- SYSTEM_PRODUCT_NAME: All Series
- SYSTEM_SKU: All
- SYSTEM_VERSION: System Version
- BIOS_VENDOR: American Megatrends Inc.
- BIOS_VERSION: 2203
- BIOS_DATE: 02/26/2016
- BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.
- BASEBOARD_PRODUCT: Z97-PRO GAMER
- BASEBOARD_VERSION: Rev X.0x
- DUMP_TYPE: 2
- BUGCHECK_P1: 17
- BUGCHECK_P2: ffffe00040628000
- BUGCHECK_P3: 0
- BUGCHECK_P4: ffffffffc00002b6
- BUGCHECK_STR: 0x10e_17
- CPU_COUNT: 8
- CPU_MHZ: dac
- CPU_VENDOR: GenuineIntel
- CPU_FAMILY: 6
- CPU_MODEL: 3c
- CPU_STEPPING: 3
- CPU_MICROCODE: 6,3c,3,0 (F,M,S,R) SIG: 1E'00000000 (cache) 1E'00000000 (init)
- CUSTOMER_CRASH_COUNT: 1
- DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
- PROCESS_NAME: System
- CURRENT_IRQL: 0
- ANALYSIS_SESSION_HOST: ZORIAN-GAMERIG
- ANALYSIS_SESSION_TIME: 05-06-2016 12:49:39.0550
- ANALYSIS_VERSION: 10.0.10586.567 amd64fre
- LAST_CONTROL_TRANSFER: from fffff801e2383e1d to fffff80317b57760
- STACK_TEXT:
- ffffd000`27773a58 fffff801`e2383e1d : 00000000`0000010e 00000000`00000017 ffffe000`40628000 00000000`00000000 : nt!KeBugCheckEx
- ffffd000`27773a60 fffff801`e39b8952 : ffffe000`40628000 ffffe000`365f0ae8 ffffe000`40628000 ffffe000`365f0ae8 : watchdog!WdLogEvent5_WdCriticalError+0xcd
- ffffd000`27773aa0 fffff801`e24643d8 : ffffe000`40dc0e20 ffffd001`ee146700 ffffe000`34da7010 ffffe000`40628000 : dxgmms2!VIDMM_GLOBAL::RestoreFromPurge+0x15ad2
- ffffd000`27773b20 fffff801`e242e4e0 : 00000000`00000000 ffffe000`45cd03a0 ffffd001`ee1467b0 fffff801`e2481600 : dxgkrnl!ADAPTER_RENDER::RestoreFromPurgeSegments+0x5c
- ffffd000`27773b50 fffff801`e2446632 : ffffe000`352c4270 ffffe000`352c4d08 fffff801`e2481600 00000000`00000000 : dxgkrnl!DXGADAPTER::ReleaseCoreSync+0xa0
- ffffd000`27773b80 fffff801`e2481726 : ffffe000`352c4270 00000000`00000000 c64ae8ce`8b49d300 8b00001e`62e9ff00 : dxgkrnl!DxgkReleaseAdapterCoreSync+0x12
- ffffd000`27773bb0 fffff803`17af8895 : ffffe000`352c4bf8 ffffe000`35a1a5c0 00000000`00000080 fffff801`e2481640 : dxgkrnl!DpiPowerArbiterThread+0xe6
- ffffd000`27773c10 fffff803`17b5c906 : ffffd001`e81c0180 ffffe000`35a1a5c0 fffff803`17af8854 1202b941`fffffc21 : nt!PspSystemThreadStartup+0x41
- ffffd000`27773c60 00000000`00000000 : ffffd000`27774000 ffffd000`2776e000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
- STACK_COMMAND: kb
- THREAD_SHA1_HASH_MOD_FUNC: e9f712e36866c268841e782e87a7bb048dc55b87
- THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 286d63a0ea43f9fab706c81ae8d738157b1deb8a
- THREAD_SHA1_HASH_MOD: 40a384b685f90ab1a143842040ce9f0e9b33ff93
- FOLLOWUP_IP:
- dxgmms2!VIDMM_GLOBAL::RestoreFromPurge+15ad2
- fffff801`e39b8952 90 nop
- FAULT_INSTR_CODE: a598e990
- SYMBOL_STACK_INDEX: 2
- SYMBOL_NAME: dxgmms2!VIDMM_GLOBAL::RestoreFromPurge+15ad2
- FOLLOWUP_NAME: MachineOwner
- MODULE_NAME: dxgmms2
- IMAGE_NAME: dxgmms2.sys
- DEBUG_FLR_IMAGE_TIMESTAMP: 56cd4793
- IMAGE_VERSION: 10.0.10586.162
- BUCKET_ID_FUNC_OFFSET: 15ad2
- FAILURE_BUCKET_ID: 0x10e_17_dxgmms2!VIDMM_GLOBAL::RestoreFromPurge
- BUCKET_ID: 0x10e_17_dxgmms2!VIDMM_GLOBAL::RestoreFromPurge
- PRIMARY_PROBLEM_CLASS: 0x10e_17_dxgmms2!VIDMM_GLOBAL::RestoreFromPurge
- TARGET_TIME: 2016-05-03T11:52:18.000Z
- OSBUILD: 10586
- OSSERVICEPACK: 0
- SERVICEPACK_NUMBER: 0
- OS_REVISION: 0
- SUITE_MASK: 272
- PRODUCT_TYPE: 1
- OSPLATFORM_TYPE: x64
- OSNAME: Windows 10
- OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
- OS_LOCALE:
- USER_LCID: 0
- OSBUILD_TIMESTAMP: 2016-03-29 08:19:02
- BUILDDATESTAMP_STR: 160328-1908
- BUILDLAB_STR: th2_release_sec
- BUILDOSVER_STR: 10.0.10586.212.amd64fre.th2_release_sec.160328-1908
- ANALYSIS_SESSION_ELAPSED_TIME: bade
- ANALYSIS_SOURCE: KM
- FAILURE_ID_HASH_STRING: km:0x10e_17_dxgmms2!vidmm_global::restorefrompurge
- FAILURE_ID_HASH: {080c4a7e-6c7f-a390-e7c9-ccc78d5fe562}
- Followup: MachineOwner
- ---------
Advertisement
Add Comment
Please, Sign In to add comment