Go to launcher - Options - Direct X and switch it to DX9 for now

Works for me on my dual ati 5770s

The DX team is definitely looking into these driver crashes.

Not sure if they are station-related, but the individuals responsible for the stations have also been alerted.


Thank you for helping us fix it by commenting here and submitting bug reports.

Yup had to change to DX9 and now it works.. DX11 doesn't work for my ati card... First time crash heading to gate I got BSD and the second time warping to get on a fresh login.. Game not responding.

Never had a BSD from Eve before.. you guys are doing something wrong with your coding.

We're keeping DX11 and DX9 as identical as possible until we're confident that these types of issues are at an absolute minimum.

The DX team are hammering away and should have an solution soon.

Thanks, Nax, Wolf, D4RK, Nerdy, Alex, and 'bubble.

Since your here can you elaborate what difference if any does DX11 do for graphics in space or is this a Wis thing over DX9?

Edit: tried a few more times on dx9 and it's borked.

Confirmed with AMD 7750 with latest drivers. Happened twice, 1. after warping to POS 2. on gate. Second crash also BSODed my system. EDIT: Switching to DX9 did not help. And now mine characted is stucked on gate, crashing always when he warped back. Thank you very MUCH CCP. Apparently testing of this patch have been very extensive...

The DX team is definitely looking into these driver crashes.

Not sure if they are station-related, but the individuals responsible for the stations have also been alerted.


Thank you, Naxirian, for helping us fix it by commenting here and submitting bug reports.

The DX team is definitely looking into these driver crashes.

Not sure if they are station-related, but the individuals responsible for the stations have also been alerted.


Thank you, Naxirian, for helping us fix it by commenting here and submitting bug reports.

Go to launcher - Options - Direct X and switch it to DX9 for now

Works for me on my dual ati 5770s

I warped from a corporation tower with corporate member forcefield. I could just be crazy.

213412014.01.28 23:39:56:012Open failed on "C:/Program Files (x86)/CCP/EVE/res/graphics/effect.dx11/managed/space/specialfx/particles/particlecloud/fixedfunctionemulationv2/ffe0.sm_depth"
213422014.01.28 23:39:56:012Couldn't open file 'res:/graphics/effect.dx11/managed/space/specialfx/particles/particlecloud/fixedfunctionemulationv2/ffe0.sm_depth'

Same Problem. Crash near Stargate. 3 Times in the last 10min.
Before Patch no problems.



Win 7 64bit/ Radeon HD 7800

It may be a bug between your software and the driver, and possibly a mismatch in their specifications for all I know, but I'd like to confirm that it's not a bug in the driver itself independent of eve. To be blunt, you guys broke something yesterday, not AMD.

Eve was working fine yesterday, and has been for the last fortnight. By coincidence, I ran an ultra-setting bioshock infinite benchmark yesterday.

This machine was build brand new from components a fortnight ago. The version of eve running here has been patched only once. It was installed from whole cloth via your downloader two weeks ago, so it too is fresh.

Today, the graphics driver is crashing, but *only* when eve is open and I am undocked doing things.

I mostly crash around stargates, but I have had a crash in a wormhole gas site.

The number of things around does not seem to be a factor, I've been docking and undocking from jita all day, never had a crash on the undock, only on stargates and that one gas site.

+1

Seems random - but happening every 5 or so minutes.

Problemsignatur:
Problemereignisname:AppHangB1
Anwendungsname:exefile.exe
Anwendungsversion:2014.1.70.5482
Anwendungszeitstempel:52e11c87
Absturzsignatur:aa58
Absturztyp:0
Betriebsystemversion:6.1.7601.2.1.0.256.1
Gebietsschema-ID:1031
Zus+ñtzliche Absturzsignatur 1:aa581359fce0f8b3b1d787be9a000b68
Zus+ñtzliche Absturzsignatur 2:994b
Zus+ñtzliche Absturzsignatur 3:994bf3caabc1c8bd5ad22c7d241ec181
Zus+ñtzliche Absturzsignatur 4:aa58
Zus+ñtzliche Absturzsignatur 5:aa581359fce0f8b3b1d787be9a000b68
Zus+ñtzliche Absturzsignatur 6:994b
Zus+ñtzliche Absturzsignatur 7:994bf3caabc1c8bd5ad22c7d241ec181

We have come up with a much simpler repro case that consistently crashes my AMD display driver (and even blue-screened once). We have a potential fix that we're about to test with the original repro case - more on this later.

You there, tell us will we (the affected) get lost game time added back to our accounts?

I'm optimistic we have found a fix - we need to do more testing to make sure nothing else broke. Assuming the testing goes well we'll have a patch ready on Monday.

In the meantime, turning off anti-aliasing should reduce the chance of driver crashes on AMD cards.

I'm optimistic we have found a fix - we need to do more testing to make sure nothing else broke. Assuming the testing goes well we'll have a patch ready on Monday.

In the meantime, turning off anti-aliasing should reduce the chance of driver crashes on AMD cards.

Will ships lost as a result of associated graphics bugs be re-reimbursed?
only cos, y'know I was told it was fixed when using directx9...

Snorlax, you cant be serious. I dont want to be rude, but this issue is affecting whole game play. If you know whats wrong, fix it now pls, cause you cant make it worse than it is.

I'm sorry, we can't release a fix to low level graphics code without more testing. I appreciate that this is frustrating but we can't risk breaking the game for even more players. My team has worked hard to identify a fix but we can't rush it, much as I'd like to.

I'm sorry, we can't release a fix to low level graphics code without more testing. I appreciate that this is frustrating but we can't risk breaking the game for even more players. My team has worked hard to identify a fix but we can't rush it, much as I'd like to.

The fact I've now lost two ships to this bug crashing two different systems means I'm less inclined to play this game

I'm sorry to hear that. I'm still inclined to keep fixing bugs and improving the game.

I'm sorry to hear that. I'm still inclined to keep fixing bugs and improving the game.

I am really happy to hear that and you have my thanks for that :)

I was just wondering, you made a mistake in game, we are loosing our ships, are you going to fix that on kb and also to replace our isk?

The FPS monitor in-game still shows DX11 in the top corner despite my having told the launcher to run in DX9. Monitor wrong or launcher setting didn't work?

I'm optimistic we have found a fix - we need to do more testing to make sure nothing else broke. Assuming the testing goes well we'll have a patch ready on Monday.

In the meantime, turning off anti-aliasing should reduce the chance of driver crashes on AMD cards.

If this fix works, is there any chance it can be deployed in a hotfix asap instead of Monday? some of us would actually like to play sometime this week please.

Does said fix maybe sorta possibly kinda also fix the same issue on nVidia cards? I'm having the same crashing issue (although not DRIVER crash, just client crash) on my 760 GTX
Here's my post in another thread: https://forums.eveonline.com/default.aspx?g=posts&m=4170994#post4170994

Interesting, is that a macbook with windows installed?

We have come up with a much simpler repro case that consistently crashes my AMD display driver (and even blue-screened once). We have a potential fix that we're about to test with the original repro case - more on this later.

Not on your life - Total custom rig.

I'm sorry, we can't release a fix to low level graphics code without more testing. I appreciate that this is frustrating but we can't risk breaking the game for even more players. My team has worked hard to identify a fix but we can't rush it, much as I'd like to.

DX 9 Gave me about an hour before it too crashed. The only solution I've found with some sort of stability past that since I do like most of us play for more than an hour here and there- Is to play it in Performance aka ugly mode. I too am glad I looked online for others having the problem before I went apes**t crazy tearing my tower apart or buying a new card...

HD770 Updated Drivers
I7 4th Gen
32GB RAM

Confirmed with AMD 7750 with latest drivers. Happened twice, 1. after warping to POS 2. on gate. Second crash also BSODed my system. EDIT: Switching to DX9 did not help. And now mine characted is stucked on gate, crashing always when he warped back. Thank you very MUCH CCP. Apparently testing of this patch have been very extensive...

And for the mac haters out there the game is running solid on my work laptop which is a macbook pro....just sayin..

The DX team is definitely looking into these driver crashes.

Not sure if they are station-related, but the individuals responsible for the stations have also been alerted.


Thank you, Naxirian, for helping us fix it by commenting here and submitting bug reports.

We have identified a probable cause for AMD drivers crashing and will have a fix in a patch on Monday. It does fix the repro case we had inhouse, and we've been testing on other setups and so far have not seen any fallout from that fix.

In the meantime some players have reported better stability with lower quality settings, in particular you should try to turn anti-aliasing off. There are mixed reports of this, but it's worth trying lower settings if you experience frequent driver crashes.

I failed to recreate the crash with a shuttle nor a hawk.
Only managed to trigger it with an Orca.

So it's something about large something yes.

Same issue like everyone here with ati 7800 series.

directx11 workaround for me:
- disable resource cache
- disable hdr
- disable anti-aliasing
don't know which of the causes the issue.....

i was able to navigate in space, dock, undock and jump through portals while dualboxing. didn't try actual fights so far.

ive been getting it in mission sites when i go through an acceleration gate
will crash 2 or 3 times then become stable enough for me to do things for about 5-10 minutes then crash again, rinse and repeat

Similar here, but instead of acceleration gates the triggers are jump gates. Suffering from this problem for days now, with no end and/or compensation in sight.

After a couple of days waiting, someone responded to my ticket and told me try directx9. No luck there, but at least someone did respond. :D At this rate, I will tell you how the ticket plays out, in a couple of months.

HTFU they've said they are investigating it and even that it should be fixed in the patch on Monday. quit thinking you are a special little snowflake just because you contribute a tiny amount each month to the CCP coffers

I placed a 10mil isk bounty on you because you're an idiot, and it will make me happy to get a notification every time someone kills you.

We have identified a probable cause for AMD drivers crashing and will have a fix in a patch on Monday. It does fix the repro case we had inhouse, and we've been testing on other setups and so far have not seen any fallout from that fix.

In the meantime some players have reported better stability with lower quality settings, in particular you should try to turn anti-aliasing off. There are mixed reports of this, but it's worth trying lower settings if you experience frequent driver crashes.

Same problem here

ATI 7970 Driver 13.12

reducing to DX9 and other parametrs only extend the time until next crash

as the crashes are unpredictible, the game is unplayable for me

i hope the monday patch will work

but CCP did you test any patch ? ATI cards are not so unusual in the world or are they ?

Yes, we did - not every ATI card crashes. There are more factors involved, but once we found a repro case we were able to find a workaround that should go out on Monday.

Recently updated my NVidia driver and with the latest patch to game as well as a proper sli profile for eve now, things are running fine with dx 11.

Yes, we did - not every ATI card crashes. There are more factors involved, but once we found a repro case we were able to find a workaround that should go out on Monday.

Maybe not, but you can add my AMD FirePro M4000 to the list.
The card crashed consistently when warping to a gate, station, or faction warfare beacon.
The computer has gone from something that could easily run two clients to an unplayable heap overnight. Thanks!

Looking around this thread, i'd say that the client is crashing on more ATI models than its running stable on. Since you didnt seem to realize that when you made your comment, Ive taken the time to put together a list for CCP.
Listed versions of crashing AMD/ATI cards so far include:
3570
4890
5700
5770
5800
5850
5870
5970
6300
6700
6790
6800
6850
6870
6900
6950
7750
7770
7800
7850
7870
7900
7950
7970
8670
M4000
R9 200
R9 270X
R9 280
R9 280X
R9 290

So, just out of curiosity.....what version(s) of ATI cards was the original (bug causing code) tested on?

Confirmed same issue happening here. Running dual 7850's on Win 8.1 x64. Crossfire is enabled.

Rest of the system

AMD FX 8 Core
12gb Memory
500GB SSHD

Running dual monitors, only ever running one client at a time, no other graphic intensive programs running simultaneously

We have identified a probable cause for AMD drivers crashing and will have a fix in a patch on Monday. It does fix the repro case we had inhouse, and we've been testing on other setups and so far have not seen any fallout from that fix.

In the meantime some players have reported better stability with lower quality settings, in particular you should try to turn anti-aliasing off. There are mixed reports of this, but it's worth trying lower settings if you experience frequent driver crashes.

Just to give you guys an update - we do have an inhouse repro of a driver crash and are working on a fix (or a workaround, rather - this does smell like a driver bug).

Hopefully we'll have something soon - I'll keep you posted.

Seriously? It just amazes me that CCP Devs have the cheek to call this a driver bug, when it was working perfectly well before the Patch.

A fantastic piece of buck passing there guys. Awesome stuff, carry on.

Seriously? It just amazes me that CCP Devs have the cheek to call this a driver bug, when it was working perfectly well before the Patch.

A fantastic piece of buck passing there guys. Awesome stuff, carry on.