10/25/2019


Microsoft (R) Windows Debugger Version 10.0.19494.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\102519-8265-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff802`28800000 PsLoadedModuleList = 0xfffff802`28c48210
Debug session time: Fri Oct 25 16:01:25.274 2019 (UTC - 6:00)
System Uptime: 0 days 0:21:38.020
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
.........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`289c1220 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff802`2d42a300=000000000000001e
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8023f2a46ab, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffa90b6c962bd8, Parameter 1 of the exception

Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 3

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-1CBU1CD

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 3

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 77

    Key  : Analysis.System
    Value: CreateObject


DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8023f2a46ab

BUGCHECK_P3: 0

BUGCHECK_P4: ffffa90b6c962bd8

READ_ADDRESS: fffff80228d733b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff80228c2a3c8: Unable to get Flags value from nt!KdVersionBlock
fffff80228c2a3c8: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
 ffffa90b6c962bd8

EXCEPTION_PARAMETER2:  ffffa90b6c962bd8

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
fffff802`2d42a2f8 fffff802`28aa678e : 00000000`0000001e ffffffff`c0000005 fffff802`3f2a46ab 00000000`00000000 : nt!KeBugCheckEx
fffff802`2d42a300 fffff802`289ca04f : fffff802`28d11000 fffff802`28800000 0005e56c`00ab6000 00000000`0010001f : nt!KiFatalExceptionHandler+0x22
fffff802`2d42a340 fffff802`288c3375 : 00000000`00000000 00000000`00000000 fffff802`2d42a8b0 00007fff`ffff0000 : nt!RtlpExecuteHandlerForException+0xf
fffff802`2d42a370 fffff802`288c790e : fffff802`2d42b2a8 fffff802`2d42aff0 fffff802`2d42b2a8 ffffa90b`bb86e031 : nt!RtlDispatchException+0x4a5
fffff802`2d42aac0 fffff802`289d321d : 00000000`00000003 00000000`00000001 00000000`00000000 fffff802`2d42b270 : nt!KiDispatchException+0x16e
fffff802`2d42b170 fffff802`289cf405 : fffff802`2d42b2e8 00000000`00000008 fffff802`2d42b2f0 00000000`00000008 : nt!KiExceptionDispatch+0x11d
fffff802`2d42b350 fffff802`3f2a46ab : 00000000`00000000 fffff802`2d42b560 00000000`00000000 ffffa90b`c376f020 : nt!KiPageFault+0x445
fffff802`2d42b4e0 fffff802`422ae314 : ffffa90b`bb86e030 00000000`00000000 ffffa90b`bb86e030 ffffa90b`bb902000 : dxgkrnl!DxgNotifyDpcCB+0x2b
fffff802`2d42b590 ffffa90b`bb86e030 : 00000000`00000000 ffffa90b`bb86e030 ffffa90b`bb902000 fffff802`422ae2a7 : nvlddmkm+0x12e314
fffff802`2d42b598 00000000`00000000 : ffffa90b`bb86e030 ffffa90b`bb902000 fffff802`422ae2a7 ffffa90b`bb902000 : 0xffffa90b`bb86e030


CHKIMG_EXTENSION: !chkimg -lo 50 -db !dxgkrnl
8 errors : !dxgkrnl (fffff8023f2a46a4-fffff8023f2a4dbc)
fffff8023f2a46a0  c0  95  01  00 *aa  8b  4f  40  45  33  f6  33 *a6  f0  44  0f ......O@E3.3..D.
fffff8023f2a46b0  b1  b1  58  0f *25  00  a8  01  74  58  48  8b *87  40  48  85 ..X.%...tXH..@H.
...
fffff8023f2a4da0  85  f6  74  e3 *66  79  58  03  48  8d  05  e9 *a4  05  00  48 ..t.fyX.H......H
fffff8023f2a4db0  89  01  74  78 *1e  83  79  60  00  0f  85  97 *d0  01  00  48 ..tx..y`.......H

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

MEMORY_CORRUPTOR:  STRIDE

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_STRIDE

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {574dbc1b-92cb-fb09-cb7a-cacc1bb2c511}

Followup:     memory_corruption
---------