Re: WinDBG Results.... Well... FileHook.sys ?

Edward Kim wrote:
>> Kurt Pruenner wrote:
>>
>> You need to install windbg and use it to analyze the memory dump:
>>
>> http://www.microsoft.com/whdc/devtools/debugging/default.mspx
>> http://www.networkworld.com/news/2005/041105-windows-crash.html
>>
>> Just set up the symbol server as shown in the networkworld.com article,
>> open your crashdump and run a "!analyze -v". That should tell you which
>> driver triggered the crash, but not neccessarily which caused it - as
>> BAD_POOL_HEADER errors usually occur when there's already some memory
>> corruption...
>>
>
>
> The Following logs shows the result of running WinDbg..
[snip]
> Probably caused by : FileHook.sys ( FileHook+580a )

Seems that piece of crap is the cause of many problems, not just
TSVN/Subversion:
http://www-01.ibm.com/support/docview.wss?ratlid=cctocbody&rs=984&uid=swg21248864

Stefan

-- 
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=1107104
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].