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.

    Problems with Nvidia Inspector

    Discussion in 'Gaming (Software and Graphics Cards)' started by InternetCliche, Feb 3, 2013.

  1. InternetCliche

    InternetCliche Notebook Enthusiast

    Reputations:
    0
    Messages:
    11
    Likes Received:
    0
    Trophy Points:
    5
    I have a sager np9150 with a gtx 670mx. From day one, nvidia inspector has always given me an unhandled exception, attempted to divide by zero. Any idea what could be causing this? Googling resulted in threads in other languages that ended without solutions. If i close the message, it keeps popping up.

    Pastebin of error: See the end of this message for details on invoking just-in-time (JIT) debuggi - Pastebin.com

    Also, how would I increase the max OC of the card? It runs stable and cold(71 C max) at the stock +135.
     
    InternetCliche, Feb 3, 2013
    #1
  2. the nightfly

    the nightfly Newbie

    Reputations:
    0
    Messages:
    8
    Likes Received:
    0
    Trophy Points:
    5
    I'm having the exact same problem on a similar machine. One site suggested that the problem might lie with inspector being set to use .NET framework 2.0, while the Sager uses a later, incompatible version (4.5).

    I'd still like to know if anyone found a workaround for this.
     
    the nightfly, Feb 8, 2013
    #2
  3. Lumpiersorz

    Lumpiersorz Newbie

    Reputations:
    0
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    5
    I'm having the same issue and it's pissing me off. I really need nvidia inspector because MSI afterburner keeps overclocking the wrong P states so all of the sudden i'm standing there with 324 mhz in a game -_-.

    Furthermore MSI afterburner doesn't seem to be able to detect the driver version i'm using.
     
    Lumpiersorz, Feb 10, 2013
    #3
  4. InternetCliche

    InternetCliche Notebook Enthusiast

    Reputations:
    0
    Messages:
    11
    Likes Received:
    0
    Trophy Points:
    5
    I can't even install an earlier .net. Windows doesn't let me.

    Can anyone help? This is really starting to me off. Windows features shows .net 3.5 sp1 enabled. WHY DOESNT IT JUST USE THAT.
     
    InternetCliche, Feb 10, 2013
    #4
  5. HTWingNut

    HTWingNut Potato

    Reputations:
    21,580
    Messages:
    35,370
    Likes Received:
    9,878
    Trophy Points:
    931
    I'm getting it now too. :mad:

    edit: I was able to make changes from the command line, the vRAM change took place but GPU speed did not. grr.

    edit edit: apparently it's due to the vBIOS I'm using.
     
    HTWingNut, Feb 17, 2013
    #5
  6. InternetCliche

    InternetCliche Notebook Enthusiast

    Reputations:
    0
    Messages:
    11
    Likes Received:
    0
    Trophy Points:
    5
    It shouldn't be a vBios proble for me - I haven't messed with that. (though i want to - increase max oc)
     
    InternetCliche, Feb 17, 2013
    #6