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

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

匿名
乐意效劳！
0 个注释
匿名
乐意效劳！
昨天更新bios以后，用csGO测试了一下，会突然花屏
0 个注释
匿名
我们使用翻译服务协助我们的用户。请原谅语法错误。
请检查您的系统上是否创建了任何新的小型转储文件。
0 个注释
匿名
我们使用翻译服务协助我们的用户。请原谅语法错误。

请检查您的系统上是否创建了任何新的小型转储文件。
我装了最新的测试版BIOS。
************* 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.032 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\061224-14984-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 22621 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff802`0ea00000 PsLoadedModuleList = 0xfffff802`0f613530
Debug session time: Wed Jun 12 01:16:36.955 2024 (UTC + 8:00)
System Uptime: 0 days 0:25:23.623
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
PEB is paged out (Peb.Ldr = 000000a0`86546018).  Type ".hh dbgerr001" for details
Loading unloaded module list
...........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`0ee177f0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffff8301`fcc6c940=0000000000000124
11: 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: ffffc88391402028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000bc800800, 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: 2249

    Key  : Analysis.Elapsed.mSec
    Value: 49402

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x124

    Key  : Bugcheck.Code.TargetModel
    Value: 0x124

    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: 0x124_0_AuthenticAMD_MEMORY__UNKNOWN_FATAL_IMAGE_AuthenticAMD.sys

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

BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffc88391402028

BUGCHECK_P3: bc800800

BUGCHECK_P4: 60c0859

FILE_IN_CAB:  061224-14984-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
  Kernel Generated Triage Dump

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  cs2.exe

STACK_TEXT:  
ffff8301`fcc6c938 fffff802`0eeff80b     : 00000000`00000124 00000000`00000000 ffffc883`91402028 00000000`bc800800 : nt!KeBugCheckEx
ffff8301`fcc6c940 fffff802`0c3710c0     : 00000000`00000000 ffff8301`fcc6ca19 ffffc883`91402028 ffffc883`8bdf3480 : nt!HalBugCheckSystem+0xeb
ffff8301`fcc6c980 fffff802`0f00ed3f     : 00000000`00000000 ffff8301`fcc6ca19 ffffc883`91402028 d8082b1b`d4482b1f : PSHED!PshedBugCheckSystem+0x10
ffff8301`fcc6c9b0 fffff802`0ef0123a     : ffffc883`957478e0 ffffc883`957478e0 ffffc883`8bdf34d0 fffff802`0ed7df3e : nt!WheaReportHwError+0x38f
ffff8301`fcc6ca80 fffff802`0ef01690     : 00000000`0000000b ffffc883`00000005 ffff8000`00000000 ffffffff`ffffffff : nt!HalpMcaReportError+0xb2
ffff8301`fcc6cbf0 fffff802`0ef01524     : ffffc883`8bcde840 1a201c28`00000000 ffff8301`fcc6ce00 be1f3046`0000000d : nt!HalpMceHandlerCore+0x138
ffff8301`fcc6cc50 fffff802`0ef009b7     : ffffc883`8bcde840 ffff8301`fcc6cef0 00000000`00000000 9cbd320f`90fd3203 : nt!HalpMceHandler+0xe0
ffff8301`fcc6cc90 fffff802`0ef0314b     : ffffc883`8bcde840 18ba3b83`14fa3baf 1bb28c89`17f28c8d 20821e09`2cc21e2d : nt!HalpHandleMachineCheck+0x97
ffff8301`fcc6ccc0 fffff802`0ef69769     : 87b5850d`8bf58561 bc8517c5`b0c517c1 0128abca`0d68abce 3a18396a`3658396e : nt!HalHandleMcheck+0x3b
ffff8301`fcc6ccf0 fffff802`0ee2997e     : 9d2fa226`916fa222 a61f3086`aa5f3082 a51787a4`a95787a0 9e271504`92671500 : nt!KiHandleMcheck+0x9
ffff8301`fcc6cd20 fffff802`0ee29593     : 00000000`00000010 00000000`00000000 ffff8301`fcbe8180 ffff8301`fcc6cef0 : nt!KxMcheckAbort+0x7e
ffff8301`fcc6ce60 fffff802`0ee2111b     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x2d3
ffffef8d`6af37bc0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SwapContext+0xab

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0x124_0_AuthenticAMD_MEMORY__UNKNOWN_FATAL_IMAGE_AuthenticAMD.sys

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

Followup:     MachineOwner
---------
0 个注释
匿名
我们使用翻译服务协助我们的用户。请原谅语法错误。
该屏幕截图表明与您的 AMD 处理器关联的驱动程序导致 PC 崩溃。
您是在超频处理器，还是在 BIOS 的 RAM 上设置了 XMP （DOCP）配置文件？
0 个注释
你好，最近用windows11玩CS2，进游戏没问题，但是一玩起来就会自动黑屏重启。

49 个答案
