Issues, Workarounds & Localization

There are a couple of crash fixes in today's release - let me know if things improve.

I have a GTX 580 in my system and I'm not seeing these crashes. Trust me - if I did, I'd have fixed them!

We're continuing to monitor crash dumps we get from you - my team's main focus is on stability and performance, and will be for the near future at least. We're doing what we can!

BTW, I assumed it was a corrupted install. Tried to run repair.exe but it was missing. (huh?) So I wiped my entire install and re-installed from scratch... and I crashed on my first gate jump, same as above.

Will do. DX9 has worked for the last dozen or so jumps, so would "appear" to be better.

This is what makes these issues so hard to fix! I would appreciate if you keep the LogServer running in case it does happen again so you can file a bug report with the log.

Of course it would be best if it just doesn't crash again :)

Or you could use your Dev powers, prowl the office and find some community Devs and force them to teach the powers of ctrl-shft-alt-m attach.

But of course, CCP Guard prowls the grounds of community devs, and you are afraid ...

I have a similar, if not identical problem to others in this thread.

Have had dozens of driver crashes as a result of having eve open. Have tested driver and card on a dozen other games, not a problem, and stress tested with with Furmark (max settings) for 24 hours, and didn't even have a temperature warning.

I have a GeForce GTX 580 card, and the problems only started after the Rubicon update. During the update, I also updated to the current Nvidia driver 322.XX from 314.XX, and I initially thought it to be a driver problem.

HOWEVER, after rolling back, then completely uninstalling and then reinstalling the old driver, the problems continued.

At the moment, Eve is unplayable on the desktop due to these errors, and I use my laptop instead. This occurs regardless of how many instances are open, and has reduced in frequency after clearing the cache, but still occurs.

No graphical glitches of any kind have been seen, and everything looks just fine right before the crashes. I receive no temp warnings from any piece of hardware, and am always alert for them.

One thing I have noticed is that it doesn't always crash the driver completely. Sometimes it'll black screen for a moment like usual, but then recover and not crash.

Yet one MORE thing, is that if Chrome is open, three scenarios play out:

Eve trips the driver, and it crashes
Eve trips the driver, recovers and CHROME crashes instead
Eve trips the driver, and both crash.

An important point is that no other program seems to be affected by this.

Just my two cents worth of experience.

Keep up the good work devs, I'm sure that you'll find a solution for this, and if it's our fault somehow, I'd appreciate a heads up.

Hello all,
Msi gtx580 here, win7pro 64bit, game has nvidia kernel crash when initiating warp or jumping into new system when grid loads, have taken note that if the f10 star map is open during warp initiation or gate jumps it never crashes. So it's clearly related to something graphical for starting warp and gate jumping.

I hope this gets fixed soon, my home is in lowsec and I can't afford to play it in this condition with this kind of liability, have noticed on several occasions it happens during undocking as well.

Flying around with star map and no real visuals is no way to play a game.

Log Name: Application
Source: Application Error
Date: 27.12.2013 00:54:59
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: 4711
Description:
Faulting application name: ExeFile.exe, version: 2013.11.65.1687, time stamp: 0x5284d329
Faulting module name: _trinity_dx11_deploy.dll, version: 2013.12.66.8394, time stamp: 0x52a87dc8
Exception code: 0xc0000005
Fault offset: 0x005b91fb
Faulting process id: 0x1aa0
Faulting application start time: 0x01cf0295933c5786
Faulting application path: D:\games\eve_main\bin\ExeFile.exe
Faulting module path: D:\games\eve_main\bin\_trinity_dx11_deploy.dll
Report Id: 206c6b3c-6e89-11e3-863e-38607753502a

i also experience this kind of behavior after the last major patch.
the screen starts resetting itself, driver recovers and it continues till either i minimize the client then it stops and after reopening the window you can continue to play or the computer crashes with a blue screen telling me that the nvlddmkm.sys has caused the crash. still haven't figured out why this happens, other games seem to not have this issue. it seems to be related with firefox, adobe plugins and running more than 6 eve clients, gates (jumping into a system) and pos force fields logging in a client that warps directly to a tower is also no fun, took me 4 times to start the client to open the corp sheet to take a user in and three of those times the game was in slowmotion, cpu did not went up and temp on the system was okay-

ah look something new came up "The socket was closed" and after this i got "The transport has not yet been connected, or authentication was not successful."

yeah maybe someone might wanna have a look at this after holidays, thanks

I ran into this issue last night.

After running through my computer (Prime95 overnight, memory tests, video card benchmarks) and checking for driver updates I verified this with the Log Sever running while attempting to jump from a station in Otela to the Josameto gate. The client locked up, dumped to desktop with a Windows message stating the display driver had crashed/kernel crashed.

I've posted a bug report ( Addressed to CCP Snorlax) with LogServer log and DxDiag log included. If there is anything else I can do please let me know. :D

I've been getting this for the last three or four days, I attributed it to an OS upgrade (went from Windows 7-8)
I've done a full reinstall of my OS, a fully clean install of Eve (having to set up overviews on multiple supers was a PITA) then again and went to windows 7. Opened the client and it happened again!
I'm hopeful that there will be a fix for this as it isn't present in any other games.
I'm running a GTX770 with the lates (332.21) drivers.