Windows 10 BSOD 0x00000124

SJ Kim 1 Reputation point
2022-08-01T00:10:36.207+00:00

My system has BSOD every day or once every few days.
Where the system is located, constant temperature and constant humidity are maintained.

It's a bit long, but the debug result of the dump file is attached below.

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

Loading Dump File [C:\Users\USER\Desktop\Dump\072722-10609-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 19041 MP (20 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff80754c00000 PsLoadedModuleList = 0xfffff8075582a230
Debug session time: Thu Jul 28 10:16:51.095 2022 (UTC + 9:00)
System Uptime: 1 days 23:03:40.801
Loading Kernel Symbols
...............................................................
................................................................
.......................................................
Loading User Symbols
Loading unloaded module list
............................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff80754ff78a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffa70065052cd0=0000000000000124
16: 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: 0000000000000004, PCI Express Error
Arg2: ffff83091f1c3028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:

------------------

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec  
Value: 6827  

Key  : Analysis.DebugAnalysisManager  
Value: Create  

Key  : Analysis.Elapsed.mSec  
Value: 13540  

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

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

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

Key  : Bugcheck.Code.DumpHeader  
Value: 0x124  

Key  : Bugcheck.Code.Register  
Value: 0x124  

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: 072722-10609-01.dmp

BUGCHECK_CODE: 124

BUGCHECK_P1: 4

BUGCHECK_P2: ffff83091f1c3028

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffa70065052cc8 fffff807550b472a : 0000000000000124 0000000000000004 ffff83091f1c3028 0000000000000000 : nt!KeBugCheckEx
ffffa70065052cd0 fffff807516215b0 : 0000000000000000 ffff83091f1c3028 ffff83091f17b4b0 ffff83091f1c3028 : nt!HalBugCheckSystem+0xca
ffffa70065052d10 fffff807551b67fe : 0000000000000000 ffffa70065052db9 ffff83091f1c3028 ffff83091f17b4b0 : PSHED!PshedBugCheckSystem+0x10
ffffa70065052d40 fffff807573836b3 : 0000000000000001 0000000000000001 ffff83091f1794b0 ffff83091f1c00d0 : nt!WheaReportHwError+0x46e
ffffa70065052e20 fffff80757383ea6 : ffffa700655c2d00 ffffa70065052ec0 ffffa700655c2e70 0000000000000000 : pci!ExpressRootPortAerInterruptRoutine+0x26b
ffffa70065052e80 fffff80757383f69 : ffffa700655c2dc0 fffff8077154ce72 ffff83091d0eba00 ffff83091d0ebb00 : pci!ExpressRootPortInterruptRoutine+0x46
ffffa70065052ee0 fffff80754f3b3f1 : 0000000000000000 fffff807550ba4da 0000000000000000 ffffde8626b1fa50 : pci!ExpressRootPortMessageRoutine+0x9
ffffa70065052f10 fffff80754ede215 : 0000000000000010 0000000000000202 ffffa70065052f60 0000000000000018 : nt!KiInterruptMessageDispatch+0x11
ffffa70065052f40 fffff80754ff90cf : ffffde8626b1fa50 ffffa700655c2dc0 000000000000042a fffff80754ff934a : nt!KiCallInterruptServiceRoutine+0xa5
ffffa70065052f90 fffff80754ff9397 : ffffde8626b1faf0 0000000000000001 0000000000040046 fffff80754e17138 : nt!KiInterruptSubDispatch+0x11f
ffffde8626b1f9d0 fffff80754ffb3ca : ffffffff00000000 0000000000000000 ffffa7006500b540 000000000000042a : nt!KiInterruptDispatch+0x37
ffffde8626b1fb60 0000000000000000 : ffffde8626b20000 ffffde8626b19000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x5a

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x124_4_GenuineIntel_PCIEXPRESS_COMPLETION_TIMEOUT_IMAGE_GenuineIntel.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {d9bf3217-47e1-78e8-f4b4-2529348d6565}

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

If you know the cause and solution of this BSOD, please help.

Thanks.

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

1 answer

Sort by: Most helpful
  1. Reza-Ameri 17,341 Reputation points Volunteer Moderator
    2022-08-01T16:23:16.103+00:00

    Try open start and search for feedback and open the Feedback Hub app and report this issue and upload dump file.
    Try run Windows Update and download and install all updates.
    Try update your drivers (including Graphic card driver).

    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.