A problem with hal.dll+12a3b - Windows 7 x64

R

ric80231

Active member
Joined
Jun 7, 2015
Posts
40
Hi,

I have had a problem with my PC for quite a while. It manifested itself as a BSOD or a hang. I finally went back to the manufacturer, they took it in and ran disk tests on it for a week, no problems. Then they reinstalled Windows, it ran fine for another day. As everything seemed to be fine at that point, the machine was returned to me.

As I started to recover machine, at first everything seemed fine, then after I had restored the backup and installed a few apps, (Lightroom, Photoshop, Firefox, Adobe Reader and Cloud Station Client(an app to sync my computer to my Synology Diskstation). I experienced an Unexpected Stop.

Since then I have restored to system to the point before Cloud Station Client was installed and I am still experiencing Unexpected Stops, these though are generating minidumps (they don't always), I was able to look at with BlueScreen Viewer. They identify hal.dll_12a3b as the cause.

I have run mdsched with no errors, and as I said the disk tests were run for a week with no problems.

I am attaching a zipped file containing the results of the SysnativeBSODCollectionApp and perfmon.

I am at my wit's end, as I said the manufacturer cannot find any faults. Could you please help me?

Sincerely R A Evans
 

Attachments

Re: A problem with hal.dll+12a3b

A little more information, after completing the above entry I ran Driver Verifier, when I ran the thrid test 'All drivers installed on the computer.' It crashed the PC. 'ghfly.sys was given as the address. I had to use system recovery and restore to a previous point to recover.
 
Re: A problem with hal.dll+12a3b

Just found the BSOD Posting Instructions, so here are the other details you ask for:

  • OS Windows 7
  • x64
  • What was original installed OS on system? Windows 7 64 bit
  • Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? OEM version pre-installed
  • Age of system (hardware)? less than a year
  • Age of OS installation - have you re-installed the OS? reinstalled Thursday 4th June
  • CPU? IntelCore i7-4790K @4.ooGHz
  • Video Card? GEForce GTX780
  • MotherBoard - (if NOT a laptop)? Gigabyte Z97X-SLI
  • Power Supply - brand & wattage (if laptop, skip this one) Novatech 600w I think
  • System Manufacturer? Novatech
  • Exact model number (if laptop, check label on bottom) NTI128
  • Laptop or Desktop? Desktop
 
Re: A problem with hal.dll+12a3b

Re-enable verifier, let it crash, boot to safe mode, turn it off, upload latest verifier crash dump.
 
Re: A problem with hal.dll+12a3b

Thanks for the reply, I apologize for not responding quicker. The machine has gone into the manufacturer again. With what I had learned on this forum and the tools it recommended, I was able to convince them that there were serious problems with the machine. I have to admit though that I was not impressed with them, they had not heard of the verifier tool. I hadn't either, but it is not my job to repair computers. If you wish I did take a picture of the BSOD for reference. I can upload that if you wish.
 
Re: A problem with hal.dll+12a3b

Most customer support representatives simply read from scripts, unless your able to get through to higher tier support.
 
Re: A problem with hal.dll+12a3b

That i7-4790k is a great part and should run cooler than the 4770k that it replaced, but I've seen a number of OEMs using stock coolers. Bad, bad, bad idea. Just because the adhesive process between the cores and the heatsink was better doesn't mean it still doesn't run incredibly hot. 4790k's amount for a lot of the 0x124s I'm seeing lately, and they've all gone back for replacement. I'm not surprised you need a new machine, honestly.
 
Re: A problem with hal.dll+12a3b

Hi Everybody,
I know it's been a long time , I've only just got the machine back from the manufacturer. After spending a week faffing around they replaced the motherboard. Guess what it still crashes in exactly the same way. I don't think I've mentioned this before, as at first I didn't realise. It crashes when you leave it alone. The screensaver kicks in displays a few things and then it crashes.

Obviously, it is going back to the manufacturer again. Does anybody have any suggestions?
 
Re: A problem with hal.dll+12a3b

Hi,

As you will have guessed I am still having problems, lots of unexpected stops and this morning the latest BSOD. I am attaching the WinDbg analysis of the "C:\WINDOWS\MEMORY.DMP" file and of a minidump that occured about the same time. I am not expert enough to establish if they are identical.

There is an event in the Event Viewer at around the same time.

Log Name: Application
Source: Microsoft-Windows-WMI
Date: 29/06/2015 02:23:52
Event ID: 10
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Brittanic
Description:
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WMI" Guid="{1edeee53-0afe-4609-b846-d8c0b2075b1f}" EventSourceName="WinMgmt" />
<EventID Qualifiers="49152">10</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-06-29T01:23:52.000000000Z" />
<EventRecordID>12845</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>Brittanic</Computer>
<Security />
</System>
<EventData>
<Data>//./root/CIMV2</Data>
<Data>SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99</Data>
<Data>0x80041003</Data>
</EventData>
</Event>
​

I was opening Photoshop when the BSOD occured.


Any help tracking this fault down would be appreciated.

I also have a question: Why was this BSOD saved as C:\Windows\MEMORY.DMP and not as a standard minidump?


SIncerely R A Evans
 

Attachments

I am attaching the WinDbg analysis of the "C:\WINDOWS\MEMORY.DMP" file
Click to expand...

Can you upload the MEMORY.DMP file to a drive site (Google, Onedrive, etc) and paste the link to it here?

Make sure to zip the MEMORY.DMP file before upload it so it's compressed.
 
Code: 
5: kd> .bugcheck
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`1078a028 00000000`bf800000 00000000`00200401

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

Error         : Internal unclassified (Proc 5 Bank 1)
  Status      : 0xbf80000000200401
  Address     : 0x00000000fee00040
  Misc.       : 0x0000000000000086

Unclassified error, processor #5 and cache bank #1.

Not sure why they replaced the mobo, because it's likely the CPU or the RAM really. Run Memtest for 8 passes to be sure it's not the RAM.

Memtest86+:

Download Memtest86+ here:

Memtest86+ - Advanced Memory Diagnostic Tool

Which should I download?

You can either download the pre-compiled .ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).

Do note that some older generation motherboards do not support USB-based booting, therefore your only option is CD (or Floppy if you really wanted to).

How Memtest works (you don't need to read, it's only for those interested in the specifics):

Memtest uses algorithms (specifically two), namely moving inversion & what is deemed Modulo-X. Essentially, the first algorithm fills the memory with a pattern. Starting at the low address, it checks to see if the pattern was changed (it should not have been), writes the patterns complement, increments the address, and repeats. Starting at the highest address (as opposed to the lowest), it follows the same checklist.

The reason for the second algorithm is due to a few limitations, with the first being that not all adjacent cells are being tested for interaction due to modern chips being 4 to 16 bits wide regarding data storage. With that said, patterns are used to go ahead and ensure that all adjacent cells have at least been written with all possible one and zero combinations.

The second is that caching, buffering and out of order execution will interfere with the moving inversions algorithm. However, the second algorithm used is not affected by this. For starting offsets of 0-20, the algorithm will write every 20th location with a pattern, write all other locations with the patterns complement, repeat the previous one (or more) times, and then check every 20th location for the previously mentioned pattern.

Now that you know how Memtest actually works, it's important to know that the tests it goes through all mean something different. It goes from Test 0 through Test 12, many of which use either one or the other algorithm discussed above, among many other things.

Any other questions, they can most likely be answered by reading this great guide here:

FAQ : please read before posting
 
Sounds like your OEM is bad at understanding problem descriptions put forth by hardware. As Patrick says, run a memtest, but if that passes, DO NOT LET THEM GO UNTIL THEY REPLACE YOUR FAILING CPU. Period.

Yes, I meant the caps ;).
 
Hi,

I ran the Memtest as you recommended and after 8 passes it still had no errors, I am attaching a picture of the results. I intend to reference this thread in my next submission to them.

Patrick and Cluberti, thanks to you both for your help.

Sincerely Ric Evans
 

Attachments

  • Memtest Results.jpg
    Memtest Results.jpg
    171.6 KB · Views: 1
Hi Everybody,

Just got the machine back from the manufacturer's, they replaced the CPU this time. After all the problems, I am not ready to trust them. I ran Prime95 as a CPU test and monitored the temperatures. The CPU reached 91C, before I terminated the test. The System Viewer app I have reported the CPU fan running at 1584 rpm.

I am not an expert in these matters, but I consider 91C to be too high a temp for the CPU. In the past the highest temp I have seen in this system is 62C. From what I've read, consistently running at that temperature shortens the life of the component.

In a previous post, Cluberti mentioned:
That i7-4790k is a great part and should run cooler than the 4770k that it replaced, but I've seen a number of OEMs using stock coolers. Bad, bad, bad idea. Just because the adhesive process between the cores and the heatsink was better doesn't mean it still doesn't run incredibly hot. 4790k's amount for a lot of the 0x124s I'm seeing lately, and they've all gone back for replacement. I'm not surprised you need a new machine, honestly.
​
Click to expand...

Am I correct in think he is right and the problem stems from inadequate cooling being provided? Novatech have already tried to sell me a replacement CPU fan. Am I being overly suspicious?

Any help or susgestions you can provide would be gratefully received.

Sincerely R A Evans
 
I wouldn't run P95 unless I absolutely had a reason to.

For one, it depends on the setting you chose. Did you choose Blend? If so, it's about as hard as you can push your system. It's generally beyond any normal stress, and that's why it's a stress testing program that's popular for overclocking. The stress you're putting your hardware under during P95, especially Blend, is not even close to what you'd get doing things such as regular browsing, or even gaming.

With that said, you're also running an OEM machine, so chances are you have the stock heatsink/cooler. Branching off of that, it's not a great cooler. It's not a bad cooler, but again, it's not a great cooler. It's not designed to withstand extreme temperatures coming from high volumes of stress. It's designed to just keep your CPU cool for things you'd just about normally do on an OEM machine. Typically running P95 is never one of these things.

So, bottom line, unless you're actually crashing as you were before, don't use P95 unless you want to kill this one too, because then warranty wouldn't even be a possibility. The next thing for you to do is monitor your temperatures under normal OEM conditions, such as browsing the internet (generally idle), and playing a game or a full-screen 3D application. If the temperatures remain fine during idle/load, you have nothing to worry about.
 
Core Temp is indeed a good tool, as is RealTemp. If you're looking to replace the stock cooler, talk to Novatech about what they offer and consider it if you're going to be pushing the system with new games or high-end graphics work on a regular basis. If you're just going to run the machine under "normal" conditions most of the time, you should be OK with what shipped with the machine.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top