BSOD - Memory Dump, help, please

Question

BSOD - Memory Dump, help, please

Anonymous

I have a very new Dell Inspiron. When I am away from the machine, I come back and it has rebooted. I know that it must be the BSOD as I am getting a new MEMORY.DMP file. I've installed WinDbg, but honestly, this results are gibberish to me. Can someone make anything of this?

Microsoft (R) Windows Debugger Version 10.0.17134.12 AMD64

Loading Dump File [C:\Windows\MEMORY.DMP]

Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

************* Path validation summary **************

Response Time (ms) Location

Deferred SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols

Executable search path is:

Windows 10 Kernel Version 17134 MP (8 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 17134.1.amd64fre.rs4_release.180410-1804

Machine Name:

Kernel base = 0xfffff8029bc9d000 PsLoadedModuleList = 0xfffff8029c05a1d0

Debug session time: Mon Jun 11 17:29:18.532 2018 (UTC - 4:00)

System Uptime: 1 days 19:36:28.315

Loading Kernel Symbols

...............................................................

................................................................

..................

Loading User Symbols

PEB address is NULL !

Loading unloaded module list

............................

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {3f, a7c3b, 3c2194b1, 5ec40aa8}

Probably caused by : Unknown_Image ( PAGE_HASH_ERRORS_INPAGE )

Followup: MachineOwner

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

0: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

MEMORY_MANAGEMENT (1a)

# Any other values for parameter 1 must be individually examined.

Arguments:

Arg1: 000000000000003f, The subtype of the bugcheck.

Arg2: 00000000000a7c3b

Arg3: 000000003c2194b1

Arg4: 000000005ec40aa8

Debugging Details:

KEY_VALUES_STRING: 1

TIMELINE_ANALYSIS: 1

DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804

SYSTEM_MANUFACTURER: Dell Inc.

SYSTEM_PRODUCT_NAME: Inspiron 5770

SYSTEM_SKU: 0811

BIOS_VENDOR: Dell Inc.

BIOS_VERSION: 1.1.3

BIOS_DATE: 02/02/2018

BASEBOARD_MANUFACTURER: Dell Inc.

BASEBOARD_PRODUCT: 0F1VY1

BASEBOARD_VERSION: A00

DUMP_TYPE: 1

BUGCHECK_P1: 3f

BUGCHECK_P2: a7c3b

BUGCHECK_P3: 3c2194b1

BUGCHECK_P4: 5ec40aa8

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.

BUGCHECK_STR: 0x1a_3f

CPU_COUNT: 8

CPU_MHZ: 708

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 8e

CPU_STEPPING: a

CPU_MICROCODE: 6,8e,a,0 (F,M,S,R) SIG: 84'00000000 (cache) 84'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXPNP: 1 (!blackboxpnp)

PROCESS_NAME: MemCompression

CURRENT_IRQL: 2

PAGE_HASH_ERRORS_DETECTED: 1

ANALYSIS_SESSION_HOST: DESKTOP-1IOFCI9

ANALYSIS_SESSION_TIME: 06-11-2018 18:12:00.0601

ANALYSIS_VERSION: 10.0.17134.12 amd64fre

TRAP_FRAME: ffffad8b59d6afa0 -- (.trap 0xffffad8b59d6afa0)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=fffff8029bdefdb0 rbx=0000000000000000 rcx=ffffc901dd63b000

rdx=ffffc901dd63b000 rsi=0000000000000000 rdi=0000000000000000

rip=fffff8029bdefe00 rsp=ffffad8b59d6b130 rbp=0000000029ed31d4

r8=0000000029ed2da0 r9=0000000000000434 r10=ffffc901dd63bea0

r11=ffffc901dd63b000 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei pl zr na po nc

nt!RtlDecompressBufferXpressLz+0x50:

fffff8029bdefe00 418b08 mov ecx,dword ptr [r8] ds:0000000029ed2da0=????????

Resetting default scope

LAST_CONTROL_TRANSFER: from fffff8029beb83fa to fffff8029be34670

STACK_TEXT:

ffffad8b59d6ab38 fffff8029beb83fa : 000000000000001a 000000000000003f 00000000000a7c3b 000000003c2194b1 : nt!KeBugCheckEx

ffffad8b59d6ab40 fffff8029bd84fc7 : ffffe0048387c7a0 ffffffffffffffff 0000000000000000 ffffe0048387c888 : nt!MiValidatePagefilePageHash+0xd9aa2

ffffad8b59d6ac20 fffff8029bd21abd : 0000000000000002 ffffad8b00000000 ffffad8b59d6add8 fffff80200000000 : nt!MiWaitForInPageComplete+0x447

ffffad8b59d6ad30 fffff8029bd0e864 : 00000000c0033333 0000000000000000 0000000029ed2da0 0000000000000000 : nt!MiIssueHardFault+0x20d

ffffad8b59d6ae30 fffff8029be439c7 : ffffad8b59d6aefc 0000000000000434 ffffe00481cd9000 ffffc901dd63c000 : nt!MmAccessFault+0x384

ffffad8b59d6afa0 fffff8029bdefe00 : ffffad8b59d6b3c8 ffffc901dd63b000 ffffc901dd63b000 fffff8029bd52980 : nt!KiPageFault+0x3c7

ffffad8b59d6b130 fffff8029bd52980 : ffffc901dd63b000 ffffe0048041f050 0000000029ed2da0 fffff8029be3ca9d : nt!RtlDecompressBufferXpressLz+0x50

ffffad8b59d6b150 fffff8029bddcd5c : 0000000000000000 fffff80200000001 0000000029ed2da0 0000000000000001 : nt!RtlDecompressBufferEx+0x60

ffffad8b59d6b1a0 fffff8029bddcbdd : 0000000000000004 ffffad8b59d6b3b0 0000000000000000 000000000000001a : nt!ST_STORE<SM_TRAITS>::StDmSinglePageCopy+0x158

ffffad8b59d6b280 fffff8029bddcaa2 : 0000000000000001 0000000000002da0 ffffad8b00002da0 0000000000002000 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0x95

ffffad8b59d6b2d0 fffff8029bddc8cd : 00000000ffffffff ffffe00481cd9000 ffffad8b59d6b3b0 ffffe00483dad550 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x186

ffffad8b59d6b370 fffff8029bddc721 : ffffe00481cd9000 fffff80200000000 0000000000000001 ffffe00480420788 : nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0xc1

ffffad8b59d6b420 fffff8029bddc631 : ffffe0048041f000 ffffe00483dad550 ffffe00481cd9000 ffffe004804209b0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x85

ffffad8b59d6b4a0 fffff8029bcaca0a : ffffe00484420080 ffffad8b59d6b570 ffffad8b59d6b770 ffffe00482a64e90 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x21

ffffad8b59d6b4d0 fffff8029bddef5d : fffff8029bddc610 ffffad8b59d6b570 0000000000000003 ffffe00481cd9000 : nt!KeExpandKernelStackAndCalloutInternal+0x8a

ffffad8b59d6b530 fffff8029bd76f49 : ffffad8b59d6b630 fffff8029bd76aed 0000000000000005 fffff8029bdde504 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xad

ffffad8b59d6b600 fffff8029bd7698a : 0000000000000005 0000000000000005 ffffad8b59d6b6b0 ffffe00483dad550 : nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x1b1

ffffad8b59d6b650 fffff8029bdde268 : 000000000000000c 0000000000000002 ffffe00483dad550 ffffe00482a64e90 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmIoCtxQueueWork+0xce

ffffad8b59d6b6d0 fffff8029bddf876 : 0000000000000002 ffffe00482a64f48 0000000000000000 ffffe0048041f000 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmPageRead+0x168

ffffad8b59d6b740 fffff8029bdb093a : ffffad8b59d6ba00 ffffe00480585580 ffffad8b59d6b820 fffff8029bd0fa76 : nt!SmPageRead+0x2e

ffffad8b59d6b790 fffff8029bd21a88 : 0000000000000002 ffffad8b59d6b820 ffffad8b59d6b8c0 8a00000085bbc825 : nt!MiIssueHardFaultIo+0x122

ffffad8b59d6b7e0 fffff8029bd0e864 : 00000000c0033333 0000000000000001 00007ff9656e3790 ffffb903efdf16d0 : nt!MiIssueHardFault+0x1d8

ffffad8b59d6b890 fffff8029be439c7 : 0000000000000000 0000000000000010 0000000000000001 0000000000000000 : nt!MmAccessFault+0x384

ffffad8b59d6ba00 00007ff965650be6 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x3c7

000000ca08bfef50 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ff9`65650be6

THREAD_SHA1_HASH_MOD_FUNC: 184a2ca67ebe94bd7abe6480b7c31ccb7fc9d481

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 1b3af023295c7073ab98357eb5443b0a4738ed39

THREAD_SHA1_HASH_MOD: ef0b9811d1c3c2b0b400d0c8a17067df59efd56d

SYMBOL_NAME: PAGE_HASH_ERRORS_INPAGE

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .thread ; .cxr ; kb

FOLLOWUP_NAME: MachineOwner

BUCKET_ID: PAGE_HASH_ERRORS_0x1a_3f

DEFAULT_BUCKET_ID: PAGE_HASH_ERRORS_0x1a_3f

PRIMARY_PROBLEM_CLASS: PAGE_HASH_ERRORS_0x1a_3f

FAILURE_BUCKET_ID: PAGE_HASH_ERRORS_0x1a_3f

TARGET_TIME: 2018-06-11T21:29:18.000Z

OSBUILD: 17134

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2018-04-27 23:58:00

BUILDDATESTAMP_STR: 180410-1804

BUILDLAB_STR: rs4_release

BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804

ANALYSIS_SESSION_ELAPSED_TIME: c5a

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:page_hash_errors_0x1a_3f

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

Followup: MachineOwner

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

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

3 answers

Answer 1

Have you've made any recent changes prior to this issue?

What troubleshooting steps have you done so far to resolve your concern?

Thank you for your reply.

The computer is new (May 17, 2018). The only hardware that I have changed was changing the HDD to a SSD, but I only noticed the stop error a few days ago. The stop error happens when I am NOT using the computer, but the computer is on. I come back to a machine that has restarted and a new memory.dmp file in the windows directory.

I have already done the following steps.

Installed all Windows Updates
Checked for driver updates (all drivers are current--no updates needed)
I have checked device health in windows defender
I have run an windows defender offline
I have run DISM.exe /Online /Cleanup-image /Restorehealth
I have run the system file checker (sfc /scannow) no errors were reported.
I have uninstalled Acronis True Image

Answer 2

I appreciate your prompt response. To further assist you with your concern, I'd recommend running Windows Memory Diagnostics utility to help us identify and diagnose problems with memory. To do this, follow the steps below:

Type mdsched.exe in the Search box and press Enter.
Choose whether to restart the computer and run the tool immediately or schedule the tool to run at the next restart.
Windows Memory Diagnostics runs automatically after the computer restarts and performs a standard memory test automatically. If you want to perform fewer or more tests, press F1, use the Up and Down arrow keys to set the Test Mix as Basic, Standard, or Extended, and then press F10 to apply the desired settings and resume testing.
When testing is completed, the computer restarts automatically. You’ll see the test results when you log on.

Note: If a computer crashes because of failing memory, and Windows Memory Diagnostics detects this, the system will prompt you to schedule a memory test the next time the computer is restarted.

Also, Dell has a built-in diagnostic tool that I'd suggest running to also identify and repair hardware related issues that can cause this issue. You may visit this link for more details.

Note: Should you need assistance on running this built-in tool, I'd recommend contacting Dell support.

Let us know if you need further assistance, we’ll be glad to assist you.

Answer 3

Hello eurbani,

Error as such typically occurs after you install a faulty or mismatched hardware (especially memory) or if installed hardware fails. Before we proceed with the resolution, we’d like to verify the following:

Have you've made any recent changes prior to this issue?
What troubleshooting steps have you done so far to resolve your concern?

As an initial troubleshooting steps, we have an entire support article dedicated on repairing blue screen errors. To view this article, click on this link.

Your reply is most important for us to ensure we assist you accordingly.

Share via

BSOD - Memory Dump, help, please

3 answers