通过

x64_memory_corruption_large 蓝屏

照阳 李 0 信誉分
2025-10-27T01:24:24.11+00:00

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [D:\云盘\OneDrive\桌面\102625-14921-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRVC:\Symbolshttp://msdl.microsoft.com/download/symbols

Executable search path is:

Windows 7 Kernel Version 26100 MP (16 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Machine Name:

Kernel base = 0xfffff8038aa00000 PsLoadedModuleList = 0xfffff8038b8f4e70

Debug session time: Sun Oct 26 15:53:47.975 2025 (UTC + 8:00)

System Uptime: 0 days 0:01:08.417

Loading Kernel Symbols

...............................................................

................................................................

................................................................

.........................................................

Loading User Symbols

Loading unloaded module list

...........

  •                                                                         *

  •                    Bugcheck Analysis                                    *

  •                                                                         *

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, ff, a, fffff80320a7c170}

Probably caused by : memory_corruption

Followup: memory_corruption

*** Memory manager detected 196736 instance(s) of page corruption, target is likely to have memory corruption.

8: kd> !analyze -v

  •                                                                         *

  •                    Bugcheck Analysis                                    *

  •                                                                         *

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

An attempt was made to access a pageable (or completely invalid) address at an

interrupt request level (IRQL) that is too high. This is usually

caused by drivers using improper addresses.

If kernel debugger is available get stack backtrace.

Arguments:

Arg1: 0000000000000000, memory referenced

Arg2: 00000000000000ff, IRQL

Arg3: 000000000000000a, value 0 = read operation, 1 = write operation

Arg4: fffff80320a7c170, address which referenced memory

Debugging Details:

READ_ADDRESS: unable to get nt!MmSpecialPoolStart

unable to get nt!MmSpecialPoolEnd

unable to get nt!MmPoolCodeStart

unable to get nt!MmPoolCodeEnd

0000000000000000

CURRENT_IRQL: 0

FAULTING_IP:

+3662633363616630

fffff803`20a7c170 0fae39 clflush [rcx]

ADDITIONAL_DEBUG_TEXT: The trap occurred when interrupts are disabled on the target.

BUGCHECK_STR: DISABLED_INTERRUPT_FAULT

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

PROCESS_NAME: svchost.exe

BAD_PAGES_DETECTED: 30080

LAST_CONTROL_TRANSFER: from fffff8038b0b39e9 to fffff8038aef9280

STACK_TEXT:

ffff98829d0af358 fffff8038b0b39e9 : 000000000000000a 0000000000000000 00000000000000ff 000000000000000a : nt!KeBugCheckEx

ffff98829d0af360 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiBugCheckDispatch+0x69

STACK_COMMAND: kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt

fffff8038aef90ca-fffff8038aef90cd  4 bytes - nt!_C_specific_handler+9a

[ ff d0 0f 1f:e8 31 42 6b ]

fffff8038aef91cc-fffff8038aef91cf  4 bytes - nt!_C_specific_handler+19c (+0x102)

[ ff d0 0f 1f:e8 2f 41 6b ]

fffff8038aef9710-fffff8038aef9712  3 bytes - nt!TmInitSystemPhase2 (+0x544)

[ 48 ff 25:4c 8b 15 ]

fffff8038aef9717-fffff8038aef971b  5 bytes - nt!TmInitSystemPhase2+7 (+0x07)

[ cc cc cc cc cc:e9 24 3c 4c 91 ]

fffff8038aef9730-fffff8038aef9732  3 bytes - nt!TmInitSystem (+0x19)

[ 48 ff 25:4c 8b 15 ]

fffff8038aef9737-fffff8038aef973b  5 bytes - nt!TmInitSystem+7 (+0x07)

[ cc cc cc cc cc:e9 44 b9 4d 91 ]

fffff8038aef9750-fffff8038aef9752  3 bytes - nt!NtCommitComplete (+0x19)

[ 48 ff 25:4c 8b 15 ]

fffff8038aef9757-fffff8038aef975b  5 bytes - nt!NtCommitComplete+7 (+0x07)

[ cc cc cc cc cc:e9 54 71 4c 91 ]

fffff8038aef9770-fffff8038aef9772  3 bytes - nt!NtCommitEnlistment (+0x19)

[ 48 ff 25:4c 8b 15 ]

fffff8038aef9777-fffff8038aef977b  5 bytes - nt!NtCommitEnlistment+7 (+0x07)

[ cc cc cc cc cc:e9 04 72 4c 91 ]

fffff8038aef9790-fffff8038aef9792  3 bytes - nt!NtCommitTransaction (+0x19)

[ 48 ff 25:4c 8b 15 ]

fffff8038aef9797-fffff8038aef979b  5 bytes - nt!NtCommitTransaction+7 (+0x07)

[ cc cc cc cc cc:e9 24 2d 4d 91 ]

fffff8038aef97b0-fffff8038aef97b2  3 bytes - nt!NtCreateEnlistment (+0x19)

[ 48 ff 25:4c 8b 15 ]

fffff8038aef97b7-fffff8038aef97bb  5 bytes - nt!NtCreateEnlistment+7 (+0x07)

[ cc cc cc cc cc:e9 24 6f 4d 91 ]

fffff8038aef97d0-fffff8038aef97d2  3 bytes - nt!NtCreateResourceManager (+0x19)

[ 48 ff 25:4c 8b 15 ]

fffff8038aef97d7-fffff8038aef97db  5 bytes - nt!NtCreateResourceManager+7 (+0x07)

[ cc cc cc cc cc:e9 34 8a 4d 91 ]

fffff8038aef97f0-fffff8038aef97f2  3 bytes - nt!NtCreateTransaction (+0x19)

[ 48 ff 25:4c 8b 15 ]

fffff8038aef97f7-fffff8038aef97fb  5 bytes - nt!NtCreateTransaction+7 (+0x07)

[ cc cc cc cc cc:e9 24 d1 4c 91 ]

fffff8038aef9810-fffff8038aef9812  3 bytes - nt!NtCreateTransactionManager (+0x19)

[ 48 ff 25:4c 8b 15 ]

fffff8038aef9817-fffff8038aef981b  5 bytes - nt!NtCreateTransactionManager+7 (+0x07)

[ cc cc cc cc cc:e9 f4 d8 4c 91 ]

fffff8038aef9830-fffff8038aef9832  3 bytes - nt!NtEnumerateTransactionObject (+0x19)

[ 48 ff 25:4c 8b 15 ]

fffff8038aef9837-fffff8038aef983b  5 bytes - nt!NtEnumerateTransactionObject+7 (+0x07)

[ cc cc cc cc cc:e9 b4 9c 4c 91 ]

fffff8038aef9850-fffff8038aef9852  3 bytes - nt!NtFreezeTransactions (+0x19)

[ 48 ff 25:4c 8b 15 ]

fffff8038aef9857-fffff8038aef985b  5 bytes - nt!NtFreezeTransactions+7 (+0x07)

[ cc cc cc cc cc:e9 e4 9e 4c 91 ]

fffff8038aef9870-fffff8038aef9872  3 bytes - nt!NtGetNotificationResourceManager (+0x19)

[ 48 ff 25:4c 8b 15 ]

fffff8038aef9877-fffff8038aef987b  5 bytes - nt!NtGetNotificationResourceManager+7 (+0x07)

[ cc cc cc cc cc:e9 e4 80 4c 91 ]

fffff8038aef9890-fffff8038aef9892  3 bytes - nt!NtOpenEnlistment (+0x19)

[ 48 ff 25:4c 8b 15 ]

fffff8038aef9897-fffff8038aef989b  5 bytes - nt!NtOpenEnlistment+7 (+0x07)

[ cc cc cc cc cc:e9 b4 71 4c 91 ]

fffff8038aef98b0-fffff8038aef98b2  3 bytes - nt!NtOpenResourceManager (+0x19)

[ 48 ff 25:4c 8b 15 ]

fffff8038aef98b7-fffff8038aef98bb  5 bytes - nt!NtOpenResourceManager+7 (+0x07)

[ cc cc cc cc cc:e9 24 82 4c 91 ]

fffff8038aef98d0-fffff8038aef98d2  3 bytes - nt!NtOpenTransaction (+0x19)

[ 48 ff 25:4c 8b 15 ]

fffff8038aef98d7-fffff8038aef98db  5 bytes - nt!NtOpenTransaction+7 (+0x07)

[ cc cc cc cc cc:e9 44 9f 4c 91 ]

fffff8038aef98f0-fffff8038aef98f2  3 bytes - nt!NtOpenTransactionManager (+0x19)

[ 48 ff 25:4c 8b 15 ]

fffff8038aef98f7-fffff8038aef98fb  5 bytes - nt!NtOpenTransactionManager+7 (+0x07)

[ cc cc cc cc cc:e9 d4 a5 4c 91 ]

fffff8038aef9910-fffff8038aef9912  3 bytes - nt!NtPrePrepareComplete (+0x19)

[ 48 ff 25:4c 8b 15 ]

fffff8038aef9917-fffff8038aef991b  5 bytes - nt!NtPrePrepareComplete+7 (+0x07)

[ cc cc cc cc cc:e9 74 73 4c 91 ]

fffff8038aef9930-fffff8038aef9932  3 bytes - nt!NtPrePrepareEnlistment (+0x19)

[ 48 ff 25:4c 8b 15 ]

fffff8038aef9937-fffff8038aef993b  5 bytes - nt!NtPrePrepareEnlistment+7 (+0x07)

[ cc cc cc cc cc:e9 94 74 4c 91 ]

fffff8038aef9950-fffff8038aef9952  3 bytes - nt!NtPrepareComplete (+0x19)

[ 48 ff 25:4c 8b 15 ]

fffff8038aef9957-fffff8038aef995b  5 bytes - nt!NtPrepareComplete+7 (+0x07)

[ cc cc cc cc cc:e9 44 75 4c 91 ]

fffff8038aef9970-fffff8038aef9972  3 bytes - nt!NtPrepareEnlistment (+0x19)

[ 48 ff 25:4c 8b 15 ]

fffff8038aef9977-fffff8038aef997b  5 bytes - nt!NtPrepareEnlistment+7 (+0x07)

[ cc cc cc cc cc:e9 64 76 4c 91 ]

fffff8038aef9990-fffff8038aef9992  3 bytes - nt!NtPropagationComplete (+0x19)

[ 48 ff 25:4c 8b 15 ]

fffff8038aef9997-fffff8038aef999b  5 bytes - nt!NtPropagationComplete+7 (+0x07)

[ cc cc cc cc cc:e9 34 ac 4c 91 ]

fffff8038aef99b0-fffff8038aef99b2  3 bytes - nt!NtPropagationFailed (+0x19)

[ 48 ff 25:4c 8b 15 ]

fffff8038aef99b7-fffff8038aef99bb  5 bytes - nt!NtPropagationFailed+7 (+0x07)

[ cc cc cc cc cc:e9 24 ad 4c 91 ]

fffff8038aef99d0-fffff8038aef99d2  3 bytes - nt!NtQueryInformationEnlistment (+0x19)

[ 48 ff 25:4c 8b 15 ]

fffff8038aef99d7-fffff8038aef99db  5 bytes - nt!NtQueryInformationEnlistment+7 (+0x07)

[ cc cc cc cc cc:e9 d4 76 4c 91 ]

fffff8038aef99f0-fffff8038aef99f2  3 bytes - nt!NtQueryInformationResourceManager (+0x19)

[ 48 ff 25:4c 8b 15 ]

fffff8038aef99f7-fffff8038aef99fb  5 bytes - nt!NtQueryInformationResourceManager+7 (+0x07)

[ cc cc cc cc cc:e9 f4 82 4c 91 ]

WARNING: !chkimg output was truncated to 50 lines. Invoke !chkimg without '-lo [num_lines]' to view entire output.

584 errors : !nt (fffff8038aef90ca-fffff8038aef9ffb)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: LARGE

FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE

BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE

Followup: memory_corruption

*** Memory manager detected 196736 instance(s) of page corruption, target is likely to have memory corruption.

8: kd> lmvm memory_corruption

start end module name

8: kd> lmvm memory_corruption

start end module name

8: kd> !chkimg

584 errors : @rip (fffff8038aef90ca-fffff8038aef9ffb)

8: kd> lmvm memory_corruption

start end module name

Windows 家庭版 | Windows 11 | 性能和系统故障
0 个注释

2 个答案

排序依据： 非常有帮助
非常有帮助 最新 最早
  1. Lester Bernard Reyes 63,710 信誉分 独立顾问
    2025-10-27T03:40:38.2666667+00:00

    您好，我是 Bernard，也是一位 Windows 用户。很高兴能为您提供帮助！

    ​​

    我了解您遇到的问题，请不用担心，我会尽力协助您。经过分析和检查 DMP 日志，我发现您遇到的错误是内存损坏（memory_corruption），这意味着您的电脑内存（RAM）本身或主板上的内存插槽存在问题。在这种情况下，可能是第三方服务导致的内存泄漏，也可能是硬件相关的问题。为了排除任何软件问题，请按照以下步骤操作：

    方法 1：执行干净启动：

    “干净启动”会以最少的驱动程序和启动程序启动 Windows，以便您确定是否有后台程序干扰了您的游戏或程序。

    • 在任务栏的搜索框中输入 msconfig，然后从结果中选择“系统配置”。
    • 在“系统配置”的“服务”选项卡上，选择“隐藏所有 Microsoft 服务”，然后选择“全部禁用”。
    • 在“系统配置”的“启动”选项卡上，选择“打开任务管理器”。
    • 在任务管理器的“启动”选项卡下，选择每个启动项，然后选择“禁用”。
    • 关闭任务管理器。
    • 在“系统配置”的“启动”选项卡上，选择“确定”。重新启动计算机后，它将处于干净启动环境中。

    故障排除参考：https://support.microsoft.com/zh-cn/topic/%E5%A6%82%E4%BD%95%E5%9C%A8-windows-%E4%B8%AD%E6%89%A7%E8%A1%8C%E5%B9%B2%E5%87%80%E5%90%AF%E5%8A%A8-da2f9573-6eec-00ad-2f8a-a97a1807f3dd

    方法 2：运行内存诊断工具：内存诊断工具是一个 RAM 测试工具，用于检查是否存在任何 RAM 问题。

    • 按下 Windows 键 + R，然后输入 mdsched.exe 并点击“确定”，然后重启设备。

    注意：如果问题仍然存在，我强烈建议您联系当地的技术人员对设备进行物理检查，因为这可能是硬件问题，可能需要更换内存条，或者只需要清洁主板。另一种方法是尝试移除每根内存条并测试是否可以正常工作。如果可以，则说明您移除的内存条有问题。

    1 个人认为此答案很有帮助。
  2. Lester Bernard Reyes 63,710 信誉分 独立顾问
    2025-10-28T15:11:45.85+00:00

    您好，感谢您提供这些信息。在这种情况下，我建议您联系当地的技术人员，让他们对设备进行实地检查，以排除任何与硬件相关的问题，特别是主板方面的问题。

    0 个注释

你的答案

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