BSOD playing FFXIV ARR, hal.dll error 0x00000124

Montoo · 01 Sep 2013

Now I don't have a solution for you, and I neither want to make things harder then they already are, but I just wanted to say I have the EXACT same error (0x00000124 HAL.DLL) as you, and it always BSOD's while playing Final Fantasy XIV A Realm Reborn, just like you. I've searched the forums from Square Enix and we're not the only ones with BSOD's or game crashes. I don't know the BCC or faulty driver from other people though.

Now, I didn't run an awful lot of tests yet, but I did check my core temperatures while my computer is running and they are all normal. I also cleaned out my pc a few weeks ago so dust can't be the problem. And the BSOD's seem only to occure while playing FFXIV ARR, just like juiceisloose. I don't have any BSOD's while playing other games.

It may just be a hardware problem. but because multiple problems have the same problem I think it's more likely there is a fault link between FFXIV and a faulty random driver.

YoYo155 · 01 Sep 2013

Montoo, Thank you for your input.
I have noticed a small amount of relation between Final Fantasy and the 0x124 bugcheck lately myself.
But as things stand we don't have enough of samples to verify a clear connection between the two.
If you can bring to the table more cases with the same circumstances then we might have something here
but please don't, for the sake of the thread not losing it's course, continue this conversation here.

You're more than welcome to open a thread in the General Discussion section of the forums :) .

juiceisloose · 12 Sep 2013

YoYo155 said:

juiceisloose said:

Yes, I understand that and as I mentioned I ran the tests already and posted the results in my initial post. I've also done the calculator for psu prior to this issue and I was under the 500w that my psu provides. I checked it again for completion sake and it is 411w.

Thanks.
411W out of 500W on 5 years old PSU is a lot to ask as components deteriorate faster
when they are run close to the top end of their spec.
Do you have a different PSU you can install for testing purposes?

Also your hard-drive is of 160GB capacity, those models are usually from 2008 and prior
which makes it very old, I suggest testing the HDD.

Code:

Model    WDC WD1600AAJS-22PSA0 ATA Device
Size    149.05 GB (160,039,763,968 bytes)

Testing the HDD:

Perform a Disk Check | Disk Check
Then Post the results following | THIS METHOD
Download SeaTools for Windows if you don't want to use a CD to test the HDD you can use YUMI – Multiboot USB Creator to create a bootable USB (instructions are found at the bottom of both pages).
If SeaTools for Windows is unable to recognize your HDD visit HDDdiag and follow the instructions.

How did you test the RAM?
What program did you use and for how many consecutive passes did you let it run for?

Updated the power supply, apparently that wasn't it as I ran into the issue after it was installed. Not a BSOD but the display/card hangs and then recovers.

New PSU info: Seasonic SS-660XP2 ATX 12V/EPS 12V, 660W, 80 PLUS PLATINUM

I did notice my MB voltage appears to be off? What would cause that? For example my -12v reading is -6.

YoYo155 · 15 Sep 2013

I encounter that to be the case with almost every PC / PSU combination I believe it's an error to do with the software
as I manually tested the voltages using a multimeter and it wasn't the case.

Now you're encountering a different problem which is called a TDR.

H2SO4 said:

These are all stop 0x116 VIDEO_TDR_FAILURE conditions.

It's not a true crash, in the sense that the bluescreen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception.

Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OSs like XP to crash. As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds. If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.

If playing with video driver versions hasn't helped, make sure the box is not overheating. Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU. Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference. If so, it might be as simple as dust buildup and subsequently inadequate cooling.

YoYo155 said:

The CHKDSK looks to be in order, did you manage to test the RAM and the HDD using Seatools (or WDLG) yet?

Upload a new file created by the SFDT, to give a broader perspective on the state the system is in.
Has anything changed at all part for the PSU (software & hardware-wise)?