Hi, I'm writing in hope of solving the random crashes during gameplay that have been plaguing me since I came back to the game in late 7.1. It seems to happen mainly in Dawntrail areas and instances, but I've had it happen in Kugane and Thavnair too. I included few of the errors codes that's I've gotten since 7.2. By "Not moving", I mean i had not touched the game for at least 2 minutes while doing something on my phone, so I don't see it being input from me causing it.
https://i.imgur.com/I1aGL36.png
I never had this issue during all of Endwalker 6.0 through 6.5. I didn't play during 7.0, but both 7.1 and 7.2 have had this happening
Things I have tried:
- Closing all overlays/overlay programs
- Lowering every graphic setting
- Nvidia DLSS and AMD FSR at low and high values
- Removing the overclock that apparently came prebuilt into this laptop
- Underclocking 30MHz
- Borderless window and windowed (full screen gives me input delay)
- Monitor refresh rate of 60 and 240
- Closing all other programs (usually just have firefox and discord open anyway)
- Fresh install of the game
- Fresh install of my graphics driver
- Unplugging my second monitor
Any advice is welcome. I've found this type of error is commonly associated with not being able to even load into the game, but all of mine are completely random during gameplay.
-=-=-=-=-=-=- FFXIV Information -=-=-=-=-=-=-
MyDocument C:\Users\gary1\OneDrive\Documents
FINAL FANTASY XIV ONLINE C:\Program Files (x86)\SquareEnix
FINAL FANTASY XIV - A Realm Reborn Language 1 Region 2
ProxyEnable 0
ProxyServer unspecified
ProxyOverride unspecified
-=-=-=-=-=-=- System Information -=-=-=-=-=-=-
SYSTEM_OS Windows 11 Pro 64-bit (6.2, Build 9200) (22621.ni_release.220506-1250)
SYSTEM_CPU 13th Gen Intel(R) Core(TM) i9-13980HX (32 CPUs), ~2.2GHz
SYSTEM_CORE_NUM SYSTEM_CORE_LOGIC 32 SYSTEM_CORE_PHYSICS 24
SYSTEM_BIOS E15M2IMS.105
SYSTEM_LANGUAGE English (Regional Setting: English)
SYSTEM_MEMORY 32469.016MB
SYSTEM_VIRTUAL_MEMORY 134217727.875MB
SYSTEM_PAGE_FILE 56021.016MB
SYSTEM_STORAGE C:\ SYSTEM_HARDDISK_DRIVE SYSTEM_TOTALDISC_SPACE 1881.820GB SYSTEM_FREEDISC_SPACE 1218.154GB
SYSTEM_DIRECTX_VERSION DirectX 12
SYSTEM_GRAPHICS Intel(R) UHD Graphics
SYSTEM_GRAPHICS_DEVICE \\.\DISPLAY1
SYSTEM_GRAPHICS_CHIP Intel(R) RaptorLake-S Mobile Graphics Controller
SYSTEM_GRAPHICS_MAKER Intel Corporation
SYSTEM_GRAPHICS_VRAM 128.000 MB
SYSTEM_GRAPHICS_SHARED_VRAM 16234.508 MB
SYSTEM_GRAPHICS_DAC Internal
SYSTEM_GRAPHICS_DISPLAY_MODE 2560 x 1600 (32 bit) (240Hz)
SYSTEM_GRAPHICS_DRIVER C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_5d58d28606217d2f\igdumdim64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_5d58d28606217d2f\igd10iumd64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_5d58d28606217d2f\igd10iumd64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_5d58d28606217d2f\igd12umd64.dll
SYSTEM_GRAPHICS_DRIVER_VERSION 32.00.0101.6129
SYSTEM_GRAPHICS_DRIVER_DATE 10/17/2024 20:00:00
SYSTEM_GRAPHICS_DRIVER_LANGUAGE English
3.0
SYSTEM_GRAPHICS_PIXEL_SHADER 3.0
SYSTEM_GRAPHICS_VERTEX_TEXTURE SYSTEM_SUPPORT
SYSTEM_GRAPHICS NVIDIA GeForce RTX 4070 Laptop GPU
SYSTEM_GRAPHICS_DEVICE \\.\DISPLAY5
SYSTEM_GRAPHICS_CHIP NVIDIA GeForce RTX 4070 Laptop GPU
SYSTEM_GRAPHICS_MAKER NVIDIA
SYSTEM_GRAPHICS_VRAM 7948.000 MB
SYSTEM_GRAPHICS_SHARED_VRAM 16234.508 MB
SYSTEM_GRAPHICS_DAC Integrated RAMDAC
SYSTEM_GRAPHICS_DISPLAY_MODE 1920 x 1080 (32 bit) (60Hz)
SYSTEM_GRAPHICS_DRIVER C:\Windows\System32\DriverStore\FileRepository\nvmii.inf_amd64_3789e49ba4bd9327\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvmii.inf_amd64_3789e49ba4bd9327\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvmii.inf_amd64_3789e49ba4bd9327\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvmii.inf_amd64_3789e49ba4bd9327\nvldumdx.dll
SYSTEM_GRAPHICS_DRIVER_VERSION 32.00.0015.7270
SYSTEM_GRAPHICS_DRIVER_DATE 3/2/2025 20:00:00
SYSTEM_GRAPHICS_DRIVER_LANGUAGE English
3.0
SYSTEM_GRAPHICS_PIXEL_SHADER 3.0
SYSTEM_GRAPHICS_VERTEX_TEXTURE SYSTEM_SUPPORT
SYSTEM_SOUND Headset Earphone (Arctis 7 Chat)
SYSTEM_SOUND_DEVICE_ID {D9DB728F-D657-490C-AAC8-4C2BE83836F6}
SYSTEM_SOUND_DEVICE_NAME USBAUDIO.sys
SYSTEM_SOUND_DRIVER_VERSION 10.0.22621.4830
SYSTEM_SOUND_DRIVER_LANGUAGE English
SYSTEM_SOUND_DRIVER_DATE 1/21/2025 20:00:00
SYSTEM_SOUND Speakers (Realtek(R) Audio)
SYSTEM_SOUND_DEVICE_ID {22C0F849-6FC2-4161-952C-86FBE2080FC3}
SYSTEM_SOUND_DEVICE_NAME RTKVHD64.sys
SYSTEM_SOUND_DRIVER_VERSION 6.0.9579.1
SYSTEM_SOUND_DRIVER_LANGUAGE English
SYSTEM_SOUND_DRIVER_DATE 9/18/2023 20:00:00
SYSTEM_INPUT {6F1D2B60-D5A0-11CF-BFC7444553540000}
SYSTEM_INPUT_NAME Mouse
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 3 SYSTEM_GAMEPAD_BUTTON 8 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {6F1D2B61-D5A0-11CF-BFC7444553540000}
SYSTEM_INPUT_NAME Keyboard
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 128 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {1E0BA4D0-17F5-11EE-8002444553540000}
SYSTEM_INPUT_NAME Intel(R) HID Event Filter
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 1 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {1E0BA4D0-17F5-11EE-8004444553540000}
SYSTEM_INPUT_NAME Intel(R) HID Event Filter
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 1 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {1E0C4110-17F5-11EE-8006444553540000}
SYSTEM_INPUT_NAME Intel(R) HID Event Filter
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 1 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {69411310-6A13-11EF-8006444553540000}
SYSTEM_INPUT_NAME CORSAIR SLIPSTREAM WIRELESS USB Receiver
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 0 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {1E0D7990-17F5-11EE-800A444553540000}
SYSTEM_INPUT_NAME Intel(R) HID Event Filter
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 1 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {1E0DEEC0-17F5-11EE-800C444553540000}
SYSTEM_INPUT_NAME HIDI2C Device
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 0 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {1E0E15D0-17F5-11EE-800E444553540000}
SYSTEM_INPUT_NAME Intel(R) HID Event Filter
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 1 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {1E0EB210-17F5-11EE-8011444553540000}
SYSTEM_INPUT_NAME HIDI2C Device
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 0 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {1E0EB210-17F5-11EE-8012444553540000}
SYSTEM_INPUT_NAME HID Button over Interrupt Driver
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 1 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {1E0CDD50-17F5-11EE-8008444553540000}
SYSTEM_INPUT_NAME SteelSeries Gaming Keyboard
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 265 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {69411310-6A13-11EF-8005444553540000}
SYSTEM_INPUT_NAME CORSAIR SLIPSTREAM WIRELESS USB Receiver
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 1024 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {1E0F4E50-17F5-11EE-8015444553540000}
SYSTEM_INPUT_NAME SteelSeries KLC
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 0 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {1E0FEA90-17F5-11EE-8017444553540000}
SYSTEM_INPUT_NAME Converted Portable Device Control device
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 3 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {DF9CB4E0-18F4-11EE-8002444553540000}
SYSTEM_INPUT_NAME SteelSeries Arctis 7
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 5 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {1E0FEA90-17F5-11EE-8018444553540000}
SYSTEM_INPUT_NAME Converted Portable Device Control device
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 1 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {1E10ADE0-17F5-11EE-801A444553540000}
SYSTEM_INPUT_NAME Intel(R) HID Event Filter
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 5 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {1E10ADE0-17F5-11EE-801C444553540000}
SYSTEM_INPUT_NAME SteelSeries ALC
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 0 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {DF9CB4E0-18F4-11EE-8001444553540000}
SYSTEM_INPUT_NAME SteelSeries Arctis 7
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 0 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {1E10ADE0-17F5-11EE-801B444553540000}
SYSTEM_INPUT_NAME SteelSeries ALC
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 4096 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {69413A20-6A13-11EF-8007444553540000}
SYSTEM_INPUT_NAME CORSAIR SLIPSTREAM WIRELESS USB Receiver
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 0 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {1E10ADE0-17F5-11EE-801D444553540000}
SYSTEM_INPUT_NAME Keyboard
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 0 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {69416130-6A13-11EF-8008444553540000}
SYSTEM_INPUT_NAME CORSAIR SLIPSTREAM WIRELESS USB Receiver
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 1024 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {1E0F4E50-17F5-11EE-8014444553540000}
SYSTEM_INPUT_NAME SteelSeries KLC
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 4096 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {1E162C20-17F5-11EE-8020444553540000}
SYSTEM_INPUT_NAME Intel(R) HID Event Filter
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 1 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {783E7600-1825-11EE-8006444553540000}
SYSTEM_INPUT_NAME Controller (Xbox One For Windows)
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 5 SYSTEM_GAMEPAD_BUTTON 16 SYSTEM_GAMEPAD_FOV 1
SYSTEM_INPUT {1E162C20-17F5-11EE-8022444553540000}
SYSTEM_INPUT_NAME Intel(R) HID Event Filter
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 2 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {1E16C860-17F5-11EE-8024444553540000}
SYSTEM_INPUT_NAME Intel(R) HID Event Filter
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 1 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {1E171680-17F5-11EE-8026444553540000}
SYSTEM_INPUT_NAME Intel(R) HID Event Filter
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 1 SYSTEM_GAMEPAD_FOV 0
-=-=-=-=-=-=- Application Information -=-=-=-=-=-=-
FFXIVLauncher
#✨announcements✨ | Donut Realm - Discord
u4bxFNtbWHwV8i3iVjMxvDJBHu7Cf2V2QZBAz (PNG Image, 2160*×*1440 pixels) — Scaled (49%) — Mozilla Firefox
Realtek Audio Console
Realtek Audio Console
_SoftwareUpdateNotificationService_Window
Windows Input Experience
OmApSvcBroker
-=-=-=-=-=-=- Install Information -=-=-=-=-=-=-
MSI Afterburner 4.6.5
Battle.net
Epson Scan 2
Google Chrome
Jagex Launcher
Microsoft Edge
Microsoft Edge WebView2 Runtime
OBS Studio
Overwatch
RivaTuner Statistics Server 7.3.4
Steam
Microsoft Visual C++ 2013 Redistributable (x64) - 12.0.30501
Epson Event Manager
Microsoft Visual C++ 2022 X86 Additional Runtime - 14.34.31938
BrLauncher
Microsoft Visual C++ 2013 x86 Minimum Runtime - 12.0.21005
MSI Center SDK
Epson ScanSmart
Microsoft .NET Runtime - 6.0.16 (x64)
FINAL FANTASY XIV ONLINE
BrLogRx
Epic Online Services
Brother PowerENGAGE
PowerENGAGE
Launcher Prerequisites (x64)
Microsoft Visual C++ 2015-2022 Redistributable (x86) - 14.34.31938
Microsoft Visual C++ 2015-2022 Redistributable (x64) - 14.40.33810
Realtek Card Reader
MSI NBFoundation Service
NetworkRepairTool
Brother Printer Driver
SoftwareUpdateNotification
Brother iPrint&Scan
Microsoft Visual C++ 2022 X86 Minimum Runtime - 14.34.31938
BrSupportTools
Microsoft Windows Desktop Runtime - 6.0.13 (x64)
HttpToUsbBridge
Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.6161
Epic Games Launcher
Brother iPrint&Scan
StatusMonitor
Intel(R) Chipset Device Software
Epson Scan OCR Component Pro
Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219
Realtek Audio Driver
Microsoft Visual C++ 2013 Redistributable (x86) - 12.0.30501
UsbRepairTool
Microsoft Visual C++ 2013 x86 Additional Runtime - 12.0.21005
Old School RuneScape
MSI App Player 5
Logitech Gaming Software 9.04
Mozilla Firefox (x64 en-US)
Mozilla Maintenance Service
Microsoft 365 - en-us
Microsoft OneNote - en-us
Timberborn
Destiny 2
VTube Studio
NieR:Automata™
FINAL FANTASY XV WINDOWS EDITION
Bloons TD 6
SteelSeries GG 83.0.0
Microsoft .NET Host - 6.0.16 (x64)
Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219
Intel(R) Chipset Device Software
Microsoft Visual C++ 2022 X64 Additional Runtime - 14.40.33810
Microsoft .NET Runtime - 6.0.13 (x64)
Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.6161
Voicemod
Microsoft Windows Desktop Runtime - 6.0.13 (x64)
Intel(R) Serial IO
Microsoft .NET Host FX Resolver - 6.0.13 (x64)
Office 16 Click-to-Run Licensing Component
Office 16 Click-to-Run Extensibility Component
Microsoft Visual C++ 2013 x64 Additional Runtime - 12.0.21005
Intel(R) Serial IO
Microsoft Visual C++ 2013 x64 Minimum Runtime - 12.0.21005
Corsair iCUE5 Software
NVIDIA Graphics Driver 572.70
NVIDIA app 11.0.2.341
NVIDIA MessageBus 3 for NvApp
NVIDIA Backend
NvCpl
NVIDIA PhysX System Software 9.23.1019
NVIDIA FrameView SDK 1.5.10819.35301613
NVIDIA HD Audio Driver 1.4.3.2
NVIDIA Install Application
NVIDIA Container
NVIDIA AIUser Container
NVIDIA LocalSystem Container
NVIDIA Session Container
NVIDIA User Container
NVIDIA NvDLISR
NVIDIA Platform Controllers and Framework
NVIDIA Watchdog Plugin for NvContainer
NVIDIA Telemetry Client
NVIDIA ShadowPlay 11.0.2.0
NVIDIA USBC Driver 1.52.831.832
NVIDIA Virtual Audio 4.65.0.3
MSI True Color
Microsoft .NET Host FX Resolver - 6.0.16 (x64)
Microsoft Visual C++ 2022 X64 Minimum Runtime - 14.40.33810
Killer Ethernet Performance Driver Suite UWD
Microsoft Update Health Tools
Microsoft .NET Runtime - 6.0.16 (x64)
Killer Wireless Driver UWD
Epic Games Launcher Prerequisites (x64)
-=-=-=-=-=-=- Proccess Information -=-=-=-=-=-=-
C:\Program Files (x86)\Brother\BrUtilities\BrLogRx.exe 00004760
C:\Program Files (x86)\Brother\SoftwareUpdateNotification\SoftwareUpdateNotificationService.exe 00004AE0
C:\Program Files (x86)\Browny02\Brother\BrPrintFinishNotice\BrPrintFinishNotice.exe 000045A0
C:\Program Files (x86)\Browny02\Brother\BrStMonW.exe 00001F08
C:\Program Files (x86)\Epson Software\Event Manager\EEventManager.exe 00004B30
C:\Program Files (x86)\SquareEnix\FINAL FANTASY XIV - A Realm Reborn\boot\ffxivlauncher64.exe 0000259C
C:\Program Files (x86)\SquareEnix\FINAL FANTASY XIV - A Realm Reborn\boot\ffxivsysinfo64.exe 00005238
C:\Program Files (x86)\Steam\bin\cef\cef.win7x64\steamwebhelper.exe 0000491C
C:\Program Files (x86)\Steam\steam.exe 00004414
C:\Program Files\Logitech Gaming Software\LCore.exe 00001128
C:\Program Files\Mozilla Firefox\firefox.exe 00003914
C:\Program Files\NVIDIA Corporation\NvContainer\nvcontainer.exe 00001BE8
C:\Program Files\SteelSeries\GG\SteelSeriesGG.exe 00003CF4
C:\Program Files\SteelSeries\GG\apps\engine\SteelSeriesEngine.exe 00002D04
C:\Program Files\SteelSeries\GG\apps\engine\prism\SteelSeriesPrism.exe 000024B0
C:\Program Files\WindowsApps\A-Volute.Nahimic_1.9.17.0_x64__w2gh52qy24etm\Nahimic3.exe 00001EF4
C:\Program Files\WindowsApps\MicrosoftWindows.Client.WebExperience_423.13900.0.0_x64__cw5n1h2txyewy\Dashboard\Widgets.exe 00003570
C:\Program Files\WindowsApps\MicrosoftWindows.Client.WebExperience_423.13900.0.0_x64__cw5n1h2txyewy\Dashboard\widgetservice.exe 00001CD0
C:\Program Files\WindowsApps\RealtekSemiconductorCorp.RealtekAudioControl_1.52.355.0_x64__dt26b99r8h8gj\RtkUWP.exe 00005858
C:\Program Files\WindowsApps\SpotifyAB.SpotifyMusic_1.215.828.0_x64__zpdnekdrzrea0\XboxGameBarSpotify.exe 0000557C
C:\Users\gary1\AppData\Local\Discord\app-1.0.9186\Discord.exe 000044A8
C:\Users\gary1\AppData\Local\NhNotifSys\nahimic\nahimicNotifSys.exe 00001FB4
C:\Windows\Explorer.EXE 00002CA0
C:\Windows\System32\DataExchangeHost.exe 00005DA4
C:\Windows\System32\DriverStore\FileRepository\igoaudioservice.inf_amd64_dbbb64c599709ac4\iGoSwServer.exe 00002BFC
C:\Windows\System32\DriverStore\FileRepository\ipf_cpu.inf_amd64_b4463a9eb4e1c069\ipf_helper.exe 00001BD8
C:\Windows\System32\DriverStore\FileRepository\realtekservice.inf_amd64_7b2fe279bbb26e16\RtkAudUService64.exe 00003C18
C:\Windows\System32\RuntimeBroker.exe 00004C14
C:\Windows\System32\SecurityHealthSystray.exe 000014C0
C:\Windows\System32\oobe\UserOOBEBroker.exe 00000A50
C:\Windows\System32\smartscreen.exe 00004410
C:\Windows\SystemApps\Microsoft.LockApp_cw5n1h2txyewy\LockApp.exe 00003ED8
C:\Windows\SystemApps\Microsoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy\StartMenuExperienceHost.exe 0000344C
C:\Windows\SystemApps\MicrosoftWindows.Client.CBS_cw5n1h2txyewy\SearchHost.exe 00003450
C:\Windows\SystemApps\MicrosoftWindows.Client.CBS_cw5n1h2txyewy\TextInputHost.exe 00000F8C
C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\ShellExperienceHost.exe 0000121C
C:\Windows\system32\ApplicationFrameHost.exe 00002138
C:\Windows\system32\DllHost.exe 00003908
C:\Windows\system32\NahimicAPO4Volume.exe 00002F60
C:\Windows\system32\sihost.exe 00002AF0
C:\Windows\system32\svchost.exe 00000238
C:\Windows\system32\taskhostw.exe 00002B64
Random directx error crashes
Printable View
-
03-31-2025, 12:31 PMrebeka139Random directx error crashes
-
03-31-2025, 11:23 PMThetaCoder
Sadly, welcome to the club. I have the exact same problem, and have been fighting with SE since Feb, with no resolution.
Nice job so for on the diags, some other things they may tell you to try, just to beat them to the punch.
- Disable full screen optimizations for the executable
- Check that the built in GPU is disabled (may not be possible since your on a laptop)
- Silly, but make sure the OS is fully updated
- Also silly, but try giving the ffxiv_dx11.exe a higher cpu priority through task manager (did squat for me, but they did ask)
- A very minor thing that got a very small amount of stability was to turn down/off the shadows and their quality.
- I see you have Steam and a few other loaders. If FF14 is not the team version, they will ask that you shut them all down.
- I don't know if it's still true, but Nahimic used to have a REALLLY bad rap, and wasn't good to have on a machine, but it may not be removable in your situation, and it shouldn't really affect FF14, just a side note.
I feel for you, as the crashes make it difficult to play, let alone enjoy the game now. I don't know if any of these will help, or give you more stability, but they are thing SE is likely to ask you to try. My read is that they have a problem with the game, no clue where it is, or are unwilling to admit it or address it. But that's me after 6+ weeks of trying to resolve it.
Good luck. -
04-01-2025, 01:49 PMrebeka139
Thanks for advice Theta. I did have one crash in 7.1 that was error codeless like yours, but it was a one time thing. Not sure if disabling the integrated graphics card is possible, will put that at the bottom of the list to try. And I did try without Steam and other game loaders.
Adding some things I tried- Disable full screen optimizations (not full screen anyhow *shrugs*)
- Normal texture resolution instead of high (forgot to try that)
- Shadows on extra low everything (gosh they look bad and flickery like that lol)
- Having Windows GameBar completely uninstalled and very much installed and open. That DCOM error just seems to be happening at the same as crashes, and happens even when GameBar is uninstalled.
And a new patch means new error codes. Getting the top set of codes in MANY areas, even Aurum Vale which to me feels like not a graphically intense area.
https://i.imgur.com/SLEnUaS.png
Also, in reading the post about my previous laptop's problem, I remembered Event Viewer exists. Got 6 errors around when the above two popups happened, not sure if any of them line up time wise as I looked later. All 6 errors were:
Source: DistributedCOM
Event ID 10010
The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout.
I uninstalled the game bar, but I need to go to bed, so will test that one next and just leave event viewer up on the second monitor. -
04-01-2025, 11:51 PMThetaCoder
Yeah, laptop graphics are a bit odd, as even if you have a 'dedicated' GPU, it shares a lot of the same physical pathways and such as the onboard, so things get oddball. Laptops also sometimes have different drivers than their desktop counterparts.
Yes, Turning those settings down isn't a real fix, it's more of a way to try and give you a bit more stability in the game before it crashes.
I seem to (haven't gone back and counted) have longer stretches of playability when I'm not in any ARR or DT areas, of course, this does limit what one can do if they are trying to play the current content.
The errors in Event Viewer are just some of the multitude of little tiny MS hiccups they haven't fixed, and have nothing to do with FF14. I've watched the event viewer while playing and nothing from the game has ever popped up.
Ultimately the things I was mentioning are just things SE will have you try if you ever get a hold of them, so you can cut them off at the pass sort of and save some time. Hopefully for you, me and the other people with this issue someone starts seeing a real issue and gets it fixed. -
04-08-2025, 09:01 AMDemon_Giri
I recently went down a rabbit hole of crashing somewhat consistently between 1 to 2 hours of playtime, no matter what I did.
For me, it was a minor instability with my RAM that only surfaced in FFXIV, and may not have had any issue until recently. Hard for me to say, as this was a new build, and my personal build is older and doesn't use higher frequency RAM or 13/14th gen intel.
Please try a memtest86 if you haven't already. There's no harm done in doing it, as it doesn't change anything, just gives you information.
I also did a more in-depth writeup of research and other solutions I feel are *actually* worthwhile and not just random BS here https://www.reddit.com/r/ffxiv/comme...t=share_button
I hope that this helps you.
EDIT: Also worth noting, while there's mention of "dx11" in the call stack in your error windows, this isn't necessarily pointing at DirectX. That's just part of the FFXIV executable's filename. -
04-09-2025, 01:56 AMrebeka139
Thanks for that write up, first I've seen on the seemingly random mid-game crashes and not on load/title screen crashes. Checking BIOS stuff was further down my list since it's what fixed my crashes with my previous laptop. Was something to do with the fact that it "could" overclock (even if it wasn't actively overclocked) was causing a complete system crash and restart, it was weird and only on the first pass of graphics cards for that laptop. I just dislike doing moderately risky stuff even though I know I won't mess up when reading a guide.
Windows memory test came back clean. Going to try a BIOS update next and then the memtest86, when my job lets me be home.
And got it with the directX nomenclature. I forgot there was ever a DX9 version and that's how they distinguished the two executables. -
04-12-2025, 12:21 PMrebeka139
(cross posting on your reddit write up). Spent the past few days testing things.
-Did a Windows memory test > Returned nothing
-Updated BIOS to the most recent official version > Did 2 overnight afk-lower-frames tests at Gridania Aetheryte. First one 90k'd (so unrelated) and the second survived ~10 hours. Did the 7.2 dungeon for expert roulette after the second test, and got the random crash THREE TIMES during the dungeon. Even reset my computer between the 2nd and 3rd crash, but that did nothing.
-Ran a MemTest86, all 14 tests including the experimental DMA test > PASSED, 0 errors...
So, uh, I'm kinda at a loss now. Was kinda hoping my RAM was messed up, but now I'm back to having no clue or lead on what's causing these crashes. Is there a "processortest86" out there? That's the only thing I can think of at the moment.
Error code I'm getting constantly, for reference (time is just related to the current patch):
An unexpected error has occurred. Exiting Final Fantasy XIV. 2025-03-26_14:08
ffxiv_dx11.exe+3E07EF
ffxiv_dx11.exe+3E0731
ffxiv_dx11.exe+5FA114
ffxiv_dx11.exe+6A2671
ffxiv_dx11.exe+5FA00E
ffxiv_dx11.exe+1B7A0D
ffxiv_dx11.exe+1B7CB3
ffxiv_dx11.exe+A1F00 -
04-12-2025, 12:49 PMGoodEater
Have you tried rolling back your nvidia drivers to 566.36? Driver versions such as 572. Seem to be causing problems with a number of games right now.
-
04-12-2025, 04:02 PMDemon_Giri
I'm sorry to hear that it didn't fix your issue.
Is your installed RAM what came with the laptop?
I also think it would be worth setting proper power limits for your CPU, as the 13th and 14th are often not set properly by motherboard manufacturers, and some users have written some decently documented posts on these chips being more stable in FFXIV afterward. We can do this temporarily just to test it out, and put it back if you find it doesn't work.
(I'm under the assumption you have an MSI)
in your BIOS, please set the following settings
In the OC section,
OC Explore mode: Expert
Advanced CPU Configuration:
Short Duration Power Limit: 253W
Long Duration Power Limit: 125W
CPU Current Limit: 307
Save and apply settings, boot into windows, then please download and install Intel XTU. You'll need to reboot once it's installed.
In Intel XTU, please change performance core ratio down a notch. So if it's 55x, make it 54x. Hit apply and please reboot one more time, then try your game.
Best of luck,
Giri -
04-13-2025, 03:46 AMrebeka139
Yes, it's the stock RAM, I haven't opened up this laptop at all. 2x 16GB part number SK Hynix HMCG78AGBSA092N
Also tried Intel's Processor Diagnostic and Prime95 for 15 mins (said most errors are found within that time). Both of those came back clean
As far as the undervolting, hit a brick wall immediately there. XTU is saying overclocking is disabled, and my BIOS has very limited options. Pictures below.
https://i.imgur.com/bbNhG0A.png
https://i.imgur.com/5k3AiGo.jpeg -
04-13-2025, 04:49 AMDemon_GiriApologies. Looks like MSI laptops have some of their bios hidden. Once you get into the main bios screen, press:Quote:
Originally Posted by rebeka139
Left Alt + Right Shift + Right Ctrl + F2 all at the same time. This should unhide some of the settings. I'm unsure if you will find the settings I mentioned before in there but you can take a look.
As for Intel XTU, there may be a toggle for "protection" within the hidden menu, but I'm unsure what your specific bios might call it. Could you take a picture of the settings you have if you manage to get that menu open?
Cheers -
04-13-2025, 06:39 AMrebeka139Ah, yes, the Super Secret Menu, where my scroll wheel is backwards. Here's an album of various things that seemed relevant: https://imgur.com/a/rebeka139-bios-oCo2t0tQuote:
Originally Posted by Demon_Giri
No sign of short duration power limit, long duration, or cpu current limit. Could be because I'm on a laptop and it has to account for AC and DC power? *shrugs* I found the same 56x/52x values that XTU showed, but they weren't editable in BIOS, or at least they wouldn't save. different numbers
I'm currently testing with Turbo Mode disabled. It was the only thing that jumped out at me as something that could cause minor stability issues to FFXIV with 2 Pcores being 56x and the other 6 being 52x.
Also, while writing this, I rechecked XTU advance view. The two watt settings here are referred to as "short duration" and "extended duration" power limit. Would that be the short and long we're looking for?
https://i.imgur.com/dJHqacw.png
Edit: Initial results of Turbo mode disabled: CPU is hold temps around 65-70ºC while playing, used to be sporadic between 70 and 93. The cpu cooling fan has NEVER been so quiet while gaming, I can actually hear the gpu fan. Holding steady at 60 fps. gpu has climbed to 90% usage sometimes but mainly in the 60%'s, not sure if it did before, paid more attention to the cpu before this. cpu usage is only at 15% at most. Did the 7.2 dungeon and desert lvl 100 dungeon for roulettes, same as yesterday. 4 crashes total yesterday within that time, 0 today.
I know that's not comprehensive results when it comes to a random crash, but I'm liking them thus far. -
04-13-2025, 09:49 AMDemon_GiriI'd recommend keeping Turbo Mode enabled. That's what allows your processor to increase operating speed when it's given more demanding tasks. Without it, your CPU will only run at base speed at all times. It may remove your crashing, as your CPU will be running extremely-throttled, but it would be a very heavy-handed way to do it. At the very least, I would try looking in the BIOS again and seeing if those core ratios are still what you set them to/what they originally were. I would listen to what the BIOS says they are over what Intel XTU says they are. Intel XTU does change BIOS values, but can only read/write what the BIOS/MOBO allows it, so I'd defer to the BIOS first.Quote:
Originally Posted by rebeka139
To answer a few questions:
In your imgur album, the third picture from the bottom, "Power Limit 1" and "Power Limit 2" are the short duration and long duration power limits. PL1 being the long duration. Also, yes, these correlate with "Turbo Boost Short Power Max" and the "Turbo Boost Power Max" settings in Intel XTU.
No relation to AC/DC power as far as available settings go. Yes, your laptop has an AC to DC adapter. The power supply in a desktop PC does the same thing. Assuming you don't have some kind of weird faulty power problem, nothing AC should ever be touching your PC or anyone else's. Pretty much all consumer-level electronics run on DC and have some kind of adapter either in the cable or built into the device itself. Available BIOS options will be largely based on what the particular motherboard manufacturer allows you.
Additionally, I have to apologize. I misread your processor model originally, so please ignore the original power limits and current limit I provided you. To avoid severely gimping your processor by turning turbo completely off, but still gain stability since the crashing does seem to be related to how the CPU is running, I'd suggest turning Turbo Mode back on, and then boot into Windows and set the following values in Intel XTU:
Turbo Boost Short Power Max: 157 W
Turbo Boost Power Max: 157 W
157W is the official "Maximum Turbo Power" wattage per Intel's official site for your processor.
We don't want the processor pulling more power than it should for turbo, sacrificing stability in the process, so lets try a little more conservative/official wattage for turbo, based on Intel's specs. We also don't necessarily want to run it LOWER than 157W for extended periods of turbo, so that's why we're setting both short and long duration turbo to the same value. It was already set to 220 on both before anyway.
I did grab a laptop of mine and was able to dig more into the MSI bios you have, myself, to get a little better idea of where things are and what they're named, but I think we might be able to do much of what we want from Intel XTU, which should write to the BIOS settings when you hit Apply anyway. You will just need to re-enable Turbo from in the BIOS.
So, just for clarification, I'd suggest:
- Boot into BIOS, re-enable turbo mode, check to see if P-Core Ratios are still what you set them to before/what they originally were. There should be two "blocks" of settings for those. One is labeled "current settings" at the top, the second "block" of values is where you would adjust them, I believe.
- Boot into Windows, Open Intel XTU, Set:
Turbo Boost Short Power Max: 157W
Turbo Boost Power Max: 157W
- Hit Apply in Intel XTU
- Reboot into BIOS, check the Power & Performance>CPU - Power Management Control>Configure Turbo Options menu to see if PL 1 and PL 2 match the 157W you just set in Intel XTU, just to make sure they took
- Reboot into Windows and try your game for a while. Monitor temps if you'd like
Hope that helps clear some things up. Let me know if you run into a snag in that process,
Giri -
04-13-2025, 12:15 PMrebeka139
You don't have to apologize, if it weren't for you I probably wouldn't have found the turbo mode on/off switch for another month or two. The fact that there's an actual chance of a light at the end of the tunnel is such a relief.
I did turn off Turbo mode mainly as a heavy handed find the source of the problem type move. It worked, but now I get ~45fps in populated areas and frontline. Still running way colder though, was peaceful without the fans going brrrrrrrr 100% of the time. Turning turbo back on and changing the voltage in XTU was going to be my next test if I didn't hear back, so good to see I was heading the right direction.
If you don't hear from me for a bit, no news is good news. I'll definitely update here and the reddit post with results, especially if sharing this info helps even one other person with this issue.
Edit: welp, immediate results of still crashing the game. Same call stacks. Tried lowering the wattage to 150 in XTU and logging back into the Frontline I was in. Game crashed a second time, so two crashes within a 15 min match. Temps were still roughly what they were from before today's testing, peaking around 93C and fans going full blast even when not near large groups. I know undervolting too much can cause damage if it goes too low, but is there a good place to start with limiting the wattage further? -
04-14-2025, 12:33 AMDemon_GiriDon't confuse turbo power limiting with undervolting here.Quote:
Originally Posted by rebeka139
Turbo power limits just say that when the cpu goes into turbo, it can't draw more than a certain wattage
Undervolting actually reduces how much power you're giving the cpu at all times
When UNDERVOLTING, you'd want to make extremely small adjustments (in volts), but the wattage change you made on the power limit honestly isn't huge.
Intel's official specs for your processor are:
Processor base power: 55w
Maximum turbo power: 157w
With the i7-14700k as an example, people usually recommend power limiting that one for exactly what Intel's specs on it are, which is 125w and 253w respectively, so let's just try setting yours the same way.
This would be 157w (or you can leave this at 150 if you want) for your short duration, and 55w for the long duration.
55w is the wattage for base frequency, so this will probably keep it from running at turbo speeds over long periods of time. If your performance is noticeably worse with this but you're not crashing anymore, you might be able to play with slowly raising it back up little by little until you find a sweet spot. -
04-14-2025, 02:55 AMrebeka139Learning a lot here, so thank you for bearing with me.Quote:
Originally Posted by Demon_Giri
Ok, so basically long/extended duration is a reference point of what power it likes to be at average (set between 55-157W for my processor) but it can go above that point. Short duration power is a cap on what power it can go up to for short bursts (157W max for me). The 56s setting is duration over which the power needs to average at the long duration reference point, and so it'll de-turbo if it starts averaging above. Just like to know what I'm messing with here.
And some good news, I found the overclock on/off switch (power & performance > CPU Managemant > Configure CPU Lock Options (at the bottom) > Disable Overclock lock), so I can finally edit those 52x/56x on the Pcores. Only seem to be able to edit them in the BIOS and not XTU, but that's fine, I know my way through that maze now.
If I'm understanding those, 52x means 52 times the clock speed (100 or 102.4MHz I'm guessing?) for ~5200MHz.
For my current test, I set short and long to 157W again and all Pcores to 52x instead of two at 56x and 6 at 52x like it's been all this time. Afterburner was showing 5242 and 5141 as the top two speeds. Temps are up in the 80C's but I didn't see any peaks in the 90C's. No crash yet after 7.1 dungeon and a frontline. It's entirely possible ffxiv just doesn't like mix-matched core speeds, and why the crash seemingly happened more often in graphically modern or crowded areas, but could still happen anywhere if the right processes hit that core speed discrepancy.
The one question I have about the Pcores at the moment, and just using arbitrary numbers here. Which is better for the CPU's long term health:
>52x/5200MHz and 8-11% usage (current)
>45x/4500MHz and 15-20% usage (rough estimates here) -
04-14-2025, 03:30 AMDemon_GiriI shit you not, I was in the process of writing an additional reply that suggested putting your power limits both back to 157 if that didn't work, and moving forward with turbo ratio adjustment.Quote:
Originally Posted by rebeka139
Your first question: The turbo power LIMITS are just that. They are limits, in wattage, of how much power the CPU can try to pull to try to achieve its turbo goals (this would be the turbo ratios). The 56 seconds setting is the definition of what it will consider "short" duration, to make the distinction between how much power it's allowed and for how long. For instance, you could say you want the CPU to be able to pull 200W but only for 10s, at which point it's only allowed 100W for turbo duties from that point onward, until it comes back out of turbo and makes a new request. This could look something like 200w for 10s and then 100w for 5 minutes. Just an example. Instituting these limits doesn't inherently tell your processor it can't try to run that fast, it just gives it less fuel when it tries. These can reduce temperatures (indirectly) and power bill.
I'm glad you found the OC lock. I had also found that in my laptop's BIOS between writings, and was doing my own testing to see toggling that would let me into more settings in XTU, but I don't have the same computer or processor as you, so my results vary from yours in that regard.
Your second question: The turbo ratios are directly correlated to the frequency that the CPU tries to run at when turbo, so reducing those ratios will directly reduce the ceiling of speed at which your processor can run. This would also, more directly and drastically, result in lower temperatures and lower power draw. You're literally telling it to run slower (when turbo).
I don't necessarily suspect the core speeds being different from eachother being the problem, but it's possible. I was going to suggest dropping each of them by about 5 respectively, which would have left them different from eachother, but a reduction across the board. I was also going to suggest the same thing on your E-Core ratios, but if you find that the change you already made stays solid, then I'd leave it. No reason to reduce it further if not for stability, unless you're just really wanting lower thermals for your laptop experience. This obviously costs you overall performance. If you ever want to confirm your ratio settings took without having to book back into BIOS, you can use HWINFO64 to see them individually.
When you open it, it'll pop up a system summary window. Close that, then in the main window you should see a list of dropdowns on the left side. open the Central Processor(s) dropdown and click on the name of your CPU. In the right-hand pane that opens, you can scroll down to the "Operating Points" section and see the "Turbo Ratio Limits (P-Cores)" entry and "Turbo Ratio Limits (E-Cores)" entry. It'll show something like 56x(1-2c), 52x(3-4c), etc. The x part being the multiplier, and the 1-2c part being which cores it applies to. Not necessary, just a tool you can use if it adds any convenience to you.
In response to your long term health question, I don't want to speak beyond my personal knowledge here, but with my current understand, I THINK:
The actual CPU usage is just a metric of how saturated or at-capacity the CPU is by its current task load. This doesn't have much bearing on life. The main factors that have influence on overall CPU lifespan are HEAT and power. Having good cooling is one of the best ways to elongate CPU life, as well as running it with an appropriate amount of power. Both of those reasons are why overclocking generally reduces life, as overclocking is usually giving it more power and pushing it harder to get more performance out of it, at the cost of higher thermals and higher power draw.
So, in your case, the 4500MHz turbo would hypothetically keep it cooler and drawing less power, which hypothetically would have a longer lifespan than the 5200MHz. It would also be slightly less performant. However, I wouldn't say you're likely to have a noticeable difference in lifespan in this case.
You may be able to drop it down to 4500MHz and not see much change in FFXIV, as your GPU is doing most of the work there, but you might find a bit less performance in CPU-centric tasks. Just FYI.
Hope that helps,
Giri -
04-14-2025, 04:50 AMwarhammer40kWTf is going on?
I just got this today after logging out to go make some food and then trying to log back in and got that error message. Been playing since ARR opening and never had any issues like this.
-
04-14-2025, 04:52 AMwarhammer40kWTf is going on?
Why is all this stuff happening all of a sudden? I was online and playing the game and then logged out to go make lunch and then tried to log back in and this error message appeared and now I can't log in. WTF is going on with SE?
-
04-14-2025, 07:13 AMrebeka139
I'm 3.5 hours into sitting afk in Tuliyollal, but with frames not reduced when afk/tabbed out, plus a hunt train. Still no crash including that dungeon and frontline earlier. Temps are a solidly in the low 90C's, but I'm going to tweak it to not be that hot all the time, definite overkill for this game.
Will continue to monitor it, but thank you so much for all the help and teaching.
Warhammer, it may help to make your own thread. While you may have gotten the same hexadecimal codes as me, it's really just a "something's wrong" kind of error message. My problem here was stupidly technical, yours may just be a full screen optimization or reset settings to default in the launcher type thing, but it still would be better to contain it in your own thread instead of two conversations here. And be specific exactly where you mean by log in, because that could be perceived as 3 separate things.Quote:
Originally Posted by warhammer40k
-
04-14-2025, 07:23 AMDemon_GiriGlad I could help and happy to hear you're running better.Quote:
Originally Posted by rebeka139
Take care -
04-15-2025, 01:58 AMXupojoonyohl
Good morning fellow adventurers and thank you all for posting in the Final Fantasy XIV Technical Support Forums.
I apologize for the delay in our response to your concern. I am glad that you are no longer experiencing this issue. If you have any more questions or concerns, please post again in the technical support forums.
This thread will be moved to "Closed Concerns”