BS ryzen 1700 WHEA_UNCORRECTABLE_ERROR

[rksora]

-I recently purchased a ryzen 1700 and today I have this blue screen
Could it be ram?
-i also get this other screen frequently, i put it at the final
-Check my system says I have 16gb only 7.59 is available, unplug the ram and connect it again now I have 16gb, any hope that would be the problem?
- Thank you for the answers

------------------------------------------------------------------------------------------------
BSOD 1

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: ffff93852612b028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2a00020, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000003f0000, Low order 32-bits of the MCi_STATUS value.

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

GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.15063.332 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER: Micro-Star International Co., Ltd

SYSTEM_PRODUCT_NAME: MS-7A34

SYSTEM_SKU: To be filled by O.E.M.

SYSTEM_VERSION: 3.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: H.40

BIOS_DATE: 05/10/2017

BASEBOARD_MANUFACTURER: Micro-Star International Co., Ltd

BASEBOARD_PRODUCT: B350 TOMAHAWK ARCTIC(MS-7A34)

BASEBOARD_VERSION: 3.0

DUMP_TYPE: 2

BUGCHECK_P1: 0

BUGCHECK_P2: ffff93852612b028

BUGCHECK_P3: b2a00020

BUGCHECK_P4: 3f0000

BUGCHECK_STR: 0x124_AuthenticAMD

CPU_COUNT: 10

CPU_MHZ: bb8

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 1

CPU_STEPPING: 1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: chrome.exe

CURRENT_IRQL: f

ANALYSIS_SESSION_HOST: KYO

ANALYSIS_SESSION_TIME: 06-14-2017 20:21:08.0311

ANALYSIS_VERSION: 10.0.15063.400 x86fre

STACK_TEXT:
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME: AuthenticAMD

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR__UNKNOWN

BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR__UNKNOWN

PRIMARY_PROBLEM_CLASS: 0x124_AuthenticAMD_PROCESSOR__UNKNOWN

TARGET_TIME: 2017-06-14T22:07:07.000Z

OSBUILD: 15063

OSSERVICEPACK: 332

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2017-05-20 00:49:54

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.15063.332

ANALYSIS_SESSION_ELAPSED_TIME: d26

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x124_authenticamd_processor__unknown

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

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

GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E

-------------------------------------------------------------------------------------------
BSOD 2

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

BAD_SYSTEM_CONFIG_INFO (74)
Can indicate that the SYSTEM hive loaded by the osloader/NTLDR
was corrupt. This is unlikely, since the osloader will check
a hive to make sure it isn't corrupt after loading it.
It can also indicate that some critical registry keys and values
are not present. (i.e. somebody used regedt32 to delete something
that they shouldn't have) Booting from LastKnownGood may fix
the problem, but if someone is persistent enough in mucking with
the registry they will need to reinstall or use the Emergency
Repair Disk.
Arguments:
Arg1: 0000000000000002, (reserved)
Arg2: ffff84807491ca70, (reserved)
Arg3: 0000000000000002, (reserved)
Arg4: ffffffffc000009a, usually the NT status code.

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

GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.15063.413 (WinBuild.160101.0800)

DUMP_TYPE: 2

BUGCHECK_P1: 2

BUGCHECK_P2: ffff84807491ca70

BUGCHECK_P3: 2

BUGCHECK_P4: ffffffffc000009a

CPU_COUNT: 10

CPU_MHZ: bb8

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 1

CPU_STEPPING: 1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: ZEROED_STACK_0x74

BUGCHECK_STR: 0x74

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: KYO

ANALYSIS_SESSION_TIME: 06-14-2017 21:54:00.0171

ANALYSIS_VERSION: 10.0.15063.400 amd64fre

STACK_TEXT:
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30


STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: ZEROED_STACK_0x74

PRIMARY_PROBLEM_CLASS: ZEROED_STACK

FAILURE_BUCKET_ID: ZEROED_STACK_0x74

TARGET_TIME: 2017-06-14T23:04:52.000Z

OSBUILD: 15063

OSSERVICEPACK: 413

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2017-06-03 03:53:36

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.15063.413

ANALYSIS_SESSION_ELAPSED_TIME: 4f7

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:zeroed_stack_0x74

FAILURE_ID_HASH: {7a54f460-4200-bd71-debe-1b7320afc145}

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

GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E

 

[elbert]

If you are overclocking try resetting your processor to standard settings and see if that helps. Mostly thats why the error 0x124. The second is memory but could be cache, RAM, or other memory on your system.

 

[rksora]

sadly, im not overcloking my cpu at all, but i unplug and plug ram and thats seem to be the second bsod issue, but im still afraid of the first one

 

[elbert]

Then there is a bigger problem of either overheating or voltage fluctuations. Use HWmonitor to watch temps and voltages.
http://www.cpuid.com/softwares/hwmonitor.html

What is your PSU? Make sure its a quality PSU and can handle the power draw.

 

[rksora]

its an antec EA 650w green 80 bronze plus, before my ryzen i have that psu whit an i5 3570 no issues everything else is the same except mobo ram (dominator platinum 3000@2133) and cpu, but the psu has 5 years never fails me, i run prime95 for 4 hours and nothing happend.

(i have a problem with the cpu it seems like a string off copper from de cooler get stiked to the cpu thats a rare isue, never see that happend to anyone),
but before this bosd whea issue, i have cpu temps at 37-39º, after this i have the cpu temps at 44-49 and for moments go to 46-49 then for second up to 56-58º and there is no workload except google chrome, maybe my cpu has a problem with the cooler and fan, tomorrow i will go to the warranty

 

[elbert]

Your temps are fine. How about the voltages? Voltage issues could be due to the motherboards VRM's.