Sign in with
Sign up | Sign in
Your question
Solved

Hal.dll Blue Screen (new i5 2500k and mobo)

Last response: in CPUs
Share
August 25, 2011 11:25:36 AM

I need some help. I keeping getting a blue screen when I play Battlefield Bad Company 2 for an hour or so. I JUST bought a i5 2500k and a Gigabyte z68x-ud3h-b3 today. Windows tells me the following


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA800A5B4028
BCP3: 00000000BF800000
BCP4: 0000000000200001
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

I downloaded the program WhoCrashed and it tells me:

On Thu 8/25/2011 11:42:57 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082511-64553-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800A5B4028, 0xBF800000, 0x200001)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

If anyone can help it would be much appreciated.
a b à CPUs
August 25, 2011 11:51:12 AM

Well, HAL deals with hardware abstraction, and its very unlikely the DLL itself is at fault. So I'd blame hardware.

First and formost, run a memory check. That should be SOP on the occurance of any BSOD.
m
0
l
August 25, 2011 12:01:25 PM

How do you do a memory check?
m
0
l
Related resources
a c 138 à CPUs
August 25, 2011 12:02:48 PM

Are you under overclock ?
0x000000124 Seem not enough PLL / vcore
m
0
l
August 25, 2011 12:07:10 PM

henydiah said:
Are you under overclock ?
0x000000124 Seem not enough PLL / vcore


I am currently overclocked. I used the gigabyte program Easytune6 to do it. Are you saying that something might not be set high enough?
m
0
l
August 25, 2011 12:11:36 PM

henydiah said:
Are you under overclock ?
0x000000124 Seem not enough PLL / vcore


Now that you mention it, CPUZ says my Core Voltage is 1.056. That seems a tad low, no?
m
0
l
a c 138 à CPUs
August 25, 2011 12:14:01 PM

Yep .. Cpu voltage not enough
m
0
l
August 25, 2011 1:00:07 PM

I just changed the core voltage to 1.350 and CPUID still shows it as 1.056. Should I not trust CPUID or is there something wrong?
m
0
l
a c 138 à CPUs
August 25, 2011 4:39:49 PM

I don't know watta the trush , I suggest uninstall easytune6 .( This software not worth) go default
m
0
l
a b à CPUs
August 25, 2011 4:54:19 PM

That chip is dynamic with voltage, unless you set the mode to Fixed voltage. If you are overclocking, then you need to make sure you are using Fixed voltage, not offset or anything else. That way when you find the stable voltage, you know it's actually the voltage you chose and not the chip auto correcting.

To reiterate, your chip showing 1.056 is normal if it is idle or not under load. Check to see if the CPU voltage goes up when you run a program that uses the CPU like prime 95. You may see it rise just by launching a "big" program.

As far as the error, ^ said check into the memory with a program called memtest86, its pretty accurate and only takes an hour or two. It can be burned to bootable CD so you dont even need windows installed.
m
0
l
August 25, 2011 10:24:25 PM

festerovic said:
That chip is dynamic with voltage, unless you set the mode to Fixed voltage. If you are overclocking, then you need to make sure you are using Fixed voltage, not offset or anything else. That way when you find the stable voltage, you know it's actually the voltage you chose and not the chip auto correcting.

To reiterate, your chip showing 1.056 is normal if it is idle or not under load. Check to see if the CPU voltage goes up when you run a program that uses the CPU like prime 95. You may see it rise just by launching a "big" program.

As far as the error, ^ said check into the memory with a program called memtest86, its pretty accurate and only takes an hour or two. It can be burned to bootable CD so you dont even need windows installed.


It's at 1.056 core voltage even when I run prime95.
m
0
l

Best solution

August 25, 2011 11:07:17 PM

Honestly, Uninstall EasyTune 6, Reset You're BIOS to Defaults, and OC from the Bios.
Share
August 25, 2011 11:46:58 PM

nocredrs said:
Honestly, Uninstall EasyTune 6, Reset You're BIOS to Defaults, and OC from the Bios.


Okie dokie. I'll give that a shot. I'm at work now so it will be a 12 hours til I get to try that.
m
0
l
September 2, 2011 1:30:45 AM

Best answer selected by prognosis.
m
0
l
February 9, 2013 10:02:31 PM

Just wondering if you ever got this problem fixed. I am running an AMD Phenom II X6 1100T on an ASRock 970 Extreme4, at stock speed and voltage, and I am getting that EXACT same error, and the EXACT same thing that you have when I run WhoCrashed. If you did get this fixed, I would love to know what you did to fix it, cause I have been messing with mine for a month now, and have even took it to a shop, and it still does it.
m
0
l
!