E
ENDER SCR0LLS
Guest
I have had to buy two more hard drives because my windows keeps getting corrupted. I have tried to solve the problem but at this point I have no clue.
I recently looked into the memory dump windows made and now I'm thinking it could be an issue related to my ram?
I would also like to note: I do a "sfc /scannow" and it says there not integrity violations. However, if I restart my PC I get blue screened and it says it scans the disk errors and tries to repair them. This is the first time it has actually repaired the error and I haven't had to buy a new hard drive.
Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\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 = 0xfffff807`45e00000 PsLoadedModuleList = 0xfffff807`46a2a2b0
Debug session time: Sat Dec 19 10:35:57.109 2020 (UTC - 5:00)
System Uptime: 8 days 1:14:49.147
Loading Kernel Symbols
...............................................................
................................................................
............................................................
Loading User Symbols
PEB address is NULL !
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`461f5780 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffe80e`47bef310=000000000000001a
8: 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: 0000000000023ada
Arg3: 000000006a021c37
Arg4: 000000003cd6a899
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2077
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-O7FBPNR
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 3582
Key : Analysis.Memory.CommitPeak.Mb
Value: 80
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: 3f
BUGCHECK_P2: 23ada
BUGCHECK_P3: 6a021c37
BUGCHECK_P4: 3cd6a899
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
PROCESS_NAME: MemCompression
PAGE_HASH_ERRORS_DETECTED: 1
STACK_TEXT:
ffffe80e`47bef308 fffff807`46357a7d : 00000000`0000001a 00000000`0000003f 00000000`00023ada 00000000`6a021c37 : nt!KeBugCheckEx
ffffe80e`47bef310 fffff807`460b69a1 : ffffaf0b`f578c030 ffffffff`ffffffff 00000000`00000000 ffff8000`c7010500 : nt!MiValidatePagefilePageHash+0x331
ffffe80e`47bef3f0 fffff807`460b4b35 : ffffe80e`00020000 ffffe80e`47bef500 ffffe80e`47bef580 fffff807`00000000 : nt!MiWaitForInPageComplete+0x351
ffffe80e`47bef4e0 fffff807`4600c9c8 : 00000000`c0033333 00000000`00000000 0000018e`020a0000 00000000`00000000 : nt!MiIssueHardFault+0x3c5
ffffe80e`47bef5f0 fffff807`46107d8c : ffff8040`20100000 ffffaf0b`f1eb6700 ffff8040`00638080 0000018e`020a0000 : nt!MmAccessFault+0x468
ffffe80e`47bef790 fffff807`460a771c : 00000000`00000001 ffff8000`c7010500 ffffe80e`47bef920 ffff8040`20100800 : nt!MiFaultInProbeAddress+0xbc
ffffe80e`47bef840 fffff807`461459a8 : 00000000`000000fc 00000000`00000000 ffffe80e`47bef989 ffffaf0c`04806a10 : nt!MiLockPageLeafPageTable+0x28c
ffffe80e`47bef8b0 fffff807`461458b8 : ffffe80e`00000000 00000000`00000000 ffffaf0c`04806a10 00000000`00000000 : nt!MiProbeLeafFrame+0x1c
ffffe80e`47bef8e0 fffff807`4610a259 : 00000000`00040000 fffff807`4604a31a ffffaf0b`f1eac8d8 00000000`00000000 : nt!MmStoreProbeAndLockPages+0x9c
ffffe80e`47bef9f0 fffff807`4610933c : 00000000`00040000 fffff807`46005611 ffffe80e`47befa60 00000000`00040246 : nt!SmKmProbeAndLockAddress+0x5d
ffffe80e`47befa20 fffff807`46109211 : 00000000`00040000 00000000`00000004 0000018e`020a0000 00000000`00020000 : nt!SmKmStoreHelperCommandProcess+0xac
ffffe80e`47befa90 fffff807`46117e25 : ffffaf0b`f1ea4080 00000000`00000080 fffff807`461091b0 000fa4ef`b59bbfff : nt!SmKmStoreHelperWorker+0x61
ffffe80e`47befb10 fffff807`461fcdd8 : ffffd781`a4440180 ffffaf0b`f1ea4080 fffff807`46117dd0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffe80e`47befb60 00000000`00000000 : ffffe80e`47bf0000 ffffe80e`47be9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
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 instance(s) of corrupted pagefilepage(s) while performing in-page operations
Continue reading...
I recently looked into the memory dump windows made and now I'm thinking it could be an issue related to my ram?
I would also like to note: I do a "sfc /scannow" and it says there not integrity violations. However, if I restart my PC I get blue screened and it says it scans the disk errors and tries to repair them. This is the first time it has actually repaired the error and I haven't had to buy a new hard drive.
Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\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 = 0xfffff807`45e00000 PsLoadedModuleList = 0xfffff807`46a2a2b0
Debug session time: Sat Dec 19 10:35:57.109 2020 (UTC - 5:00)
System Uptime: 8 days 1:14:49.147
Loading Kernel Symbols
...............................................................
................................................................
............................................................
Loading User Symbols
PEB address is NULL !
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`461f5780 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffe80e`47bef310=000000000000001a
8: 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: 0000000000023ada
Arg3: 000000006a021c37
Arg4: 000000003cd6a899
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2077
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-O7FBPNR
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 3582
Key : Analysis.Memory.CommitPeak.Mb
Value: 80
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: 3f
BUGCHECK_P2: 23ada
BUGCHECK_P3: 6a021c37
BUGCHECK_P4: 3cd6a899
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
PROCESS_NAME: MemCompression
PAGE_HASH_ERRORS_DETECTED: 1
STACK_TEXT:
ffffe80e`47bef308 fffff807`46357a7d : 00000000`0000001a 00000000`0000003f 00000000`00023ada 00000000`6a021c37 : nt!KeBugCheckEx
ffffe80e`47bef310 fffff807`460b69a1 : ffffaf0b`f578c030 ffffffff`ffffffff 00000000`00000000 ffff8000`c7010500 : nt!MiValidatePagefilePageHash+0x331
ffffe80e`47bef3f0 fffff807`460b4b35 : ffffe80e`00020000 ffffe80e`47bef500 ffffe80e`47bef580 fffff807`00000000 : nt!MiWaitForInPageComplete+0x351
ffffe80e`47bef4e0 fffff807`4600c9c8 : 00000000`c0033333 00000000`00000000 0000018e`020a0000 00000000`00000000 : nt!MiIssueHardFault+0x3c5
ffffe80e`47bef5f0 fffff807`46107d8c : ffff8040`20100000 ffffaf0b`f1eb6700 ffff8040`00638080 0000018e`020a0000 : nt!MmAccessFault+0x468
ffffe80e`47bef790 fffff807`460a771c : 00000000`00000001 ffff8000`c7010500 ffffe80e`47bef920 ffff8040`20100800 : nt!MiFaultInProbeAddress+0xbc
ffffe80e`47bef840 fffff807`461459a8 : 00000000`000000fc 00000000`00000000 ffffe80e`47bef989 ffffaf0c`04806a10 : nt!MiLockPageLeafPageTable+0x28c
ffffe80e`47bef8b0 fffff807`461458b8 : ffffe80e`00000000 00000000`00000000 ffffaf0c`04806a10 00000000`00000000 : nt!MiProbeLeafFrame+0x1c
ffffe80e`47bef8e0 fffff807`4610a259 : 00000000`00040000 fffff807`4604a31a ffffaf0b`f1eac8d8 00000000`00000000 : nt!MmStoreProbeAndLockPages+0x9c
ffffe80e`47bef9f0 fffff807`4610933c : 00000000`00040000 fffff807`46005611 ffffe80e`47befa60 00000000`00040246 : nt!SmKmProbeAndLockAddress+0x5d
ffffe80e`47befa20 fffff807`46109211 : 00000000`00040000 00000000`00000004 0000018e`020a0000 00000000`00020000 : nt!SmKmStoreHelperCommandProcess+0xac
ffffe80e`47befa90 fffff807`46117e25 : ffffaf0b`f1ea4080 00000000`00000080 fffff807`461091b0 000fa4ef`b59bbfff : nt!SmKmStoreHelperWorker+0x61
ffffe80e`47befb10 fffff807`461fcdd8 : ffffd781`a4440180 ffffaf0b`f1ea4080 fffff807`46117dd0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffe80e`47befb60 00000000`00000000 : ffffe80e`47bf0000 ffffe80e`47be9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
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 instance(s) of corrupted pagefilepage(s) while performing in-page operations
Continue reading...