Guild Wars 2

Just so people know, AMD beta drivers up to AMD Beta Drivers 13.11beta 9.2 do not work with GW2. I tested beta 2 and beta 6. The game will simply crash to your desktop and give you an error.

I just bought the game last night on 11/08/2013. Downloaded the game, got the to TOS page and the game would crash after hitting “Accept”. After trying pretty much every fix on the internet I discovered that I had to use the WHQL AMD 13.9 Drivers without the new frame-pacing improvements to get the game to work. I don’t have this issue with any other game (I have about 20 installed from different companies) so it was one of the last things I tried.

It’s my hope ArenaNet and/or AMD will work get this issue resolved before the WHQL drivers are released.

That’s not something that ArenaNet has to worry about. It’s a beta driver. They either work or they don’t. The only product fixed will be the next version of the driver.

This isn’t a complaint to or about ArenaNet on this issue. This is just to inform users of this problem so they can resolve it without having to go through what I went through.

My statement was aimed at the part that looked like you were saying for ANet to fix it but it appears edited so I guess my previous message is no longer valid.

Tarvaln.6298:

Just so people know, AMD beta drivers up to AMD Beta Drivers 13.11beta 9.2 do not work with GW2. I tested beta 2 and beta 6. The game will simply crash to your desktop and give you an error.

Strange… I installed those very drivers yesterday, and GW2 works fine. I have a Radeon HD 7850 on Windows 8.1.

One person’s experience =/= everyone else’s.

Espionage.3685:

Tarvaln.6298:

Just so people know, AMD beta drivers up to AMD Beta Drivers 13.11beta 9.2 do not work with GW2. I tested beta 2 and beta 6. The game will simply crash to your desktop and give you an error.

Strange… I installed those very drivers yesterday, and GW2 works fine. I have a Radeon HD 7850 on Windows 8.1.

One person’s experience =/= everyone else’s.

Beta drivers will not work the same for everyone. For Tarvaln, his hardware configuration and software configuration were unfortunately right enough that they didn’t work.

Avelos.6798:

Beta drivers will not work the same for everyone. For Tarvaln, his hardware configuration and software configuration were unfortunately right enough that they didn’t work.

Fair enough, although this is the first and only report I’ve seen of GW2 not working. It’s leading me to believe there’s some other issue interfering instead of just the driver itself.

@Tarvaln, how did you remove previous drivers? What OS are you on? What card do you have?

I recommend using DDU from Wagnard for uninstalling the previous driver: http://forums.guru3d.com/showthread.php?t=379505

I found a possible culprit (memory leak?) and I think might be a quick & dirty fix for it until either AMD or Anet fixes the problem on their end.

As you can see in the attached screenshot of the task manager, there is a running process that is taking up memory space and shouldn’t be there in the first place when gw2 is running. I discovered that forcing it closed “fixes” the problem somewhat, and I am able to play gw2 without further issues.

Those drivers work for me on 7850 and windows 7

The game is running fine for me on Windows 7 with my R9-290.

There could be a few things that are causing my problems.

1.)I’m running 2 7950s in Crossfire. I did try switching to single GPU on the 13.11 beta 9.2 and GW2 gave me the same crash issue.
2.)My 7950s are OC’d to 1050/1250. It’s not a big OC but it might be a culprit.
3.) I have had games that throw me issues/crash on the first run and then play fine after that. That could be the case but I doubt it.

I’m guessing that the issue is with the new frame-pacing. I’d love to be proven wrong though. I really miss it with my other games now that I’m on the 13.9 WHQL driver.

If anyone else is running Xfire with the beta drivers please let me know.

First off, I would like to apologize for not getting back to this topic with the solution I have uncovered while looking for a more permanent fix to this memory leak issue.

Apparently dllhost.exe (the offending process) is an actual legitimate Windows process, just poorly implemented. The fix is to use a third-party utility to do all the heavy lifting instead of having Windows work it every single instance. Download Media Preview and install it; this should resolve the problem once and for all.

http://lifehacker.com/5908599/media-preview-adds-windows-explorer-thumbnails-to-nearly-any-video-file

It is from my understanding that Microsoft has already fixed the issue, but only for Windows 8 systems.