Genuine Intel driver fail-dump file below

Pfister1 1 Reputation point
2022-05-01T14:01:31+00:00

Hi, having BSOD under any load about twice a day. System below, dump file below.

OS Name Microsoft Windows 10 Pro
Version 10.0.19044 Build 19044
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name DESKTOP-QAESODV
System Manufacturer HP
System Model OMEN by HP Obelisk Desktop 875-0xxx
System Type x64-based PC
System SKU 4NN43AA#ABA
Processor Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz, 3000 Mhz, 8 Core(s), 8 Logical Processor(s)
BIOS Version/Date AMI F.29, 8/2/2021
SMBIOS Version 3.2
Embedded Controller Version 29.40
BIOS Mode UEFI
BaseBoard Manufacturer HP
BaseBoard Product 84FD
BaseBoard Version 00
Platform Role Desktop
Secure Boot State On
PCR7 Configuration Elevation Required to View
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume5
Locale United States
Hardware Abstraction Layer Version = "10.0.19041.1566"
User Name DESKTOP-QAESODV\jfiel
Time Zone Central Daylight Time
Installed Physical Memory (RAM) 32.0 GB
Total Physical Memory 30.2 GB
Available Physical Memory 25.1 GB
Total Virtual Memory 61.2 GB
Available Virtual Memory 53.9 GB
Page File Space 31.0 GB
Page File D:\pagefile.sys
Kernel DMA Protection Off
Virtualization-based security Not enabled
Device Encryption Support Elevation Required to View
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes

Dump FIle:

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

Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Bitmap Dump File: Full address space is available

************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff80258800000 PsLoadedModuleList = 0xfffff8025942a290
Debug session time: Sat Apr 30 16:07:20.836 2022 (UTC - 5:00)
System Uptime: 0 days 0:27:59.598
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.........................
Loading User Symbols

Loading unloaded module list
.......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff80258bf7d50 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff60229fda390=0000000000000124
0: 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
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: ffffbd0895f24028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: ffffbd08820bcaac
Arg4: ffffbd08821e11a0

Debugging Details:


KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 3343

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 6880

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

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

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

Key  : WER.OS.Branch
Value: vb_release

Key  : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key  : WER.OS.Version
Value: 10.0.19041.1

FILE_IN_CAB: MEMORY.DMP

BUGCHECK_CODE: 124

BUGCHECK_P1: 10

BUGCHECK_P2: ffffbd0895f24028

BUGCHECK_P3: ffffbd08820bcaac

BUGCHECK_P4: ffffbd08821e11a0

PROCESS_NAME: System

STACK_TEXT:
fffff60229fda388 fffff80258db64dc : 0000000000000124 0000000000000010 ffffbd0895f24028 ffffbd08820bcaac : nt!KeBugCheckEx
fffff60229fda390 fffff80258db7039 : ffffbd088f4df910 ffffbd088f4df910 ffffbd08820bca80 ffffbd0898f45378 : nt!WheaReportHwError+0x3ec
fffff60229fda470 fffff80258db7155 : 0000000000000000 0000000000000062 ffffbd088f4df910 0000000000000000 : nt!WheaHwErrorReportSubmitDeviceDriver+0xe9
fffff60229fda4a0 fffff8025b8c2671 : 0000000000000000 fffff60229fda6c0 ffffbd08821e11a0 0000000000000000 : nt!WheaReportFatalHwErrorDeviceDriverEx+0xf5
fffff60229fda500 fffff8025b8bba50 : 0000000000000000 ffffbd08821e11a0 ffffbd08821ea1a0 0000000000000000 : storport!StorpWheaReportError+0x9d
fffff60229fda590 fffff8025b8a3c94 : 0000000000000000 0000000000000000 0000000000000000 fffff60229fda930 : storport!StorpMarkDeviceFailed+0x358
fffff60229fda820 fffff8025b85b3bd : 0000000000000000 ffffbd08821e6020 0000000000000000 0000000000000000 : storport!StorPortNotification+0x16474
fffff60229fda8f0 fffff8025b85e5b2 : ffffbd08c1000002 0000000000000000 ffffbd08821e6020 0000000000000003 : stornvme!ControllerReset+0x1a1
fffff60229fda970 fffff8025b85d52f : ffffbd08821e6020 ffffbd08821e1050 ffffbd08935e2a00 8000000000002000 : stornvme!NVMeControllerReset+0x10a
fffff60229fda9a0 fffff8025b8b9146 : ffffbd08935e2a00 ffffbd08821e1050 ffffbd0882146080 ffffbd087de92a50 : stornvme!NVMeControllerAsyncResetWorker+0x3f
fffff60229fda9d0 fffff80258af33f5 : ffffbd089499a540 ffffbd089499a540 ffffbd08821e1050 fffff8025b1bc5c0 : storport!StorPortWorkItemRoutine+0x46
fffff60229fdaa00 fffff80258abfc75 : ffffbd088aed9040 ffffbd088aed9040 fffff80258af32c0 0000000000000000 : nt!IopProcessWorkItem+0x135
fffff60229fdaa70 fffff80258aeec05 : ffffbd088aed9040 0000000000000080 ffffbd087df02080 000fa4efbd9bbfff : nt!ExpWorkerThread+0x105
fffff60229fdab10 fffff80258bff3a8 : fffff80254220180 ffffbd088aed9040 fffff80258aeebb0 0000000000000000 : nt!PspSystemThreadStartup+0x55
fffff60229fdab60 0000000000000000 : fffff60229fdb000 fffff60229fd4000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .cxr; .ecxr ; 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


Windows for business | Windows Client for IT Pros | User experience | Other
{count} votes

2 answers

Sort by: Most helpful
  1. Pfister1 1 Reputation point
    2022-05-02T20:57:41.377+00:00

    UPDATE: Omen controller was overclocking. HP BIOS settings do not have an overclocking option in performance settings. Had to use the OMEN/ ASUS software. Been clean running for 3 days now. Fingers crossed.

    0 comments No comments

  2. Docs 16,071 Reputation points
    2022-05-04T18:57:12.72+00:00

    What steps had you made to overclock the HP computer?

    How did you find the problem?

    Which software was installed?

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.