cancel
Showing results for 
Search instead for 
Did you mean: 

Asus Prime X370 Pro deffective or 1700x cpu?

magnusr
Level 7
Sometimes I just get a bsod 124. Running windows 10 x64. It can happen in the middle of the night (while the machines does nothing). I have tried three different memory providers: kingston hyperx, corsair vengeance LPX and now the GSkill Fury X just to make sure it has nothing to do with the memory. All the latest drivers and updates.

Latest bios 0805. All latest drivers to date.

My info: Acer XR341CK | AMD Ryzen 1700X | Asus Prime X370-pro | Asus Strix GTX 1070 | G.Skill Flare X 3200MHz 16GB | Noctua NH-U12S SE-AM4 | Samsung 850 EVO M.2 | Corsair Obsidian Series 550D

I have attached the minidump. Here is from the analyze -v command. Is my cpu or mainboard deffective?

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: ffffd50e898f4038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.15063.447 (WinBuild.160101.0800)

DUMP_TYPE: 2

BUGCHECK_P1: 0

BUGCHECK_P2: ffffd50e898f4038

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BUGCHECK_STR: 0x124_AuthenticAMD

CPU_COUNT: 10

CPU_MHZ: d42

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 1

CPU_STEPPING: 1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: EAGLE

ANALYSIS_SESSION_TIME: 06-30-2017 08:15:50.0428

ANALYSIS_VERSION: 10.0.15063.400 amd64fre

STACK_TEXT:
ffff8701`5b1965b0 fffff801`0be23d6d : 00000000`00000000 ffffd50e`898f4010 fffff801`0bd4b6a0 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x7b
ffff8701`5b196ae0 fffff801`0bc68808 : ffffd50e`898f4010 00000000`00000000 fffff801`0bd44f00 ffffd50e`8990f040 : nt!WheapCreateTriageDumpFromPreviousSession+0x2d
ffff8701`5b196b10 fffff801`0bc6931b : fffff801`0bd4b640 fffff801`0bd4b640 fffff801`0bd4b6a0 fffff801`0bfcc0b0 : nt!WheapProcessWorkQueueItem+0x48
ffff8701`5b196b50 fffff801`0ba49ca8 : 00000000`00000000 ffffd50e`8990f040 ffffd50e`8707f2c8 fffff801`0be04380 : nt!WheapWorkQueueWorkerRoutine+0x2b
ffff8701`5b196b80 fffff801`0bae8ac7 : ffff8701`5a796180 00000000`00000080 ffffd50e`85e80040 ffffd50e`8990f040 : nt!ExpWorkerThread+0xd8
ffff8701`5b196c10 fffff801`0bb7d946 : ffff8701`5a796180 ffffd50e`8990f040 fffff801`0bae8a80 00000000`00000000 : nt!PspSystemThreadStartup+0x47
ffff8701`5b196c60 00000000`00000000 : ffff8701`5b197000 ffff8701`5b191000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: 26acd050bd9f055d0a04825d57b9e0e6be9c1a07

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: a03c6a9dfa29d92fd9c43635891e8ca372d4227f

THREAD_SHA1_HASH_MOD: 30a3e915496deaace47137d5b90c3ecc03746bf6

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME: AuthenticAMD

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_CACHE_PRV

BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_CACHE_PRV

PRIMARY_PROBLEM_CLASS: 0x124_AuthenticAMD_PROCESSOR_CACHE_PRV

TARGET_TIME: 2017-06-30T00:53:46.000Z

OSBUILD: 15063

OSSERVICEPACK: 447

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-20 06:55:49

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.15063.447

ANALYSIS_SESSION_ELAPSED_TIME: 3fb

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x124_authenticamd_processor_cache_prv

FAILURE_ID_HASH: {cedb04af-9437-ee8e-2e67-54d858b5dbbc}

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

4: kd> !errec ffffd50e898f4038
No export errec found
4: kd> !errrec ffffd50e898f4038
===============================================================================
Common Platform Error Record @ ffffd50e898f4038
-------------------------------------------------------------------------------
Record Id : 01d2f13b53247fa2
Severity : Fatal (1)
Length : 928
Creator : Microsoft
Notify Type : Machine Check Exception
Timestamp : 6/30/2017 0:53:46 (UTC)
Flags : 0x00000002 PreviousError

===============================================================================
Section 0 : Processor Generic
-------------------------------------------------------------------------------
Descriptor @ ffffd50e898f40b8
Section @ ffffd50e898f4190
Offset : 344
Length : 192
Flags : 0x00000001 Primary
Severity : Fatal

Proc. Type : x86/x64
Instr. Set : x64
Error Type : Cache error
Operation : Instruction Execute
Flags : 0x00
Level : 0
CPU Version : 0x0000000000800f11
Processor ID : 0x0000000000000000

===============================================================================
Section 1 : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor @ ffffd50e898f4100
Section @ ffffd50e898f4250
Offset : 536
Length : 128
Flags : 0x00000000
Severity : Fatal

Local APIC Id : 0x0000000000000000
CPU Id : 11 0f 80 00 00 08 10 00 - 0b 32 d8 7e ff fb 8b 17
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0 @ ffffd50e898f4250

===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ ffffd50e898f4148
Section @ ffffd50e898f42d0
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal

Error : ICACHEL0_IRD_ERR (Proc 0 Bank 5)
Status : 0xbaa0000000090150
3,495 Views
5 REPLIES 5

Nighter3D
Level 7
Have you run any stress tests??


Stress tests can be quite handy in checking issues. They put a intense load on the targeted component which is handy in finding instability and failing hardware.
For CPU+MEM i often use Prime95. For GPUs furmark and it's fuzzy donut of doom is a classic choice and for memory Memtest86. But there are many more to choose from. See if you can get a hint from stress tools.


Also i had my system throw WHEA errors recently. For me it was caused by my GPU which was crashing rather randomly as it was starting to fail due to age. Have you looked at that possibility?? Another possiblity is dirty power from a failing Power supply

805 is a very old bios. 1401 is giving the most stability. Link is in the top post of this forum.

syldon wrote:
805 is a very old bios. 1401 is giving the most stability. Link is in the top post of this forum.


He is talking about the PRIME X370. For that one 0805 is the most recent one based on the AGESA1006.

Will note tough that this is indeed the Crosshair VI Hero forum and probably not the best place to ask regarding the Prime X370

Nighter3D wrote:
He is talking about the PRIME X370. For that one 0805 is the most recent one based on the AGESA1006.

Will note tough that this is indeed the Crosshair VI Hero forum and probably not the best place to ask regarding the Prime X370


I see it now, cheers.

Eleiyas
Level 10
I noticed this:
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

Win8 drivers?

Are all your drivers and settings up to date?