Windows Forum

Ask something
Discussion Locked

Virtual Memory Errors 500hours CPU time

0 helpful
7 replies

by cenedra

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have a windows 2000 domain and currently have around 120 extra machines that are up, but not used, All of which display virtual memory errors after about 500 hours (or just less) CPU up time.

I believe that there was some issue with windows 2000 that caused this, but cannot now find any reference to this.

Obviously a reboot clears the error, but with our setup an automated regular re-boot is something we'd like to avoid.

Any Ideas or has anyone got a similar issue?

7 replies

by cactus pete

It may not be Windows, but some other management software that is common to all the builds. Either way, try using perfmon to determine where the memory leak is. Something may be spawning more and more working threads and failing to release them when done...

by sgt_shultz

well, first thought is: virus. if you feel safe about that..
you are not giving us much to go on. but make sure device manager looks ok. no bangs or yellow question marks you can't explain. have a look at event viewer. the problem is probably either older version software that needs updating or maybe bad driver. get yourself a test machine. 500 hours is long time to wait for error. find another way of testing for leaks (performance monitor?)then and update all the drivers to latest greatest. then disable stuff running in the background wholesale until you get rid of error, then add stuff back in...look for culprit in anti-virus software or 'pc-doctor' type software.
what protocols are you running?
did this ever used to work? what changed?

by cenedra

Perfmon has failed to show anything in partuicular up, but we're living with it for the moment - we've got one desktop with perfmon running constantly so we'll see where that gets us

by sgt_shultz

well, first thought is: virus. if you feel safe about that..
you are not giving us much to go on. but make sure device manager looks ok. no bangs or yellow question marks you can't explain. have a look at event viewer. the problem is probably either older version software that needs updating or maybe bad driver. get yourself a test machine. 500 hours is long time to wait for error. find another way of testing for leaks (performance monitor?)then and update all the drivers to latest greatest. then disable stuff running in the background wholesale until you get rid of error, then add stuff back in...look for culprit in anti-virus software or 'pc-doctor' type software.
what protocols are you running?
did this ever used to work? what changed?

This discussion is closed to new replies.