你好，最近用windows11玩CS2，进游戏没问题，但是一玩起来就会自动黑屏重启。

匿名
2024-06-09T16:14:40+00:00

我查了一下事件产查看器，发 现出现以下错误

Windows 家庭版 | Windows 11 | 性能和系统故障

锁定的问题。 此问题已从 Microsoft 支持社区迁移。 你可投票决定它是否有用，但不能添加评论或回复，也不能关注问题。

0 个注释

49 个答案

排序依据： 最早
非常有帮助 最新 最早
  1. 匿名
    2024-06-11T15:54:53+00:00

    我们使用翻译服务协助我们的用户。请原谅语法错误。

    单击 analyze –v 后，该窗口中应该会有更多的文本

    ************* 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:\Users\admin\Desktop\060724-12046-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 22621 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 22621.1.amd64fre.ni_release.220506-1250
Kernel base = 0xfffff802`80e00000 PsLoadedModuleList = 0xfffff802`81a13530
Debug session time: Fri Jun  7 22:39:48.629 2024 (UTC + 8:00)
System Uptime: 0 days 0:52:17.226
Loading Kernel Symbols
...............................................................
................................................................
................................................................
............
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000a8`f0236018).  Type ".hh dbgerr001" for details
Loading unloaded module list
.................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`812177f0 48894c2408      mov     qword ptr [rsp+8],rcx ss:ffff9101`37db4940=0000000000000124
10: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffdc875cc47028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000fc800800, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000060c0859, Low order 32-bits of the MCi_STATUS value.

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: hal!_WHEA_MEMORY_ERROR_SECTION                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: hal!_WHEA_MEMORY_ERROR_SECTION                ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 359

    Key  : Analysis.Elapsed.mSec
    Value: 22554

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x124

    Key  : Bugcheck.Code.TargetModel
    Value: 0x124

    Key  : Failure.Bucket
    Value: 0x124_0_AuthenticAMD_MEMORY__UNKNOWN_FATAL_IMAGE_AuthenticAMD.sys

    Key  : Failure.Hash
    Value: {b0905187-9dbc-d607-4dc5-8630b9eddb7f}

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Version
    Value: 10.0.22621.1

BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffdc875cc47028

BUGCHECK_P3: fc800800

BUGCHECK_P4: 60c0859

FILE_IN_CAB:  060724-12046-01.dmp

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  cs2.exe

STACK_TEXT:  
ffff9101`37db4938 fffff802`812ff80b     : 00000000`00000124 00000000`00000000 ffffdc87`5cc47028 00000000`fc800800 : nt!KeBugCheckEx
ffff9101`37db4940 fffff802`809310c0     : 00000000`00000000 ffff9101`37db4a19 ffffdc87`5cc47028 ffffdc87`563f12f0 : nt!HalBugCheckSystem+0xeb
ffff9101`37db4980 fffff802`8140ed3f     : 00000000`00000000 ffff9101`37db4a19 ffffdc87`5cc47028 ffffbf00`e088d9c8 : PSHED!PshedBugCheckSystem+0x10
ffff9101`37db49b0 fffff802`8130123a     : ffffdc87`5c654900 ffffdc87`5c654900 ffffdc87`563f1340 fffff802`8117df3e : nt!WheaReportHwError+0x38f
ffff9101`37db4a80 fffff802`81301690     : 00000000`0000000a ffffdc87`00000000 00000000`00000000 00000000`00000000 : nt!HalpMcaReportError+0xb2
ffff9101`37db4bf0 fffff802`81301524     : ffffdc87`56374780 ffffffff`00000000 ffff9101`37db4e00 ffffbf00`00000000 : nt!HalpMceHandlerCore+0x138
ffff9101`37db4c50 fffff802`813009b7     : ffffdc87`56374780 ffff9101`37db4ef0 00000000`00000000 ffffbf00`e088dca8 : nt!HalpMceHandler+0xe0
ffff9101`37db4c90 fffff802`8130314b     : ffffdc87`56374780 ffffbf00`e088dcc8 ffffbf00`e088dcc8 ffffffff`00000000 : nt!HalpHandleMachineCheck+0x97
ffff9101`37db4cc0 fffff802`81369769     : ffffbf00`e088dce8 ffffffff`00000000 00000000`00000000 ffffbf00`e088dd08 : nt!HalHandleMcheck+0x3b
ffff9101`37db4cf0 fffff802`8122997e     : 00000000`00000000 ffffbf00`e088dd28 ffffbf00`e088dd28 ffffffff`00000000 : nt!KiHandleMcheck+0x9
ffff9101`37db4d20 fffff802`81229593     : 00000000`00000000 00000000`00000000 00000260`75b42690 ffff9101`37db4ef0 : nt!KxMcheckAbort+0x7e
ffff9101`37db4e60 00007ff9`283f2a9a     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x2d3
000000a8`f097f900 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`283f2a9a

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0x124_0_AuthenticAMD_MEMORY__UNKNOWN_FATAL_IMAGE_AuthenticAMD.sys

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {b0905187-9dbc-d607-4dc5-8630b9eddb7f}

Followup:     MachineOwner
---------

    此答案是否有帮助?

    0 个注释
  2. 匿名
    2024-06-11T15:56:40+00:00

    您的 minidump 文件表明与您的处理器相关的驱动程序导致您的 PC 崩溃。

    转到制造商网站上您的 PC 或主板的支持页面，然后从那里下载并安装他们推荐的芯片组驱动程序版本，如果您的驱动器没有使用 Bitlocker 加密，请检查可能需要安装的任何 BIOS 更新

    此答案是否有帮助?

    0 个注释
  3. 匿名
    2024-06-11T16:03:46+00:00

    您的 minidump 文件表明与您的处理器相关的驱动程序导致您的 PC 崩溃。

    转到制造商网站上您的 PC 或主板的支持页面，然后从那里下载并安装他们推荐的芯片组驱动程序版本，如果您的驱动器没有使用 Bitlocker 加密，请检查可能需要安装的任何 BIOS 更新

    我的电脑是微星主板MSI，请问你的意思是，要我更新主板的BIOS是吗？

    此答案是否有帮助?

    0 个注释
  4. 匿名
    2024-06-11T16:05:40+00:00

    我们使用翻译服务协助我们的用户。请原谅语法错误。

    是的，这是正确的，如果您没有使用 Bitlocker 加密驱动器，请查看 MSI 网站以查找是否有任何可能需要安装的可用 BIOS udpate，并从该 MSI 网站重新安装芯片组驱动程序。

    此答案是否有帮助?

    0 个注释
  5. 匿名
    2024-06-11T16:11:59+00:00

    我们使用翻译服务协助我们的用户。请原谅语法错误。

    是的，这是正确的，如果您没有使用 Bitlocker 加密驱动器，请查看 MSI 网站以查找是否有任何可能需要安装的可用 BIOS udpate，并从该 MSI 网站重新安装芯片组驱动程序。

    非常感谢，我按照你的方式我尝试一下，很感谢，打扰你休息了，你很专业，也很棒，谢谢你我的朋友

    此答案是否有帮助?

    0 个注释