Ff14 Crashing Windows 10
![Windows Windows](https://appuals.com/wp-content/uploads/2017/12/2017-12-28_152815.jpg)
Trying to play ffxi, and i get an error after clicking play.its the play in the menue before you get warnings about not neglecting family/friends.after i click play, it'll load up ffxi. But will immedietely close the ffxi window and go back to playonline with this mssg:'Terminated as error occurred in FINAL FANTASY XI. Failed to initialize Direct3D. Please check that this computer has the required specifications to run FINAL FANTASY XI.(-1)'i'm not sure what to do;;, i checked my direct3d, and online says that mine is up to date and working fine.any suggestions welcomed or anyone have similar problem and found solution? Ffxi uses directx 8.1, each numbered directx version is seperate: having directx 11 doesn't mean you have directx 8.1try installing that, and see if it fixes the problem(seeing as ffxi is primarily software rendered and only uses.present on xp, OS and hardware are generally pretty irrelevant.)While it is mostly software on the UI, there are 3D elements (But they're rendered outside in it's own before before being applied to the screen along with the overlay, thus why hardware settings like AA tends not to affect a lot of the components, though FXAA will work regardless). But as a result, some erroneous settings that won't even apply can cause the game to crash if he's forcing it.
![Ff14 Crashing Windows 10 Ff14 Crashing Windows 10](https://user-images.githubusercontent.com/3034651/51284219-6f138700-19b0-11e9-85a9-fe6e6fd96f2e.png)
Quality wise I've always found the best result is just super-sampling the resolution in the registry.But I'm with what is said so far, go and grab directX 8.x, may simply be missing the runtimes, or they may need a reinstall (or the DLLs may need to be re-registered if they were moved or the system is a new one). While it is mostly software on the UI, there are 3D elements (But they're rendered outside in it's own before before being applied to the screen along with the overlay, thus why hardware settings like AA tends not to affect a lot of the components, though FXAA will work regardless). But as a result, some erroneous settings that won't even apply can cause the game to crash if he's forcing it. Quality wise I've always found the best result is just super-sampling the resolution in the registry.But I'm with what is said so far, go and grab directX 8.x, may simply be missing the runtimes, or they may need a reinstall (or the DLLs may need to be re-registered if they were moved or the system is a new one).that's all lovely (commonplace) information, but knowing his OS or hardware has no relation to whether he's forcing AA, etc. You were rude about information that's completely irrelevant to his problem. Suggestion/Possible fix for your situationThe error mostly like has nothing to do Directx, as you can get this error if you don't have resolution set in the FFXI config.
If the setting have been clear out recently it will show up blank in ffxi config. Running thought it again will reapply the setting back to where they need to be in reg which allow the game to open past the play.Hrm this does make sense, I recall one time when the game updated and had an additional option in the FFXI config, but because I did not go into the config yet to update it's values, the game kept crashing until I realized that. This is quite a common problem, several things you can try, read solutions here:OS can be relevant to the problem because driver is the interface between the OS and your hardware, and directx is basically a layer of librarys built on top (they are, theoretically, backwards compatible, so if you have a later direct x library installed it should technically stuff work, but meh.), hardware. Not so much in this case. And I can't help but agree about the rudeness, you could've just simply asked for those stuff, not everyone is expert at bug reporting. (if he is, chances are he would've googled around first and found his answer).
Ff14 Crashing Windows 10 1
Sorry for necro, but I'm having this problem now. I tried to launch vanilla ff to finish addon missions, no go, same direct 3D quote. I decided I'd just wait on missions and tried to log in using windower again, and now windower launch crashes as the same point (right after hitting play). Windower worked literally an hour before, so I don't know what's up/how to fix it.Operating System - Windows 8.1 with Bing 64-bitCPU - Intel Celeron N2840 @ 2.16GHz 41 째CBay Trail-M 22nm TechnologyRAM - 4.00GB DDR3 @ 666MHz (9-9-9-24)Motherboard - Acer Aspire ES1-512 (CPU 1) 44 째CGraphics - Generic PnP Monitor (1366x768@60Hz)Intel HD Graphics (Acer Incorporated ALI)Storage - 465GB Western Digital WDC WD5000LPVX-22V0TT0 (SATA) 37 째CIt's a shitty $300 laptop, but it ran it fine until now.Help! Trying to play ffxi, and i get an error after clicking play.its the play in the menue before you get warnings about not neglecting family/friends.after i click play, it'll load up ffxi.
But will immedietely close the ffxi window and go back to playonline with this mssg:'Terminated as error occurred in FINAL FANTASY XI. Failed to initialize Direct3D. Please check that this computer has the required specifications to run FINAL FANTASY XI.(-1)'i'm not sure what to do;;, i checked my direct3d, and online says that mine is up to date and working fine.any suggestions welcomed or anyone have similar problem and found solution?
. Filters. Community. Useful Information.
Ff14 Keeps Crashing
Live Content.Current Patch: PSA:5 days Live Letter @ E3 Maintenance.Topics.Notices.Dev Blog.Latest Community Threads.Weekly Threads.Subreddit Legend: Posting Rules: Please read our before posting. Be civil. Every other technical post I've made has been downvoted to oblivion and never seen the light of day, but here's hoping that someone sees this that actually needs it.So here goes nothing.It seems like the DX11 client is very sensitive to programs that run an overlay on your display. There are some exceptions to the rule. Steam overlay doesn't seem to be causing any issues, but it would probably be wise to disable it. However, programs like EVGA Precision, Display Fusion, and Google Hangouts desktop app seem to cause frequent crashes.
(Edit: some users aren't having any issues with Display Fusion.)It probably wouldn't hurt to also disable any windows aero effects as well.At first I thought either SE screwed something up in the DX11 client or Nvidia had something jacked up in their driver, but after disabling all of the overlay programs on my system I haven't had any blackscreen crashes.Averaging about 54-65 fps depending by area with GTX 980 Win8.1 on custom near max settings.is a nice little guide if you want to eek out a bit more fps.' Use low-detail models on distant objects. (LOD)' in graphics settings seemed to make the game a lot more stable as well. However, It will drastically reduce the eye-candy of objects not in your immediate area. Makes flying look a lot less pretty.Edit: Words & formatting.Edit2: Post your GPU, and OS if you're experiencing the black screen crash. Seems like it might be an issue with the client and Win8.
Update: People appear to be having it on Win7 as well. Just less frequently it seems.Edit3: Linked a thread that helped with stability and got an extra 10fpsEdit4: had another possible fix.YMMV but I was having 2 issues and I've been messing around with them for days to try and fix them.While playing: 'Display driver stopped responding and has recovered' - Error present with 353.30 and 353.06, so after much trial and error I rolled back to 350.12 and changed the physx setting setting physx to GPU instead of auto which seems to have fixed it. Uninstalled with DDU and clean install each time.On exit: 'Final Fantasy XIV: A Realm Reborn has encountered an error and needs to close.' - resolved this with uninstalling the nvidia HD audio drivers, and setting ffxivboot.exe to 'run as administrator' and win7 compatibility.Edit5: There is a thread on the official forums about this as well. Not really any new information on it.No dev response yet either =(UPDATE 7/30: After updating to Win10, with the Win10 Geforce driver (353.30 WHQL ) I have had 0 stability issues. Ran the DX11 client on full blast for 9 hrs. Not a single issue.
(Update: 1 week later, still no crashes.). Problem isn't only Nvidia. I currently can't use dx11 client at all 'cause it keeps crashing periodically with my R9 285. Older AMD cards seem not to have this problem so this is gonna be a problem to everybody buying the new AMD R9 300 series.Of those programs, I have only had Steam up and running while playing the game. Haven't tried closing Steam though.Edit: Tried just now with dx11 again with Steam turned off, and it crashed after about 15 minutes of gameplay.
![Download Download](https://i3.photobucket.com/albums/y64/McVinster/reshade%20error_zpsok1adkrh.png)
They have definately screwed something up with the dx11 client from SE's end. Download mod gta vice city.