Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › BSOD with Hal.dll
New Posts  All Forums:Forum Nav:

BSOD with Hal.dll

post #1 of 4
Thread Starter 
So today I got a BSOD while watching a video and listening to music and thought it was a one off kind of thing until I got it again 2 hours later. I will attach my minidump to this post so that someone can please help me with this problem. Thank you.

New WinRAR ZIP archive.zip 19k .zip file
post #2 of 4
Hi smile.gif

I've analyzed your dump file and it's your traditional x124 hardware BSOD. The most basic cause of this BSOD is an unstable overclock, and I noticed your system is OC'd, so please return ALL overclocks to stock. You're more than welcome to OC again once we've solved your issue.

Took a quick look at your drivers list and your ASACPI.sys driver is dated from 2005. The pre 2009 driver is a very large causer of BSODs. (Asus ATK0110 ACPI Utility (a known BSOD maker in Win7). Also a part of the Asus PCProbe and AISuite Utilities). Update it here.

Driver(s) that need to be updated:
000.fcl - Fri Sep 26 09:11:22 2008 (CyberLink FCL Driver). Update here.

Dump for reference:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\Icarus\Downloads\041512-8330-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02a59000 PsLoadedModuleList = 0xfffff800`02c9d650
Debug session time: Sun Apr 15 22:27:49.692 2012 (UTC - 4:00)
System Uptime: 0 days 3:06:13.816
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80042c7028, b401a000, 135}

Probably caused by : hardware

Followup: MachineOwner

3: kd> !analyze -v
*                                                                             *
*                        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: fffffa80042c7028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b401a000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000135, Low order 32-bits of the MCi_STATUS value.

Debugging Details:

BUGCHECK_STR:  0x124_AuthenticAMD





fffff880`02fdda88 fffff800`02a22a3b : 00000000`00000124 00000000`00000000 fffffa80`042c7028 00000000`b401a000 : nt!KeBugCheckEx
fffff880`02fdda90 fffff800`02be5b33 : 00000000`00000001 fffffa80`042c8d30 00000000`00000000 fffffa80`042c8d80 : hal!HalBugCheckSystem+0x1e3
fffff880`02fddad0 fffff800`02a22700 : 00000000`00000728 fffffa80`042c8d30 fffff880`02fdde30 00000000`00000700 : nt!WheaReportHwError+0x263
fffff880`02fddb30 fffff800`02a22052 : fffffa80`042c8d30 fffff880`02fdde30 fffffa80`042c8d30 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`02fddc80 fffff800`02a15e8f : 00000000`02a71988 00000000`00000001 fffff880`02fddeb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`02fddcc0 fffff800`02ad456c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff880`02fddcf0 fffff800`02ad43d3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`02fdde30 000007fe`eba09b7c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`1ed9b0d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`eba09b7c


FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware




Followup: MachineOwner

post #3 of 4
Thread Starter 
Thanks alot for the help. I forgot to mention that I recently reinstalled W7 on my PC because I got a SSD and wanted to install it on that instead of my standard drive, so I knew I would forget to update some things. Also I thought that the OC I did was an issue since I live in New York and it's been very hot today, so when I ran Prime95 after the overclock it never passed 51C but now I'm watching a video and it's at 50C, so I will lower the OC and if it continue I will just put it back to stock until it get cooler or I get more fans.

On a side note, I got another BSOD last week when I was trying to convert something and I know it was the conversion because it happened twice during conversion. I don't want to abuse your helpfulness but if you can help me one more time I will even more grateful than I am now (I'll attach that minidump aswell).

New WinRAR ZIP archive.zip 19k .zip file
post #4 of 4
The one you've attached in your last post is also a x124 hardware bugcheck, likely the overclock as well.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Windows
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › BSOD with Hal.dll