02-19-2014 11:00 PM
Hey guys. I've been using my Y580 for a little more than a year now and I absolutely loved it. Recently though, my graphics card has completely dissappeared. This happened after playing an hour or so of Titanfall (which ran really well) and attempting to update my nvidia drivers. I was not able to update the installation using both Geforce Experience and manually. While downloading manually, I noticed that their website was not able to detect my graphics card. I then checked the device manager and all I could see was the Intel card. Later on, the Nvidia control panel was also unable to detect the card.
I decided to uninstall all my drivers and start again with the one on the Lenovo driver page. I was able to successfully download the driver and it made the 660 appear in the device manager. This did not solve my troubles because when I tried to play a game, the 660 dissapeared again. I then looked through the BIOS and I was also unable to find the card. Frustrated, I did a system restore to before I first downloaded the driver. Once again, the 660M briefly appeared again but dissapeared when I tried to game or update it.
I was just wondering if this is a software or hardware problem? Is there anyway I can fix it without sending it in for repairs (I'm not sure if I'm still under warranty anymore)?
Solved! Go to Solution.
02-20-2014 04:44 PM
It happens from time to time with my Y580. The way I fix it is that I turn it off in BIOS (switch to UMA graphics from Switchable graphics), let it run for a day only witn Intel GPU, then switch it back on in BIOS. Works 9/10 in my case, but rest assured, it will happen again.
02-21-2014 05:32 PM
02-21-2014 08:23 PM
02-22-2014 01:56 PM
Yup, that's your GPU. I've seen many people report problems with this GPU including me. From my experience it means it is dying and there's not a lot you can do. In my case it still works when I do it the way I described, but I decided to give up. I turned off the Nvidia GPU in BIOS and I'm buying a desktop
05-29-2014 10:56 AM
06-01-2014 09:00 PM
This is just a temporary fix. Once it started acting up, it's gonna do it again at some point. Then again, and again...