Sign in with
Sign up | Sign in
Your question

Recurring file corruption problem

Last response: in Windows 2000/NT
Share
January 5, 2004 1:02:36 PM

there are 2 computers here at work that keep crashing. the error at the startup screen is WINNT\SYSTEM32\CONFIG\SYSTEMced is corrupt. anyone ever have this problem? also, i ran several repairs that did not fix it. it seems that the only way is a complete reinstall. is there a way to replace this one file for the next time? the computers are 2k pro, sp4, all patched/updated nforce2.

Itchy and Scratchy #1325,Itchy plays Scratchy's skeleton like a xylophone; strikes the same rib twice but clearly 2 different notes sound. are we to believe that this is some sort of magic xylophone?
January 11, 2004 3:54:23 PM

If the file corruption is recurring, you may be looking at a dying harddisk or a virus. You should run some antivirus program and drive tests before attempting to fix the problem.

<i><b>Engineering is the fine art of making what you want from things you can get</b></i>
January 14, 2004 8:44:12 AM

Don't discount your memory being faulty. Most files are placed into memory and read from there, and in some cases these files are then written back to disk. If you scan your HDD and it is clean try checking your memory with a memory checking program (don't ask me for any names as it has been years since i last used one...) or alternativly try swapping with known good memory...
Related resources
January 14, 2004 12:17:42 PM

to test your memory, got <A HREF="http://www.memtest86.com" target="_new">here</A> and get memtest86. It will let you know if the problem is with your memory.

Spec:
Intel P4 2.4B
MSI 645E Max-U Mobo
512MB DDR333
GF3 ti200 64MB
SB Live 5.1
WD 60GB (Storage)
Maxtor 6GB (System)
Maxtor 120GB
LG 24x24x32 CDR
WIN2K PRo SP4
February 26, 2004 10:20:14 PM

I ran MemTest86+ for an hour on both of my machines (identical hardware) and they both were error free for that 1 hour duration.... How long should I run it before I can assume that everything is good (how long does the program run in the first place?)

I am not some amateur-crastinator... I am a PRO-crastinator!
February 27, 2004 2:40:08 AM

this is a symptom of one of several possible problems, including bad hardware. however, chances are that is is fixable. go <A HREF="http://support.microsoft.com/?kbid=269075" target="_new">here</A>


Gigabyte 7VRXP mobo; AMD Athlon 1400+; 512 MB PC-133 memory; Radeon 8500 64 MB; Lite-on CD-RW 32x12x40; LG DVD-ROM; TB Santa Cruz; Videomate Gold+ TV Tuner; NEC FE700+ monitor
February 27, 2004 2:47:02 PM

Anyone here know WHAT exactly the following registry tweak (taken from the above link) is actually doing to solve the issue? I am considering doing this tonight, but I am paranoid... 5 days of fighting with my new systems, I'm not to eager to make things worse.

Start registry editor (Regedt32.exe).
Locate and click the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Share

On the Registry menu, click Save Key.
In the File name box, type Shares.new, and then click Save.
Locate and click the following key in the registry:
HKEY_LOCAL_MACHINE

On the Registry menu, click Load Hive.
In the list of files, click the System.old file, and then click Open.
In the Key Name box type System.old, and then click OK.
Locate and click the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\Select

Note the setting for the Default value.
Locate and click the following key in the registry
HKEY_LOCAL_MACHINE\System.old\ControlSetx\Services\LanmanServer\Shares

where x is the number that you noted in step 8.
On the Registry menu, click Save Key.
In the File name box, type Shares.old, and then click Save.
Restore the Shares.new key to the System.old registry hive:
HKEY_LOCAL_MACHINE\System.old\ControlSetx\Services\LanmanServer\Shares

Click the HKEY_LOCAL_MACHINE\System.old key.
On the Registry menu, click Unload Hive.
Quit Registry Editor.
Restart the computer to the Recovery Console.
At the command prompt, type the following lines, pressing ENTER after you type each line:
ren system system.org
ren system.old system

At the command prompt, type exit, and then press ENTER to restart the computer.

I am not some amateur-crastinator... I am a PRO-crastinator!
February 28, 2004 12:36:08 AM

no idea what the edit does. but you are wise not to trust the procedure even though it comes directly from the microsoft support site. things can always go wrong. if i were you, before i started fiddling in the registry, i would make sure anything important that i wanted was backed up on disk.

Gigabyte 7VRXP mobo; AMD Athlon 1400+; 512 MB PC-133 memory; Radeon 8500 64 MB; Lite-on CD-RW 32x12x40; LG DVD-ROM; TB Santa Cruz; Videomate Gold+ TV Tuner; NEC FE700+ monitor
February 28, 2004 12:38:07 AM

oh, by the way, have you first investigated hardware causes of the problem? you may want to systematically remove hardware (starting with modems/NIC cards) so see if this cures the problem. i once heard of a guy who had this error, and his modem hardware was the cause of the problem.

good luck.

Gigabyte 7VRXP mobo; AMD Athlon 1400+; 512 MB PC-133 memory; Radeon 8500 64 MB; Lite-on CD-RW 32x12x40; LG DVD-ROM; TB Santa Cruz; Videomate Gold+ TV Tuner; NEC FE700+ monitor
!