open All Channels
seplocked Issues, Workarounds & Localization
blankseplocked Client crash since 1.6
This thread is older than 90 days and has been locked due to inactivity.

Pages: 1 [2]

Author Topic

Grishnak U'rtal
Posted - 2011.06.13 17:34:00 - [31]

I am experiencing Client crashes as well, however my client is not minimized and I am not alt+tab'd from the client. I am in game with the game displayed on-screen.
My crashes occur during gate jumps and while un-docking from stations. Less annoying experiences are when the client does not crash completely, though the display will flash off for about 4-5 seconds when entering a new system after a gate jump. Not as critical as a crash but I'm sure it's a related issue.
I am using a one year old laptop w/ Intel HD graphics. I notice while having the driver info open, when the client crashes, my Graphics Memory Used is near, at or over the Maximum Available Graphics Memory. It's as if since the most recent patch update, my Graphics Memory does not purge old data.
I have a hard time blaming my Intel onboard Graphics Accelerator seeing as how this issue has never happened prior to the 1.6.1 patch was applied on my machine. Prior to the recent patches, the client has run without issue.

Posted - 2011.06.13 19:13:00 - [32]

I'm having this issue as well. The problem seems to be related to loading grids. I have seen this issue on all forms of grid change (entering warp, exiting warp, docking, undocking, jumping between systems, clone jumping to a different type of station). It does not appear to matter if you are actively piloting, auto piloting, alt-tabbed, minimized, etc.

Once, this problem has escalated to a failure to display anything but my cursor and the esc-menu, while still loading grid. I consider this escalation do to the fact that I can still be blown up under these circumstances.

Kira Doshu
Posted - 2011.08.01 01:21:00 - [33]

Same issue, back to python27.dll. Any time a grid menu/window updates, there's an obvious momentary slow down, usually resulting in a crash.

Pages: 1 [2]

This thread is older than 90 days and has been locked due to inactivity.


The new forums are live

Please adjust your bookmarks to

These forums are archived and read-only