Try to force Windows to show failed drivers and produce minidump files, turn on Driver Verifier.
Make the BSOD happen 3 times and after that see if the files were created.
Before you run Driver Verifier, please create a new System Restore Point.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : false AllowNugetExeUpdate : false AllowNugetMSCredentialProviderInstall : false AllowParallelInitializationOfLocalRepositories : true
-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true
>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds
************* Waiting for Debugger Extensions Gallery to Initialize **************
>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.031 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 36
Microsoft (R) Windows Debugger Version 10.0.25877.1004 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\022224-31312-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
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
Kernel base = 0xfffff802`2e000000 PsLoadedModuleList = 0xfffff802`2ec2a770
Debug session time: Thu Feb 22 19:52:14.958 2024 (UTC + 1:00)
System Uptime: 0 days 0:05:17.622
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
.............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`2e3fd5b0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff802`32224cd0=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: 0000000000000004, PCI Express Error
Arg2: ffffd80da5e4e028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
*** WARNING: Check Image - Checksum mismatch - Dump: 0x1444a, File: 0x14db4 - C:\ProgramData\Dbg\sym\hidi2c.sys\785C504F15000\hidi2c.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 4624
Key : Analysis.Elapsed.mSec
Value: 20391
Key : Analysis.IO.Other.Mb
Value: 18
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 20
Key : Analysis.Init.CPU.mSec
Value: 609
Key : Analysis.Init.Elapsed.mSec
Value: 85921
Key : Analysis.Memory.CommitPeak.Mb
Value: 96
Key : Bugcheck.Code.LegacyAPI
Value: 0x124
Key : Failure.Bucket
Value: 0x124_4_GenuineIntel_PCIEXPRESS_RECEIVER_OVERFLOW_IMAGE_GenuineIntel.sys
Key : Failure.Hash
Value: {292b172a-d242-4fa5-ed33-089eb4b12cc5}
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Version
Value: 10.0.19041.1
BUGCHECK_CODE: 124
BUGCHECK_P1: 4
BUGCHECK_P2: ffffd80da5e4e028
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FILE_IN_CAB: 022224-31312-01.dmp
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffff802`32224cc8 fffff802`2e4b96aa : 00000000`00000124 00000000`00000004 ffffd80d`a5e4e028 00000000`00000000 : nt!KeBugCheckEx
fffff802`32224cd0 fffff802`2a8b15b0 : 00000000`00000000 ffffd80d`a5e4e028 ffffd80d`a5e3b4b0 ffffd80d`a5e4e028 : nt!HalBugCheckSystem+0xca
fffff802`32224d10 fffff802`2e5bb9ae : 00000000`00000000 fffff802`32224db9 ffffd80d`a5e4e028 ffffd80d`a5e3b4b0 : PSHED!PshedBugCheckSystem+0x10
fffff802`32224d40 fffff802`30444a33 : 00000000`00000001 00000000`00000001 ffffd80d`a5e394b0 ffffd80d`a5e4b4d0 : nt!WheaReportHwError+0x46e
fffff802`32224e20 fffff802`30445226 : ffffc480`b33a1b00 fffff802`32224ec0 ffffc480`b33a1bf0 00000000`00000001 : pci!ExpressRootPortAerInterruptRoutine+0x26b
fffff802`32224e80 fffff802`304452e9 : ffffc480`b33a1b40 00000000`00989680 00000000`00000000 00000000`00000000 : pci!ExpressRootPortInterruptRoutine+0x46
fffff802`32224ee0 fffff802`2e340331 : fffff802`2ec48d90 00000000`00000000 00000000`00000202 fffff802`2e250a82 : pci!ExpressRootPortMessageRoutine+0x9
fffff802`32224f10 fffff802`2e300825 : ffffe80c`3da4fa00 00000000`00000000 fffff802`28dd7180 fffff802`2e300825 : nt!KiInterruptMessageDispatch+0x11
fffff802`32224f40 fffff802`2e3ff31f : fffff802`32215a50 ffffc480`b33a1b40 00000000`00000173 fffff802`2e4058e0 : nt!KiCallInterruptServiceRoutine+0xa5
fffff802`32224f90 fffff802`2e3ff5e7 : fffff802`32215af0 00000000`00000001 00000000`00040046 fffff802`2e2541c8 : nt!KiInterruptSubDispatch+0x11f
fffff802`322159d0 fffff802`2e401f6a : 00000000`00000000 fffff802`2ed27a00 ffffd80d`b50df080 00000000`00000173 : nt!KiInterruptDispatch+0x37
fffff802`32215b60 00000000`00000000 : fffff802`32216000 fffff802`3220f000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel.sys
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: 0x124_4_GenuineIntel_PCIEXPRESS_RECEIVER_OVERFLOW_IMAGE_GenuineIntel.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {292b172a-d242-4fa5-ed33-089eb4b12cc5}
Followup: MachineOwner
---------
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Try to force Windows to show failed drivers and produce minidump files, turn on Driver Verifier.
Make the BSOD happen 3 times and after that see if the files were created.
Before you run Driver Verifier, please create a new System Restore Point.
Thanks for replying ,
So ,Bios is up tp date and according to Intel Driver Support assistant , all my intel drivers are up to date.
Overclocking are all disabled , and i don't think my laptop support the overclocking settings.
My name is Jonathan Deives. I'm an Independent Advisor and I will be happy to help you today..
The minidump you sent indicates that the cause of the BSOD is "GenuineIntel.sys". which is the Intel processor driver.
But it can also be caused by another driver, software or hardware.
You can try the following.
Go to the manufacturer's website and search for your system model.
Also download Intel Driver Support assistant to check if there are any drivers available;