win2k console lockup

[Guest]

My o/s is windows 2000 server (sp4). This is a member server in an active
directory domain. My problem is this: every 7 to 10 days the console becomes
"locked up" with a windows 2000 image on a black backgound. Movement from
the mouse or keyboard will not "wakeup the pc" or return it to a desktop or
login screen. The server is still available to connect to as a shared
resource on the local network. The DOS app that is served out to the network
is still available and working fine. The server can be browsed to over the
local network and shares opened and written to. I can ping the server and
get a reply back ok. The server can NOT be connected to via RDP. There are
several backup tasks configured to run in the scheduled tasks but they no
longer start. These are robocopy batch files backing up to a locally
connected usb external drive. The event logs seem to stop recording any
events. The only way to regain control of the console is to reboot the
server. It will then run fine for another 7 to 10 days when the problem
occurs again. Any suggestions would be appreciated.

 

[Dave Patrick]

Could be something is memory leaking up to the point of the lockup. You can
use Task Manager and or Performance Monitor to see what is consuming the
mem/ cpu. A consistently positive "Mem Delta" value may indicates a memory
leak.


--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| My o/s is windows 2000 server (sp4). This is a member server in an active
| directory domain. My problem is this: every 7 to 10 days the console
becomes
| "locked up" with a windows 2000 image on a black backgound. Movement
from
| the mouse or keyboard will not "wakeup the pc" or return it to a desktop
or
| login screen. The server is still available to connect to as a shared
| resource on the local network. The DOS app that is served out to the
network
| is still available and working fine. The server can be browsed to over the
| local network and shares opened and written to. I can ping the server and
| get a reply back ok. The server can NOT be connected to via RDP. There
are
| several backup tasks configured to run in the scheduled tasks but they no
| longer start. These are robocopy batch files backing up to a locally
| connected usb external drive. The event logs seem to stop recording any
| events. The only way to regain control of the console is to reboot the
| server. It will then run fine for another 7 to 10 days when the problem
| occurs again. Any suggestions would be appreciated.

 

[lforbes]

Could be something is memory leaking up to the point of the
lockup. You can
use Task Manager and or Performance Monitor to see what is
consuming the
mem/ cpu. A consistently positive "Mem Delta" value may
indicates a memory
leak.


--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| My o/s is windows 2000 server (sp4). This is a member
server in an active
| directory domain. My problem is this: every 7 to 10 days
the console
becomes
| "locked up" with a windows 2000 image on a black backgound.
Movement
from
| the mouse or keyboard will not "wakeup the pc" or return it
to a desktop
or
| login screen. The server is still available to connect to
as a shared
| resource on the local network. The DOS app that is served
out to the
network
| is still available and working fine. The server can be
browsed to over the
| local network and shares opened and written to. I can ping
the server and
| get a reply back ok. The server can NOT be connected to via
RDP. There
are
| several backup tasks configured to run in the scheduled
tasks but they no
| longer start. These are robocopy batch files backing up to
a locally
| connected usb external drive. The event logs seem to stop
recording any
| events. The only way to regain control of the console is to
reboot the
| server. It will then run fine for another 7 to 10 days when
the problem
| occurs again. Any suggestions would be appreciated.

Hi,

When I had this problem it turned out to be faulty RAM in my server.
Did you upgrade it recently? When I replaced the faulty RAM the
problem went away.

Cheers,

Lara