Log in

View Full Version : Game Crashes on Main Character...



MaiMizzu
08-23-2011, 01:22 AM
Please help.

This is a problem I had rarely before yesterday, but now it's continous. Usually restarting my comp solved the problem.. but not this time.
When I try to log into my main character, the game crashes. This is the error report:

Problem signature:
Problem Event Name: APPCRASH
Application Name: pol.exe
Application Version: 1.18.13.0
Application Timestamp: 4dc3b714
Fault Module Name: igdumd32.dll
Fault Module Version: 7.15.10.1666
Fault Module Timestamp: 49a6effc
Exception Code: c0000005
Exception Offset: 00004d25
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 1033
Additional Information 1: fd00
Additional Information 2: ea6f5fe8924aaa756324d57f87834160
Additional Information 3: fd00
Additional Information 4: ea6f5fe8924aaa756324d57f87834160

I can't get around this. So I thought. On a whim, I tried logging into one of my spare characters, and I had no problem at all. I had all the functionality and graphics effects I normally had. I tried logging into my main character again, and the game crashes every time.

How can I solve this? I have the latest drivers for all.. the dll mentioned is connected to the intel graphics chipset I have.
I don't know if it'd help, but if I could even get someone to homepoint my main character, I dont know if that would help or not.

Thank you in advance for your assistance in this.

Talmar
08-25-2011, 04:54 AM
As of August 23rd, I am having the same issue. It happened as I was teleporting to Valkurm Dunes via Horst in Port Jeuno. The character select screens shows that I am in Valkurm however if i attempt to log in, FFXI and POL both crash. Logging into my mule character works just fine.

I'm not sure if this is a related issue as well but, about an hour or so earlier, I was attempting to outpost warp to Beaucedine Glacier via Jeanvirgaud in Northern San d'Oria. I'm used to certain NPCs not loading from time to time. Normally if I run far enough away and come back, zone and zone back in or log out then log back in the issue normally fixes itself. This time it didn't however.

If someone could help me with this I would be eternally grateful.