BSOD help please

whippywhip · 24 Jul 2022 at 19:54

Hi guys, i really need some expert help here and would appreciate your input very very much, recently i started getting bsod's when gaming radomly every now and then, everything is at stock and temps on the main hardware components is fine as far as i can see (gpu,cpu)

i'm no expert regarding bsod's so don't understand what the dumps mean, i'm sure it's hardware related but not sure what part, memtest was passed overnight so not that as far as i can see,

i'm going to post the dmp file here so excuse the long text and really would appreciate any help from you guys, i'll also upload the file, thanks. EDIT: can't seem to see where to attach files

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: ffffc48cb7b33028, 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: 3140

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 9120

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

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

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

Key : WER.OS.Branch
Value: co_release

Key : WER.OS.Timestamp
Value: 2021-06-04T16:28:00Z

Key : WER.OS.Version
Value: 10.0.22000.1

FILE_IN_CAB: MEMORY.DMP

DUMP_FILE_ATTRIBUTES: 0x1000

BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffc48cb7b33028

BUGCHECK_P3: bc800800

BUGCHECK_P4: 60c0859

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME: AC2-Win64-Shipping.exe

STACK_TEXT:
ffff9a01`35927948 fffff801`6af0195b : 00000000`00000124 00000000`00000000 ffffc48c`b7b33028 00000000`bc800800 : nt!KeBugCheckEx
ffff9a01`35927950 fffff801`6ee010c0 : 00000000`00000000 ffff9a01`35927a29 ffffc48c`b7b33028 ffffc48c`b7b33028 : nt!HalBugCheckSystem+0xeb
ffff9a01`35927990 fffff801`6b03fae3 : 00000000`00000000 ffff9a01`35927a29 ffffc48c`b7b33028 ffffc48c`afefbbf0 : PSHED!PshedBugCheckSystem+0x10
ffff9a01`359279c0 fffff801`6af0334d : ffffc48c`b6989900 ffffc48c`b6989900 ffffc48c`afefbc40 178bfbff`7ef8320b : nt!WheaReportHwError+0x393
ffff9a01`35927a90 fffff801`6af03798 : 00000000`0000000f ffffc48c`00000000 00000000`00000000 00000000`0000000f : nt!HalpMcaReportError+0xb1
ffff9a01`35927bf0 fffff801`6af0362c : ffffc48c`afd52b40 6f6e6e61`00000000 ffff9a01`35927e00 20534f44`00000000 : nt!HalpMceHandlerCore+0x138
ffff9a01`35927c50 fffff801`6af02acb : ffffc48c`afd52b40 ffff9a01`35927ef0 00000000`00000000 ea3ca594`eb38d748 : nt!HalpMceHandler+0xe0
ffff9a01`35927c90 fffff801`6af0544b : ffffc48c`afd52b40 00000000`00000000 00000000`00000000 000a8664`00004550 : nt!HalpHandleMachineCheck+0x97
ffff9a01`35927cc0 fffff801`6af65849 : 00007000`1c0e020b 00000000`0000f000 00001000`00000000 00000001`c0000000 : nt!HalHandleMcheck+0x3b
ffff9a01`35927cf0 fffff801`6ae278fe : 00000000`0000000a 00001000`00017000 41600001`000205a3 00000000`00040000 : nt!KiHandleMcheck+0x9
ffff9a01`35927d20 fffff801`6ae27528 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7e
ffff9a01`35927e60 00007ff7`bd1c37f8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x2a8
00000058`4e71e9b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff7`bd1c37f8

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

BUILDLAB_STR: co_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

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

Minibiker · 24 Jul 2022 at 20:13

Have you tried with one stick of RAM at a time (assuming you have more than 1 stick installed)

whippywhip · 24 Jul 2022 at 20:15

Minibiker said:
Have you tried with one stick of RAM at a time (assuming you have more than 1 stick installed)

Hi, i have run memtest over night and it passed with no errors,

i'm not sure what else to try with memory as it's only every now and then the bsod is happening

thanks

Minibiker · 24 Jul 2022 at 20:16

whippywhip said:
Hi, i have run memtest over night and it passed with no errors,

i'm not sure what else to try with memory as it's only every now and then the bsod is happening

thanks

Could you post up your full pc spec list?

whippywhip · 24 Jul 2022 at 20:21

Minibiker said:
Could you post up your full pc spec list?

msi gaming plus b550
5800x cpu
corsair 3600mhz vengence rgb pro 32gb
evga b5 850watt psu
nvidia 3070 founders edition
Samsung 980 1TB

azazl187 · 24 Jul 2022 at 20:24

you can download a program called WhosCrashed which may help you find out what the issue is. You will need to start with hardware and remove/add to see if that resolves the issue.

Minibiker · 24 Jul 2022 at 20:25

whippywhip said:
msi gaming plus b550
5800x cpu
corsair 3600mhz vengence rgb pro 32gb
evga b5 850watt psu
nvidia 3070 founders edition
Samsung 980 1TB

I'd try the one stick at a time just to rule that out... It could be faulty drives also

azazl187 · 24 Jul 2022 at 20:26

you should also monitor temps. Have you tried a fresh install of windows?

whippywhip · 24 Jul 2022 at 20:37

azazl187 said:
you can download a program called WhosCrashed which may help you find out what the issue is. You will need to start with hardware and remove/add to see if that resolves the issue.

thanks i'll try that

azazl187 said:
you should also monitor temps. Have you tried a fresh install of windows?

monitor ram temps? i have afterburner monitor gpu and cpu temps, they seem fine, windows install is about 6 months old

azazl187 · 24 Jul 2022 at 20:57

whippywhip said:
thanks i'll try that

monitor ram temps? i have afterburner monitor gpu and cpu temps, they seem fine, windows install is about 6 months old

Monitor all temps. CPU, GPU, ram, storage. If its happening randomly while gaming it could be any of things. Has the case got good airflow? Could it be related to recent ambient high temps ?

Maybe download ddu and wipe all GPU drivers and reinstall

whippywhip · 24 Jul 2022 at 21:04

happens when playing games atm, the dump file suggest amd, so i'm thinking maybe a cpu problem, my gpu is nvidia

mickyflinn · 24 Jul 2022 at 21:14

whippywhip said:
happens when playing games atm, the dump file suggest amd, so i'm thinking maybe a cpu problem, my gpu is nvidia

Morherboard Bios up to date ?

DoneADougalOnSofa · 24 Jul 2022 at 21:19

I had similar issues when I got my 5800X. Might be worth trying Level 1 Load-line calibration (LLC) in the BIOS.
Ryzen Clock Tuner reported excess vdroop (low voltage) and wouldn't run at default settings. LLC on both CPU and SOC completely solved it for me, no crashes whatsoever since.

whippywhip · 24 Jul 2022 at 21:20

mickyflinn said:
Morherboard Bios up to date ?

yes i updated it

DoneADougalOnSofa said:
I had similar issues when I got my 5800X. Might be worth trying Level 1 Load-line calibration (LLC) in the BIOS.
Ryzen Clock Tuner reported excess vdroop (low voltage) and wouldn't run at default settings. LLC on both CPU and SOC completely solved it for me, no crashes whatsoever since.

i'll try this right away, thanks for the suggestion

Nick1881 · 25 Jul 2022 at 16:07

whippywhip said:
yes i updated it

i'll try this right away, thanks for the suggestion

Have you had any luck? I have a similar issue but my BSOD is Critical_Process_Died.

I actually bought a new M.2 and did a fresh install but it's still happening. I had it happen during a game, then it rebooted and happened twice more a few seconds after getting in to Windows.

I removed my RAM and IF overclock which made no difference. I'm currently running with 1 stick of RAM removed.

whippywhip · 25 Jul 2022 at 16:36

Nick1881 said:
Have you had any luck? I have a similar issue but my BSOD is Critical_Process_Died.

I actually bought a new M.2 and did a fresh install but it's still happening. I had it happen during a game, then it rebooted and happened twice more a few seconds after getting in to Windows.

I removed my RAM and IF overclock which made no difference. I'm currently running with 1 stick of RAM removed.

time will tell, the bsods are random, about twice a week

Nick1881 · 25 Jul 2022 at 17:38

whippywhip said:
time will tell, the bsods are random, about twice a week

Mine is very random too, though 3 in a row today was different. It's been ok so far with 1 stick of RAM, survived a short gaming session.

DoneADougalOnSofa · 26 Jul 2022 at 09:24

One other issue I had with my 5800X turned out to be an over-tightened CPU cooler. My chip went back to OCUK for testing- it was fine. My cooler was too tight and causing the RAM to misbehave, which apparently is a thing....
Sounds weird, but maybe worth a try to remove and re-seat with minimal pressure.

(Symptoms were a straight refusal to boot (DRAM led red) with any ram in dual-channel. Single stick still worked, but anything in B channel was no-go)

therealdippy · 26 Jul 2022 at 13:17

@whippywhip - download the MSFT debugging toolkit and run WinDbg on the dump file to see if it gives any more clues.

Is AC2-Win64-Shipping.exe a game? Are the BSODs only with games i.e. the PC is "under stress"?

whippywhip · 26 Jul 2022 at 15:11

DoneADougalOnSofa said:
One other issue I had with my 5800X turned out to be an over-tightened CPU cooler. My chip went back to OCUK for testing- it was fine. My cooler was too tight and causing the RAM to misbehave, which apparently is a thing....
Sounds weird, but maybe worth a try to remove and re-seat with minimal pressure.

(Symptoms were a straight refusal to boot (DRAM led red) with any ram in dual-channel. Single stick still worked, but anything in B channel was no-go)

i'm aware of overtightening, that's why i i only go to when the screw stops and not carrying on