Overclock.net › Forums › Intel › Intel - General › Hal.dll BSOD on i7 920 - need some help
New Posts  All Forums:Forum Nav:

Hal.dll BSOD on i7 920 - need some help

post #1 of 12
Thread Starter 
A few months ago I pieced together a 1366 build for my girlfriend, and she has been receiving daily, constant BSOD's for Hal.dll

Hardware list:
Windows 7 Home Premium x64
CPU: i7 920
Mobo: EVGA x58 SLI3
RAM: Corsair Vengeance 1600 (3x2GB)
GPU: EVGA GTX560 448 core
PSU: Corsair AX750

The BSODs don't seem to be related to a certain game or application, and will happen even while the PC is idle.

We have reformatted the HDD, updated the BIOS on the motherboard, and neither helped.

I will attach the most recent .dmp file, and appreciate any and all help anyone can provide.

050312-27066-01.zip 21k .zip file
Edited by itskerby - 5/3/12 at 12:21am
post #2 of 12
Hi smile.gif

The dump you've attached is a x124 hardware BSOD pointing to intelppm.sys (Intel Processor Driver), this is a Windows component, so it is not the official cause and something else is driving it to fault (especially since it's a x124 hardware bugcheck).

The following can cause a x124 hardware bugcheck:

1. Unstable overclock. Any hardware that is brought beyond its stock specifications can and will cause issues if the overclock is in fact unstable.

2. Inadequate cooling / overheating. Ensure that the computer is being properly cooled, all fans are running as they should, and the system / fans are cleaned of dust every few months.

3. Out-of-date hardware related drivers (video, sound, NIC, etc),.

4. Not having the latest BIOS.

5. Hardware failure.

Here's what you can do to determine the cause of hardware failure if all else fails and you've ruled out software:

1. Run CHKDSK:

Open the "Computer" window
Right-click on the drive in question
Select the "Tools" tab
In the Error-checking area, click .

2. Run Memtest to test your memory for errors.

3. Stress test your video cards with your choice of a program (FurMark, etc) to ensure the video cards aren't artifacting at stock settings and that there are no crashes.

4. If all else fails, start removing hardware one at a time and try and find a culprit.

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


Loading Dump File [C:\Users\Cardbox\Downloads\050312-27066-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02e08000 PsLoadedModuleList = 0xfffff800`0304c650
Debug session time: Thu May  3 01:28:37.880 2012 (UTC - 4:00)
System Uptime: 0 days 21:11:32.817
Loading Kernel Symbols
...............................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8007e90028, fa000000, 400405}

Unable to load image \SystemRoot\system32\DRIVERS\intelppm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : hardware

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffffa8007e90028, 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:  
fffff800`00ba8a98 fffff800`03402a3b : 00000000`00000124 00000000`00000000 fffffa80`07e90028 00000000`fa000000 : nt!KeBugCheckEx
fffff800`00ba8aa0 fffff800`02f94b33 : 00000000`00000001 fffffa80`07e77450 00000000`00000000 fffffa80`07e774a0 : hal!HalBugCheckSystem+0x1e3
fffff800`00ba8ae0 fffff800`03402700 : 00000000`00000728 fffffa80`07e77450 fffff800`00ba8e70 fffff800`00ba8e00 : nt!WheaReportHwError+0x263
fffff800`00ba8b40 fffff800`03402052 : fffffa80`07e77450 fffff800`00ba8e70 fffffa80`07e77450 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`00ba8c90 fffff800`03401f0d : 00000000`00000008 00000000`00000001 fffff800`00ba8ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`00ba8cd0 fffff800`033f5e88 : 00000000`00000000 fffff800`02ff9e80 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`00ba8d00 fffff800`02e8356c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`00ba8d30 fffff800`02e833d3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`00ba8e70 fffff880`043ed9c2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff800`00b9cc98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm+0x39c2


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

post #3 of 12
Thread Starter 
Thanks E-Peen,

1. Unstable overclock. Any hardware that is brought beyond its stock specifications can and will cause issues if the overclock is in fact unstable.
No overclocks, everything is running stock.
2. Inadequate cooling / overheating. Ensure that the computer is being properly cooled, all fans are running as they should, and the system / fans are cleaned of dust every few months.
Temperatures are good, that was my first thought when it started.
3. Out-of-date hardware related drivers (video, sound, NIC, etc),.
Unless for some reason EVGA is packaging out of date LAN or Audio drivers on their website, we have the latest drivers installed.
4. Not having the latest BIOS.
Bios is on the latest version
5. Hardware failure.

I have a sinking feeling it's going to be the processor. It's (of course) the only part that wasn't bought new, it's from Ebay.
I'll start swapping out hardware and see if we can narrow it down, I was just holding out hope that maybe it was a rogue driver crash.

(+Rep)
post #4 of 12
Quote:
Originally Posted by itskerby View Post

I'll start swapping out hardware and see if we can narrow it down, I was just holding out hope that maybe it was a rogue driver crash.
(+Rep)

Before you start swapping out hardware, I'd suggest running diagnostics (Furmark for GPU, memtest for RAM, chkdsk for HDD, etc) I have recommended above to save yourself some time and aggravation when it comes to removing parts.
post #5 of 12
Thread Starter 
Quote:
Originally Posted by E-Peen View Post

Before you start swapping out hardware, I'd suggest running diagnostics (Furmark for GPU, memtest for RAM, chkdsk for HDD, etc) I have recommended above to save yourself some time and aggravation when it comes to removing parts.

Yeah I meant to add that to the main post, Furmark passes the Extreme Burn in test with no artifacts, peaks at ~68C. I have an aggressive fan profile set up with Afterburner, that was where I started.
I checked a few weeks ago with a R/O Chkdsk, and there were no bad sectors, have not done a Chkdsk /F though.
We'll start the memtest tonight.
post #6 of 12
Make sure for Memtest, you run it for multiple passes. I'd recommend running it overnight and checking it when you wake up. Also, with Asus P67 boards, it's recommended to disable Legacy USB Support and burning Memtest to a disc as USB is known to cause false positives / incorrect errors with Legeacy USB Support enabled on P67 boards.

After you finish testing, you can re-enable Legacy USB Support once again (enable and disable in the EFI BIOS).
post #7 of 12
Thread Starter 
Quote:
Originally Posted by E-Peen View Post

Make sure for Memtest, you run it for multiple passes. I'd recommend running it overnight and checking it when you wake up. Also, with Asus P67 boards, it's recommended to disable Legacy USB Support and burning Memtest to a disc as USB is known to cause false positives / incorrect errors with Legeacy USB Support enabled on P67 boards.
After you finish testing, you can re-enable Legacy USB Support once again (enable and disable in the EFI BIOS).

Ah, this isn't for my sig rig, it's for a different one.

Hardware list:
Windows 7 Home Premium x64
CPU: i7 920
Mobo: EVGA x58 SLI3
RAM: Corsair Vengeance 1600 (3x2GB)
GPU: EVGA GTX560 448 core
PSU: Corsair AX750

Is 7 passes good for Memtest, or would you recommend more?
post #8 of 12
Quote:
Originally Posted by itskerby View Post

Ah, this isn't for my sig rig, it's for a different one.
Hardware list:
Windows 7 Home Premium x64
CPU: i7 920
Mobo: EVGA x58 SLI3
RAM: Corsair Vengeance 1600 (3x2GB)
GPU: EVGA GTX560 448 core
PSU: Corsair AX750
Is 7 passes good for Memtest, or would you recommend more?

7-8 is usually the amount I recommend.
post #9 of 12
Thread Starter 
Just to follow up on this thread with an update (Don't you hate it when there's no conclusion to troubleshooting theads? tongue.gif)

I was browsing around an old i7 920 overclocking thread, and they referenced the 124 BSOD in relation to overclocking.

Now this proc is running completely at stock but I figured it was worth a shot, so I increased vcore by 2 steps.

Where the PC was going to the hal.dll 124 BSOD 1-2 times a day, I'm now up to 48 hours with no crashes.

I will update again after more time has passed.

EDIT: To follow up on other suggestions, the Memory passed 7 passes of Memtest with no errors, and Chkdsk came back clean. So HDD and RAM are not the culprit.
post #10 of 12
Hello, how's your system now?
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Intel - General
Overclock.net › Forums › Intel › Intel - General › Hal.dll BSOD on i7 920 - need some help