Hal.dll BSOD

OcUK might build these machines and use the same overclocking profile on them all so your components might just be a bit more temperamental compared to their reference machine.

Post back with your results, will be interesting to see what it was.
 
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
 
I'm sure they do test them, chances are they can squeeze more power out of each machine if they overclocked them individually but equally it wouldn't be cost-effective to have someone messing with a machine for hours :D.

I'm still rocking an Intel E2180 @ 3.2Ghz which I build back in 2007. Probably time to upgrade!

If you get any more BSODs feel free to upload the minidumps and I'll take another look. Unfortunately the nature of hardware issues is that they're usually a pain to pin down and can happen randomly, so OcUKs testing may have just missed them.
 
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.
 
Sounds promising. I guess if it stays stable you could re-instantiate the overclock but wind it back a bit (say to 4.4Ghz) and see if it's stable there. Might be less hassle if you're happy at a sightly lower speed than sending it back.

I wouldn't have thought another hard drive would make a difference, unless you're right on the edge of the PSUs power output (I doubt it) and it's tipping it over the edge.
 
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
 
Sounds like the best option, I'm sure they'll be able to sort something out.

Depends how much you can be bothered messing with the overclock too I guess, if you're prepared to spend a few hours then you'll be able to sort it out I'm sure.
 
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
 
Definitely sounds like a step in the right direction :).

Now you know what it is the shop staff should have a better idea in assisting you, they might have some updated overclock settings for you to try.
 
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.
 
Np, glad you got it sorted.

A dodgy overclock can pretty much take anything out and give very random errors; if the CPU is corrupting data then whatever is using that data is likely to go wrong so you can easily go down the wrong path thinking it's something else.
 
You must log in or register to reply here.
Back
Top Bottom