最近电脑时常蓝屏蓝屏时显示终止代码为:MACHINE_CHECK_EXCEPTION,重启电脑又能正常使用,但是使用一段时间后,又开始蓝屏,终止代码还是:MACHINE_CHECK_EXCEPTION。已获取到蓝屏时的dmp文件内容如下: Microsoft (R) Windows Debugger Version 10.0.19041.1 X86 Copyright (c) Microsoft Corporation. All rights reserved.   Loading Dump File [C:\Users\zhangxy\Documents\WeChat Files\wxid_viyjottk8kzd11\FileStorage\File\2022-10\102522-9843-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 17763 MP (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0xfffff806`742b0000 PsLoadedModuleList = 0xfffff806`746c9710 Debug session time: Tue Oct 25 13:30:53.542 2022 (UTC + 8:00) System Uptime: 0 days 0:13:08.296 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                                    * *                                                                             * *******************************************************************************  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: 0000000000000000 Arg2: fffff8067668eb20 Arg3: 0000000000000000 Arg4: 0000000000000000  Debugging Details: ------------------   KEY_VALUES_STRING: 1      Key  : Analysis.CPU.Sec     Value: 3      Key  : Analysis.DebugAnalysisProvider.CPP     Value: Create: 8007007e on DESKTOP-NOAKA77      Key  : Analysis.DebugData     Value: CreateObject      Key  : Analysis.DebugModel     Value: CreateObject      Key  : Analysis.Elapsed.Sec     Value: 3      Key  : Analysis.Memory.CommitPeak.Mb     Value: 95      Key  : Analysis.System     Value: CreateObject   DUMP_FILE_ATTRIBUTES: 0x8   Kernel Generated Triage Dump  BUGCHECK_CODE:  9c  BUGCHECK_P1: 0  BUGCHECK_P2: fffff8067668eb20  BUGCHECK_P3: 0  BUGCHECK_P4: 0  BLACKBOXPNP: 1 (!blackboxpnp)   CUSTOMER_CRASH_COUNT:  1  PROCESS_NAME:  System  BAD_STACK_POINTER:  fffff8067668eae8  STACK_TEXT:   fffff806`7668eae8 fffff806`7425777f : 00000000`0000009c 00000000`00000000 fffff806`7668eb20 00000000`00000000 : nt!KeBugCheckEx fffff806`7668eaf0 fffff806`74257bf1 : 00000000`00000006 fffff806`7668ee50 00000000`00000000 00000000`00000006 : hal!HalpMcaReportError+0x113 fffff806`7668ec40 fffff806`74256e0c : 00000000`00000000 fffff806`7668eed0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x131 fffff806`7668ec70 fffff806`74257e37 : ffff9c0e`90e8f980 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpHandleMachineCheck+0x5c fffff806`7668eca0 fffff806`7453a0e0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x37 fffff806`7668ecd0 fffff806`744753fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x10 fffff806`7668ed00 fffff806`744750a3 : fffff806`00000000 fffff806`74474fe0 fffff806`73148180 00000000`00000000 : nt!KxMcheckAbort+0x7a fffff806`7668ee40 fffff806`8303136f : fffff806`83031404 00000000`00000000 ffff9c0e`953ac0f0 fffff806`73148180 : nt!KiMcheckAbort+0x263 fffff806`766796a8 fffff806`83031404 : 00000000`00000000 ffff9c0e`953ac0f0 fffff806`73148180 ffff9c0e`953ac000 : intelppm!MWaitIdle+0x1f fffff806`766796b0 fffff806`743651ab : 00000000`00000000 ffff9c0e`00000086 00000000`00000000 00000000`00000204 : intelppm!AcpiCStateIdleExecute+0x24 fffff806`766796e0 fffff806`7436495f : 00000000`00000000 00000000`00000002 00000000`00000002 00000000`00000008 : nt!PpmIdleExecuteTransition+0x6bb fffff806`76679a00 fffff806`7446a37c : 00000000`00000000 fffff806`73148180 00000000`00000000 fffff806`7480e400 : nt!PoIdle+0x33f fffff806`76679b60 00000000`00000000 : fffff806`7667a000 fffff806`76673000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c   SYMBOL_NAME:  intelppm!MWaitIdle+1f  MODULE_NAME: intelppm  IMAGE_NAME:  intelppm.sys  IMAGE_VERSION:  10.0.17763.503  STACK_COMMAND:  .thread ; .cxr ; kb  BUCKET_ID_FUNC_OFFSET:  1f  FAILURE_BUCKET_ID:  0x9C_GenuineIntel_STACKPTR_ERROR_intelppm!MWaitIdle  OSPLATFORM_TYPE:  x64  OSNAME:  Windows 10  FAILURE_ID_HASH:  {d82f1232-e6fd-ac41-d01e-ddeec73b684b}  Followup:     MachineOwner ---------      欢迎访问本站!。显示英特尔相关的硬件错误。若是有超频,降压等,建议恢复正常,xmp也关闭。然后到电脑品牌的官网更新一下bios,覆盖安装一下芯片组驱动,英特尔快速存储技术驱动,请勿使用第三方的驱动安装程序。(bios中若是有cpu节能功能,建议关闭一下。)然后在任务栏搜索框输入注册表打开(修改注册表有风险,请先备份https://support.microsoft.com/zh-cn/topic/%E5%A.)进入HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\intelppm双击右侧的Start更改数值数据为4然后执行一下干净启动,排除其他干扰:https://support.microsoft.com/zh-cn/help/929135.先卸载设备中全部的第三方反病毒软件与系统优化软件(例如360、联想电脑管家、360桌面、腾讯电脑管家、腾讯桌面、鲁大师,代理,加速器,虚拟机等)。然后鼠标右键单击开始菜单→运行(RUN)→输入:msconfig(按下Enter键)点击上面的“服务”勾选下面的“隐藏所有Microsoft服务”(请务必勾选)点击“全部禁用”。然后鼠标右键单击开始菜单→任务管理器,(点击底部“详细信息”),点击顶部”启动”,鼠标右键单击“状态”显示为“已启动”的项,选择“禁用”。(禁用所有启动项。)然后鼠标右键单击开始按钮(图标的按钮)→"WindowsPowerShell(I)(管理员)(A)”→输入:(WIndows11中可能显示Windows终端(管理员))sfc/SCANNOW(按下Enter键)Dism/Online/Cleanup-Image/ScanHealth(按下Enter键)Dism/Online/Cleanup-Image/CheckHealth(按下Enter键)DISM/Online/Cleanup-image/RestoreHealth(按下Enter键)完成后重启电脑,再次输入:sfc/SCANNOW(按下Enter键)看下是否有改善。

点赞(31) 打赏

微信小程序

微信扫一扫体验

立即
投稿

微信公众账号

微信扫一扫加关注

发表
评论
返回
顶部