W2k hangs on startup.

2336

Elite Member
Feb 11, 2000
4,667
7
81
Folks, I've run into a W2k rig that either gives me a blue stop screen or stops at the splash screen and the startup bar doesn't even move. The message on the blue stop screen is 00x00000067. CONFIG_INITIALIZATION_FAILED. When I went to Microsoft's site and research the code it says that either the RAM is bad or the motherboard, in so many words. Is it possible to install the HDD into a known working system to verify this? or will W2k go berserk due to many hardware change, like WinXP, and just shutdown? Any help would greatly appreciated.

Rick
 

mechBgon

Super Moderator<br>Elite Member
Oct 31, 1999
30,699
1
0
Opinion: Win2k will not like being transferred to a new mobo (generally). It'll either BSOD, lock up, or just keep starting/restarting. Now, you could try reinstalling Windows2000 over the top of itself... boot from Win2k CD, and when it asks the first time about whether you want to repair or reinstall, say "reinstall." It will do some stuff, ask about where to install... pick the partition that Win2k is already installed on and it will say "Hey! There's Win2k already, do you want to repair it or clean-install?" and you say "Repair, pleeze :)" and cross your fingers.

I haven't done it in a while so I might not have the dialogues quite verbatim ;) but I'm sure you can adapt & overcome. BTW, this advice comes courtesy of one of those massive IBM click-clack keyboards you sold me a while back :D Stillllllll going...
 

2336

Elite Member
Feb 11, 2000
4,667
7
81
Thanks for the input Tom. I think I'm just going to do a fresh re-install using a known, working MoBo and be done with it. I'm glad to see you're getting good mileage out of those keyboards. They're better than the Energizer bunny!;)
 

2336

Elite Member
Feb 11, 2000
4,667
7
81
Well gang.:confused: The CONFIG_INITIALIZATION_FAILED again! The system ran fine all day yesterday, he shut it down last night and when he tried to boot up this morning he got the same error - CONFIG_INITIALIZATION_FAILED. At this point the only thing I can possibly offer as an explanation is his RAM or his power feed. He is using an ancient surge protector in a part of our area that is well known for wildly fluctuating electrical power. With my limited experience with W2k I'm at a loss at this point.:disgust: