Question Random BSODs typically when Idle - New System

Jan 29, 2020
1
0
10
0
Hi everyone,

New here but really could use some help. I built a brand new PC a few months back (Specs are here). I am randomly getting BSODs with the code "WHEA_UNCORRECTABLE_ERROR". This is my first build so ANY input would be greatly appreciated.

I have tried running Memtest86, reinstalling windows 10, checking/formatting my hard drives, and unplugging and replugging power chords. I have turned off and overclocking capabilities and everything performs well in userbenchmark. I also updated windows, and installed the latest motherboard and graphics drivers.

I'm completely at a loss as to what it could be other than the CPU or motherboard. Games run perfectly and it is random when I get the BSOD.

Below is the most recent dump file:

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

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


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER: Micro-Star International Co., Ltd.

SYSTEM_PRODUCT_NAME: MS-7B17

SYSTEM_SKU: Default string

SYSTEM_VERSION: 2.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: A.60

BIOS_DATE: 08/08/2019

BASEBOARD_MANUFACTURER: Micro-Star International Co., Ltd.

BASEBOARD_PRODUCT: MPG Z390 GAMING EDGE AC (MS-7B17)

BASEBOARD_VERSION: 2.0

DUMP_TYPE: 2

BUGCHECK_P1: 0

BUGCHECK_P2: ffffdf0f84487028

BUGCHECK_P3: b2000000

BUGCHECK_P4: 30005

BUGCHECK_STR: 0x124_GenuineIntel

CPU_COUNT: 10

CPU_MHZ: e10

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: c

CPU_MICROCODE: 6,9e,c,0 (F,M,S,R) SIG: BE'00000000 (cache) BE'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME: System

CURRENT_IRQL: f

ANALYSIS_SESSION_HOST: DESKTOP-46G2N7O

ANALYSIS_SESSION_TIME: 01-29-2020 19:05:15.0178

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

STACK_TEXT:
fffff80668484918 fffff80665c4cfe3 : 0000000000000124 0000000000000000 ffffdf0f84487028 00000000b2000000 : nt!KeBugCheckEx
fffff80668484920 fffff80666b8191b : ffffdf0f806125f0 0000000000000000 ffffdf0f84487028 0000000000000000 : hal!HalBugCheckSystem+0xd3
fffff80668484960 fffff80665fe894d : ffffdf0f806125f0 fffff806684849e9 0000000000000000 ffffdf0f84487028 : PSHED!PshedBugCheckSystem+0xb
fffff80668484990 fffff80665c4e941 : fffff80668484ab0 0000000000000000 ffffdf0f80612640 ffffdf0f806125f0 : nt!WheaReportHwError+0x37d
fffff80668484a50 fffff80665c4edda : 0000000000000010 ffffdf0f80612640 fffff80668484c08 fffff80668484e50 : hal!HalpMcaReportError+0x6d
fffff80668484bb0 fffff80665c4ecb4 : ffffdf0f7c4cc450 0000000000000001 0000000000000000 0000000000000000 : hal!HalpMceHandlerCore+0xf2
fffff80668484c00 fffff80665c4ef20 : 0000000000000010 0000000000000001 0000000000000000 0000000000000000 : hal!HalpMceHandler+0xe0
fffff80668484c40 fffff80665c4dfc8 : 0000000000000000 fffff80668484ed0 0000000000000000 0000000000000000 : hal!HalpMceHandlerWithRendezvous+0xd4
fffff80668484c70 fffff80665c4f1a7 : ffffdf0f7c4cc450 0000000000000000 0000000000000000 0000000000000000 : hal!HalpHandleMachineCheck+0x5c
fffff80668484ca0 fffff80665f4ca1b : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : hal!HalHandleMcheck+0x37
fffff80668484cd0 fffff80665e784ba : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiHandleMcheck+0xb
fffff80668484d00 fffff80665e78171 : ffffdf0f00000000 fffff80665e780ae ffffffffffffffff 0000000000000000 : nt!KxMcheckAbort+0x7a
fffff80668484e40 fffff80665cdb1e8 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiMcheckAbort+0x271
fffff806684681d0 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!ExAllocateHeapPool+0xae8


THREAD_SHA1_HASH_MOD_FUNC: 77138abdea5740c321cca488ffc4081e0e18228a

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: e9020b9d7d8a002d778eedb9021d1b5538b10c13

THREAD_SHA1_HASH_MOD: 2e7aa506b46de331baac28a574c338764f2697af

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x124_GenuineIntel_VRF_PROCESSOR_MAE_UNKNOWN

BUCKET_ID: 0x124_GenuineIntel_VRF_PROCESSOR_MAE_UNKNOWN

PRIMARY_PROBLEM_CLASS: 0x124_GenuineIntel_VRF_PROCESSOR_MAE_UNKNOWN

TARGET_TIME: 2020-01-29T23:36:00.000Z

OSBUILD: 18362

OSSERVICEPACK: 592

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 1972-08-21 20:24:00

BUILDDATESTAMP_STR: 190318-1202

BUILDLAB_STR: 19h1_release

BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME: f41

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x124_genuineintel_vrf_processor_mae_unknown

FAILURE_ID_HASH: {86b830ad-b4dd-33a4-d583-287f8d31c4b5}

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

rurush

Honorable
Dec 18, 2013
4
0
10,510
0
Hello,

Not sure if this can help but according to microsoft :

It can be heat related, defective hardware, memory or even a processor that is beginning to fail or has failed. If over-clocking has been enabled, try disabling it. Confirm that any cooling systems such as fans are functional. Run system diagnostics to confirm that the system memory is not defective. It is less likely, but possible that a driver is causing the hardware to fail with this bug check.

Also there is this old post : https://forums.tomshardware.com/threads/how-to-fix-whea_uncorrectable_error-124.2635865/
 

ASK THE COMMUNITY

TRENDING THREADS