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.

    What's eating my battery?

    Discussion in 'Windows OS and Software' started by Syberia, Apr 3, 2012.

  1. Syberia

    Syberia Notebook Deity

    Reputations:
    596
    Messages:
    1,611
    Likes Received:
    1
    Trophy Points:
    56
    My laptop died in class tonight after about an hour and a half. Normally it lasts on the high end of 2-3 hours, more if I'm careful. Checking task manager, there was a constant 20-25% usage across all 8 threads, attributed to DotNETfx. Pausing the .NET framework service took CPU load back down to 1-2% where it usually idles. This is an almost new install of Windows, with the same software I was using before and I never had this issue until now.

    What can I do to fix this? Disabling services is not a permanent solution.
     
  2. tijo

    tijo Sacred Blame

    Reputations:
    7,588
    Messages:
    10,023
    Likes Received:
    1,077
    Trophy Points:
    581
    If i remember correctly, i read something about some .net process taking a good chunk of CPU power at the beginning with a clean install then things getting back to normal until the next clean install after a little while once it's finished doing whatever it was doing. I'll try to see if i can find that info again.

    Take it for what it is though, a foggy memory.

    EDIT: Not the same process, but here's what i was talking about: http://blogs.msdn.com/b/davidnotario/archive/2005/04/27/412838.aspx. In the end it wasn't related to a clean install, but to .net updates/new install.
     
  3. Syberia

    Syberia Notebook Deity

    Reputations:
    596
    Messages:
    1,611
    Likes Received:
    1
    Trophy Points:
    56
    That is the offending process. I saw the DotNETfx in the far right column. I suppose I'll leave it powered on tonight and hope it's done by tomorrow. It did just install about 70 updates last night so I suppose this is to be expected.


    ...but do you know how utterly inconvenient it is to type out notes on a phone?
     
  4. tijo

    tijo Sacred Blame

    Reputations:
    7,588
    Messages:
    10,023
    Likes Received:
    1,077
    Trophy Points:
    581
    I got a pretty good idea. :p

    At least you found what the problem was and it wasn't gremlins. ;)
     
  5. ScuderiaConchiglia

    ScuderiaConchiglia NBR Vaio Team Curmudgeon

    Reputations:
    2,674
    Messages:
    6,039
    Likes Received:
    0
    Trophy Points:
    205
    Most likely you are suffering the pains of having just applied a .Net service pack. A soon as you do that, the .Net library app does some major cleanup or recompilation of the libraries, I don't remember the specifics. But it is a one time event that will consume a lot of cpu use until it finshes. Once it is done the issue goes away. (At least until the next .Net service pack comes out.)

    Edit: I see tijo pointed you to an article with much more specifics of what I was referring to.

    Gary