Avatar of donpick
donpick
 asked on

Requesting help interpreting a blue screen event on a laptop

The laptop is an HP 470 G3 with an i5 processor.  It has 8 gigs memory.  It has an ST500LM000-1EJ162-SSHD hard drive.  I have configured the laptop to produce mini dumps.  I have attached a mini dump.  The program WhoCrashed suggests the problem is due to a hardware error of some sort.  What can you experts tell me about this blue screen event?

 010120-14071-01.dmp
Windows 7Hardware

Avatar of undefined
Last Comment
nobus

8/22/2022 - Mon
Jackie Man

There is not much information from your minidump file.

As the timestamp for HAL.dll is on 28 Nov 2019.

Did you recall installing drivers, devices or software before 28 Nov 2019?
☠ MASQ ☠

The .dmp is pointing at a hardware problem with your PCI-E hardware, either the motherboard or a device that's in the socket.

The problem with 124 hardware errors is they don't distinguish between hardware that is physically bad and outdated/conflicting drivers.


If you're getting the errors on a regular basis and they are since a Windows update I'd look at chipset drivers or even BIOS updates to ensure your hardware is as compatible as possible with latest version of Windows.  There's an outside chance of a dying hardware component though.


More detailed output from your mini dump file here:

*******************************************************************************
*                                                                             *
*                        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
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000004, PCI Express Error
Arg2: fffffa8007fa68d8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1


STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  7601.24540.amd64fre.win7sp1_ldr_escrow.191127-1706

SYSTEM_MANUFACTURER:  HP

SYSTEM_PRODUCT_NAME:  HP ProBook 470 G3

SYSTEM_SKU:  W0S57UT#ABA

BIOS_VENDOR:  HP

BIOS_VERSION:  N78 Ver. 01.12

BIOS_DATE:  06/14/2016

BASEBOARD_MANUFACTURER:  HP

BASEBOARD_PRODUCT:  8102

BASEBOARD_VERSION:  KBC Version 40.60

DUMP_TYPE:  2

BUGCHECK_P1: 4

BUGCHECK_P2: fffffa8007fa68d8

BUGCHECK_P3: 0

BUGCHECK_P4: 0

HARDWARE_VENDOR_ID:  8086

HARDWARE_DEVICE_ID:  9D15

BUGCHECK_STR:  0x124_GenuineIntel

CPU_COUNT: 4

CPU_MHZ: 960

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 4e

CPU_STEPPING: 3

CPU_MICROCODE: 6,4e,3,0 (F,M,S,R)  SIG: 84'00000000 (cache) 84'00000000 (init)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  7

ANALYSIS_SESSION_HOST:  WIN64MAIN

ANALYSIS_SESSION_TIME:  01-02-2020 07:28:12.0300

ANALYSIS_VERSION: 10.0.17763.132 amd64fre

STACK_TEXT:  
fffff880`03d31938 fffff800`037fa9ef : 00000000`00000124 00000000`00000004 fffffa80`07fa68d8 00000000`00000000 : nt!KeBugCheckEx
fffff880`03d31940 fffff800`0339a27f : 00000000`00000001 fffffa80`07f87b10 00000000`00000000 fffffa80`07f86b60 : hal!HalBugCheckSystem+0x1e3
fffff880`03d31980 fffff880`00e73d07 : fffffa80`00000750 fffffa80`07f87b10 00000000`00000000 fffffa80`07fa5ab0 : nt!WheaReportHwError+0x26f
fffff880`03d319e0 fffff880`00e7372e : 00000000`00000000 fffff880`03d31b30 fffffa80`07c7dc00 fffffa80`0d569bb8 : pci!ExpressRootPortAerInterruptRoutine+0x27f
fffff880`03d31a40 fffff800`0329fb08 : fffff880`03d00180 fffff880`03d31b30 fffffa80`07c7dc00 fffff880`03d0f101 : pci!ExpressRootPortInterruptRoutine+0x36
fffff880`03d31ab0 fffff800`032a2402 : fffff880`03d00180 fffff880`03d0f140 00000000`00000002 fffff800`00000002 : nt!KiInterruptDispatch+0xb8
fffff880`03d31c40 00000000`00000000 : fffff880`03d32000 fffff880`03d2c000 fffff880`03d31c00 00000000`00000000 : nt!KiIdleLoop+0x32


THREAD_SHA1_HASH_MOD_FUNC:  2d8c7b9193f02b08ab24ba41de41d2f44e5a6960

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  2181f0423e0d1d45a9ad3af2859f10cfdbb15305

THREAD_SHA1_HASH_MOD:  a62b7e72857a05600f6640c34cc76bfd649b1220

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PCIEXPRESS_VENID_8086_DEVID_9D15

BUCKET_ID:  X64_0x124_GenuineIntel_PCIEXPRESS_VENID_8086_DEVID_9D15

PRIMARY_PROBLEM_CLASS:  X64_0x124_GenuineIntel_PCIEXPRESS_VENID_8086_DEVID_9D15

TARGET_TIME:  2020-01-02T01:37:04.000Z

OSBUILD:  7601

OSSERVICEPACK:  1000

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 7

OSEDITION:  Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2019-11-28 02:52:33

BUILDDATESTAMP_STR:  191127-1706

BUILDLAB_STR:  win7sp1_ldr_escrow

BUILDOSVER_STR:  6.1.7601.24540.amd64fre.win7sp1_ldr_escrow.191127-1706

ANALYSIS_SESSION_ELAPSED_TIME:  4ba

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x124_genuineintel_pciexpress_venid_8086_devid_9d15

FAILURE_ID_HASH:  {939af09e-39eb-5b82-044a-527f0a4c2cdd}

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

Open in new window

ASKER CERTIFIED SOLUTION
nobus

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
andyalder

You could always try disabling the network and wifi adapters in device manager to help troubleshoot.
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23
donpick

ASKER
Hello Jackie Man:   I'd like to upload the entire *.dmp file but the Experts Exchange site tells me it is too big. I configured mini dump so the size of the dump file would be smaller.   Suggestions?

Hello nobus:  OK, I'll do this just as soon as possible.

Hello andyalder:  How would I be able to use my laptop if the network and wifi are disabled?  Are you suggesting I should disable the network and wifi and let the laptop sit unused for some period of time?   How long?
SOLUTION
Log in to continue reading
Log In
Sign up - Free for 7 days
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
SOLUTION
Log in to continue reading
Log In
Sign up - Free for 7 days
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
SOLUTION
Log in to continue reading
Log In
Sign up - Free for 7 days
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
donpick

ASKER
I will transfer the full dump file to the cloud and share a link just as soon as possible.
donpick

ASKER
Thank you all for your help.  Nobus said to update the drivers.  I updated some of them (particularly the Chipset driver) and the computer has been stable since.  I will update more drivers as I have time.
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
nobus

>>   I will update more drivers as I have time  <<  imo don't wait - bad ones can also corrupt other parts...