Name: cpmusick Date: November 2, 2001 at 13:38:34 Pacific Subject: C:\windows\system32\config\SYSTEM
Comment:
When I try to boot up WindowsXp, it says that the following file is either missing or corrupt:
c:\windows\system32\config\SYSTEM
I know how to fix it, it's just that it keeps showing this error. I'll fix it, then I'll run my computer just fine for a couple days or so, then it says it again.
Does anyone know why it keeps saying this error? Thanks.
I have the same problem, but except SYSTEM it is the SOFTWARE hive. I get it about every few weeks, and it requires me to re-install XP (a pain!). Anyone got any ideas?
Aargh! This problem is driving me crazy. However, I'm glad that someone else seems to be experiencing it too. I think I know what is leading to it on my machine. I'm on a network whose server provides a Samba share (using a ROS [real operating system]), and - thank god - is where I keep the things that actually mean something to me. However, over the past two days, My Network Places has started mapping EVERY DRIVE LETTER POSSIBLE (outside of C: and D:) to this Samba share.
I've accessed the Microsuck KB article noted above, and can't seem to start the regedt32.exe from the Repair console. I'm probably missing something really basic.
Here's a thread with a temporary fix. http://www.computing.net/windowsxp/wwwboard/forum/1321.html BTW, it seems to be a memory issue, whether it be bad memory or a bad memory slot.
I have also this kind of problem.. It's had no problem under w2k... when I installed XP after several reboot, the message appeared. I read the Aaron message. I tried GoldMemory to test my ram and the test told me one of the memory slot was bad. even if I had no problem under XP. I removed the memory and I got no problem so far...
what board are you guys using? i'm using an "inexpensive' board that appears to have a bad ddr slot and i'm getting the same area. i would tend to agree with the guy above about it being a memory issue because of this. i'm using a k7s5a board...anyone else having problems with that board?
I've been fighting and researching this problem for weeks now and I've been able to make it stop on my computer by slowing down my PC133 SDRAM to 100Mhz. I've also seen this mentioned in other newgroups as a possible cause / cure. If any of you have 133Mhz ram and can run it at 100Mhz, give it a try and please post your findings. Btw, my memory sticks are good Crucial memory and I'm pretty sure there's nothing wrong with it.
Does anyone have a fix to the same problem, except with C:\windows\system32\config\SOFTWARE ? I saw someone else had it, but he didn't say if there was a fix.
I have been experiencing this error over and over- it does it with a different file sometimes (default/software or hal.dll) and I have formatted 3 times (ntfd/fat... makes no difference) might try removing a stick of RAM, but I doubt that is the problem... M$ have built XP from the ground up... with bugs as per usual. Amiga One will be here soon hopefully.
Hello! I had the same problem but it seems to gone out. I have a Sound blaster Live! Value and I put Windows 2000 drivers instead of default XP drivers to enjoy all the functions of my sound card. It worked but... some time when leaved my session: "DELDRV don't respond..." or something like this. And of course: Error...systemroot\system32\config\software...Sometimes at startup!
I have update my driver with the new creative Update version (for my sound card and windows XP): No errors when leaving, no errors when starting!
So I hope that my message will be able to help you, (wait a minute before buying new memory sticks!) and good luck!
Damn, I've had this problem since november/december or so. Well thx to FZ Kuno 4 giving me the link to this site :)
Anyway, I have been reinstalling windowsXP since i purchased my new computer(way more than 30 times now). The same problem occurs after the system 4 some reason freezes. In 90-95% of the times the comp, 4 some reason have freezed, this problem occurs - not always then. I have also tried it in Win2k, and so has one of my buddy's. I have also tried it on my old K6-2, but only once, where my new AthlonXP, well at least over 30 times.
I've been trying to test all my hardware, cound not find anything broken or anything that may have caused this problem. I have thought of a harddrive or memory problem, since I only get this problem after the comp for some reason was not able to close down proporly.
Well I will now try to run WinXP with FAT32, it might work? - anyway, if this does not help I will go back to WinME, I simply refuse to go the ghost way, and ghost the s--- every 2. day or so - or try the method descriped at the MS site, do that every 2. day? - hell no!!!
why doesn't microsoft come out with an update to fix the regristry problem with the file windows\system32\config\SOFTWARE. i'm talking about a critical update that you can download. it would make everyones lives easier. Somebody should contact microsoft and tell them to get there asses moving.
I did have the same problem and here is what caused it for me. I updated the BIOS on my ASUS A&V266-E and when you load the "setup defaults" the entry for "DDR_1T/2T_ITEM" is set to "1T_DDR". This is what caused XP to not be able to boot with the error msg. I changed it to "2T_DDR" and everything works fine now. There is also a option for "AUTO" which works also. Hope this helps.
I'm having this problem right now, and didnt install the Repair Console... never mind.... anyway, my reason for posting is that i have a feeling that this is only effecting AMD boxes, especially Athlons and Durons (k7's)... anyone had this problem with a intel box?
I the same probs. Iīve installed XP prof for nearly 20 times. Sometimes itīs working for over 30 times I boot, sometimes just a few times. Iīve an MSI K7S5A Board with 266MHZ Ram and Athlon1200C, Iīve taken out all cards, also the onboard and the probs with the system-file appeared again. Also I tried FAT32, installation on C:, on D: and so on. The problems didnīt change.
Does someone has more helpfull hints for this problem???
Same problem encountered for the first time (the "system" flavor). I'm running a P3 on a 100 MHz BX board, so it's not related exclusively to AMD, DDR or 133RAM. What a pain! Haven't checked my memory yet.
I've got also a card based on SIS735 (Elite K7S5A I guess). I am not encountering this problem, but my father who's got an ASUS card (A7V I think, not sure though) and an Athlon 600 encounter it all the time. I will try to test the memory and post the result, but it was working fine with windows 98 os2 !!!
I have the same problem. K7S5A board with a Athlon 1200 MHz cpu and 128 DDR memory. I thought that it was the Harddisk, it wasn't that, so i'm now trying memory.
I have been testing the all afternoon with a hardware testing program, it seems there is something wrong with the base ram (cache) which is a part of the AMD Athlon series processors. I have 5 Athlon 1200 MHz cpu's three of them got the \windows\system32\config\system problem the other two working OK.
Yesterday I downloaded several Critical Patches from WIndows Update. One of the 8 updates was not installed and had given some error. As usual, I was asked to restart my PC. When I restarted my machine, XP gave the missing \windows\system32\config\SYSTEM error.
I had a similar problem with Windows 2000 and it had to do with the following (I will use layman's terms to describe what happened according to the experts in that forum): when you shut down your PC, the system saves the hive, software, system etc files. But sometimes the system kind of shuts faster and does not save those files correctly and corrupts them. I guess it is something similar here.
btw, the problem is not limited to AMD. I have an Intel chipset.
My Windows drive is NTFS. When I turned my Computer on, I saw the message "The file system32\config\SYSTEM is corruped or missing".
I did the following and solved the problem:
I restarted my PC from WinXP CDROM and went to the Recovery Console and typed these sentences to restore the file SYSTEM:
CD system32\config REN system system.old COPY ..\..\repair\system EXIT
then, when I restarted my PC, I saw another message that said the file c_1256.nls was missing or corrupted.
I went to the Recovery Console again and restored the file from WINXP CDROM as following:
CD system32 COPY H:\I386\c_1256.nl_ EXIT
where "H:\" is my CD Drive.
after restarting, another message apeared that said c_720.nls was missing and I did above again for this file and after restarting I got my Windows healthy again!
I've only just encoutered this problem in the last few days, the only things I've changed are adding a graphics tablet and doing a windows update. I did however try and use the recovery option by booting off the XP CD but when it goes 'starting windows' after loading everything the computer crashes and then just goes back into windows? I really have no idea!
This is a system with three OSes - Win98SE, WinXP-pro, Mandrake Linux.
Only XP has this kind of problem. Goldmemory tested ok in quick mode.
Elitegroup K7S5A, Duron 1200 256MB PC-133 infineon RAM Asus7100 (Geforce2/MX) Acer 20/10/40 and a Noname DVD-ROM
I don't think it always is RAM related. My system runs stably for days, only this problem at bootime occurs frequently. Someone here mentioned she/he thinks it might be related to fast shutdown (which frequently was a major broblem in WinME) - I tend to think so too.
Is there a patch or something that can be changed in the registry to disable fast shutdown (such a thing existed in WinME)?
I recently went from 98se to XP and suffered the same problem after EVERY reboot. Eventually I switched back to 98se after trying everything I could possibly think of to get it to work.
However my friend recently got XP on his machine and it worked perfectly with nearly identical hardware:
1ghz AMD TBird AbitKT7a Raid board. 1 stick of 256 meg PC133 major ram Herc Geforce 3 2 * 30gig IBM telestos
I thought - well if he can do it - so can I. It could only be a setting somewhere as if its working in his and not mine then its simply faulty hardware (and I knew it was all fine).
I isolated my problem at memory speed. In my bios I had it set to "fast". Simply moving it to normal speed cured it and I've been stable for days now.
Im still waiting for the crash to happen but in the meantime I have what is in my opinion a very nice smooth (stable?) operating system.
I have been having this problem for some time now it it seems to be happening faster each time. It would give me the error once in awhile,then it was doing it very often. Im on an AMD Duron700 ASUS A7V-133 256 ram
Its is funny how it kinda creaps up on you when you least expect it. The ram I have was bought from the place that built the pc. It started off with 128,so I bought another 128 stick. Should I just go into bios and change from 133 to 100mhz? I really like XP but man....this is KILLIN ME!!!! If I cant get a fix for this,I may have to go back to win2k.
This seems like a big issue here and hope to get it fixed one way or another before MS gets a load of bad emails!! LOL
