PC Processors

[buildorbust]

Just BSOD, WOW!!!!!! Any amd processor bsod? Bad quality control? 

Computer: MSI MS-7C84
CPU: AMD Ryzen 9 5950X (Vermeer, VMR-B0)
3400 MHz (34.00x100.0) @ 3600 MHz (36.00x100.0)
Motherboard: MSI MAG X570 TOMAHAWK WIFI (MS-7C84)
BIOS: 1.40, 10/29/2020
Chipset: AMD X570 (Bixby)
Memory: 32768 MBytes @ 1600 MHz, 16-19-19-39
- 16384 MB PC17000 DDR4 SDRAM - G Skill F4-3600C16-16GVKC
- 16384 MB PC17000 DDR4 SDRAM - G Skill F4-3600C16-16GVKC
Graphics: GIGABYTE RTX 2070 Super Gaming OC (GV-N207SGAMING OC-8GC)
NVIDIA GeForce RTX 2070 Super, 8192 MB GDDR6 SDRAM
Drive: Samsung SSD 970 EVO Plus 500GB, 488.4 GB, NVMe
Drive: WDC WD20EARX-00PASB0, 1953.5 GB, Serial ATA 6Gb/s @ 6Gb/s
Drive: OCZ-AGILITY3, 117.2 GB, Serial ATA 6Gb/s @ 6Gb/s
Drive: Samsung SSD 860 PRO 512GB, 500.1 GB, Serial ATA 6Gb/s @ 6Gb/s
Sound: NVIDIA TU104 - High Definition Audio Controller
Sound: AMD Starship/Matisse/Vermeer - HD Audio Controller
Network: RealTek Semiconductor RTL8125 Gaming 2.5GbE Family Ethernet Controller
Network: Intel Wi-Fi 6 AX200 160MHz
OS: Microsoft Windows 10 Enterprise (x64) Build 19041.450 (2004/May 2020 Update)

[pokester]

Hard to say it may be just the immaturity of the bios you are using and a future one will correct the issue. The best thing I would think for you would be to talk with the support department for your motherboard. Make sure they know what you are getting with their product. They should be able to help you diagnose if this is just growing pains of a new product of if they think maybe you do have a CPU issue. 

Being and early adopter can be a painful thing. 

[Nerevar]

i experienced similar problems after updating to a AGESA 1.0.8.1 BIOS for my Gigabyte X570 Xtreme motherboard. I got random reboots, which were predecessed by WHEA errors in my event viewer log. The ID of the WHEA errors is 19. Downgrading to a pre-Zen3 compatible BIOS resolved the problem (no reboots since 2,5 weeks). That's why I'm hesitating to upgrade to 1.1.0.0 :-(

[pokester]

There have been a ton  of the WHEA errors reported after bios updates since mid this year. Definitely something going on there. However this error is also a very generic error and phsyical hardware issues with CPU, GPU, Memory, power etc can all cause the same errors. As well as registry corruption and malware can do it too. So it can be very hard to pin down the errors. All I know is I have run into none of this with Zen 2 on B450 and I have 3 boards personally so maybe just luck but I think it really is more stable. Most of these complaints seem to be on x5xx boards and it looks like Zen 3 is maybe starting off with some issues too. Hope they get it sorted. It doesn't matter how fast your processor is, if the experience isn't stable. 

[buildorbust]

Microsoft (R) Windows Debugger Version 10.0.19041.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [F:\Windows\Minidump\112720-9828-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (32 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff803`72400000 PsLoadedModuleList = 0xfffff803`7302a3b0
Debug session time: Fri Nov 27 07:47:56.096 2020 (UTC + 3:00)
System Uptime: 0 days 11:15:48.909
Loading Kernel Symbols
...............................................................
................................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
................
For analysis of this file, run !analyze -v
12: 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
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffff9887c38c7028, Address of the 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:
------------------

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
fffff8037300f340: Unable to get Flags value from nt!KdVersionBlock
fffff8037300f340: Unable to get Flags value from nt!KdVersionBlock
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
fffff8037300f340: Unable to get Flags value from nt!KdVersionBlock
*************************************************************************
*** ***
*** ***
*** 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.Sec
Value: 2

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on USER-PC

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 20

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

Key : Analysis.System
Value: CreateObject

BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffff9887c38c7028

BUGCHECK_P3: bc800800

BUGCHECK_P4: 60c0859

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: dota2.exe

STACK_TEXT:
ffffdf80`895e1938 fffff803`728b31ca : 00000000`00000124 00000000`00000000 ffff9887`c38c7028 00000000`bc800800 : nt!KeBugCheckEx
ffffdf80`895e1940 fffff803`6e5015b0 : 00000000`00000000 ffff9887`c38c7028 ffff9887`b80f2200 ffff9887`c38c7028 : nt!HalBugCheckSystem+0xca
ffffdf80`895e1980 fffff803`729b4d3e : 00000000`00000000 ffffdf80`895e1a29 ffff9887`c38c7028 ffff9887`b80f2200 : PSHED!PshedBugCheckSystem+0x10
ffffdf80`895e19b0 fffff803`728b4af1 : ffff9887`c35f7b50 ffff9887`c35f7b50 ffff9887`b80f2250 ffff9887`b80f2200 : nt!WheaReportHwError+0x46e
ffffdf80`895e1a90 fffff803`728b4e63 : 00000000`0000000c ffff9887`b80f2250 ffff9887`b80f2200 00000000`0000000c : nt!HalpMcaReportError+0xb1
ffffdf80`895e1c00 fffff803`728b4d40 : ffff9887`b6ef38a0 00000000`00000000 ffffdf80`895e1e00 00000000`00000000 : nt!HalpMceHandlerCore+0xef
ffffdf80`895e1c50 fffff803`728b4285 : ffff9887`b6ef38a0 ffffdf80`895e1ef0 00000000`00000000 00000000`00000000 : nt!HalpMceHandler+0xe0
ffffdf80`895e1c90 fffff803`728b6a45 : ffff9887`b6ef38a0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0xe9
ffffdf80`895e1cc0 fffff803`7290c179 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x35
ffffdf80`895e1cf0 fffff803`728042fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9
ffffdf80`895e1d20 fffff803`72803fb7 : 00000000`00000000 fffff803`72803eec ffff9887`ca94a000 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffffdf80`895e1e60 fffff803`85e3e06c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277
ffff9586`430ca9f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x82e06c

MODULE_NAME: AuthenticAMD

IMAGE_NAME: AuthenticAMD.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR__UNKNOWN

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {92068ce4-dacf-c0d2-ac6c-91e2b9ac5b67}

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

[buildorbust]

CPU: ryzen 5950x

Motheboard: MSI tomahawk x570 wifi

Memory: G.Skill Ripjaws V DDR4 2x16Gb F4-3600C16D-32GVKC

PSU: Seasonic SSR-750TR

GPU: Nvidia RTX 2070 Super

[Marucins]

Welcome to the club.
Lots of people are struggling with the 5950X, especially with GIGABYTE motherboards.

[Marucins]

Welcome to the club.
Lots of people are struggling with the 5950X, especially with GIGABYTE motherboards.

Replaced 3950X with 5950X=WHEA and reboots 

Others still struggle with the BIOS, but the truth is that getting 2 CCX with 8 core cores is much more difficult...

PS. I sent my processor to exchange for a new, working one. 

[Amiles]

Hello! I just finished a build with a 5950x, and was curious if you ever found out what exactly was causing this problem.  I seem to be having the same issue on an ASUS motherboard.  If you sent it in to get a replacement, did the replacement have the same issues? Thanks!

[deepcuts]

I have bought another 5950X and returned the 1st defective 5950X.
The replacement CPU fixed my problems.
AMD has some serious QQ problems.

[knubb]

Hello sir, same here 5950x and gigabyte x570 elite. At first I couldn't even boot the **bleep**ing thing and I had the cpu led several times.

After what has been like 20 bios flash I can barely boot and I immediately get a bsod. definitely something wrong. I already sent and RMA request since last week but no answer at all.

Very first AMD processor that I bought and probably the very last one. 

[knubb]

Hello Sir, same here 5950x x570 aorus elite. At first I couldn't even boot the **bleep** thing. I must have done at least 10 bios flash. Now it can barely boot and just crash whatever I do. I've tried another board doesn't even boot. I've already made a warranty request last week that was left unanswered.

This is the first time that I bought an AMD processor and it will probably be the last time. 

[buildorbust]

minidump file

https://drive.google.com/file/d/1L8alcMCjbr6t2lzB316vABp1Xn2dAnhe/view?usp=sharing 

Microsoft (R) Windows Debugger Version 10.0.19041.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\112820-13453-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (32 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff803`23200000 PsLoadedModuleList = 0xfffff803`23e2a310
Debug session time: Sat Nov 28 02:47:48.458 2020 (UTC - 8:00)
System Uptime: 0 days 0:09:16.055
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
Loading unloaded module list
.........
For analysis of this file, run !analyze -v
12: 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
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffc08c05544028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bc000800, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000001010135, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------

fffff80323e0f340: Unable to get Flags value from nt!KdVersionBlock
fffff80323e0f340: Unable to get Flags value from nt!KdVersionBlock
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
fffff80323e0f340: Unable to get Flags value from nt!KdVersionBlock
*************************************************************************
*** ***
*** ***
*** 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.Sec
Value: 2

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-96HSJQP

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 28

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

Key : Analysis.System
Value: CreateObject

BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffc08c05544028

BUGCHECK_P3: bc000800

BUGCHECK_P4: 1010135

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: dota2.exe

STACK_TEXT:
ffffd100`be9d7938 fffff803`236b333a : 00000000`00000124 00000000`00000000 ffffc08c`05544028 00000000`bc000800 : nt!KeBugCheckEx
ffffd100`be9d7940 fffff803`1f6d15b0 : 00000000`00000000 ffffc08c`05544028 ffffc08c`02af7200 ffffc08c`05544028 : nt!HalBugCheckSystem+0xca
ffffd100`be9d7980 fffff803`237b4e3e : 00000000`00000000 ffffd100`be9d7a29 ffffc08c`05544028 ffffc08c`02af7200 : PSHED!PshedBugCheckSystem+0x10
ffffd100`be9d79b0 fffff803`236b4c61 : ffffc08c`0c797900 ffffc08c`0c797900 ffffc08c`02af7250 ffffc08c`02af7200 : nt!WheaReportHwError+0x46e
ffffd100`be9d7a90 fffff803`236b4fd3 : 00000000`0000000c ffffc08c`02af7250 ffffc08c`02af7200 00000000`0000000c : nt!HalpMcaReportError+0xb1
ffffd100`be9d7c00 fffff803`236b4eb0 : ffffc08c`00f048a0 00000000`00000000 ffffd100`be9d7e00 00000000`00000000 : nt!HalpMceHandlerCore+0xef
ffffd100`be9d7c50 fffff803`236b43f5 : ffffc08c`00f048a0 ffffd100`be9d7ef0 00000000`00000000 00000000`00000000 : nt!HalpMceHandler+0xe0
ffffd100`be9d7c90 fffff803`236b6bb5 : ffffc08c`00f048a0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0xe9
ffffd100`be9d7cc0 fffff803`2370c2b9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x35
ffffd100`be9d7cf0 fffff803`236036fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9
ffffd100`be9d7d20 fffff803`236033b7 : 00000000`00000000 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffffd100`be9d7e60 00007ffc`95be99f9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277
0000004f`0317b370 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`95be99f9

MODULE_NAME: AuthenticAMD

IMAGE_NAME: AuthenticAMD.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR__UNKNOWN

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {92068ce4-dacf-c0d2-ac6c-91e2b9ac5b67}

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

[elstaci]

I recently purchased a new Asus Motherboard and it has two latest BIOS.

Non-BETA BIOS has Patch B

BETA BIOS has Patch C.

I asked Asus Tech about the difference between Non-BETA and BETA BIOS and  he mentioned the Patches are different.

Possibly Patch C might be for the new AMD Processors but at least at Asus it is still considered to be BETA BIOS.

EDIT: Went to your Motherboad BIOS download page and the latest is a BETA BIOS which i would avoid installing:

7C84v151(Beta version)

MSI Latest Non-BETA includes Patch C in it.

[buildorbust]

7C84v151 - bsod

7C84v14 - bsod

7C84v13 - bsod

[deepcuts]

Same issue on a Gigabyte Aorus X570 Xtreme
Upgraded from 3950X to 5950X = from stable to constant reboots in seconds.
Stock settings with defaults loaded and memory at 2133 Mhz
The only setting that "fixes" constant reboots and BSODS is to disable Core Performance Boots, which locks the CPU at 3.4 Ghz.
Replaced everything but CPU and motherboard.
Opened a ticket with AMD. So far no reply. Not even the email with "A separate email containing your service request reference number will follow."
I hope this is a BIOS issue, but at the same time, there are other users with the same board and without this issue.