I don't think that's it. My coworker has an identical hardware setup and he says he's never had this problem. And anyways, I work for a small company, and we don't have any extra graphics cards to swap in.
It happens to ours sometimes when in a command and moving over civil points with the point style as the X inside the O (pdmode 35). If OSMODE is 107 (end mid nod int ins) it looks like acad tries to calculate every endpoint, intersection, midpoint etc. on every point symbol. The farther zoomed out and the closer the points are to eachother the slower it goes. I usually toggle F3 to turn off osnaps when rolling over stuff like this. That or turn off some of the osnaps.
I found that simply turning off some of the osnap settings (intersection in particular for some reason) and turning off "selection preview when a command is active" in the options has solved this issue. I haven't experienced this crash since adjusting these two things.
Hope it helps you too.
1. If any antivirus running just stop all of its services by using services.msc command.
2. Update display drivers from the chipsets home site and not from the drivers CD/DVD came with it.
I know this is an old post, but I was having the same issue in Civil 3D2015. The only previous solution I could find was to turn off my osnaps, which was a real nuisance since you need them for most everything. I tried the other suggestions in this post and they did not for me. I found that by turning off the apparent intersection osnap, this glitch improved but did not go away entirely. Turning off the intersection & apparent intersection eliminated it completely. At least now I only have to manually snap to intersections instead of all snap options..............
Access a broad range of knowledge to help get the most out of your products and services.