Registry Problems?

[stupdasso]

Hey All, If you guys can figure this one out it would be great! Ok here is the situation. When I run programs that access the registry and runs a scan i.e. Ad-Aware, Regclean or Registry Mechanic the computer just automatically restarts with no error message on shut down. Once the computer does restart I get this message, "The system has recovered from a serious error". When I click on more information it has these two lines C:\DOCUME~1\default\LOCALS~1\Temp\WERa131.dir00\Mini111505-02.dmpC:\DOCUME~1\default\LOCALS~1\Temp\WERa131.dir00\sysdata.xmlI notice every time that the system is "scanning" the registry it does this and that is the only time it does it. I have tried running these programs in Safe Mode and it still does it. If anyone can help me with this problem I surely would be greatful! Thanks in advance for any help you may provide.Dan p.s.- I don't know if this would help but here is the error signature it has also:BCCode : 51 BCP1 : 00000004 BCP2 : 00000001 BCP3 : E382D6C8 BCP4 : 0083EC48 OSVer : 5_1_2600 SP : 2_0 Product : 256_1 System specs:Windows Xp Pro Sp21.5 GB Pentium 480gb HD w/ 46gb free256 mb RDRAMCompaq Presario 7126clI have ran AVG Antivirus and Spybot and both say I am clean!

[usasma]

I'm starting to experiment on the dump files - if you'd like me to take a look at yours, I'll see what I can figger out. As I understand it, evaluating the dump file will give us the names of the file(s) that caused the error - not just the name of the file that the error occurred in. Just PM me and I'll give you an email addy to send it to.Here's a link to the description of the BugCheckCode:http://www.osronline.com/ddkx/ddtools/bccodes_4c6f.htmand indicates that it could be a hardware problem or file system corruption.So, I'd run chkdsk.exe /f from the Run command (as I recall, you'll have to reboot for it to run) and see if there are any errors.Also, you can go to Start...Run, then type in "diskmgmt.msc" (without the quotes) and press Enter. Then check to see if the disk is rated as "Healthy". Another tool for this is a SMART diagnostic reader. One is available in SpeedFan, which you can download for free here: http://www.almico.com/speedfan.php (although it's a fan and temperature tool - it has the SMART capabilities built into it).Troubleshooting the hardware will be a bit more difficult. Start by looking for error messages in the Event Viewer. Go to Start...Run...and type in "eventvwr.msc" (without the quotes) and press Enter. In the left hand pane will be 3 categories (Application, Security, and System). Click on each one and view the messages in the right hand pane. Do this for each category and let us know the error messages that are there. Windows is setup by default, to write the error messages to the Event Log when a crash occurs.

[kkehoe]

It's probably a good idea to disable auto-restart to see if the system will hang at a Stop error on shutdown and give you the chance to get the details, rather than just rebooting.Go to System Properties > Advanced > Startup and Recovery, and uncheck Automatically Restart under the System Failure section.Post back with the Stop error info if you get it.Kevin

[stupdasso]

usasma and kkehoe, Thanks for the quick replies. Well here is were I stand, I ran a chkdsk.exe and it said no errors found but I did notice that it said 32 kb in bad sectors. Didn't really know if this would cause a problem. I also turned of the Automatically Restart and caught what it said: A problem has been detected and Windows has been shut down to prevent damage to you computer. Registry_Error Beginning dump of physical memory Stop:0X00000051 (0X00000004, 0X00000001, 0XE11137E8, 0X0083EC48)So I think it is looking more and more like a corrupted registry? If it is corrupted, except for certain scanning software, and my programs are working otherwise, should I just live with it or will I possibly have more problems down the road? Is there anyway to fix the registry without having to reinstall the OS? Ugh I hope that I don't have to do a reinstall. I would not look forward to doing that. Thanks again for your help guy's. Let me know what you think. I really appreciate the help thus far.Dan

Edited November 16, 2005 by stupdasso

[usasma]

By default, the system logs crashes to the Event log - so, unless you've switched it off, the STOP error will be in the Event Viewer. Also, BugCheckCodes generally are the same as STOP errors. Microsoft alludes to this relationship in several of their online articles.Most of the STOP 0x51 errors are described as relating to Win2K. But, since XP was built up from Win2K - the procedures will be essentially the same.Win2K article (similar to XP) http://support.microsoft.com/kb/282501'nother one: http://msdn.microsoft.com/library/default....w2kmsgs/442.aspFrom this link: http://aumha.org/win5/kbestop.php

0x00000051: REGISTRY_ERROR(Click to consult the online MSDN article.)This indicates a Registry or Configuration Manager problem. An I/O error may have occurred while the Registry was trying to read one of its files (caused by hardware or file system problems). This message might also appear due to a memory management error (more common in earlier versions of Windows NT). * How to Troubleshoot a “STOP 0x00000051 REGISTRY ERROR†Error Message {KB 282501} Win 2000 * You Receive a “Stop 0x51 (REGISTRY_ERROR)†Error Message {KB 321771} Win 2000 * “Stop 0x00000051 REGISTRY_ERROR†Error Message When You Log On {KB 810558} Win 2000 SP3 (during logon or Registry backup) * Windows NT 4.0 Setup Troubleshooting Guide {KB 126690} NT 4 (Recommendations for the current error message are buried down inside this article, which isn’t necessarily limited to NT 4.)

Did you get a chance to try these suggestions?:Also, you can go to Start...Run, then type in "diskmgmt.msc" (without the quotes) and press Enter. Then check to see if the disk is rated as "Healthy". Another tool for this is a SMART diagnostic reader. One is available in SpeedFan, which you can download for free here: http://www.almico.com/speedfan.php (although it's a fan and temperature tool - it has the SMART capabilities built into it).This will further verify the status of your hard drive (chkdsk.exe should have marked those sectors as being "bad"). Eliminating the hard drive as the cause of the problem will lead us to the registry repair issue (which I'll have to do some research on - if you don't have a good backup copy of it).

[stupdasso]

Hey usasma, Yes I did try your suggestion of running diskmgmt.msc and it says that the disk is healthy. I also ran SpeedFan and it too said it was fine. I also ran eventvwr.msc and I don't see anything in the list about the Stop Error that occured. I wish I could tell you more but I haven't been able to find out anymore. Thanks for your continued help I really appreciate it.ThanksDan

[usasma]

OK, it's not likely your hard drive because of the tests that you've run.Event Viewer won't say "STOP" anywhere that's obvious. You'll have to check each message (in the right hand pane) that says "Error" by right clicking on it and selecting "Properties". There should be at least 2 in the System category - the original BugCheck that you gave us, and the STOP error that you gave us. The difficulty lies in finding them, especially if there's a lot of errors!The next step is memory testing. First, you'll delete and then recreate your pagefile to ensure that there isn't corruption within it. Then, you can run a couple of these free memory testers (from a floppy disk) to help rule out a physical memory error.To delete and recreate your pagefile, follow these steps:1) Go to Start...Control Panel...System...Advanced tab...Performance Settings button.2) Click on the Advanced tab, then on the Virtual Memory Change button.3) Write down the current settings for your pagefile4) Click on "No paging file", the click OK to exit all the dialogs5) Reboot your system6) Go to Start...Control Panel...System...Advanced tab...Performance Settings button.7) Click on the Advanced tab, then on the Virtual Memory Change button8) Re-enter the settings that you wrote down in step 3. Click OK to exit all the dialogs.9) Reboot your system10) Check to make sure the settings are correct.Here's some links for the memory testers (they're all free):http://www.simmtester.com/page/products/doc/download.asphttp://oca.microsoft.com/en/windiag.asphttp://www.memtest.org/http://www.memtest86.com/Any errors at all means bad memory - no errors means it just didn't find anything (not that the RAM is good). The longer the test runs, the better (I suggest a minimum of 2 hours and a maximum of 8 for normal purposes)Finally, we come to the repair of the registry itself (this being the 3rd of the most possible causes for this problem). First, I'd like to suggest that you get a copy of ERUNT, a free registry backup program. It comes bundled with NTREGOPT - a free program to optimize your registry. It's available for free from here: http://www.larshederer.homepage.t-online.de/erunt/ The first step in repairing your registry is to back it up (hence the recommendation for you to use ERUNT). Here's a bunch of links on registry repair:http://support.microsoft.com/?kbid=822705&SD=techhttp://support.microsoft.com/default.aspx?...kb;en-us;307545http://aumha.org/regfiles.htmhttp://www.google.com/search?hl=en&lr=&q=r...+xp&btnG=Searchhttp://support.microsoft.com/kb/322756Sounds like an awful lot of trouble to me. Now, assuming that there are no other hardware issues that are causing this (see the first article) - then a software fix would be in order. BUT, I don't know that there aren't any other hardware issues - so take this advice with a grain of salt!And, being as I'm lazy, I'd just do a repair install of XP (instructions here: http://www.michaelstevenstech.com/XPrepairinstall.htm ) and be done with it. A repair install will leave your programs, files, and settings intact - while "repairing" the operating system (Microsoft refers to this as a reinstallation).BUT, you'll have to visit Windows Update immediately afterwards to ensure that you've still got the latest updates (because Windows Update is more current than the CD that you used to do the repair install).Good Luck!

Edited November 17, 2005 by usasma

[dagger2000]

ok hi, this is my frist time posting hope you dont mind. i m actually having the same problem, my comp when ever i run registry mecahnic or the new spyware agent that looks through your reg i get rebooted, except no errors or anything, its like someone pushed the power button. im baffled. i cant figured it out. when i do spysheriff (microsofts new toy) it digs through my reg and says theres some stuff in there but as soon as it pulls it up it automatically shuts down, it didnt start doing this up until a few months ago, any suggestions?

[patio]

dagger it's probably best if you start a new thread with your problem. It helps to keep things sorted...And Welcome Aboard !patio.

[stupdasso]

Hey all, I thought I would bring this topic back up thinking someone may have an answer to it by now since I am still having the problem. Thanks in advance for any help you can provide.Dan

[Marsden11]

It is very simple... do NOT run Registry tools. You do NOT need them. They are NOT going to make your systems run faster and are more likely to hose your Registry which you are experiencing now.If you are going to run CHKDSK /F don't. Instead run CHKDSK /R as the /F switch only fixes. The /R switch fixes and recovers corrupt data. /R implies /F

[stupdasso]

It is very simple... do NOT run Registry tools. You do NOT need them. They are NOT going to make your systems run faster and are more likely to hose your Registry which you are experiencing now.If you are going to run CHKDSK /F don't. Instead run CHKDSK /R as the /F switch only fixes. The /R switch fixes and recovers corrupt data. /R implies /F

Marsden, You are quite correct about running any reg tools, but when you want to get rid of spyware registry entries and you don't want to spend hours finding where they are at in the registry, then you need to run certain programs that scan the registry which makes it a lot easier to get rid of spyware entries. Some of the reg tools out there do a very good job on cleaning up the registry of bad or obsolete entries which does slow computer performance. So if I can get the problem fixed... why not? I know there are a lot of knowledgeable people on this forum and why not pick their brain if I can.Dan Edited May 4, 2006 by stupdasso

[Marsden11]

Any respectable anti spyware program will remove damaging entries. You certainly don't need "another" tool to do that job.

So if I can get the problem fixed... why not?

You are assuming you are fixing the problem and not creating more issues. You are also assuming that your favorite Reg cleaner was perfectly written with zero chance of errors. The problem here is that a small error in cleaning your Registry can hose your system.Please provide some links that can prove cleaning your Registry improves computer performance. Sounds very similar to programs that claim to optimize your system memory. Or how removing unused system services will improve computer performance. Unless of course saving several hundred milliseconds at system startup will be very noticeable.

[stupdasso]

Any respectable anti spyware program will remove damaging entries. You certainly don't need "another" tool to do that job. You are assuming you are fixing the problem and not creating more issues. You are also assuming that your favorite Reg cleaner was perfectly written with zero chance of errors. The problem here is that a small error in cleaning your Registry can hose your system.Please provide some links that can prove cleaning your Registry improves computer performance. Sounds very similar to programs that claim to optimize your system memory. Or how removing unused system services will improve computer performance. Unless of course saving several hundred milliseconds at system startup will be very noticeable.

Here is a link directly to the Microsoft KB article Registry editing The article may be a little old but it still pertains to WinXP. Scroll down to the "Cleaning The Registry" part of the article. I know that "Any respectable anti spyware program will remove damaging entries". But that is part of my problem. When I use Ad-Aware and it starts to scan the registry that is when I get the error, get it? :hmm:Oh and here is an Updated article Speed up your PC by cleaning your registry Edited May 4, 2006 by stupdasso

[Gus K]

I thoroughly agree with Marsden on the use of cleaners. Forums are littered with posts of folks who have hosed their systems after such cleanings. And even though for some all seems fine, sometime later when they open a seldom used program they can find it broken and start searching for answers, having forgotten about their previous cleaning. The second MS site link that was provided intrigued me though. MS must know the registry better than most (I think).

Here is a link directly to the Microsoft KB article Registry editing The article may be a little old but it still pertains to WinXP.

This link concerned W98, not XP and the software mentioned is years old and generally not available. It's latest incarnation jv16 showed over 1000 'errors' in my rig. It's a wonder it still works ( ), but I do like jv16's 'Installed Software' module for removing errant reg entries after an uninstall of a program.Well I took the plunge and let MS's online scan do it's work (after making a new Acronis image). It found about 284 bad entries and I went with it. So far so good (only time will tell). My rig seemed to restart a tad quicker, but I've got no hard evidence to back that up. Jv16 now shows 435 errors. I'll let those ride.

[zlim]

1. dump regClean; it is no longer supported by MS and you are using it on an OS that it wasn't intended forhttp://www.pcworld.com/downloads/file_desc...,RSS,RSS,00.asp2. dump Registry Mechanic. I've read of numerous problems from that APP.Here is a comparison from Oct. 2005http://www.informationweek.com/story/showA...cleID=171203805He recommends EasyCleaner. (I had a problem after running v2 so I removed this from my system). I have never had a problem with CCleaner and I save all registry entries that are removed so I can reinstall if there is a problem.CHECK your RAM. I've read a post with the sysdata.xml error and it was caused by bad RAM.and I found this but since you already have SP2, it may not apply.

Error Message:The system has recovered from a serious error. C:\Windows\Minidump020404-01.dmp C:\Docume~1\Darle~1\Locals~1\Temp\Wer5E.tmp.diroo\sysdata.xmlTranslation:This error message may appear after the system reboots unexpectedly at random times.This error message reveals a problem with a memory dump (an inventory of the contents of computer memory; sometimes referred to as a minidump). It seems the OS created a memory dump file but forgot about it, so it’s attempting to create the file again. The resulting conflict leads to a serious error and the sudden system meltdown.Solution:The minidump error is sometimes associated with an outdated video driver (a program that facilitates communication between a hardware component and the rest of the system), so one potential solution is to download a driver update for the video card. You can get one by visiting the Support or Downloads area of the card manufacturer’s Web site. An updated driver may take care of the problem, but regardless of whether it does, we also recommend downloading the WinXP patch that Microsoft released to combat memory dump problems. You can get the update by visiting http://www.microsoft.com/downloads/details...40-F30014ADC3BBand clicking Download in the upper-right section of the page. Next, you should access the Windows Update site and install WinXP SP1a from the list of critical updates.Just for good measure, you should take a moment to purge your system of the minidump and Sysdata.xml files by deleting them from the C:/DOCUMENTS AND SETTINGS and C:/WINDOWS folders, respectively. You can restart the computer when the files are gone.

and this http://www.barrett.net/xpmemorydump.html Edited May 4, 2006 by zlim

[rbdietz]

Once the computer does restart I get this message, "The system has recovered from a serious error". When I click on more information it has these two lines C:\DOCUME~1\default\LOCALS~1\Temp\WERa131.dir00\Mini111505-02.dmpC:\DOCUME~1\default\LOCALS~1\Temp\WERa131.dir00\sysdata.xml

XML just a specially formated text file.Have you looked at sysdata.xml in notepad?Maybe that would provide a clue.