Guild Wars 2

Is anyone else having problems with video capture software? I’m getting reproducible crashes since the 28th. So far I’ve tried Dxtory with several codecs (huffyuv, lagarith, dxtory, uT) as well as MSI Afterburner. I can record in other games fine, and haven’t changed anything of note on my computer. I’m thinking it might be a video driver issue or a problem with GW2 itself, since I’ve had problems on and off with GW2 crashing upon startup when Dxtory was already open.

I have a Radeon HD 6950 with driver version 12.100.17.0 on 64bit Win7. I’ll try the newest beta driver and see how that goes.

Update: Still crashing with latest beta drivers.

DXTory seems to work fine for GW2 for me

MSI Afterburner’s OSD collides with GW2 somehow.
try changing OSD rendering mode to “Vector 2D”. it seems to fix the porblem.

wauwi.9162:

MSI Afterburner’s OSD collides with GW2 somehow.
try changing OSD rendering mode to “Vector 2D”. it seems to fix the porblem.

Thanks for the tip. I tried 2D, and even disabling the OSD, but it still locks up.

Edit: tried Dxtory and Bandicam without OSD and those don’t work either.

Try exiting MSI Afterburner

I’m having the same problems. I tried using Bandicam and got the blue screen. I restarted and tried MSI Afterburner, game crashes. I tried updating to the latest beta drivers, no go. Was OC’d, switched everything to default, still can’t record. Tried other games, namely The Witcher 2, Torchlight 2 and Borderlands with both MSI and Bandicam and can record them fine. I had been recording GW2 videos fine as well up until I’m assuming January’s update (today was my first time recording since then).

Windows 7
1090T
AMD 7950 with 13.2 beta6 drivers
16GB RAM
500GB of space free on the 1TB HDD that I use for my vids.

EDIT: Continued to read on this and it’s an issue with the 13.2 drivers. 13.1 work fine.

I’m running into a different, yet similar issue. I open GW2, minimize to the desktop and start Bandicam, then go back to GW2. I know that Bandicam is working in the background because I see the FPS overlay in the corner. However, when I hit the button to start recording a video, the entire game freezes and I can’t move the mouse or anything. Eventually my computer will reboot. I tried using Bandicam to record other games and I don’t have the issue. I’ve ran tests on my RAM and video card and it reports no errors. I even tried updating Bandicam to the latest version, and that didn’t work. So I cut a support ticket and they told me to try turning off the FPS overlay. Tried that, didn’t help. Then they told me they don’t support 3rd party applications running along side GW2 and I should contact Bandicam to resolve this. Problem isn’t with Bandicam, as I can use it to record any game other than GW2.

This started happening for me after the February patch was related a few days ago. I think the issue is a memory leak in GW2 that gets exposed when Bandicam interacts with GW2. Since the patch, I’ve also noticed graphics performance hits, so it could also be the way GW2 interacts with Bandicam and the video drivers. Support ticket is still open, so I’ll see what they say and report any updates I get.

Here are my specs:
Windows 7, 64-bit
Core i7 2600k
16GB RAM (DDR3-1600)
AMD Radeon HD 7950 with 13.1 drivers
GW2 is installed on an SSD, videos are stored on a 1TB HDD.

Nothing above is overclocked, and I tried switching the video output directory to the SSD and got the same result.

Roll back to 13.1 drivers beta drivers cannot record GW2 atm, the game will just lock up

I thought I was the only one with this problem I was running MSI Afterburner and now it just locks up my computer. I uninstalled and haven’t tried anything else yet.

Make sure to send in a report to ati so they can get the next round of beta drivers if not the official launch compatible. I would hate to see these drivers not work with any video editing software just because they didn’t get enough inquiry into the issue.

Tried the newly released 13.3 beta drivers, recording still causes crashes and bsods. Have reported to AMD but has anyone else got any news regarding this, maybe a workaround?