Results 1 to 10 of 179

Hybrid View

  1. #1
    Player
    Ephemeris's Avatar
    Join Date
    Jun 2017
    Location
    Ul'dah
    Posts
    7
    Character
    Ephemeris Til'elrin
    World
    Ragnarok
    Main Class
    Ninja Lv 60
    Quote Originally Posted by Aladire View Post
    Guys, I had this issue over a year ago with a newly built computer. Please, let me summarize things of what to do. I want to let you know that if adjusting settings does not resolve stuff, then you have a defective part(s), which can also be hard to troubleshoot. The reason that the game tends to have the trouble is that most of the time you are not using most of the hardware power till you run games like this. So, here are the steps:

    1. Check to make sure there are no hardware issues in the event view under windows.
    2. Reinstall the graphic drivers with a CLEAN install. This will wipe any profile such as SLI settings.
    3. Check to make sure that DirectX is updated. An earlier post of mine talked about this. (Windows 10 gets them through windows update, but may need to manually trigger for DX9 and DX11.)
    4. If you are missing the .Net Framework 3.5 and the latest, install those. Again, an earlier post of mine explained how.
    5. Make sure that all of the windows updates are installed. Some of them fix issues with the windows settings while others fix security vulnerabilities. Few actually add or change features.
    6. For windows 10 users, try disabling the windows 10 gaming mode. (This will only be an option with windows 10 build 1703 or later, which currently is the creator update.) You can find more info at this link: http://gadgets.ndtv.com/games/featur...ows-10-1680332
    7. Reinstall the game if still issues.

    Now, if after all steps above have been done and still crashing, then some more extreme tech settings will have to be done. Be very careful with what I am about to suggest as these steps are typically used by those who overclock their systems. You do not want to set things too high that will cause overheating and damaging hardware. If you are too scared to do this, ask someone who knows how to. That being said, adjust these settings: (Do these one at a time to see if any of these help. If not fix, set the settings back and try the next step.)
    1. In the BIOS, adjust the voltage level to the PCI Express/Graphic card by a very small percentage such as 0.5 volts. Go a little higher or a little lower.
    2. In the BIOS, adjust the voltage level of the RAM, again go only about 0.1 volts or even 0.2 volts.
    3. In the BIOS, adjust the CPU Ratio to 1 setting difference.
    4. In the BIOS, adjust the CPU Voltage by the lowest increment of only 1 step. (I am not sure what the change amount is here.)

    If all of these steps still do not resolve the issue, then:
    1. Do a reset of the BIOS settings.
    2. Then make sure you have the latest BIOS firmware installed.
    3. Then, go in each setting for the RAM and CPU and make sure that everything is set to the correct setting, such as the latency and DRAM Timing. Sometimes the BIOS fails to pick up the profile.

    Now, if after all of these steps and still getting errors, I am sorry to say this, but this is confirmation that a hardware is failing. It will be either the PSU, Motherboard, CPU, or graphic card, or multiple at once. You will have to start troubleshooting which component is failing. To be honest, this is usually rare if the computer has been working for more than a year. So, I am hoping it is not this case.
    You did not have this issue, nor are your posts helpful. They are taking the topic away from the problem and placing blame on the user.

    It would be great if you would stop wasting people's time and making them spend hours on unnecessary legwork just to confirm that this is indeed a FFXIV problem, and as someone else said stop giving the SE staff who are at forums the impression that this is somehow easily resolvable and our fault.

    If any of this was a hardware issue as you claim, it would:

    1. Be present in every other modern game that either used DX11 or utilized computer resources to a high degree.
    2. Result in BSODs or restarts rather than game crashes and DirectX errors.
    3. Would not happen to so many users with identifiable similarities.

    We are all playing other MMOs and other games with no issues at all.

    This is a driver problem with this specific game and the fix has to come from either AMD or the developers, as was confirmed in the past. The drivers that were stable and worked flawlessly were the ones where AMD specifically addressed it and documented it in the patch notes.

    Under any circumstance, do not fiddle with your voltage settings nor BIOS if you don't have an advanced understanding of hardware. Your computer does not need tweaking on such a low level in order to function properly, and you can seriously damage it to the point of it not working.
    (3)

  2. #2
    Player
    Aladire's Avatar
    Join Date
    Aug 2013
    Location
    IL
    Posts
    259
    Character
    Cron Job
    World
    Malboro
    Main Class
    White Mage Lv 80
    Quote Originally Posted by Ephemeris View Post
    You did not have this issue, nor are your posts helpful. They are taking the topic away from the problem and placing blame on the user.

    It would be great if you would stop wasting people's time and making them spend hours on unnecessary legwork just to confirm that this is indeed a FFXIV problem, and as someone else said stop giving the SE staff who are at forums the impression that this is somehow easily resolvable and our fault.

    If any of this was a hardware issue as you claim, it would:

    1. Be present in every other modern game that either used DX11 or utilized computer resources to a high degree.
    2. Result in BSODs or restarts rather than game crashes and DirectX errors.
    3. Would not happen to so many users with identifiable similarities.

    We are all playing other MMOs and other games with no issues at all.

    This is a driver problem with this specific game and the fix has to come from either AMD or the developers, as was confirmed in the past. The drivers that were stable and worked flawlessly were the ones where AMD specifically addressed it and documented it in the patch notes.

    Under any circumstance, do not fiddle with your voltage settings nor BIOS if you don't have an advanced understanding of hardware. Your computer does not need tweaking on such a low level in order to function properly, and you can seriously damage it to the point of it not working.
    Fine. I will stop trying to help the people in this thread.

    Just for your information, here is what my issue was and you can tell yourself if it is the same issue:
    My computer did not crash. I did not get any BSOD as you say.
    My monitor would occasionally go blank and then recover. I would see an error message, sometimes but not all the time, that my graphic drivers have stop responding and restarted successfully.
    I would get a crash of the game and error 11000002 thrown.
    The game would work fine in DX9. It was only crashing in DX11.
    This was on Windows 10 before the anniversary update.
    It was only one 1 of my computer, which has all new parts. My old desktop was fine and was not crashing on DX9 or DX11.
    At the time, I was using Nvidia GeForce 680.
    The error happens mostly when I am in a dungeon or in Iddyllshire. Rare did it happen when I was alone outside of towns.
    The error happens randomly where sometimes I would be able to play for hours while other days I could play about 2 mins.
    It was only happening in FF14 while WoW ran perfectly fine.

    So, if this does not describe what is happening, then I must be reading a different thread.

    Just so you know, just because there is a problem with hardware does not mean you would get BSOD. Sometimes a hardware problem can present itself in crashing drivers. I know this from the 16 years I have been building and repairing computers as well as providing tech support to others. I even work as one for a little over a year.
    (0)