Tip: Run a free scan for common Windows errors ad

re: Question about 'Dealing with Bad Memory (RAM)' Saturday, September 21, 2002 at 11:38 am Posted by Brenden (2 messages posted) My mistake Windows 2000 Server hold up to 4 Gigs of memory, Advanced Server is up to 8 Gigs of Memory. On Saturday, September 21, 2002 at 11:08 am, Brenden wrote: >I currently have a GA-7DPXDW Gigabite Server board that I just purchased recently. > It has 4 DIMM Slots that are capable of holding up to 4 GIGS of PC2100 DDR Registered >ECC type ram. The PC2100 DDR Registered ECC is the only type of RAM that my board >will accept. In it I had 2 PC2100 DDR Registered ECC RAM (512MB each stick) in the >first 2 DIMM Slots and it worked fine. I recently purchased a PC2100 DDR Registered >ECC 1 Gigabite stick of RAM from I-buy.com. When I stick the 1 GIG stick in my first >slot on my board and that is the only stick I put in this time, my BIOS detects >the 1 GIG stick of ram and gets to the part of (Starting Windows). Before I even >have the chance of hitting F-8 to use all of the advanced startup options that Windows >2000 Advanced Server has it locks up at that point. When I keep the 1 GIG stick >in the first slot and put one or two of the 512 sticks of RAM in the second and third >slot I get the same results. When I place one of the 512 sticks in the first slot >and the 1 GIG slot in the second (I know your not really suppose to do that) as soon >as it gets up to the Windows is starting up screen it gets past about the first 3 >bars and I get the following error message: > >Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced > >I am able to get into the advanced startup options when the RAM is in this way trying >to use last known good configuration and safe mode but comes up with the same error >message. I get the same results when placing the 1 GIG stick in the third slot with >the 2 512 sticks in the first 2. Does anyone know if this is due to Windows 2000 >Advanced Server. I do know that Windows 2000 Advanced Server is able to handle up >to 4 Gigs of RAM although they dont really speciffy weather that can be DDR or just >standard SDRAM. or could this be due to my board which is a GA-7DPWDW Server board >purchased from Gigabite, or possible bad ram. Also does anyone know of a good hardware >troubleshooting utility that will let me check the RAM before the system boots up?? >Any help would be greatly appreciated. Thanks ahead of time all [Reply or follow-up to this message] re: Question about 'Dealing with Bad Memory (RAM)' Sunday, September 22, 2002 at 12:55 pm Posted by Bob (177 messages posted) Since everything works fine with 2 sticks of memory at a time, like 2 512Mb in the first two slots, but does not work with 1 stick or 3 sticks, looks like you need to fill the memory banks 2 with the same size memory sticks, I can only advise that you get another 1Gb memory stick and use these 1Gb memory sticks, 2 at a time like you installed the 512Mb sticks that worked. Two 512Mb and 2 1Gb memory sticks may work but you really should keep the sticks the the same size in pairs (two at a time, even if the BIOS says it sees the memory installed 1 bank at a time) The only clue I have is that two memory sticks, of the same size worked, 1 installed will not work, 2 of mixed size did not work and 3 of different sized did not work. Looks like you need at least two memory sticks of the same size, which means pairs. On Saturday, September 21, 2002 at 11:08 am, Brenden wrote: >I currently have a GA-7DPXDW Gigabite Server board that I just purchased recently. > It has 4 DIMM Slots that are capable of holding up to 4 GIGS of PC2100 DDR Registered >ECC type ram. The PC2100 DDR Registered ECC is the only type of RAM that my board >will accept. In it I had 2 PC2100 DDR Registered ECC RAM (512MB each stick) in the >first 2 DIMM Slots and it worked fine. I recently purchased a PC2100 DDR Registered >ECC 1 Gigabite stick of RAM from I-buy.com. When I stick the 1 GIG stick in my first >slot on my board and that is the only stick I put in this time, my BIOS detects >the 1 GIG stick of ram and gets to the part of (Starting Windows). Before I even >have the chance of hitting F-8 to use all of the advanced startup options that Windows >2000 Advanced Server has it locks up at that point. When I keep the 1 GIG stick >in the first slot and put one or two of the 512 sticks of RAM in the second and third >slot I get the same results. When I place one of the 512 sticks in the first slot >and the 1 GIG slot in the second (I know your not really suppose to do that) as soon >as it gets up to the Windows is starting up screen it gets past about the first 3 >bars and I get the following error message: > >Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced > >I am able to get into the advanced startup options when the RAM is in this way trying >to use last known good configuration and safe mode but comes up with the same error >message. I get the same results when placing the 1 GIG stick in the third slot with >the 2 512 sticks in the first 2. Does anyone know if this is due to Windows 2000 >Advanced Server. I do know that Windows 2000 Advanced Server is able to handle up >to 4 Gigs of RAM although they dont really speciffy weather that can be DDR or just >standard SDRAM. or could this be due to my board which is a GA-7DPWDW Server board >purchased from Gigabite, or possible bad ram. Also does anyone know of a good hardware >troubleshooting utility that will let me check the RAM before the system boots up?? >Any help would be greatly appreciated. Thanks ahead of time all [Reply or follow-up to this message] re: Question about 'Dealing with Bad Memory (RAM)' Monday, September 23, 2002 at 12:41 pm Posted by Max Pascazi (1 messages posted) Hi, I have recently purchased the same board, the GA-7DPXDW. I was having many problems with windows XP as you describe. Plus stop errors. I have 3 dimms, 1x512meg, 2x256mg. After putting placing the 2 256's in the first two slots and the 512 in the 3rd the system is much more stable. Haven't gotten a XP stop error yet. I also have 2 2000 Athlon MPs. However, the GMT utility from Giga-Byte for this board, reports that the second CPU is "disabled via BIOS". SiSoft Sandra and benchmarking show that there is only one CPU going? Did I miss some jumper, or should I take AMD up on there 3 year warranty? Max [Reply or follow-up to this message] Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Tuesday, December 10, 2002 at 12:52 am Posted by don (3 messages posted) This is what it says when I am trying to boot up. Does anyone know what I am supposed to do to fix this problem. Any help would be appreciated. Thanks [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Monday, January 6, 2003 at 11:32 am Posted by Phlimm (1 messages posted) On Tuesday, December 10, 2002 at 12:52 am, don wrote: >This is what it says when I am trying to boot up. >Does anyone know what I am supposed to do to fix this problem. >Any help would be appreciated. >Thanks To fix this, use one of the two links and follow the directions: First try this one: http://www.jsifaq.com/SUBF/TIP2700/rh2783.htm If that doesn't work, roll up your sleeves and go here: http://www.jsifaq.com/SUBL/tip5900/rh5999.htm Good Luck [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Friday, March 7, 2003 at 1:56 am Posted by Paul Walsh (1 messages posted) Boot up using a W2K CD Choose the Repair option from the recovery console Press C to use the console Type cd system32\config Then type ren system system.old Type copy c:\winnt\repair\regback\system c:\winnt\system32\config Reboot the PC On Tuesday, December 10, 2002 at 12:52 am, don wrote: >This is what it says when I am trying to boot up. >Does anyone know what I am supposed to do to fix this problem. >Any help would be appreciated. >Thanks [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Thursday, March 13, 2003 at 11:36 am Posted by Chad (1 messages posted) I have followed this step and my computer locked up and I had to rebbot. When I went to run these steps again, the ren system system.old wouldn't work, it said it couldn't find it. Also I am using a windows XP professional recover console, I don't have a windows 2000 pro disk to use because it is OEM. This sucks. Any ideas here? On Friday, March 7, 2003 at 1:56 am, Paul Walsh wrote: >Boot up using a W2K CD > >Choose the Repair option from the recovery console > >Press C to use the console > >Type cd system32\config > >Then type ren system system.old > >Type copy c:\winnt\repair\regback\system c:\winnt\system32\config > >Reboot the PC > > > [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Friday, April 4, 2003 at 11:31 pm Posted by Andrew Wolcott (1 messages posted) I'm in the same boat. I have done nearly everything to remedy this without success. If someone has any ideas or knows how to fix this, without a full re-install, please email at awolcott@bellsouth.net Andrew W. Atlanta, GA On Thursday, March 13, 2003 at 11:36 am, Chad wrote: >I have followed this step and my computer locked up and I had to rebbot. When I went >to run these steps again, the ren system system.old wouldn't work, it said it couldn't >find it. > >Also I am using a windows XP professional recover console, I don't have a windows >2000 pro disk to use because it is OEM. > >This sucks. Any ideas here? > [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Wednesday, April 9, 2003 at 5:35 pm Posted by Rhys (1 messages posted) I don't know whether this would have helped you, but it may help others. I was going to go through the whole replace the system hive thing to repair the same problem but thought I would run a chkdsk within the recovery console first, problem gone On Tuesday, December 10, 2002 at 12:52 am, don wrote: >This is what it says when I am trying to boot up. >Does anyone know what I am supposed to do to fix this problem. >Any help would be appreciated. >Thanks [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Sunday, April 20, 2003 at 3:39 pm Posted by Wahib Yusuf (1 messages posted) i followed the instructions from the following article which seems like the recommended microsoft solution and was able to boot my system... it looks like it will restore your system to an previous working registry... good luck http://www.kellys-korner-xp.com/xp_sys32.htm On Monday, January 6, 2003 at 11:32 am, Phlimm wrote: >On Tuesday, December 10, 2002 at 12:52 am, don wrote: >This is what it says when I am trying to boot up. >Does anyone know what I am supposed to do to fix this problem. >Any help would be appreciated. >Thanks > > >To fix this, use one of the two links and follow the directions: > >First try this one: >http://www.jsifaq.com/SUBF/TIP2700/rh2783.htm > >If that doesn't work, roll up your sleeves and go here: >http://www.jsifaq.com/SUBL/tip5900/rh5999.htm > >Good Luck [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Thursday, April 24, 2003 at 6:06 am Posted by Rebecca (3 messages posted) It may seem intuitive, but I had this problem and never thought to check the system properties for the registry quota. Turned out that my max reg. quota setting was too low and the registry had grown to be bigger than what was allowed...ergo, the problem. I restored the registry, increased the registry quota, and rebooted. All has been well since then. On Sunday, April 20, 2003 at 3:39 pm, Wahib Yusuf wrote: >i followed the instructions from the following article which seems like the recommended >microsoft solution and was able to boot my system... it looks like it will restore >your system to an previous working registry... good luck > >http://www.kellys-korner-xp.com/xp_sys32.htm > > [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Thursday, April 24, 2003 at 6:09 am Posted by Rebecca (3 messages posted) Make sure your registry quota setting isn't too low. I had this problem for weeks, only to find out that my registry size had exceeded the quota that is set by default with the Win2K installation. Restoring the registry, increasing the quota, and rebooting...fixed the problem. In my case, at least! On Friday, March 7, 2003 at 1:56 am, Paul Walsh wrote: >Boot up using a W2K CD > >Choose the Repair option from the recovery console > >Press C to use the console > >Type cd system32\config > >Then type ren system system.old > >Type copy c:\winnt\repair\regback\system c:\winnt\system32\config > >Reboot the PC > > > [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Thursday, April 24, 2003 at 1:53 pm Posted by peter (1 messages posted) I dont get it what am i to do? On Tuesday, December 10, 2002 at 12:52 am, don wrote: >This is what it says when I am trying to boot up. >Does anyone know what I am supposed to do to fix this problem. >Any help would be appreciated. >Thanks [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Thursday, May 1, 2003 at 4:13 pm Posted by rick (1 messages posted) I administer 70 laptops, and I have seen this error about 5 times, most of the time I have just re-imaged and reconfigured but this I decided to look into it further and this is the fix. Thanks. On Thursday, April 24, 2003 at 6:09 am, Rebecca wrote: >Make sure your registry quota setting isn't too low. I had this problem for weeks, >only to find out that my registry size had exceeded the quota that is set by default >with the Win2K installation. Restoring the registry, increasing the quota, and rebooting...fixed >the problem. In my case, at least! > > [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Sunday, June 22, 2003 at 2:05 pm Posted by eric (1 messages posted) how do i get to the recovery console? iam using win 2k, do i boot from the cd and what do i do after i boot form the cd? On Thursday, March 13, 2003 at 11:36 am, Chad wrote: >I have followed this step and my computer locked up and I had to rebbot. When I went >to run these steps again, the ren system system.old wouldn't work, it said it couldn't >find it. > >Also I am using a windows XP professional recover console, I don't have a windows >2000 pro disk to use because it is OEM. > >This sucks. Any ideas here? > [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Monday, July 7, 2003 at 9:47 am Posted by Deosyne (64 messages posted) If you dont have a recent archive of your system files then you can do the following it's not elegant but it works. 1. rename your %system%/system32/config/system and system.alt to other names 2. copy %system%/repair/system to system32/config directory and restart ***THIS WILL UPDATE THE HIVE ONLY TO THE POINT WHICH THE REPAIR FILE IS DATED*** On Sunday, June 22, 2003 at 2:05 pm, eric wrote: >how do i get to the recovery console? iam using win 2k, do i boot from the cd and >what do i do after i boot form the cd? > > > [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Monday, September 22, 2003 at 11:30 am Posted by Umang (1 messages posted) I am having a problem booting Windows because that file is missing. When I try to use the repair option from my Windows boot disk, it doesn't work. When I try to console method, I can't figure out what the Administrator password is. How do I go about fixing this? On Thursday, April 24, 2003 at 6:09 am, Rebecca wrote: >Make sure your registry quota setting isn't too low. I had this problem for weeks, >only to find out that my registry size had exceeded the quota that is set by default >with the Win2K installation. Restoring the registry, increasing the quota, and rebooting...fixed >the problem. In my case, at least! > > [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Thursday, October 2, 2003 at 12:25 pm Posted by alan (1 messages posted) Stoked. chkdsk repaired the error in a heart beat. I can't tell you how much i appreciate your post. cheers. alan. ps. afterwards, i increased the registry quota just in case. On Wednesday, April 9, 2003 at 5:35 pm, Rhys wrote: >I don't know whether this would have helped you, but it may help others. I was going >to go through the whole replace the system hive thing to repair the same problem >but thought I would run a chkdsk within the recovery console first, problem gone > > [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Thursday, October 2, 2003 at 5:22 pm Posted by Dave Mgbeokwere (1 messages posted) Rebecca, please try to solve the first problem first which is that Windows would not start! If it does not start then, there is no way to make the changes you suggest to the registry. Indeed, what Umang really means is that Windows hangs which also means that it simply delivers the irksome message and refuses do anything else. That also means that neither ctrl+alt+del nor any other key on the keyboard works. Please, if you would first say how to get out of that sys lockup first, that would then make it possible to apply your solution. Again, since your readers vary in their computer-literacy levels, it pays to assume the lowest level coupled with down-to-earth, step-by-step instructions. Thanks. On, Thursday, April 24, 2003 at 6:09 am, Rebecca wrote: >Make sure your registry quota setting isn't too low. I had this problem for weeks, >only to find out that my registry size had exceeded the quota that is set by default >with the Win2K installation. Restoring the registry, increasing the quota, and rebooting...fixed >the problem. In my case, at least! > > [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Wednesday, October 15, 2003 at 12:23 pm Posted by Randy Forcier (1 messages posted) This has happened to me 4 times now. Can someone please tell me what to do to stop this from happening or why it happens? Thank You, Randy On Thursday, March 13, 2003 at 11:36 am, Chad wrote: >I have followed this step and my computer locked up and I had to rebbot. When I went >to run these steps again, the ren system system.old wouldn't work, it said it couldn't >find it. > >Also I am using a windows XP professional recover console, I don't have a windows >2000 pro disk to use because it is OEM. > >This sucks. Any ideas here? > [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Wednesday, October 22, 2003 at 6:23 am Posted by Michele Ampy (1 messages posted) Check disk will repair Windows 2000, but it will destroy your user configuration data. On Thursday, April 24, 2003 at 1:53 pm, peter wrote: >I dont get it what am i to do? > > [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Monday, November 3, 2003 at 3:04 pm Posted by Antoine (1 messages posted) Thanks to your tips I managed to recover from the situation, however I want to prevent it from happening again. How do you your registry quota exactly ? I went to Control Panel / system / advanced / Performance options / change. There I can see that my maximum registry size is 90 MB, it also says that the current registry size is 16 MB. Do I need to increase that size (90 MB seems ok to me) ? Thanks, Antoine. On Thursday, April 24, 2003 at 6:09 am, Rebecca wrote: >Make sure your registry quota setting isn't too low. I had this problem for weeks, >only to find out that my registry size had exceeded the quota that is set by default >with the Win2K installation. Restoring the registry, increasing the quota, and rebooting...fixed >the problem. In my case, at least! > > [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Tuesday, November 4, 2003 at 12:35 am Posted by Marshall (1 messages posted) if you have'nt found out yet that mess. is stamped over another one so really its sysem i would copy my system.alt change it or i mean save as system,and cross your fingers reboot On Wednesday, October 22, 2003 at 6:23 am, Michele Ampy wrote: > >Check disk will repair Windows 2000, but it will destroy your user configuration >data. > [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Wednesday, November 5, 2003 at 7:38 pm Posted by Mark (2 messages posted) Also understand, there is no file called "systemced". The file is called just "system". The confusion stems from the fact that the error message is overwritting the text already on the screen, without removing it. So the "ced" was part of some other word. On Thursday, April 24, 2003 at 6:06 am, Rebecca wrote: >It may seem intuitive, but I had this problem and never thought to check the system >properties for the registry quota. Turned out that my max reg. quota setting was >too low and the registry had grown to be bigger than what was allowed...ergo, the >problem. I restored the registry, increased the registry quota, and rebooted. All >has been well since then. > > [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Thursday, November 6, 2003 at 6:12 am Posted by Rebecca (3 messages posted) Just as a follow-up, it turned out to be a modem compatibility problem causing the error. Had to figure it out by stripping the machine of all non-essential hardware and start adding pieces and parts from there. Tricky! [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Friday, January 2, 2004 at 10:31 pm Posted by TJ (1 messages posted) Chkdisk worked for me too!!! Thank you very much!!! TJ [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Friday, January 16, 2004 at 12:51 am Posted by Gene (1 messages posted) Im thinking your file is corrupted. The ram shouldn't be messing up windows. I suggest run the recovery disc or the windows installation to repair it. On Tuesday, December 10, 2002 at 12:52 am, don wrote: >This is what it says when I am trying to boot up. >Does anyone know what I am supposed to do to fix this problem. >Any help would be appreciated. >Thanks [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Tuesday, February 3, 2004 at 7:07 am Posted by omega1 (1 messages posted) Hi, I've tried everything suggested here, and managed to get to the logon window (previously it stopped at bootup), but when I get to the logon, the keyboarrd and mouse do not work... any ideas?? Thanks On Friday, January 16, 2004 at 12:51 am, Gene wrote: >Im thinking your file is corrupted. The ram shouldn't be messing up windows. I suggest >run the recovery disc or the windows installation to repair it. > > [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Wednesday, February 4, 2004 at 8:42 pm Posted by Steve (1 messages posted) Try searching 269075 on www.support.microsoft.com, it will give you step by step instructions on how to fix. On Wednesday, November 5, 2003 at 7:38 pm, Mark wrote: >Also understand, there is no file called "systemced". The file is called just "system". >The confusion stems from the fact that the error message is overwritting the text >already on the screen, without removing it. So the "ced" was part of some other word. > > [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Tuesday, February 17, 2004 at 9:09 am Posted by Ursula (1 messages posted) I have this same problem, which started after I installed the latest Windows update two days ago. I don't have a Windows 2000 cd/floppy and am not having success getting it to start in DOS mode via F8. I have read through all the responses here, but I have not the faintest idea how to get to the "recovery console" or the registry. Please help? Thanks in advance. [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Tuesday, February 17, 2004 at 4:39 pm Posted by nonesuch (1 messages posted) Hmm... might be possible to use NT Password Recovery floppy to reset admin password, then use the recovery console to do the steps others have mentioned here. I've used the NT Password Recovery floppy about 4 times, and it never lets me CHANGE passwords, but will let me reset them to null if lost/forgotten. See http://home.eunet.no/~pnordahl/ntpasswd/ for the utility. On Monday, September 22, 2003 at 11:30 am, Umang wrote: >I am having a problem booting Windows because that file is missing. When I try to >use the repair option from my Windows boot disk, it doesn't work. When I try to console >method, I can't figure out what the Administrator password is. How do I go about >fixing this? > > [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Tuesday, March 23, 2004 at 6:08 pm Posted by Mike Eathorne (1 messages posted) I'm having a similar problem that I was hoping someone out there could help me with. I have a 1.2 GHz Compaq with I think 640 MB Ram (I upgraded from the factory 128 to 640 - I think; can't remember at the moment). I remember when I upgraded the memory about 6 months back that it was an unusual number (which could be the problem I suppose). Running XP Professional and, Norton Internet Security. After updating my Norton Virus definitions and restarting I get the "Windows could not start because the following file is missing or corrupt: Windows\System32\Config\System" message. Last time I got this message (roughly a month ago) I tried my hardest to repair it but ended up having to take it in as I exhausted all of my mental knowledge of PCs/Software. Unfortunately, I don't have a recovery disk (I know, I know....unbelievably stupid of me). But, I do have the XP upgrade disk. Any ideas on how to resolve this so I don't have to take it in again? Thanks in advance! On Tuesday, February 3, 2004 at 7:07 am, omega1 wrote: >Hi, > >I've tried everything suggested here, and managed to get to the logon window (previously >it stopped at bootup), but when I get to the logon, the keyboarrd and mouse do not >work... any ideas?? > >Thanks > > >On Friday, January 16, 2004 at 12:51 am, Gene wrote: >>Im thinking your file is corrupted. The ram shouldn't be messing up windows. I suggest >>run the recovery disc or the windows installation to repair it. >> >> [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Saturday, April 24, 2004 at 9:07 am Posted by Steve (1 messages posted) I have the same problem. No floopy or cd. So how do get to the desktop to perform any of these suggestions when I cannot get past the error message? Using F8 or any command does not work. Can I use the XP pro recovery disk? Will it automatically boot up in the drive in my Win2000 machine? Any ideas would be welcome. Thanks On Tuesday, March 23, 2004 at 6:08 pm, Mike Eathorne wrote: >I'm having a similar problem that I was hoping someone out there could help me with. > I have a 1.2 GHz Compaq with I think 640 MB Ram (I upgraded from the factory 128 >to 640 - I think; can't remember at the moment). I remember when I upgraded the >memory about 6 months back that it was an unusual number (which could be the problem >I suppose). Running XP Professional and, Norton Internet Security. > >After updating my Norton Virus definitions and restarting I get the "Windows could >not start because the following file is missing or corrupt: Windows\System32\Config\System" >message. Last time I got this message (roughly a month ago) I tried my hardest to >repair it but ended up having to take it in as I exhausted all of my mental knowledge >of PCs/Software. Unfortunately, I don't have a recovery disk (I know, I know....unbelievably >stupid of me). But, I do have the XP upgrade disk. Any ideas on how to resolve >this so I don't have to take it in again? > >Thanks in advance! > > [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Friday, August 27, 2004 at 9:48 pm Posted by Julie (1 messages posted) Hello, I have read the information about this subject. I am gathering all the steps to take. However, I have a question before I begin to do anything on my computer. If I change the registry information or follow the steps that MS provides or any steps that others have suggested here, does this mean the files on my harddrive.... such as MS Word documents, software programs installed, etc. are completely deleted? In other words, does changing the registry in effect automatically delete everything and the only thing left on your harddrive is Win 2k? Does this mean I'm competely starting over and I lose everything, but now able to boot up Win 2k? As a result of this boot-up error problem, I ended up installing another Win 2k on my computer, so in effect I have 2 operating systems to choose from to load my computer. (I made sure that no changes were made to previous files in 1st win 2k, installed 2nd win 2k and named it in a folder titled Recovery versus WINNT) So far it is working okay, but with the other same problems this system has overall--(It freezes up with no error messages-no blue screen-nothing but the screen I last was looking at-mouse frozen-can't ctrl-alt-del as it does nothing-requires a hardboot of shutting off the computer.)-- Anyway, of course, I still can't load my original operating system and I have no access to any of my document and software files. So does this added information make a difference in the steps I take? I assume that as long as I change the registry as it relates to the original (non-booting and error message) operating system that I should be okay. Thanks for any feedback on this. I know this was a long message. Julie :-) On Tuesday, December 10, 2002 at 12:52 am, don wrote: >This is what it says when I am trying to boot up. >Does anyone know what I am supposed to do to fix this problem. >Any help would be appreciated. >Thanks [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Wednesday, September 29, 2004 at 3:16 pm Posted by bamartin14 (1 messages posted) I have installed a parallel copy of Win2k and have been following the instructions outlined at http://www.jsifaq.com/SUBL/tip5900/rh5999.htm but I running into errors when I try to open the system hive and enter in contents in the "Key Name" field. The error message that I get is "Registry editor could not accomplish the requested operation". I have researched this but haven't been able to find a work around. Does anyone know the answer to this problem? Thanks, On Monday, January 6, 2003 at 11:32 am, Phlimm wrote: > >On Tuesday, December 10, 2002 at 12:52 am, don wrote: >>This is what it says when I am trying to boot up. >>Does anyone know what I am supposed to do to fix this problem. >>Any help would be appreciated. >>Thanks > > >To fix this, use one of the two links and follow the directions: > >First try this one: >http://www.jsifaq.com/SUBF/TIP2700/rh2783.htm > >If that doesn't work, roll up your sleeves and go here: >http://www.jsifaq.com/SUBL/tip5900/rh5999.htm > >Good Luck [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Wednesday, October 27, 2004 at 8:27 am Posted by babar jamil (1 messages posted) Hi: I am using MS article 269075 to resolve this problem. I am into OS now but when I go to action item called “restore a backup of the system hive”, specifically to item #8 (i.e. In the key name box type System.old, and then click ok) I get message saying, “Registry editor couldn’t load the key. This file is not a valid registry key” Please note that System.old on my computer resides at C:\winnt\system32\config. Any help will be appreciated.(E-Mail Address: bjamiil@yahoo.com) Regards BJ On Friday, August 27, 2004 at 9:48 pm, Julie wrote: >Hello, > >I have read the information about this subject. I am gathering all the steps to take. > However, I have a question before I begin to do anything on my computer. > >If I change the registry information or follow the steps that MS provides or any >steps that others have suggested here, does this mean the files on my harddrive.... >such as MS Word documents, software programs installed, etc. are completely deleted? > In other words, does changing the registry in effect automatically delete everything >and the only thing left on your harddrive is Win 2k? Does this mean I'm competely >starting over and I lose everything, but now able to boot up Win 2k? > >As a result of this boot-up error problem, I ended up installing another Win 2k on >my computer, so in effect I have 2 operating systems to choose from to load my computer. >(I made sure that no changes were made to previous files in 1st win 2k, installed >2nd win 2k and named it in a folder titled Recovery versus WINNT) So far it is working >okay, but with the other same problems this system has overall--(It freezes up with >no error messages-no blue screen-nothing but the screen I last was looking at-mouse >frozen-can't ctrl-alt-del as it does nothing-requires a hardboot of shutting off >the computer.)-- Anyway, of course, I still can't load my original operating system >and I have no access to any of my document and software files. So does this added >information make a difference in the steps I take? I assume that as long as I change >the registry as it relates to the original (non-booting and error message) operating >system that I should be okay. > >Thanks for any feedback on this. I know this was a long message. > >Julie :-) > > > [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Tuesday, November 2, 2004 at 7:19 pm Posted by emilisaac (1 messages posted) If the quoted KB article doesn't help, microsoft provides the following instead: http://support.microsoft.com/default.aspx?scid=kb;en-us;Q302829 On Wednesday, October 27, 2004 at 8:27 am, babar jamil wrote: >Hi: > >I am using MS article 269075 to resolve this problem. I am into OS now but when I >go to action item called “restore a backup of the system hive”, specifically to item >#8 (i.e. In the key name box type System.old, and then click ok) I get message saying, >“Registry editor couldn’t load the key. This file is not a valid registry key” Please >note that System.old on my computer resides at C:\winnt\system32\config. > > >Any help will be appreciated.(E-Mail Address: bjamiil@yahoo.com) > >Regards >BJ [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Monday, December 27, 2004 at 1:42 pm Posted by Justine (2 messages posted) Hello Everybody, I have read all the instructions on this thread and have tried to run the recovery console but I am not getting anywhere. In every instruction, I end up at an impasse in the command promt. What should one do if one *doesn't* have a backup of the registry? I am at a total loss- been trying to solve this problem for weeks and I can't find any instructions that work. How can you restore a registry that hasn't been backed up? And if you can't, what can you do to not lose your data?! Any help out there would be **greatly** appreciated! [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Wednesday, December 29, 2004 at 9:33 am Posted by brandon (2 messages posted) once you are at the " C:/windows " prompt insert the original Windows XP CD and type CHKDSK /R and hit enter... then wait it may take a while..good luck and let me know if it works for ya it did for me On Thursday, November 6, 2003 at 6:12 am, Rebecca wrote: >Just as a follow-up, it turned out to be a modem compatibility problem causing the >error. Had to figure it out by stripping the machine of all non-essential hardware >and start adding pieces and parts from there. Tricky! [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Wednesday, December 29, 2004 at 9:42 am Posted by brandon (2 messages posted) once you are at the " C:/windows " prompt insert the original Windows XP CD and type CHKDSK /R and hit enter... then wait it may take a while..good luck and let me know if it works for ya it did for me On Tuesday, December 10, 2002 at 12:52 am, don wrote: >This is what it says when I am trying to boot up. >Does anyone know what I am supposed to do to fix this problem. >Any help would be appreciated. >Thanks [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Wednesday, December 29, 2004 at 10:05 pm Posted by Justine (2 messages posted) Well, I installed a parallel installation of win2k under \winnt\new successfully. Then I tried to find \winnt\system32\config but the config directory of the original operating system actually *is* missing. There is just no config folder there at all! Is there something I can do in this case other than just forgetting the old installation and trying to use the new one? (my software and hardware configuring is kind of complex) Now that I know way more about this than I ever wanted to, does anyone have any ideas as to why the winnt\system32\config directory actually vanished? At this point, I am curious... Finally, if the original installation really is worthless, how do I get rid of it? Thanks in advance! On Monday, December 27, 2004 at 1:42 pm, Justine wrote: >Hello Everybody, > >I have read all the instructions on this thread and have tried to run the recovery >console but I am not getting anywhere. In every instruction, I end up at an impasse >in the command promt. What should one do if one *doesn't* have a backup of the registry? >I am at a total loss- been trying to solve this problem for weeks and I can't find >any instructions that work. How can you restore a registry that hasn't been backed >up? And if you can't, what can you do to not lose your data?! Any help out there >would be **greatly** appreciated! [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Thursday, January 6, 2005 at 9:41 am Posted by Boilerman872 (1 messages posted) I had this same problem on a Windows 2000 machine. I tried all of the previous suggestions but the solution was to download a utility from Microsoft (chkreg.exe) along with a 6 diskette XP boot set. The chkreg utility will modify disk 6 of the set. When you boot from the set, choose the repair option. This will run the chkreg.exe program. I my case it took less than 10 seconds to repair the registry and after rebooting I was back in business. Following is the link to the Microsoft Website: http://support.microsoft.com/default.aspx?scid=kb;en-us;830570 On Tuesday, December 10, 2002 at 12:52 am, don wrote: >This is what it says when I am trying to boot up. >Does anyone know what I am supposed to do to fix this problem. >Any help would be appreciated. >Thanks [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Friday, April 1, 2005 at 5:40 am Posted by Jeffrey (1 messages posted) I have run into a similar situation and unfortunately the suggestions posted have not corrected the system. I had to reinstall everything and restore my data from tapes. My question is just for morbid curiousity. Now that my server is running normally is it possible to change the System and system.alt files to read only? Or phrased more appropriately, what would happen if I changed the files to read-only? I believe I already know the answer, but I’m to chicken to test it and I’m without resources to make a new test system. Thanks in advance. On Thursday, January 6, 2005 at 9:41 am, Boilerman872 wrote: >I had this same problem on a Windows 2000 machine. I tried all of the previous suggestions >but the solution was to download a utility from Microsoft (chkreg.exe) along with >a 6 diskette XP boot set. The chkreg utility will modify disk 6 of the set. When >you boot from the set, choose the repair option. This will run the chkreg.exe program. > I my case it took less than 10 seconds to repair the registry and after rebooting >I was back in business. Following is the link to the Microsoft Website: > >http://support.microsoft.com/default.aspx?scid=kb;en-us;830570 > > > [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Friday, September 23, 2005 at 5:40 am Posted by TradeSlayer (1 messages posted) If you can boot to the drive you just have to run a chkdsk against it and it will recover the lost files. It worked for me. On Thursday, March 13, 2003 at 11:36 am, Chad wrote: >I have followed this step and my computer locked up and I had to rebbot. When I went >to run these steps again, the ren system system.old wouldn't work, it said it couldn't >find it. > >Also I am using a windows XP professional recover console, I don't have a windows >2000 pro disk to use because it is OEM. > >This sucks. Any ideas here? > [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Monday, September 26, 2005 at 6:01 am Posted by tim williams (1 messages posted) Hi there I have got this problem that a few of you seem to have experianced, however when I try the command "ren system.alt systemalt.old" the file is not recognised also when I do the "copy part" the file is not recognised....any ideas please? On Monday, January 6, 2003 at 11:32 am, Phlimm wrote: > >On Tuesday, December 10, 2002 at 12:52 am, don wrote: >>This is what it says when I am trying to boot up. >>Does anyone know what I am supposed to do to fix this problem. >>Any help would be appreciated. >>Thanks > > >To fix this, use one of the two links and follow the directions: > >First try this one: >http://www.jsifaq.com/SUBF/TIP2700/rh2783.htm > >If that doesn't work, roll up your sleeves and go here: >http://www.jsifaq.com/SUBL/tip5900/rh5999.htm > >Good Luck [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Tuesday, November 29, 2005 at 2:07 pm Posted by Will Balleto (1 messages posted) This Worked For Me. If PC fails to boot with the following error "WINNT\SYSTEM32\CONFIG\SYSTEMced" Follow these steps. Boot with a WIN2K or XP CD select R for Repair and go to the recovery console choose the windows installation to log onto Type the Administrator password Then type FIXBOOT Type Y and reboot. [Reply or follow-up to this message] re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced Wednesday, November 29, 2006 at 4:29 am Posted by Johne Barnsley (1 messages posted) Hi there - I had this problem on my PC and followed your instructions to the letter and WOW! it worked! Many Thanks John Barnsley UK On Thursday, March 13, 2003 at 11:36 am, Chad wrote: >I have followed this step and my computer locked up and I had to rebbot. When I went >to run these steps again, the ren system system.old wouldn't work, it said it couldn't >find it. > >Also I am using a windows XP professional recover console, I don't have a windows >2000 pro disk to use because it is OEM. > >This sucks. Any ideas here? > [Reply or follow-up to this message] re: Question about 'Dealing with Bad Memory (RAM)' Tuesday, October 30, 2007 at 6:42 pm Posted by tazzy (1 messages posted) I was wondering if you ever got your single cpu problem figured out. Im dealing with the exact same thing and not finding much help or knowledge thanks On Monday, September 23, 2002 at 12:41 pm, Max Pascazi wrote: >Hi, > >I have recently purchased the same board, >the GA-7DPXDW. I was having many problems with >windows XP as you describe. Plus stop errors. >I have 3 dimms, 1x512meg, 2x256mg. After putting >placing the 2 256's in the first two slots >and the 512 in the 3rd the system is much more >stable. Haven't gotten a XP stop error yet. > >I also have 2 2000 Athlon MPs. However, the GMT >utility from Giga-Byte for this board, >reports that the second CPU is "disabled via BIOS". >SiSoft Sandra and benchmarking show that >there is only one CPU going? > >Did I miss some jumper, or should I take >AMD up on there 3 year warranty? > >Max > [Reply or follow-up to this message] Tip: Use one of the [Reply or follow-up to this message] links above to add a message to this thread Search this forum Start a new thread on a different subject Report abuse of the forum Return to the Windows 2000 Discussion Forum