Update 2

Waited a couple versions or so, can confirm issue is now gone in 376.33. Tested on a Dell XPS 15 with a 960M.


This issue seems to be only on the M - MX family. Desktop GPUs aren't affected.

Due to the influx of the "Blender is lagging" posts, I'm going to pin this on the main site until the issue is resolved, and our close-votes review queue calms down. From what I've seen only 2.78 users are posting but it might affect other versions as well.

See Blender 2.78 with Windows 10 lags when interacting with the UI and the official release thread for the driver is here https://forums.geforce.com/default/topic/978895/geforce-drivers/official-376-09-game-ready-whql-display-driver-feedback-thread-released-11-28-16-/1/

DO NOT UPDATE TO Official 376.09 Game Ready WHQL Display Driver (Released 11/28/16).

If you have already, the best "fix" is to rollback to your previous working driver, personally 375.95 seems to be a good version in the same month. If for some reason you can't do this, open the NVIDIA control panel and force Blender to use the intel chipset, if you have that option (not recommended as you might see flickering).

  • $\begingroup$ What's the correct response to all the lag questions? Close as off-topic because it's a driver issue or answer one and merge all the duplicates into that? $\endgroup$ Dec 9 '16 at 17:11
  • $\begingroup$ @RayMairlot We support hardware type questions to an extent now remember, the latter is what was done and is recommended. Also there is a new driver out that I should test and see if the issue was resolved. $\endgroup$
    – iKlsR
    Dec 9 '16 at 17:14
  • $\begingroup$ We support hardware questions? Have you got a link to a meta question regarding this? $\endgroup$ Dec 9 '16 at 17:20
  • $\begingroup$ @RayMairlot Woops, I meant to say performance, kinda interleaves but yeah as detailed here meta.blender.stackexchange.com/questions/354/… one post for any widespread issue as a canonical post or answer and link to that. $\endgroup$
    – iKlsR
    Dec 9 '16 at 17:28
  • 1
    $\begingroup$ Just leaving this as reference link to the original question in case one needs to close as duplicate blender.stackexchange.com/questions/68311/… $\endgroup$ Dec 12 '16 at 0:33
  • $\begingroup$ To clarify, by M - MX family you mean the mobile GPUs, not workstation-class Maxwell architecture GPUs which are also prefixed with an m. $\endgroup$
    – PGmath
    Dec 23 '16 at 23:54
  • $\begingroup$ @PGmath yes, mobile $\endgroup$
    – iKlsR
    Dec 24 '16 at 1:10
  • $\begingroup$ I am using NVIDIA's graphics driver v376.54, and the problem was still there for me. I removed the driver and Blender is running smooth. The problem is still here guys. $\endgroup$ Feb 17 '17 at 20:31
  • $\begingroup$ @AfzaalAhmadZeeshan Maybe update to latest? 378 here working fine. $\endgroup$
    – iKlsR
    Feb 20 '17 at 19:24
  • $\begingroup$ @iKlsR, works like a charm. :-) $\endgroup$ Feb 20 '17 at 23:12
  • $\begingroup$ the problem is still occuring in 397.93 version, using 2.78b I hope they will deal with this in 2.80, i'm using gt755m $\endgroup$
    – royor
    May 26 '18 at 20:07
  • $\begingroup$ What is this post doing on meta? $\endgroup$
    – Nicola Sap
    Dec 12 '18 at 16:32
  • 1
    $\begingroup$ @NicolaSap There was a bug in a Nvidia driver and we were getting flooded with questions related to it. It served as a place to point users to since it could be seen in the sidebar on the main site. $\endgroup$
    – iKlsR
    Dec 13 '18 at 15:04

You must log in to answer this question.

Browse other questions tagged .