Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: BSOD ntoskrnl.exefollowing hal.dll crash

25 Aug 2013   #1

Windows 7 Pro x64
BSOD ntoskrnl.exefollowing hal.dll crash

Repeated crashes, often whilst Google Chrome being used. Any idea's why? Possibly started after NVIDA Driver update a few months ago but can't be sure. Thanks for any help

My System SpecsSystem Spec

26 Aug 2013   #2

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit

  BIOS Version                  1203 = The latest version available at ASUS 
  BIOS Starting Address Segment f000
  BIOS Release Date             06/25/2008
Hello BlueSprint.

A stop 0x124 is basically a hardware level error, and it is very possible for such an old computer.

If you can frame an idea that the driver update has anything to do with the BSODs, you may plan to roll it back to the earlier version.
Device Manager - Roll Back Driver
You updated the driver on 1st of July, and the BSODs started from 3rd July.

Considering the age of the computer, I want to suggest you the following tests:

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

Stress test the CPU.
Hardware - Stress Test With Prime95

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Also let us know the wattage of the PSU.

Let us know the results.
*                                                                             *
*                        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: 0000000000000000, Machine Check Exception
Arg2: fffffa8007dbd2d8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

Debugging Details:

BUGCHECK_STR:  0x124_GenuineIntel





fffff880`031a86f0 fffff800`03115ca9 : fffffa80`07dbd2b0 fffffa80`06a32660 00000000`00000006 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031a8c10 fffff800`02ff6e97 : fffffa80`07dbd2b0 fffff800`030702d8 fffffa80`06a32660 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031a8c40 fffff800`02f5e285 : fffff800`030d1b40 00000000`00000001 fffffa80`079b29c0 fffffa80`06a32660 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031a8c80 fffff800`02ed4261 : fffff880`01090e00 fffff800`02f5e260 fffffa80`06a32600 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031a8cb0 fffff800`03168bae : 00000000`00000000 fffffa80`06a32660 00000000`00000080 fffffa80`06a20040 : nt!ExpWorkerThread+0x111
fffff880`031a8d40 fffff800`02ebb8c6 : fffff880`02f64180 fffffa80`06a32660 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031a8d80 00000000`00000000 : fffff880`031a9000 fffff880`031a3000 fffff880`03d06740 00000000`00000000 : nt!KxStartSystemThread+0x16


FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel



BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

Followup: MachineOwner

1: kd> !errrec fffffa8007dbd2d8
Common Platform Error Record @ fffffa8007dbd2d8
Record Id     : 01cea1c5bc22a765
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 8/25/2013 19:03:13 (UTC)
Flags         : 0x00000002 PreviousError

Section 0     : Processor Generic
Descriptor    @ fffffa8007dbd358
Section       @ fffffa8007dbd430
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : BUS error
Operation     : Generic
Flags         : 0x00
Level         : 0
CPU Version   : 0x00000000000006fb
Processor ID  : 0x0000000000000000

Section 1     : x86/x64 Processor Specific
Descriptor    @ fffffa8007dbd3a0
Section       @ fffffa8007dbd4f0
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000000
CPU Id        : fb 06 00 00 00 08 04 00 - bd e3 00 00 ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa8007dbd4f0

Section 2     : x86/x64 MCA
Descriptor    @ fffffa8007dbd3e8
Section       @ fffffa8007dbd570
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : BUSL0_SRC_ERR_M_NOTIMEOUT_ERR (Proc 0 Bank 0)
  Status      : 0xf200084000000800
My System SpecsSystem Spec
26 Aug 2013   #3

Windows 7 Pro x64

Thanks ARC, I'll work my way through those things and report back.
My System SpecsSystem Spec


 BSOD ntoskrnl.exefollowing hal.dll crash

Thread Tools

Similar help and support threads
Thread Forum
BSOD DRIVER_POWER_STATE_FAILURE crash at ntoskrnl.exe+75bc0
I get the same BSOD every time. Usually, almost exclusively when I shut the laptop and it is supposed to sleep. What happens is, it turns off. I have attached the BSOD file. I am guessing my power supply is running into problems. Tell me I am wrong.... please?
BSOD Help and Support
BSOD ntoskrnl.exe , All the Time !! Crash Address ntoskrnl.exe+80640
Jan 2014 //------------------------------------------- How to Solve : 1- I've uninstalled my windows and recover my laptop with recovery DVD to it's original factory state.(original windows :)) 2- Never installed Norton internet security again , I'm using Microsoft Security Essentials now. 3-...
BSOD Help and Support
BSOD crash of SYSTEM_SERVICE_EXCEPTION ntoskrnl.exe pls help!!!
m getting BSOD frequently sometimes more than 4 in one hour ..after doing some research i installed the BLUESCREEN VIEWER where from i got this error type.pls guys help me solve this bug
BSOD Help and Support
BSOD all from same crash address ntoskrnl.exe+7cc40.. please help!!
hi can someone please help i keep getting blue error screens different types of errors but all having the same crash address been using bluescreen viewer to see the errors iv tried as much as i can by updating drivers and checking if windows is up to date looked on other forums but just...
BSOD Help and Support
System crash (BSOD) - ntoskrnl.exe?
A couple of months ago I started getting sporadic system crashes for reasons I didn't understand, so I simply reinstalled Windows and that solved my problem for a bit. A couple of weeks ago, I started having the same problem but I noticed the 0x1E stop code, I didn't know better at the time, so I...
BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 12:04.

Twitter Facebook Google+

Windows 7 Forums

Seven Forums Android App Seven Forums IOS App