Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\SUBHO\Desktop\112419-31687-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 18362 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff802
Debug session time: Sun Nov 24 01:02:17.308 2019 (UTC + 5:30)
System Uptime: 0 days 6:32:50.961
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
***
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: 000000000009f82b
Arg3: 000000006d673cbe
Arg4: 000000001acf1774
Debugging Details:
------------------
KEY_VALUES_STRING: 1
PROCESSES_ANALYSIS: 1
SERVICE_ANALYSIS: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.18362.356 (WinBuild.160101.0800)
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
DUMP_TYPE: 2
BUGCHECK_P1: 3f
BUGCHECK_P2: 9f82b
BUGCHECK_P3: 6d673cbe
BUGCHECK_P4: 1acf1774
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: 4
CPU_MHZ: e70
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 5e
CPU_STEPPING: 3
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: avguard.exe
CURRENT_IRQL: 2
PAGE_HASH_ERRORS_DETECTED: 1
ANALYSIS_SESSION_HOST: DESKTOP-QP54UD0
ANALYSIS_SESSION_TIME: 11-24-2019 01:58:26.0823
ANALYSIS_VERSION: 10.0.18362.1 amd64fre
LAST_CONTROL_TRANSFER: from fffff8026a663b96 to fffff8026a5c10a0
STACK_TEXT:
fffff98c
fffff98c
fffff98c
fffff98c
fffff98c
fffff98c
00000000
THREAD_SHA1_HASH_MOD_FUNC: 8b6e3ada00439d00cd6002e9bc2bdd23ad35bd9c
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 216aab493693fd831612962b01315a855ee608ea
THREAD_SHA1_HASH_MOD: ee8fcf1fb60cb6e3e2f60ddbed2ec02b5748a693
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: 2019-11-23T19:32:17.000Z
OSBUILD: 18362
OSSERVICEPACK: 356
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: unknown_date
BUILDDATESTAMP_STR: 160101.0800
BUILDLAB_STR: WinBuild
BUILDOSVER_STR: 10.0.18362.356
ANALYSIS_SESSION_ELAPSED_TIME: 1bbe
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: kmage_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.
MY PC SPECS ARE :i3 6100 ,4-4gb of 1 crucial and 1 adata ram total 8gb and gt 1030
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\SUBHO\Desktop\112419-31687-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 18362 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff802
6a400000 PsLoadedModuleList = 0xfffff802
6a8475b0Debug session time: Sun Nov 24 01:02:17.308 2019 (UTC + 5:30)
System Uptime: 0 days 6:32:50.961
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: 000000000009f82b
Arg3: 000000006d673cbe
Arg4: 000000001acf1774
Debugging Details:
------------------
KEY_VALUES_STRING: 1
PROCESSES_ANALYSIS: 1
SERVICE_ANALYSIS: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.18362.356 (WinBuild.160101.0800)
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
DUMP_TYPE: 2
BUGCHECK_P1: 3f
BUGCHECK_P2: 9f82b
BUGCHECK_P3: 6d673cbe
BUGCHECK_P4: 1acf1774
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: 4
CPU_MHZ: e70
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 5e
CPU_STEPPING: 3
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: avguard.exe
CURRENT_IRQL: 2
PAGE_HASH_ERRORS_DETECTED: 1
ANALYSIS_SESSION_HOST: DESKTOP-QP54UD0
ANALYSIS_SESSION_TIME: 11-24-2019 01:58:26.0823
ANALYSIS_VERSION: 10.0.18362.1 amd64fre
LAST_CONTROL_TRANSFER: from fffff8026a663b96 to fffff8026a5c10a0
STACK_TEXT:
fffff98c
f3877568 fffff802
6a663b96 : 000000000000001a 00000000
0000003f 000000000009f82b 00000000
6d673cbe : nt!KeBugCheckExfffff98c
f3877570 fffff802
6a48e112 : ffffb60590a505e0 ffffffff
ffffffff 0000000000000000 ffffb605
90a506d0 : nt!MiValidatePagefilePageHash+0x10157afffff98c
f3877650 fffff802
6a48d65d : 0000000000000002 fffff98c
00000000 fffff98cf3877808 fffff802
00000000 : nt!MiWaitForInPageComplete+0x472fffff98c
f3877760 fffff802
6a47317b : 00000000c0033333 00000000
00000001 000000000d67aacf 00000000
00000000 : nt!MiIssueHardFault+0x1adfffff98c
f3877860 fffff802
6a5cf120 : ffffb6058baea080 ffffb605
8ee9d660 0000000000ebd000 00000000
0becf734 : nt!MmAccessFault+0x40bfffff98c
f3877a00 00000000
7765b0c8 : 0000000000000000 00000000
00000000 0000000000000000 00000000
00000000 : nt!KiPageFault+0x36000000000
0becf3c4 00000000
00000000 : 0000000000000000 00000000
00000000 0000000000000000 00000000
00000000 : 0x7765b0c8THREAD_SHA1_HASH_MOD_FUNC: 8b6e3ada00439d00cd6002e9bc2bdd23ad35bd9c
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 216aab493693fd831612962b01315a855ee608ea
THREAD_SHA1_HASH_MOD: ee8fcf1fb60cb6e3e2f60ddbed2ec02b5748a693
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: 2019-11-23T19:32:17.000Z
OSBUILD: 18362
OSSERVICEPACK: 356
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: unknown_date
BUILDDATESTAMP_STR: 160101.0800
BUILDLAB_STR: WinBuild
BUILDOSVER_STR: 10.0.18362.356
ANALYSIS_SESSION_ELAPSED_TIME: 1bbe
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: kmage_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.
MY PC SPECS ARE :i3 6100 ,4-4gb of 1 crucial and 1 adata ram total 8gb and gt 1030