Question i am getting memory management error

Jul 19, 2022
icrosoft (R) Windows Debugger Version 10.0.22621.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\perez\OneDrive\Desktop\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff80613400000 PsLoadedModuleList = 0xfffff8061402a230
Debug session time: Tue Jul 19 11:22:32.823 2022 (UTC - 5:00)
System Uptime: 0 days 0:45:17.455
Loading Kernel Symbols
...Page 10d6c1 not present in the dump file. Type ".hh dbgerr004" for details
Loading User Symbols
PEB address is NULL !
Loading unloaded module list
For analysis of this file, run !analyze -v
11: kd> !analyze -v
  • *
  • Bugcheck Analysis *
  • *

# Any other values for parameter 1 must be individually examined.
Arg1: 000000000000003f, An inpage operation failed with a CRC error. Parameter 2 contains
the pagefile offset. Parameter 3 contains the page CRC value.
Parameter 4 contains the expected CRC value.
Arg2: 0000000000121676
Arg3: 0000000063311b29
Arg4: 00000000c01f3bb0

Debugging Details:


Key : Analysis.CPU.mSec
Value: 3265

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 3714

Key : Analysis.Init.CPU.mSec
Value: 2952

Key : Analysis.Init.Elapsed.mSec
Value: 51619

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

Key : Memory.System.Errors.PageHashErrors
Value: 1

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




BUGCHECK_P2: 121676

BUGCHECK_P3: 63311b29

BUGCHECK_P4: c01f3bb0

ADDITIONAL_DEBUG_TEXT: Memory Manager detected corruption of a pagefile page while performing an in-page operation.
The data read from storage does not match the original data written.
This indicates the data was corrupted by the storage stack, or device hardware.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)


PROCESS_NAME: MemCompression


TRAP_FRAME: fffffe8e2c9803b0 -- (.trap 0xfffffe8e2c9803b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffb88194711000 rbx=0000000000000000 rcx=ffffde8d4d9acc40
rdx=ffffb88194711000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80613a5b280 rsp=fffffe8e2c980540 rbp=ffffde8d4d9acc40
r8=ffffa70e74dd238c r9=0000000066ea0000 r10=0000000000000004
r11=0000000000000003 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
fffff80613a5b280 0fb613 movzx edx,byte ptr [rbx] ds:0000000000000000=??
Resetting default scope

fffffe8e2c97f4e8 fffff80613958d1d : 000000000000001a 000000000000003f 0000000000121676 0000000063311b29 : nt!KeBugCheckEx
fffffe8e2c97f4f0 fffff806136bc5d1 : ffffde8d5bbfabd0 ffffffffffffffff 0000000000000000 fffff681301b95e8 : nt!MiValidatePagefilePageHash+0x331
fffffe8e2c97f5d0 fffff806136819f5 : fffffe8e00004000 fffffe8e2c97f700 fffffe8e2c97f760 fffff80600000000 : nt!MiWaitForInPageComplete+0x351
fffffe8e2c97f6c0 fffff806136cf6d8 : 00000000c0033333 0000000000000000 00000260372bd7f0 0000000000000000 : nt!MiIssueHardFault+0x3c5
fffffe8e2c97f7d0 fffff8061380675e : 0000000000006000 fffff8061367cbc2 fffff80615822650 fffffe8e2c97fad8 : nt!MmAccessFault+0x468
fffffe8e2c97f970 fffff8061380b552 : fffff8061360c137 ffffde8d00000003 0000000000000000 0000000000000000 : nt!KiPageFault+0x35e
fffffe8e2c97fb08 fffff8061360c137 : ffffde8d00000003 0000000000000000 0000000000000000 ffffde8d5e07d9a8 : nt!memcpy+0x92
fffffe8e2c97fb10 fffff8061360bf39 : 0000000000000004 fffff8061360c32e 0000000000000000 0000000000000001 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageCopy+0x1db
fffffe8e2c97fbd0 fffff8061360c8a0 : 0000000000000001 000000000000d7f0 ffffde8d59614000 ffffde8d00001000 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0xa5
fffffe8e2c97fc20 fffff8061360bc84 : 00000000ffffffff ffffde8d60355000 fffffe8e2c97fd00 ffffde8d606eff50 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x180
fffffe8e2c97fcc0 fffff80613607505 : ffffb88191008730 0000000000000003 0000000000000000 0000000000000000 : nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0xc8
fffffe8e2c97fd70 fffff80613607611 : ffffde8d59614000 ffffde8d606eff50 ffffde8d60355000 ffffde8d596159c0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x85
fffffe8e2c97fdf0 fffff8061367ca68 : ffffde8d5c0d5080 ffffde8d59614000 0000000000000000 ffffde8d5dd20e00 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x21
fffffe8e2c97fe20 fffff8061360517f : fffff806136075f0 fffffe8e2c97fec0 0000000000000003 0000000000000000 : nt!KeExpandKernelStackAndCalloutInternal+0x78
fffffe8e2c97fe90 fffff80613704c10 : fffffe8e2c97ff90 0000000031526d73 00000000000003ff fffff806141239c0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xc7
fffffe8e2c97ff60 fffff80613704644 : 000000000000000c 00000000000003ff fffffe8e2c980010 fffff806141239c0 : nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x1ac
fffffe8e2c97ffb0 fffff80613605707 : 000000000000000c 0000000000000001 ffffde8d606eff50 ffffde8d5dd20e00 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmIoCtxQueueWork+0xc0
fffffe8e2c980040 fffff80613753cdb : ffffde8d00000001 ffffde8d5dd20ec0 0000000000000000 ffffde8d59614000 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmPageRead+0x167
fffffe8e2c9800b0 fffff80613680f50 : fffffe8e00000100 0000000000000000 fffffe8e2c980308 fffff80613681d70 : nt!SmPageRead+0x33
fffffe8e2c980100 fffff806136818cd : 0000000000000002 fffffe8e2c980190 fffffe8e2c980308 ffffde8d5dd20db0 : nt!MiIssueHardFaultIo+0x10c
fffffe8e2c980150 fffff806136cf6d8 : 00000000c0033333 0000000000000000 ffffa70e74dd238c 0000000000000000 : nt!MiIssueHardFault+0x29d
fffffe8e2c980210 fffff8061380675e : 0000000100000101 0000800000000000 0000800000000002 ffffa70e749a9c38 : nt!MmAccessFault+0x468
fffffe8e2c9803b0 fffff80613a5b280 : 0000000000000000 ffffde8d4d9acc40 0000000000000001 0000000000000000 : nt!KiPageFault+0x35e
fffffe8e2c980540 fffff80613a5b3dc : ffffb88194711000 ffffa70e74dd238c 0000000000000047 fffffe8e2c981000 : nt!MiApplyCompressedFixups+0x60
fffffe8e2c9805a0 fffff80613a5b9fd : ffffde8d5c0d5080 ffffde8d4d9acc40 0000000066ea0000 0000000000000047 : nt!MiPerformFixups+0x88
fffffe8e2c980640 fffff806136831f0 : 0000000000000000 000000000000000c 0000000000000000 0000000000000000 : nt!MiRelocateImagePfn+0x18d
fffffe8e2c9806b0 fffff806136bc594 : ffffde8d00000000 0000000000000000 0000000000000000 ffffde8d5c8f1080 : nt!MiValidateInPage+0x260
fffffe8e2c980760 fffff806136819f5 : fffffe8e00008000 fffffe8e2c980800 fffffe8e2c9808f0 fffff80600000000 : nt!MiWaitForInPageComplete+0x314
fffffe8e2c980850 fffff806136cf6d8 : 00000000c0033333 0000000000000001 0000000076ee761a ffffa70e708f8ad8 : nt!MiIssueHardFault+0x3c5
fffffe8e2c980960 fffff8061380675e : ffffde8d5c0d5000 00007ff96a545ce0 fffffe8e2c980b80 0000000000000000 : nt!MmAccessFault+0x468
fffffe8e2c980b00 0000000076ee761a : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x35e
000000000569cee0 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x76ee761a


MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

STACK_COMMAND: .cxr; .ecxr ; kb


OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release


OSNAME: Windows 10

FAILURE_ID_HASH: {6a2d4548-0eec-578d-e8f1-9e2239aa9a00}

Followup: MachineOwner

*** Memory manager detected 1 instance(s) of corrupted pagefile page(s) while performing in-page operations.

my pc specs


PSU: make, model, wattage, age, condition (original to build, new, refurbished, used)? History of heavy gaming use, video editing, or bit mining.

Disk drives: make, model, capacity, how full?

Look in Reliability History and Event Viewer for any errors, warnings, or informational events regarding RAM. But do not disregard other errors or error patterns.
if this is a intel based system and you were using the intel storage driver. update the intel chipset drivers from your motherboard vendors website or directly from intel:
Intel® Driver & Support Assistant

then turn off the system virtual memory, reboot and turn it back on again so that your pagefile.sys is deleted and a new one is created. This will dump any corruptions that are stored in the pagefile that the memory manager has not attempted to get the data from. (to prevent future bugchecks due to un detected corruptions)

I mention this due to a bug in the intel drivers that cause pagefile.sys corruptions over time. (bug in sleep function cause corruptions after each sleep/wake cycle) This was fixed in the new drivers.

otherwise you would want to update the bios and confirm your memory timings by running memtest86 on its own boot image.
Last edited: