BSOD during "normal usage", bug code 0x00000124, driver hal.dll

coco · 14 Apr 2019

Hi,

From last week, my system started to through various BSOD's during normal usage.

After some investigation, I tested the memory using MemTest and found that 1 module (out of 4) had more than 10.000 errors. I removed that module but the system was still crashing. For this reason, I returned the memory pack and bought a pack of 2 * 16 Corsair Vengeance LPX (2x, 16GB, DDR4-3200, DIMM 288) but I'm still experiencing the same problems.

As majority of the posts are mentioning that this is caused by drivers, I have to mention that before the BSOD started to appear, I did not upgrade any of the drivers or BIOS. Computer was built in Dec 2018 and since then I did not have any issues with it.

The only "update" that happen during that week was from Windows 10 and I suspect that it has something to do with that.

During this weekend I did the following in order to find the cause:
- tested the CPU with Intel Diagnostic Tool (0 errors)
- tested the new memory with MemTest (0 errors)
- re-installed windows with latest drivers for all components
- updated the bios to 1.50 (latest)

I can play for hours any of the latest games with or without DirectX12 enabled and there are no issues. But when the system is in "normal usage" (chrome, visual studio code, pycharm, spotify) it throws a BSOD at a random point and it drives me crazy as I cannot find the cause.

I found that during 3DMark TimeSpy DirectX12 it throws a BSOD instantly when it starts but not in other tests that are provided by 3DMark. Tested with the integrated Benchmark provided by majority of new games in DirectX12 and no issues.

The system was never overclocked except the XPS option which is enabled. All the other BIOS options are on "default" setting.

I also used the WinDbg to investigate the .dmp files and all are pointing to MODULE_NAME: GenuineIntel but it can be that I'm wrongly interpreting this information.

If you need any extra information, please let me know.

Thank you in advance

MrPepka · 14 Apr 2019

The KMODE_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000001E. This indicates that a kernel-mode program generated an exception which the error handler did not catch.

Code:

Microsoft (R) Windows Debugger Version 10.0.17763.132 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\041319-8453-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*
Symbol search path is: SRV*
Executable search path is: 
Windows 10 Kernel Version 17763 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17763.1.amd64fre.rs5_release.180914-1434
Machine Name:
Kernel base = 0xfffff807`7f41a000 PsLoadedModuleList = 0xfffff807`7f8359f0
Debug session time: Sat Apr 13 21:12:03.069 2019 (UTC + 2:00)
System Uptime: 0 days 0:37:28.812
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.......
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc000001d, fffff8077f5402d6, ffff9e8166d90400, 1}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!PpmIdleExecuteTransition+746 )

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

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc000001d, The exception code that was not handled
Arg2: fffff8077f5402d6, The address that the exception occurred at
Arg3: ffff9e8166d90400, Parameter 0 of the exception
Arg4: 0000000000000001, Parameter 1 of the exception

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


KEY_VALUES_STRING: 1


STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  17763.1.amd64fre.rs5_release.180914-1434

DUMP_TYPE:  2

BUGCHECK_P1: ffffffffc000001d

BUGCHECK_P2: fffff8077f5402d6

BUGCHECK_P3: ffff9e8166d90400

BUGCHECK_P4: 1

EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP: 
nt!PpmIdleExecuteTransition+746
fffff807`7f5402d6 07              ???

EXCEPTION_PARAMETER1:  ffff9e8166d90400

EXCEPTION_PARAMETER2:  0000000000000001

BUGCHECK_STR:  0x1E_c000001d

CPU_COUNT: 10

CPU_MHZ: e10

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: c

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  MICHAL

ANALYSIS_SESSION_TIME:  04-14-2019 20:26:16.0099

ANALYSIS_VERSION: 10.0.17763.132 amd64fre

LAST_CONTROL_TRANSFER:  from fffff8077f6a7dbe to fffff8077f5cd5e0

FAILED_INSTRUCTION_ADDRESS: 
nt!PpmIdleExecuteTransition+746
fffff807`7f5402d6 07              ???

STACK_TEXT:  
ffffed85`4644e4f8 fffff807`7f6a7dbe : 00000000`0000001e ffffffff`c000001d fffff807`7f5402d6 ffff9e81`66d90400 : nt!KeBugCheckEx
ffffed85`4644e500 fffff807`7f5d60cf : fffff807`7f8fd000 fffff807`7f41a000 0005be48`00a6f000 00000000`0010001f : nt!KiFatalExceptionHandler+0x22
ffffed85`4644e540 fffff807`7f440b20 : ffffed85`4644eb90 00000000`00000000 ffffed85`4644eab0 00000000`00000000 : nt!RtlpExecuteHandlerForException+0xf
ffffed85`4644e570 fffff807`7f485e74 : ffffed85`4644f4a8 ffffed85`4644f1f0 ffffed85`4644f4a8 ffff9e81`66d80180 : nt!RtlDispatchException+0x430
ffffed85`4644ecc0 fffff807`7f5dee42 : 00000000`00000000 00000000`00000000 00000000`00000000 00000005`3c656000 : nt!KiDispatchException+0x144
ffffed85`4644f370 fffff807`7f5d968e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
ffffed85`4644f550 fffff807`7f5402d6 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`000000ac : nt!KiInvalidOpcodeFault+0x30e
ffffed85`4644f6e0 fffff807`7f53f9ff : 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000008 : nt!PpmIdleExecuteTransition+0x746
ffffed85`4644fa00 fffff807`7f5d0fcc : ffffffff`00000000 ffff9e81`66d80180 ffff9e81`66d90400 ffff8d8c`13c32080 : nt!PoIdle+0x33f
ffffed85`4644fb60 00000000`00000000 : ffffed85`46450000 ffffed85`46449000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c


THREAD_SHA1_HASH_MOD_FUNC:  21d9502f1f72bcc22e5d110e27e803eefd1e97d7

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  151699116375d33870a941d07fd782622f252423

THREAD_SHA1_HASH_MOD:  bc100a5647b828107ac4e18055e00abcbe1ec406

FOLLOWUP_IP: 
nt!PpmIdleExecuteTransition+746
fffff807`7f5402d6 07              ???

FAULT_INSTR_CODE:  e0220f07

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  nt!PpmIdleExecuteTransition+746

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  10.0.17763.379

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  746

FAILURE_BUCKET_ID:  0x1E_c000001d_BAD_IP_nt!PpmIdleExecuteTransition

BUCKET_ID:  0x1E_c000001d_BAD_IP_nt!PpmIdleExecuteTransition

PRIMARY_PROBLEM_CLASS:  0x1E_c000001d_BAD_IP_nt!PpmIdleExecuteTransition

TARGET_TIME:  2019-04-13T19:12:03.000Z

OSBUILD:  17763

OSSERVICEPACK:  379

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:  unknown_date

BUILDDATESTAMP_STR:  180914-1434

BUILDLAB_STR:  rs5_release

BUILDOSVER_STR:  10.0.17763.1.amd64fre.rs5_release.180914-1434

ANALYSIS_SESSION_ELAPSED_TIME:  5fb7

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x1e_c000001d_bad_ip_nt!ppmidleexecutetransition

FAILURE_ID_HASH:  {840356b0-555a-1439-a734-c58aa813b227}

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

3: kd> .load pde
=========================================================================================
 PDE v11.3 - Copyright 2017 Andrew Richards
=========================================================================================
3: kd> !dpx
Start memory scan  : 0xffffed854644e4f8 ($csp)
End memory scan    : 0xffffed8546450000 (Kernel Stack Base)

               rsp : 0xffffed854644e4f8 : 0xfffff8077f6a7dbe : nt!KiFatalExceptionHandler+0x22
0xffffed854644e4f8 : 0xfffff8077f6a7dbe : nt!KiFatalExceptionHandler+0x22
0xffffed854644e510 : 0xfffff8077f5402d6 : nt!PpmIdleExecuteTransition+0x746
0xffffed854644e528 : 0xfffff8077feae4b0 : hal!HalpDmaMapScatterTransferV2+0x110
0xffffed854644e538 : 0xfffff8077f5d60cf : nt!RtlpExecuteHandlerForException+0xf
0xffffed854644e540 : 0xfffff8077f8fd000 : "nt!Ports <PERF> (nt+0x4e3000)"
0xffffed854644e548 : 0xfffff8077f41a000 : "nt!MmFreeIndependentPages <PERF> (nt+0x0)"
0xffffed854644e560 : 0xffffed854644eb30 : 0xfffff8077f5d0fcc : nt!KiIdleLoop+0x2c
0xffffed854644e568 : 0xfffff8077f440b20 : nt!RtlDispatchException+0x430
0xffffed854644e668 : 0xfffff8077fe8f4ba : hal!IoMapTransfer+0x4a
0xffffed854644e678 : 0xfffff8077f6ad74c : nt!KeRemoveDeviceQueue+0x6c
0xffffed854644e798 : 0xfffff8077feac3e5 : hal!HalAllocateAdapterChannel+0x45
0xffffed854644e7a0 : 0xfffff8077feaccf0 : hal!HalpAllocateAdapterCallbackV2
0xffffed854644e878 : 0xfffff803ac4b60f3 : ndis!NdisMAllocateNetBufferSGList+0x113
Unable to load image \SystemRoot\System32\drivers\e2xw10x64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for e2xw10x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e2xw10x64.sys
0xffffed854644ea28 : 0xfffff8077f4413e0 : nt!RtlGetExtendedContextLength2+0x3c
0xffffed854644ea38 : 0xfffff8077f53b204 : nt!RtlpGetStackLimits+0x14
0xffffed854644ea68 : 0xfffff8077f440796 : nt!RtlDispatchException+0xa6
0xffffed854644eab8 : 0xfffff8077f41a000 : "nt!MmFreeIndependentPages <PERF> (nt+0x0)"
0xffffed854644eb08 : 0xfffff8077f913650 : "nt!Ports <PERF> (nt+0x4f9650)"
0xffffed854644eb28 : 0xfffff803ac4b563e : ndis!ndisMSendNBLToMiniport+0xe
0xffffed854644eb30 : 0xfffff8077f5d0fcc : nt!KiIdleLoop+0x2c
0xffffed854644eb38 : 0xfffff8077f41a000 : "nt!MmFreeIndependentPages <PERF> (nt+0x0)"
0xffffed854644eb40 : 0xfffff8077f913650 : "nt!Ports <PERF> (nt+0x4f9650)"
0xffffed854644eb50 : 0xfffff803ad151400 : wfplwfs!LwfLowerReturnNetBufferLists+0xc0
0xffffed854644eb60 : 0xfffff8077f6a7d9c : nt!KiFatalExceptionHandler
0xffffed854644eb98 : 0xfffff8077f53f705 : nt!PoIdle+0x45
0xffffed854644eba0 : 0xfffff8077f5d1101 : nt!KiIdleLoop+0x161
0xffffed854644eba8 : 0xfffff8077f41a000 : "nt!MmFreeIndependentPages <PERF> (nt+0x0)"
0xffffed854644ebb0 : 0xfffff8077f90adc4 : "nt!Ports <PERF> (nt+0x4f0dc4)"
0xffffed854644ebb8 : 0xfffff8077f41a000 : "nt!MmFreeIndependentPages <PERF> (nt+0x0)"
0xffffed854644ebc0 : 0xfffff8077f90ad94 : "nt!Ports <PERF> (nt+0x4f0d94)"
0xffffed854644ebc8 : 0xfffff8077f41a000 : "nt!MmFreeIndependentPages <PERF> (nt+0x0)"
0xffffed854644ebd0 : 0xfffff8077f913650 : "nt!Ports <PERF> (nt+0x4f9650)"
0xffffed854644ec08 : 0xfffff8077f486321 : nt!KiPreprocessFault+0xb1
0xffffed854644ec18 : 0xfffff803ac4b5630 : ndis!ndisMSendNBLToMiniport
0xffffed854644ec30 : 0xffffed854644ec40 : 0xfffff8077f5402d6 : nt!PpmIdleExecuteTransition+0x746
0xffffed854644ec38 : 0xfffff8077f4414ba : nt!RtlInitializeExtendedContext2+0x32
0xffffed854644ec40 : 0xfffff8077f5402d6 : nt!PpmIdleExecuteTransition+0x746
0xffffed854644ec48 : 0xfffff8077f5402e6 : nt!PpmIdleExecuteTransition+0x756
0xffffed854644ec50 : 0xfffff8077f5402d7 : nt!PpmIdleExecuteTransition+0x747
0xffffed854644ec68 : 0xfffff8077f5402d6 : nt!PpmIdleExecuteTransition+0x746
0xffffed854644ec78 : 0xfffff8077f4861ee : nt!KdTrap+0x22
0xffffed854644ecb8 : 0xfffff8077f485e74 : nt!KiDispatchException+0x144
0xffffed854644ecf8 : 0xfffff803ac75d121 : tcpip!FlpSendPacketsHelper+0x2c1
0xffffed854644ed18 : 0xffff8d8c0d611820 : 0xfffff803ac8fa410 : tcpip!gWfpGlobalTriageBlock
0xffffed854644ed38 : 0xfffff8077f540f3f : nt!PpmUpdatePerformanceFeedback+0x14f
0xffffed854644eda8 : 0xfffff8077f41a000 : "nt!MmFreeIndependentPages <PERF> (nt+0x0)"
0xffffed854644ede8 : 0xfffff8077f5402d6 : nt!PpmIdleExecuteTransition+0x746
0xffffed854644efe8 : 0xfffff803ac9472a9 : tcpip!RssRunLoadDistribution+0xc9
0xffffed854644eff8 : 0xfffff803ac8ec280 : tcpip!Ipv4Global
0xffffed854644f048 : 0xfffff8077f5438ae : nt!KiIntSteerCalculateDistribution+0x1de
0xffffed854644f148 : 0xfffff8077f4413e0 : nt!RtlGetExtendedContextLength2+0x3c
0xffffed854644f188 : 0xfffff8077f4412d9 : nt!RtlGetExtendedContextLength+0x2d
0xffffed854644f298 : 0xfffff8077fe8b7a9 : hal!KeQueryPerformanceCounter+0x1d9
0xffffed854644f2a8 : 0xfffff8077f47ab19 : nt!KeQueryInterruptTimePrecise+0x59
0xffffed854644f2c8 : 0xfffff8077f53b511 : nt!EtwWriteEx+0xe1
0xffffed854644f2e8 : 0xffff8d8c0d409010 : 0xfffff8077f95d448 : nt!PpmPerfDomainHead
0xffffed854644f368 : 0xfffff8077f5dee42 : nt!KiExceptionDispatch+0xc2
0xffffed854644f398 : 0xfffff8077fe8c5ad : hal!HalRequestSoftwareInterrupt+0xcd
0xffffed854644f4b8 : 0xfffff8077f5402d6 : nt!PpmIdleExecuteTransition+0x746
0xffffed854644f4f8 : 0xfffff8077fe8b945 : hal!HalSendSoftwareInterrupt+0xa5
0xffffed854644f548 : 0xfffff8077f5d968e : nt!KiInvalidOpcodeFault+0x30e
0xffffed854644f550 : 0x0000000000000000 :  Trap @ ffffed854644f550
0xffffed854644f598 : 0xfffff8077f41a000 : "nt!MmFreeIndependentPages <PERF> (nt+0x0)"
0xffffed854644f5b8 : 0xfffff8077f58a4d8 : nt!PpmEventArbitratorPerfStateChange+0x188
0xffffed854644f628 : 0xfffff8077f540f3f : nt!PpmUpdatePerformanceFeedback+0x14f
0xffffed854644f698 : 0xfffff8077f6ed99b : nt!PpmIdleUpdateConcurrency+0x73
0xffffed854644f6b8 : 0xfffff8077f5402d6 : nt!PpmIdleExecuteTransition+0x746
0xffffed854644f718 : 0xfffff8077fe8b9f5 : hal!HalpApicRequestInterrupt+0x95
0xffffed854644f7d8 : 0xfffff8077fe8b7a9 : hal!KeQueryPerformanceCounter+0x1d9
0xffffed854644f808 : 0xfffff8077f540bce : nt!PpmIdlePrepare+0x43e
0xffffed854644f998 : 0xfffff8077fe8cae6 : hal!HalPerformEndOfInterrupt+0x16
0xffffed854644f9c0 : 0xfffff8077f41a000 : "nt!MmFreeIndependentPages <PERF> (nt+0x0)"
0xffffed854644f9f8 : 0xfffff8077f53f9ff : nt!PoIdle+0x33f
0xffffed854644fa38 : 0xfffff8077f534300 : nt!KiSearchForNewThreadOnProcessor+0x30
0xffffed854644fb18 : 0xfffff8077f5d460f : nt!SwapContext+0x1af
0xffffed854644fb58 : 0xfffff8077f5d0fcc : nt!KiIdleLoop+0x2c

Update Killer network card driver:

Code:

3: kd> lmvm e2xw10x64
Browse full module list
start             end                 module name
fffff803`b1a40000 fffff803`b1a69000   e2xw10x64 T (no symbols)           
    Loaded symbol image file: e2xw10x64.sys
    Image path: \SystemRoot\System32\drivers\e2xw10x64.sys
    Image name: e2xw10x64.sys
    Browse all global symbols  functions  data
    Timestamp:        Thu Sep 20 07:10:32 2018 (5BA32BC8)
    CheckSum:         0002FE78
    ImageSize:        00029000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

The WHEA_UNCORRECTABLE_ERROR bug check has a value of 0x00000124. This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). 1st parameter = 0x0 - A machine check exception occurred.

Code:

Microsoft (R) Windows Debugger Version 10.0.17763.132 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\041319-8828-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*
Symbol search path is: SRV*
Executable search path is: 
Windows 10 Kernel Version 17763 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17763.1.amd64fre.rs5_release.180914-1434
Machine Name:
Kernel base = 0xfffff804`18413000 PsLoadedModuleList = 0xfffff804`1882e9f0
Debug session time: Sat Apr 13 18:35:17.068 2019 (UTC + 2:00)
System Uptime: 0 days 0:14:14.810
Loading Kernel Symbols
...............................................................
................................................................
.............................................................
Loading User Symbols
Loading unloaded module list
......................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, ffff828a05703028, b2000000, 30005}

Probably caused by : GenuineIntel

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

7: 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: ffff828a05703028, 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


STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  17763.1.amd64fre.rs5_release.180914-1434

DUMP_TYPE:  2

BUGCHECK_P1: 0

BUGCHECK_P2: ffff828a05703028

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

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  3DMarkTimeSpy.exe

CURRENT_IRQL:  f

ANALYSIS_SESSION_HOST:  MICHAL

ANALYSIS_SESSION_TIME:  04-14-2019 20:40:16.0999

ANALYSIS_VERSION: 10.0.17763.132 amd64fre

STACK_TEXT:  
ffffb980`297dada8 fffff804`18ec5667 : 00000000`00000124 00000000`00000000 ffff828a`05703028 00000000`b2000000 : nt!KeBugCheckEx
ffffb980`297dadb0 fffff804`3aea146b : ffff828a`05703028 ffff828a`042e46e0 ffff828a`042e46e0 ffff828a`042e46e0 : hal!HalBugCheckSystem+0xd7
ffffb980`297dadf0 fffff804`187315ae : ffff828a`05703028 00000000`00000000 ffff828a`042e46e0 ffff828a`042e46e0 : PSHED!PshedBugCheckSystem+0xb
ffffb980`297dae20 fffff804`18ec6f59 : 00000000`00000728 00000000`00000007 00000000`00000000 00000000`00000000 : nt!WheaReportHwError+0x25e
ffffb980`297dae80 fffff804`18ec72de : 00000000`00000010 ffff828a`042e4730 ffffb980`297db028 00000000`00000007 : hal!HalpMcaReportError+0x5d
ffffb980`297dafd0 fffff804`18ec71ba : ffff828a`042e3920 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xf2
ffffb980`297db020 fffff804`18ec7424 : 00000000`00000010 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xda
ffffb980`297db060 fffff804`18ec669c : 00000000`00000000 ffffb980`297db2f0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xd4
ffffb980`297db090 fffff804`18ec76c7 : ffff828a`042e3920 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpHandleMachineCheck+0x5c
ffffb980`297db0c0 fffff804`1869f16b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x37
ffffb980`297db0f0 fffff804`185d4f7a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0xb
ffffb980`297db120 fffff804`185d4c60 : 00000000`00000000 00000000`00000000 00000000`16bafad0 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffffb980`297db260 00000001`4005aa65 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x260
00000000`16bafa78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00000001`4005aa65


THREAD_SHA1_HASH_MOD_FUNC:  4de11a045a075685c6206f99f334fdcf81e00201

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  0b8032aa666286f6596270ae3164aba9f3d108a7

THREAD_SHA1_HASH_MOD:  e68de900930b6f9798c6a02efd69edc806b33cb0

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_MAE

BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_MAE

PRIMARY_PROBLEM_CLASS:  0x124_GenuineIntel_PROCESSOR_MAE

TARGET_TIME:  2019-04-13T16:35:17.000Z

OSBUILD:  17763

OSSERVICEPACK:  379

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:  unknown_date

BUILDDATESTAMP_STR:  180914-1434

BUILDLAB_STR:  rs5_release

BUILDOSVER_STR:  10.0.17763.1.amd64fre.rs5_release.180914-1434

ANALYSIS_SESSION_ELAPSED_TIME:  afc

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x124_genuineintel_processor_mae

FAILURE_ID_HASH:  {7c95de0c-286c-8226-45c2-422b4de101d6}

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

7: kd> !errrec ffff828a05703028
===============================================================================
Common Platform Error Record @ ffff828a05703028
-------------------------------------------------------------------------------
Record Id     : 01d4f214e369b095
Severity      : Fatal (1)
Length        : 864
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 4/13/2019 16:35:17 (UTC)
Flags         : 0x00000000

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

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Micro-Architectural Error
Flags         : 0x00
CPU Version   : 0x00000000000906ec
Processor ID  : 0x0000000000000007

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ ffff828a057030f0
Section       @ ffff828a05703240
Offset        : 536
Length        : 64
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000007
CPU Id        : ec 06 09 00 00 08 10 07 - ff fb fa 7f ff fb eb bf
                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

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffff828a05703138
Section       @ ffff828a05703280
Offset        : 600
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : Unknown (Proc 7 Bank 0)
  Status      : 0xb200000000030005

coco · 14 Apr 2019

Thank you for the help MrPepka.

I checked the driver version in Device Manager and it was 9.0.0.49. This was installed using "Killer Software Package - For Windows 10 1803+" from support.killernetworking.com (theoretically it should be the latest version).

You suggested that I should update the driver, so I just performed the following:
- removed everything using KillerSoftwareUninstaller.1.0.2019.0411
- installed the drivers as provided by MSI Dragon Center application (as previously I had the ones from Killer Network, I assumed that I should use the ones provided by MSI)

In regards to WHEA_UNCORRECTABLE_ERROR, should I do anything or it is a result of the driver issue ?

MrPepka · 14 Apr 2019

Have you tested your drive with the HD Tune program?

coco · 14 Apr 2019

No, I never tested the storage drives.

I just installed HD Tune(trial) and I see that it has a variety of options. Should I run something specific (i.e. Benchmark test, Error test ) ?

MrPepka · 14 Apr 2019

Show the S.M.A.R.T disk

coco · 14 Apr 2019

Attached the SMART of all three, however for the M2 drive I picked the information from Samsung Magician as it was not listed inside the HD Tune.

All look ok.