Hal.dll BSOD

Jotunkaiser

Jotunkaiser

Jotunkaiser

Associate
Joined
17 Apr 2009
Posts
303
Location
Liverpool
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.
 
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.
 
2vsjkt0.jpg
 
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
 
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"
 
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
 
ye that makes more sense, id like to think they do test each individual machine though as its a lot of money to spend and is part of the reason I have shopped here for years, I cant say I have had a lot of problems with OCUK just niggles I suppose that anyone can have.

Its just that since buying this machine I have had nothing but trouble, I built a machine myself 4 years ago and its still going strong Q6600 etc lol.

Just fed up now with trying to fix this, it does feel more like a software issue to me than hardware though - but I will defo run stock and see and let you know.

Thanks again Pho, you are great <3
 
Well so far so good, normaly watching a video it would have crashed by now - I've just reset the cpu to stock, gonna check it for a few days so I'm 100% sure though. Thanks for catching that CPU, It was the last thing I thought it might be.

Could adding another sata HD mess up the overclock atall? because thats the only change I have made, although it did crash before I installed that HD. just wondering if it would matter.
 
the Voltage is at something like 1.36 maybe If i push it up abit more it might be stable @ 4.6ghz, I might give them a bell tomoz and see what they say as it was bought @4.6ghz but ye I guess 4.4 wont make a diff really
 
well it must have been that for sure, because I have not had a single crash since reseting to stock, I feel like a weight has been lifted haha - was really bugging me no pun intended
 
Spoke to them today, really helpful emailed me another set of settings to try but they was for a 4.8ghz clock lol, so ended up just pushing the CPU Voltage to 1.4 and its running fine @ 4.6ghz - 66 deg after 5-6hrs of prime 95 with no crashes - fingers crossed everythings fine now.

I just wanna say thanks so much Pho for catching that, I really didnt think an unstable overclock would throw up a hal.dll error, In my exp when an overclock is unstable it just reboots and resets settings etc so it must have been borderline.

But ye - Thanks again mate, I would have still been bashing my head against the wall lol.
 
You must log in or register to reply here.
Back
Top Bottom