Windows 10: BSOD, Bugcheck Analysis : "probably caused by : GenuineIntel"

My 4-year-old custom build started having Bluescreens a month ago, it's rather random and sometimes I don't have crashes for days but it's very unpredictable. I wasn't able to trigger the crash with various test programs so I'm a little lost how I find a solution to my problem. Here is the analyse for the Crashdump, I hope you can do something about it.

Crashdump Analyse with WinDbg:


Microsoft (R) Windows Debugger Version 10.0.17134.12 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\TomBi\Desktop\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.


************* Path validation summary **************
Response Time (ms) Location
OK C:\symbol
Symbol search path is: C:\symbol
Executable search path is:
Windows 10 Kernel Version 17134 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff800`8460e000 PsLoadedModuleList = 0xfffff800`849bc170
Debug session time: Thu Sep 13 14:01:16.559 2018 (UTC + 1:00)
System Uptime: 0 days 1:11:01.278
Loading Kernel Symbols
...............................................................
................................................................
................................................................
....
Loading User Symbols

Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, ffff998aba0dc028, bf800000, 124}

Probably caused by : GenuineIntel

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

5: 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: ffff998aba0dc028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.

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


KEY_VALUES_STRING: 1


TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804

SYSTEM_MANUFACTURER: MSI

SYSTEM_PRODUCT_NAME: MS-7845

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

SYSTEM_VERSION: 1.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: V2.10

BIOS_DATE: 02/17/2016

BASEBOARD_MANUFACTURER: MSI

BASEBOARD_PRODUCT: Z97-GD65 GAMING (MS-7845)

BASEBOARD_VERSION: 1.0

DUMP_TYPE: 1

BUGCHECK_P1: 0

BUGCHECK_P2: ffff998aba0dc028

BUGCHECK_P3: bf800000

BUGCHECK_P4: 124

BUGCHECK_STR: 0x124_GenuineIntel

CPU_COUNT: 8

CPU_MHZ: fa0

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R) SIG: 22'00000000 (cache) 22'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: f

ANALYSIS_SESSION_HOST: DESKTOP-EG6T4T9

ANALYSIS_SESSION_TIME: 09-13-2018 18:07:57.0598

ANALYSIS_VERSION: 10.0.17134.12 x86fre

STACK_TEXT:
ffffc880`08a84be8 fffff800`84fa1520 : 00000000`00000124 00000000`00000000 ffff998a`ba0dc028 00000000`bf800000 : nt!KeBugCheckEx
ffffc880`08a84bf0 fffff80c`61d914ba : ffff998a`ba0dc028 ffff998a`b950c1d0 ffff998a`b950c1d0 ffff998a`b950c1d0 : hal!HalBugCheckSystem+0xd0
ffffc880`08a84c30 fffff800`848cccd1 : ffff998a`ba0dc028 00000000`00000000 ffff998a`b950c1d0 ffff998a`b950c1d0 : PSHED!PshedBugCheckSystem+0xa
ffffc880`08a84c60 fffff800`84fa2c60 : 00000000`00000728 00000000`00000005 00000000`00000000 00000000`00000000 : nt!WheaReportHwError+0x261
ffffc880`08a84cc0 fffff800`84fa2fc0 : 00000000`00000010 ffff998a`b950c220 ffffc880`08a84e68 00000000`00000005 : hal!HalpMcaReportError+0x50
ffffc880`08a84e10 fffff800`84fa2eae : ffff998a`b950bf60 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xe0
ffffc880`08a84e60 fffff800`84fa30f2 : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xda
ffffc880`08a84ea0 fffff800`84fa3390 : ffff998a`b950bf60 ffffc880`08a850d0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
ffffc880`08a84ed0 fffff800`847c523b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
ffffc880`08a84f00 fffff800`847c4eff : 00000000`00000000 fffff800`847c4e7e 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
ffffc880`08a85040 fffff80c`660c13f3 : fffff80c`660c13b4 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x1bf
ffffab0a`048616e8 fffff80c`660c13b4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`000000eb : intelppm!MWaitIdle+0x23
ffffab0a`048616f0 fffff800`84661e8f : 00000000`00000000 ffffc880`00000071 ffffc880`08a7eec8 00000003`e030d762 : intelppm!AcpiCStateIdleExecute+0x24
ffffab0a`04861720 fffff800`84660e05 : 00000000`00000003 00000000`00000002 00000000`00000000 00000000`00000008 : nt!PpmIdleExecuteTransition+0xeff
ffffab0a`04861b00 fffff800`847ba3ac : ffffffff`00000000 ffffc880`08a79180 ffffc880`08a89200 ffff998a`c3242400 : nt!PoIdle+0x345
ffffab0a`04861c60 00000000`00000000 : ffffab0a`04862000 ffffab0a`0485c000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c


THREAD_SHA1_HASH_MOD_FUNC: 59e9e43a47d77c1821bd0dcaa629b8864b0a3695

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 9b3580dade932aecdb23076fc15f1b9e5f95401b

THREAD_SHA1_HASH_MOD: e009adc9bacbf3448800bf42f66b4f3b1a2af526

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_CACHE

PRIMARY_PROBLEM_CLASS: 0x124_GenuineIntel_PROCESSOR_CACHE

TARGET_TIME: 2018-09-13T13:01:16.000Z

OSBUILD: 17134

OSSERVICEPACK: 0

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: 2018-08-03 04:10:45

BUILDDATESTAMP_STR: 180410-1804

BUILDLAB_STR: rs4_release

BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804

ANALYSIS_SESSION_ELAPSED_TIME: 6e5

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x124_genuineintel_processor_cache

FAILURE_ID_HASH: {4c8f3f5e-1af5-ed8b-df14-d42663b1dfa7}

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

:)

 

BSOD w/ a WHEA_UNCORRECTABLE_ERROR after building a new PC with the hard-drive from my old PC.

Probably caused by : GenuineIntel

Bugcheck 0X124 can be difficult to troubleshoot as it is usually a hardware error in which Minidumps cannot find the exact cause. Here in your dump, it says probably caused by GenuineIntel which most probably is your Graphics Card or processor.

These are the standard troubleshooting steps:

BugCheck Code 124

In your case, the first step I would suggest is to try Reseating the Processor and connecting the cables again. If that doesn't help, please let us know.

Edit: Closely examining the dump blames L2 Cache had a read/write error:

Error: DCACHEL2_DRD_ERR (Proc 3 Bank 6)

So this is definately a Processor issue.

 

(BSOD) bugcheck was: 0x000000a0 INTERNAL_POWER_ERROR

Has any one got this BSOD when stress testing a overclock before? i can get the minidump if some one can read it for me i was trying for 4.5Ghz @ 1.31v and after around 20min of stressing i would get this BSOD and it would shut my system down not even sure i saw a BSOD just a shutdown?

 

BSOD Crashes bugchecks




Warning Programs that claim to update your drivers install either the wrong or corrupted drivers.
If you have installed any driver with Driver Booster 3, please remove them as it may cause trouble.
It is best that you remove IObit software and use a restore point to revert back their changes.

I would also suggest that you remove Norton and Networkx seeing they have caused some crashes.
Code:

Code:

******************************************************************************* *                                                                             * *                        Bugcheck Analysis                                    * *                                                                             * *******************************************************************************  Use !analyze -v to get detailed debugging information.  BugCheck 133, {1, 1e00, 0, 0}  *** WARNING: Unable to verify timestamp for networx.sys *** ERROR: Module load completed but symbols could not be loaded for networx.sys Probably caused by : tdx.sys ( tdx!TdxSendDatagramTransportAddress+420 )  Followup:     MachineOwner ---------   ******************************************************************************* *                                                                             * *                        Bugcheck Analysis                                    * *                                                                             * *******************************************************************************  Use !analyze -v to get detailed debugging information.  BugCheck 19, {e, ffffd000219bb340, ffffe002020fd010, bd6ca4a877952118}  *** WARNING: Unable to verify timestamp for SRTSP64.SYS *** ERROR: Module load completed but symbols could not be loaded for SRTSP64.SYS Probably caused by : Pool_Corruption ( Processing initial command '!analyze -v; !sysinfo smbios; !sysinfo machineid; !sysinfo cpuspeed; !thread; .bugcheck; .time;' nt!ExFreePool+783 )  Followup:     Pool_corruption