BSOD ntoskrnl.exefollowing hal.dll crash

[BlueSprint]

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

 

[Arc]

  BIOS Version                  1203 = [FONT=Verdana]The latest version available at [URL="http://www.asus.com/Motherboards/P5KC/#support_Download_25"]ASUS [/URL][/FONT]
  BIOS Starting Address Segment f000
  BIOS Release Date           [COLOR=Red]  06/25/2008[/COLOR]

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                                    *
*                                                                             *
*******************************************************************************

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: 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

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
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


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

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

 

[BlueSprint]

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