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.

    Dramatic loss in FPS for no apparent reason. NP2090

    Discussion in 'Sager and Clevo' started by PercocetPenguin, Apr 10, 2008.

  1. PercocetPenguin

    PercocetPenguin Notebook Enthusiast

    Reputations:
    3
    Messages:
    30
    Likes Received:
    0
    Trophy Points:
    15
    Hey all, when I recently re-installed WinXP on my np2090 two days ago, I was getting 25fps in Crysis.
    Now, I'm getting 5fps in Crysis.
    The only difference is I've installed steam and some steam games, but steam isn't even running while I'm playing Crysis.
    My drivers are the same, the clock speeds on my card are the same, I really have no idea what cut my fps so dramatically.
    Any ideas? I really prefer not having to reinstall my OS every few days to get playable fps in Crysis.

    Edit: Oh yea, and my settings in Crysis are the same.
     
  2. Shyster1

    Shyster1 Notebook Nobel Laureate

    Reputations:
    6,926
    Messages:
    8,178
    Likes Received:
    0
    Trophy Points:
    205
    Have you checked to see if the steam updater is starting up automatically and running in the background? Use the task manager or the adminitrative controls utility to see whether or not any of the steam processes are starting automatically.
     
  3. PercocetPenguin

    PercocetPenguin Notebook Enthusiast

    Reputations:
    3
    Messages:
    30
    Likes Received:
    0
    Trophy Points:
    15
    Nope, steam is completely out of the picture.
     
  4. pjriot

    pjriot Notebook Enthusiast

    Reputations:
    6
    Messages:
    24
    Likes Received:
    0
    Trophy Points:
    5
    I ran across something similar in a Rock notebook I had lately but I noticed slowdowns booting too. In my case my secondary IDE controller (the one the HDD is attached to) had switched itself to PIO mode instead of DMA mode 5. Go into device manager and right click properties on yours. If its the same story then just uninstall the controller from the device manager and restart. Note, if the PIO mode persists after rebooting (or it happens a few reboots later) back your stuff up and save up for a new hard drive!

    If it isn't that then (probably more likely to be honest) its probably a software issue. That means update ad-aware, spybot, stinger and your av software, check your process list against google (task manager is usually good enough but you may want to run hijack this) and get scanning.

    EDIT: Actually it was quite apparent the hdd was the cause of the issue in the first case as the drive light was going crazy trying to load textures for bf2142 etc.
     
  5. PercocetPenguin

    PercocetPenguin Notebook Enthusiast

    Reputations:
    3
    Messages:
    30
    Likes Received:
    0
    Trophy Points:
    15
    I fixed it by changing my video driver to 174.82.
    Although I don't get why there was such a dramatic change without changing anything.
     
  6. Shyster1

    Shyster1 Notebook Nobel Laureate

    Reputations:
    6,926
    Messages:
    8,178
    Likes Received:
    0
    Trophy Points:
    205
    If you feel up to experimenting, uninstall the 174.82 driver then do a fresh install of the other driver you were using before and see if the problem persists. It's possible that one of the games you d/l-ed monkeyed with the driver (either innocently or intentionally, who knows) and left it the worse for the wear.

    Keep in mind (I'm sure you do, but I like to hear myself type :D ) that you need to uninstall a driver before you either install a new one or re-install the old one - if you don't and you attempt to re-install the old driver, a part of the driver that is malfunctioning because its corrupted may not actually get replaced with a clean copy if the installer "sees" that it's still there and is designed to not overwrite pre-existing components.