Forum Discussion
Try downclocking your core clock. You can do it using MSI Afterburner. If that doesn't work, either your card is overheating or it's dying.
You can also try doing a complete uninstall of the driver (which means also deleting all files related to Nvdia found in your hdd and registry) and then reinstalling only the graphics driver and the Physix driver.
There might be an issue with the IRQ priorities. If you have a dedicated sound card on board, it might be conflicting with the HD audio driver that is usually installed along with the graphics driver.
- 11 years ago
Yeah it seems to be a conflict with old realtek drivers at least according to people on the nvidia and sevenforums. I used to get the crash on my 590 gtx I had to revert to an old driver like 331.88 or something, any newer and it would crash, but there eventaully came a driver when it worked fine again, (if you use SLI try with only one card enabled). Now I don't have the 590 plugged in anymore but a 970 and it works great so far. (Also the vram on the 590 isn't enough to do anything really, it said 3gb vram, and I expected to be getting 3gb of vram, but since its build in SLI it only had 1.5gb useable vram(since it is split over both gpus), but they don't advertise that in the specs...
http://www.sevenforums.com/graphic-cards/126584-display-driver-nvlddmkm-stopped-responding.html
DA:I requires lots of vram at least if you're maxing the settings. On the second picture you can see it hitting above 3GB vram usage.
- 11 years ago
@Herethos wrote:Yeah it seems to be a conflict with old realtek drivers at least according to people on the nvidia and sevenforums. I used to get the crash on my 590 gtx I had to revert to an old driver like 331.88 or something, any newer and it would crash, but there eventaully came a driver when it worked fine again, (if you use SLI try with only one card enabled). Now I don't have the 590 plugged in anymore but a 970 and it works great so far. (Also the vram on the 590 isn't enough to do anything really, it said 3gb vram, and I expected to be getting 3gb of vram, but since its build in SLI it only had 1.5gb useable vram(since it is split over both gpus), but they don't advertise that in the specs...
http://www.sevenforums.com/graphic-cards/126584-display-driver-nvlddmkm-stopped-responding.html
DA:I requires lots of vram at least if you're maxing the settings. On the second picture you can see it hitting above 3GB vram usage.
http://imgur.com/i2jJBRm,juBto5l#0
It is an issue with the coding in the game. dot. period. end.
It cannot be fixed playerside. DOT. PERIOD. END.
however the game can be made somewhat more stable, and have a little more time between crashes with nvidia gpus, or slightly less stuttering with AMD using the mantle api.
DOT! PERIOD! END!
- 11 years ago
It only happened to me twice so far of the 60 hours of total gameplay. Just before the driver crashed, noticed the gameplay was really stuttering.
- 11 years ago
@Maevos wrote:Try downclocking your core clock. You can do it using MSI Afterburner. If that doesn't work, either your card is overheating or it's dying.
You can also try doing a complete uninstall of the driver (which means also deleting all files related to Nvdia found in your hdd and registry) and then reinstalling only the graphics driver and the Physix driver.
There might be an issue with the IRQ priorities. If you have a dedicated sound card on board, it might be conflicting with the HD audio driver that is usually installed along with the graphics driver.
It is an issue with the coding in the game. dot. period. end.
It cannot be fixed playerside. DOT. PERIOD. END.
however the game can be made somewhat more stable, and have a little more time between crashes with nvidia gpus, or slightly less stuttering with AMD using the mantle api.
DOT! PERIOD! END!
- 11 years ago
@Maevos wrote:Try downclocking your core clock. You can do it using MSI Afterburner. If that doesn't work, either your card is overheating or it's dying.
NOT TRUE. and Jinnrou, once you have 30 years of experience working on computers, and custom building gaming rigs, then by all means, I will have a little more respect for your train of thought as to what is dying.
Downclocking was suggested on page 4 of this entire forum, basically day 1 of release in the US... and has had no substancial impact on performance. Yes, the game doesn't do well with factory OC'd cards. period.
it just furthers the premise that the game needs to be re-coded for better performance and stability across all platforms.
You can also try doing a complete uninstall of the driver (which means also deleting all files related to Nvdia found in your hdd and registry) and then reinstalling only the graphics driver and the Physix driver. <<<which was my suggestion to begin with, but rather than doing a complete uninstall, my suggetions was to do a custom clean install, and only select the main driver, and physx.... my way insures all of the other unnnecessary nvidia drivers/software was certainly removed.
There might be an issue with the IRQ priorities. If you have a dedicated sound card on board, it might be conflicting with the HD audio driver that is usually installed along with the graphics driver.
all of the issues that people are having across all platforms with performance and crashes, is due to coding errors in the game which cannot be fixed by the end-user.
however, if you set your system to output the audio,
to 24 bit, stereo, 44.1 KHZ,
and the ingame audio settings to stereo/headphones
it does help with a minor increase to stability......
downclocking only gives a little more stability (with this game) as (once again) it IS A CODING ISSUE WITH THE GAME THAT CANNOT BE FIXED BY THE END USER!