Constant Registry Corruption

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hey all, I am having a problem where every 3 weeks or so my registry gets
corrupted...I know how to fix this generally, but once I have replaced the
registry files I get corruptions in the system32\driver folder as well...if I
keep replacing these files eventually I just get the 'blue screen of death'
anyway so it's pointless. Does anyone know why the registry keeps breaking?

I dont know if it helps but, I am running McAfee Security Center, and that
is nearly always the first program that goes..the icon turns black (meaning
it's disabled) and then I know the wave of nonesense is coming. The pc
freezes, and I get files missing messages upon restarting.

Is there anything I can do to protect against this more efficiently? For
example a program which can automatically fix the registry if it gets
threatened, or idealy stop them from being threatened in the first place.

Thanks a lot for any help or advice.
Alex
 
I know how to fix the registry, that isnt what I asked. I asked if there is
a way to stop it from breaking...or if there is an explination for it
happening every 3 weeks.

regards
Alex
 
Al said:
Hey all, I am having a problem where every 3 weeks or so my registry
gets corrupted...I know how to fix this generally, but once I have
replaced the registry files I get corruptions in the system32\driver
folder as well...if I keep replacing these files eventually I just
get the 'blue screen of death' anyway so it's pointless. Does anyone
know why the registry keeps breaking?

I dont know if it helps but, I am running McAfee Security Center, and
that is nearly always the first program that goes..the icon turns
black (meaning it's disabled) and then I know the wave of nonesense
is coming. The pc freezes, and I get files missing messages upon
restarting.

Is there anything I can do to protect against this more efficiently?
For example a program which can automatically fix the registry if it
gets threatened, or idealy stop them from being threatened in the
first place.

Thanks a lot for any help or advice.
Alex

First eliminate any spyware.
What You Should Know About Spyware
http://www.microsoft.com/athome/security/spyware/devioussoftware.mspx

CAUTION!!!!! Removing some spyware can damage the Winsock stack and you may
not be able to connect to the Internet. Before you try to remove spyware,
download a copy of LSP-Fix - a free program to repair damaged Winsock 2
stacks (all Windows versions)
http://www.cexx.org/lspfix.htm
Winsockfix for W95, W98, ME, NT, 2000, XP
http://www.tacktech.com/pub/winsockfix/WinsockFix.zip
Directions here: http://www.tacktech.com/display.cfm?ttid=257
WinXP:
Get WinSockxpFix
http://www.spychecker.com/program/winsockxpfix.html
How to Reset Internet Protocol (TCP/IP) in Windows XP
http://support.microsoft.com/kb/299357
In WinXP SP2: You can fix Winsock by going to Start | Run and typing
CMD
In the command window type
netsh winsock reset

See
Dealing with Unwanted Spyware and Parasites
http://mvps.org/winhelp2002/unwanted.htm
Help with Hijackware
http://aumha.org/a/parasite.htm
http://aumha.org/a/quickfix.htm
http://aumha.net/viewtopic.php?t=5878
http://mvps.org/winhelp2002/unwanted.htm
http://inetexplorer.mvps.org/data/prevention.htm
http://inetexplorer.mvps.org/data/tshoot.htm
http://www.mvps.org/sramesh2k/Malware_Defence.htm
http://defendingyourmachine.blogspot.com

--
Frank Saunders, MS-MVP, IE/OE
Please respond in Newsgroup only. Do not send email
http://www.fjsmjs.com
Protect your PC
http://www.microsoft.com./athome/security/protect/default.aspx
http://defendingyourmachine.blogspot.com/
 
I suggest running chkdsk /r as one measure. Bad sectors or a failing hard
drive is one possible cause of these repeat events.
 
Bad ram is another possible cause.

Kerry

GTS said:
I suggest running chkdsk /r as one measure. Bad sectors or a failing hard
drive is one possible cause of these repeat events.
 
Kerry Brown said:
Bad ram is another possible cause.

Yeah, I'd agree w/ this. Test your RAM w/ memtest86+, it should run at
least 2 cycles w/ zero errors to be considered ok. Even a single error is
too many.

http://www.memtest.org/

get the "pre-compiled package for floppy", or if you have no floppy drive
then the "pre-compiled bootable ISO" [you'll need a cd burner program that
handles ISOs, like EZCD or Nero; I'm sure there are freebees out there
too].
 

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

Back
Top