AMD 1.1 GHz Thunderbird ABIT KT7-RAID 512 MB PC-133 Micron Memory Win2000 SP1 SoundBlaster Live Value PCI NIC WD 20.5 GB HD I got my system parts about three weeks ago. For the first two weeks I had to install Win2000 at least 7 times. After giving up and deciding it was a hardware problem I called the store where I purchased the parts. They told me that it's a known problem that systems faster then 900 MHz can corrupt the registry on auto power shutdown. This appears to be my problem, because the system never had a problem when I restarted the system. Only on shutdown. I searched the web and I could only find information about the shutdown problem on Win98/Me and a patch file. Nothing could be found for Win2000. For the last 1.5 weeks I would do a restart and turn off the power when the BIOS screen came up. Today the system would not boot. I had to enter the emergency console and issue a FIXBOOT command. The system then restarted. I guess I turned the power off at the wrong time and corrupted the boot block. This is a real hassle and I don't trust the system. Any ideas?

I have the same motherboard you do and I've been having the exact same problem. I have installled Windows probably 5 times now. I even exchanged my hard drive once with Maxtor, thinking that was the problem. If anyone has an idea how to fix this I would greatly appreciate it.

I hope this helps. I have an almost identical system :- ABIT KT7 Raid mobo Athlon 900 overclocked to 997Mhz 512MB PC133 SDRAM 2xIBM Telstro 46GB ATA-100 drives (striped) OS on an 8GB IBM ATA-66 drive SB Live! Platinum nVidia GeForce2 GTS I have had Win2K running on the system now for about 3 months without any problems of this sort at all. I'm not sur if there is an inherent problem with the mobo or if you've just been unlucky. If there is a problem with CPU's over 900Mhz, I do haven't come across it. This may be that mine is overclocked, I'm not sure. You could always reducing the clock multiplier in SoftMenu to 850 or 900Mhz and see if the problem persists. This is hardly a solution, but at least it will show if the mobo is faulty or not. If you can't access the clock multiplyer, this is how to do it. On the top right side of the CPU is a series of silver solder points. Get a pencil and join these points. That's it. Beware though that overclocking any CPU will invalidate the warranty. Good luck

I am having the same problem with: AOpen MX59Pro mainboard AMD K6-2/500MHz 256MB PC-133 SDRAM D-Link ISA NIC 20GB Seagate HD I would say it's not because your sytems are too fast. ;-) Reboot == fine Power down == file system or registry corruption most of the time.

I had the same problem with my home pc. I just installed windows 2k pro, and been having problems with the system hive of the profile getting corrupted. I had to reinstall once, when I stupidly didn't create an ERD. I've hosed the profile 2 or 3 times since then. At least after the first reinstall, I remembered to do the ERD. At first I thought it was Diablo II or my large Hard Drive. Now, I suspect it is the powerdown routine. Gateway Pentium III 500MHz 384MB RAM 40GB WD IDE Drive Windows 2k SP1 I remember we had the same problems with certain laptops on NT4. We ended up distributing a registry hack that prevented the powerdown on shutdown. In NT 4.0, the key is: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] "PowerdownAfterShutdown"="1" I would imagine that Win2k is similar. (I don't have win2k at work to check). Just change the "PowerdownAfterShutdown" value to "0", instead of "1". That worked for the laptops. It might be worth a try. There might also be a way to change it with the GUI, but I don't have win2k in front of me. I would imagine it is in the APM section. -Steve

I modified my bios and turned of ACPI, I have been running my system for months with no problems. I have a 900mhz TBird overclocked to 1013ghz. Here is a link with alot of info for Abit KT7 series mobo. http://www.viahardware.com/faq/kt7/kt7faq.htm

There something you guys should know, a friend of mine was having problem with almost the same configuration, but the problem was solved when he installed the latest via 4 in 1 drivers before first shutdown. Is reported that there is some problem with via amd chipsets (kt and others) and sb live! series sound card. Good Luck