Windows Forum

Ask something
Discussion Locked

registry checker

0 helpful
21 replies

by rickyrattlesnake

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Windows registry checker comes up on every reboot. It tells me it has found an error in my system files and replaced it with a recent backup. It then repeats the process over and over until it tries to rebuild the registry and is unable to. I have to boot in DOS and manually replace the files with good backups that I have renamed to keep registry checker from deleting them in this process. I am running Windows 98 on an AMD K6-2 350 Mhz machine with 128 MB RAM. This happens whether or not I install any new software. Any way to keep this from happening?

21 replies

by rcom

Something is obviously corrupting the registry. Got virus software?
Boot to just the DOS prompt and type in SCANREG /FIX
Maybe the problem will be resolved.
The thing to find out is what's cauing the registry to be damaged each time you reboot. One question is are you able to use the computer or is it in a loop doing what you described.

by rickyrattlesnake

I've tried this. The registry is not corrupt. Scanreg/fix doesn't work. It says it can't rebuild the registry. It stays in a loop until I manually replace the registry.

by ann777

If I were you, I'd copy your backup registry files to system.dat and system.da0 and user.dat and user.da0 then shutdown and see if the same thing somes up on boot.

If it still continues after that, then remove all of your networking protocols (control panel --> Network) and reboot, reinstall all your networking protocols. Most of the time, this is caused by corrupted protocols trying to write to the registry.

I've seen this happen on public library computers until the protocols were wiped and re-created.

by shanghai sam

I can boot this machine, but not reboot. If it tries to reboot, then registry checker comes on. That's when I manually restore a good registry. Not a problem with network protocols. Thanks, though.

by rcom

Just questions about your respose to my attempt at assisting you. Which by the way you so kindly rejected while overlooking the fact that a simple thanks may have been a good gesture. I'm the first of the 2 replies to your question.

Anyway What do you call the registry besides "corrupted" if it doesn't work and needs to restored from your "uncorrupt" backup?

A registry that cannot be rebuilt is usually called "corrupt", or do you have another word for it. I'm allways ready to be enlightened.

Your backup isn't "corrupt" until you change it to system.dat. The file then somehow gets modified or damaged ("corrupted") or you wouldn't be having this problem, no?

You can stop this loop by manually changing the file but then it happens again, doesn't that mean something is modifying the registry?

The thing to do is narrow it down to what is causing that. There is hundreds of entries in the registry and this problem could be caused by many things but one thing for certain is your registry file is getting "corrupted". KA-PESH !

by shanghai sam

Thank you, but no, it is not a corrupt registry. I look at the so-called "corrupt" registry and compare it to my good registry and they are always identical. This occurs not just on this setup, but on other configurations of the same machine. Maybe hardware related?

by pinoy_teknik

Do you suspected your RAM already...???

Its that a single stick of 128 or 2 x 64?
If it is 2 try to put it one by one....And check if it will happen again...

My PC encounters that, AMD 750 and 192 MB of RAM... First i suspected the Windows System File so i reinstall it but now work..

So my second step is the termination of a hardware
And i found out that it is a faulty memory by putting it one by one...

Hope it will guide you some steps!!

__________
Pinoy_Teknik
http://kickme.to/flaire

by pinoy_teknik

CORRECTION AT THIS LINE!!!

My PC encounters that, AMD 750 and 192 MB of RAM... First i suspected the Windows System File so i reinstall it but not work..

by shanghai sam

Thanks, but this was one of the first things I tried. I totally replaced memory and it is still happening.

by borginva

If you can boot into your OS, I would recommend you use MSCONFIG and disable any extra things you do not need to start up with the machine (AOL, RealPlayer, etc). Give yourself as few booting things as possible. Do the same to the STARTUP folder.
Then, from sites like pcworld or download.com, use a few cleaning programs like Microsoft's RegClean or JV16 Powertools, and do a little clean up of the registry. If you have NSW or Ontrack, use those registry cleaners. (If you want any of these registry cleaners like RegClean or JV16, E-mail me and I will send them so you do not have to go searching).
Then reboot, see what happens.
There would have to be something causing the corruption upon reboot. If it boots fine, then you may have found itto be one of the programs you disabled. For which ever programs you need to start up with the OS, enable one at a time each program you need. You may find the culprit.
It could be a network protocol if you have them installed. You may try what the other user suggested.
The only way to fix this is trial and error repairing and deducting.
Grab some coffee, friend.

by shanghai sam

Thanks, but I've cleaned the registry and I have nothing extra in MSCONFIG. I've disabled everything and it still happens. Again, it is not the network protocols. I have even had this happen when I try to reboot and choose to go into either Safe Mode or Command Prompt. I've tried for months to figure out what is causing this problem. Even rebuilding the system from scratch was of no help.

by rickyrattlesnake

Point value changed by question poster. Thanks for your suggestions so far. I've even had other IT professionals I know look at it. We're all stumped here.

by c.barnhorst

If you've spent months on this why not a new box? As in eBay. I can tell by your answers how frustrated you are. New box. Faster box. Move components as needed. New planter into the deal. I'm not trying to be cute. You frustration is just not worth the little money needed to step up a little.

by rickyrattlesnake

I have newer boxes. This machine works flawlessly except for this. Also, it runs apps faster than my Pentium 4 1.2 GHz Dell machine.

by borginva

It has got to be one of your programs, unless you rebuilt your system with nothing but a fresh install of 98. Then, it would be a hardware issue.
Have you elimenated your other software? Are you currently on a clean install of 98, nothing more?

by rickyrattlesnake

It did this with a clean install as well as on a different hard drive on the same machine since I posted this. Now I'm almost certain it is hardware-related.

by pinoy_teknik

OK, memory is not faulty, and you are sure with that. AND i think its to far from software issue.
Co'z you said that you done a fresh install, am i right...

How about the BIOS, Check some string settings that is regarding to the memory setup. (ADVANCE CHIPSET FEATURES)

If does'nt effect..

Do fresh clean istall with minimum hardware installed. Remove some plug-in cards there, except the Video Card. So install........

Make sure you have a correct driver that you used (Device Driver),Wrong drivers is a caused and i know you know that, JUST WANT TO DOUBLE CHECK!!

If does'n affect and still bugging you!!

Reply!! for follow up...

________
Pinoy_Teknik
http://kickme.to/flaire

by rickyrattlesnake

Not the BIOS. One of the first steps I took was checking the BIOS and then going so far as to replace it. Also, doesn't appear to be a plug-in card problem. I even tried it with nothing but the video card using a clean install and by using a different video card. This just doesn't make sense.

by rkliwon

Hey Ricky,
I am experiencing the same @#$&@!! registry-problem you are facing and I have read all the comments and answers concerning your problem. I have not tried it yet, but could it possibly have something to do with the software on the win98 installation cd? Have you used the same cd for every installation? Let's try using another cd (not a copy). you never know..I myself am getting pretty tired of it. I am experiencing it on a small network of 10 pc's out of which 4 or 5 are giving me this error..

This discussion is closed to new replies.