ESO Disappears When Logging Out

Shantu · August 2018

I noticed this once yesterday, then this morning after the megaservers maintenance, every time I log out of a character ESO just disappears to the desktop. Not a huge deal, but I then have to use the launcher to restart the program, which can be a bit of a pain when logging in and out of characters to do daily crafting writs.

ZOS_Bill · August 2018

@Shantu

If ESO is disappearing after you log out, the game is likely crashing. You should try running a repair through the launcher and see if that stops ESO from crashing when you log out. Additional crash troubleshooting steps can be found here.

Shantu · August 2018

I figured it out. This from Event Viewer:

Faulting application name: eso64.exe, version: 1.0.0.1, time stamp: 0x5b4682f1
Faulting module name: RzChromaSDK64.dll_unloaded, version: 2.11.2.17, time stamp: 0x5afbf218
Exception code: 0xc0000005
Fault offset: 0x00000000000013f4
Faulting process id: 0x45c
Faulting application start time: 0x01d42a74cf2fbadb
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Zenimax Online\Launcher\..\The Elder Scrolls Online\game\client\eso64.exe
Faulting module path: RzChromaSDK64.dll

I recent installed Razer software for a new mouse. I hated the fact that Razer forces you to create an online account so when using the mouse it can snoop on your computer and send back data (its a friggin' mouse!!). So I was trying a little creative mitigation by disabling some of the FIVE OS services this software installs. 2 of them were "Razer Chroma SDK Server" and "Razer Chroma SDK Service". Note the faulting module path above: RzChromaSDK64.dll. When I turn these services back on ESO will now allow me to log out successfully.

So a mouse service and associated library crashes ESO. Really? Time to uninstall the BS mouse software and find my hammer.

Nestor · August 2018

Razor mice can have Chroma effects based on things happening in the game. So there is the tie in. Now, whether these effects are worthwhile is up to you.

SlippyCheeze · August 2018

Shantu wrote: »

So a mouse service and associated library crashes ESO. Really? Time to uninstall the BS mouse software and find my hammer.

Well, most likely the Razor supplied Chrome SDK that is embedded in the ESO client to permit integration will crash if it fails to communicate with the service they supply. You are free to speculate about this being bad programming vs deliberate behaviour as you wish.

So, yes, to some level this is an accurate description of what has happened.

FWIW, I can recommend the Logitech G902 "wireless" gaming mouse, which also operates happily in USB wired mode, as being effective but not having the same issues that the Razor hardware has. Apparently it is now the [Logitech G903](https://www.logitechg.com/en-us/product/g903-wireless-gaming-mouse) after a hardware bump. I can also recommend the [Logitech G602](https://www.logitechg.com/en-us/product/g602-wireless-gaming-mouse) as being effective, though I prefer the G902.

Shantu · August 2018

With Razer, I thought I was just purchasing a $100 mouse with some expanded functionality. To some extent, I got that. But to use it, literally before the Synapse 3 software would be allowed to run, I had to create an online ID with Razer. Little did I know this software also gives me no option other than allow them to collect usage data on my machine send it to their servers. The Chroma stuff was of no interest to me but I was given to choice at installation. After paying that kind of money for a mouse and then being given no other option to use the extended functionality, really got under my skin. My bad for not conducting due diligence prior to purchase. But it's a mouse for pete's sake!

I do think it's bad programming that disabling a mouse service and the subsequent existence of 1 file from a separate company would crash ESO. If this was caused by the way this Chroma crap is coded into ESO, then shame on them.

Anyway, completely removing the Synapse 3 mouse software resolved the issue. First and last time I'll have anything to do with that company. I do have a Logitech G302 and their gaming software on my computer that forces me to go through none of this BS. Expensive lesson learned.

SlippyCheeze · August 2018

Shantu wrote: »

I do think it's bad programming that disabling a mouse service and the subsequent existence of 1 file from a separate company would crash ESO. If this was caused by the way this Chroma crap is coded into ESO, then shame on them.

I can't be certain, of course, but I'd lay good odds that the crash is in the code that Razor supply, in an unmodifiable format, as part of integration of apps and their lighting stuff. So, ZOS never saw the code that would cause the crash, didn't write it, and couldn't fix it even if they did want to.

Shantu · August 2018

Well, here's something strange. Just crashed to the desktop in the middle of game play. Here's the Event Viewer:

Faulting application name: eso64.exe, version: 1.0.0.1, time stamp: 0x5b4682f1
Faulting module name: RzChromaSDK64.dll_unloaded, version: 2.11.2.17, time stamp: 0x5afbf218
Exception code: 0xc0000005
Fault offset: 0x00000000000013f4
Faulting process id: 0x16b0
Faulting application start time: 0x01d42dab6ef2e5d7
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Zenimax Online\Launcher\..\The Elder Scrolls Online\game\client\eso64.exe
Faulting module path: RzChromaSDK64.dll
Report Id: 9fea6f32-e4a3-40bc-b509-ea5902b37b7d

So I reinstalled the Razer Synapse 3. The thing is, I have ALL Razer services disabled and the Synapse software is not running. There is no program from Razer running on my computer. I do this because while I want some of the extra functionality, when I want it, I do NOT want this company snooping around my computer sending my system and usage data back to them. Anyway, the question is, why would ESO crash on the Razer library when there are no Razer programs running? My bet is that ESO is coded to look for the library, if it exists, use it, and when leveraging the function calls in the library they, in turn, make calls to these services that are turned off. Whatever the case, bad programming on someone's part when crashing ESO becomes collateral damage.