1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

W2K shutdown problem

Discussion in 'Legacy Windows' started by VoodoU, 2004/01/29.

Thread Status:
Not open for further replies.
  1. 2004/01/29
    VoodoU

    VoodoU Inactive Thread Starter

    Joined:
    2002/06/05
    Messages:
    13
    Likes Received:
    0
    Hello all,

    I have installed w2k sp4 on a brand new machine here are the machine specs:


    MSI KM4M mainboard
    80 GB WD HDD
    256 MB PC3200 DDR SDRAM
    ATHLONXP 2600+ 333MHZ 512 KB cache With AMD fan
    SONY 52X CD-ROM
    Hewlet packard 5650 printer connected via USB
    There is also a WASP barcode scanner connected to the PS2 keyboard port, in-line with the KB.
    case is a TTGI 701 series with a 350 Watt power supply.

    W2K Service pack 4 (Updates after SP installed)
    norton systemworks 2003 (all up to date)
    MemTurbo
    No other system utilities running.

    What is happening: The computer will run for hours on end. After a period of nonuse it will shut down automatically.
    I have set the power profile in W2K to never shut anything down, not to enter sleep and not to hibernate(customers request). Yet it still shuts down. It only seems to do this after a period of nonuse...while using the computer it does not shutdown.

    It is not rebooting just shutting down and powering the tower off.

    It does not leave any kind of error log....it does not run a chkdisk on startup, as though it was properly shut down.

    Note: When first bringing the computer up I installed the printer via a parrallel cable on LPT 1, as soon as I installed the printer driver and the test page began to print the computer would shut off in mid-print. Upon rebooting it would run a chkdsk etc. How I solved this problem was to use an updated driver from HP. I completely uninstalled the old driver, connected the computer via USB instead of parrallel cable. The printer then printed fine and the computer did not shut down during printing and was used for hours afterwards.

    Any light that you all could shed on this for me would be a great help as I am at about my wits end!!:mad:

    Thanks
     
  2. 2004/01/29
    Newt

    Newt Inactive

    Joined:
    2002/01/07
    Messages:
    10,974
    Likes Received:
    2
    The fact that you mention hibernate (assuming it's available in the power settings) indicates an ACPI capable machine. But even though it's new, there may have been a BIOS problem with power management that was fixed with a BIOS update.

    Have you verified that you have the most recent version loaded?

    If you do, I'd suggest setting the PC to hibernate and then after it has done so once, reboot and set it not to hibernate. May shake loose a stuck setting of some kind that way.

    If that fails and the NIC has wake on lan as an option, you might try turning that on since it causes the PC not to be shut down quite as far as if it isn't enabled.

    Otherwise, it is a puzzle.
     
    Newt,
    #2

  3. to hide this advert.

  4. 2004/01/30
    TonyT

    TonyT SuperGeek Staff

    Joined:
    2002/01/18
    Messages:
    9,072
    Likes Received:
    400
    Try uninstalling the printer completely and see if shutdown issue still exists. If still exists, then cause is not the printer. If no issues, then try install the hp following these hp instructions:

    click here
     
  5. 2004/02/07
    VoodoU

    VoodoU Inactive Thread Starter

    Joined:
    2002/06/05
    Messages:
    13
    Likes Received:
    0
    Solved

    First off thank you Newt and TonyT.....Sorry that it has taken me so long to post the results of this fiasco but here they are.


    The computer was shutting down because the bios settings for shutting down when the CPU temp reached 60C was enabled. I disabled that and everything was fine.

    Footnote: After that I was getting random blue screens the one I got mostly was IRQL_NOT_LESS_OR_EQUAL.

    I thought that this was a problem with the modem that i had installed as it was the last piece of hardware.


    It turns out that this error and many other BSOD were being caused by bad RAM...replaced the stick and everything seems fine just added this last part to hopefully help anyone else :)
     
  6. 2004/02/08
    Newt

    Newt Inactive

    Joined:
    2002/01/07
    Messages:
    10,974
    Likes Received:
    2
    Thanx for the update. Glad it's working for you now.
     
    Newt,
    #5
Thread Status:
Not open for further replies.

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.