Hal.Dll BSODs at Random Intervals

[Lodey]

Hi, Sevenforums community!

I've been experiencing BSODs lately, most of them related to hal.dll, I thought maybe they were related to an overclock, so I went back down to stock speeds and got one again about a week later. Not sure what might be causing them.

I've uploaded the last few BSODs dating back to March. Hope you all can help, thank you so much!

 

[townsbg]

That is probably the worst file to have a corrupt error message for and the thing is that it might not even be that file that is corrupted. I would either do a clean install or restore from backup however you can try a repair first. http://www.sevenforums.com/tutorials/3413-repair-install.html

 

[Lodey]

Not corrupted, eh? What could be wrong outside of that? I was hearing that that .dll has to do with overheating or something?

 

[townsbg]

That file is the interface between the OS and the hardware so if it isn't that file it could be any other OS file trying to access the computer (such as the kernel) or it could be hardware. I'd start with a repair or a reinstall.

 

[Lodey]

That seems so invasive for this, no other options? A repair doesn't seem like the worst option, though.. won't lose too much, no?

 

[townsbg]

Information
This will show you how to do a repair install (aka: in-place upgrade install) to fix your currently installed Windows 7 and preserve your user accounts, data, programs, and system drivers.

You should back up your files, pictures, music, and program installers first to be safe but this is such a low level file that there really isn't any other option. Frankly I'm surprised that you don't get blue a screen every time you boot up.

 

[axe0]

This is a 0x124, a hardware crash, a clean install won't help then.
However, we'll need more information to find out more, looking at the up times this isn't a hardware crash but something acting as a hardware crash.
Please read BSOD Posting Instructions

Please fill in your system specs

Please follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely.
How to fill in your system specs:

 

[Lodey]

Thank you, I updated my info. and filled in some other boxes.

 

[axe0]

Please don't forget :ar: http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

 

[Lodey]

Here you are.

 

[axe0]

You are running an ASUS Product ID (PID) on a Gigabyte board.
This makes your installation counterfeit.
Troubleshooting a counterfeit installation is useless as it is not known what has been modified to your system.
A counterfeit installation contains heavily modified code which causes the system to behave in unexpected ways.
For this reason, analyzing counterfeit systems is unreliable and most analysts won't try it.

OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
Registered Owner:          Lodey
Registered Organization:   
Product ID:                [COLOR="Red"]00426-OEM-8992662-00173[/COLOR] <-- ASUS PID on Gigabyte board
Original Install Date:     3/12/2014, 5:19:56 AM
System Boot Time:          4/16/2016, 1:39:22 AM
System Manufacturer:       Gigabyte Technology Co., Ltd.

I recommend to install a genuine copy of Windows.
If, after you have installed a genuine copy of Windows, you still get BSOD's we'll be happy to assist you.

 

[Lodey]

I've had the same OS installed for two plus years and it has been very stable until the past 2 months, even still, the BSODs as you can tell from the logs aren't frequent. Without getting into this discussion too much, this is a very recent problem and I honestly doubt it has anything to do with that. I can understand being bound by legal obligations here(?), but I'm not seeing a direct correlation.

 

[axe0]

It is prohibited to give support for any way of piracy per the forum rules, being it a discussion, helping with a crack, or troubleshooting on a system where a crack is present. As long as piracy is present on your system there is no support given until you can proof to have a genuine installation by posting the report of Windows Genuine and Activation Issue Posting Instruction

 

[Lodey]

That's what I figured, well, I appreciate the eagerness to help before the [giant exposition]. Wonder if that was your first order of business with these posting instructions, considering the first logs I posted and updated system specs should have been sufficient enough.

 

[axe0]

My history has teached me to first check if a system is genuine or not, non-genuine systems may or may not be a hell to troubleshoot and thus wasting time for something that may lead to no root cause.

 

[townsbg]

You are running an ASUS Product ID (PID) on a Gigabyte board.
This makes your installation counterfeit.
Troubleshooting a counterfeit installation is useless as it is not known what has been modified to your system.
A counterfeit installation contains heavily modified code which causes the system to behave in unexpected ways.
For this reason, analyzing counterfeit systems is unreliable and most analysts won't try it.

OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
Registered Owner:          Lodey
Registered Organization:   
Product ID:                [COLOR=Red]00426-OEM-8992662-00173[/COLOR] <-- ASUS PID on Gigabyte board
Original Install Date:     3/12/2014, 5:19:56 AM
System Boot Time:          4/16/2016, 1:39:22 AM
System Manufacturer:       Gigabyte Technology Co., Ltd.

I recommend to install a genuine copy of Windows.
If, after you have installed a genuine copy of Windows, you still get BSOD's we'll be happy to assist you.

So does this mean that he installed an OEM copy on a asus computer and then transferred it (or copied it) onto an gigabyte pc? If so that could explain some of his problems correct?

 

[axe0]

He simply illegal activated the installation, the illegal activation may or may not have to do with the problem, but it can't be said with certainty.

 

[townsbg]

What kind of illegal activation?

 

[axe0]

See post #11

 

[townsbg]

That doesn't help me understand how that might have happened.