Share via

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

Anonymous
2018-09-13T16:42:34+00:00

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 = 0xfffff8008460e000 PsLoadedModuleList = 0xfffff800849bc170

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:  

ffffc88008a84be8 fffff80084fa1520 : 0000000000000124 0000000000000000 ffff998aba0dc028 00000000bf800000 : nt!KeBugCheckEx

ffffc88008a84bf0 fffff80c61d914ba : ffff998aba0dc028 ffff998ab950c1d0 ffff998ab950c1d0 ffff998ab950c1d0 : hal!HalBugCheckSystem+0xd0

ffffc88008a84c30 fffff800848cccd1 : ffff998aba0dc028 0000000000000000 ffff998ab950c1d0 ffff998ab950c1d0 : PSHED!PshedBugCheckSystem+0xa

ffffc88008a84c60 fffff80084fa2c60 : 0000000000000728 0000000000000005 0000000000000000 0000000000000000 : nt!WheaReportHwError+0x261

ffffc88008a84cc0 fffff80084fa2fc0 : 0000000000000010 ffff998ab950c220 ffffc88008a84e68 0000000000000005 : hal!HalpMcaReportError+0x50

ffffc88008a84e10 fffff80084fa2eae : ffff998ab950bf60 0000000000000001 0000000000000000 0000000000000000 : hal!HalpMceHandlerCore+0xe0

ffffc88008a84e60 fffff80084fa30f2 : 0000000000000008 0000000000000001 0000000000000000 0000000000000000 : hal!HalpMceHandler+0xda

ffffc88008a84ea0 fffff80084fa3390 : ffff998ab950bf60 ffffc88008a850d0 0000000000000000 0000000000000000 : hal!HalpMceHandlerWithRendezvous+0xce

ffffc88008a84ed0 fffff800847c523b : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : hal!HalHandleMcheck+0x40

ffffc88008a84f00 fffff800847c4eff : 0000000000000000 fffff800847c4e7e 0000000000000000 0000000000000000 : nt!KxMcheckAbort+0x7b

ffffc88008a85040 fffff80c660c13f3 : fffff80c660c13b4 0000000000000000 0000000000000000 0000000000000000 : nt!KiMcheckAbort+0x1bf

ffffab0a048616e8 fffff80c660c13b4 : 0000000000000000 0000000000000000 0000000000000000 00000000000000eb : intelppm!MWaitIdle+0x23

ffffab0a048616f0 fffff80084661e8f : 0000000000000000 ffffc88000000071 ffffc88008a7eec8 00000003e030d762 : intelppm!AcpiCStateIdleExecute+0x24

ffffab0a04861720 fffff80084660e05 : 0000000000000003 0000000000000002 0000000000000000 0000000000000008 : nt!PpmIdleExecuteTransition+0xeff

ffffab0a04861b00 fffff800847ba3ac : ffffffff00000000 ffffc88008a79180 ffffc88008a89200 ffff998ac3242400 : nt!PoIdle+0x345

ffffab0a04861c60 0000000000000000 : ffffab0a04862000 ffffab0a0485c000 0000000000000000 0000000000000000 : 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


Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

18 answers

Sort by: Most helpful
  1. Sumit D - IA 168.6K Reputation points Independent Advisor
    2018-09-14T09:16:54+00:00

    Okay, enough. Please stop the test(I thought it was written in the tutorial that it should be run <2 hours)

    Next check would be for memory.

    I suggest you to Run memory test for at least 8 passes, prefarably Overnight.

    https://www.tenforums.com/tutorials/14201-memte...

    If you have a DDR4 RAM, use MemTest86 rather than MemTest86+

    https://www.memtest86.com/

    When the test completes post back the Image(You can use your phone's camera).

    Disclaimer:

    This is a non-Microsoft website which would provide accurate and safe information. Watch out for ads on the site which are frequently classified as a PUP (Potentially Unwanted Products). There is no need to buy paid products to fix your computers as they do more harm than good sometimes.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-09-14T09:15:17+00:00

    It's running now for the last 9-10 hours without an error

    Was this answer helpful?

    0 comments No comments
  3. Sumit D - IA 168.6K Reputation points Independent Advisor
    2018-09-14T08:07:17+00:00

    Did it pass?

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-09-13T18:39:29+00:00

    Thanks for the reply, prime95 is running for the moment but for how long should I let it run?

    Was this answer helpful?

    0 comments No comments
  5. Sumit D - IA 168.6K Reputation points Independent Advisor
    2018-09-13T16:46:57+00:00

    BCC124 is usually Hardware.
    https://answers.microsoft.com/en-us/windows/wik...
    Run prime95 and post results.
    https://www.tenforums.com/tutorials/16474-prime...
    Disclaimer:
    This is a non-Microsoft website which would provide accurate and safe information. Watch out for ads on the site which are frequently classified as a PUP (Potentially Unwanted Products). There is no need to buy paid products to fix your computers as they do more harm than good sometimes.

    Was this answer helpful?

    0 comments No comments