FFXI crashes windows

[RAIST]

or it could be corrupted indexes/sectors on the hard drive too. Could try running a chkdsk /F or /R on the drive that FFXI is installed on:

****NOTE: THIS IS FOR XP...VISTA/WIN7 USE A DIFFERENT DISK CHECKING UTILITY

Start/Run, and enter CMD in the box and hit <ENTER> to open a DOS window.

Then type the appropriate command, "chkdsk C: /F" or "chkdsk E: /F" followed by <ENTER>.

(/F is faster, but it doesn't check the sectors, just the files for corruption. /R checks sectors also, so you could run with /R instead of /F for a more thorough check if you like).

By running it in the DOS window like that, you will see the results when it finishes if it doesn't require a reboot to run. If the drive is flagged as a system drive (C: will be because that is what Windows is on, E: could be also if there is something it needs to access in real time like part of the swap file, etc.), it will prompt you to run it on reboot. If so, let it schedule it and then restart the system. If running on reboot, you will need to keep an eye on the messages while it runs. Just as it finishes it will state if it found errors or not (may go by real fast if running on reboot). If it found errors, run it again until it doesn't report it found errors. If you missed the message at the end, run it again just to be sure.

***Note: You may see the progress indicators go back and forth during the process (count up to 80%, then drop back to 55%, etc.). This is normal for it to do this. If by chance it is unable to correct all errors on the drive during a reboot, it may run it again the next time you reboot--so, it is kind of idiot proof in that regard...eventually it should fix all the errors after it reboots a few times.

If after several passes it is still being marked as "dirty" and running the check with each reboot, you potentially have some problems with sectors on the drive and will need to run it with the /R command to check all sectors and try to recover data. This is the only way to make it reset that dirty bit and ultimately stop the check on reboot--but it might take a few passes to fix everything. If this is the case, you would be better off booting from the installation CD (if you have one) and going into Recovery Console to run the commands there until it stops finding errors.

[Gyeff]

chkdsk C: /F came out clean.

I had recently reformatted my computer btw.

[brawly]

I am having the same problem as Gyeff, the exact same problem. And I think I found your post on Nvidia forums Gyeff so I am just going to copy/paste what I typed there. I didn't find any solution as of yet BUT I haven't tried some of the suggestions in this topic. I'll give them a try and see what happens. Here is the link to the Nividia forum that I believe Gyeff posted there. [URL="http://forums.nvidia.com/index.php?showtopic=218804&st=0&gopid=1355347&#entry1355347"]

Here is what I posted on the Nvidia site:

"My system is doing that exact same BSOD in the same area within FFXI (Buburimu Peninsula, near the outpost). The only Difference is I am running the Nvidia GeForce 7900 GS, I have updated the drivers for the video card as well as uninstalled and install older drivers, it didn't work. I reinstalled the up-to-date driver since the older driver(s)didn't work. Looking in the Computer Management window under the event viewer:system, the event(s)had listed 1003 and 1001 (which after a little digging said would accompany the error event)with the associated BSOD.

This is the save event logs:
Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 1/9/2012
Time: 2:46:37 PM
User: N/A
Computer:
Description:
Error code 1000008e, parameter1 c0000005, parameter2 bd1bbc62, parameter3 b1b8daf4, parameter4 00000000.

For more information, see Help and Support Center at http://go.microsoft....ink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 38 1000008
0020: 65 20 20 50 61 72 61 6d e Param
0028: 65 74 65 72 73 20 63 30 eters c0
0030: 30 30 30 30 30 35 2c 20 000005,
0038: 62 64 31 62 62 63 36 32 bd1bbc62
0040: 2c 20 62 31 62 38 64 61 , b1b8da
0048: 66 34 2c 20 30 30 30 30 f4, 0000
0050: 30 30 30 30 0000



Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 1/9/2012
Time: 2:45:33 PM
User: N/A
Computer:
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0xbd1bbc62, 0xb1b8daf4, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini010912-06.dmp.

For more information, see Help and Support Center at http://go.microsoft....ink/events.asp.

I tried everything I could think of and every suggestion I could find on the innterwebs. My computer skill is somewhat lacking but not horrible. Any help would be much appreciated since I must be overlooking somethings."

Anyway I am going to try some of the suggestions here and see what happens.