Question BSOD: screen freezes, sound buzzes, computer reboots ?

[Aleki45]

Hello,

I bought this computer a few weeks ago:

Motherboard: Gigabyte A520M S2H
CPU: AMD Ryzen 7 5700X
Cooler: Stock
GPU: Palit GP RTX3070 8GB
RAM: XPG 2x8GB 3200Mhz
Storage: 1TB Lexar NM620 M.2 NVMe SSD
PSU: Fractal Design Anode Bronze 750W
Case: DEEPCOOL Matrexx 50 ADD-RGB 4F

I'm using it mostly to play the newest Call of Duty Modern Warfare III and about a couple weeks ago or so I had a weird crash while I was playing. The screen froze, the sound buzzed and 1 or 2 seconds later the computer rebooted automatically.

I did a completly fresh reinstallation of Windows, updated all the drivers and the BIOS but the crash happened again and again...

The weird part is that it seems really random. Today I turned on the computer and after 30 minutes playing the computer crashed, the day before was the same, it crashed like 3 or 4 times within ~2 hours; but the other day I was playing and livestreaming it for +8 hours straight and nothing happened.

I used a stress and benchmark software to see if I would get any crash, but nothing happened.

Later I installed also a hardware monitoring software to check temperatures and I noticed that my cpu reaches 50C/55C while idle, 60C/70C while browsing internet and 85C/90C+ while gaming. I just ordered a new water cooler hoping that it will fix the overheating problem.

But let's say that the stock cooler/heatsink is installed correctly with new thermal paste and it's working properly, could the overheating be a more serious CPU issue? Because the stock cooler should be able to handle the CPU considering that there's no overclocks or anything like that.
Also my case has decent ventilation: 3x120mm intake, 1x140mm exhaust and now it will have another 2 120mm exhaust from the water cooler.

Also, before leaving to work today I left the computer turned on and running MemTest86 and in ~30 minutes it looked like it was stuck at 21%.

Meanwhile I checked the Windows MiniDump file but I really don't understand it, I was hoping to get some help regarding this. Here is what I got from the dump file:


*******************************************************************************
* *
* 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: ffffbe073bc37028, 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: 2483

Key : Analysis.Elapsed.mSec
Value: 10832

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

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

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

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

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

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

Key : Bugcheck.Code.LegacyAPI
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: ffffbe073bc37028

BUGCHECK_P3: bc800800

BUGCHECK_P4: 60c0859

FILE_IN_CAB: 021324-8968-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: cod.exe

STACK_TEXT:
ffff9b81`fb265938 fffff805`7a4fee1b : 00000000`00000124 00000000`00000000 ffffbe07`3bc37028 00000000`bc800800 : nt!KeBugCheckEx
ffff9b81`fb265940 fffff805`767b10c0 : 00000000`00000000 ffff9b81`fb265a19 ffffbe07`3bc37028 ffffbe07`3a0d7ae0 : nt!HalBugCheckSystem+0xeb
ffff9b81`fb265980 fffff805`7a60e3bf : 00000000`00000000 ffff9b81`fb265a19 ffffbe07`3bc37028 00000000`00000000 : PSHED!PshedBugCheckSystem+0x10
ffff9b81`fb2659b0 fffff805`7a50084a : ffffbe07`3a1adb00 ffffbe07`3a1adb00 ffffbe07`3a0d7b30 fffff805`7a380a1e : nt!WheaReportHwError+0x38f
ffff9b81`fb265a80 fffff805`7a500ca0 : 00000000`0000000c ffffbe07`00000000 00000000`00000000 00000000`00000000 : nt!HalpMcaReportError+0xb2
ffff9b81`fb265bf0 fffff805`7a500b34 : ffffbe07`3a0dc900 00000000`00000000 ffff9b81`fb265e00 00000000`00000000 : nt!HalpMceHandlerCore+0x138
ffff9b81`fb265c50 fffff805`7a4fffc7 : ffffbe07`3a0dc900 ffff9b81`fb265ef0 00000000`00000000 00000000`00000000 : nt!HalpMceHandler+0xe0
ffff9b81`fb265c90 fffff805`7a50275b : ffffbe07`3a0dc900 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0x97
ffff9b81`fb265cc0 fffff805`7a568e39 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x3b
ffff9b81`fb265cf0 fffff805`7a428b7e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9
ffff9b81`fb265d20 fffff805`7a428793 : 00000000`00000000 00000000`00000000 000002a9`619871a0 ffff9b81`fb265ef0 : nt!KxMcheckAbort+0x7e
ffff9b81`fb265e60 00007ff7`8601ce2e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x2d3
000000dd`7e0fe230 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff7`8601ce2e


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
---------

 

[Fix_that_Glitch]

What cooler do you currently have installed? I would clean off the coolers and cpu thermal paste. Repaste the cooling plate and after screwing down the cooling plate ,remove the cooling plate again and see how even, or uneven the thermal paste spreads on the cpu and cooling plate.

 

[Aleki45]

What cooler do you currently have installed? I would clean off the coolers and cpu thermal paste. Repaste the cooling plate and after screwing down the cooling plate ,remove the cooling plate again and see how even, or uneven the thermal paste spreads on the cpu and cooling plate.

I had the stock cooler that comes with the Ryzen 7 5700X.
I just installed a new water cooler (Cooler Master MasterLiquid ML240R RGB) and temperatures are now okay: 30C-40C while idle and 60C-70C while gaming.
Still I didn't test it a lot so I'm not sure if the problem was the cpu or if there's is something wrong with the RAM.

 

[Fix_that_Glitch]

I had the stock cooler that comes with the Ryzen 7 5700X.
I just installed a new water cooler (Cooler Master MasterLiquid ML240R RGB) and temperatures are now okay: 30C-40C while idle and 60C-70C while gaming.
Still I didn't test it a lot so I'm not sure if the problem was the cpu or if there's is something wrong with the RAM.

You can try using one stick of ram at a time to see if one of them is the culprit, your mini dump pointed at your call of duty exe, but that could simply be the last thing running when it crashed.

 

[Aleki45]

You can try using one stick of ram at a time to see if one of them is the culprit, your mini dump pointed at your call of duty exe, but that could simply be the last thing running when it crashed.

Actually it only crashes in Call of Duty, I wouldn't be surprised if the problem was in the game considering how poorly made and optimized it is lmao But anyways, I installed a new water cooler and I was doing today stress tests to CPU, GPU and RAM and everything went fine. Temperatures on CPU were always below 80C and on GPU always below 70C. And I just bought a 4 pin splitter to connect both the radiator fans and the water pump itself to the CPU_FAN because my motherboard doesn't have CPU_OPT or PUMP header so maybe the temperatures will even drop a little bit because right now I have the radiator fans connected to the SYS_FAN header so it doesn't really pump those rpms according to the CPU temperature. Hopefully it was just a overheating problem and it won't happen anymore. But now I'm curious, is it normal for this CPU to heat so much with the stock cooler? And I can guarantee that it was installed correctly with fress thermal paste.

 

[Aleki45]

Actually it only crashes in Call of Duty, I wouldn't be surprised if the problem was in the game considering how poorly made and optimized it is lmao But anyways, I installed a new water cooler and I was doing today stress tests to CPU, GPU and RAM and everything went fine. Temperatures on CPU were always below 80C and on GPU always below 70C. And I just bought a 4 pin splitter to connect both the radiator fans and the water pump itself to the CPU_FAN because my motherboard doesn't have CPU_OPT or PUMP header so maybe the temperatures will even drop a little bit because right now I have the radiator fans connected to the SYS_FAN header so it doesn't really pump those rpms according to the CPU temperature. Hopefully it was just a overheating problem and it won't happen anymore. But now I'm curious, is it normal for this CPU to heat so much with the stock cooler? And I can guarantee that it was installed correctly with fress thermal paste.

UPDATE: After installing the splitter cable I redid the stress tests and WOW! The CPU temperatures were always below 60C!

 

[Fix_that_Glitch]

Anymore crashes?