Windows 10: Another BSOD MEMORY_MANAGEMENT 1a

Well it seems that every 2 weeks i get a BSOD and i am lost, I have ran alot of hardware checks and seem to be going no where. I have reinstalled windows not keeping anything, and still getting these errors. below is the dump file from windbg. Thanks for the help!



Eric



Microsoft R Windows Debugger Version 10.0.19041.685 X86
Copyright c Microsoft Corporation. All rights reserved.


Loading Dump File 030621-34078-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 Personal
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff804`12a00000 PsLoadedModuleList = 0xfffff804`1362a390
Debug session time: Sat Mar 6 11:48:59.797 2021 UTC - 7:00
System Uptime: 0 days 23:11:51.475
Loading Kernel Symbols
.

Press ctrl-c cdb, kd, ntsd or ctrl-break windbg to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
.............................
For analysis of this file, run !analyze -v
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

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: 00000000000537d0
Arg3: 00000000a7a816b1
Arg4: 000000006d18a01b

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

*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 12

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

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 63

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

Key : Analysis.System
Value: CreateObject


BUGCHECK_CODE: 1a

BUGCHECK_P1: 3f

BUGCHECK_P2: 537d0

BUGCHECK_P3: a7a816b1

BUGCHECK_P4: 6d18a01b

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: MemCompression

PAGE_HASH_ERRORS_DETECTED: 1

TRAP_FRAME: ffffe58aa7980060 -- .trap 0xffffe58aa7980060
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff80412cf4990 rbx=0000000000000000 rcx=ffffe6811e649000
rdx=ffffe6811e649000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80412cf49e0 rsp=ffffe58aa79801f8 rbp=0000026dff362069
r8=0000026dff362090 r9=000000000000002f r10=ffffe6811e649ea0
r11=0000026dff3620bf r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!RtlDecompressBufferXpressLz+0x50:
fffff804`12cf49e0 418b08 mov ecx,dword ptr [r8] ds:0000026d`ff362090=????????
Resetting default scope

STACK_TEXT:
ffffe58a`a797fbd8 fffff804`12f57c6d : 00000000`0000001a 00000000`0000003f 00000000`000537d0 00000000`a7a816b1 : nt!KeBugCheckEx
ffffe58a`a797fbe0 fffff804`12cb69a1 : ffff978f`8c4f79a0 ffffffff`ffffffff 00000000`00000000 ffff9681`36ff9b10 : nt!MiValidatePagefilePageHash+0x331
ffffe58a`a797fcc0 fffff804`12cb4b35 : ffffe58a`00010000 ffffe58a`a797fe00 ffffe58a`a797fe50 fffff804`00000000 : nt!MiWaitForInPageComplete+0x351
ffffe58a`a797fdb0 fffff804`12c0c9c8 : 00000000`c0033333 00000000`00000000 0000026d`ff362090 00000000`00000000 : nt!MiIssueHardFault+0x3c5
ffffe58a`a797fec0 fffff804`12e03c5e : 000000cd`5dc7b480 00000000`00000000 00000000`00000001 000000cd`5dc7b390 : nt!MmAccessFault+0x468
ffffe58a`a7980060 fffff804`12cf49e0 : ffffe681`1e649000 ffff978f`89cf9050 fffff804`12cc42d0 ffffe681`1e649000 : nt!KiPageFault+0x35e
ffffe58a`a79801f8 fffff804`12cc42d0 : ffffe681`1e649000 ffffe681`1e649000 00000000`00000002 0000026d`ff362090 : nt!RtlDecompressBufferXpressLz+0x50
ffffe58a`a7980210 fffff804`12cc4018 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlDecompressBufferEx+0x60
ffffe58a`a7980260 fffff804`12cc3ea5 : 00000000`00000004 fffff804`12cc3a0e 00000000`00000000 00000000`00000001 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageCopy+0x150
ffffe58a`a7980320 fffff804`12cc36dc : 00000000`00000001 00000000`00012090 ffff978f`89cf9000 ffff978f`00001000 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0xa5
ffffe58a`a7980370 fffff804`12cc350c : 00000000`ffffffff ffff978f`85190000 ffffe58a`a7980450 ffff978f`84f0b4d0 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x180
ffffe58a`a7980410 fffff804`12cc3359 : fffff804`0f419730 00000000`00000001 00000000`00000000 00000000`00000000 : nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0xc8
ffffe58a`a79804c0 fffff804`12cc3211 : ffff978f`89cf9000 ffff978f`84f0b4d0 ffff978f`85190000 ffff978f`89cfa9c0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x85
ffffe58a`a7980540 fffff804`12d54488 : ffff978f`89390080 ffff978f`89cf9000 00000000`00000000 ffff978f`868aabd0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x21
ffffe58a`a7980570 fffff804`12d0a337 : fffff804`12cc31f0 ffffe58a`a7980610 00000000`00000003 00000000`00000000 : nt!KeExpandKernelStackAndCalloutInternal+0x78
ffffe58a`a79805e0 fffff804`12c3e0b4 : ffffe58a`a79806e0 00000000`31526d73 00000000`000003ff fffff804`137239c0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xc7
ffffe58a`a79806b0 fffff804`12c3dae8 : 00000000`0000000c 00000000`000003ff ffffe58a`a7980760 fffff804`137239c0 : nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x1ac
ffffe58a`a7980700 fffff804`12d09597 : 00000000`0000000c 00000000`00000001 ffff978f`84f0b4d0 ffff978f`868aabd0 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmIoCtxQueueWork+0xc0
ffffe58a`a7980790 fffff804`12d1d34b : ffff978f`00000001 ffff978f`868aac90 00000000`00000000 ffff978f`89cf9000 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmPageRead+0x167
ffffe58a`a7980800 fffff804`12cb6f60 : 0000007f`00000100 00000000`00000000 ffffe58a`a7980a58 fffff804`12cb4eb0 : nt!SmPageRead+0x33
ffffe58a`a7980850 fffff804`12cb4a0d : 00000000`00000002 ffffe58a`a79808e0 ffffe58a`a7980a58 ffff978f`868aab80 : nt!MiIssueHardFaultIo+0x10c
ffffe58a`a79808a0 fffff804`12c0c9c8 : 00000000`c0033333 00000000`00000001 000002c8`594bffdc 00000000`00000000 : nt!MiIssueHardFault+0x29d
ffffe58a`a7980960 fffff804`12e03c5e : 000002c8`3911d1a0 000000cd`5dc7abc0 ffffe58a`a7980b80 ffff978f`00000000 : nt!MmAccessFault+0x468
ffffe58a`a7980b00 00007ffb`115cbc56 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x35e
000000cd`5dc7a720 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`115cbc56


SYMBOL_NAME: PAGE_HASH_ERRORS_INPAGE

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: PAGE_HASH_ERRORS_0x1a_3f

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

Followup: MachineOwner
---------

*** Memory manager detected 1 instances of corrupted pagefilepages while performing in-page operations.

:)

 

Frequent display driver crashes and MEMORY_MANAGEMENT BSOD

http://lmgtfy.com/?q=ryzen+ windows+7+bsod+memory_management
./werdonerhere

 

Frequent display driver crashes and MEMORY_MANAGEMENT BSOD

Well sorry to tell you but display driver still crashes when launching a game.
so uhh
./wernotdonehere

It could be because it's an upgrade from w7 and not a clean install, which I'll try tomorrow, but still.

 

Memory_Management appears often, and then the PC restarts

These were similar errors as before ( PAGE_FAULT_IN_NONPAGED_AREA (50) and MEMORY_MANAGEMENT (1a) ).

There is a driver, ASACPI.sys , that could be problematic.

If you open "Uninstall or change a program" is there a listing for "ACPI driver for ATK 0110 virtual device"?