Maintenance for the week of July 21:
• PC/Mac: NA and EU megaservers for maintenance – July 21, 4:00AM EDT (8:00 UTC) - 12:00PM EDT (16:00 UTC)
• Xbox: NA and EU megaservers for patch maintenance – July 23, 6:00AM EDT (10:00 UTC) - 12:00PM EDT (16:00 UTC)
• PlayStation®: NA and EU megaservers for patch maintenance – July 23, 6:00AM EDT (10:00 UTC) - 12:00PM EDT (16:00 UTC)

SOLVED 64 bit crash at login

Lewandowsky
Lewandowsky
✭✭✭
I am trying to act in good faith and made several attempts at fixes already, so forgive me if 1) there is a more appropriate thread (I looked and they weren't exactly applicable or were probably too old so far as I can tell), I haven't provided all necessary information (spent some time looking for what to include), I shouldn't be worrying about this yet because support isn't total for 64-bit yet (I looked and I thought we're not supposed to have to wait for DB for this to work), or otherwise generally screwed up. 32-client runs (relatively) great.

64-bit client crashes on login. Every time. Exact spot. I'd like to get it running because I bought a new system in large part because my last one couldn't have graphics upgraded (yeah it was an old Macbook) when DirectX support changed recently, and I ended up spending a few bucks on a nice system. I'd like to take full advantage of it. I kind of expected to be able to.

Fixes I've tried:
Waiting for various patches (I've had this problem since I bought the computer 3/2016)
Running the executable directly from the file itself rather than the desktop shortcut I made for the 64-bit client
Downloaded latest C++ per ZOS instructions.
Deleted usersettings.txt
Un-installed and re-downloaded all of the program. All of it.
Removed all add-ons (I do not get to the point where I can disable them, because I crash before character-select, but I tried deleting the whole folder anyway)

Crash info:
It's too long to include in message body, see attached file for crash report. I always "submit" the crash report BTW.

System info:
Attached as file (it seems I can't attach multiple files, so the system info report follows the crash report, separated by horizontal line)

Game consultant info:
Attached as file (it seems I can't attach multiple files, so the game consultant info follows the system info, separated by horizontal line - this is the last section)

If the combined crash, system, and game consultant info gets me berated for not having enough details, have mercy on me. I'd really like to get this working to its full potential, and I get the sense forums can be more helpful than ZOS itself.
Edited by Lewandowsky on May 30, 2016 11:37PM
  • Turklertc
    Turklertc
    Soul Shriven
    I´ve the same problem :/ EU
  • Nestor
    Nestor
    ✭✭✭✭✭
    ✭✭✭✭✭
    I have not tried the 64 bit for a while due to the sound issues, but when I did use it, it as stable and performed well, other than the sound issues. So, this will be some maddening issue that only some machines have and not others.

    Now, I notice you have an Asus Mobo. Asus has two programs that are, or were, known problems for games, in particular Bethesda Games. GamerOSD and Xonar. The first allows you change the screen resolution on the fly among other things, and the Xonar is mostly for enhancing surround sound, something this game does not need at all. Try disabling those programs and see what happens. Your not uninstalling them or anything, just follow the clean boot procedure to stop them from loading with Windows

    https://support.microsoft.com/en-us/kb/929135

    This process is totally reversable.
    Enjoy the game, life is what you really want to be worried about.

    PakKat "Everything was going well, until I died"
    Gary Gravestink "I am glad you died, I needed the help"

  • Lewandowsky
    Lewandowsky
    ✭✭✭
    Nestor wrote: »
    I have not tried the 64 bit for a while due to the sound issues, but when I did use it, it as stable and performed well, other than the sound issues. So, this will be some maddening issue that only some machines have and not others.

    Now, I notice you have an Asus Mobo. Asus has two programs that are, or were, known problems for games, in particular Bethesda Games. GamerOSD and Xonar. The first allows you change the screen resolution on the fly among other things, and the Xonar is mostly for enhancing surround sound, something this game does not need at all. Try disabling those programs and see what happens. Your not uninstalling them or anything, just follow the clean boot procedure to stop them from loading with Windows

    https://support.microsoft.com/en-us/kb/929135

    This process is totally reversable.

    Thanks for the tip. Followed the instructions, disabled all non-microsoft services and the all the startup processes. Turned out that made my network inaccessible, so tried it again disabling everything that was not Microsoft or Intel. Unfortunately no appreciable change in the 64-bit crash. Not something I would've known to try on my own though so this is good. You or any other reader have any other ideas?
  • Lewandowsky
    Lewandowsky
    ✭✭✭
    Help ticket likely to be helpful at this point?
  • ZOS_DaryaK
    ZOS_DaryaK
    admin
    I would definitely recommend you submit a ticket to our support team and be sure to include your game consultant.
    The Elder Scrolls Online: Tamriel Unlimited - ZeniMax Online Studios
    Forum Rules | Code of Conduct | Terms of Service | Home Page | Help Site
    Staff Post
  • Lewandowsky
    Lewandowsky
    ✭✭✭
    Turklertc wrote: »
    I´ve the same problem :/ EU

    So a couple of things.
    Thank you ZOS for being responsive to my ticket. I was publicly condescending, and I was wrong. I do not in fact meet the minimum requirements, because my video card is a NVIDIA 960M. The M is a problem. Maybe I'm the only one that didn't know; I am a lay person when it comes to tech, and I believed when I got this new system it was a good one - something I could take with me to game with when I work out of town. Newer Republic of Gamers machine. This system isn't officially supported by ESO or Witcher 3 that I was considering buying because it is a M-designation card. I am horribly disappointed and the fault is mine. Yes I am <insert derogatory terms>. No excuse.

    HOWEVER-

    There may be something of a work around - but not quite a fix. I guess my rig is actually decent if not officially supported? I guess? So there might be little fixes here and there. So if you're having a similar problem and are using a laptop or know you are using a mobile (M) card try this or an equivalent if you're having similar crashes:
    Open NVIDIA control panel
    Manage 3D settings
    Global settings
    High performance NVIDIA Processor (rather than auto)
    Apply

    Doing this I am able to get past the login to character select! I don't know what will happen after. Kinda crazy that the computer doesn't figure the graphics processor to use was the NVIDIA rather than integrated when running ESO? I don't entirely understand. I'll post an update in a while about whether this runs smoothly or not with some periods of play.
  • Nestor
    Nestor
    ✭✭✭✭✭
    ✭✭✭✭✭

    Doing this I am able to get past the login to character select! I don't know what will happen after. Kinda crazy that the computer doesn't figure the graphics processor to use was the NVIDIA rather than integrated when running ESO? I don't entirely understand. I'll post an update in a while about whether this runs smoothly or not with some periods of play.

    Let me explain what happened. Fortunately, you now know how to fix this.

    Laptops, and most desktop PCs want to default to the CPU graphics and not the graphics card. The system is supposed to trigger to use the 3D if you launch a game, but, a lot of games start out in 2D, with the splash screens, so the system never knows to use the graphics card instead of the CPU. You have to force the system to either use the 3D card exclusively, or use the Nvidia Control panel to force operation with certain games.

    Just remember this for any other games that won't launch properly.

    Enjoy the game, life is what you really want to be worried about.

    PakKat "Everything was going well, until I died"
    Gary Gravestink "I am glad you died, I needed the help"

  • Lewandowsky
    Lewandowsky
    ✭✭✭
    OK I have marked this as solved.

    I have been able to run the 64-bit on that system for several hours and it went pretty smoothly, no crashes just the well-described bursts of static and environment noise.

    Problem was indeed that the system was trying to use "integrated graphics" rather than the graphics card. ZOS to their credit was very responsive; though they told me they couldn't actually offer trouble shooting because the 760M didn't technically meet system requirements (because of the M - seems to be common and I'm kinda of surprised, but then I'm a tech lay-person), they did offer general ideas about how to make sure the system was handling this properly, and that advice DID include the fix. So thank you ZOS. Not ideal but it's working and ZOS gets a point in the responsive and helpful column.

    Thanks for the ideas and help guys. If you are encountering a crash after log-in as I described, check how NVIDIA is running graphics for this problem, and that the GPU is designated.
Sign In or Register to comment.