"FFXIV Has Stopped Working"

[marianneh]

My boyfriend has the same problem (game crashing after pressing "Play") since this morning, but everything is working fine for me. That happens to him after almost every patch.

He has had the same problem before and fixed it with system restore, but that is not working anymore.

He has tried installing DirectX 9 again, deleting NVIDIA drivers with driver fusion and trying different drivers, deleting the FFXIV folder under My Games, rebooting several times, running the game as administrator, running another game in the background, even changing the sound format to 44100 Hz and god knows what else.

We have checked every forum discussion about this problem that can be found through google and tried most of the suggested fixes, but had no luck so far.

Hell, how can such a huge game be having stupid problems just like any small crappy private server. What are we even paying for, are we getting money back for the days we lost trying to fix their stupid mistakes?

If anyone has come up with a working solution to this problem, please let us know, we're really losing it here!

[Judge_Xero]

I had this issue for weeks. I finally got it solved for me, but it may help others. Nothing else seemed to mess up except for FFXIV.

I ran MEMTest86 and found that my Ram was bad. It was GSkillz 2X4GB 2133Mhz. I turned my Ram down to 1600Mhz with stock timings 9-9-9-21 2T - It passed MemTest at those settings but it would still crash FFXIV.

Swapped out to my trusty Samsung Green 1.3v Ram and everything is running great.

[marianneh]

Thank you for the answer, but sadly it didn't fix our problem

If this is any help then here is the event log:

- System
- Provider
[ Name] Application Error
- EventID 1000
[ Qualifiers] 0
Level 2
Task 100
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2014-08-21T16:36:28.000000000Z
EventRecordID 8453
Channel Application
Computer kai-PC
Security
- EventData
ffxiv.exe
1.0.0.0
53f4e8b7
ffxiv.exe
1.0.0.0
53f4e8b7
c0000005
00a84436
3d0
01cfbd5e0bb45b93
C:\Program Files\SquareEnix\FINAL FANTASY XIV - A Realm Reborn\game\ffxiv.exe
C:\Program Files\SquareEnix\FINAL FANTASY XIV - A Realm Reborn\game\ffxiv.exe
4c29a066-2951-11e4-9103-001966469f04

[Syx]

I had this issue for weeks. I finally got it solved for me, but it may help others. Nothing else seemed to mess up except for FFXIV.

I ran MEMTest86 and found that my Ram was bad. It was GSkillz 2X4GB 2133Mhz. I turned my Ram down to 1600Mhz with stock timings 9-9-9-21 2T - It passed MemTest at those settings but it would still crash FFXIV.

Swapped out to my trusty Samsung Green 1.3v Ram and everything is running great.

Really glad to hear that one of my suggestions helped you pinpoint the problem. For those of you still experiencing these issues, please follow my previous post.

There's corruption somewhere. Somewhere, either in RAM, VRAM, or on your disk drive, data is being incorrectly read/stored. That the error is recurring leads me to believe you have a hardware issue, not software. I recommend S.M.A.R.T tests on your drive (http://hddscan.com/), pre-boot memtests (http://memtest.org/), and maybe some VRAM tests (http://mikelab.kiev.ua/index_en.php?...ROGRAMS/vmt_en).

If you see c0000005 (0xc0000005) as the error code when FFXIV crashes that is a completely generic MEMORY_ACCESS_VIOLATION error. The cause is difficult to pinpoint, but the first step would be to rule out any possible hardware problems. Memtest x86 needs about 1.5 to 2 hours to complete. Seriously, suck it up and perform the tests. I cannot stress enough that making a post here saying "still got a problem" without performing any troubleshooting will result in being COMPLETELY ignored by anyone that could possibly assist you. Set aside half a day and run all the tests above. Rule out a hardware problem to narrow the scope of our search-and-destroy effort of this obnoxious error.

[Squa11_Leonhart]

Access violations are not just hardware in origin, infact if it was the hardware you would likely hit a kernel exception and BSOD.

software violations usually occur as a result of foreign code being injected into the process and then not having memory managed properly.

[Syx]

This is true, but the kernel does not access all of the RAM all of the time. There could be addresses in RAM allocated towards programs that would not get touched by sensitive operating system processes. If there is a phsyical defect in the user mode RAM, it wouldn't reflect as a BSOD to the kernel, since the address is outside of its protected allocations and in the USER MODE physical address range. You can use http://www.winsiderss.com/tools/meminfo/meminfo.htm to see how the RAM is physically divided by Windows on your system. You can then go to the Device Manager, go to view, and Resources by Connection and view what hardware is occupying what physical address ranges. RAM usage is much more complex than what you suggest, which is why I suggest testing your hardware first. It's easier to do than debugging software, especially for users who aren't computer savvy. The only way a BSOD would occur from hardware problem in RAM in User Mode is if it was calling a driver that was buggy, like a graphics driver. WDDM lets part of the graphics driver processes exist in User Mode, but if the problem was part of the graphics drivers, you would likely see errors in other games.

After you rule out your hardware, start auditing your programs. Go through your Programs and Features and remove any unused and/or unknown programs.

[Chaotika]

Faulting application name: ffxiv.exe, version: 1.0.0.0, time stamp: 0x53f4e8b7
Faulting module name: ffxiv.exe, version: 1.0.0.0, time stamp: 0x53f4e8b7
Exception code: 0xc0000005

I have the same issue after the last ffxiv update. 21Aug2014

Fault offset: 0x00adfb79
Faulting process id: 0xe5c
Faulting application start time: 0x01cfbd98d251fd14
Faulting application path: C:\Program Files (x86)\SquareEnix\FINAL FANTASY XIV - A Realm Reborn\game\ffxiv.exe
Faulting module path: C:\Program Files (x86)\SquareEnix\FINAL FANTASY XIV - A Realm Reborn\game\ffxiv.exe
Report Id: b6855b64-298c-11e4-bb07-902b345ca9ea

Hope this helps

[Squa11_Leonhart]

This is true, but the kernel does not access all of the RAM all of the time. There could be addresses in RAM allocated towards programs that would not get touched by sensitive operating system processes. If there is a phsyical defect in the user mode RAM, it wouldn't reflect as a BSOD to the kernel, since the address is outside of its protected allocations and in the USER MODE physical address range. You can use http://www.winsiderss.com/tools/meminfo/meminfo.htm to see how the RAM is physically divided by Windows on your system. You can then go to the Device Manager, go to view, and Resources by Connection and view what hardware is occupying what physical address ranges. RAM usage is much more complex than what you suggest, which is why I suggest testing your hardware first. It's easier to do than debugging software, especially for users who aren't computer savvy. The only way a BSOD would occur from hardware problem in RAM in User Mode is if it was calling a driver that was buggy, like a graphics driver. WDDM lets part of the graphics driver processes exist in User Mode, but if the problem was part of the graphics drivers, you would likely see errors in other games.

After you rule out your hardware, start auditing your programs. Go through your Programs and Features and remove any unused and/or unknown programs.

applications map memory virtually, but any attempt by the kernel to map virtual memory to physical addresses that are faulty will hit a kernel mode access violation and crash the system.

software access violations are more commonly than a nything a result of applications injecting themselves into the games process in unmanaged/poorly written ways.

[Vhex]

0xc0000005 has always been my error code but last time I ran Memtest86 I left it on for at least 10 passes which was like four hours and it passed.

But could my crashing still be memory problems? should I just replace it? I don't have any spare memory to test it.

Oh and putting my graphics on standard really minimized the crashes... but I would rather not play that way...

[Squa11_Leonhart]

do you have a radeon? if so theres the problem.

the drivers are leaking memory which will generate an access violation when memory can no longer be mapped.