and did it find any errors? If it did, you will need to run it again with
/F. In all likelyhood, you will need to let it schedule itself to run on
next startup.
You should then immediately restart the system and run the chkdsk--allow
some time for this. If you forget to do it now, it will happen
unexpectedly....
"Richiepoobubblesbonbonpercyfilth"
<(E-Mail Removed)> wrote in
message news:266FA05D-2EB1-49DB-936D-(E-Mail Removed)...
>i ran CHDSK but (F parameter not specified
> Running CHKDSK in read only mode)
>
> "Engel" wrote:
>
>> Hello mon,
>>
>>
>> Maybe you could try doing CHKDSK and see if it corrects the problem.
>> -- - - -
>
>>
>>
>>
>> Few questions
>>
>> Do you have Windows Live OneCare installed?
>>
>>
>> What do you see in the system event logs around the time of the crash???
>> Can you check the event log (start | run | eventvwr) and look at the
>> System log for any error messages from "Windefend" ? There should be an
>> error
>> entry with some more information.
>>
>>
>> What action brings up that message?
>> Manually or Automatic Scan.
>> Quick or Full scan
>>
>>
>> So does the same thing happen when you reboot into Safe Mode and run a
>> scan?
>>
>> I'm sure more knowledgeable people will be along sººn
>> - -- ---
>>
>>
>>
>>
>>
>> "mon" wrote:
>>
>> > Looks as though no-one has had 'error 0x8050800c' in Defender for quite
>> > a
>> > while.
>> > I am running XP pro Sp3.
>> > Windows Defender Version: 1.1.1593.0
>> > Engine Version: 1.1.3520.0
>> > Definition Version: 1.33.9651.0
>> > Every scan crashes with unexpected 'error 0x8050800c'.
>> > Any ideas?
>> >
|