Random BSOD x124 caused by hal.dll

Jakeulas · 08 Nov 2012

yea, just tried turning off 2 cores. Same result, 10 min in and BSoD. Other than running that game, my pc seems to be running smoothly. Even the couple hours in Diablo 3 hasn't caused in issue.

I asked in the GW2 forums if anybody has found a fix with their specific issues. Nothing yet.
I'm now debating on upgrading my cpu to the 8350 Pile Driver or getting a new GPU. Of course, since I've nearly rebuilt a computer, why stop until its all been redone. Might have it finished buy Xmas.

Britton30 · 08 Nov 2012

Back there somewhere your dump mentioned a Fatal Error with the CPU, I'd go with that first. Also a few of these blamed, AuthenticAMD.
The FX8350 has some good Newegg reviews.
If you hadn't already bought a board, I would have suggested an Ivy Bridge setup.

Jakeulas · 12 Nov 2012

Hey, So It's not just the game. I've played a few movies lately and I'll get the same BSoD after 20-30min. The cheaper route is obviously a CPU.
Yes, had I thought that the CPU was bad before the board, I would've gone with an Ivy Bridge setup too. maybe in the distant future. :)

As Of now, I think I'll spend the money and get the FX-8350 pile driver cpu. I dont want to upgrade again for another couple years.
However, I noticed my graphics card is having a difficult time playing 2 movie files simultaneously. They both studder something awful. If you could recommend a better graphics card as well, I'll save up for that too.

Thanks

Britton30 · 12 Nov 2012

Well...your GPU seems like a good one unless it has just went bad. 1GB of GDDR5 and a 256 bit interface is fairly high end. You can get one with 2GB of GDDR5 and it may work better.

How do you watch two movies at once?

Jakeulas · 19 Nov 2012

I want to Thank you guys for your help on this matter. I hope you both have a Great week and Happy Thanksgiving.

Update: yesterday I was trying to update my iPad in iTunes when it BSoD

, Except it didn't recover it went into a restarting boot loop. So I opened the Bios and realized when I swapped out my motherboard I never reconfigured it to ACHI.

So, I switched that, but I still had my HDD plugged in. So I shutdown, unplugged it, booted from my win 7 cd, and deleted the previous partition and formated the SSD. Reinstalled windows. Booted up and installed all the drivers from my gigabyte cd. Shutdown and then reconnected my HDD. This time I noticed the HDD had a partition that was being recognized that wasnt previously, so I selected the partition and deleted via a tut I found. Restarted. Downloaded various programs and what not to get my system back to where it was. In all this time, no problems or BSoD. So why the hell not, I loaded up GW2 and SURPRISE

it played for 2 hrs without incident. So I decided to do all the things that would cause a BSoD to return from previous attempts. So far over the course of 5 hrs and trying to recreate a BS I have yet to get one.

I have no idea what the problem was, but maybe that partition on my HDD was causing a conflict with the operating system? It once ran win7 but once I got the SSD, I just used it as storage.

So, I will monitor this for 2 weeks, (I'll be outta town for a few of those days) with intentionally trying to recreate the x124 BSoD. If, I can't after 2 weeks I suppose we can mark this solved. :)

Britton30 · 19 Nov 2012

Thanks for the update. Let us know how it goes. :)

Arc · 20 Nov 2012

Eagerly waiting for your next update in this thread. If all goes well, we will get some new direction..

Jakeulas · 22 Nov 2012

So I decided to startup the PC and I get a BSoD right off the batt. Only difference from now and then was I installed all the Windows updates. So here is the dump file. I'm starting to feel like this is a software issue, or a conflict with a windows update.

Arc · 22 Nov 2012

Sorry to say, but ....

Code:

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

Use !analyze -v to get detailed debugging information.

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

Probably caused by : AuthenticAMD

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

It is the same

Britton30 · 22 Nov 2012

Have you checked for a BIOS update? Sorry if you did, I just didn't want to search through 9 pages.