Mike said:
I have a neighbor who has a windows 7 desktop, she told me it wouldn't
boot, and even after repeated attempts to repair itself (the repair
utility reports that it was successful) it still won't boot, after
several attempts to repair itself we decided to reinstall windows from
the hidden partition (she didn't get a CD or DVD with the computer).
Windows installed and booted, installed several updates, I installed
Avast, OpenOffice, Chrome, Firefox and went home. A day later the
computer is having the same problem. While I was there I made sure SMART
was enabled, so next time I'm there I"ll boot into Ubuntu from a CD and
see what SMART reports.
Is this a common problem with windows 7? Any suggestions about how to
diagnose this, if SMART is not reporting errors?
TIA,
Mike
And if you check the Avast logs or quarantine folder or whatever,
what do you find ? Maybe Avast yanked something important ?
In this thread, they refer to a "chest", and Avast does have a log viewer,
but they don't mention whether a simple text file is available with log info
in it (for times when Windows is dead). You could at least locate the chest
folder and check its contents.
http://forum.avast.com/index.php?topic=42687.0
Does the user know how to do a clean shutdown ? Does she just
"turn off the power" ? This wouldn't normally hurt the machine,
as NTFS has a journal and the file system should be relatively
robust. And since you've reinstalled, the file system probably
got repaired at that point (the installer probably runs
chkdsk if it isn't starting with a clean partition).
You also have the option of doing an offline malware scan, with
the 196MB CD here. Just in case something nasty is lurking there.
On my machine, this takes an hour or two to scan C:, so you
have to allocate enough time for this. (Check it's working,
then walk away until done.) The scanner will pop up dialogs, but
the dialogs shouldn't prevent it from running to completion.
Then you can check the "report", to see what it found.
http://support.kaspersky.com/faq/?qid=208282163
As far as I know, the BIOS "enable SMART" option, is there so
that the BIOS can check the SMART stats at POST. I don't think
the BIOS influences the OS ability to read SMART for itself.
There's not much point in the BIOS disabling it. It's not
a security hole or anything.
*******
I've had problems myself, when doing two things. One was fooling
around with the System Volume Information contents. Another was
attempting to make changes to the file system from a Linux LiveCD
(just doing file cleanup of non-system files).
I didn't do enough fault isolation, to determine exactly what I
shouldn't be doing. What seems to be key here, is Volume Shadow
Service, which does things like build System Restore points,
and it also is used for building live system images while the
OS is running. If VSS was disabled, my guess is at least in
my case, the OS would be a lot more stable (less breakable).
But I'm not sure how this scenario fits with your neighbor.
They're not likely to be doing the kinds of things I was doing.
They'd have to be dual booting Linux, and messing around with the
Win7 partition.
In a dual boot scenario, if you have WinXP and Win7 on the same
computer, the System Restore in WinXP should be turned off. As
they don't play nice with each other's SVI folders. It's
too bad WinXP doesn't come with a "only meddle with C: please"
setting, instead of destroying any new disk that gets
connected to the WinXP OS. As a consequence, I leave System
Restore turned off on WinXP, so I won't forget if I slave up
the drive from my Win7 machine.
*******
First step when you return to the neighbor, is burn that set
of recovery DVDs from the hidden partition. That's your
insurance. Not only do you burn the DVDs, you also "image"
them immediately and store them on some hard drive. If the
DVDs get "bit rot", you can then burn another set. This will
likely take half the day, before you even get down to business.
I think when my laptop burned the set, it did a "verify" of
the media afterwards. At one time, there were computers that
would blindly burn a set, only allow you to burn one set,
but not verify, and if the media was bad, you were screwed.
An alternative, is to image the entire drive, making sure that
the hidden partition is included in the backup.
Paul