频繁蓝屏，是不是内存条出了问题

Question

前不久配的电脑，感觉买到水货内存条了

想让大佬看看是不是内存条出了问题，该怎么解决

崩溃日记：https://pan.baidu.com/s/1IOoUYALJLoGhX8JPjz6VuA 提取码：xy8h

Answer 1

今天又再次蓝屏，每天固定蓝屏一次 Microsoft (R) Windows Debugger Version 10.0.21349.1004 AMD64 Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\070521-7453-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff802`2c400000 PsLoadedModuleList = 0xfffff802`2d02a230
Debug session time: Mon Jul  5 16:47:50.742 2021 (UTC + 8:00)
System Uptime: 0 days 5:45:32.570
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
nt!KeBugCheckEx:
fffff802`2c7f6c20 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffffa0b`60f723a0=000000000000001a
3: 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: 00000000000048f4
Arg3: 000000007c8537ef
Arg4: 0000000081147dd7

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1874

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 11648

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

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

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

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

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  1a

BUGCHECK_P1: 3f

BUGCHECK_P2: 48f4

BUGCHECK_P3: 7c8537ef

BUGCHECK_P4: 81147dd7

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

PAGE_HASH_ERRORS_DETECTED: 1

STACK_TEXT:  
fffffa0b`60f72398 fffff802`2c9587fd     : 00000000`0000001a 00000000`0000003f 00000000`000048f4 00000000`7c8537ef : nt!KeBugCheckEx
fffffa0b`60f723a0 fffff802`2c65dae1     : ffffdc0f`202650d0 ffffffff`ffffffff 00000000`00000000 ffffff7d`05b2eab8 : nt!MiValidatePagefilePageHash+0x331
fffffa0b`60f72480 fffff802`2c65bc75     : fffffa0b`00001000 fffffa0b`60f72600 fffffa0b`60f72610 fffff802`00000000 : nt!MiWaitForInPageComplete+0x351
fffffa0b`60f72570 fffff802`2c728278     : 00000000`c0033333 00000000`00000000 fffffa0b`65d57000 00000000`00000000 : nt!MiIssueHardFault+0x3c5
fffffa0b`60f72680 fffff802`2c6855d0     : 8a000001`00000000 ffffdc0f`182f2080 00000000`00000fff 00000000`00000000 : nt!MmAccessFault+0x468
fffffa0b`60f72820 fffff802`2c684ecb     : ffffdc0f`00000000 ffffad81`15140180 ffffdc0f`18347080 00000000`00000000 : nt!MiInPageSingleKernelStack+0x370
fffffa0b`60f72a80 fffff802`2c7aff1f     : 00000000`00000000 ffffdc0f`00000000 ffffad81`15140100 11477982`ffffff00 : nt!KiInSwapKernelStacks+0x4b
fffffa0b`60f72ad0 fffff802`2c6f53b5     : ffffdc0f`07f75040 fffff802`2c7afea0 fffff802`2d050b00 00000000`00000000 : nt!KeSwapProcessOrStack+0x7f
fffffa0b`60f72b10 fffff802`2c7fe278     : ffffad81`15140180 ffffdc0f`07f75040 fffff802`2c6f5360 00000000`00000000 : nt!PspSystemThreadStartup+0x55
fffffa0b`60f72b60 00000000`00000000     : fffffa0b`60f73000 fffffa0b`60f6c000 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

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.

Answer 2

您好，我是微软社区独立顾问（Microsoft Community Independent Advisor）

Yu Huang。很高兴能为您提供技术支持！

通过您的日志文件分析来看，导致此次蓝屏的进程为：Steam.exe、dgprotect.exe、。

建议您先卸载重装设备中的 Steam、驱动精灵 应用，再重启设备使用一段时间，看是否还会蓝屏。

希望此条回复能帮助到您。