FFXI crashes windows

Haha! I fixed the problem. It was so simple, I wonder why I didn't think of it sooner. I went into nvidia control panel and changed application specific settings specific to FFXI. By default it has Aniosotropic filtering off, Antialiasing off, Antianaliasing-transparency off, Texture filtering-Aniosotropic filter optimization off and Vertical sync off.

I made most of those settings application controlled or on. I'm not sure which exact setting fixed it as those big words mean nothing to me :p

Nevermind, the problem is back again. It appears that the source of the complication is when my game tries to load the Windurst Outpost guards/ Banner. The problem appeared to go away when Sandoria was controlling Buburimu Peninsula.

Can someone tell me how I can fix this issue?

Quote:

---

Originally Posted by Gyeff

Nevermind, the problem is back again. It appears that the source of the complication is when my game tries to load the Windurst Outpost guards/ Banner. The problem appeared to go away when Sandoria was controlling Buburimu Peninsula.

Can someone tell me how I can fix this issue?

---

Try check files from POL, I wonder if the npc dats for that specific zone are corrupt, If I knew how i'd suggest removing those dats and forcing pol to check all files and redownload just those dats, my friend had a similar issue with the new holiday pants and ulhuadshi after the last patch.

Btw, this time I'm not stuck at Buburimu Peninsula. I'm now stuck right by the outpost in West Sarutabaruta. The Windurst outpost guards or Windurst banner won't load for me, that's what's probably causing the issue.

Again, when I was stuck in Buburimu Peninsula the issue was resolved when Sandoria captured the area, the Sandoria Guard NPC and banner loads properly.

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.

chkdsk C: /F came out clean.

I had recently reformatted my computer btw.

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.

Kernel Mode Exception errors (8e errors) are some of the worst buggers to nail down. The error message really doesn't give much to go on....all you can really be certain of is a driver crashed for some reason. With nVidia there was a known issue with the infinite loop bug, so that is usually the first thing eveyone looks at is the nVidia driver. With ATI, it was issues with the Overdrive in the CCC that sometimes caused issues. But...it could be a number of issues:

You could have a hardware fault due to overheating....or just plain worn out hardware. First there is the obvious stuff that leads to overheating--overclocking, improper voltage settings, poorly mounted cooling devices, or poor ventilation. Get in there and make sure your heatsinks are seated well, fans are working properly, clean out the dust bunnies (get that caked on lint off your heatsinks!!). This can be a bit of a tedious task, but one that should be done periodically, especially if your system has a little age on it. If you've been overclocking or running manual settings to tweak out your system, try undoing them and running on "safe" settings to see if the problem goes away, or at least diminishes. This can be a strong indicator of a hardware related issue versus something in software.

Running CHKDSK or ScanDisk tools to test your drive integrity is always a good idea too, as that is a common point of failure (sectors simply get weak over time, can have crosslinked files, all kinds of snafus in the file system). This is another task that should be done periodically regardless--sometimes data just glitches on shutdown or even during normal write operations. I don't mean run one every week or something, but a few times a year is a good idea for most regular users. If you are having abrupt shutdowns and stop errors, this should definately be done after the problem has been cleared up, as you may have some data corruption in the file system.

Another one to focus on is your actual memory chips. You would be surprised how many times people get cards that go bad early on but never catch the problem because the faulty cell is simply never touched....then one day, under heavier load, the system tries to read/write/refresh a flaky cell, and BSOD. memtest86 is a good tool for testing memory. It's a free download, various formats. The easiest one is the bootable CD image that you use to burn a CD. This isn't the only tool, it's just a popular diagnostic tool. Methods vary.... some will test each chip individually, while others will test in pairs (for the dual-link boost) and swap out chips until they find the bad one. Another one some like is Prime95 for stress testing, as it can be configured to pretty much target just stressing your CPU, then expanding out to different levels of your memory susbsystems (L2/L3 caches, main memory, and eventually your swap file). The documentation on it can be a bit overwhelming, but there is a pretty simple guide that walks you through just what you need to know and do to stress test with it here. This specifically shows how to hammer just your CPU and it's onboard cache, but if you read the window where you set the small FFT, it explains what happens when you select the larger sample sizes (larger samples stress more parts of your system).

Then...there is the dreaded Software related stuff. First and foremost, scan the $h!t out of your system. Virus Scan, Malware Scans--run the full battery. Malwarebytes.org has a great free on-demand scanner that has a great track record for removing malicious stuff. Many paid-for applications will point people to this software if there are signs of infection that are proving difficult to remove/recover from. Sometimes malicious software creates conflicts with drivers because they try to access the locked memory (one thing that leads to various kernel mode exception errors). So, make sure your system is clean.

***NOTE: there have been some documented issues with various security software in the past. Not to single out Symantec specifically on this point....but I know from personal experience that an older version of Norton AV had an issue with it before, as well as Adaware. So, if you recently had software get updated, this could be part of your problem. It should also be noted that Microsoft itself has screwed this pooch several times before as well. If you got Windows Updates about the time the problem showed up, you might need to try rolling back updates or checking for new updates to fix something that the last update may have broken (this tends to be a trend with Microsoft).

You may simply have a conflict with another driver on your system. Your error message may be referencing a specific driver--that does not necessarily mean THAT driver is the culprit, just that the error occurred when that driver was taking action. Common offenders in this category are the things that are more like "standby" things that only kick in for specific events (drivers to support drive image backups like PowerQuest or Ghost, Security Software update utilities, systray apps that monitor temps and adjust fan speeds and such). Might be worth it to go through and disable devices/services/apps you don't need to have running in the background to see if the problem persists. If so, then start to enable them one at a time until the problem comes back...then see if you can get an update for that product. Common offenders in this category can be problematic, as they can still be things you need for gaming--things like environmental audio support for your soundcard (EAX extensions for Asus/Yamaha/Realtek soundcards...even the Creative Audigy lines of cards have caused problems in the past). Sometimes it isn't the drivers themselves, but the tools used to configure the devices (systray apps for sound or video cards, etc.). So, sometimes you have to really strip a system down before you find the program causing the problem.

Obviously, if you have recently updated drivers/applications related to your video/sound....may need to try rolling back. Note, this can be an application not specific to your video/sound card...it could be something easily overlooked like Cyberlink PowerDVD, or even Windows MediaPlayer or something that might be loading a filter or something in the background you are unaware of---so if anything recently updated or got installed, need to look closely at that. It could even be your Wireless Connection Utility, or your netword card's driver causing an issue. Pretty much, when it comes to it being a driver issue, just about anything goes. So, if you don't NEED the device and/or utility while gaming, try disabling it to see if it helps. If so, try a different driver or utiltiy to manage it. Sometimes (though it is rare) it can even be a BIOS problem with your motherboard....so may be worth it to update your BIOS even (always get a backup of your current BIOS though for safety sake, either by dumping it with the update utility or download your current release as well as the newer one).

Thanks Raist, the help you offered in this topic help resolved the problem. What I did was chkdsk /R for both of my drives. After that was done I went and got the driver that SE listed as the "OK" driver for the geforce 7 series (which when I think about it I must not have tried), I guess I was just overlooking that specific driver.

Before I tried that driver, I did do a bios update/memtest86/update drivers for sounds card/tested to see if it was an overheating problem.

Thanks Again Raist for the suggestions and the link to the driver website.

I recently returned to this game as would crash every time I faced a Windurst outpost/banner/border guard. I changed my driver to the SE recommended driver for my Nvidia card 6800 and OS (Windows XP) and it worked like a charm. Scroll down to find yours:

http://www.playonline.com/ff11us/env...tml?pageID=win