Crash when AutoRetainer switches characters (Multi mode) after 7.4 / Dalamud API14

[reygoldk24]

Summary

After FFXIV 7.4 and the migration to Dalamud API14 / .NET 10, AutoRetainer frequently causes the game to crash during automatic character switching in Multi mode.

The crash seems to occur at the moment AutoRetainer automatically logs into a character, especially when the FFXIV window is not in the foreground (background / alt-tabbed).

---

Environment

• Dalamud version: 14.0.0.2
• Runtime: .NET 10
• AutoRetainer: 4.5.5.4
• OS: Windows 11 (25H2)
• CPU: AMD Ryzen5 5600X
• GPU: NVIDIA RTX4060Ti 8GB

---

What happens

• AutoRetainer is running in Multi mode
• Characters are switched automatically
• At the moment of logging into a character, the game crashes with an access violation (C0000005)
• This happens very frequently (often within an hour)
• Crashes are much more likely when FFXIV is not the active / foreground window

---

What does NOT trigger it

• Manual play without AutoRetainer
• Single-character usage
• Being logged in and idle (no character switch)

---

Observations

• The crash happens exactly at character login, not during gameplay
• It feels like something is accessed before the client/UI is fully ready
• Other plugins are mostly stable; the issue appears strongly correlated with AutoRetainer’s character switching
• Given that this started after the API14 / .NET 10 migration, it may be related to timing or missing guards during character switching

---

Crash log excerpt

Unhandled native exception occurred at ffxiv_dx11.exe+108AE55
Code: C0000005 (Access Violation)

Occurs during automatic character login
(Full crash log can be provided if needed)

---

Please excuse any awkward or unnatural wording, as this report was written using translation assistance.
Thank you for maintaining AutoRetainer.

[throwawayusername-2024]

It happens outside of multi mode too. I've been getting this when using Artisan with AutoRetainer integration.

Here are some additional details. This crashes on 4.5.5.5.

Exception Info #0
Address: C0000005
Flags: 0
Address: 7FF61CD389C0
Parameters: 0, 4D01F5D8
Call Stack
{
  [0]	ffxiv_dx11.exe+6189C0	(Component::GUI::AtkValue.GetUInt)
  [1]	ffxiv_dx11.exe+6189C0	(Component::GUI::AtkValue.GetUInt)
  [2]	ffxiv_dx11.exe+1289811	(Client::UI::AddonSynthesis.OnRefresh+0x61)
  [3]	7FFA0F46B42D
}

Registers
{
  RAX:	2470EE841F0 [ffxiv_dx11.exe+20C7030	(vtbl_Client::UI::Misc::RaptureTextModule)]
  RBX:	248188F06A0 [246D457EE70]
  RCX:	4D01F5D8
  RDX:	1A
  R8:	4D01F5D8
  R9:	2466F656570 [7FFA0B4BC6D0]
  R10:	7FFA0F46B42D [3F3D83010447C641]
  R11:	2468834CB60
  R12:	9
  R13:	2263300ECE8 [7FFA0B5963A8]
  R14:	FFEC3B352F61
  R15:	4D01F5D8
  RSI:	1A
  RDI:	4D01F5D8
  RBP:	248188F06A0 [246D457EE70]
  RSP:	E5B934DA88 [ffxiv_dx11.exe+1289811	(Client::UI::AddonSynthesis.OnRefresh+0x61)]
  RIP:	ffxiv_dx11.exe+6189C0	(Component::GUI::AtkValue.GetUInt)
}

Stack
{
  [RSP+0]	ffxiv_dx11.exe+1289811	(Client::UI::AddonSynthesis.OnRefresh+0x61)
  [RSP+8]	18
  [RSP+10]	0
  [RSP+18]	18
  [RSP+20]	0
  [RSP+28]	2262FA83440 [2480F15D850]
  [RSP+30]	28
  [RSP+38]	0
  [RSP+40]	10000
  [RSP+48]	0
  [RSP+50]	2470EE841F0 [ffxiv_dx11.exe+20C7030	(vtbl_Client::UI::Misc::RaptureTextModule)]
  [RSP+58]	24679B10000 [8B488045894810FF]
  [RSP+60]	ntdll.dll+1CCA4	(RtlAllocateHeap+0xAD4)
  [RSP+68]	0
  [RSP+70]	0
  [RSP+78]	0
}

[Limiana]

Hello!
Please use this instruction to confirm that this issue indeed originates from AutoRetainer:

= How to confirm if a certain plugin is causing crashes or misbehavior

1. Make sure you are on the "release" branch:
   • Type /xlbranch in chat.
   • If it shows anything other than "release", select "release", press "Pick", then restart the game. (Do not use "Pick & Restart.")
   • If "release" isn’t available yet, check back in a few hours or the next day.
2. Completely close the game.
3. Open XIVLauncher. If autologin is enabled, hold Shift while opening it to temporarily disable autologin.
4. Right-click the "Log In" button in XIVLauncher, then select "Start w/o any plugins."
5. Log into your character as usual.
6. Confirm that safe mode is active:
   • Type /xlplugins in chat.
   • Look for the message: "You enabled safe mode, no plugins will be loaded."
7. Type /xldev in chat. A debug menu will appear on top of your screen.
8. Open "Plugins", then select "Disable safe mode."
9. Enable the plugin you suspect is causing issues.
10. Try to reproduce the crash or issue.

• If it happens with only this plugin enabled, collect your logs and report it to the plugin developer.
• If not, disable the plugin, then test the next one you suspect. Repeat until you find the cause.

11. (Optional/Advanced) If you suspect a combination of plugins, you can enable them together and test. Keep in mind this makes it harder for developers to diagnose.

Note: because Lifestream is required for AutoRetainer usage, enable both Lifestream and AutoRetainer.

After crashing with just Lifestream and AutoRetainer enabled, please send logs according to the following instruction:

= How to properly send logs after error or crash?

Please do not copy logs from Dalamud's xllog window or plugin's log window. If you have encountered any problem, please do this:

1. Please make sure that the log level is set to "Debug" in /xllog top left corner.
2. Recreate the problem. As soon as you have encountered the problem, without doing anything further and without restarting your game, send these files:
   %appdata%\XIVLauncher\dalamud.log
%appdata%\XIVLauncher\dalamud.boot.log
   If you are encountering crashes, please additionally go to %appdata%\XIVLauncher\ folder and search for recently created text files starting with "dalamud_appcrash_" and send them as well.
   Additionally, Windows Event Viewer can also have crash logs. To access them, open start menu or press Windows+R key combo, then type eventvwr, go to "Windows Logs" - "Application" section, and find recent "Error" events related to "ffxiv_dx11.exe" application.
   Please make sure that you do not have more than one instance of the game running before sending logs.

In case if files are too big for Discord upload, please use https://transfer.it/ to upload them.

[cloud3d1214]

did anybody figure out why this is happening? It always seems to happen when I have 2 accounts open both using multi and seems to happen the most when its trying to change characters (as I own many submarines) and never during gameplay.

[reygoldk24]

I sincerely apologize for the significant delay in confirmation.
I saw a post on the Puni.sh Discord server stating that "installing any of NoTypeSay, JobBars, or MapPartyAssist causes crashes."
I was using NoTypeSay, and since I removed it, I have not experienced any login crashes.
I apologize for submitting this as an issue without properly isolating the cause.