通过

如何解决我的Windows pc 上的SYMBOL_NAME: nt!ST_STORE<SM_TRAITS>::StDmPageError+10a 问题

^^ AME 40 信誉分
2024-06-19T14:29:24.2433333+00:00 
************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : true
   AllowNugetExeUpdate : true
   NonInteractiveNuget : true
   AllowNugetMSCredentialProviderInstall : true
   AllowParallelInitializationOfLocalRepositories : true

   EnableRedirectToV8JsProvider : false

   -- Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.031 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 41

Microsoft (R) Windows Debugger Version 10.0.27553.1004 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\061724-12687-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 (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff806`33400000 PsLoadedModuleList = 0xfffff806`3402a360
Debug session time: Mon Jun 17 23:06:01.600 2024 (UTC + 8:00)
System Uptime: 1 days 1:07:10.115
Loading Kernel Symbols
...............................................................
................................................................
................................................................
....................................
Loading User Symbols
PEB address is NULL !
Loading unloaded module list
....................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`337fdb50 48894c2408      mov     qword ptr [rsp+8],rcx ss:ffffe086`8db2c100=000000000000012b
5: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

FAULTY_HARDWARE_CORRUPTED_PAGE (12b)
This BugCheck indicates that a single bit error was found in this page.  This is a hardware memory error.
Arguments:
Arg1: ffffffffc00002c4, virtual address mapping the corrupted page
Arg2: 000000000000061a, physical page number
Arg3: 000001cd16443d70, zero
Arg4: ffff8d014ccc9000, zero

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2203

    Key  : Analysis.Elapsed.mSec
    Value: 5455

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 0

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

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

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

    Key  : BlackBox.SmDecompressionFailure.CompressedSize
    Value: 0x61a

    Key  : BlackBox.SmDecompressionFailure.CompressionFormat
    Value: 0x3

    Key  : BlackBox.SmDecompressionFailure.SourceDataHash
    Value: 0x9fb66e60

    Key  : BlackBox.SmDecompressionFailure.SourceDataOffset
    Value: 0x3d70

    Key  : BlackBox.SmDecompressionFailure.SourcePFN1
    Value: 0x1234dd

    Key  : BlackBox.SmDecompressionFailure.SourcePFN2
    Value: 0x35d2dc

    Key  : BlackBox.SmDecompressionFailure.TargetPFN
    Value: 0x173cb9

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x12b

    Key  : Bugcheck.Code.TargetModel
    Value: 0x12b

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: 0x12B_c00002c4_StCtDecompressFailed_nt!ST_STORE_SM_TRAITS_::StDmPageError

    Key  : Failure.Hash
    Value: {c6a6bb4d-3b77-dff6-2d9b-75f5d0f61a50}


BUGCHECK_CODE:  12b

BUGCHECK_P1: ffffffffc00002c4

BUGCHECK_P2: 61a

BUGCHECK_P3: 1cd16443d70

BUGCHECK_P4: ffff8d014ccc9000

FILE_IN_CAB:  061724-12687-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  MemCompression

STACK_TEXT:  
ffffe086`8db2c0f8 fffff806`3399d0b2     : 00000000`0000012b ffffffff`c00002c4 00000000`0000061a 000001cd`16443d70 : nt!KeBugCheckEx
ffffe086`8db2c100 fffff806`33860837     : 00000000`00000001 00000000`c00002c4 ffff8d01`4ccc9000 00000000`00000001 : nt!ST_STORE<SM_TRAITS>::StDmPageError+0x10a
ffffe086`8db2c160 fffff806`336e3e95     : 00000000`00000004 fffff806`336e39fe 00000000`00000000 00000000`00000001 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageCopy+0x17c97f
ffffe086`8db2c220 fffff806`336e3764     : 00000000`00000001 00000000`00003d70 00000000`00000000 ffffa10c`0000f000 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0xa5
ffffe086`8db2c270 fffff806`336e4360     : fffff806`ffffffff ffffa10c`fee94000 ffffe086`8db2c350 ffffa10c`fe9f7390 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x180
ffffe086`8db2c310 fffff806`336e45cd     : ffff8d01`2dc81730 00000000`00000001 00000000`00000000 00000000`00000000 : nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0xc8
ffffe086`8db2c3c0 fffff806`336e4681     : ffffa10c`f1b0e000 ffffa10c`fe9f7390 ffffa10c`fee94000 ffffa10c`f1b0f9c0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x85
ffffe086`8db2c440 fffff806`33673b48     : ffffa10c`f1caf540 ffffa10c`f1b0e000 00000000`00000000 ffffa10c`fd971260 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x21
ffffe086`8db2c470 fffff806`3374643f     : fffff806`336e4660 ffffe086`8db2c510 00000000`00000003 00000000`00000000 : nt!KeExpandKernelStackAndCalloutInternal+0x78
ffffe086`8db2c4e0 fffff806`33608aa4     : ffffe086`8db2c5e0 00000000`31526d73 00000000`000003ff fffff806`341239c0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xc7
ffffe086`8db2c5b0 fffff806`336084d8     : 00000000`0000000c 00000000`000003ff ffffe086`8db2c660 fffff806`341239c0 : nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x1ac
ffffe086`8db2c600 fffff806`336e5547     : 00000000`0000000c 00000000`0000000f ffffa10c`fe9f7390 ffffa10c`fd971260 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmIoCtxQueueWork+0xc0
ffffe086`8db2c690 fffff806`3374e18b     : ffffa10c`0000000f ffffa10c`fd971320 00000000`00000000 ffffa10c`f1b0e000 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmPageRead+0x167
ffffe086`8db2c700 fffff806`33665274     : 0000007f`00000100 00000000`00000000 ffffe086`8db2c958 fffff806`336661f0 : nt!SmPageRead+0x33
ffffe086`8db2c750 fffff806`33665d4d     : 00000000`00000002 ffffe086`8db2c7e0 ffffe086`8db2c958 ffffa10c`fd971210 : nt!MiIssueHardFaultIo+0x10c
ffffe086`8db2c7a0 fffff806`3361be98     : 00000000`c0033333 00000000`00000001 00000202`5206c728 00000000`00000000 : nt!MiIssueHardFault+0x29d
ffffe086`8db2c860 fffff806`3380dc6d     : ffffa10c`f1caf540 00000000`00000000 00000000`00000000 ffffa10c`f51ad950 : nt!MmAccessFault+0x468
ffffe086`8db2ca00 00007fff`9e96a97a     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x36d
00000096`e3cfeea0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`9e96a97a


SYMBOL_NAME:  nt!ST_STORE<SM_TRAITS>::StDmPageError+10a

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.4522

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  10a

FAILURE_BUCKET_ID:  0x12B_c00002c4_StCtDecompressFailed_nt!ST_STORE_SM_TRAITS_::StDmPageError

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {c6a6bb4d-3b77-dff6-2d9b-75f5d0f61a50}

Followup:     MachineOwner
---------
Windows 商业版 | 面向 IT 专业人士的 Windows 客户端 | 用户体验 | 其他
0 个注释
接受的答案
  1. Wesley Li 11,285 信誉分
    2024-06-19T16:52:12.55+00:00

    您好，
    FAULTY_HARDWARE_CORRUPTED_PAGE (12b) 表示Windows 内存管理器检测到损坏，且这种损坏只能由使用物理寻址访问内存的组件引起。

    物理内存损坏的原因包括：

    • RAM硬件有缺陷。
    • 驱动程序或设备通过不正确的 DMA 操作或关联的 MDL 错误地修改物理页面。
    • 由硬件设备或固件损坏内存导致的损坏，例如固件在电源转换过程中非法修改物理页。

    若要调查此 bug 检查是否是由有缺陷的 RAM 硬件引起的，请运行 Windows 内存诊断工具。在控制面板搜索框中，输入__“内存__”，然后选择“诊断计算机的内存问题”。运行测试后，使用事件查看器查看系统日志下的结果。选择__“MemoryDiagnostics-Results__”条目以查看结果。

    0 个注释

0 个其他答案

排序依据： 非常有帮助
非常有帮助 最新 最早

你的答案

问题作者可以将答案标记为“接受的答案”，这有助于用户了解已解决作者问题的答案。