CPU Usage Alarms

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • David Burstin

    CPU Usage Alarms

    Whenever I run VS.NET 2003, my CPU usage sits on 100%,
    with total memory usage at 330MB. The CPU stays at 100%,
    even before any projects are opened (on the start page)
    and for the rest of the session. This somehow leads to me
    getting system alarms from my motherboard.

    Is there something running in the background which takes
    up all this CPU time? An option which could be turned off?

    I am running a Pentium IV 2.0 Ghz processor on a Gigabyte
    motherboard with 256 MB RAM and 40 GB HDD.

    Any suggestions would be appreciated.
  • 4Space

    #2
    Re: CPU Usage Alarms

    You didn't say whether or not it was the Visual Studio process that was
    eating all the processor time. It would also suggest that the cooling needs
    attention in the case. Any PC should be able to run at 100% CPU
    indefinitely.

    Cheers,

    4Space

    "David Burstin" <burstin@bigpon d.net.au> wrote in message
    news:1e6a01c33e cb$58619820$a60 1280a@phx.gbl.. .[color=blue]
    > Whenever I run VS.NET 2003, my CPU usage sits on 100%,
    > with total memory usage at 330MB. The CPU stays at 100%,
    > even before any projects are opened (on the start page)
    > and for the rest of the session. This somehow leads to me
    > getting system alarms from my motherboard.
    >
    > Is there something running in the background which takes
    > up all this CPU time? An option which could be turned off?
    >
    > I am running a Pentium IV 2.0 Ghz processor on a Gigabyte
    > motherboard with 256 MB RAM and 40 GB HDD.
    >
    > Any suggestions would be appreciated.[/color]


    Comment

    • David Burstin

      #3
      Re: CPU Usage Alarms

      Thanks for your reply.
      It is the Visual Studio that is using all the processor
      time. It holds 99%, all other processes make up the
      remaining 1%. Also, the fan is running at normal speed,
      and I can't work out why it is setting off the
      motherboard alarms. It might be a memory alarm, as VS.NET
      has twice increased the virtual memory allocation. BTW -
      it is VS.NET 2003 running the comapct framework
      (including emulator).
      All I know is that stopping VS.NET stops the alarms
      instantly.

      Comment

      Working...