"Malke" <> wrote in message
news:e$...
> Tae Song wrote:
>
>>
>> "Sergey Kishkevich" <> wrote in message news:...
>>> Message-ID: <>
>>> X-Mailer: http://www.umailcampaign.com, ip log:212.98.185.123
>>> Newsgroups: microsoft.public.windows.vista.general
>>> NNTP-Posting-Host: 22.bb.5446.static.theplanet.com 70.84.187.34
>>> Path: TK2MSFTNGP01.phx.gbl!TK2MSFTNGP04.phx.gbl!newspe.c om
>>> Lines: 1
>>> Xref: TK2MSFTNGP01.phx.gbl
>>> microsoft.public.windows.vista.general:1336816
>>>
>>> Unfortunately, Event log doesn't contain any useful information. The
>>> latest
>>> thing I did with my hardware - I added two 1T HDD in RAID 1. The main
>>> HDD
>>> (Seagate 500G ES.2) used for OS was not updated. Do you know any tool to
>>> monitor when HDD switches in power safe mode?
>>>
>>> url:http://ureader.com/msg/168736794.aspx
>>
>> Just rename DfrgNtfs.exe to something else for an hour. If the problem
>> doesn't disappear you can change it back.
>
> I really don't know why you are persisting in thinking this is a software
> issue, especially in light of the new information from the OP which you
> quoted above.
>
> Malke
> --
> MS-MVP
> Elephant Boy Computers - Don't Panic!
> http://www.elephantboycomputers.com/#FAQ
>
I already said I had the same exact problem. Just what harm is there in
renaming DfrgNtfs.exe for a short while?
I won't be recommending a solution I haven't tried and tested.