Maintenance for the week of March 25:
• [COMPLETE] ESO Store and Account System for maintenance – March 28, 9:00AM EDT (13:00 UTC) - 12:00PM EDT (16:00 UTC)

Official Feedback Thread for 64-bit Client

  • Docmandu
    Docmandu
    ✭✭✭✭✭
    Guess the exe packer doesn't like >win7 64-bit systems.
  • Wolfster
    Wolfster
    ✭✭✭
    I just posted this on the patch notes thread but I'm gonna shamelessly repeat it here:

    Yesterday's version of the 64bit Mac client ran beautifully (30+ fps), today's is running at an average of 5 fps. Altering graphics settings is having no effect - same on minimum and maximum settings.

    2.4Ghz i7 (quad core)
    8Gb memory
    GeForce GT 650M 1024Mb
  • KhajitFurTrader
    KhajitFurTrader
    ✭✭✭✭✭
    ✭✭
    Wolfster wrote: »
    Yesterday's version of the 64bit Mac client ran beautifully (30+ fps), today's is running at an average of 5 fps. Altering graphics settings is having no effect - same on minimum and maximum settings.
    I haven't noticed any drastic change in performance after logging in today, but virtually the first thing I always do after a patch hits is to reset the Video Settings to their defaults, by pressing [X] in the corresponding menu. Then I set them back to ultra-high quality, and at my iMac's resolution of 2560x1440, I got the same FPS as before, as far as I was able to tell (20-25 FPS outdoors, but I won't probably use these settings on live later on).

  • Marques
    Marques
    ✭✭✭
    Concerning the bug with water textures when there's rainfall on the ground (Mac) can we expect a fix for that on the PTS?

    Also the issue that the character is stuck upon login (jumping is a current workaround) is being addressed?
  • Anhel67
    Anhel67
    Soul Shriven
    64-bit Client doesn't work I know it , but why 32 bit won't start also . I start client press login and then endless loading.
  • Weng
    Weng
    ✭✭✭
    Windows 10 Pro
    64-Bit

    I get a 0xc000007b exception when starting the eso64.exe.
  • daemonios
    daemonios
    ✭✭✭✭✭
    ✭✭✭✭✭
    Windows 10 Home 64-bit, no luck running the client. Every time the following error is logged in the event viewer:
    Faulting application name: eso64.exe, version: 1.0.0.1, time stamp: 0x56b55b28
    Faulting module name: eso64.exe, version: 1.0.0.1, time stamp: 0x56b55b28
    Exception code: 0xc0000005
    Fault offset: 0x0000000000912e53
    Faulting process ID: 0x2798
    Faulting application start time: 0x01d1638ec9f65928
    Faulting application path: D:\ESO_PTS\The Elder Scrolls Online PTS\game\client\eso64.exe
    Faulting module path: D:\ESO_PTS\The Elder Scrolls Online PTS\game\client\eso64.exe
    Report ID: 2d8aa095-50c5-471a-979e-9b7aed370369
    Faulting package full name:
    Faulting package-relative application ID:

    Under details I get the following information:
    - System

    - Provider

    [ Name] Application Error

    - EventID 1000

    [ Qualifiers] 0

    Level 2

    Task 100

    Keywords 0x80000000000000

    - TimeCreated

    [ SystemTime] 2016-02-09T23:08:31.472942700Z

    EventRecordID 1445

    Channel Application

    Computer Neo

    Security


    - EventData

    eso64.exe
    1.0.0.1
    56b55b28
    eso64.exe
    1.0.0.1
    56b55b28
    c0000005
    0000000000912e53
    2798
    01d1638ec9f65928
    D:\ESO_PTS\The Elder Scrolls Online PTS\game\client\eso64.exe
    D:\ESO_PTS\The Elder Scrolls Online PTS\game\client\eso64.exe
    2d8aa095-50c5-471a-979e-9b7aed370369
  • Yiko
    Yiko
    ✭✭✭✭✭
    Wolfster wrote: »
    I just posted this on the patch notes thread but I'm gonna shamelessly repeat it here:

    Yesterday's version of the 64bit Mac client ran beautifully (30+ fps), today's is running at an average of 5 fps. Altering graphics settings is having no effect - same on minimum and maximum settings.

    2.4Ghz i7 (quad core)
    8Gb memory
    GeForce GT 650M 1024Mb

    Having the exact same problem
  • iqoologiceb17_ESO
    iqoologiceb17_ESO
    ✭✭✭
    win 10 here.. runs shortly then terminates without any notification

    Windows 10 Pro x64
    Running eso64.exe runs and then terminates shortly after with no error but I looked in to Event Viewer and saw this:

    Event ID 1000
    Faulting application name: eso64.exe, version: 1.0.0.1, time stamp: 0x56b55b28
    Faulting module name: eso64.exe, version: 1.0.0.1, time stamp: 0x56b55b28
    Exception code: 0xc0000005
    Fault offset: 0x0000000000912e53
    Faulting process id: 0x2e58
    Faulting application start time: 0x01d1638f35fb1fe4
    Faulting application path: D :\Program Files (x86)\Zenimax Online\The Elder Scrolls Online PTS\game\client\eso64.exe
    Faulting module path: D :\Program Files (x86)\Zenimax Online\The Elder Scrolls Online PTS\game\client\eso64.exe
    Report Id: c8112328-f7e6-486d-8cb5-fc0efb331012
    Faulting package full name: 
    Faulting package-relative application ID: 
    

    Event ID 1001
    Fault bucket 120408964937, type 4
    Event Name: APPCRASH
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: eso64.exe
    P2: 1.0.0.1
    P3: 56b55b28
    P4: eso64.exe
    P5: 1.0.0.1
    P6: 56b55b28
    P7: c0000005
    P8: 0000000000912e53
    P9: 
    P10: 
    
    Attached files:
    C:\Users\Milos\AppData\Local\Temp\WERB189.tmp.WERInternalMetadata.xml
    C:\Windows\Temp\WERB5DF.tmp.csv
    C:\Users\Milos\AppData\Local\Temp\WERB5FE.tmp.appcompat.txt
    C:\ProgramData\Microsoft\Windows\WER\Temp\WERB61E.tmp.dmp
    C:\Users\Milos\AppData\Local\Temp\WERB63F.tmp.WERDataCollectionFailure.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_eso64.exe_50b2ea5ffb3dae2d3a20b356c3f9d220794b5f57_333209f0_2cb2b64b
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 61675719-3018-46cd-944c-762af0faba1e
    Report Status: 4104
    Hashed bucket: 60e38259453ab646da80bb1166002954
    

    I attached Game Consultant report just in case :)
    Edited by iqoologiceb17_ESO on February 10, 2016 1:24AM
    PC EU
  • MissBizz
    MissBizz
    ✭✭✭✭✭
    ✭✭✭✭✭
    Windows 8.1 64 bit
    Already had the 2010 C++ installed

    "ESO has stopped working"
    Problem signature:
    Problem Event Name: APPCRASH
    Application Name: eso64.exe
    Application Version: 1.0.0.1
    Application Timestamp: 56b55b28
    Fault Module Name: eso64.exe
    Fault Module Version: 1.0.0.1
    Fault Module Timestamp: 56b55b28
    Exception Code: c0000005
    Exception Offset: 0000000000912e53
    OS Version: 6.3.9600.2.0.0.768.101
    Locale ID: 1033
    Additional Information 1: 972c
    Additional Information 2: 972cbf321beba0872c6ad37af43c68e6
    Additional Information 3: 185a
    Additional Information 4: 185a06e82a2ef5f7e55512c1ea4c1d24

    Attempted to run as administrator and still a no go.

    Can open up 32 bit client via launcher (although after I exited I noticed I got the "cannot determine version error". Took longer than usual to get to the Bethesda logo but it worked. Can log into a character and move around. Unfortunately can't stay on right now but 32 bit APPEARS to work for me.
    Lone Wolf HelpFor the solo players who know, sometimes you just need a hand.PC | NA | AD-DC-EP | Discord
  • Enodoc
    Enodoc
    ✭✭✭✭✭
    ✭✭✭✭✭
    Dagoth_Rac wrote: »
    Neither 32-bit nor 64-bit working on my Windows Vista machine and I have used PTS in the past. Both result in the standard ESO crash dialog box where you enter what you were doing and hit submit.
    @Dagoth_Rac What's your DirectX version? Vista's standard DirectX 9 is no longer supported.
    UESP: The Unofficial Elder Scrolls Pages - A collaborative source for all knowledge on the Elder Scrolls series since 1995
    Join us on Discord - discord.gg/uesp
  • Kas
    Kas
    ✭✭✭✭✭
    win10 here, 32bit working fine. 64bit does not start (process immediately closes after start)
    @bbu - AD/EU
    Kasiia - Templar (AR46)
    Kasiir Aberion - Sorc (AR38)
    Dr Kastafari - Warden (~AR31)
    + many others
  • Sidney
    Sidney
    ✭✭✭✭
    This is the official feedback thread for the 64-bit Client. Specific feedback that the team is looking for includes:
    • If you used the 64-bit client, did you find it worked ok?
    • Did you crash while using this client? If so, how often?
    • Did you notice anything peculiar?
    • Did you run into any issues when using /feedback or /bug?
    • Do you have any other general feedback?


    @ZOS_GinaBruno Sadly, the 64 bit client crashes before it even fully registers on my machine. It opens and I see it in task manager, but it never actually shows up. I tried running as administrator and putting it in Windows 7 Compatibility mode.

    I am on Windows 10.

    Version=1
    EventType=APPCRASH
    EventTime=130995355326165912
    ReportType=2
    Consent=1
    UploadTime=130995355326940218
    ReportIdentifier=22e676e7-cf88-11e5-8d7c-5404a64de33e
    IntegratorReportIdentifier=13dac06f-20b3-4f7b-900a-92c8b8e321c5
    NsAppName=eso64.exe
    Response.BucketId=60e38259453ab646da80bb1166002954
    Response.BucketTable=4
    Response.LegacyBucketId=120408964937
    Response.type=4
    Sig[0].Name=Application Name
    Sig[0].Value=eso64.exe
    Sig[1].Name=Application Version
    Sig[1].Value=1.0.0.1
    Sig[2].Name=Application Timestamp
    Sig[2].Value=56b55b28
    Sig[3].Name=Fault Module Name
    Sig[3].Value=eso64.exe
    Sig[4].Name=Fault Module Version
    Sig[4].Value=1.0.0.1
    Sig[5].Name=Fault Module Timestamp
    Sig[5].Value=56b55b28
    Sig[6].Name=Exception Code
    Sig[6].Value=c0000005
    Sig[7].Name=Exception Offset
    Sig[7].Value=0000000000912e53
    DynamicSig[1].Name=OS Version
    DynamicSig[1].Value=10.0.10586.2.0.0.768.101
    DynamicSig[2].Name=Locale ID
    DynamicSig[2].Value=1033
    DynamicSig[22].Name=Additional Information 1
    DynamicSig[22].Value=972c
    DynamicSig[23].Name=Additional Information 2
    DynamicSig[23].Value=972cbf321beba0872c6ad37af43c68e6
    DynamicSig[24].Name=Additional Information 3
    DynamicSig[24].Value=185a
    DynamicSig[25].Name=Additional Information 4
    DynamicSig[25].Value=185a06e82a2ef5f7e55512c1ea4c1d24
    UI[2]=C:\Program Files (x86)\Zenimax Online\The Elder Scrolls Online PTS\game\client\eso64.exe
    UI[3]=ESO has stopped working
    UI[4]=Windows can check online for a solution to the problem.
    UI[5]=Check online for a solution and close the program
    UI[6]=Check online for a solution later and close the program
    UI[7]=Close the program
    
    Edited by Sidney on February 10, 2016 12:21AM
    >.<_____/
    If you want me to read a post aimed at me, please put @Sidney.
    Please give us tail armor and dyeable tail ribbons.
    Click Here -->Support Dyeable Tail Ribbons<---
    All your mats r belong to Khajiit.
    Click Here -->Support Tail Armor<---
  • Dagoth_Rac
    Dagoth_Rac
    ✭✭✭✭✭
    ✭✭✭✭
    Enodoc wrote: »
    Dagoth_Rac wrote: »
    Neither 32-bit nor 64-bit working on my Windows Vista machine and I have used PTS in the past. Both result in the standard ESO crash dialog box where you enter what you were doing and hit submit.
    @Dagoth_Rac What's your DirectX version? Vista's standard DirectX 9 is no longer supported.

    @Enodoc

    Dual GTX 560 Ti with DirectX 11 on my Vista 64-bit machine. The 32-bit eso.exe crashes immediately, but I do get the ESO crash dialog box where it asks me to type in what was happening when I crashed. I just installed PTS on a Windows 7 64-bit machine with a single GTX 970, again DirectX 11. And again, 32-bit eso.exe crashes immediately with the standard ESO crash dialog box where it asks me to type in what was happening when I crashed. It does behave differently with eso64.exe. On Vista, eso64.exe is standard ESO crash. On Windows 7, eso64.exe is "0xc000007b" error.

  • NewBlacksmurf
    NewBlacksmurf
    ✭✭✭✭✭
    ✭✭✭✭✭
    Eek I'm going to sit out this round on PTS. Waiting for consistent stability first.
    Wow. Not sure if ppl joke about ZOS not testing stuff but this doesn't look good
    -PC (PTS)/Xbox One: NewBlacksmurf
    ~<{[50]}>~ looks better than *501
  • Vaktus
    Vaktus
    ✭✭
    Eek I'm going to sit out this round on PTS. Waiting for consistent stability first.
    Wow. Not sure if ppl joke about ZOS not testing stuff but this doesn't look good

    If you're truly looking for 'consistent stability', the PTS is not where you'll find it.
    Sixteen-year-old on a quest for world domination. Watch out!
  • NewBlacksmurf
    NewBlacksmurf
    ✭✭✭✭✭
    ✭✭✭✭✭
    Vaktus wrote: »
    Eek I'm going to sit out this round on PTS. Waiting for consistent stability first.
    Wow. Not sure if ppl joke about ZOS not testing stuff but this doesn't look good

    If you're truly looking for 'consistent stability', the PTS is not where you'll find it.

    Respectfully I've been around long enough to understand what PTS....
    -PC (PTS)/Xbox One: NewBlacksmurf
    ~<{[50]}>~ looks better than *501
  • fr33r4ng3r
    fr33r4ng3r
    ✭✭✭
    Windows 10 here too. Same issue. eso64.exe crashes immediately on start-up (I don't have Visual Studio installed - so no debug diagnostics to share unfortunately). GTX 970 GC and latest Nvidia drivers etc.

    eso.exe starts normally - though I have not tested exhaustively.
  • Enodoc
    Enodoc
    ✭✭✭✭✭
    ✭✭✭✭✭
    Dagoth_Rac wrote: »
    Enodoc wrote: »
    Dagoth_Rac wrote: »
    Neither 32-bit nor 64-bit working on my Windows Vista machine and I have used PTS in the past. Both result in the standard ESO crash dialog box where you enter what you were doing and hit submit.
    @Dagoth_Rac What's your DirectX version? Vista's standard DirectX 9 is no longer supported.
    @Enodoc

    Dual GTX 560 Ti with DirectX 11 on my Vista 64-bit machine. The 32-bit eso.exe crashes immediately, but I do get the ESO crash dialog box where it asks me to type in what was happening when I crashed. I just installed PTS on a Windows 7 64-bit machine with a single GTX 970, again DirectX 11. And again, 32-bit eso.exe crashes immediately with the standard ESO crash dialog box where it asks me to type in what was happening when I crashed. It does behave differently with eso64.exe. On Vista, eso64.exe is standard ESO crash. On Windows 7, eso64.exe is "0xc000007b" error.
    Hmm, interesting. I'm not sure what to suggest, really. I had thought the end of official support for Vista was tied to DirectX, but maybe there's more to it than that.
    UESP: The Unofficial Elder Scrolls Pages - A collaborative source for all knowledge on the Elder Scrolls series since 1995
    Join us on Discord - discord.gg/uesp
  • smacx250
    smacx250
    ✭✭✭✭✭
    With the Mac client, I still crash every time I press "E" to loot a mob. I submitted the crash report.

    Also, I find that on initial login the connection times out as the texture compilation occurs, and then if I login again (don't quit the client), it goes very quickly to the character select screen. If you can't speed up the texture compilation, then the initial connection timeout should be increased.

    OS X 10.9.5, late 2013 15" retina macbook pro, 2.3 GHz i7, 16GB
  • KennanTheCold
    KennanTheCold
    ✭✭✭
    I'm running on Windows 7 Ultimate, downloaded latest patch for PTS, and after hitting launch I get the standard crash dialog box from ESO, asking me to describe what I was doing at time of crash. This has happened for both the 32-bit and 64-bit version. Really hoping this will be solved soon, in the meantime i'm considering unistalling PTS and reinstalling it. Any thoughts on that?
    Edited by KennanTheCold on February 10, 2016 12:56AM
    Kennan Freesword
    Adielle Freesword
    Kennan Freesword Jr
    Noble Freesword
    Tara Freesword
    Bruce Freesword
  • joleda4ub17_ESO
    joleda4ub17_ESO
    ✭✭✭
    My i3-2120, 8 gb, 560 ti, win 7 64-bit scream machine ran eso64.exe just fine!
  • Dagoth_Rac
    Dagoth_Rac
    ✭✭✭✭✭
    ✭✭✭✭
    I'm running on Windows 7 Ultimate, downloaded latest patch for PTS, and after hitting launch I get the standard crash dialog box from ESO, asking me to describe what I was doing at time of crash. This has happened for both the 32-bit and 64-bit version. Really hoping this will be solved soon, in the meantime i'm considering unistalling PTS and reinstalling it. Any thoughts on that?

    I am having same issue, on both Vista and Windows 7. Glad I am not the only one having trouble with 32-bit! If it went live as-is I could not play game. At all. Neither 32-bit nor 64-bit. On either of my computers. :-(
  • Shuichi
    Shuichi
    ✭✭✭
    Can confirm Windows 10 will not launch, no compatibility mode, admin run will cause any reacion.

    Radeon 7950, AMD-FX 6350, 8 GB RAM
    Hand of Sithis - Daggerfall Covenant
  • KaneBunce
    KaneBunce
    Ruben wrote: »
    We believe we've found the problem relating to an encryption issue, and will let you know when we'll be able to fix it as soon as we can. Still testing, though. Please stand by...

    It's nice to know that the problem was found. I guess the fix is coming with next weeks patch? Or will it be pushed in a smaller incremental as soon as it's ready?

    I am not expecting anything sooner than next weeks. Two patches in one week seems unlikely.
    "A contradiction cannot exist in reality. Not in part, nor in whole." - Wizard's 9th Rule.
  • ZOS_GinaBruno
    ZOS_GinaBruno
    Community Manager
    Ruben wrote: »
    We believe we've found the problem relating to an encryption issue, and will let you know when we'll be able to fix it as soon as we can. Still testing, though. Please stand by...

    It's nice to know that the problem was found. I guess the fix is coming with next weeks patch? Or will it be pushed in a smaller incremental as soon as it's ready?

    Yes, should be fixed with our incremental early next week. Unfortunately we cannot do another full patch before then, and it's not something that can be hotfixed.
    Gina Bruno
    Senior Community Manager
    Dev Tracker | Service Alerts | ESO Twitter | My Twitter
    Staff Post
  • Volkodav
    Volkodav
    ✭✭✭✭✭
    ✭✭
    Excuse me if I ask a silly question, but how do I know if I downloaded the 64 bit client?

    It automatically downloads when you patch. :)

    Well,if it automatically DLed,I have no problem with it.I was in the PTS last night and all's fine.
  • KaneBunce
    KaneBunce
    Ruben wrote: »
    We believe we've found the problem relating to an encryption issue, and will let you know when we'll be able to fix it as soon as we can. Still testing, though. Please stand by...

    It's nice to know that the problem was found. I guess the fix is coming with next weeks patch? Or will it be pushed in a smaller incremental as soon as it's ready?

    Yes, should be fixed with our incremental early next week. Unfortunately we cannot do another full patch before then, and it's not something that can be hotfixed.

    It is a shame that many of us have to wait just because we updated to newer versions of Windows.

    Though it begs the question, was the 64 bit client tested on anything more recent than Windows 7? I hope it was, as proper testing policy is to test it on all recent versions of Windows. I will give you guys the benefit of the doubt and assume it was simply that the encryption was not an issue internally as all internal PCs have the encryption cabilities that are needed.
    "A contradiction cannot exist in reality. Not in part, nor in whole." - Wizard's 9th Rule.
  • KaneBunce
    KaneBunce
    Oh, and in the meantime, I assume there is no workaround that we can apply?
    "A contradiction cannot exist in reality. Not in part, nor in whole." - Wizard's 9th Rule.
  • Idinuse
    Idinuse
    ✭✭✭✭✭
    Is @Xiana the only one that's been able to successfully launch the 64-bit client? Anyone else?

    Launch went smooth. Game worked flawless until it crashed while watching duels outside Chalman. More testing coming.

    Win7 64-bit, 8MB ram, SET RequestedNumJobThreads "-1", SET RequestedNumWorkerThreads "-1", SET PlayerStandInsEnabled.2 "0", eso64.exe launched without "-USEALLAVAILABLECORES" switch.

    Edit* On Windows 10, I get the "0xc000007b" error immediately upon launch with eso64.exe, no matter what I try (admin, compatibility mode etc).
    Edited by Idinuse on February 10, 2016 3:59AM
    Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium dolorem que laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?
Sign In or Register to comment.