Random BSOD x124 caused by hal.dll

Arc · 09 Sep 2012

You are welcome :) Take your time, if needed, ask for help.

Best of luck!

Jakeulas · 10 Sep 2012

Hey ARC, do you have any recommendations for driver scanning/updating software? I noticed a few drivers are from clear back in 2006.
Thanks in advance.

Arc · 10 Sep 2012

Mate you may try DriverMax for this purpose.

Jakeulas · 10 Sep 2012

Well, in the middle of writing an update of how well everything seemed to be going...
I got another BSOD.

As of this morning, I removed the stock heat sink and installed a Corsair H60 water cooler on the cpu. Then ran Prime95 for 2 hours. (txt file included)

I only had a couple of outdated drivers, installed those. I'll keep working on the list.
Thanks. Please let me know if you see anything in the dump file.

Arc · 10 Sep 2012

Very good news that the test successfully passed.

But, all the three crashes of today indicated the same thing, as earlier.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8008d8c028, b6004000, 64000135}

Probably caused by : hardware

Followup: MachineOwner
---------

It is a hardcore hardware issue. So, suggestion will be just the same as earlier.

In this situation, you are follow the Generic "Stop 0x124" Troubleshooting Strategy .
For the information, follow the link : Stop 0x124 - what it means and what to try.

Follow all the steps from #1 to #9. One of them must work for you, but it is very difficult to say which one is the most appropriate one for you.

If all fails, follow the step #9.

Jakeulas · 10 Sep 2012

Thanks ARC, I will continue through the list. I was reading about the AMD FUEL.SERVICE.EXE and a lot of forums indicate that users are having similar issues with it. I disabled it in the startup services (msconfig) and also deleted this associated driver (AODDriver4.1) causing issues from Control Catalyst 12.8.

Doing this, people have posted as solving their issues with that BSoD error.

We'll see what comes of it.

Arc · 10 Sep 2012

Jakeulas said:

Thanks ARC, I will continue through the list. I was reading about the AMD FUEL.SERVICE.EXE and a lot of forums indicate that users are having similar issues with it. I disabled it in the startup services (msconfig) and also deleted this associated driver (AODDriver4.1) causing issues from Control Catalyst 12.8.

Doing this, people have posted as solving their issues with that BSoD error.

We'll see what comes of it.

Well done!
CCC is always a trouble. I wish it will help you to solve your problem.

Jakeulas · 11 Sep 2012

A New day, a new problem discovered. Lol

So, I decided to run a dskchk and defragment last night, all night.

Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
99328 file records processed. File verification completed.
98 large file records processed. 0 bad file records processed. 0 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
136906 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
99328 file SDs/SIDs processed. Cleaning up 4 unused index entries from index $SII of file 0x9.
Cleaning up 4 unused index entries from index $SDH of file 0x9.
Cleaning up 4 unused security descriptors.
Security descriptor verification completed.
18790 data files processed. CHKDSK is verifying Usn Journal...
36162984 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
99312 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
228615636 free clusters processed. Free space verification is complete.
Windows has checked the file system and found no problems.

976657407 KB total disk space.
61909132 KB in 76310 files.
54992 KB in 18791 indexes.
0 KB in bad sectors.
230739 KB in use by the system.
65536 KB occupied by the log file.
914462544 KB available on disk.

4096 bytes in each allocation unit.
244164351 total allocation units on disk.
228615636 allocation units available on disk.

Internal Info:
00 84 01 00 89 73 01 00 60 d8 02 00 00 00 00 00 .....s..`.......
b3 03 00 00 2c 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 ................

Windows has finished checking your disk.
Please wait while your computer restarts.

Everything looks fine, but when the machine rebooted I got this error and noticed every time I reboot I get this error in event viewer.

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.

I researched it a bit and only came to one solution, a Microsoft Fixit. I applied the patch, lets hope it helps.

If you have anymore suggestions, I continue to appreciate your help and namely just the idea I'm not doing this by myself.

Arc · 11 Sep 2012

Continue with your plan. Best of luck. :)

If needed, we are here.

Jakeulas · 11 Sep 2012

Hey Arc,
I've nearly completed my work through the list. Ran tests now all on pieces of equipment. Ran memtest86+ for 7 hrs, no errors. GPU furmark bench test, and everything else I could think of. The last thing to do is a "vanilla" install. I plan to do this on my SSD, was hoping to fix this before I switched over.

Today, I decided to just leave the pc on without actually using it. BSoD when i woke the pc from idle. I can't understand that. I guess, I'm just going to have to rebuild.