• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

strange problems in W2K

novice

Golden Member
I recently upgraded my wife's system with a new motherboard, CPU and ram. Here are the system specs:
MSI KT6V-LSR KT600 chipset
AMD Sempron 2400+ retail hsf
Kingston Value Ram PC-3200 512 mb
Orig, Maxtor D-740X 40 gig HD now WD Caviar SE 80 gig)
Gainward Geforce 2 Pro Video card
Windows 2000 service pack 4
orig. D-Link D-120 wireless USB NIC
currently D-Link DWL-520 PCI network card

My problem is that I lose my internet connection to the wirless access point. The card appears to be fine but can't connect. When it does this, I also have problems getting into device manager to check on the system's hardware status. It also hard locks when I try to shut it down. Once I manually shut down, it sometimes won't reboot. Then if I leave it off for a while, it reboots and everything works normally, including the internet. I assumed it was a bad hard drive, perhaps with a corrupted file in windows, so I replaced the drive and used norton ghost to clone the old drive to the new. I also swapped the USB NIC for a PCI based wireless network card. It seemed to be fixed, but now it is doing it again. It will work for days at a time, then act up. Could it be:
1. Bad CPU?
2. Bad motherboard?
3. Bad ram?
4. Bad power supply? (It is an Antec 300 watt unit that is a few years old)
5. Bad Windows?

The only other thing I have noticed is that the CPU runs a lot hotter than my old Duron 850 on the Chaintech AJA2E KT133E board. My BIOS shows around 50 to 53 C for the cpu under light load. Seems like it should run cooler than that. Any ideas or suggestions? I thought I had it fixed when I swapped out the network card. Then I thought I had it whipped when I replaced the hard drive with a new Western Digital Caviar SE (80) gig. But now it is acting up again. Kind of annoying, especially the way it works okay again if you wait a while.
Appreicate any input or suggestions as to how best to troubleshoot.
Chuck
 
Well, Montag451, thanks for responding. I checked the event viewer and came up with some consistent errors that occur periodically. Service control manager event 7000 and 7009 with the 7009 being Timeout waiting for the Zip To a Service to connect; and the event 7000 : The Qip To a Service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. Not sure what that means, but could it explain the periodic inability to connect to the internet followed by an unwillingness to complete the loading of windows? If I leave the system off for a while, like more than an hour, it will then boot normally and is able to access the internet, and seems to run normally, for several days at a time, then it will do it again. (Usually when my wife needs something from it in a hurry, go figure!) Appreciate any response, and thanks for the reply, montag451.
 
you said that you cloned your drive....in this case any problem that happened to be software related will still be present....

I'm not saying that this is definately your problem but try a clean install using one of your hard drives and see if the problem still exists....

also 50-53 degrees isn't that hot for a cpu these days..

also....are you doing anything in particular when the crashes occur or is it just random??

any peer to peer sharing....that used to drop my router!!
 
I realize that cloning the drive would carry over any software related problems, but wanted to make sure that we retained all of our data and drivers from our existing drive. And of course, after I made the switch, everything worked great. (For a couple of weeks, then the same issues)And no, not doing anything in particular when it crashes. Most times it happens when the PC is in standby mode, and when it wakes up, it can't access the internet. Then when you try to shut down, it hard locks, then after hitting the reset, it won't finish loading windows until it has completely cooled off. Then it will cold boot normally, at least so far. Thanks for your input, fuzzynavel.
 
Did you clone system drivers to new mobo then it might not work because they are different system drivers. You can clone anything for back up only if you can use on same mobo but not on new mobo.
My suggest is you have to install windows os then install drivers that comes with new mobo.
 
Thanks for the reply, Rottie. The reason I chose the motherboard I did was because I have had good luck in the past upgrading motherboards by choosing a newer version of the same chipset manufacturer. I simply reinstall the motherboard drivers and it actually works pretty well. In this case I went from a Via KT133E board to a KT600 chipset motherboard. It was working fine for a month or two, so I don't think the new motherboard was the problem. I did do a search on the Windows 2000 knowledge base and ran windows update finding a couple of patches relating to working behind a NAT on a network and booting/shutdown problems with networking and installed those. Keeping fingers crossed as it has worked since then...
 
Hi,
Might want to check out Microsoft:
Q155814
Q315194

Also, if you are running the following - look at the MS Q no.
Microsoft Exchange Management - See Q309511.
SharePoint Portal Server - See Q316267.
MSSQLSERVER - See Q306034.
Microsoft Exchange MTA Stacks - See Q325907.
Savroam - See "Symantec Support Document ID:2004080513005448".
VERITAS VSS Provider - See the link to "Veritas Support Document ID: 272751


Seems you have your work cut out for you.
Good luck, and please let us know if anything works, or not.
 
Thanks for your input, Montag. I think you may have hit on something for me. That Q315194 makes reference to the Documents and Settings folder being moved to a non accessible volume, making the system time out. The two events that they list for this happening are the same two events that show up in my event viewer. It also makes me wonder if I might be getting randomly hosed by having the Via Raid Tool installed on my system, even though I am not running Raid. When it boots, it shows "No System Disk present and then searches for network disk, then boots. Could this be part of my problem? Do you think it would cause any harm to try to uninstall the Via Raid Tool? Do you think this could be part of my problem? FWIW. it hasn't crashed since my installation of the 2 Win2K updates, keeping my fingers crossed. Thanks again for posting, I am pretty darn ignorant as to software in general and windows in particular, but enjoy learning.
 
Why is the RAID tool running when there is no RAID?

Was it installed with the chipset drivers?

If so, try disabling [backup backup backup backup] the tool [see if you can do it under Hardware devices], or uninstalling it, or, better still,
START
RUN
type MSCONFIG
goto STARTUP tab,
untick the RAID TOOL.

see if that does anything.

Let us know
good luck
 
I installed the RAID tool when I installed the chipset drivers. Thought it would be ready to go once I picked up a pair of SATA hard drives down the road. Unfortunately Windows 2000 Pro doesn't have MSCONFIG, the only thing I miss from Windows 98! I also don't see the RAID tool listed separately in the add/remove programs on the control panel. I guess I will have to remove the chipset drivers, then reinstall just the ones I need. Of course, I have a natural reluctance to mess with a system that is functioning, which mine is, (at the moment, at least) I would hate to remove the chipset drivers and have a major meltdown.
 
WAIT,

Download a tool - startup cop, or any other startup tool.
I'm sure that win2k can use msconfig, but you have to download it seperately!

Do that, or do a search for another startup manager [lots of freeware yoots to pick from]
 
Thanks for the link, montag. Installed and unchecked Via RAID tool. No longer runs at startup. System is still stable, so am keeping fingers crossed that the patches fixed the problem. Time will tell. Thanks for your help.
 
Back
Top