Question BSOD - LiveKernelEvent 124

[berseker_96]

MB: msi b450m-a pro
CPU: Ryzen 9 5900x
GPU RXT 3060 12GB ASUS
16GB RAM 2X8GB 2400MHZ
800W ATX NETWAY PSU
2x SAMSUNG EVO HDD 1TB, 1x HDD KINGSTON 500GB
W10


Crashes only happen during gaming. PC ( new CPU, GPU AND PSU) is 2 months old. Went from a AMD GPU to a NVIDIA GPU, used DDU to make a clean install.

CPU temp doesn't go over 65ºC. No overclocking setups.

Tried: Scanning drives, windows memory diagnostic, /scan /restorehealth, checking drivers, updating gpu drivers.




DMP from the last crash:

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: ffff9f83c59e7028, 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_PROCESSOR_GENERIC_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_PROCESSOR_GENERIC_ERROR_SECTION ***
*** ***
*************************************************************************

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2859

Key : Analysis.Elapsed.mSec
Value: 10198

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

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

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

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

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

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

Key : Bugcheck.Code.LegacyAPI
Value: 0x124

Key : Dump.Attributes.AsUlong
Value: 8

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Failure.Bucket
Value: 0x124_0_AuthenticAMD_PROCESSOR__UNKNOWN_IMAGE_AuthenticAMD.sys

Key : Failure.Hash
Value: {035dcc87-485b-74b3-1c1b-ee50cb0c2865}


BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffff9f83c59e7028

BUGCHECK_P3: bc800800

BUGCHECK_P4: 60c0859

FILE_IN_CAB: 122623-6078-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: DeadByDaylight

STACK_TEXT:
ffffd781`581a6938 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx


MODULE_NAME: AuthenticAMD

IMAGE_NAME: AuthenticAMD.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x124_0_AuthenticAMD_PROCESSOR__UNKNOWN_IMAGE_AuthenticAMD.sys

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {035dcc87-485b-74b3-1c1b-ee50cb0c2865}

Followup: MachineOwner



(I'm not that much into tech so I'm kinda lost. Thank you in advance)

 

[Colif]

I don't know this brand

800W ATX NETWAY PSU

what GPU did you have before?
Do you get the BSOD on old GPU?

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

1. Open Windows File Explore
2. Navigate to C:\Windows\Minidump
3. Copy the mini-dump files out onto your Desktop
4. Do not use Winzip, use the built in facility in Windows
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
7. Then post a link here to the zip file, so we can take a look for you . . .

WHEA - Windows Hardware Error Architecture. Its an error called by CPU but not necessarily caused by it, they can be any hardware. Sometimes even software.
If last change you made was GPU and you didn't have them before, it could be it or something else reacting to the change in the system.

 

[--SID--]

800W ATX NETWAY PSU

Probably junk. Provide us a picture of the label!

 

[Colif]

if its in game, it probably is the PSU not being able to actually power everything under pressure.

but I don't like guessing

 

[berseker_96]

I don't know this brand

what GPU did you have before?
Do you get the BSOD on old GPU?

I had a RX580, and had no problems with that one at all.

Probably junk. Provide us a picture of the label!

The brand is from the most used shop in Spain to help you with computers (PCBox).

In the dropbox link I attach the last reports and a picture of the label.

https://www.dropbox.com/scl/fi/b8of...-PSU.zip?rlkey=o2yinmycczs799rf21tmedjzg&dl=0

 

[berseker_96]

if its in game, it probably is the PSU not being able to actually power everything under pressure.

but I don't like guessing

Yeah might be. I only changed CPU, GPU and PSU, so one of these is causing the problem.

Just ran memtest86 and no errors came.

 

[Colif]

New and old GPU both have same wattage
what CPU did you have before?

could be a combo of things... PSU appears to be weakest link

Not sure if this is the same model PSU - https://foro-elchapuzasinformatico-...tr_sl=es&_x_tr_tl=en&_x_tr_hl=en&_x_tr_pto=sc

report - mostly for me, didn't help a lot this time.

WHEA errors rarely tell me a lot


File: 122623-6078-01.dmp (Dec 26 2023 - 22:20:32)
BugCheck: [WHEA_UNCORRECTABLE_ERROR (124)]
Probably caused by: AuthenticAMD (Process: DeadByDaylight)
Uptime: 0 Day(s), 18 Hour(s), 33 Min(s), and 48 Sec(s)

File: 122423-5953-01.dmp (Dec 25 2023 - 06:16:07)
BugCheck: [WHEA_UNCORRECTABLE_ERROR (124)]
Probably caused by: AuthenticAMD (Process: HogwartsLegacy)
Uptime: 0 Day(s), 4 Hour(s), 17 Min(s), and 28 Sec(s)

File: 122423-5734-01.dmp (Dec 25 2023 - 01:58:10)
BugCheck: [WHEA_UNCORRECTABLE_ERROR (124)]
Probably caused by: AuthenticAMD (Process: HogwartsLegacy)
Uptime: 1 Day(s), 2 Hour(s), 45 Min(s), and 56 Sec(s)

File: 122223-5937-01.dmp (Dec 23 2023 - 08:24:25)
BugCheck: [WHEA_UNCORRECTABLE_ERROR (124)]
Probably caused by: AuthenticAMD (Process: HogwartsLegacy)
Uptime: 0 Day(s), 2 Hour(s), 54 Min(s), and 48 Sec(s)

Hogwarts is victim, not cause.

Comment: 2 or more types of RAM are installed.
how long you used unmatching ram sticks?
8192MB 2400MHz Kingston KHX3200C18D4/8G
8192MB 2400MHz Kingston KHX3200C16D4/8GX
different latency, doubt it would be cause?

 

[berseker_96]

My last CPU was a Ryzen 5 2600.

Looks to be the same PSU model. The 800W one.


I've been using a 2nd RAM stick for almost 4 years, since I wanted to play Warzone during Covid lockdown and 8gb weren't enough, so I went for another one (closest one to the one I had that I could find).

 

[berseker_96]

if its in game, it probably is the PSU not being able to actually power everything under pressure.

but I don't like guessing

Can't reply to your last answer.
This is the link to the product.
https://www.pcbox.com/ap-nw3516-fuente-alimentacion-800-netway/p

 

[Colif]

netway could be a brand owned by PCBox, i can't find a lot on it. they have a wide selection - https://www.pcbox.com/netway

wattage difference in CPU might be cause, you have a few more cores now than before.

I would be tempted to get a PSU from Corsair if you can. It is more likely to actually supply power you need.
https://www.corsair.com/us/en/p/psu...old-certified-fully-modular-psu-cp-9020180-na

 

[DSzymborski]

The PSU is absolutely horrifying. Why spend so much on a PC and then dump in some cheap, mystery meat group-regulated PSU? Hopefully it didn't damage anything already.

 

[Colif]

The PSU is absolutely horrifying. Why spend so much on a PC and then dump in some cheap, mystery meat group-regulated PSU? Hopefully it didn't damage anything already.

(I'm not that much into tech so I'm kinda lost. Thank you in advance)

Perhaps they didn't know any better

 

[berseker_96]

netway could be a brand owned by PCBox, i can't find a lot on it. they have a wide selection - https://www.pcbox.com/netway

wattage difference in CPU might be cause, you have a few more cores now than before.

I would be tempted to get a PSU from Corsair if you can. It is more likely to actually supply power you need.
https://www.corsair.com/us/en/p/psu...old-certified-fully-modular-psu-cp-9020180-na

It's a brand owned, yes.

But if the power isn't sufficient enough, shouldn't the computer switch off directly, instead of going blue screen and restarting?

 

[DSzymborski]

It's a brand owned, yes.

But if the power isn't sufficient enough, shouldn't the computer switch off directly, instead of going blue screen and restarting?

Usually, yes, but a junk PSU can also *damage* parts and indirectly cause problems.

The best practice, when faced with a significant problem when a junk PSU is present, is to eliminate that first and then deal with the issue. Kind of like if your hot water heater has a leak, the first thing you do is close off the water supply.