+1
got this crash like 4 times now, appears after i teleport back to lavenders bed (house).
![]()
+1
got this crash like 4 times now, appears after i teleport back to lavenders bed (house).
![]()
Well, it may be a needle in a haystack, but it's definitely not just one :P A lot of people get this kind of error in many different ways. Oh and it doesn't hang in both DX modes. It just throws that error after pressing the Play button on the launcher for the DX11. Only DX9 is capable of actually getting in for a minute or two. At best. I'm an IT and I know where you're coming from, but the reason here is perfectly simple and obvious. Bad patch.
I can say that because everything else works perfectly just as it did. The only thing that doesn't want to work is FFXIV AFTER this patch. Before it worked perfectly and I haven't changed nothing in that time and by that I mean nothing new installed, nothing new downloaded, nothing adjusted. On top of that I thoroughly tested the stability of the PC and checked if there are any errors on the HDD, registry and so on and so forth. Everything being top notch.
I'm just hoping that this issue is being addressed and the next maintenance window will fix this, even though it wasn't listed in the change list for it. Otherwise I'm gonna feel a bit scammed tbh. I mean maintenance window took 1 day, then I can't play for the next 2 days and if the next patch/maintenance wouldn't fix the issue, I'd most likely be looking at more days lost. It may be nothing to most, but I don't have money to spent. Every day counts for me.
Ez fixes are Uninstal reinstal, download driver sweeper clear all old drivers for Nvidia and reinstall them, change to direct x9, reinstall windows or face reset windows, use the changes I listed above with vsync and bilinear and changing the direct x from the options menu, run in lowest setting in windowed mode, other options I heared that work is running something like diablo in the background then running ff14, it tricks the graphics card
had the same issue last night
Eorzean Alliance Embassy: FB Group
https://www.facebook.com/groups/FFXIVEmbassy/
Had this happen to me twice so far today. Both times when i exited a completed duty. Its not a driver issue, since nothing was flagged up on the reliability monitors.
updating on the dx11 error list
This is from when i was farming a1s:
and this is form df expert
Quick edit: Noticed, after just skimming over the other post, the DX11 seems to be area located, for exemple, Norit was in lavender bed and i was in lavender bed when i was farming A1S, so it's the same error code.
Could be some effect that are messed with the dx11 version of the client with the 3.5 update.
Last edited by Hacchan; 01-19-2017 at 06:05 PM.
I'm having the exact same problem. Only happens when I zone into the Mist. Today it's only when I teleport but last night was also doing it after exiting a duty and zoning back into the mist. I can teleport everywhere just fine.
So far I've only gotten it while entering Mist where our FC house is located, it has happened when I've exited our house and when I've teleported into the zone using the free company estate teleport.
No issues so far using the private estate teleport to lavender beds or apartment teleport to Goblet.
I just had this happen to me twice as well. Teleporting my FC house in the Lavender Beds. Unfortunately, now it appears I can't log in so I must be stuck teleporting?
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.