WHEA BSOD Everytime PC Is Turned On Solved

  1.    #1

    WHEA BSOD Everytime PC Is Turned On

    Windows 10 Pro v1903
    Beginning about two weeks ago, every time I power on my PC, I get a BSOD with the WHEA stop code. After making a system dump, the PC restarts and all works fine until I next power the PC off.
    I have run "DISM.exe /Online /Cleanup-image /Restorehealth", "sfc /scannow" and MEMTEST 5.1.
    All report no errors.
    Windows Update History shows one driver updated:
    HP Inc. - SoftwareComponent - 6/20/2019 12:00:00 AM - 1.0.644.0
    DriverBooster reports several recently updated drivers:

    This is what the "WhoCrashed" program reports:
    Crash Dump Analysis

    Crash dumps are enabled on your computer.

    Crash dump directories:

    On Sun 07/Jul/19 12:09:25 your computer crashed or a problem was reported
    crash dump file: C:\WINDOWS\Minidump\070719-8796-01.dmp
    This was probably caused by the following module: hal.dll (hal+0x477E8)
    Bugcheck code: 0x124 (0x4, 0xFFFFC80F87571038, 0x0, 0x0)
    file path: C:\WINDOWS\system32\hal.dll
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Hardware Abstraction Layer DLL
    Bug check description: 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).
    This is likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
    On Sun 07/Jul/19 12:09:25 your computer crashed or a problem was reported
    crash dump file: C:\WINDOWS\MEMORY.DMP
    This was probably caused by the following module: pshed.dll (PSHED!PshedBugCheckSystem+0x10)
    Bugcheck code: 0x124 (0x4, 0xFFFFC80F87571038, 0x0, 0x0)
    file path: C:\WINDOWS\system32\pshed.dll
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Platform Specific Hardware Error Driver
    Bug check description: 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).
    This is likely to be caused by a hardware problem.
    The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

    I have uploaded the output from V2 Log collector ("OMEN875-(2019-07-13_10-41-24)").
    I would welcome any suggestions as to how to proceed!

    - - - Updated - - -

    It seems I was experiencing a hardware fault with pci express. I updated my BIOS to F.20-05/20/2019. The problem has disappeared.
    WHEA BSOD Everytime PC Is Turned On Attached Files
      My ComputerSystem Spec

  2.    #2

    Although STOP 0x124 errors are most frequently caused by hardware problems, then can be caused by software.
    As such, please update/uninstall the programs associated with the following older drivers:

    pcouffin.sys Tue Dec 5 09:39:30 2006 (457584A2)
    Please uninstall your VSO software to remove this one.

    jaksta_va.sys Wed Apr 11 05:29:19 2012 (4F854EEF)
    VSC driver - by e2eSoft -or-S3 Nokia USB Port driver VSC - Virtual Sound Card | E2ESOFT
    Please uninstall the program associated with this driver

    PxHlpa64.sys Tue Apr 24 13:26:29 2012 (4F96E245)
    Sonic CD/DVD driver (used by many different CD/DVD programs)
    Please uninstall this program also

    PUSBODD2.SYS Fri Jan 18 06:08:06 2013 (50F92D16)
    Pioneer USB Optical Disk Drive
    Uninstall the program for this (you can use the built in Windows drivers and the device will work fine)
    HWiNFO64A.SYS Tue Mar 31 05:51:32 2015 (551A6E24)
    HWiNFO32 Kernel Driver
    Please uninstall due to the age of the driver.

    wdcsam64.sys Fri Oct 9 16:31:13 2015 (56182411)
    Western Digital SCSI Arcitecture Model (SAM) WDM driver
    This is the software for an attached USB drive - it's not needed in order to run/access the drive. Please uninstall this software.

    Then run the system and see if that stops the BSOD's

    If not, then please:
    - run MemTest86 (as it'll boot using UEFI): MemTest86 - Official Site of the x86 Memory Testing Tool
    - run Seagate Seatools on ALL drives (HDD/SSD/USB): How to use SeaTools for Windows | Seagate Support US

    Let us know the results and we'll move on from there.
      My ComputerSystem Spec

  3. Posts : 271
    Windows 8.1 Enterprise x64

    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 = 0x4 - PCI Express error
    Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [F:\071119-8375-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 18362 MP (12 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 18362.1.amd64fre.19h1_release.190318-1202
    Machine Name:
    Kernel base = 0xfffff804`45a00000 PsLoadedModuleList = 0xfffff804`45e432f0
    Debug session time: Fri Jul 12 08:15:45.758 2019 (UTC + 2:00)
    System Uptime: 0 days 12:35:39.586
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    For analysis of this file, run !analyze -v
    0: kd> !analyze
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    Use !analyze -v to get detailed debugging information.
    BugCheck 124, {4, ffffdb09788d3038, 0, 0}
    *** WARNING: Unable to verify timestamp for win32k.sys
    Probably caused by : GenuineIntel
    Followup:     MachineOwner
    0: kd> !analyze -v
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    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.
    Arg1: 0000000000000004, PCI Express Error
    Arg2: ffffdb09788d3038, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    Debugging Details:
    BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202
    SYSTEM_PRODUCT_NAME:  OMEN by HP Obelisk Desktop 875-0xxx
    BIOS_DATE:  01/15/2019
    DUMP_TYPE:  2
    BUGCHECK_P1: 4
    BUGCHECK_P2: ffffdb09788d3038
    BUGCHECK_P3: 0
    BUGCHECK_P4: 0
    BUGCHECK_STR:  0x124_GenuineIntel
    CPU_COUNT: c
    CPU_MHZ: c78
    CPU_VENDOR:  GenuineIntel
    CPU_MODEL: 9e
    CPU_MICROCODE: 6,9e,a,0 (F,M,S,R)  SIG: 9A'00000000 (cache) 9A'00000000 (init)
    BLACKBOXBSD: 1 (!blackboxbsd)
    BLACKBOXNTFS: 1 (!blackboxntfs)
    BLACKBOXPNP: 1 (!blackboxpnp)
    PROCESS_NAME:  System
    ANALYSIS_SESSION_TIME:  07-14-2019 00:04:55.0121
    ANALYSIS_VERSION: 10.0.18362.1 amd64fre
    fffff804`4ae2bce8 fffff804`464f97e8 : 00000000`00000124 00000000`00000004 ffffdb09`788d3038 00000000`00000000 : nt!KeBugCheckEx
    fffff804`4ae2bcf0 fffff804`48981920 : ffffdb09`7c1a0890 00000000`00000000 ffffdb09`788d3038 00000000`00000000 : hal!HalBugCheckSystem+0xd8
    fffff804`4ae2bd30 fffff804`45d3d7ca : ffffdb09`7c1a0890 fffff804`4ae2bdb9 00000000`00000000 ffffdb09`788d3038 : PSHED!PshedBugCheckSystem+0x10
    fffff804`4ae2bd60 fffff804`48fde064 : 00000000`00000000 00000000`00000000 ffffdb09`7c1a11b0 ffffdb09`788b2010 : nt!WheaReportHwError+0x37a
    fffff804`4ae2be20 fffff804`48fde7e2 : ffffb081`009ffb40 fffff804`4ae2bec0 ffffb081`009ffbf0 fffff38d`8aa2f720 : pci!ExpressRootPortAerInterruptRoutine+0x270
    fffff804`4ae2be80 fffff804`48fde899 : ffffb081`009ffb40 00000000`00989680 ffffa46e`b4b7750d 00000000`00000f32 : pci!ExpressRootPortInterruptRoutine+0x22
    fffff804`4ae2bee0 fffff804`45b1aaa1 : 00000000`00000000 00000000`00001000 fffff38d`8c917200 fffff804`464b51e1 : pci!ExpressRootPortMessageRoutine+0x9
    fffff804`4ae2bf10 fffff804`45a02e15 : fffff38d`8b2cf510 fffff804`46520ca0 fffff804`421f6180 00000000`00000000 : nt!KiInterruptMessageDispatch+0x11
    fffff804`4ae2bf40 fffff804`45bbe0ef : fffff804`4ae1ca50 ffffb081`009ffb40 00000000`0000082e ffffb081`009ffb40 : nt!KiCallInterruptServiceRoutine+0xa5
    fffff804`4ae2bf90 fffff804`45bbe3b7 : 00000000`00000002 fffff804`421f6180 fffff804`4ae1cb00 00000000`00000001 : nt!KiInterruptSubDispatch+0x11f
    fffff804`4ae1c9d0 fffff804`45bc038e : 00000000`00000000 fffff804`421f6180 ffffdb09`8ee15040 00000000`0000082e : nt!KiInterruptDispatch+0x37
    fffff804`4ae1cb60 00000000`00000000 : fffff804`4ae1d000 fffff804`4ae16000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x4e
    THREAD_SHA1_HASH_MOD_FUNC:  5fbb1bde575d8e48180077938aa26f0023078061
    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  d64f8d96b05babed038709e48f1ba84800578154
    THREAD_SHA1_HASH_MOD:  54a8497e43a7fa468d86348aca3de4fbf67d4a0a
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: GenuineIntel
    IMAGE_NAME:  GenuineIntel
    STACK_COMMAND:  .thread ; .cxr ; kb
    TARGET_TIME:  2019-07-12T06:15:45.000Z
    OSBUILD:  18362
    SUITE_MASK:  272
    OSNAME:  Windows 10
    OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS
    USER_LCID:  0
    OSBUILD_TIMESTAMP:  1972-02-02 09:33:06
    BUILDDATESTAMP_STR:  190318-1202
    BUILDLAB_STR:  19h1_release
    BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202
    FAILURE_ID_HASH_STRING:  km:0x124_genuineintel_pciexpress_venid_10ec_devid_8168_unsupported_request
    FAILURE_ID_HASH:  {25af4548-7f77-0cbf-392d-421eabca330f}
    Followup:     MachineOwner
    0: kd> !errrec ffffdb09788d3038
    Common Platform Error Record @ ffffdb09788d3038
    Record Id     : 01d5380fae001443
    Severity      : Informational (3)
    Length        : 672
    Creator       : Microsoft
    Notify Type   : PCI Express Error
    Timestamp     : 7/12/2019 6:15:45 (UTC)
    Flags         : 0x00000000
    Section 0     : PCI Express
    Descriptor    @ ffffdb09788d30b8
    Section       @ ffffdb09788d3148
    Offset        : 272
    Length        : 208
    Flags         : 0x00000001 Primary
    Severity      : Recoverable
    Port Type     : Endpoint
    Version       : 1.1
    Command/Status: 0x4010/0x0107
    Device Id     :
      VenId:DevId : 10ec:8168
      Class code  : 010000
      Function No : 0x00
      Device No   : 0x00
      Segment     : 0x0000
      Primary Bus : 0x02
      Second. Bus : 0x00
      Slot        : 0x0000
    Dev. Serial # : 01000000684ce000
    Express Capability Information @ ffffdb09788d317c
      Device Caps : 05908cc0 Role-Based Error Reporting: 1
      Device Ctl  : 2010 ur fe nf ce
      Dev Status  : 001b UR fe NF CE
       Root Ctl   : 0000 fs nfs cs
    AER Information @ ffffdb09788d31b8
      Uncorrectable Error Status    : 00100000 UR ecrc mtlp rof uc ca cto fcp ptlp sd dlp und
      Uncorrectable Error Mask      : 00400000 ur ecrc mtlp rof uc ca cto fcp ptlp sd dlp und
      Uncorrectable Error Severity  : 00462030 ur ecrc MTLP ROF uc ca cto FCP ptlp SD DLP und
      Correctable Error Status      : 00002000 ADV rtto rnro dllp tlp re
      Correctable Error Mask        : 00006000 ADV rtto rnro dllp tlp re
      Caps & Control                : 000000b4 ecrcchken ECRCCHKCAP ecrcgenen ECRCGENCAP FEP
      Header Log                    : 40000001 0000000f a3408e7c 00000000
      Root Error Command            : 00000000 fen nfen cen
      Root Error Status             : 00000000 MSG# 00 fer nfer fuf mur ur mcr cer
      Correctable Error Source ID   : 00,00,00
      Correctable Error Source ID   : 00,00,00
    Section 1     : Processor Generic
    Descriptor    @ ffffdb09788d3100
    Section       @ ffffdb09788d3218
    Offset        : 480
    Length        : 192
    Flags         : 0x00000000
    Severity      : Informational
    Proc. Type    : x86/x64
    Instr. Set    : x64
    CPU Version   : 0x00000000000906ea
    Processor ID  : 0x0000000000000000
    Here you just have to go to the site that collects device IDs whether it is PCI or USB and you already have the answer. The problem is your network card
    PCI\VEN_10EC&DEV_8168 - RTL8111/8168/8411 PCI Express… | Device Hunt
    You have the latest drivers for the network card from what I see, therefore the fastest way will be to disable the integrated network card in the BIOS, and then buy and connect the network card to PCI-E
      My ComputerSystem Spec


Related Threads
BSOD/freeze after exactly 11min 15sec uptime every time. This has been going on for some time while I've been trialing and erroring. Computer locks up exactly 11m 15s after power on (BIOS set to boot with power on). That's 11m 10s after POST beep...
Hello, I don't know surely why this happen suddenly. I did not change or install anything before this bsod come. I test playing other games and it seems fine. I already reset windows 10 (with keep my files option), re install steam and dota, and...
BSOD everytime open browser in BSOD Crashes and Debugging
Hi, as title, i try uninstall the driver ( AMD ) but everytime restart it auto install. i already disable window update but still keep getting BSOD. please find attach file. thank you.
frequently BSOD everytime after appr. 30min in BSOD Crashes and Debugging
Hey Folks! Had in the past already random BSOD with the current machine (at that time Win7 and Win8.1) but just one in two or three months. After I upgraded the machine to Win10 I'm facing heavy frequent BSOD everytime after appr. 20-40mins and...
BSOD everytime in BSOD Crashes and Debugging
Ok so I am having a very strange issue. Background: so basically i just built a brand new computer, bought all the parts and built it myself and everything seemed to be working fine, even though i installed windows 2 times (the first time i...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 11:28.
Find Us