Q:
Blackscreen/Reboot
A:
Hey, was having the same issue as you for a while. You’ve got better specs on me in everything, but we share the same graphics card. My crashes started out as a black screen after about 3-4 hours of playing, sometimes just rebooting my system for me, sometimes just hanging on the Black screen for 3-5 secs then coming back to my desktop with GW still running minimized.
Gradually problem got worse over time – crashing after 30-60 min in world, 5-10 in every dungeon. Event viewer/bug checks always pointed towards nvidia driver when it pointed anywhere at all – most of the time it didn’t tell me much of anything.
From what I know this kind of black screen locking up without a BSOD (esp given that at times I could return to GW in the bar after a long pause and stutter) is your card performing a memory dump.
I began by rolling back my driver to 314 – didn’t help. I rolled my driver back to 306 – made the whole system much more unstable. I reinstalled windows and tried 314 again – same problem.
In the end what I had to do was install the 320.49 driver (last driver having any changes with the 660 in mind). After that world seemed more stable, but I always still crashed in dungeon after 5-10 min. Finally, i bit the bullet and under clocked with Evga Precision (MSI afterburner and several other utilities can also do it). The underclocking will not harm your system, it made GW run better in all aspects for me, and you can easily revert to default clocking in the program outside of GW while playing something else. It’s all managed in the utility.
Underclock yourself by 100 GPU and 10 Mem. Let the program run in the background while you play.
Also worth looking into is if your Intel Raid driver is up to date – for my gf, this seems to have been her problem with crashes. They released a new driver last month. intel link
Finally, google the program “Who crashed” – it is a much better program for investigating driver related crashing and is much more of a help than event viewer.
Thanks for the post, Milkduds. I will try that when I get home from work today and see what happens.
So I tried as recommended above, however, it seems I have to underclock at least by 150MHz and 20 mem. Though it rebooted once at those levels, so I underclocked to 175 and 25, and so far, so good.