Platform: Windows 7
ISP: Charter Communications
Type of Internet Connection: Cable
Internet Connection Speed: 40 Mbit/second
Frequency: Sometimes
World: Leviathan
Occurance 1
Date & Time: May 17, 2014 - 7:25:45.068 PM EST
Character Name: Dshsb
Race: Tarutaru M
Main Job: Geomancer
Support Job: Red Mage
Area and Coordinates: Yorcia Weald (U), the winding path leading past the first blockage toward Ironbeak Inguza's normal spawn point
Party or Solo: Alliance
NPC Name: Luopan
Monster Name: Podarge
Steps: Upon Luopan death, client crashed.
Occurance 2
Date & Time: April 30, 2014 - 1:41:07.380 AM EST
Character Name: Slothface
Race: Tarutaru M
Main Job: Summoner
Support Job: Scholar
Area and Coordinates: Stellar Fulcrum, BCNM Arena #1, East Wall
Party or Solo: Party
NPC Name: Titan
Monster Name: Kam'lanaut
Steps: Upon releasing Titan, client crashed.
Occurance 3
Date & Time: April 30, 2014 - 2:35:04.973 AM EST
Character Name: Dshsb
Race: Tarutaru M
Main Job: Geomancer
Support Job: Red Mage
Area and Coordinates: Buburimu Peninsula, F-7, roughly 40 yalms from G-7 facing east on the main walkway
Party or Solo: Solo
NPC Name: Luopan
Monster Name: N/A
Steps: Upon using full circle, client crashed.
Occurance 4
Date & Time: April 29, 2014 - 5:14:48.681 PM EST
Character Name: Slothface
Race: Tarutaru M
Main Job: Summoner
Support Job: Scholar
Area and Coordinates: Stellar Fulcrum, BCNM Arena #1, East Wall
Party or Solo: Party
NPC Name: Titan
Monster Name: Kam'lanaut
Steps: Upon Titan's death, client crashed.
Upon attaching a debugger, the crash was caused by a TEST operation on a calculated DWORD that appears to be adding an offset to a NULL value. The stack trace went through several functions in graphics driver DLLs. The disassembly is as follows:
0F2221D4 test byte ptr [eax+198h],4
When this crash occurs, eax always has a value of 0, resulting in a memory operation on a value that is far out of FFXI's memory space, being simply the offset. An access violation error is thrown, at which point the client will hard crash. Players on my server have confirmed this issue is also present on Xbox-360, and many are effected. This issue first began after the April 8 version update.
This adjustment seems to be the most likely candidate for the creation of the bug, as it deals directly with pets and effects. If there's any more information I can provide to be of help, I'd be glad to do my best. This bug has made it impossible for me to use my Geomancer in endgame content, and the last report of it was moved to 'insufficient information' without so much as a response.The Effects section of the Config menu has undergone the following adjustments.
-Battle effects for one's pets are now included under "You."
-Battle effects for party members' pets are now included under "Party."