Guild Wars 2

PC specs
GPU: Nvidia GTX 770
CPU: Intel i5-4670k
RAM: DDR3-1600 8gb
64bit client is downloaded onto kitten (fresh install)
OS: Win10
Graphics Driver: Nvidia 358.91 (up to date)

Issue
GW2 will freeze for a 4-10 seconds and then restore. Windows notification window will read something along the times of, “Game driver crashed and restored”.

I noticed this happens commonly in the HoT maps but does happen in normal maps. I’ve had this happen whether the map is populated or empty. The crashes will sometimes happen several times within the span of 10 minutes. Sometimes I can go a whole hour without a crash.

Can anyone help me? These crashes are driving me crazy and have led to a lot of deaths in game.

if your driver for NVidia is crashing do these 2 things.

1. submit a ticket into anet
2. Submit a bug report to NVidia to update the driver for the new 64 bit exe.

zondabmw.5490:

if your driver for NVidia is crashing do these 2 things.

1. submit a ticket into anet
2. Submit a bug report to NVidia to update the driver for the new 64 bit exe.

ANet will tell you to downclock your hardware if it’s overclocked (even factory overclocked) as GW2 is overly sensitive to overclocking. Downclocking my video card fixed the crashing problem for me. Otherwise they will tell you to either upgrade to the newest and/or beta driver, OR downgrade your driver to a known more stable version like 347.88…or they will tell you to lower your graphics setting in GW2. The problem with this error is that there is no set thing that seems to trigger it and it has been a thorn that has affected nVidia cards from atleast the 400 series, right up to the Titans.

“Display driver nvlddmkm stopped responding and has successfully recovered”, look familiar?

nVidia will tell you similar things, except they will go one step further and sometimes ask to see your system specs using an application called Speccy. Then they will recommend hardware configurations that might cause issues as well as software/services that are running that can cause issues. They will also tell you right out (If you ask them) that many companies, eVGA for example, overclock their cards too aggressively and can cause instabilities.

This is copied from nVidia’s support forum.

—SNIP—
“Turn off the Windows 10 Driver updating. <——-Does not work for some.
Defer the Windows 10 Driver updating.

Turn off FAST BOOT in the POWER OPTIONS.

Download DDU:
Install
run it
Enter Safe mode
Uninstall all the NVIDIA software and Drivers
Clean and Restart
Download this 347.88 driver
Run it
Select CUSTOM Install
Uncheck EVERYTHING except Geforce Driver and PhysX <——————-Important
Check the CLEAN INSTALL box
Finish install
Reboot"
—SNIP—

None of this worked for me. Over the course of fighting this error for nearly 3 years, I’ve done dozens of different combinations of settings and hardware configurations, reinstalled Windows, replaced my RAM, monitor, keyboard and mouse, unplugged all unneeded peripherals and killed all unneeded background processes and nothing worked….until I downclocked the video card and have not had a crash since.

https://forum-en.gw2archive.eu/forum/support/support/Crash-to-blank-screen-with-sound-SOLVED/5755714

I started having this problem with GW2 around late Dec of 2012 to early Jan 2013 and the first time I reported this problem to ANet, after fighting with the place I bought the system, nVidia and eVGA, exhausting hardware alternatives, was Jan/Feb of 2013. To be very clear, if I had of listened to kirito.4138 at the time, and downclocked my GPU, I likely would have saved myself A LOT of headache and hundreds of dollars in hardware and service fees, but I was stubborn and absolutely refused to downclock my brand new hardware.

My original thread in the support forums
https://forum-en.gw2archive.eu/forum/support/support/Crashing-problems/1264339

So, it is a problem with GW2, and something with how it’s using the nVidia hardware. It randomly affects people, it has been a problem for nearly 3 years and not likely it’s going away any time soon. So best try to other alternatives rather than counting ANet to fix it.