Annoyances.org
Home » Windows 2000 Discussion Forum » Message 1032631681 Search | Help | Home
  
Tip: Run a free scan for common Windows errors ad

Question about 'Dealing with Bad Memory (RAM)'
Saturday, September 21, 2002 at 11:08 am
Windows 2000 Annoyances Discussion Forum
Posted by Brenden (2 messages posted)


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


Responses to this message:
*re: Question about 'Dealing with Bad Memory (RAM)' (Brenden: Saturday, September 21, 2002 at 11:38 am)
*re: Question about 'Dealing with Bad Memory (RAM)' (Bob: Sunday, September 22, 2002 at 12:55 pm)
*re: Question about 'Dealing with Bad Memory (RAM)' (Max Pascazi: Monday, September 23, 2002 at 12:41 pm)
*Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (don: Tuesday, December 10, 2002 at 12:52 am)

All messages in this thread [show all]
-Question about 'Dealing with Bad Memory (RAM)' (Brenden: Sat, Sep 21, 2002, 11:08 am)
*re: Question about 'Dealing with Bad Memory (RAM)' (Brenden: Sat, Sep 21, 2002, 11:38 am)
*re: Question about 'Dealing with Bad Memory (RAM)' (Bob: Sun, Sep 22, 2002, 12:55 pm)
-re: Question about 'Dealing with Bad Memory (RAM)' (Max Pascazi: Mon, Sep 23, 2002, 12:41 pm)
*re: Question about 'Dealing with Bad Memory (RAM)' (tazzy: Tue, Oct 30, 2007, 6:42 pm)
-Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (don: Tue, Dec 10, 2002, 12:52 am)
-re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (Phlimm: Mon, Jan 6, 2003, 11:32 am)
-re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (Wahib Yusuf: Sun, Apr 20, 2003, 3:39 pm)
-re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (Rebecca: Thu, Apr 24, 2003, 6:06 am)
-re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (Mark: Wed, Nov 5, 2003, 7:38 pm)
-re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (Rebecca: Thu, Nov 6, 2003, 6:12 am)
*re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (brandon: Wed, Dec 29, 2004, 9:33 am)
*re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (Steve: Wed, Feb 4, 2004, 8:42 pm)
*re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (bamartin14: Wed, Sep 29, 2004, 3:16 pm)
*re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (tim williams: Mon, Sep 26, 2005, 6:01 am)
-re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (Paul Walsh: Fri, Mar 7, 2003, 1:56 am)
-re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (Chad: Thu, Mar 13, 2003, 11:36 am)
*re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (Andrew Wolcott: Fri, Apr 4, 2003, 11:31 pm)
-re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (eric: Sun, Jun 22, 2003, 2:05 pm)
*re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (Deosyne: Mon, Jul 7, 2003, 9:47 am)
*re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (Randy Forcier: Wed, Oct 15, 2003, 12:23 pm)
*re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (TradeSlayer: Fri, Sep 23, 2005, 5:40 am)
*re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (Johne Barnsley: Wed, Nov 29, 2006, 4:29 am)
-re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (Rebecca: Thu, Apr 24, 2003, 6:09 am)
*re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (rick : Thu, May 1, 2003, 4:13 pm)
-re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (Umang: Mon, Sep 22, 2003, 11:30 am)
*re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (nonesuch: Tue, Feb 17, 2004, 4:39 pm)
*re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (Dave Mgbeokwere: Thu, Oct 2, 2003, 5:22 pm)
*re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (Antoine: Mon, Nov 3, 2003, 3:04 pm)
*re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (Ursula: Tue, Feb 17, 2004, 9:09 am)
-re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (Rhys: Wed, Apr 9, 2003, 5:35 pm)
-re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (alan: Thu, Oct 2, 2003, 12:25 pm)
*re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (TJ: Fri, Jan 2, 2004, 10:31 pm)
-re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (peter: Thu, Apr 24, 2003, 1:53 pm)
-re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (Michele Ampy: Wed, Oct 22, 2003, 6:23 am)
*re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (Marshall: Tue, Nov 4, 2003, 12:35 am)
-re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (Gene: Fri, Jan 16, 2004, 12:51 am)
-re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (omega1: Tue, Feb 3, 2004, 7:07 am)
-re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (Mike Eathorne: Tue, Mar 23, 2004, 6:08 pm)
*re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (Steve: Sat, Apr 24, 2004, 9:07 am)
-re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (Julie: Fri, Aug 27, 2004, 9:48 pm)
-re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (babar jamil: Wed, Oct 27, 2004, 8:27 am)
*re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (emilisaac: Tue, Nov 2, 2004, 7:19 pm)
-re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (Justine: Mon, Dec 27, 2004, 1:42 pm)
*re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (Justine: Wed, Dec 29, 2004, 10:05 pm)
*re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (brandon: Wed, Dec 29, 2004, 9:42 am)
-re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (Boilerman872: Thu, Jan 6, 2005, 9:41 am)
*re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (Jeffrey: Fri, Apr 1, 2005, 5:40 am)
*re: Windows could not start because the following file is missing or corrupt: \winnt\system32\config\SYSTEMced (Will Balleto: Tue, Nov 29, 2005, 2:07 pm)
Return to the Windows 2000 Discussion Forum


All content at Annoyances.org is Copyright ©1995-2012 Creative Elementtm All rights reserved.
Please do not plagiarize; redistributing these pages without permission is strictly prohibited.