BSOD - hal.dll

husker91 · 18 Jul 2011

I've been having several BSOD's over the past couple days. It seems to be caused by hal.dll but I have no idea what it's from or does. Could someone help?

Attached is my minidump.

Maguscreed · 18 Jul 2011

I'll have a look at the crash files here.
First thing I want you to do meanwhile is run this
SFC /SCANNOW Command - System File Checker

edit: okay given the info the debugger is spitting out in conjunction with the specific error you are seeing. I'm going to have to guess you are developing a hard drive problem.
The other possibility is that you have overclocked your system and that overclock has become unstable.

Stop 0x124 - what it means and what to try
Give that a look over if you are not overclocked.

Code:

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: fffffa8008361028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000f653c000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000128, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  Launcher.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff800`00ba8ac8 fffff800`033f2903 : 00000000`00000124 00000000`00000000 fffffa80`08361028 00000000`f653c000 : nt!KeBugCheckEx
fffff800`00ba8ad0 fffff800`02f8a493 : 00000000`00000001 fffffa80`079d4820 00000000`00000000 fffffa80`079d4870 : hal!HalBugCheckSystem+0x1e3
fffff800`00ba8b10 fffff800`033f25c8 : 00000000`00000728 fffffa80`079d4820 fffff800`00ba8e70 00000000`0c201a00 : nt!WheaReportHwError+0x263
fffff800`00ba8b70 fffff800`033f1f1a : fffffa80`079d4820 fffff800`00ba8e70 fffffa80`079d4820 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`00ba8cc0 fffff800`033e5e8f : 00000000`fffdf000 00000000`00000001 fffff800`00ba8ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`00ba8d00 fffff800`02e72fac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff800`00ba8d30 fffff800`02e72e13 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`00ba8e70 00000000`6fa46407 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`08f2fe10 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6fa46407


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

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

husker91 · 18 Jul 2011

I am overclocked, fsb overclock to be exact so processor and ram are overclocked, reduced memory multiplier to keep it in the specified range. Processor is at 3.2GHZ from 2.6GHZ. Also unlocked another 2mb of l3 cache. I'll run a memory test to see if thats what is causing it. Thanks for the help.

Another thing I noticed is that it happens most when I start a game. My gpu is overclocked as well, just dropped it to see if that could be why.

Running the SFC now as well, lol

Maguscreed · 18 Jul 2011

Well just let me clarify one thing.
A WHEA error is either the overclock, or it's damaged hardware.
There really aren't many things that generate that particular error.