BSOD - BCC 124 while playing games - ntoskrnl.exe

[manno3k]

x86 (32-bit) or x64 ?Windows 7 Home Premium 64bit
the original installed OS on the system?This was the original OS
an OEM or full retail version? OEM
What is the age of system (hardware)? The system was purchased 10/12/2010 but some items were added from original
What is the age of OS installation - OS was just re-installed on 1/30-1/31

I have been having problems with my PC over the past week or so. I have been getting a BCC 124 error and its been difficult to diagnose what the issue is. The crashes were occurring usually within 15 minutes of playing a PC game (SWTOR, Civ 5, LoL). I started using BueScreenView to see what the cause was and it was Hal.dll coming up most of the time. I tried several things to fix it after reading articles online. Startup repair didnt find anything, sfc found no violations, memtest, chckdsk, and a clean reinstall of windows did not help. I think I finally stopped getting hal.dll errors after doing repair console command bootsect.exe /nt60 ALL /force and now its blue screening for ntoskrnl.exe after 30m-1h of playing a PC game. Most of the articles I located online for these were for windows XP so it has been hard to find out what the next step would be for Windows 7. Any help would be appreciated.

Michael

Here is the info from the last dmp below and the rest is attached.

==================================================
Dump File : 020412-21606-01.dmp
Crash Time : 2/4/2012 12:31:37 AM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`0ea838f8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4a5e4c
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16841 (win7_gdr.110622-1503)
Processor : x64
Crash Address : ntoskrnl.exe+4a5e4c
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\020412-21606-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 262,144
==================================================
​

 

[Influx]

Are you overclocking?

HAL (hardware abstraction layer) may have caused it.

Analysis by windbg (013112-21824-01.dmp):

BugCheck 124, {0, fffffa800ea67028, fa000000, 400405}
Probably caused by : hardware
Followup: MachineOwner
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: fffffa800ea67028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000fa000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000400405, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
BUGCHECK_STR: 0x124_GenuineIntel
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: f
STACK_TEXT:
fffff880`0311db58 fffff800`02c1c903 : 00000000`00000124 00000000`00000000 fffffa80`0ea67028 00000000`fa000000 : nt!KeBugCheckEx
fffff880`0311db60 fffff800`02dd9513 : 00000000`00000001 fffffa80`0ea5a4f0 00000000`00000000 fffffa80`0ea5a540 : hal!HalBugCheckSystem+0x1e3
fffff880`0311dba0 fffff800`02c1c5c8 : 00000000`00000728 fffffa80`0ea5a4f0 fffff880`0311df30 fffff880`0311df00 : nt!WheaReportHwError+0x263
fffff880`0311dc00 fffff800`02c1bf1a : fffffa80`0ea5a4f0 fffff880`0311df30 fffffa80`0ea5a4f0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`0311dd50 fffff800`02c1bdd5 : 00000000`00000008 00000000`00000001 fffff880`0311dfb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`0311dd90 fffff800`02c0fe88 : fffffa80`0e93c8c0 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`0311ddc0 fffff800`02cc37ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`0311ddf0 fffff800`02cc3613 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`0311df30 fffff800`02cce97e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`0313d560 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiTimerWaitTest+0x3e
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE
BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE
Followup: MachineOwner

 

[yowanvista]

STOP 0x124 is a hardware error caused by a possible defect in one of your hardware componentshttp://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

1.) Update your BIOS
2.) Verify that nothing is overclocked

Run Prime 95 to test your CPU. Carefully the instructions in this tutorial: CPU - Stress Test with Prime95. Run 3 separate tests, one on each of the settings (Blend, Small FFTs, Large FFTs). Post back with your results.
Note that this test may overheat the CPU, ensure proper cooling

*******************************************************************************
*                                                                             *
*                        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: fffffa800ea838f8, 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:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`01fc36f0 fffff800`020d9979 : fffffa80`0ea838d0 fffffa80`0cdac680 00000000`00000015 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`01fc3c10 fffff800`01fbb3c7 : fffffa80`0ea838d0 fffff800`020345f8 fffffa80`0cdac680 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`01fc3c40 fffff800`01f23955 : fffff800`02096380 fffffa80`0e7f5828 fffffa80`0e7f5820 fffffa80`0cdac680 : nt!WheapProcessWorkQueueItem+0x57
fffff880`01fc3c80 fffff800`01e9c7e1 : fffff880`01122e00 fffff800`01f23930 fffffa80`0cdac680 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`01fc3cb0 fffff800`0212f6fa : 00000000`0000043c fffffa80`0cdac680 00000000`00000080 fffffa80`0cd319e0 : nt!ExpWorkerThread+0x111
fffff880`01fc3d40 fffff800`01e6db46 : fffff880`01ece180 fffffa80`0cdac680 fffff880`01ed8fc0 fffff800`0211065f : nt!PspSystemThreadStartup+0x5a
fffff880`01fc3d80 00000000`00000000 : fffff880`01fc4000 fffff880`01fbe000 fffff880`01fc3260 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

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

 

[manno3k]

Are you overclocking? Everything has been restored to default.

You should do a system file check. - I did run the SFC /scannow several times and it did not locate any problems. The hal.dll may have been corrected at this time since it has not appeared for the past 3 days after doing the bootsect.exe /nt60 ALL /force command. I think I need help with reviews of the dmp's from 2/1-2/4 with ntoskrnl.exe to see what the next steps are. Thanks.

 

[manno3k]

I tried to run the three different stress tests with Prime 95 and the benchmark, but it could not complete any of them. At some point during each test the computer just rebooted itself without any blue screen. I tried to run them all at least 2-3 times and it looks like only one of the tests and the benchmark managed to post something into the results document.

 

[yowanvista]

I tried to run the three different stress tests with Prime 95 and the benchmark, but it could not complete any of them. At some point during each test the computer just rebooted itself without any blue screen. I tried to run them all at least 2-3 times and it looks like only one of the tests and the benchmark managed to post something into the results document.

The tests were incomplete, could run run Prime95 in SafeMode?
Is your CPU adequately cooled?

 

[matrixxxx]

Whenever I enable Symantec endpoint protection I get the nost...exe notifications. I choose not to notify me. I think this is got to do with the keyboard settings