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.

    Asus G1S 8600M GT PCI-E x16 @ x1 problem

    Discussion in 'Asus' started by Arbalester, Jan 21, 2009.

  1. Arbalester

    Arbalester Newbie

    Reputations:
    0
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    5
    Hello,

    I guess I've had this problem since last month. At first I noticed a drop in fps when running 3DMark06. Fps dropped from about 26 to 16 fps at certain point (about 40 % less than normal). Total score with standard settings (1280x1024) went down aproximately from 4000 to 2600. At that time I wasn't aware of PCI-E speed being the reason. Restart didn't resolve the problem but the problem disappeared after the notebook was off for a long time.

    Now the problem seems to be constant. Sometimes after long shut down state the PCI-E speed might be x8 but that's gone if restarted.

    I've done over- and underclocking with RivaTuner witch might contribute to the problem. I've also made some modifications, including buying ZM-NC1000, changing thermal paste to CPU and GPU and drilling holes in the bottom of the case (where the internal GPU heatsink is beneath), to fight G1S' heat issues (so it's goodbye for warranty).

    I've tried several GPU drivers, reinstalled Vista (32bit) and currently running newest stock drivers available.

    I wonder if RivaTuner could have messed Video BIOS. I've checked if it's possible to flash it but every nvflash version from 5.31 to 5.72 seems to say:
    "EEPROM ID (20,00) : Unknown
    ERROR: Supported EEPROM not found"

    I haven't bothered trying every single version of nvflash because the documents (from 5.31 to 5.72) don't include "Dev=(20,00)" ("Dev=(20,05)" being to closest one). I wonder if I'm correct about the relationship between "EEPROM ID (20,00)" and "Dev=(20,05)".

    NVidia control panel shows Video BIOS version as 60.84.41.00.12. I've checked GPU information with NVidia control panel, GPU-Z and Everest. Is it a concern that neither nvflash, GPU-Z nor NiBiTor can read VBIOS correctly on G1S? Everything seems to be fine but that PCI-E speed. What could be the next move?
     
  2. King of Interns

    King of Interns Simply a laptop enthusiast

    Reputations:
    1,329
    Messages:
    5,418
    Likes Received:
    1,096
    Trophy Points:
    331
    Try to revert to the original drivers that came with your machine. At least you will know its a problem that can or can't be fixed with default settings etc.
     
  3. Arbalester

    Arbalester Newbie

    Reputations:
    0
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    5
    I actually reinstalled Vista one time with only drivers from the driver CD that came with the notebook. It didn't resolve the problem which was confirmed by GPU-Z information and 3DMark06 tests.

    Thanks for quick reply thought. Any ideas are welcome.
     
  4. Arbalester

    Arbalester Newbie

    Reputations:
    0
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    5
    I tried this: http://forum.notebookreview.com/showthread.php?t=261929 but only "PerfLevelSrc" can be found in registry and that's "2222". So PowerMizer is not installed? :confused:

    GPU-Z shows all the time:
    GPU Core Clock: 475 MHz​
    GPU Memory Clock: 700 MHz​

    In fact I noticed clocks being stuck like this when using RivaTuner before any Vista reinstallation but thought aero wanted all the power and it's OK :eek:

    Can PowerMizer affect PCI-E bus? If it could, it's definitely worth trying to get it working but how? And still if anyone has flashed successfully G1S' VBIOS, please tell how.
     
  5. Arbalester

    Arbalester Newbie

    Reputations:
    0
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    5
    This one's solved by RMA. There was something wrong with motherboard.