So I recently got a new Lenovo IdeaPad 330 with a GTX 1050, working and compiling CUDA 10.1 samples in Visual Studio 2017. It worked and I was able to compile and run the CUDA 10.1 demos nicely. I used VS2017 to open and compile the CUDA Smoke Particle demo then ran it to get a reportedly 173.5 fps. It looked smooth enough but that fps looked too high. Anyway after configuring the rest of the new system and a few restarts I loaded VS2017 to test CUDA again. However something had changed in my video configuration as I could no longer use the Nvidia card’s acceleration. Here’s what I did firstly to get the system up and running:
1 Installed Microsoft Visual Studio Community 2017.
2 Installed Nvidia’s CUDA 10.1.105 package.
3 Opened GeForce Experience and installed the GeForce Game Ready Driver 425.31 package.
4 Compiled the CUDA demo in Visual Studio 2017 using (retargeting) Windows SDK Version 10.0.15063.0.
This worked at first but after a couple of restarts the drivers seemed to have rolled back and stopped functioning correctly. Device manager reports everything as fine with the card and VS2017 still compiles CUDA samples but there’s no access to 3D acceleration. Also the Nvidia Control panel fails to load and just closes itself down. The CUDA demos now freeze on the first frame.
Maybe the drivers aren’t stable for the Lenovo implementation of the GTX 1050 but it was working fine earlier. I don’t suppose anyone has come across this or know what can be done.