After a 6 month or so break from game I'm back but have ran into some issues upon return. I started my break right before the May update which adjusted the UI in game and caused some issues with existing dat mods. I believe I solved all of those issues through some trouble shooting and downloading the newest dat mods after the update. The issue I have now is random crash to desktop which can happen on any one of my 6 accounts. I have the windows event viewer dump and I'm hoping someone much smarter than I could provide insight on what this could possibly be.
General info:
Nvidia RTX 3080
Driver version 566.14
12 Gen Core i9-12900K
64 GB Ram
Windows 10
Dgvoodoo2 (VRAM set to only 256)
XIView 2.0, using latest from here:
https://github.com/KenshiDRK/XiView
Using XI Pivot on one character, but not the rest. For kicks I ran XI without XI Pivot on my main and still receive the same crash. I assume I can rule this out.
Here's two separate dumps that occurred very close time wise together.
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2024-11-21T17:31:17.5441835Z" />
<EventRecordID>52460</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>DESKTOP-QPQ18C5</Computer>
<Security />
</System>
- <EventData>
<Data>pol.exe</Data>
<Data>1.18.13.0</Data>
<Data>4e3bcddc</Data>
<Data>KERNELBASE.dll</Data>
<Data>10.0.19041.5131</Data>
<Data>082fad93</Data>
<Data>c0000005</Data>
<Data>0014623c</Data>
<Data>67c0</Data>
<Data>01db3c2f5d4fde3a</Data>
<Data>C:\Program Files (x86)\PlayOnline\SquareEnix\PlayOnlineViewer\pol.exe</Data>
<Data>C:\WINDOWS\System32\KERNELBASE.dll</Data>
<Data>ab7ab714-a62e-4046-9fda-09a3388831ea</Data>
<Data />
<Data />
</EventData>
</Event>
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2024-11-21T17:44:50.7464288Z" />
<EventRecordID>52464</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>DESKTOP-QPQ18C5</Computer>
<Security />
</System>
- <EventData>
<Data>pol.exe</Data>
<Data>1.18.13.0</Data>
<Data>4e3bcddc</Data>
<Data>KERNELBASE.dll</Data>
<Data>10.0.19041.5131</Data>
<Data>082fad93</Data>
<Data>c0000005</Data>
<Data>0014623c</Data>
<Data>6428</Data>
<Data>01db3c2fbb649f8a</Data>
<Data>C:\Program Files (x86)\PlayOnline\SquareEnix\PlayOnlineViewer\pol.exe</Data>
<Data>C:\WINDOWS\System32\KERNELBASE.dll</Data>
<Data>fbe6545d-c83a-46a3-b279-21ca55db2ffd</Data>
<Data />
<Data />
</EventData>
</Event>
Any help would be greatly appreciated. One last thing to mention, I do seem to be having an issue with going from POL to FFXI, the borderless window FFXI screen will load black and then hang up with the blue mouse wheel spinning for roughly 35 seconds. Then it will resume as normal. This happens on all six accounts. I ran Thorny's ram patch and that oddly enough fixed it for the next log in cycle, but after last night maintenance it's back again this morning.
FFXI Random Crash To Desktop
FFXI random crash to desktop
For me the only fix that resolved game crashes very similar to yours (started approx. in july2024) was replacing motherboard , main SSD drive and reinstalling windows. Kept everything else including processor and GPU. Since it was covered by my Lenovo warranty i only lost time. Game runs smoth again. 6 characters take about 15% CPU and 35-50% GPU resources. Still cant figure out what exactly made it crash hardware of software...
Event viewer logs are hard to look at in that format. You may also need to consider the surrounding events in the log. There's also the chance there is no relevant data and the issue is occurring internally.
The guy above I would have pointed at ram or a bad system file.
Didn't the patch have to be applied anytime there was pol.exe change?
The guy above I would have pointed at ram or a bad system file.
Didn't the patch have to be applied anytime there was pol.exe change?
Ragnarok.Blackcoffee said: »
Dgvoodoo2 (VRAM set to only 256)
why do you have vram set so low? you have plenty on that card.
was it a typo? 256 is really low.
if it wasn't you should increase that to the highest value you can manage when using 6 accounts, 2048 probably
Ragnarok.Blackcoffee said: »
Dgvoodoo2 (VRAM set to only 256)
This is bad, it's likely to break if you do this.
VRAM value is what dgVoodoo2 reports to the game during DX initialization, if that value is too small it will cause issues, if it's larger then 2GB it can also cause issues. Set it to 2048MB and leave it alone.
Thanks for all the feedback!
Yikes. Did you do it all at once or did you strategically do it like reinstalling windows, then SSD, then Mobo? Or all at once? I feel like I may have to go this route. My PC runs similar to yours resource wise 6 box.
I tried a ffxi file check and ran everything dat wise vanilla, but I still had a CTD at 4am this morning. And yea, the RAM patch has to be run every time there's a file check I believe.
notice the card you have: Nvidia RTX 3080
why do you have vram set so low? you have plenty on that card.
was it a typo? 256 is really low.
if it wasn't you should increase that to the highest value you can manage when using 6 accounts, 2048 probably
This is bad, it's likely to break if you do this.
VRAM value is what dgVoodoo2 reports to the game during DX initialization, if that value is too small it will cause issues, if it's larger then 2GB it can also cause issues. Set it to 2048MB and leave it alone.
I actually did run at 256 MB since that was the default setting lol. Oddly enough back in April of this year I was running the game like this with no issues. I believe I have 10 GB of ram on this GPU so I went ahead and upped it to 1056 MB. If I full time 6 box would running at 2048MB cause issues potentially since 2048 x6 = 12,288MB which exceeds my 10GB?
One item I did think of was packetflow. I just saw my settings run this at all times and not only in instances. Sounds like a reach, but could that cause issues?
I think I'll just need to reinstall FFXI and see if that fixes it, after that maybe windows. For the reinstall of FFXI, the POL download files are ok? I saw something about the steam install being "better" for some reason but it could have been an old post.
Phoenix.Zzzeeettt said: »
For me the only fix that resolved game crashes very similar to yours (started approx. in july2024) was replacing motherboard , main SSD drive and reinstalling windows. Kept everything else including processor and GPU. Since it was covered by my Lenovo warranty i only lost time. Game runs smoth again. 6 characters take about 15% CPU and 35-50% GPU resources. Still cant figure out what exactly made it crash hardware of software...
Yikes. Did you do it all at once or did you strategically do it like reinstalling windows, then SSD, then Mobo? Or all at once? I feel like I may have to go this route. My PC runs similar to yours resource wise 6 box.
Fenrir.Jinxs said: »
Event viewer logs are hard to look at in that format. You may also need to consider the surrounding events in the log. There's also the chance there is no relevant data and the issue is occurring internally.
The guy above I would have pointed at ram or a bad system file.
Didn't the patch have to be applied anytime there was pol.exe change?
The guy above I would have pointed at ram or a bad system file.
Didn't the patch have to be applied anytime there was pol.exe change?
I tried a ffxi file check and ran everything dat wise vanilla, but I still had a CTD at 4am this morning. And yea, the RAM patch has to be run every time there's a file check I believe.
Fenrir.Niflheim said: »
Ragnarok.Blackcoffee said: »
Dgvoodoo2 (VRAM set to only 256)
why do you have vram set so low? you have plenty on that card.
was it a typo? 256 is really low.
if it wasn't you should increase that to the highest value you can manage when using 6 accounts, 2048 probably
Asura.Saevel said: »
Ragnarok.Blackcoffee said: »
Dgvoodoo2 (VRAM set to only 256)
This is bad, it's likely to break if you do this.
VRAM value is what dgVoodoo2 reports to the game during DX initialization, if that value is too small it will cause issues, if it's larger then 2GB it can also cause issues. Set it to 2048MB and leave it alone.
I actually did run at 256 MB since that was the default setting lol. Oddly enough back in April of this year I was running the game like this with no issues. I believe I have 10 GB of ram on this GPU so I went ahead and upped it to 1056 MB. If I full time 6 box would running at 2048MB cause issues potentially since 2048 x6 = 12,288MB which exceeds my 10GB?
One item I did think of was packetflow. I just saw my settings run this at all times and not only in instances. Sounds like a reach, but could that cause issues?
I think I'll just need to reinstall FFXI and see if that fixes it, after that maybe windows. For the reinstall of FFXI, the POL download files are ok? I saw something about the steam install being "better" for some reason but it could have been an old post.
Ragnarok.Blackcoffee said: »
I actually did run at 256 MB since that was the default setting lol. Oddly enough back in April of this year I was running the game like this with no issues. I believe I have 10 GB of ram on this GPU so I went ahead and upped it to 1056 MB. If I full time 6 box would running at 2048MB cause issues potentially since 2048 x6 = 12,288MB which exceeds my 10GB?
So that value isn't how much dgVoodoo2 eats immediately, it's how much it reports is "available" to be eaten. While FFXI was indeed designed to run on very small amounts of GPU memory, it was also designed to run at 640x480 30FPS and tiny texture sizes. Modern systems are able to run it at much higher quality, and modern Windower takes advantage of this and lets you set higher resolutions and use higher quality textures from mods. Translating from DX8 to DX11 also incurs an increase in memory overhead as DX11 uses more buffers / caches.
When you put all that together you get much higher memory usage then vanilla FFXI. If you are running a bunch of really tiny windows with no texture swaps, then 512MB is fine. If running larger resolutions then 1024MB, and if running a full screen 2560x1440p or 3840x2160 then you definitely want 2GB.
You can actually go higher then 2GB, but you need to use the LargeAddressAware mod for that.
Asura.Saevel said: »
Ragnarok.Blackcoffee said: »
I actually did run at 256 MB since that was the default setting lol. Oddly enough back in April of this year I was running the game like this with no issues. I believe I have 10 GB of ram on this GPU so I went ahead and upped it to 1056 MB. If I full time 6 box would running at 2048MB cause issues potentially since 2048 x6 = 12,288MB which exceeds my 10GB?
So that value isn't how much dgVoodoo2 eats immediately, it's how much it reports is "available" to be eaten. While FFXI was indeed designed to run on very small amounts of GPU memory, it was also designed to run at 640x480 30FPS and tiny texture sizes. Modern systems are able to run it at much higher quality, and modern Windower takes advantage of this and lets you set higher resolutions and use higher quality textures from mods. Translating from DX8 to DX11 also incurs an increase in memory overhead as DX11 uses more buffers / caches.
When you put all that together you get much higher memory usage then vanilla FFXI. If you are running a bunch of really tiny windows with no texture swaps, then 512MB is fine. If running larger resolutions then 1024MB, and if running a full screen 2560x1440p or 3840x2160 then you definitely want 2GB.
You can actually go higher then 2GB, but you need to use the LargeAddressAware mod for that.
Thanks for the info, I went ahead and changed it to 2GB.
As an update, I tried reinstalling FFXI but ran into the same issues. I ended up reinstalling windows 10 completely and so far it appears the crash to desktop issue has been resolved.
Necro Bump Detected!
[243 days between previous and next post]
Appropriating this thread for a similar issue I'm facing. I don't know if a Windows reinstall applies since this Windows install is relatively fresh.
Recently, FFXI will freeze for a few seconds before crashing to desktop without any error. This can happen minutes or hours after launching the game without any rhyme or reason. The Event Viewer > Windows Logs > Application section contains something like this each time:
Sometimes LuaCore.dll isn't included. Just pol.exe.
From my understanding, 0xc0000005 is a memory access issue. I've done the following so far to remedy:
1) Reinstall Windower
2) Prune Windower plugins to find a culprit
3) Clean sweep and reinstall NVIDIA drivers
4) Tested RAM for errors (three different applications)
5) Checked SSD integrity
6) System file scan and repair
7) Malware and virus scan
No problems found, or no improvements made. I'm running out of ideas.
Windows 11 was installed about a month ago. No other applications have acted strangely outside FFXI.
Recently, FFXI will freeze for a few seconds before crashing to desktop without any error. This can happen minutes or hours after launching the game without any rhyme or reason. The Event Viewer > Windows Logs > Application section contains something like this each time:
Sometimes LuaCore.dll isn't included. Just pol.exe.
From my understanding, 0xc0000005 is a memory access issue. I've done the following so far to remedy:
1) Reinstall Windower
2) Prune Windower plugins to find a culprit
3) Clean sweep and reinstall NVIDIA drivers
4) Tested RAM for errors (three different applications)
5) Checked SSD integrity
6) System file scan and repair
7) Malware and virus scan
No problems found, or no improvements made. I'm running out of ideas.
Windows 11 was installed about a month ago. No other applications have acted strangely outside FFXI.
Assuming Windows 11, Did you disable Game Mode?
Before I officially recommend the following, what are your system specs? At first glance, it sounds like you're using a laptop, some combined integrated+PCIE graphics card combination or that you are simply not using DGVoodoo (or dxproxy).
Worst case, and I hope this isn't true. But, you may be using an early Intel i9-13/14x00 series CPU that was recalled ~2 years ago due to some freezing/instability issues. (Intel extended the RMA period to 3 years too. In my case, they upgraded me for free from an i9-13900k to i9-14900k, but it took 2 weeks for me to buy the new CPU and 2 MONTHS to get reimbursed by intel. I sent an email every other week until they did it, but they're support guy was always responsive)
Anyway, please share your system specs before you do these things:
0.) If this is a new PC build with 0-2 year old hardware, did you update your BIOS settings, device drivers (not just GPU) or check your manufacturer's release notes?)
1.) Disable thermal throttling of your CPU/GPU (this is to observe if freezing happens at the same amount of time as your previous observations). You'll want to use a program like HWInfo64 to monitor System/CPU/GPU temps to make sure you're not throttling or freezing due to high temperatures.
2.) Completely separate from #1, you can go to your BIOS and enable/disable low power states for your PCIE devices. This is to ensure that your GPU isn't entering a low-power state (called C-states) that FFXI doesn't know how to wake-up.
3.) Odd question: Have you replaced or added any third party power or USB cables in your build. (I could tell you stories of how shotty cables from USB devices have suddenly caused blue screens and PC freezes).
Always make a note of your current BIOS settings before changing them (via a pen/paper or a screenshot from your phone).
Before I officially recommend the following, what are your system specs? At first glance, it sounds like you're using a laptop, some combined integrated+PCIE graphics card combination or that you are simply not using DGVoodoo (or dxproxy).
Worst case, and I hope this isn't true. But, you may be using an early Intel i9-13/14x00 series CPU that was recalled ~2 years ago due to some freezing/instability issues. (Intel extended the RMA period to 3 years too. In my case, they upgraded me for free from an i9-13900k to i9-14900k, but it took 2 weeks for me to buy the new CPU and 2 MONTHS to get reimbursed by intel. I sent an email every other week until they did it, but they're support guy was always responsive)
Anyway, please share your system specs before you do these things:
0.) If this is a new PC build with 0-2 year old hardware, did you update your BIOS settings, device drivers (not just GPU) or check your manufacturer's release notes?)
1.) Disable thermal throttling of your CPU/GPU (this is to observe if freezing happens at the same amount of time as your previous observations). You'll want to use a program like HWInfo64 to monitor System/CPU/GPU temps to make sure you're not throttling or freezing due to high temperatures.
2.) Completely separate from #1, you can go to your BIOS and enable/disable low power states for your PCIE devices. This is to ensure that your GPU isn't entering a low-power state (called C-states) that FFXI doesn't know how to wake-up.
3.) Odd question: Have you replaced or added any third party power or USB cables in your build. (I could tell you stories of how shotty cables from USB devices have suddenly caused blue screens and PC freezes).
Always make a note of your current BIOS settings before changing them (via a pen/paper or a screenshot from your phone).
Felgarr said: »
Assuming Windows 11, Did you disable Game Mode?
Felgarr said: »
Before I officially recommend the following, what are your system specs? At first glance, it sounds like you're using a laptop, some combined integrated+PCIE graphics card combination or that you are simply not using DGVoodoo (or dxproxy)
Intel i9-14900HX
NVIDIA RTX 4070, 8 GB
32 GB RAM, 2 modules of 16GB of:
https://www.memorybenchmark.net/ram.php?ram=Samsung+M425R2GA3EB0-CWMOD+16GB&id=26241
KIOXIA XG8 SSD 1TB
Nothing is overclocked or undervolted. All stock.
Felgarr said: »
Worst case, and I hope this isn't true. But, you may be using an early Intel i9-13/14x00 series CPU that was recalled ~2 years ago due to some freezing/instability issues. (Intel extended the RMA period to 3 years too. In my case, they upgraded me for free from an i9-13900k to i9-14900k, but it took 2 weeks for me to buy the new CPU and 2 MONTHS to get reimbursed by intel. I sent an email every other week until they did it, but they're support guy was always responsive)
Felgarr said: »
0.) If this is a new PC build with 0-2 year old hardware, did you update your BIOS settings, device drivers (not just GPU) or check your manufacturer's release notes?)
Felgarr said: »
1.) Disable thermal throttling of your CPU/GPU (this is to observe if freezing happens at the same amount of time as your previous observations). You'll want to use a program like HWInfo64 to monitor System/CPU/GPU temps to make sure you're not throttling or freezing due to high temperatures.
Felgarr said: »
2.) Completely separate from #1, you can go to your BIOS and enable/disable low power states for your PCIE devices. This is to ensure that your GPU isn't entering a low-power state (called C-states) that FFXI doesn't know how to wake-up.
Felgarr said: »
3.) Odd question: Have you replaced or added any third party power or USB cables in your build. (I could tell you stories of how shotty cables from USB devices have suddenly caused blue screens and PC freezes).
Thanks for the ideas so far.
hi mihgo!
does it run loud/hot when playing ffxi? wish I remembered the specs for the Omen laptop I had that did pretty much the same thing. eventually it basically bricked and I never did pinpoint the problem, just took the L and got a new one.
does it run loud/hot when playing ffxi? wish I remembered the specs for the Omen laptop I had that did pretty much the same thing. eventually it basically bricked and I never did pinpoint the problem, just took the L and got a new one.
Kaffy said: »
hi mihgo!
does it run loud/hot when playing ffxi? wish I remembered the specs for the Omen laptop I had that did pretty much the same thing. eventually it basically bricked and I never did pinpoint the problem, just took the L and got a new one.
does it run loud/hot when playing ffxi? wish I remembered the specs for the Omen laptop I had that did pretty much the same thing. eventually it basically bricked and I never did pinpoint the problem, just took the L and got a new one.
Not particularly hot. The fans wind up every now and then in populated spaces, but I haven't seen CPU temps exceed 68C with FFXI. Moreover, I haven't found any correlation between fan activity and crashes. I'm as liable to crash in my mog house as Mhaura.
Felgarr said: »
1.) Disable thermal throttling of your CPU/GPU (this is to observe if freezing happens at the same amount of time as your previous observations).
2.) Completely separate from #1, you can go to your BIOS and enable/disable low power states for your PCIE devices. This is to ensure that your GPU isn't entering a low-power state (called C-states) that FFXI doesn't know how to wake-up.
2.) Completely separate from #1, you can go to your BIOS and enable/disable low power states for your PCIE devices. This is to ensure that your GPU isn't entering a low-power state (called C-states) that FFXI doesn't know how to wake-up.
OK I gotta Correct that:
on 1:
No need to run the risk by disabling Thermal Throttling. You can just read the state of the #Prochot flag. Since its an intel CPU realtemp can be used for this
#Prochot flag has 3 states.
- Not aktivated ( everything is fine)
- Activate (CPU IS currently over thermal Treshodl and is now running in lowest P-state)
- Logged (at some point since boot the the CPU was overheating
If BIdirectional Prochot is enabled another Device overheating can trigger the CPU to go into a overheating mode as wall. i do not believe the #Prochot Flag show any difference between which device cause the CPU to enter overheat mode.
on 2:
- PCIE power states does NOT adjust the GPU it adjust the PCIE
- Your GPU is not running in C-states but in D-states. (C-state are specific for you Main Processor)
- FFXI does not need to "know" anything about this. As it is handled by ACPI.
More details:
many time D-states of a graphics cards are linked to the L-states of the PCIE because its rarely needed to run without getting data over PCIE. However just like you can have Different P-states the Same C-states you can have different D-states under the same L-states
For CPU it goes pretty much likes this
G states > S states > C states > P states
In regards to who "overrides" what
For GPU you can argue this b
G states > S states > L states -> D states
How D state sere are more aking to C state above
https://www.intel.com/content/dam/doc/white-paper/pci-express-architecture-power-management-rev-1-1-paper.pdf
https://en.wikipedia.org/wiki/ACPI
@op
Do you have vsync enabled in Dgvoodoo ?
Do you have vsync enabled in Dgvoodoo ?
DaneBlood said: »
@op
Do you have vsync enabled in Dgvoodoo ?
Do you have vsync enabled in Dgvoodoo ?
alamihgo said: »
i9-14900HX
I have the i9-14900K/96GB RAM and 3090Ti (24GB). I'm fairly certain FFXI is freezing due to something (CPU, GPU) entering a low power state and not being able to be enter a higher power state as your computer's workload increases. I can be wrong about this theory, but laptop are you running on that has this CPU btw? (I didn't know it existed!)
Could you share screenshots of your DGVoodoo settings?
These are mine:
I have noticed that if I set VRAM to 2048/4096MB, I get crashes and instability. (Even with the LargeAddressAware patcher for POL.exe : https://github.com/ThornyFFXI/LargeAddressAware )
Do you have Power Savings settings like like hibernation enabled or your hard disks to be turned off for some reason?
Also, stupid question: Are you using any HD graphics mods in your FFXI setup? Do you still get crashes if you disable/don't load most of your addons and plugins?
Lenovo Legion 5. It's set to the "performance" mode currently—just in case anything was trying to hobble the CPU/GPU—but it was originally "balanced" when the issues began.
I use 2048MB VRAM on dgvoodoo, but I will try 1024 and see what happens. My dgvoodoo settings are otherwise identical to yours, except I have 4x anisotropic filtering. I will also set this to "app driven" to test.
All power save/sleep settings are disabled (HDD, Display, etc) in Windows as well as the manufacturer's software.
I don't use any HD replacers. I've already tried stripping addons and plugins down to the bare minimum of essential plugins and I still crash. One thing I could try is afk pure vanilla FFXI to see if it is a Windower-dependent crash, but that seems unlikely.
edit: LOL 1024MB in dgvoodoo fixed an FPS issue I had resigned to suffer forever:
https://www.ffxiah.com/forum/topic/58480/ffxi-stuttering-only-at-60fps/#3751510
So blessings of Altana on you, brother.
I use 2048MB VRAM on dgvoodoo, but I will try 1024 and see what happens. My dgvoodoo settings are otherwise identical to yours, except I have 4x anisotropic filtering. I will also set this to "app driven" to test.
All power save/sleep settings are disabled (HDD, Display, etc) in Windows as well as the manufacturer's software.
I don't use any HD replacers. I've already tried stripping addons and plugins down to the bare minimum of essential plugins and I still crash. One thing I could try is afk pure vanilla FFXI to see if it is a Windower-dependent crash, but that seems unlikely.
edit: LOL 1024MB in dgvoodoo fixed an FPS issue I had resigned to suffer forever:
https://www.ffxiah.com/forum/topic/58480/ffxi-stuttering-only-at-60fps/#3751510
So blessings of Altana on you, brother.
[+]
*** windows, do not mean to derail but was checking my dgvoodoo settings to compare and this happened just opening pol folder, not even the dgvoodoo exe
alamihgo said: »
Lenovo Legion 5. It's set to the "performance" mode currently—just in case anything was trying to hobble the CPU/GPU—but it was originally "balanced" when the issues began.
I use 2048MB VRAM on dgvoodoo, but I will try 1024 and see what happens. My dgvoodoo settings are otherwise identical to yours, except I have 4x anisotropic filtering. I will also set this to "app driven" to test.
All power save/sleep settings are disabled (HDD, Display, etc) in Windows as well as the manufacturer's software.
I don't use any HD replacers. I've already tried stripping addons and plugins down to the bare minimum of essential plugins and I still crash. One thing I could try is afk pure vanilla FFXI to see if it is a Windower-dependent crash, but that seems unlikely.
edit: LOL 1024MB in dgvoodoo fixed an FPS issue I had resigned to suffer forever:
https://www.ffxiah.com/forum/topic/58480/ffxi-stuttering-only-at-60fps/#3751510
So blessings of Altana on you, brother.
I use 2048MB VRAM on dgvoodoo, but I will try 1024 and see what happens. My dgvoodoo settings are otherwise identical to yours, except I have 4x anisotropic filtering. I will also set this to "app driven" to test.
All power save/sleep settings are disabled (HDD, Display, etc) in Windows as well as the manufacturer's software.
I don't use any HD replacers. I've already tried stripping addons and plugins down to the bare minimum of essential plugins and I still crash. One thing I could try is afk pure vanilla FFXI to see if it is a Windower-dependent crash, but that seems unlikely.
edit: LOL 1024MB in dgvoodoo fixed an FPS issue I had resigned to suffer forever:
https://www.ffxiah.com/forum/topic/58480/ffxi-stuttering-only-at-60fps/#3751510
So blessings of Altana on you, brother.
Nice! Let me know if the freezing persists (even if it's less frequent) or if a specific windower addon or plugin is giving you trouble and I can take a look it.
I had a good feeling, but then crashed in Norg at the moogles. :(
Got anything else up your sleeve?
Got anything else up your sleeve?
Do you see any other non-ffxi event logs of level critical/error/warning correlating with the crashes? And any particular spam or very high rate of other event logs regardless of severity level?
I manage a fleet of ~50 or so Lenovo Legion 5's used by designers/CAD software users, and they all went haywire last month.
This is not a prescribed fix for your issue- it's merely a testimonial of weird behavior seen on the Legion 5's and perhaps steering your research toward issues with that particular model might yield something. Maybe the issues are not unique to ffxi. The issue I faced we never actually got to the bottom of -why- it was happening, we were just so relieved to get past it as it was dozens of ours of time per week down the drain reinstalling windows as a temp fix before finding the real fix
I manage a fleet of ~50 or so Lenovo Legion 5's used by designers/CAD software users, and they all went haywire last month.
This is not a prescribed fix for your issue- it's merely a testimonial of weird behavior seen on the Legion 5's and perhaps steering your research toward issues with that particular model might yield something. Maybe the issues are not unique to ffxi. The issue I faced we never actually got to the bottom of -why- it was happening, we were just so relieved to get past it as it was dozens of ours of time per week down the drain reinstalling windows as a temp fix before finding the real fix
Interesting that you mention this.Nothing correlating specifically with the timestamp of the crashes, but it's interesting that you mention Windows Defender. There is a lot of WD activity, including unexpected terminations and restarts.
I'll look into this.
Aquatiq said: »
Do you see any other non-ffxi event logs of level critical/error/warning correlating with the crashes? And any particular spam or very high rate of other event logs regardless of severity level?
I'll look into this.
alamihgo said: »
I had a good feeling, but then crashed in Norg at the moogles. :(
Got anything else up your sleeve?
Got anything else up your sleeve?
I'm leaning towards a Lua add on being the reason. I would make a backup of you windower startup text file (I forget the name). Remove all of the Addons and see if you crash
alamihgo said: »
Intel i9-14900HX
alamihgo said: »
I am 95% sure only desktop CPUs were impacted, but it's entirely possible Intel was fibbing about that.
That's the Intel line, but plenty of people have reported instability with that processor. They're all manufactured with the same process before being cut and binned, so I wouldn't rule this out so quickly.
https://www.tomshardware.com/pc-components/cpus/intel-says-13th-and-14th-gen-mobile-cpus-are-crashing-but-not-due-to-the-same-bug-as-desktop-chips-chipmaker-blames-common-software-and-hardware-issues
They also acknowledged an allegedly separate issue with mobile CPUs. It feels like a PR line to me.
Anecdotally, we've seen the chip instability manifest within LuaJIT quite frequently on Ashita. I don't have a breakdown of why it happens more frequently within the Lua interpreter, but there might be commonalities with Windower there.
It's PR non-sense so they don't have to give refunds to corporate clients.
They're the same chips, the desktop CPUs just have features disabled in hardware.
They're the same chips, the desktop CPUs just have features disabled in hardware.
I also get random crashes time to time also, sometime the game will freeze for 1-2 secs and return to normal.
Shiva.Thorny said: »
alamihgo said: »
Intel i9-14900HX
alamihgo said: »
I am 95% sure only desktop CPUs were impacted, but it's entirely possible Intel was fibbing about that.
That's the Intel line, but plenty of people have reported instability with that processor. They're all manufactured with the same process before being cut and binned, so I wouldn't rule this out so quickly.
https://www.tomshardware.com/pc-components/cpus/intel-says-13th-and-14th-gen-mobile-cpus-are-crashing-but-not-due-to-the-same-bug-as-desktop-chips-chipmaker-blames-common-software-and-hardware-issues
They also acknowledged an allegedly separate issue with mobile CPUs. It feels like a PR line to me.
Anecdotally, we've seen the chip instability manifest within LuaJIT quite frequently on Ashita. I don't have a breakdown of why it happens more frequently within the Lua interpreter, but there might be commonalities with Windower there.
alamihgo said: »
Shiva.Thorny said: »
alamihgo said: »
Intel i9-14900HX
alamihgo said: »
I am 95% sure only desktop CPUs were impacted, but it's entirely possible Intel was fibbing about that.
That's the Intel line, but plenty of people have reported instability with that processor. They're all manufactured with the same process before being cut and binned, so I wouldn't rule this out so quickly.
https://www.tomshardware.com/pc-components/cpus/intel-says-13th-and-14th-gen-mobile-cpus-are-crashing-but-not-due-to-the-same-bug-as-desktop-chips-chipmaker-blames-common-software-and-hardware-issues
They also acknowledged an allegedly separate issue with mobile CPUs. It feels like a PR line to me.
Anecdotally, we've seen the chip instability manifest within LuaJIT quite frequently on Ashita. I don't have a breakdown of why it happens more frequently within the Lua interpreter, but there might be commonalities with Windower there.
When did your purchase the laptop?
What's your current BIOS version? I'm genuinely curious as there were 3-4 BIOS updates (microcode updates) LAST YEAR for this issue. I suspect it's gotten better.
Edit: I need your laptop model number, there's like 20 different Lenovo Legion 5 model numbers
All FFXI content and images © 2002-2025 SQUARE ENIX CO., LTD. FINAL
FANTASY is a registered trademark of Square Enix Co., Ltd.