RegSeeker crashes - help!

  • Thread starter Thread starter ©®
  • Start date Start date
©

©®

I am using RegSeeker 1.35 build 1203 with XP Pro and often when I choose
Clean the registry or Startup entries and run these two - I often get
the BSOD and the PC restarts.
Sometimes I can stop the BSOD by unchecking HKEY_CLASSES_ROOT and
ActiveX/COM (CLSID) in the Clean the registry section. Not sure about
Startup entries.
Does anyone else have a similar problem?
Is there an upgrade?
Thanks
 
©® wrote in said:
I am using RegSeeker 1.35 build 1203 with XP Pro and often when I choose
Clean the registry or Startup entries and run these two - I often get
the BSOD and the PC restarts.
Sometimes I can stop the BSOD by unchecking HKEY_CLASSES_ROOT and
ActiveX/COM (CLSID) in the Clean the registry section. Not sure about
Startup entries.
Click to expand...

Sounds to me as if RegSeeker is choking on some data (possible
invalid) in one (or more) of those locations. Tried other cleaners,
any errors then?
I would also give both Spybot C&D <http://www.safer-networking.org/>,
AND Spywareblaster
<http://www.javacoolsoftware.com/spywareblaster.html> a run to
check/block for "bad" ActiveX controls (see webpages).
Would also install the free version of Winpatrol
<http://www.winpatrol.com>, for among other things to have a look at
your current startup settings for possible errors (and unwanted
programs) there (and for future control with apps and other "stuff"
loading at startup) Don't know if any of this will help, but IMHO
worth a try.

All the best,
Bjorn Simonsen
 
On my computer the RegSeeker main gui
screen has gone funny. All the command on the left-hand side are heavily
shaded balck and are not viewable. Only can see bit of it
by hovering the mouse over it.
Any suggestion?
Thanks.



I am using RegSeeker 1.35 build 1203 with XP Pro and often when I choose
Clean the registry or Startup entries and run these two - I often get
the BSOD and the PC restarts.
Sometimes I can stop the BSOD by unchecking HKEY_CLASSES_ROOT and
ActiveX/COM (CLSID) in the Clean the registry section. Not sure about
Startup entries.
Does anyone else have a similar problem?
Is there an upgrade?
Thanks
 
©® said:
I am using RegSeeker 1.35 build 1203 with XP Pro and often when I
choose Clean the registry or Startup entries and run these two - I
often get the BSOD and the PC restarts.
Sometimes I can stop the BSOD by unchecking HKEY_CLASSES_ROOT and
ActiveX/COM (CLSID) in the Clean the registry section. Not sure about
Startup entries.
Does anyone else have a similar problem?
Is there an upgrade?
Thanks
Click to expand...

This doesn't address your situation directly. However, I agree with Fred
Langa (see below), that the use of aggressive registry cleaners especially
in XP is completely unnecessary and potentially unsafe. I would try jv16
PowerTools or EasyCleaner.

From Fred Langa:
http://www.langa.com/newsletters/2004/2004-02-05.htm#3

".... on my XP system, I no longer notice any particular benefit from
aggressive Registry cleaning. So, some months ago, I asked myself: If
aggressive cleaning offers no discernable benefit, and may cause occasional
trouble, why am I doing it?

So I stopped using aggressive cleaners, and now use only the limited, but
virtually bulletproof cleaning of WinDoctor. If I didn't have WinDoctor, I
probably would use another cleaning tool but not in an aggressive way,
letting it clean only the most obvious, common Registry clutter.

I still clean my Win98 systems more rigorously, but XP simply doesn't seem
to need highly aggressive routine Registry maintenance."
 
Jordan said:
This doesn't address your situation directly. However, I agree with Fred
Langa (see below), that the use of aggressive registry cleaners especially
in XP is completely unnecessary and potentially unsafe. I would try jv16
PowerTools or EasyCleaner.
Click to expand...

I'v been using Regseeker for about 18 months on an XP system. I delete
all green finds and decide about the red ones individually. If a red
one points to a program which is no longer on my system I delete it,
else I keep it. This has kept me out of trouble al those months. I.e.
if you use RegSeeker sensibly it's a great registry cleaner. BTW, I
use the same strategy 2K and 98 systems.

Tom
 
Bjorn Simonsen said:
Sounds to me as if RegSeeker is choking on some data (possible
invalid) in one (or more) of those locations. Tried other cleaners,
any errors then?
Click to expand...
[...]

I've had errors and crashes with Total Uninstall. When there are certain
invalid characters involved. For instance when an idiot decides to have as
part of his software company subkey name a "\".

Another bad character might have been the colon, but now I'm going from
~memory, did not spend time recording which characters. Just, when the
problem arose, I tracked down and manually deleted the retardedly named
keys. After that TUN could deal with the cleaned remainder, not choke up.

I saw in TUN's history file, that its author has done updates in order
to survive when incompetent programmers inject the registry with bad
characters. My experience with the current version shows there is still
work to be done for these scenarios.

This whole story, it's not because I got confused about who the lead
character in the thread, RegSeeker; but in order to offer a parallel.
To support that this as theory of suspect cause. Some bad/invalid
characters in the registry are choking it. If the case, one would do
well to hunt those down - ie, stare down the "marked for deletion" keys
in RS for anything looking deformed. Then use a registry editor to purge
the suspects.
 
Back
Top