The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    [GT60] [2OC] [770M] Cannot update to 320.xx driver

    Discussion in 'MSI' started by ddonuts4, Sep 6, 2013.

  1. ddonuts4

    ddonuts4 Notebook Enthusiast

    Reputations:
    39
    Messages:
    47
    Likes Received:
    0
    Trophy Points:
    15
    I recently received my new GT60 2OC, and immediately opened the GeForce experience app to check for driver updates. A driver update was available, so I clicked express installation. The installer ran for a bit, then said 'Cannot find compatible graphics hardware'. Since then, I have tried

    1. Using custom installation from the GeForce experience app
    2. Using an installer directly from NVidia
    3. Forcing all programs to run with the dedicated graphics processor
    4. Uninstalling all graphics drivers on the computer then attempting to install the 320.49 driver

    Is anyone else having this problem? Also, if anyone else is (or was), were you able to fix it?
     
  2. adriano_banano

    adriano_banano Notebook Consultant

    Reputations:
    4
    Messages:
    107
    Likes Received:
    13
    Trophy Points:
    31
    Unfortunately, Nvidia has messed up with the detection of GT60 & GT70 with 700m series GPUs. It seems that we are advancing a little, cause new drivers are at least "detected" by GeForce Experience (although they can't be installed yet).

    The current options you have are:

    1) Sticking with the 311.83
    2) Modify INF file of your system so you can install those 320.49
    3) Install beta drivers, since there no problem when you install them (you have to download them manually)
     
  3. ryzeki

    ryzeki Super Moderator Super Moderator

    Reputations:
    6,552
    Messages:
    6,410
    Likes Received:
    4,087
    Trophy Points:
    431
    As adriano_banano said, it's wrongly detected as a supported GPU on those drivers. Betas work so the best course is to ignore the message from the auto update and then install the newest once they are available.
     
  4. ZiggyDeath

    ZiggyDeath Notebook Enthusiast

    Reputations:
    16
    Messages:
    41
    Likes Received:
    2
    Trophy Points:
    16
    It goes a step even further than that. If you have a beta drivers installed, the GeForce Experience app will then correctly find workable drivers when they are released. For example if you install Beta 326.19, GeForce Experience will correctly detect that Beta 326.80 is the newest available driver.
     
  5. zipperi

    zipperi Notebook Deity

    Reputations:
    53
    Messages:
    741
    Likes Received:
    190
    Trophy Points:
    56
  6. ZiggyDeath

    ZiggyDeath Notebook Enthusiast

    Reputations:
    16
    Messages:
    41
    Likes Received:
    2
    Trophy Points:
    16
    The developer 326.84 and 326.98 both use older versions of Physx drivers compared to beta 326.80, as well as lacking several performance fixes introduced in 326.80. The lack of newer Physx drivers alone can cause performance issues - although you can patch it in using drivers containing a different revision.

    On top of that, I'm not sure whether or not the developer drivers are fully integrated into the GeForce Experience application like the beta drivers - given the OP's use of GFE, I would assume that he would want to have a lower maintenance setup.
     
  7. ddonuts4

    ddonuts4 Notebook Enthusiast

    Reputations:
    39
    Messages:
    47
    Likes Received:
    0
    Trophy Points:
    15
    Thanks for all your responses! I'll just mod the .inf if i need to then. I've done it on my old ASUS UL50Vt so I think i should be able to do it for the GT60 too. It's just changing a few lines of code, I believe.