Share via

Random BSOD - Memory Management Error

Anonymous
2023-01-24T16:15:44+00:00

I'm keep getting this BSOD sometimes (for a period it keeps happening, then it stops, then it somehow starts again and so on). Today I checked the dump file generated by Windows but I can't understand what's the reason behind this BSOD, so I'm pasting here the result of WinDbg:

MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: 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: 0000000000004df2 Arg3: 00000000624539f6 Arg4: 000000004ac4ac56

Debugging Details:

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 3358

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 18605

Key  : Analysis.IO.Other.Mb
Value: 8

Key  : Analysis.IO.Read.Mb
Value: 0

Key  : Analysis.IO.Write.Mb
Value: 25

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

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

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

Key  : Bugcheck.Code.DumpHeader
Value: 0x1a

Key  : Bugcheck.Code.Register
Value: 0x1a

Key  : Dump.Attributes.AsUlong
Value: 8

Key  : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

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

FILE_IN_CAB: 012423-59609-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump

BUGCHECK_CODE: 1a

BUGCHECK_P1: 3f

BUGCHECK_P2: 4df2

BUGCHECK_P3: 624539f6

BUGCHECK_P4: 4ac4ac56

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)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: MsMpEng.exe

PAGE_HASH_ERRORS_DETECTED: 1

STACK_TEXT:
fffff58a3e52c678 fffff8032eb5b0ed : 000000000000001a 000000000000003f 0000000000004df2 00000000624539f6 : nt!KeBugCheckEx fffff58a3e52c680 fffff8032e8f1841 : ffff9e8c89afd0d0 ffffffffffffffff 0000000000000000 ffffdf0118868850 : nt!MiValidatePagefilePageHash+0x331 fffff58a3e52c760 fffff8032e8ef555 : fffff58a00010000 fffff58a3e52c800 fffff58a3e52c8f0 fffff80300000000 : nt!MiWaitForInPageComplete+0x351 fffff58a3e52c850 fffff8032e839aa8 : 00000000c0033333 0000000000000001 000002310d10a37f 0000000000000000 : nt!MiIssueHardFault+0x3c5 fffff58a3e52c960 fffff8032ea08dd8 : 000002311162b9aa 0000007b00000001 000002311f373640 ffff9e8c00000000 : nt!MmAccessFault+0x468 fffff58a3e52cb00 00007ffc9c693e3e : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x358 0000007ba56facd0 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffc`9c693e3e

SYMBOL_NAME: PAGE_HASH_ERRORS_INPAGE

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: PAGE_HASH_ERRORS_0x1a_3f

OSPLATFORM_TYPE: x64

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.

I thought this could be due to my HDD leaving me but then tools such as crystaldisk tells me it's still doing decently so I have no clue what this could be and how to potentially fix this.
Do any of you have some suggestion? Thank you so much for reading all of this!

Windows for home | Windows 10 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

9 answers

Sort by: Most helpful
  1. DaveM121 889.2K Reputation points Independent Advisor
    2023-01-25T10:06:25+00:00

    Hi Seinko, thank you for keeping me updated, please let me know the result of the 4 pass scan with MemTest86.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2023-01-25T09:59:51+00:00

    Earlier yesterday I ran a test with the Windows Memory Diagnostic Tool and highlighted no error with RAM, i'll try with MemTest86 too maybe we'll retrieve more info about that.

    For the drivers part I got all the latest stuff installed, even the BIOS version

    Was this answer helpful?

    0 comments No comments
  3. DaveM121 889.2K Reputation points Independent Advisor
    2023-01-25T08:21:04+00:00

    Hi Seinko,

    Your minidump files just indicate memory (RAM) corruption no specific driver is listed

    1

    Go to the support page for your PC or Motherboard on the manufacturers website, then from there, download and install the version of Chipset drivers they recommend and while there, check for any BIOS update that may need to be installed.

    2

    Wait to see if your system stabilizes, if not, the best option is to download the widely available free utility MemTest86, then run a full 4 pass scan with that to test your RAM for physical errors

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2023-01-24T20:59:24+00:00

    Hi Dave, thanks for reaching me out.
    I created a folder with today's minidump files and uploaded it on Drive, you can find it HERE

    Was this answer helpful?

    0 comments No comments
  5. DaveM121 889.2K Reputation points Independent Advisor
    2023-01-24T16:48:36+00:00

    Hi Seinko,

    I am Dave, I will help you with this.

    Please upload any minidump files you have, I will check those to see if they provide any insight into a potential cause of the system crashes.

    Open Windows File Explorer.

    Navigate to C:\Windows\Minidump

    Copy any minidump files onto your Desktop, then zip those up.

    Upload the zip file to the Cloud (OneDrive, DropBox... etc.), then choose to share those and get a share link.

    Then post the link here to the zip file, so we can take a look for you.

    Was this answer helpful?

    0 comments No comments