XP Pro SP3 machine with Norton 360 has died twice in 3 months due to MISSING BOOT MANAGER failure ... the first time I restored this by cloning to a new drive and running FIXMBR ... the second time I wasn't that lucky ... had to do a RECOVER INSTALL from a SP2 OS CD ... after doing SP3 followed by 150+ updates I was able to get back into the machine.
In both cases the root folder was clogged with over 20 thousand {***...***} files of various lengths (the file names resemble Registry Keys but are all random and don't match any thing in the registry) ... these started randomly populating again over a 24hr period so whatever was causing this original issue appears to be still active ... the machine has run no errors with DELL's Diags for over 24 hrs ... I scanned the machine with Microsofts safety Scan, Malwarebytes and Norton 360 but can't find anything ... sfc /scannow also revealed nothing.
I wanted to use filemon from Windows System Internals but this appears to have been discontinued by Microsoft ... they said to use ProcMon however this crashes ... as the hardware checks out, I suspect this crash may be related to whatever this machine is infected with?
Any other ideas would be welcome ... this machine has been running 24/7 for several years with plenty of customizations ... it would be a real chore to attempt to recover it's current state after a Clean install.
In both cases the root folder was clogged with over 20 thousand {***...***} files of various lengths (the file names resemble Registry Keys but are all random and don't match any thing in the registry) ... these started randomly populating again over a 24hr period so whatever was causing this original issue appears to be still active ... the machine has run no errors with DELL's Diags for over 24 hrs ... I scanned the machine with Microsofts safety Scan, Malwarebytes and Norton 360 but can't find anything ... sfc /scannow also revealed nothing.
I wanted to use filemon from Windows System Internals but this appears to have been discontinued by Microsoft ... they said to use ProcMon however this crashes ... as the hardware checks out, I suspect this crash may be related to whatever this machine is infected with?
Any other ideas would be welcome ... this machine has been running 24/7 for several years with plenty of customizations ... it would be a real chore to attempt to recover it's current state after a Clean install.