Windows 2000 SP4 server.... reboot issue

Discussion in 'NZ Computing' started by Simon, Jan 21, 2004.

  1. Simon

    Simon Guest

    I have a server with Xeon 2.4Ghz processor, 4GB RAM, 60GB HDD and it
    runs no programs, only 2 additional services.

    The 2 services related to Text-to-speech software called Speechify.

    Over the past couple of months the server has been rebooting itself
    every few days.

    In the Event Viewer the sequence of events leading to an unplanned
    system reboot starts with an error with Event ID 2019. This error under
    Windows 2000 Server is documented at
    http://www.jsiinc.com/SUBO/tip7100/rh7141.htm - this problem can occur
    if you have an Intel network adapter and you do NOT have the latest
    driver. "Previous drivers leaked memory, causing the subject behavior.
    Subsequent errors in the Event Viewer related to insufficient memory
    resources being available", despite a physical memory resource of 4GB,
    which indicates to me a severe memory leak.

    The latest drivers for both the 100Mb and 1000Mb Intel NIC's (standard
    on the server) were updated with drivers dated December 2003, where the
    previous drivers were dated March 2003.

    However, this has NOT solved the problem and the server continues to
    reboot randomly. There is no pattern to the timing of the reboots,
    except that they are every 4-7 days.

    I am thinking of going down the track of a memory management tool for
    the machine. Any suggestions on which one? Any other suggested courses
    of action?
     
    Simon, Jan 21, 2004
    #1
    1. Advertisements

  2. No experience with *real* servers but I had the same problem with another
    machine and the PSU turned out to be the culprit. It would power off,
    usually when accesing network resources via explorer (I really never
    bothered to track exactly what) and restart.
     
    Damien McBain, Jan 21, 2004
    #2
    1. Advertisements

  3. Simon

    Simon Guest

    But there are events messagees immediately prior to the reboot
    suggesting that the system is out of memory.
     
    Simon, Jan 21, 2004
    #3
  4. Simon

    atec77 Guest

    install one of the logging tools and start reading , it sounds like
    something is not releasing memory , in which case the machine will
    reboot auto magically , use a memory manager like fixit (your choice)
    and tag the logs for reading until you do actually diagnose the leak,
     
    atec77, Jan 21, 2004
    #4
  5. Simon

    AD. Guest

    I doubt it's the NIC drivers, I've seen that message before on machines
    without Intel NICs. There could be any number of other reasons for it.

    One of our servers had that a few weeks ago (during the xmas break), and
    it just caused a major slowdown that a reboot fixed. The server had spare
    memory left - it seems to be a memory allocation rather than exhaustion
    problem.

    Good luck!

    Cheers
    Anton
     
    AD., Jan 21, 2004
    #5
  6. Or, a quick, simple and easy test to make sure it's not hardware problem,
    swap your memory sticks for ones that are working and see if the problem
    persists.

    Another idea is the power supply. It may be on its last legs.
     
    R Green - WoWsat.com, Jan 21, 2004
    #6
  7. Simon

    Gib Bogle Guest

    What is Task Manager showing is happening to the memory usage over time?

    Gib
     
    Gib Bogle, Jan 22, 2004
    #7
  8. Yep, the PSU aint just a switched transformer, it's controlled by the
    system, hence my previous suggestion (it's also one of the cheapest things
    to replace, a good 400w Antec for $100ish).
     
    Damien McBain, Jan 22, 2004
    #8
  9. Simon

    Guest Guest

    $100 here, $100 there, pretty soon it adds up to real money. It would be nice
    to have a real indication it's the P/S before shelling out the dough. Maybe
    borrowing one from another system for a test...
     
    Guest, Jan 22, 2004
    #9
  10. Having a spare PSU, especially with a server, is always a good idea.
     
    T.N.O. - Dave.net.nz, Jan 22, 2004
    #10
  11. Simon

    E. Guest

    Check your services and see if any are set to reboot after a failure or
    subsequent failure.
    E.
     
    E., Jan 23, 2004
    #11
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.