Re: Vista hang after inactivity

"Sergey Kishkevich" <test@tut.by> wrote in message news:...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Message-ID: <2b339bb49b7b43a9bb4e2899176a7063@newspe.com>
> X-Mailer: , 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.com
> 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:<!--colorc--><!--/colorc-->

Just rename DfrgNtfs.exe to something else for an hour. If the problem
doesn't disappear you can change it back.

 

Tae Song wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
>
> "Sergey Kishkevich" <test@tut.by> wrote in message news:...<!--coloro:green--><span style="color:green <!--/coloro-->
>> Message-ID: <2b339bb49b7b43a9bb4e2899176a7063@newspe.com>
>> X-Mailer: , 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.com
>> 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:<!--colorc--><!--/colorc-->
>
> Just rename DfrgNtfs.exe to something else for an hour. If the problem
> doesn't disappear you can change it back.<!--colorc--><!--/colorc-->

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!

 

"Malke" <malke@invalid.invalid> wrote in message
news:e$BpoBFPKHA.1876@TK2MSFTNGP06.phx.gbl...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Tae Song wrote:
><!--coloro:green--><span style="color:green <!--/coloro-->
>>
>> "Sergey Kishkevich" <test@tut.by> wrote in message news:...<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
>>> Message-ID: <2b339bb49b7b43a9bb4e2899176a7063@newspe.com>
>>> X-Mailer: , 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.com
>>> 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:<!--colorc--><!--/colorc-->
>>
>> Just rename DfrgNtfs.exe to something else for an hour. If the problem
>> doesn't disappear you can change it back.<!--colorc--><!--/colorc-->
>
> 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!
>
><!--colorc--><!--/colorc-->

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.