Computer reboots near Conquest Overseer NPCs

[Ordo]

Thread Title:
Whenever I am close enough to a Regional Conquest Overseer NPC's location (either outpost or border guards) for the NPC to load and be targetable, my PC reboots. I just recently returned to the game after several years away, and I did not have this problem when I played previously.

Details:
- I've tested this problem by going near multiple Conquest Overseer NPCs, and it happens near each of them.
- When I try to log back in, the crash/reboot occurs within 1 to 2 seconds after the black loading screen.
- I am able to approach, talk to, etc. Conquest Overseer NPCs just fine on my laptop, so I can log back in on my laptop just fine to move my character away.
- Interestingly, this problem does not occur with the overseers in cities (at least in Windurst, I haven't tested the other cities yet).
- I thought it might be a corrupted .dat file, so I tried using the Check Files utility (no problems found) and completely re-installing the game. Neither solved the problem
- I've also updated my video card driver.

Some other players have posted about similar problems:
http://forum.square-enix.com/ffxi/th...-Outpost-Crash
http://forum.square-enix.com/ffxi/th...y-my-main-char

In both cases, it doesn't look like they were able to fid a solution.

Steps:
- Whenever I approach an outpost or border Conquest Overseer NPC location, my computer reboots.

Date & Time:
Multiple times over the past 3-4 days as I've tried to solve the problem.

Frequency:
Always when I approach the locations of these NPCs, or attempt to log in nearby.

Platform:
PC

PC Specs:
Intel Pentium D 3.00GHz CPU
2 GB RAM

Operating System:
Windows XP Pro SP3

Graphics Card:
NVIDIA GeForce 6600

ISP:
Comcast

Type of Internet Connection:
Broadband cable.

Hope that someone can help, this is pretty frustrating as the Conquest Overseers are pretty important NPCs... and I'd rather not have to run the game on my laptop just to get signet and use the outpost teleports.

Also, before anyone suggests that I open certain network ports, I can say fairly confidently that that is not the issue here, as I do not encounter this problem on my laptop that is connected to the same network through the same router and modem.