Registry error-----HELP!!!

G

Guest

I have always used 2 registry scan tools--Norton One Button Check Up and
System Mechanic.
I have used these programs successfully for years.
Now I cannot run these registry tools without my PC restarting shortly after
the scan begins.

Not sure what changes (hardware/software/config) prompted this behavior and
I cannot recall how long I have had the issue (6 mos?), but I have reached
the point where it is just pi**ing me off now and I am seeking solutions.

I run a Pentium Core 2 Duo with 1GB DDR2 RAM.
Windows XP Home SP2.

After forcing the BSOD I was able to copy the following STOP ERROR:
STOP 0X00000051 (0X00000004, 0X00000001, 0XE35F8368, 0X00100080)
 
S

Shenan Stanley

ChuckTheDuck said:
I have always used 2 registry scan tools--Norton One Button Check
Up and System Mechanic.
I have used these programs successfully for years.
Now I cannot run these registry tools without my PC restarting
shortly after the scan begins.

Not sure what changes (hardware/software/config) prompted this
behavior and I cannot recall how long I have had the issue (6
mos?), but I have reached the point where it is just pi**ing me off
now and I am seeking solutions.

I run a Pentium Core 2 Duo with 1GB DDR2 RAM.
Windows XP Home SP2.

After forcing the BSOD I was able to copy the following STOP ERROR:
STOP 0X00000051 (0X00000004, 0X00000001, 0XE35F8368, 0X00100080)

Do not take this personally - this post is meant for EVERYONE...

<sarcasm>Oh no! You use a tool clean your registry for you and something
seems to be going wrong with the system/tool? I am shocked! </sarcasm>

That's the problem with these tools - Russian Roulette... How many times can
you pull the trigger? Maybe you'll always win, maybe you won't. It's
better to learn how to maintain your system in the nitty-gritty 'get your
hands dirty' way - so you know everything that gets done instead of letting
some tool do it for you automagically... IMHO.

<the actual help>

First off - if your problem is centered around the running of these two
tools only - and not random system reboots when these tools are not in use -
you are in the wrong place for help. Your problem OBVIOUSLY lies with the
tools in question and you should contact the technical support for said
tools.

Having said that and given you are not even sure what prompted the promblem
to start/when - some general questions are necxessary to drill down to the
core of the issue..

Searching and reading - I have to ask first if you added any new
memory/replaced old memory/replace the motherboard or processor?

This article claims to have a fix for such errors in Windows XP... You'd
have to call and convince them you have this problem if you plan on not
paying for the call: http://support.microsoft.com/kb/815265

The most common theme is actually hardware issues. Think back - way back -
what hardware have you changed? Can you temporarily undo the hardware
changes - one at a time - until you find the problem area?
 
D

db

not likely that
the registry cleaner
removed anything that
you didn't authorize.

my guess is that you
have been experiencing
an issue(s) before deciding
to use a registry cleaner(s)
and my guess is that the
use of them was not the first
time as well for this particular
discussion.

in any case, you likely
have backups of the registry
since i know that system mechanic
takes the extra step.

also, if norton
was used then it likely
removed a corrupted registry
key or system file since
registry cleaners sometimes
clean more than just the
registry, like trash files, etc

i'm not a fan
of norton. but i
would guess that since norton
is supposedly a "great" system
it likely made a restore point
either in windows or inside
one of its symantec modules.

something to keep in mind
is that if there was a corrupt
system file that was deleted,
then it likely needs a genuine
replacement...


you should look into those
errors a bit more rather
than scap goating a registry
cleaner....


- db

I have always used 2 registry scan tools--Norton One Button Check Up and
System Mechanic.
I have used these programs successfully for years.
Now I cannot run these registry tools without my PC restarting shortly after
the scan begins.

Not sure what changes (hardware/software/config) prompted this behavior and
I cannot recall how long I have had the issue (6 mos?), but I have reached
the point where it is just pi**ing me off now and I am seeking solutions.

I run a Pentium Core 2 Duo with 1GB DDR2 RAM.
Windows XP Home SP2.

After forcing the BSOD I was able to copy the following STOP ERROR:
STOP 0X00000051 (0X00000004, 0X00000001, 0XE35F8368, 0X00100080)
 
G

Guest

As a note, I have recently used the Windows Live One Care Safety Scaner and
received the same STOPERROR when it scanned the registry.
So while I am NOT sure the problem was not caused by 3rd party scanners, I
AM now sure that the BSOD and STOP ERROR are not isolated to only the Norton
and Sys Mech programs.

I have a registry problem and i simply do not know how to resolve it now.
 
S

Shenan Stanley

ChuckTheDuck said:
As a note, I have recently used the Windows Live One Care Safety
Scaner and received the same STOPERROR when it scanned the registry.
So while I am NOT sure the problem was not caused by 3rd party
scanners, I AM now sure that the BSOD and STOP ERROR are not
isolated to only the Norton and Sys Mech programs.

I have a registry problem and i simply do not know how to resolve
it now.

Let me say I don't trust OneCare even as much as I trust the other two...
I'd recommend NORTON 2004 circa products before OneCare - and those were
just sad and resource-hogging. ;-)

I'd still say you need to check your memory and any new hardware you
installed inthe last 6 months.
Also - update all your hardware drivers straight from each hardware
manufacturer's web site...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top