Posts by Mani
|
1)
(Message 6765)
Posted 3 Jun 2020 by Mani Post: Hi! That I already found out though experience but does not help with preventing it. |
|
2)
(Message 6669)
Posted 12 May 2020 by Mani Post: Hi! Sorry for the long delay. What driver are you using? And it is not that I can not run any asteroid jobs, but that some jobs will cause Windows 7 to decide that the driver is not responding and forces a reset. As I said, this causes my desktop to be screwed up and Nvidia GeForce Experience not to be able to access the driver to display card information or access video recording settings or perform video recordings. |
|
3)
(Message 6612)
Posted 27 Apr 2020 by Mani Post: An update. I went into Nvidia GeForce Experience to reset my video recording before going in-game and it couldn’t even access information about the card now. |
|
4)
(Message 6611)
Posted 27 Apr 2020 by Mani Post: Hi! I started running asteroid jobs again after seeing the new CUDA102 application was released notice and things seemed to be going fine for a while. Then I got a “Display driver nvlddmkm stopped responding and has successfully recovered.” message from Windows again. This causes problems with some visual elements on my desktop and prevents me from recording in-game content until I turn off video recording and then turn it back on again, which is a hassle. If this continues to happen, I’ll have to stop accepting asteroid jobs again. Any suggestions? |
|
5)
(Message 6559)
Posted 14 Apr 2020 by Mani Post: Hi! I seem to be having this same problem running the asteroid app. At least in some cases, the app will start running and then Windows will detect that the video driver has stopped responding and restarts it. This stops the app from continuing and it apparently just sits there until the next project swap time. I have seen an elapsed time of 1:30 and the app is only at 0.010% done. I have recently updated to an EVGA GTX 1660 XC Gaming (06G-P4-1163). |