These forums have been archived and are now read-only.

The new forums are live and can be found at

Issues, Workarounds & Localization

  • Topic is locked indefinitely.

Game crashes on resolution changed

Niobea Aenir
Goonswarm Federation
#1 - 2013-06-21 21:46:16 UTC  |  Edited by: Niobea Aenir
If I don't start eve just after restarting my computer, game client always crash after changing resolution - that means maximizing window, switching to fullscreen, or just resizing the game windows.

I'm getting this error since last update. Does have anyone else the similar issue and how can I solve it?

EDIT: it is not after I restart my computer, it goes wrong after first time launching & closing eve client. For the first time it works properly, but when I start eve for the second time, it starts crashing. No logs from log server - when I start client for the second time, it is unable to connect to log server.
Deep Core Mining Inc.
Caldari State
#2 - 2013-07-06 14:35:25 UTC
I'm Experiencing the same,
Although im not able to change anything at first start.
Anything to do with resolution or full screen is instant crash

you managed to fix it?
Xeano Estrado
Estrado Empire
#3 - 2013-07-07 11:26:23 UTC
Can you please include a dxdiag (or link to it). That way the ccp devs can have a closer look at it..
Xyne Talice
Ganis Support Corporation
#4 - 2013-07-09 16:15:51 UTC

I might have a similar problem:

I have two eve clients running, one on 1920x1080 without problems, the other spans across two monitors (1920x1080 and 1280x1024 with the 56 pixel rows unaccessible)

Both have frameless windowed mode and same settings, but only the client spanning over two monitors crashes occasionally (about once or twice per evening)
I narrowed the crash instances down mostly to times when I activate/deactivate the desktop on my third monitor or when I start/stop a videostream, go fullscreen etc)

Machine is Windows 8 x64 running on core i5 3570k with radeon hd7770

see you Xyne
seth Hendar
I love you miners
#5 - 2013-07-10 11:42:17 UTC
a cropmate is experiencing the same, and for him, disabling the TS3 overlay plugin solved the issue, so if you have any kind of overlay (mumble / TS / Fraps etc...) try disvabling it, and see if the issue still occur