It's so odd - why are the forums for such a big game abandoned?Quote:
Originally Posted by HuaTuo
Black screen after launching the game
Printable View
-
10-11-2022, 05:52 PMCaffeinePanda
-
10-12-2022, 08:23 PMCaffeinePanda
Daily post - still not working & still not acknowledged
-
10-13-2022, 12:57 AMyate
Same issue here. It also works if you remove/rename steamclient64.dll from your Steam folder before launching the game.
Here's a dump of the process when it's hanging, not that it's super helpful. Seems like there's some issue with the way this game is using the steam API
Code:*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for steamclient64.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for steam_api64.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ffxiv_dx11.exe -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for nvwgf2umx.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for nvcuda64.dll -
GetUrlPageData2 (WinHttp) failed: 12007.
DUMP_CLASS: 2
DUMP_QUALIFIER: 400
FAULTING_IP:
+0
00000000`00000000 ?? ???
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 0000000000000000
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000000
NumberParameters: 0
FAULTING_THREAD: 00003b08
DEFAULT_BUCKET_ID: STATUS_BREAKPOINT
PROCESS_NAME: ffxiv_dx11.exe
ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached.
EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid
EXCEPTION_CODE_STR: 80000003
WATSON_BKT_PROCSTAMP: 63178c27
WATSON_BKT_PROCVER: 1.0.0.0
PROCESS_VER_PRODUCT: FINAL FANTASY XIV
WATSON_BKT_MODULE: unknown
WATSON_BKT_MODVER: 0.0.0.0
WATSON_BKT_MODOFFSET: 0
WATSON_BKT_MODSTAMP: bbbbbbb4
BUILD_VERSION_STRING: 10.0.19041.1889 (WinBuild.160101.0800)
MODLIST_WITH_TSCHKSUM_HASH: b0d60123200cf4e76ec3dd1569c915c388da025b
MODLIST_SHA1_HASH: 95f5d70f4f62623e6a543bf52be81a8c28c8dcc0
NTGLOBALFLAG: 0
APPLICATION_VERIFIER_FLAGS: 0
PRODUCT_TYPE: 1
SUITE_MASK: 272
DUMP_FLAGS: 8000c07
DUMP_TYPE: 0
ANALYSIS_SESSION_HOST:
ANALYSIS_SESSION_TIME: 10-01-2022 18:49:11.0738
ANALYSIS_VERSION: 10.0.14321.1024 amd64fre
THREAD_ATTRIBUTES:
OS_LOCALE: ENU
PROBLEM_CLASSES:
Tid [0x0]
Frame [0x00]
String [STATUS_BREAKPOINT]
Data Bucketing
BUGCHECK_STR: STATUS_BREAKPOINT
LAST_CONTROL_TRANSFER: from 00007ff830a5af23 to 00007ff83332d244
STACK_TEXT:
00000058`5a18edd8 00007ff8`30a5af23 : 00000002`00000001 00000001`00000002 00000000`00000000 00007ff8`30a93a7b : ntdll!NtReadFile+0x14
00000058`5a18ede0 00007fff`b8f1f0c0 : 00000001`0001b000 00000000`00000000 00000001`00000001 00000058`5a18f2b0 : KERNELBASE!ReadFile+0x73
00000058`5a18ee60 00007fff`b8f1c181 : 00000000`00000000 00000000`0002bf00 000001de`00000000 000001de`6d100440 : steamclient64!Steam_TerminateGameConnection+0x384f20
00000058`5a18f2b0 00007fff`b8f1c4c0 : 000001de`6d190144 000001de`6d100440 00000058`5a18f480 00000000`00000000 : steamclient64!Steam_TerminateGameConnection+0x381fe1
00000058`5a18f2f0 00007fff`b8f00b41 : 00000000`00000001 00000000`00000001 000001de`6d190000 00000000`00000040 : steamclient64!Steam_TerminateGameConnection+0x382320
00000058`5a18f450 00007fff`b8dd90b4 : 000001de`6d0912c0 00000000`00000000 00000058`5a18f7a0 00007fff`b97fcf48 : steamclient64!Steam_TerminateGameConnection+0x3669a1
00000058`5a18f770 00007fff`b8d909dc : 00000000`00000001 00000000`0af949a4 000001de`00000000 00000000`0000000b : steamclient64!Steam_TerminateGameConnection+0x23ef14
00000058`5a18f800 00007ff8`013f719a : ffffffff`00000000 00000000`00000000 000001de`67521780 00000000`00000001 : steamclient64!Steam_TerminateGameConnection+0x1f683c
00000058`5a18f880 00007ff8`013f8170 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : steam_api64!SteamAPI_SetTryCatchCallbacks+0x222a
00000058`5a18f8b0 00007ff6`2620d828 : 000001de`6ae4cc00 00000000`00000000 00000000`00000005 000001de`7516b1f0 : steam_api64!SteamAPI_RunCallbacks+0x70
00000058`5a18f8e0 00007ff6`25c92908 : 000001de`6757df90 00000000`00000000 00000000`00000000 000001de`67521780 : ffxiv_dx11+0x60d828
00000058`5a18f910 00007ff6`25c562b5 : 00000007`3f86c8e2 00000000`00000006 00000000`00000001 00000000`00000000 : ffxiv_dx11+0x92908
00000058`5a18f940 00007ff6`25c59907 : 00000058`5a18fab0 00000000`00000000 00000000`00000000 00000000`00000000 : ffxiv_dx11+0x562b5
00000058`5a18f9b0 00007ff6`2715720f : 00000000`0000000a 00000000`00000000 00000000`00000000 00000000`00000000 : ffxiv_dx11+0x59907
00000058`5a18fee0 00007ff8`32e27034 : 00000000`00000000 00000000`00000000 00000000`00000000 00007ff8`00770000 : ffxiv_dx11+0x155720f
00000058`5a18ff20 00007ff8`332e26a1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14
00000058`5a18ff50 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21
STACK_COMMAND: ~0s; .ecxr ; kb
THREAD_SHA1_HASH_MOD_FUNC: 381c0ac413399062e171a3713d2c20f1741b0dff
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 3a07856cd4950014a52192315fd8f790150af6de
THREAD_SHA1_HASH_MOD: b7c652e4258c3e4bce98b15e467582dae73ae68f
FOLLOWUP_IP:
steamclient64!Steam_TerminateGameConnection+384f20
00007fff`b8f1f0c0 85c0 test eax,eax
FAULT_INSTR_CODE: 7674c085
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: steamclient64!Steam_TerminateGameConnection+384f20
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: steamclient64
IMAGE_NAME: steamclient64.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 63339b1a
BUCKET_ID: STATUS_BREAKPOINT_steamclient64!Steam_TerminateGameConnection+384f20
PRIMARY_PROBLEM_CLASS: STATUS_BREAKPOINT_steamclient64!Steam_TerminateGameConnection+384f20
FAILURE_EXCEPTION_CODE: 80000003
FAILURE_IMAGE_NAME: steamclient64.dll
BUCKET_ID_IMAGE_STR: steamclient64.dll
FAILURE_MODULE_NAME: steamclient64
BUCKET_ID_MODULE_STR: steamclient64
FAILURE_FUNCTION_NAME: Steam_TerminateGameConnection
BUCKET_ID_FUNCTION_STR: Steam_TerminateGameConnection
BUCKET_ID_OFFSET: 384f20
BUCKET_ID_MODTIMEDATESTAMP: 63339b1a
BUCKET_ID_MODCHECKSUM: 151ef85
BUCKET_ID_MODVER_STR: 7.53.93.61
BUCKET_ID_PREFIX_STR: STATUS_BREAKPOINT_
FAILURE_PROBLEM_CLASS: STATUS_BREAKPOINT
FAILURE_SYMBOL_NAME: steamclient64.dll!Steam_TerminateGameConnection
FAILURE_BUCKET_ID: STATUS_BREAKPOINT_80000003_steamclient64.dll!Steam_TerminateGameConnection
WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne/ffxiv_dx11.exe/1.0.0.0/63178c27/unknown/0.0.0.0/bbbbbbb4/80000003/00000000.htm?Retriage=1
TARGET_TIME: 2022-10-01T22:48:20.000Z
OSBUILD: 19044
OSSERVICEPACK: 1889
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt SingleUserTS
USER_LCID: 0
OSBUILD_TIMESTAMP: 2011-03-01 17:27:29
BUILDDATESTAMP_STR: 160101.0800
BUILDLAB_STR: WinBuild
BUILDOSVER_STR: 10.0.19041.1889
ANALYSIS_SESSION_ELAPSED_TIME: 19db
ANALYSIS_SOURCE: UM
FAILURE_ID_HASH_STRING: um:status_breakpoint_80000003_steamclient64.dll!steam_terminategameconnection
FAILURE_ID_HASH: {f19f7334-0e4c-ee40-78e6-09f7dba5b83e}
Followup: MachineOwner
-
10-13-2022, 09:08 AMDeadlyStingerrly thx now i can play ffxiv with steam open XDQuote:
Originally Posted by yate
-
10-13-2022, 11:42 AMHuaTuo
gonna try this rn. That would mean a permanent fix without having to close steam each time?
EDIT: Works. Tried multiple times while having Steam on. Not sure if or how this fix affects any other instalations of games, but this appears to be a PERMANENT fix.
3 months later, a member of a gaming community comes up with a solution that SE and STEAM could not. Just wow..
I have updated OP headline based on this - thank you for this @Yate -
10-13-2022, 02:39 PMyateIt's not permanent solution unfortunately, Steam will redownload the dll the next time its opened, and who knows the consequences of removing it, but at least it's a different way of launching the game besides force closing Steam.Quote:
Originally Posted by HuaTuo
-
10-13-2022, 02:43 PMCaffeinePandaHelpful! Thank you so much. This works.Quote:
Originally Posted by yate
My FFXIV client via Steam still freezes (and requires task manager to close) upon ending my game session, any ideas on that e.g. can I rename another file? -
10-14-2022, 05:26 AMyate
I did some more experimenting, no need to rename/remove steamclient64.dll in the Steam Folder.
Instead, I renamedinsideCode:steam_api64.dll
toCode:<Steam Folder>\steamapps\common\FINAL FANTASY XIV Online\boot
That seems to consistently work for me, and it persists through Steam restarting. I'm assuming it will work until FFXIV pushes an update for that file. Again, not sure what the consequences are, but it allows me to play the game without quitting Steam.Code:steam_api64-bak.dll
-
10-14-2022, 01:23 PMCaffeinePandaInteresting - within Final Fantasy XIV Online I don't have a boot to steam file, but I do have a 'boot' folder, and within that, similarly named files, but none that match exactly what you shared above. I'll make a backup and mess around renaming and see.... thanks a lot for sharing.Quote:
Originally Posted by yate
-
10-14-2022, 01:41 PMyateI edited my post to make it more clear which file I changed.Quote:
Originally Posted by CaffeinePanda
-
10-14-2022, 03:30 PMCaffeinePandaPerfect! Thank you - perhaps it was clear already and I misunderstood. The new solution is far better, as some other games failed to work with the file being renamed (those that required to connect online).Quote:
Originally Posted by yate
It seems to launch fine, but /sometimes/ will require task manager to close. Our best band aid fix so far... -
10-15-2022, 12:10 AMChudah
Thank you for this! I've been quietly following this thread for 3 months hoping that Square=Enix might finally acknowledge the issue. As always, it comes down to the community to find fixes and work-arounds.
-
10-15-2022, 07:50 AMSodipopsReported
I keep going back to tech support chat and on the last one today I requested that someone come look at this thread. I do hope that it goes to someone and that this is revisited so you don't have to keep up the good fight and bumping it every day.
-
10-15-2022, 01:31 PMAlienTech
Found another temp fix
That seems to consistently work for me, and it persists through Steam restarting. I'm assuming it will work until FFXIV pushes an update for that file. Again, not sure what the consequences are, but it allows me to play the game without quitting Steam.Code:I did some more experimenting, no need to rename/remove steamclient64.dll in the Steam Folder.
Instead, I renamed "steam_api64.dll" inside <Steam Folder>\steamapps\common\FINAL FANTASY XIV Online\boot to "steam_api64-bak.dll"
https://steamcommunity.com/app/39210...2110406105307/
https://forum.square-enix.com/ffxiv/...he-game/page17
100% works -
10-15-2022, 07:40 PMCaffeinePandaWhat's the other temp fix? It looks like you quoted Yate and removed the name. That Steam thread you linked, links back to Yate in this thread :)Quote:
Originally Posted by AlienTech
-
10-15-2022, 10:47 PMAlienTechrenamed "steam_api64.dll" inside <Steam Folder>\steamapps\common\FINAL FANTASY XIV Online\boot to "steam_api64-bak.dll"Quote:
Originally Posted by CaffeinePanda
-
10-16-2022, 05:30 PMCaffeinePandaYa, but that's what the guy in this thread said lol, I'm saying the Steam link you gave, was linking to this thread, all g, nvm.Quote:
Originally Posted by AlienTech
-
10-16-2022, 11:13 PMSodipops
Possible fix on my end.
I have been tinkering and reinstalling the game a bit now and something worked. I haven't tested it out to see if it will do this 100% of the time but this is the first time in over a week that I am in the game and actually able to do things.
Simple fix was to download in a different driver. The game was originally in my e: drive and now I have changed it to my D: drive. It seems that something (regardless of changes ) was still corrupted and retrying on a new drive fixed it. I know it may not be possible for every one but this was my solution. -
10-18-2022, 11:03 AMCaffeinePanda
Daily post - still not fixed
-
10-18-2022, 11:01 PMCaffeinePanda
6.25 - no acknowledgement, no fix.
But thank Eorzea that a fix was rolled out for "An issue when using the glamour dresser wherein the icon for gear placed in the dresser did not display correctly under certain conditions."
See here => https://eu.finalfantasyxiv.com/lodes...337ea9b2c12277
It's not in resolved issues, nor the known issues. -
10-19-2022, 12:08 PMyate
It also seems to be a problem with the launcher specifically, or the way the game handles being launched by it. I'm not sure how much more I can say about that.
-
10-20-2022, 01:58 PMCaffeinePanda
Daily post - still not acknowledged or resolved
-
10-20-2022, 03:05 PMZeroRaziel
Same here. Have been having this problem right after 6.2, not resolved yet.
-
10-21-2022, 02:20 PMCaffeinePanda
Daily post - still not acknowledged or resolved
-
10-23-2022, 02:17 PMCaffeinePanda
Daily post - still not acknowledged or resolved
-
10-24-2022, 12:02 PMyate
Here's another bizarre technique that works for me (maybe 90% of the time). When you click the Play button on the launcher, immediately open the start menu (either with your mouse or the windows button). Keep the start menu open. The game will load in an off centered window, wait until you see the ESRB rating and click the game window to load in full screen normally.
-
10-25-2022, 02:14 PMCaffeinePandaInteresting! Will try soon. I don't turn my PC off (not for FFXIV, just coincidence), so the file renaming appears permanent (even throughout recent 6.25 patch).Quote:
Originally Posted by yate
-
10-26-2022, 05:51 PMCaffeinePanda
Daily post - still not acknowledged or resolved
-
10-26-2022, 07:37 PMChrispyBacon
Same issue, only started happening after the latest patch.
This issue makes the game completely unplayable and certainly won't be renewing my monthly sub until it's fixed. -
10-27-2022, 12:16 PMCaffeinePanda
Daily post - still not acknowledged or resolved
-
10-27-2022, 11:39 PMCaffeinePanda
Daily post - still not acknowledged or resolved
-
10-28-2022, 07:54 AMChrispyBaconIt's actually quite sad that they haven't replied to this thread to at least acknowledging that there's an issue.Quote:
Originally Posted by CaffeinePanda
-
10-28-2022, 10:17 AMCaffeinePandaI was sad, but it's almost a meme now, I wonder if I can hit 1000 posts.Quote:
Originally Posted by ChrispyBacon
I am hoping for a big apology, and ~6 months game time offered to everyone involved, given that many (thousands at least) have lost 2 months of gameplay at this point, on top of the effort/frustration. Hell, soon, SE needs to make us a custom apology mount >:) -
10-28-2022, 01:03 PMon9desu
I don't know what they're doing there at SE. I check this post every time before I try logging into the game hoping they would do something about it already. Just wanted to say I really appreciate the the daily update CaffeinePanda.
-
10-28-2022, 07:57 PMCaffeinePandaNo problem! I just hope they don't delete the thread & bury the issue. I've copied it all into word, though :)Quote:
Originally Posted by on9desu
-
10-29-2022, 10:28 AMCaffeinePanda
Daily post - still not acknowledged or resolved
-
10-30-2022, 10:59 AMCaffeinePanda
Daily post - still not acknowledged or resolved
-
10-31-2022, 10:21 AMCaffeinePanda
Daily post - still not acknowledged or resolved
-
11-01-2022, 02:45 AMFieryone
Sure is great that I can't even boot into the game now with this Steam API Bug, I'd REALLY love for it to be fixed.
-
11-01-2022, 01:17 PMCaffeinePanda
Hm, patch notes for 6.28, no specific mention of this issue, unless we fall under 'various other issues'...