2000 pro random reboots

bdoerflerbdoerfler Member Posts: 6 ■□□□□□□□□□
just built new system seems to reboot randomly. 2.8 800mghz fsb 1gig pc3200 mem; 128 meg of video mem is this too fast for win 2000 pro?

Comments

  • NERVNERV Member Posts: 15 ■□□□□□□□□□
    Check and see if it is making a **** log. Also, you might want to make sure your bios settings are at default. It sound like a hardware issue not an os issue.
    ________
    NERV
    ________
  • JOblessELementJOblessELement Member Posts: 134
    I've had similar reboots with Win2k. Mine boiled down to being an incompatible video card for the motherboard I owned. In your case, it could be anything. Like NERV said, analyze that **** log.
    I am free of all prejudices. I hate everyone equally.
  • Kevin57Kevin57 Member Posts: 16 ■□□□□□□□□□
    We had two issues:
    -The CPU was too fast for 2000Pro. It looks like the max is about 2.0GHZ.
    -The IDE HD slave was trying to take over for the SATA HD master. Causing all HD to HD transfers to crash the system.
  • spicc7spicc7 Member Posts: 47 ■■□□□□□□□□
    Have you checked your event viewer?
    Disable Shadow BIOS?
    Checked memory settings in BIOS
    Have all your SP's installed?
    How is your cooling?
    __________________________________________
    CCNA, CCNA Security, MCSA, MCP, A+, Network+
  • PavlovPavlov Member Posts: 264
    WOW! New one on me... I've never encountered an Operating System suffering because the CPU was too fast icon_confused.gif

    I would recommend the same things everyone else has... Check your error logs and be sure the hardware is on the HCL.
    Pavlov
    A+, Net+, i-Net+, CIW-A
    MCP NT4, MCSA 2K, MCSE 2K
  • aznluvsmcaznluvsmc Member Posts: 47 ■■□□□□□□□□
    Also could be a RAM issue. Windows 2000 is very picky on the RAM that is used in the computer. There maybe an address or range of addresses in a specific RAM chip that is causing the reboot. I've seen this problem many times in Windows XP.
  • zen4glennzen4glenn Member Posts: 9 ■□□□□□□□□□
    Make sure you are not having a resource conflict. If you have a SB live, take it out temporarily. They eat IRQs like it is its job. 2000 is very picky on its ram. Are they matched sticks? If only one stick...latency timing alright? But, first...check IRQs.
  • rossonieri#1rossonieri#1 Member Posts: 799 ■■■□□□□□□□
    have you installed all the hardware correctly? because alot in my case like this the power connector on both mainboard or harddrive doesnt plug correctly and it just like turn the whole system down temporarely, check using event viewer or chkdsk /f if there is a bad sector on your drive.
    the More I know, that is more and More I dont know.
  • nyma96nyma96 Member Posts: 12 ■□□□□□□□□□
    check the cables???
    I had random reboots because of loose cables....took me a month to find out...even tried reseating the cpu...:)
Sign In or Register to comment.