Microsoft ® Windows Debugger Version 10.0.20153.1000 AMD64
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\090920-6406-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff8046f000000 PsLoadedModuleList = 0xfffff804
6fc2a310
Debug session time: Wed Sep 9 16:18:09.895 2020 (UTC + 3:00)
System Uptime: 0 days 4:57:09.537
Loading Kernel Symbols
…
…
…
…
Loading User Symbols
Loading unloaded module list
…
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff8046f3f3ea0 48894c2408 mov qword ptr [rsp+8],rcx ss:fffff30d
93d37860=000000000000001a
6: kd> !analyze -v
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000061941, The subtype of the bugcheck.
Arg2: 00000266568f9030
Arg3: 000000000000000d
Arg4: fffff30d93d37a00
Debugging Details:
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2186
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-6N98JSF
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 22084
Key : Analysis.Memory.CommitPeak.Mb
Value: 77
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 1a
BUGCHECK_P1: 61941
BUGCHECK_P2: 266568f9030
BUGCHECK_P3: d
BUGCHECK_P4: fffff30d93d37a00
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: FlightSimulator.exe
STACK_TEXT:
fffff30d93d37858 fffff804
6f472c08 : 000000000000001a 00000000
00061941 00000266568f9030 00000000
0000000d : nt!KeBugCheckEx
fffff30d93d37860 fffff804
6f40205e : 000002630d081c00 00000000
00000000 0000000000000000 ffff950f
00000000 : nt!MmAccessFault+0x184488
fffff30d93d37a00 00007ffd
b28b9474 : 0000000000000000 00000000
00000000 0000000000000000 00000000
00000000 : nt!KiPageFault+0x35e
000000ca0a5af7b8 00000000
00000000 : 0000000000000000 00000000
00000000 0000000000000000 00000000
00000000 : 0x00007ffd`b28b9474
MODULE_NAME: hardware
IMAGE_NAME: hardware_ram
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x1a_61941_PAGE_TABLE_RESERVED_BITS_SET_IMAGE_hardware_ram
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {c6e5c6cf-692e-7852-5dc5-b74944540fc0}
Followup: MachineOwner
congratulation, now we have memory_management blue screen, first in my life i used memory test(windows memory diagnostic tool) 2cycles no errors… thank you for wasting time… must be they start fix it, after this implementation will destroy ram or drive store…