Hal.dll BSOD

Jotunkaiser · 12 Feb 2012 at 18:54

Hiya all,

I recently purchased a battlefield commander machine from Ocuk with an SSD - since day one of getting the machine its none stop BSOD's. I chose to install my own Win 7 64x as I already had it.

This is the 2nd time ive done a complete install and I keep getting a BSOD refering to hal.dll sayin its causing the crashes (according to blue screen viewer)

021212-5116-01.dmp 12/02/2012 18:48:01 0x00000124 00000000`00000000 fffffa80`07124028 00000000`be200000 00000000`0005110a hal.dll hal.dll+12a3b x64 ntoskrnl.exe+7cc40 C:\Windows\Minidump\021212-5116-01.dmp 4 15 7601 291,744

I'm at my wits end now, I've tried almost everything and cannot work out what it could be, so any help would be greatly appreciated. Thanks.

Duke · 12 Feb 2012 at 19:03

Always best to check the hardware before re-installing.

Burn a copy of Ultimate Boot CD and give memtest a try.

Pho · 12 Feb 2012 at 19:07

Could you upload C:\Windows\Minidump\021212-5116-01.dmp somewhere?

robinbredin · 12 Feb 2012 at 19:08

There is a youtube video on how to fix a Hal.dll.
http://www.youtube.com/watch?v=jvMkt9fkHCI&feature=relmfu

Jotunkaiser · 12 Feb 2012 at 19:15

Pho said:
Could you upload C:\Windows\Minidump\021212-5116-01.dmp somewhere?

ye sure, will do that now

Jotunkaiser · 12 Feb 2012 at 19:19

http://www.filedropper.com/021212-5116-01 thats the dmp file

Jotunkaiser · 12 Feb 2012 at 19:54

So this could be a hardware issue?

Pho · 12 Feb 2012 at 21:13

Sorry went off to eat.

Here's your dump:

Code:

*******************************************************************************
*                                                                             *
*                        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: fffffa8007124028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000005110a, 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:  launcher.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`0316da58 fffff800`03017a3b : 00000000`00000124 00000000`00000000 fffffa80`07124028 00000000`be200000 : nt!KeBugCheckEx
fffff880`0316da60 fffff800`031db513 : 00000000`00000001 fffffa80`07129ea0 00000000`00000000 fffffa80`07129ef0 : hal!HalBugCheckSystem+0x1e3
fffff880`0316daa0 fffff800`03017700 : 00000000`00000728 fffffa80`07129ea0 fffff880`0316de30 fffff880`0316de00 : nt!WheaReportHwError+0x263
fffff880`0316db00 fffff800`03017052 : fffffa80`07129ea0 fffff880`0316de30 fffffa80`07129ea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`0316dc50 fffff800`03016f0d : 00000000`00000004 00000000`00000001 fffff880`0316deb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`0316dc90 fffff800`0300ae88 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`0316dcc0 fffff800`030c952c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`0316dcf0 fffff800`030c9393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`0316de30 00000000`0005c982 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`02dbfd34 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x5c982


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

Followup: MachineOwner

Poking the error address (Arg2):

Code:

2: kd> !errrec fffffa8007124028
===============================================================================
Common Platform Error Record @ fffffa8007124028
-------------------------------------------------------------------------------
Record Id     : 01cce9a2f54475a3
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 2/12/2012 17:41:20
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa80071240a8
Section       @ fffffa8007124180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Cache error
Operation     : Generic
Flags         : 0x00
Level         : 2
CPU Version   : 0x00000000000206a7
Processor ID  : 0x0000000000000004

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa80071240f0
Section       @ fffffa8007124240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000004
CPU Id        : a7 06 02 00 00 08 10 04 - bf e3 9a 1f ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa8007124240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8007124138
Section       @ fffffa80071242c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : GCACHEL2_ERR_ERR (Proc 2 Bank 6)
  Status      : 0xbe2000000005110a
  Address     : 0x00000001b9743140
  Misc.       : 0x000000d084024086

It looks like it may be a problem with your CPU's L2 cache. Is your CPU overclocked at all? It might be worth trying to update your BIOS too as I read that may affect it.

Also what are your CPU temps?

Jotunkaiser · 12 Feb 2012 at 21:14

it came pre overclocked to 4.6ghz from OCUK its a battlefield commander system.

Pho · 12 Feb 2012 at 21:19

Could you run Real Temp and post your temperatures?

Do you know what you're doing in terms of overclocking, and are you able to reduce the speed a bit to see if that helps (/proves the issue)?

Jotunkaiser · 12 Feb 2012 at 21:26

I know enough ye, my temps dont go above 79 but this isnt happening whilst gaming etc its just watching video's etc nothing to stressfull, sometimes I can go downstairs come back up while the comp is doing nothing but d/l and its crashed.

other times it hangs and I cant move mouse etc but I can see screen then I have to force reboot, its always sound releated ive noticed though sound+video of sorts.

Jotunkaiser · 12 Feb 2012 at 21:26

I was just watching a TV show and the same thing happend after about 10 mins or so

Jotunkaiser · 12 Feb 2012 at 21:30

Pho · 12 Feb 2012 at 21:30

79c? Intel show the TCase as 72.6 (http://ark.intel.com/products/52210/Intel-Core-i5-2500K-Processor-(6M-Cache-3_30-GHz)) which I'm fairly sure you don't want to be over for long.

Could be a heat issue if that's true.

edit: wrote that before your screenshots.

Neil79 · 12 Feb 2012 at 21:33

68c+ does seem a bit warm without even gaming, hell mine reaches close to that but ONLY in intel burn test and overclocked

Pho · 12 Feb 2012 at 21:36

I favour the declocking route, stick it down to 4Ghz or something and see how it goes, guessing you have the latest video/sound drivers etc?

I feel your pain with random crashes, my work laptop is crashing randomly and not even saving a dump file to analyse it (it is enabled to do it). Very annoying.

Jotunkaiser · 12 Feb 2012 at 21:36

Not sure thats what the checklist they sent me says - about the temps etc, I do look from time to time and ive run heaven etc and prime 95 for a while and its not really jumped anything over 79 that I can recall

Just getting a little annoyed with it now as since I have bought it, nothing but problems and I know 9 times out of 10 thats user error.

I'm trying everything just to have a stable system that doesnt crash but cannot seem to find it, My last machine still works perfect to this day without a hiccup.

This is the first time I've had an SSD though, I thought maybe @ first it was something I was doing wrong - the machine came with SSD plugged in and also a 2nd storage drive I added, I just installed w7 64x on SSD without unplugging HD.

So I thought I would reinstall today and unplug all other HD's but the same error is back again... /sigh

Jotunkaiser · 12 Feb 2012 at 21:39

My main issue with underclocking the machine is, I bought it as a pre overclocked / checked machine so surely these errors would have appeared when they tested it? or else why send me it haha.

On OCUK's check sheet it gets all ticks for testing, and it says "Max temp 79"

Pho · 12 Feb 2012 at 21:44

Well if it's crashing and it's not going over 72 then I'd say ignore that for now. To me 79 seems way too high but that might be the maximum it can get before it automatically shuts down whereas 72.6 is what you probably want to keep it under (just guessing).

I wouldn't have thought it would be to do with the SSD, the errors definitely point at the CPU but they're not 100% going to be right.

I see your point with underclocking it, but I think it would be a useful test (assuming it doesn't void any warranty with OcUKs return policy) - if you underclock it and it's stable then clearly it's an issue when it's running at 4.6Ghz so you can go back to the store and get them to replace it.

Jotunkaiser · 12 Feb 2012 at 21:47

There is a profile saved in the bios, what I might do is run it @ stock and then reload the profile if needs be, I have had the error "overclock failed" before on boot.

Thanks for all the help mate, really greatfull - ive been at this for about 8hrs lol