電腦進行遊戲一直當機重開(附上DMP資訊)

匿名
2025-03-04T12:38:00+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.046 seconds

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

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.188 seconds

----> Repository : UserExtensions, Enabled: true, Packages count: 0

----> Repository : LocalInstalled, Enabled: true, Packages count: 29

Microsoft (R) Windows Debugger Version 10.0.26100.3037 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\***\OneDrive\桌面\030425-15609-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 26100 MP (6 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Kernel base = 0xfffff804f0e00000 PsLoadedModuleList = 0xfffff804f1cf4770

Debug session time: Tue Mar 4 20:13:15.752 2025 (UTC + 8:00)

System Uptime: 0 days 0:12:54.459

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

3: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

MACHINE_CHECK_EXCEPTION (9c)

A fatal Machine Check Exception has occurred.

KeBugCheckEx parameters;

x86 Processors

    If the processor has ONLY MCE feature available (For example Intel

    Pentium), the parameters are:

    1 - Low  32 bits of P5\_MC\_TYPE MSR

    2 - Address of MCA\_EXCEPTION structure

    3 - High 32 bits of P5\_MC\_ADDR MSR

    4 - Low  32 bits of P5\_MC\_ADDR MSR

    If the processor also has MCA feature available (For example Intel

    Pentium Pro), the parameters are:

    1 - Bank number

    2 - Address of MCA\_EXCEPTION structure

    3 - High 32 bits of MCi\_STATUS MSR for the MCA bank that had the error

    4 - Low  32 bits of MCi\_STATUS MSR for the MCA bank that had the error

IA64 Processors

    1 - BugCheck Type

        1 - MCA\_ASSERT

        2 - MCA\_GET\_STATEINFO

            SAL returned an error for SAL\_GET\_STATEINFO while processing MCA.

        3 - MCA\_CLEAR\_STATEINFO

            SAL returned an error for SAL\_CLEAR\_STATEINFO while processing MCA.

        4 - MCA\_FATAL

            FW reported a fatal MCA.

        5 - MCA\_NONFATAL

            SAL reported a recoverable MCA and we don't support currently

            support recovery or SAL generated an MCA and then couldn't

            produce an error record.

        0xB - INIT\_ASSERT

        0xC - INIT\_GET\_STATEINFO

              SAL returned an error for SAL\_GET\_STATEINFO while processing INIT event.

        0xD - INIT\_CLEAR\_STATEINFO

              SAL returned an error for SAL\_CLEAR\_STATEINFO while processing INIT event.

        0xE - INIT\_FATAL

              Not used.

    2 - Address of log

    3 - Size of log

    4 - Error code in the case of x\_GET\_STATEINFO or x\_CLEAR\_STATEINFO

AMD64 Processors (If Param 1 is < 0x80000000)

    1 - Bank number

    2 - Address of MCA\_EXCEPTION structure

    3 - High 32 bits of MCi\_STATUS MSR for the MCA bank that had the error

    4 - Low  32 bits of MCi\_STATUS MSR for the MCA bank that had the error

AMD64 Processors (If Param 1 is > 0x80000000)

    1 - Failure Type

       VALUES:

            0x80000001: Spurious MCE

                2 - Address of MCA\_EXCEPTION structure

            0x80000002: Rendezvous failure

                2 - Address of MCA\_EXCEPTION structure

       END\_VALUES

Arguments:

Arg1: 0000000080000001

Arg2: ffffce8002bd8b00

Arg3: 0000000000000000

Arg4: 0000000000000000

Debugging Details:


KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec

Value: 3515

Key  : Analysis.Elapsed.mSec

Value: 11166

Key  : Analysis.IO.Other.Mb

Value: 6

Key  : Analysis.IO.Read.Mb

Value: 1

Key  : Analysis.IO.Write.Mb

Value: 24

Key  : Analysis.Init.CPU.mSec

Value: 16108

Key  : Analysis.Init.Elapsed.mSec

Value: 571001

Key  : Analysis.Memory.CommitPeak.Mb

Value: 99

Key  : Bugcheck.Code.LegacyAPI

Value: 0x9c

Key  : Dump.Attributes.AsUlong

Value: 1008

Key  : Dump.Attributes.DiagDataWrittenToHeader

Value: 1

Key  : Dump.Attributes.ErrorCode

Value: 0

Key  : Dump.Attributes.KernelGeneratedTriageDump

Value: 1

Key  : Dump.Attributes.LastLine

Value: Dump completed successfully.

Key  : Dump.Attributes.ProgressPercentage

Value: 0

Key  : Failure.Bucket

Value: 0x9C\_SPURIOUS\_GenuineIntel\_intelppm!MWaitIdle

Key  : Failure.Hash

Value: {1132fd1e-b4e3-34d7-1215-2712eb51da30}

BUGCHECK_CODE: 9c

BUGCHECK_P1: 80000001

BUGCHECK_P2: ffffce8002bd8b00

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FILE_IN_CAB: 030425-15609-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008

Kernel Generated Triage Dump

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:

ffffce8002bd8ac8 fffff804f12fc728 : 000000000000009c 0000000080000001 ffffce8002bd8b00 0000000000000000 : nt!KeBugCheckEx

ffffce8002bd8ad0 fffff804f12fcbcc : 0000000000000006 ffffce8002bd8e50 0000000000000000 0fc085c933000012 : nt!HalpMcaReportError+0x154

ffffce8002bd8c40 fffff804f12fbd25 : 0000000000000000 0000000080000001 ffffce8002bd8ed0 05c70000441f0fff : nt!HalpMceHandlerWithRendezvous+0x11c

ffffce8002bd8c70 fffff804f12ff5db : ffffce8002bd8e40 8b4cffffff64820f 5d2ee8ed3345f075 0f4140578b48000c : nt!HalpHandleMachineCheck+0x8d

ffffce8002bd8ca0 fffff804f1375a49 : 0000000000000000 0000000000000000 0753840fd28548b0 0000000000000000 : nt!HalHandleMcheck+0x6b

ffffce8002bd8cd0 fffff804f148937e : 01441184c7d70345 cdebfe5600000000 41c58b45404f8b4c 3b4128518b45d58b : nt!KiHandleMcheck+0x9

ffffce8002bd8d00 fffff804f1488f99 : 0000000000000010 0000000000000000 0f60016c39443041 0000000000000000 : nt!KxMcheckAbort+0x7e

ffffce8002bd8e40 fffff80497ca81ae : fffff80497ca3c03 00000001cdc60e4a ffffde87c3c8f9e0 ffff045f3ac9518c : nt!KiMcheckAbort+0x2d9

ffffde87c3c8f8a8 fffff80497ca3c03 : 00000001cdc60e4a ffffde87c3c8f9e0 ffff045f3ac9518c 0000000000000000 : intelppm!MWaitIdle+0x2e

ffffde87c3c8f8b0 fffff804f1209d77 : 00000000ffffffff ffffde87c3c8f9e0 ffff9d0f80567000 ffffce8002ba4180 : intelppm!AcpiCStateIdleExecute+0x23

ffffde87c3c8f8e0 fffff804f1208b07 : ffff9d0f80567000 ffff9d0f80567000 ffffde87c3c8fad9 ffffce8002ba4180 : nt!PpmIdleExecuteTransition+0x5ab

ffffde87c3c8fa70 fffff804f1479e94 : ffffce8002ba4180 ffffce8002ba4100 0000000000000000 0000eb850f504700 : nt!PoIdle+0x187

ffffde87c3c8fb40 0000000000000000 : ffffde87c3c90000 ffffde87c3c89000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x54

SYMBOL_NAME: intelppm!MWaitIdle+2e

MODULE_NAME: intelppm

IMAGE_NAME: intelppm.sys

IMAGE_VERSION: 10.0.26100.3037

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 2e

FAILURE_BUCKET_ID: 0x9C_SPURIOUS_GenuineIntel_intelppm!MWaitIdle

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {1132fd1e-b4e3-34d7-1215-2712eb51da30}

Followup: MachineOwner


***版主刪除的個人資訊。 請參閱Microsoft 社群,瞭解有關如何保護隱私的詳細資訊***

適用於首頁的 Windows | Windows 11 | 效能和系統失敗

鎖定的問題。 此問題已從 Microsoft 支援服務社群移轉。 您可以對其是否有幫助進行投票,但無法對問題新增註解或回覆,或進行追蹤。

0 則留言 沒有留言
{count} 則投票

1 個回答

排序依據: 最實用
  1. 匿名
    2025-03-05T08:17:40+00:00

    宥豪林 您好,歡迎您諮詢微軟社區

    理解您的情況,根據提供的資訊欄,特定的藍色畫面錯誤是MACHINE_CHECK_EXCEPTION (9c),這是一個致命的硬體錯誤,表示處理器偵測到硬體問題並觸發了機器檢查異常。這通常與硬體故障有關,例如 CPU、記憶體、主機板或電源問題。但這裡 Arg1 顯示這是一個「Spurious MCE」(偽異常),可能是硬體錯誤訊號被錯誤觸發,或是驅動程式與硬體互動時的問題。  堆疊中的關鍵點在這裡:崩潰發生在此驅動模組中,intelppm.sys 是 Intel 的電源管理驅動,它負責管理CPU的功勞調節。和intelppm!MWaitIdle+0x2e一起出現的有nt!KiIdleLoop+0x54它們通常指示處理器電源管理或空閒處理邏輯中存在問題。這些問題可能由驅動程式錯誤、硬體故障、系統更新不相容或配置錯誤引起。intelppm.sys 是 Intel 的電源管理驅動,負責處理 CPU 的節能狀態(C-States)。崩潰發生在 MWaitIdle 函數中,這通常與 CPU 使用 MWAIT 指令進入低功耗模式有關。結合 Spurious MCE,可能是驅動與硬體的兼容性問題,或硬體本身對 MWAIT 指令的回應異常。初步分析可能是硬體(CPU/主機板)、驅動、韌體或電源(過熱/不穩定)問題。現階段的建議:步驟一:確保系統更新,存取硬體製造商官網取得電源管理驅動和晶片組驅動並完成更新,同時更新 BIOS/UEFI韌體,並進入BIOS,在 BIOS 中關閉 CPU C-States,啟動遊戲,看是否還藍屏。免責聲明: 微軟不提供任何暗示或其他保證和/或保證,對您從第三方連結網站獲得的資訊或任何與技術相關的支援不負責。若您仍將嘗試修改BIOS設置,請先備份好重要的資料。步驟二:執行下載硬體製造商提供的工具檢查 CPU 健康狀況。如果沒有偵測到問題,可以考慮監控核心狀態,使用硬體監控工具觀察遊戲載入時各核心的負載,看是否有核心進入空閒。步驟三:測試其他場景,執行 CPU 壓力測試,檢查是否也會觸發類似藍色畫面。如果是,則可能是硬體問題。

    Best Wish

    Leo Z | 微軟社群支援

    0 則留言 沒有留言