Question getting this BSOD every week or 2 for months, nothing has worked please help !

[kpsdf23451]

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
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000010, Device Driver Error
Arg2: ffffde0ea04c7028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: ffffde0e7d7c1b5c
Arg4: ffffde0e7d8211a0

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

*** WARNING: Check Image - Checksum mismatch - Dump: 0xd94f, File: 0x72fd - C:\ProgramData\Dbg\sym\hal.dll\1A7BE8E96000\hal.dll

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3265

Key : Analysis.Elapsed.mSec
Value: 3332

Key : Analysis.IO.Other.Mb
Value: 0

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 0

Key : Analysis.Init.CPU.mSec
Value: 265

Key : Analysis.Init.Elapsed.mSec
Value: 4193

Key : Analysis.Memory.CommitPeak.Mb
Value: 91

Key : Analysis.Version.DbgEng
Value: 10.0.27704.1001

Key : Analysis.Version.Description
Value: 10.2408.27.01 amd64fre

Key : Analysis.Version.Ext
Value: 1.2408.27.1

Key : Bugcheck.Code.KiBugCheckData
Value: 0x124

Key : Bugcheck.Code.LegacyAPI
Value: 0x124

Key : Bugcheck.Code.TargetModel
Value: 0x124

Key : Failure.Bucket
Value: 0x124_16_GenuineIntel__UNKNOWN_IMAGE_GenuineIntel.sys

Key : Failure.Hash
Value: {37af9407-4a3e-0b08-acdd-dadffdc34c3c}

Key : Hypervisor.Enlightenments.Value
Value: 0

Key : Hypervisor.Enlightenments.ValueHex
Value: 0

Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 0

Key : Hypervisor.Flags.ApicEnlightened
Value: 0

Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 1

Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key : Hypervisor.Flags.CpuManager
Value: 0

Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 0

Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 0

Key : Hypervisor.Flags.Epf
Value: 0

Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 0

Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1

Key : Hypervisor.Flags.MaxBankNumber
Value: 0

Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0

Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 0

Key : Hypervisor.Flags.Phase0InitDone
Value: 0

Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key : Hypervisor.Flags.RootScheduler
Value: 0

Key : Hypervisor.Flags.SynicAvailable
Value: 0

Key : Hypervisor.Flags.UseQpcBias
Value: 0

Key : Hypervisor.Flags.Value
Value: 16908288

Key : Hypervisor.Flags.ValueHex
Value: 1020000

Key : Hypervisor.Flags.VpAssistPage
Value: 0

Key : Hypervisor.Flags.VsmAvailable
Value: 0

Key : Hypervisor.RootFlags.AccessStats
Value: 0

Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 0

Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 0

Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key : Hypervisor.RootFlags.HostTimelineSync
Value: 0

Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key : Hypervisor.RootFlags.IsHyperV
Value: 0

Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 0

Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 0

Key : Hypervisor.RootFlags.MceEnlightened
Value: 0

Key : Hypervisor.RootFlags.Nested
Value: 0

Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 0

Key : Hypervisor.RootFlags.Value
Value: 0

Key : Hypervisor.RootFlags.ValueHex
Value: 0

Key : SecureKernel.HalpHvciEnabled
Value: 0

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 124

BUGCHECK_P1: 10

BUGCHECK_P2: ffffde0ea04c7028

BUGCHECK_P3: ffffde0e7d7c1b5c

BUGCHECK_P4: ffffde0e7d8211a0

FILE_IN_CAB: MEMORY.DMP

FAULTING_THREAD: ffffde0e9ac28040

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: System

STACK_TEXT:
ffffdb8c`c90cf3d8 fffff801`76dbc91f : 00000000`00000124 00000000`00000010 ffffde0e`a04c7028 ffffde0e`7d7c1b5c : nt!KeBugCheckEx
ffffdb8c`c90cf3e0 fffff801`76dbd389 : ffffde0e`ab3c6890 ffffde0e`ab3c6890 ffffde0e`7d7c1b30 ffffde0e`ae757378 : nt!WheaReportHwError+0x4cf
ffffdb8c`c90cf4b0 fffff801`76dbd4a5 : 00000000`00000000 00000000`00000062 ffffde0e`ab3c6890 00000000`00000000 : nt!WheaHwErrorReportSubmitDeviceDriver+0xe9
ffffdb8c`c90cf4e0 fffff801`7ac63791 : 00000000`00000000 ffffdb8c`c90cf700 ffffde0e`7d8211a0 ffffde0e`7d7bb0ff : nt!WheaReportFatalHwErrorDeviceDriverEx+0xf5
ffffdb8c`c90cf540 fffff801`7ac5cb70 : 00000000`00000000 ffffde0e`7d8211a0 ffffde0e`7d8311a0 00000000`00000000 : storport!StorpWheaReportError+0x9d
ffffdb8c`c90cf5d0 fffff801`7ac2f0cc : fffff801`7ac89000 00000000`00000062 00000000`00000000 ffffdb8c`c90cf970 : storport!StorpMarkDeviceFailed+0x358
ffffdb8c`c90cf860 fffff801`7aceb57d : 00000000`00000100 ffffde0e`7d7bb020 00000000`00000000 00000000`00000000 : storport!StorPortNotification+0x91c
ffffdb8c`c90cf930 fffff801`7acee78e : ffffde0e`c1000002 00000000`00000000 ffffde0e`7d7bb020 00000000`00000003 : stornvme!ControllerReset+0x1a1
ffffdb8c`c90cf9b0 fffff801`7aced6ef : ffffde0e`7d7bb020 ffffde0e`7d821050 ffffde0e`a5b24630 00000000`00000000 : stornvme!NVMeControllerReset+0x10a
ffffdb8c`c90cf9e0 fffff801`7ac5a246 : ffffde0e`a5b24630 ffffde0e`7d821050 ffffde0e`9d20e040 ffffde0e`794cca60 : stornvme!NVMeControllerAsyncResetWorker+0x3f
ffffdb8c`c90cfa10 fffff801`76b43ea5 : ffffde0e`b05dcd80 ffffde0e`b05dcd80 ffffde0e`7d821050 fffff801`bd605dc0 : storport!StorPortWorkItemRoutine+0x46
ffffdb8c`c90cfa40 fffff801`76a22525 : ffffde0e`9ac28040 ffffde0e`9ac28040 fffff801`76b43d70 00000000`00000000 : nt!IopProcessWorkItem+0x135
ffffdb8c`c90cfab0 fffff801`76b29905 : ffffde0e`9ac28040 00000000`00000080 ffffde0e`794de080 00000000`00000004 : nt!ExpWorkerThread+0x105
ffffdb8c`c90cfb50 fffff801`76c07318 : ffff9d01`90640180 ffffde0e`9ac28040 fffff801`76b298b0 fffff801`76a532b1 : nt!PspSystemThreadStartup+0x55
ffffdb8c`c90cfba0 00000000`00000000 : ffffdb8c`c90d0000 ffffdb8c`c90c9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .process /r /p 0xffffde0e794de080; .thread 0xffffde0e9ac28040 ; kb

FAILURE_BUCKET_ID: 0x124_16_GenuineIntel__UNKNOWN_IMAGE_GenuineIntel.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {37af9407-4a3e-0b08-acdd-dadffdc34c3c}

Followup: MachineOwner

 

[artk2219]

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
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000010, Device Driver Error
Arg2: ffffde0ea04c7028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: ffffde0e7d7c1b5c
Arg4: ffffde0e7d8211a0

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

*** WARNING: Check Image - Checksum mismatch - Dump: 0xd94f, File: 0x72fd - C:\ProgramData\Dbg\sym\hal.dll\1A7BE8E96000\hal.dll

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3265

Key : Analysis.Elapsed.mSec
Value: 3332

Key : Analysis.IO.Other.Mb
Value: 0

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 0

Key : Analysis.Init.CPU.mSec
Value: 265

Key : Analysis.Init.Elapsed.mSec
Value: 4193

Key : Analysis.Memory.CommitPeak.Mb
Value: 91

Key : Analysis.Version.DbgEng
Value: 10.0.27704.1001

Key : Analysis.Version.Description
Value: 10.2408.27.01 amd64fre

Key : Analysis.Version.Ext
Value: 1.2408.27.1

Key : Bugcheck.Code.KiBugCheckData
Value: 0x124

Key : Bugcheck.Code.LegacyAPI
Value: 0x124

Key : Bugcheck.Code.TargetModel
Value: 0x124

Key : Failure.Bucket
Value: 0x124_16_GenuineIntel__UNKNOWN_IMAGE_GenuineIntel.sys

Key : Failure.Hash
Value: {37af9407-4a3e-0b08-acdd-dadffdc34c3c}

Key : Hypervisor.Enlightenments.Value
Value: 0

Key : Hypervisor.Enlightenments.ValueHex
Value: 0

Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 0

Key : Hypervisor.Flags.ApicEnlightened
Value: 0

Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 1

Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key : Hypervisor.Flags.CpuManager
Value: 0

Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 0

Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 0

Key : Hypervisor.Flags.Epf
Value: 0

Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 0

Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1

Key : Hypervisor.Flags.MaxBankNumber
Value: 0

Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0

Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 0

Key : Hypervisor.Flags.Phase0InitDone
Value: 0

Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key : Hypervisor.Flags.RootScheduler
Value: 0

Key : Hypervisor.Flags.SynicAvailable
Value: 0

Key : Hypervisor.Flags.UseQpcBias
Value: 0

Key : Hypervisor.Flags.Value
Value: 16908288

Key : Hypervisor.Flags.ValueHex
Value: 1020000

Key : Hypervisor.Flags.VpAssistPage
Value: 0

Key : Hypervisor.Flags.VsmAvailable
Value: 0

Key : Hypervisor.RootFlags.AccessStats
Value: 0

Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 0

Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 0

Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key : Hypervisor.RootFlags.HostTimelineSync
Value: 0

Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key : Hypervisor.RootFlags.IsHyperV
Value: 0

Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 0

Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 0

Key : Hypervisor.RootFlags.MceEnlightened
Value: 0

Key : Hypervisor.RootFlags.Nested
Value: 0

Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 0

Key : Hypervisor.RootFlags.Value
Value: 0

Key : Hypervisor.RootFlags.ValueHex
Value: 0

Key : SecureKernel.HalpHvciEnabled
Value: 0

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 124

BUGCHECK_P1: 10

BUGCHECK_P2: ffffde0ea04c7028

BUGCHECK_P3: ffffde0e7d7c1b5c

BUGCHECK_P4: ffffde0e7d8211a0

FILE_IN_CAB: MEMORY.DMP

FAULTING_THREAD: ffffde0e9ac28040

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: System

STACK_TEXT:
ffffdb8c`c90cf3d8 fffff801`76dbc91f : 00000000`00000124 00000000`00000010 ffffde0e`a04c7028 ffffde0e`7d7c1b5c : nt!KeBugCheckEx
ffffdb8c`c90cf3e0 fffff801`76dbd389 : ffffde0e`ab3c6890 ffffde0e`ab3c6890 ffffde0e`7d7c1b30 ffffde0e`ae757378 : nt!WheaReportHwError+0x4cf
ffffdb8c`c90cf4b0 fffff801`76dbd4a5 : 00000000`00000000 00000000`00000062 ffffde0e`ab3c6890 00000000`00000000 : nt!WheaHwErrorReportSubmitDeviceDriver+0xe9
ffffdb8c`c90cf4e0 fffff801`7ac63791 : 00000000`00000000 ffffdb8c`c90cf700 ffffde0e`7d8211a0 ffffde0e`7d7bb0ff : nt!WheaReportFatalHwErrorDeviceDriverEx+0xf5
ffffdb8c`c90cf540 fffff801`7ac5cb70 : 00000000`00000000 ffffde0e`7d8211a0 ffffde0e`7d8311a0 00000000`00000000 : storport!StorpWheaReportError+0x9d
ffffdb8c`c90cf5d0 fffff801`7ac2f0cc : fffff801`7ac89000 00000000`00000062 00000000`00000000 ffffdb8c`c90cf970 : storport!StorpMarkDeviceFailed+0x358
ffffdb8c`c90cf860 fffff801`7aceb57d : 00000000`00000100 ffffde0e`7d7bb020 00000000`00000000 00000000`00000000 : storport!StorPortNotification+0x91c
ffffdb8c`c90cf930 fffff801`7acee78e : ffffde0e`c1000002 00000000`00000000 ffffde0e`7d7bb020 00000000`00000003 : stornvme!ControllerReset+0x1a1
ffffdb8c`c90cf9b0 fffff801`7aced6ef : ffffde0e`7d7bb020 ffffde0e`7d821050 ffffde0e`a5b24630 00000000`00000000 : stornvme!NVMeControllerReset+0x10a
ffffdb8c`c90cf9e0 fffff801`7ac5a246 : ffffde0e`a5b24630 ffffde0e`7d821050 ffffde0e`9d20e040 ffffde0e`794cca60 : stornvme!NVMeControllerAsyncResetWorker+0x3f
ffffdb8c`c90cfa10 fffff801`76b43ea5 : ffffde0e`b05dcd80 ffffde0e`b05dcd80 ffffde0e`7d821050 fffff801`bd605dc0 : storport!StorPortWorkItemRoutine+0x46
ffffdb8c`c90cfa40 fffff801`76a22525 : ffffde0e`9ac28040 ffffde0e`9ac28040 fffff801`76b43d70 00000000`00000000 : nt!IopProcessWorkItem+0x135
ffffdb8c`c90cfab0 fffff801`76b29905 : ffffde0e`9ac28040 00000000`00000080 ffffde0e`794de080 00000000`00000004 : nt!ExpWorkerThread+0x105
ffffdb8c`c90cfb50 fffff801`76c07318 : ffff9d01`90640180 ffffde0e`9ac28040 fffff801`76b298b0 fffff801`76a532b1 : nt!PspSystemThreadStartup+0x55
ffffdb8c`c90cfba0 00000000`00000000 : ffffdb8c`c90d0000 ffffdb8c`c90c9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .process /r /p 0xffffde0e794de080; .thread 0xffffde0e9ac28040 ; kb

FAILURE_BUCKET_ID: 0x124_16_GenuineIntel__UNKNOWN_IMAGE_GenuineIntel.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {37af9407-4a3e-0b08-acdd-dadffdc34c3c}

Followup: MachineOwner

Have you run memtest86 or any memory checking program?

 

[kpsdf23451]

Have you run memtest86 or any memory checking program?

ive done windows memory diagnostic 2 times ya

 

[artk2219]

ive done windows memory diagnostic 2 times ya

I meant a bootable one, like memtest86, you would leave that to run overnight or over a weekend to check for issues.

 

[ubuysa]

As above, RAM is the most likely cause. That's because the 0x124 bugcheck indicates a fatal hardware error and because the dump also contains a checksum mismatch for the hal.dll executable...

*** WARNING: Check Image - Checksum mismatch - Dump: 0xd94f, File: 0x72fd - C:\ProgramData\Dbg\sym\hal.dll\1A7BE8E96000\hal.dll

This indicates that the checksum for hal.dll in the dump does not match the actual checksum in the Microsoft libraries. That's most usually caused by bad RAM. Test you RAM as follows...

1. Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
3. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86 and do another four iterations. Even a single bit error is a failure.

 

[triplex1]

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
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000010, Device Driver Error
Arg2: ffffde0ea04c7028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: ffffde0e7d7c1b5c
Arg4: ffffde0e7d8211a0

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

*** WARNING: Check Image - Checksum mismatch - Dump: 0xd94f, File: 0x72fd - C:\ProgramData\Dbg\sym\hal.dll\1A7BE8E96000\hal.dll

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3265

Key : Analysis.Elapsed.mSec
Value: 3332

Key : Analysis.IO.Other.Mb
Value: 0

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 0

Key : Analysis.Init.CPU.mSec
Value: 265

Key : Analysis.Init.Elapsed.mSec
Value: 4193

Key : Analysis.Memory.CommitPeak.Mb
Value: 91

Key : Analysis.Version.DbgEng
Value: 10.0.27704.1001

Key : Analysis.Version.Description
Value: 10.2408.27.01 amd64fre

Key : Analysis.Version.Ext
Value: 1.2408.27.1

Key : Bugcheck.Code.KiBugCheckData
Value: 0x124

Key : Bugcheck.Code.LegacyAPI
Value: 0x124

Key : Bugcheck.Code.TargetModel
Value: 0x124

Key : Failure.Bucket
Value: 0x124_16_GenuineIntel__UNKNOWN_IMAGE_GenuineIntel.sys

Key : Failure.Hash
Value: {37af9407-4a3e-0b08-acdd-dadffdc34c3c}

Key : Hypervisor.Enlightenments.Value
Value: 0

Key : Hypervisor.Enlightenments.ValueHex
Value: 0

Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 0

Key : Hypervisor.Flags.ApicEnlightened
Value: 0

Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 1

Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key : Hypervisor.Flags.CpuManager
Value: 0

Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 0

Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 0

Key : Hypervisor.Flags.Epf
Value: 0

Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 0

Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1

Key : Hypervisor.Flags.MaxBankNumber
Value: 0

Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0

Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 0

Key : Hypervisor.Flags.Phase0InitDone
Value: 0

Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key : Hypervisor.Flags.RootScheduler
Value: 0

Key : Hypervisor.Flags.SynicAvailable
Value: 0

Key : Hypervisor.Flags.UseQpcBias
Value: 0

Key : Hypervisor.Flags.Value
Value: 16908288

Key : Hypervisor.Flags.ValueHex
Value: 1020000

Key : Hypervisor.Flags.VpAssistPage
Value: 0

Key : Hypervisor.Flags.VsmAvailable
Value: 0

Key : Hypervisor.RootFlags.AccessStats
Value: 0

Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 0

Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 0

Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key : Hypervisor.RootFlags.HostTimelineSync
Value: 0

Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key : Hypervisor.RootFlags.IsHyperV
Value: 0

Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 0

Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 0

Key : Hypervisor.RootFlags.MceEnlightened
Value: 0

Key : Hypervisor.RootFlags.Nested
Value: 0

Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 0

Key : Hypervisor.RootFlags.Value
Value: 0

Key : Hypervisor.RootFlags.ValueHex
Value: 0

Key : SecureKernel.HalpHvciEnabled
Value: 0

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 124

BUGCHECK_P1: 10

BUGCHECK_P2: ffffde0ea04c7028

BUGCHECK_P3: ffffde0e7d7c1b5c

BUGCHECK_P4: ffffde0e7d8211a0

FILE_IN_CAB: MEMORY.DMP

FAULTING_THREAD: ffffde0e9ac28040

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: System

STACK_TEXT:
ffffdb8c`c90cf3d8 fffff801`76dbc91f : 00000000`00000124 00000000`00000010 ffffde0e`a04c7028 ffffde0e`7d7c1b5c : nt!KeBugCheckEx
ffffdb8c`c90cf3e0 fffff801`76dbd389 : ffffde0e`ab3c6890 ffffde0e`ab3c6890 ffffde0e`7d7c1b30 ffffde0e`ae757378 : nt!WheaReportHwError+0x4cf
ffffdb8c`c90cf4b0 fffff801`76dbd4a5 : 00000000`00000000 00000000`00000062 ffffde0e`ab3c6890 00000000`00000000 : nt!WheaHwErrorReportSubmitDeviceDriver+0xe9
ffffdb8c`c90cf4e0 fffff801`7ac63791 : 00000000`00000000 ffffdb8c`c90cf700 ffffde0e`7d8211a0 ffffde0e`7d7bb0ff : nt!WheaReportFatalHwErrorDeviceDriverEx+0xf5
ffffdb8c`c90cf540 fffff801`7ac5cb70 : 00000000`00000000 ffffde0e`7d8211a0 ffffde0e`7d8311a0 00000000`00000000 : storport!StorpWheaReportError+0x9d
ffffdb8c`c90cf5d0 fffff801`7ac2f0cc : fffff801`7ac89000 00000000`00000062 00000000`00000000 ffffdb8c`c90cf970 : storport!StorpMarkDeviceFailed+0x358
ffffdb8c`c90cf860 fffff801`7aceb57d : 00000000`00000100 ffffde0e`7d7bb020 00000000`00000000 00000000`00000000 : storport!StorPortNotification+0x91c
ffffdb8c`c90cf930 fffff801`7acee78e : ffffde0e`c1000002 00000000`00000000 ffffde0e`7d7bb020 00000000`00000003 : stornvme!ControllerReset+0x1a1
ffffdb8c`c90cf9b0 fffff801`7aced6ef : ffffde0e`7d7bb020 ffffde0e`7d821050 ffffde0e`a5b24630 00000000`00000000 : stornvme!NVMeControllerReset+0x10a
ffffdb8c`c90cf9e0 fffff801`7ac5a246 : ffffde0e`a5b24630 ffffde0e`7d821050 ffffde0e`9d20e040 ffffde0e`794cca60 : stornvme!NVMeControllerAsyncResetWorker+0x3f
ffffdb8c`c90cfa10 fffff801`76b43ea5 : ffffde0e`b05dcd80 ffffde0e`b05dcd80 ffffde0e`7d821050 fffff801`bd605dc0 : storport!StorPortWorkItemRoutine+0x46
ffffdb8c`c90cfa40 fffff801`76a22525 : ffffde0e`9ac28040 ffffde0e`9ac28040 fffff801`76b43d70 00000000`00000000 : nt!IopProcessWorkItem+0x135
ffffdb8c`c90cfab0 fffff801`76b29905 : ffffde0e`9ac28040 00000000`00000080 ffffde0e`794de080 00000000`00000004 : nt!ExpWorkerThread+0x105
ffffdb8c`c90cfb50 fffff801`76c07318 : ffff9d01`90640180 ffffde0e`9ac28040 fffff801`76b298b0 fffff801`76a532b1 : nt!PspSystemThreadStartup+0x55
ffffdb8c`c90cfba0 00000000`00000000 : ffffdb8c`c90d0000 ffffdb8c`c90c9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .process /r /p 0xffffde0e794de080; .thread 0xffffde0e9ac28040 ; kb

FAILURE_BUCKET_ID: 0x124_16_GenuineIntel__UNKNOWN_IMAGE_GenuineIntel.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {37af9407-4a3e-0b08-acdd-dadffdc34c3c}

Followup: MachineOwner

Turn off Windows Hypervisor

1. On your PC, open the Control Panel.
2. Select Programs. Programs and Features.
3. Select Turn Windows features on or off.
4. Expand the sections for Hyper-V. Hyper-V Platform.
5. Deselect Hyper-V Hypervisor. On Windows 10 Home devices, deselect Windows Hypervisor Platform.
6. Restart your computer.

 

[johnbl]

looks like the nvme drive controller stopped responding windows attempted to reset and it still did not respond and windows called the bugcheck.
normally you would start by:
update the bios, update the cpu chipset drivers, update any controller driver on the motherboard, update any firmware for the nvme

if you provide a kernel dump i can look at the internal logs.
on the minidump someone can look at the WHEA_ERROR

check to make sure the nvme is not overheating. It could be something like thermal expansion causing the connections to not align up. (it would act like the device was disconnected while windows was running)

you can start cmd.exe as an admin then run
sfc.exe /scannow
dism.exe/ online /cleanup-image /restorehealth
to repair any modified core windows files.

 

[kpsdf23451]

I meant a bootable one, like memtest86, you would leave that to run overnight or over a weekend to check for issues.

As above, RAM is the most likely cause. That's because the 0x124 bugcheck indicates a fatal hardware error and because the dump also contains a checksum mismatch for the hal.dll executable...

*** WARNING: Check Image - Checksum mismatch - Dump: 0xd94f, File: 0x72fd - C:\ProgramData\Dbg\sym\hal.dll\1A7BE8E96000\hal.dll

This indicates that the checksum for hal.dll in the dump does not match the actual checksum in the Microsoft libraries. That's most usually caused by bad RAM. Test you RAM as follows...

1. Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
3. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86 and do another four iterations. Even a single bit error is a failure.

ran memtest86 2 times, 0 errors

looks like the nvme drive controller stopped responding windows attempted to reset and it still did not respond and windows called the bugcheck.
normally you would start by:
update the bios, update the cpu chipset drivers, update any controller driver on the motherboard, update any firmware for the nvme

if you provide a kernel dump i can look at the internal logs.
on the minidump someone can look at the WHEA_ERROR

check to make sure the nvme is not overheating. It could be something like thermal expansion causing the connections to not align up. (it would act like the device was disconnected while windows was running)

you can start cmd.exe as an admin then run
sfc.exe /scannow
dism.exe/ online /cleanup-image /restorehealth
to repair any modified core windows files.

everything on my motherboard is updated, and nvme firmware, and ive done the cmd.exe stuff

i changed my settings to give a kernel memory dump, i guess i just need to wait to get another bsod?

 

[johnbl]

ran memtest86 2 times, 0 errors

everything on my motherboard is updated, and nvme firmware, and ive done the cmd.exe stuff

i changed my settings to give a kernel memory dump, i guess i just need to wait to get another bsod?

yes but look to see if the file is already there. it will be named memory.dmp
problem is that it might not get written if the device is not responding.

note: you can google how to force windows to do a kernel memory dump using a keyboard.
set the registry settings. often the logs will fill up with errors before the device actually fails.

this means you can run the system for a while and force a memory dump on the working system and then look at the internal logs for errors. for heat related problems the logs might have minor errors that get corrected on a retry. Later if the device does not respond within the timeout windows will attempt to reset the device. The pci/e bus can be screwy since so many devices now run thru it.
if you want, i can look at the logs of a kernel dump of a working system. just let it run for maybe 20 minutes to get everything warm/hot and force the dump with your keyboard.

you could also put the minidump on a server, mark if for public access and post a link.
the minidump can have some useful info inside even though the logs are not included.

 

[kpsdf23451]

yes but look to see if the file is already there. it will be named memory.dmp
problem is that it might not get written if the device is not responding.

note: you can google how to force windows to do a kernel memory dump using a keyboard.
set the registry settings. often the logs will fill up with errors before the device actually fails.

this means you can run the system for a while and force a memory dump on the working system and then look at the internal logs for errors. for heat related problems the logs might have minor errors that get corrected on a retry. Later if the device does not respond within the timeout windows will attempt to reset the device. The pci/e bus can be screwy since so many devices now run thru it.
if you want, i can look at the logs of a kernel dump of a working system. just let it run for maybe 20 minutes to get everything warm/hot and force the dump with your keyboard.

you could also put the minidump on a server, mark if for public access and post a link.
the minidump can have some useful info inside even though the logs are not included.

MEMORY.DMP

drive.google.com

heres memory.dmp
does that work ?

 

[johnbl]

the system was running for 22 hours (it might suggest a sleep related issue or heating)
I would remove the two overclocking drivers, just for testing.
i would remove the apple drivers if they are for usb charging of an apple device.

I will take a look at the logs but remove the above to see if it helps.
(apple chargers violate USB power specs, and now the USB is routed thru the PCI/e bus and can mess anything up connected to the pci/e )




---------------------
Processor Version Intel(R) Core(TM) i7-14700KF
Processor Voltage 8ah - 1.0V
External Clock 100MHz
Max Speed 8500MHz
Current Speed 3400MHz
Core Count 2 20
Processor Characteristics fc
Enabled Characteristics:
0x 2: 64-bit Capable
0x 3: Multi-Core
0x 4: Hardware Thread
0x 5: Execute Protection
0x 6: Enhanced Virtualization
0x 7: Power/Performance Control
Vendor American Megatrends International, LLC.
BIOS Version FKa
BIOS Starting Address Segment f000
BIOS Release Date 09/26/2024
Manufacturer Gigabyte Technology Co., Ltd.
Product Name Z790 AORUS ELITE AX
Family Z790 MB

overclock drivers installed:
gdrv3.sys Mon Jul 29 22:50:48 2024
iocbios2.sys Fri Jun 16 15:05:53 2023

note:
appleLowerFilter.sys
AppleKmdfFilter.sys

 

[johnbl]

your system is having some issue with this device:
PnpProblemCode : 24
PnpVetoType : 0
DeviceId : USB\VID_054C&PID_0CE6\5&30741cdd&0&10

Sony Corp.
DualSense wireless controller (PS5)
see this: https://www.playstation.com/en-us/support/hardware/pair-dualsense-controller-bluetooth/#usb
maybe see if there is a firmware update.

You have a lot of usb traffic on a usb 2 hub. you might want to move some devices to a usb3 hub. you might see if there is firmware update for the devices.

overall, I can not tell why the drive did not respond.

it looks like a bug or timing issue.





=============

looks like the file system told the nvme to flush data to disk and never got a response. other threads tried to access the resource
Contention Count = 77897977 times.

be back looking at the logs in 10 mins

threads waiting for access:

RazerAppEngine.exe
steamwebhelper.exe
csrss.exe (the system also was trying to process mouse input data)
and
SamsungMagician.exe

note:
InstancePath is "SCSI\Disk&Ven_NVMe&Prod_Samsung_SSD_990\5&144c0637&0&000000"

devices:
Razer DeathAdder V2
Razer Huntsman V3 Pro TKL
Yeti Stereo Microphone
DualSense Wireless Controller
looks like they are connected to a usb 2 hub that is suspended

note: filter driver running ucpd
https://www.ghacks.net/2024/04/08/new-sneaky-windows-driver-ucdp-stops-non-microsoft-software-from-setting-defaults/#:~:text=Microsoft has integrated the driver userChoice Protection Driver,,purpose: to block access to UserChoice Registry keys.

 

[kpsdf23451]

the system was running for 22 hours (it might suggest a sleep related issue or heating)
I would remove the two overclocking drivers, just for testing.
i would remove the apple drivers if they are for usb charging of an apple device.

I will take a look at the logs but remove the above to see if it helps.
(apple chargers violate USB power specs, and now the USB is routed thru the PCI/e bus and can mess anything up connected to the pci/e )




---------------------
Processor Version Intel(R) Core(TM) i7-14700KF
Processor Voltage 8ah - 1.0V
External Clock 100MHz
Max Speed 8500MHz
Current Speed 3400MHz
Core Count 2 20
Processor Characteristics fc
Enabled Characteristics:
0x 2: 64-bit Capable
0x 3: Multi-Core
0x 4: Hardware Thread
0x 5: Execute Protection
0x 6: Enhanced Virtualization
0x 7: Power/Performance Control
Vendor American Megatrends International, LLC.
BIOS Version FKa
BIOS Starting Address Segment f000
BIOS Release Date 09/26/2024
Manufacturer Gigabyte Technology Co., Ltd.
Product Name Z790 AORUS ELITE AX
Family Z790 MB

overclock drivers installed:
gdrv3.sys Mon Jul 29 22:50:48 2024
iocbios2.sys Fri Jun 16 15:05:53 2023

note:
appleLowerFilter.sys
AppleKmdfFilter.sys

how can i delete the apple drivers?

 

[johnbl]

how can i delete the apple drivers?

I added more notes:
you can fix the sony adapter driver. (update firmware if you can, for this device and the mouse) Note: some devices have a switch for pc or ps/mac mode check docs.
maybe move some devices off of the USB 2 hub and put them on usb 3.

overall, it looks like the drive never confirmed that some data was written to the drive and it just blocked other threads in the system. Windows thought the drive failed and bugchecked the system. normally I would be looking at the firmware (bios or drive firmware update) but you also samsung magician running so it could be involved also.

you might also check for errors on your drive ie run windows chkdsk utility on the drive.

https://learn.microsoft.com/en-us/w...ion/windows-commands/chkdsk?tabs=event-viewer

 

[kpsdf23451]

I added more notes:
you can fix the sony adapter driver. (update firmware if you can, for this device and the mouse) Note: some devices have a switch for pc or ps/mac mode check docs.
maybe move some devices off of the USB 2 hub and put them on usb 3.

overall, it looks like the drive never confirmed that some data was written to the drive and it just blocked other threads in the system. Windows thought the drive failed and bugchecked the system. normally I would be looking at the firmware (bios or drive firmware update) but you also samsung magician running so it could be involved also.

you might also check for errors on your drive ie run windows chkdsk utility on the drive.

https://learn.microsoft.com/en-us/w...ion/windows-commands/chkdsk?tabs=event-viewer

so could it be related to my ssd temperature???


one thing I definitely know its not is Samsung Magician, I only just downloaded that and i just updated my SSD firmware with it about a month ago, awhile after I've been having this same BSOD issue

 

[kpsdf23451]

your system is having some issue with this device:
PnpProblemCode : 24
PnpVetoType : 0
DeviceId : USB\VID_054C&PID_0CE6\5&30741cdd&0&10

Sony Corp.
DualSense wireless controller (PS5)
see this: https://www.playstation.com/en-us/support/hardware/pair-dualsense-controller-bluetooth/#usb
maybe see if there is a firmware update.

You have a lot of usb traffic on a usb 2 hub. you might want to move some devices to a usb3 hub. you might see if there is firmware update for the devices.

overall, I can not tell why the drive did not respond.

it looks like a bug or timing issue.





=============

looks like the file system told the nvme to flush data to disk and never got a response. other threads tried to access the resource
Contention Count = 77897977 times.

be back looking at the logs in 10 mins

threads waiting for access:

RazerAppEngine.exe
steamwebhelper.exe
csrss.exe (the system also was trying to process mouse input data)
and
SamsungMagician.exe

note:
InstancePath is "SCSI\Disk&Ven_NVMe&Prod_Samsung_SSD_990\5&144c0637&0&000000"

devices:
Razer DeathAdder V2
Razer Huntsman V3 Pro TKL
Yeti Stereo Microphone
DualSense Wireless Controller
looks like they are connected to a usb 2 hub that is suspended

note: filter driver running ucpd
https://www.ghacks.net/2024/04/08/new-sneaky-windows-driver-ucdp-stops-non-microsoft-software-from-setting-defaults/#:~:text=Microsoft has integrated the driver userChoice Protection Driver,,purpose: to block access to UserChoice Registry keys.

thank you for your assistance btw !!

 

[johnbl]

so could it be related to my ssd temperature???


one thing I definitely know its not is Samsung Magician, I only just downloaded that and i just updated my SSD firmware with it about a month ago, awhile after I've been having this same BSOD issue

at this point I would not guess that it is temps. I can not rule it out.
just that the nvme did not respond, which caused windows to attempt to reset the hardware. the reset did not respond so windows figured the hardware failed. iIt looks like the ntfs (filesystem) never got a response from the drive and kept a lock that blocked all of the other programs from doing what they wanted.

it could be the new Microsoft service blocked access to a registry setting that one of the running programs wanted to change. main point is to find out why the drive did not respond. work around could be to reduce the activity on the drive.
start cmd as an admin and run
chkdsk.exe c: /scan (to see if there is some error on the drive)

chkdsk.exe c: /offlinescanandfix

note: these drives have firmware that does a lot of work. these can get starved out and not have enough time to run. You might boot into bios and just let the machine be idle for a hour or so. after 5 minutes of being idle the firmware will run its cleanup routines. it might repair the problem.
generally you see this after you install a new drive or format a drive. in this case the firmware might have a large queue of clean up to complete.

SamsungMagician.exe was running at the time of the bugcheck. it was waiting for access to the drive. your razer devices were also waiting. the system service was also waiting on some mouse function call. you might remove the software or update it (RazerAppEngine.exe)

maybe just fixing the sony adapter failed install would remove the lock on the files system.
plug and play tried to install the driver over 3500 times.

note: this person has the same type of issue.

Question - Repeated BSOD WHEA_UNCORRECTABLE_ERROR (124) on Device Driver Error ?

Hi! This is absolutely driving me crazy. I'm running numerous video editing and emulators on my PC and recently the PC starts dropping BOSD bomb out of no where. The only thing I can say is the GPU fan seems to go nuts before the BOSD happens. The fault is very repeatable. I just have to open...

forums.tomshardware.com

 

[kpsdf23451]

at this point I would not guess that it is temps. I can not rule it out.
just that the nvme did not respond, which caused windows to attempt to reset the hardware. the reset did not respond so windows figured the hardware failed. iIt looks like the ntfs (filesystem) never got a response from the drive and kept a lock that blocked all of the other programs from doing what they wanted.

it could be the new Microsoft service blocked access to a registry setting that one of the running programs wanted to change. main point is to find out why the drive did not respond. work around could be to reduce the activity on the drive.
start cmd as an admin and run
chkdsk.exe c: /scan (to see if there is some error on the drive)

chkdsk.exe c: /offlinescanandfix

note: these drives have firmware that does a lot of work. these can get starved out and not have enough time to run. You might boot into bios and just let the machine be idle for a hour or so. after 5 minutes of being idle the firmware will run its cleanup routines. it might repair the problem.
generally you see this after you install a new drive or format a drive. in this case the firmware might have a large queue of clean up to complete.

SamsungMagician.exe was running at the time of the bugcheck. it was waiting for access to the drive. your razer devices were also waiting. the system service was also waiting on some mouse function call. you might remove the software or update it (RazerAppEngine.exe)

maybe just fixing the sony adapter failed install would remove the lock on the files system.
plug and play tried to install the driver over 3500 times.

note: this person has the same type of issue.

Question - Repeated BSOD WHEA_UNCORRECTABLE_ERROR (124) on Device Driver Error ?

Hi! This is absolutely driving me crazy. I'm running numerous video editing and emulators on my PC and recently the PC starts dropping BOSD bomb out of no where. The only thing I can say is the GPU fan seems to go nuts before the BOSD happens. The fault is very repeatable. I just have to open...

forums.tomshardware.com

hey! i took all of your advice and i have been BSOD free since (i thought)
about month ago there was this new BSOD ive never seen before DPC_WATCHDOG_VIOLATION (133) that i didnt even realize happened somehow? i just noticed it randomly looking at my memory.dmp file
maybe there's something else bad here?
thanks again for your great help!
https://drive.google.com/file/d/1oIWy9ekZ20ztZJ7KNOPdzZokGe9f0-S3/view?usp=sharing

 

[johnbl]

the watchdog violation came from Microsoft winsock driver. this is most likely going to be a bug in your 3rd party network driver.
I would look for a update to this driver:
rtf64x64.sys Wed Sep 22 01:40:17 2021
or
Netwtw14.sys Mon Aug 19 01:22:39 2024
or
rt640x64.sys Thu May 23 23:57:12 2024
or it could be any other driver that uses streaming Like your old
SteamStreamingSpeakers.sys Thu Jul 20 17:56:15 2017 (driver)

i will look in the dump to see if i can tell which one caused the problem.
----------------
looks like 17 threads are waiting for a release of a lock
the owning thread looks like power management waiting for a wake up signal.
note: updated lan driver is dated dec 10 2024
https://www.gigabyte.com/Motherboard/Z790-AORUS-ELITE-AX-rev-10/support#support-dl-driver-lan
(you should also update the Bluetooth and wireless driver from the same site if you have not)

I would update your network drivers starting with the oldest one.
or turn off sleep states for the drivers in power management.
also check for bios updates relating to power management/sleep
specs get updated and new power states get enabled with windows update. (I still would expect the old network driver is failing a new wake request, it is pretty common for old drivers to not to have implemented the functions correctly, since they were off by default a few years ago in windows, they get turned on later with windows updates)

your bios:
BIOS Version FKa
BIOS Starting Address Segment f000
BIOS Release Date 09/26/2024
Manufacturer Gigabyte Technology Co., Ltd.
Product Name Z790 AORUS ELITE AX