Hello,
I installed a new AMD Ryzen 5 5600X on my PC few months ago and on the first day it crashed with the very same error I will paste below, and since then it never had crashed. About two weeks ago, my PC started to crash with BSOD WHEA error quite frequently. I have now consistently reproduced the issue after playing for 30 minutes up to hour and a half of Squad.
Here's the full WinDBG Error analyzis:
I was first thinking that it was caused by insufficient PSU capacity. However, even though both the GPU and CPU do recommend a higher W PSU, calculators also vaguely show that even under maximum resource usage, it doesn't jump over 450 to 500W. Still not sure about that, but these are the things I've done so far:
Any suggestions and further troubleshooting tips would be greatly appreciated. Thanks
I installed a new AMD Ryzen 5 5600X on my PC few months ago and on the first day it crashed with the very same error I will paste below, and since then it never had crashed. About two weeks ago, my PC started to crash with BSOD WHEA error quite frequently. I have now consistently reproduced the issue after playing for 30 minutes up to hour and a half of Squad.
Here's the full WinDBG Error analyzis:
Code:
Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff801`18200000 PsLoadedModuleList = 0xfffff801`18e2a210
Debug session time: Fri Feb 17 06:13:27.117 2023 (UTC + 2:00)
System Uptime: 0 days 0:28:02.710
Loading Kernel Symbols
...............................................................
......Page 8082e3 not present in the dump file. Type ".hh dbgerr004" for details
..........................................................
................................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000ec`17a78018). Type ".hh dbgerr001" for details
Loading unloaded module list
.......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`185fa090 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffcf80`5dcae940=0000000000000124
9: 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: ffffb881bc003028, 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:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2374
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 2796
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 796
Key : Analysis.Init.Elapsed.mSec
Value: 9118
Key : Analysis.Memory.CommitPeak.Mb
Value: 98
Key : Bugcheck.Code.DumpHeader
Value: 0x124
Key : Bugcheck.Code.KiBugCheckData
Value: 0x124
Key : Bugcheck.Code.Register
Value: 0x124
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
FILE_IN_CAB: MEMORY.DMP
BUGCHECK_CODE: 124
BUGCHECK_P1: 0
BUGCHECK_P2: ffffb881bc003028
BUGCHECK_P3: bc800800
BUGCHECK_P4: 60c0859
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: SquadGame.exe
STACK_TEXT:
ffffcf80`5dcae938 fffff801`186b688a : 00000000`00000124 00000000`00000000 ffffb881`bc003028 00000000`bc800800 : nt!KeBugCheckEx
ffffcf80`5dcae940 fffff801`178f15b0 : 00000000`00000000 ffffb881`bc003028 ffffb881`b7bf5d20 ffffb881`bc003028 : nt!HalBugCheckSystem+0xca
ffffcf80`5dcae980 fffff801`187b8a9e : 00000000`00000000 ffffcf80`5dcaea29 ffffb881`bc003028 ffffb881`b7bf5d20 : PSHED!PshedBugCheckSystem+0x10
ffffcf80`5dcae9b0 fffff801`186b81b1 : ffffb881`bf9e0070 ffffb881`bf9e0070 ffffb881`b7bf5d70 ffffb881`b7bf5d20 : nt!WheaReportHwError+0x46e
ffffcf80`5dcaea90 fffff801`186b8523 : 00000000`00000009 ffffb881`b7bf5d70 ffffb881`b7bf5d20 00000000`00000009 : nt!HalpMcaReportError+0xb1
ffffcf80`5dcaec00 fffff801`186b8400 : ffffb881`b7b2e678 01d8c32f`00000000 ffffcf80`5dcaee00 01d93f19`606058fa : nt!HalpMceHandlerCore+0xef
ffffcf80`5dcaec50 fffff801`186b7945 : ffffb881`b7b2e678 ffffcf80`5dcaeef0 00000000`00000000 00010018`0000005a : nt!HalpMceHandler+0xe0
ffffcf80`5dcaec90 fffff801`186ba105 : ffffb881`b7b2e678 01d8ec66`721999fa 01d8ec66`721999fa 00000000`00000000 : nt!HalpHandleMachineCheck+0xe9
ffffcf80`5dcaecc0 fffff801`1870fb99 : 00690073`006e030c 0078006f`00720070 00790073`002e0079 00000000`00000073 : nt!HalHandleMcheck+0x35
ffffcf80`5dcaecf0 fffff801`1860acba : 00000018`000001a6 30334150`4749b5e5 01d5ac95`d898e245 010cc4c7`d0105eb0 : nt!KiHandleMcheck+0x9
ffffcf80`5dcaed20 fffff801`1860a977 : fffff802`00000000 fffff801`1860a8ac 00000000`00000040 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffffcf80`5dcaee60 fffff802`fe3d02f9 : f1889633`f77aa3bb fe1a6337`f1d4fdd6 ffffffff`2474d8f6 f59d4ba3`f3e1041c : nt!KiMcheckAbort+0x277
ffffa185`c55a79d8 f1889633`f77aa3bb : fe1a6337`f1d4fdd6 ffffffff`2474d8f6 f59d4ba3`f3e1041c f08e50f0`f3a34d16 : EasyAntiCheat_EOS+0x3902f9
ffffa185`c55a79e0 fe1a6337`f1d4fdd6 : ffffffff`2474d8f6 f59d4ba3`f3e1041c f08e50f0`f3a34d16 f7405ea8`f777dc8a : 0xf1889633`f77aa3bb
ffffa185`c55a79e8 ffffffff`2474d8f6 : f59d4ba3`f3e1041c f08e50f0`f3a34d16 f7405ea8`f777dc8a f1380f61`f3c4604d : 0xfe1a6337`f1d4fdd6
ffffa185`c55a79f0 f59d4ba3`f3e1041c : f08e50f0`f3a34d16 f7405ea8`f777dc8a f1380f61`f3c4604d fdf8fc0f`fcc50a6f : 0xffffffff`2474d8f6
ffffa185`c55a79f8 f08e50f0`f3a34d16 : f7405ea8`f777dc8a f1380f61`f3c4604d fdf8fc0f`fcc50a6f 00000000`00000000 : 0xf59d4ba3`f3e1041c
ffffa185`c55a7a00 f7405ea8`f777dc8a : f1380f61`f3c4604d fdf8fc0f`fcc50a6f 00000000`00000000 00000000`00000000 : 0xf08e50f0`f3a34d16
ffffa185`c55a7a08 f1380f61`f3c4604d : fdf8fc0f`fcc50a6f 00000000`00000000 00000000`00000000 00000000`00000000 : 0xf7405ea8`f777dc8a
ffffa185`c55a7a10 fdf8fc0f`fcc50a6f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xf1380f61`f3c4604d
ffffa185`c55a7a18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000008 : 0xfdf8fc0f`fcc50a6f
MODULE_NAME: AuthenticAMD
IMAGE_NAME: AuthenticAMD.sys
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: 0x124_0_AuthenticAMD_PROCESSOR_BUS_L1_SRC_IRD_I_NOTIMEOUT_IMAGE_AuthenticAMD.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {9849fca8-6c5b-4c6a-ecca-8c5e153b17bd}
Followup: MachineOwner
---------I was first thinking that it was caused by insufficient PSU capacity. However, even though both the GPU and CPU do recommend a higher W PSU, calculators also vaguely show that even under maximum resource usage, it doesn't jump over 450 to 500W. Still not sure about that, but these are the things I've done so far:
- All driver updates have been installed. I have also tried the usual file system and image checks and repairs.
- Re-seated RAM
- Reset BIOS and Installed latest drivers.
- Chipset Drivers update.
- Tested Memory Frequencies from 2400 to 3200 (currently sitting on 3200)
- Tested RAM with Window's Diagnostics tool (extended test, resulted in no problems)
- CPU Stress test via AMD Ryzen Master of 60 seconds, no errors, no high temperatures (maximum of 70 to 73 depending on what I am playing). GPU temperatures are also within norm on the low end. Also CPU Stress test via Prime95 to see if it detects any errors, but no entries of such.
- The issue occurs only when playing video games. Doesn't happen during video playing, Youtube, discord usage, photoshop, etc. Only when gaming.
- Reseat CPU with new thermal paste (last one was applied about four months ago so I doubt this will fix it).
- Possible undervoltage? Everywhere I see this processor is maintained at around 1.2~1.37V. However, mine, according to ryzen master works at 1.03~1.06 regardless of usage. I admit I don't like to overclock since I dont understand and allow the system to do its normal automatic boost when necessary, but the voltage, at least I haven't noticed so far to spike above 1.067. Maybe increase that? I don't know tbh.
- Accept the CPU I got was a faulty one and try to replace it. Warranty laws in Europe are finicky, especially in my region. But it is still under warranty and I might have to send it back if I don't find any solution, only for them to be unable to recreate the problem. To be honest I am in severe belief that there's nothing wrong with the processor.
Any suggestions and further troubleshooting tips would be greatly appreciated. Thanks
Last edited:
Facebook
Twitter
Instagram