locked
Interpreting Kernel Event Error Log for video decompression freeze bug RRS feed

  • Question

  • I have an HTPC running Windows 7 home SP1 and it has always frozen the system when playing any MP4, based video, streamed or local.  The whole system would stay unresponsive and audio buffer would loop playing the same signal until the system unfreezes about 30 seconds later.  It never happened with DVD's, or with audio files, so I narrowed it down to MP4's that probably use hardware acceleration.  The CPU would spike and go back to normal, and the process repeats itself every few minutes.

    I used to have an ATI when it started this problem, then I installed an NVIDIA card and re-installed W7 and the problem persisted, to my dismay.  I had no indication of what was causing it, until I started surfing the Event Logs and found a Kernel Event log, but I don't know how to interpret it to solve my problem.  I don't know which compressor is being used, and I tried using GraphEdit to find out, but it would not show the compressor.

    Any help interpreting the data I got would be greatly appreciated.  I have the dump files associated with this error.  Thanks.

    UCFAerokid

    --------------------------------------------------------------------------------------------------------------------

    Version=1
    EventType=LiveKernelEvent
    EventTime=129916926938624423
    ReportType=4
    Consent=1
    ReportIdentifier=f5ffca95-fab4-11e1-bcf3-9e14c23c7093
    Response.type=4
    DynamicSig[1].Name=OS Version
    DynamicSig[1].Value=6.1.7601.2.1.0.768.3
    DynamicSig[2].Name=Locale ID
    DynamicSig[2].Value=1033
    Sec[0].Key=BCCode
    Sec[0].Value=117
    Sec[1].Key=BCP1
    Sec[1].Value=84B5B008
    Sec[2].Key=BCP2
    Sec[2].Value=8EF4CED8
    Sec[3].Key=BCP3
    Sec[3].Value=00000000
    Sec[4].Key=BCP4
    Sec[4].Value=00000000
    Sec[5].Key=OS Version
    Sec[5].Value=6_1_7601
    Sec[6].Key=Service Pack
    Sec[6].Value=1_0
    Sec[7].Key=Product
    Sec[7].Value=768_1
    File[0].CabName=WD-20120909-1531.dmp
    File[0].Path=WD-20120909-1531.dmp
    File[0].Flags=65538
    File[0].Type=2
    File[0].Original.Path=C:\Windows\LiveKernelReports\WATCHDOG\WD-20120909-1531.dmp
    File[1].CabName=sysdata.xml
    File[1].Path=WER-1489263-0.sysdata.xml
    File[1].Flags=65538
    File[1].Type=5
    File[1].Original.Path=C:\Windows\Temp\WER-1489263-0.sysdata.xml
    File[2].CabName=WERInternalMetadata.xml
    File[2].Path=WERBA69.tmp.WERInternalMetadata.xml
    File[2].Flags=65538
    File[2].Type=5
    File[2].Original.Path=C:\Windows\Temp\WERBA69.tmp.WERInternalMetadata.xml
    FriendlyEventName=Video hardware error
    ConsentKey=LiveKernelEvent
    AppName=Windows
    AppPath=C:\Windows\System32\WerFault.exe
    ReportDescription=A problem with your video hardware caused Windows to stop working correctly.

    -------------------------------------------------------------------------------------------------------------

    <?xml version="1.0" encoding="UTF-16"?>
    <WERReportMetadata>
        <OSVersionInformation>
            <WindowsNTVersion>6.1</WindowsNTVersion>
            <Build>7601 Service Pack 1</Build>
            <Product>(0x3): Windows 7 Home Premium</Product>
            <Edition>HomePremium</Edition>
            <BuildString>7601.17803.x86fre.win7sp1_gdr.120330-1504</BuildString>
            <Revision>1130</Revision>
            <Flavor>Multiprocessor Free</Flavor>
            <Architecture>X86</Architecture>
            <LCID>1033</LCID>
        </OSVersionInformation>
        <ProblemSignatures>
            <EventType>LiveKernelEvent</EventType>
        </ProblemSignatures>
        <DynamicSignatures>
            <Parameter1>6.1.7601.2.1.0.768.3</Parameter1>
            <Parameter2>1033</Parameter2>
        </DynamicSignatures>
        <SystemInformation>
            <MID>01679552-5A11-4526-97B0-C2D2D8B32483</MID>
            <SystemManufacturer>System manufacturer</SystemManufacturer>
            <SystemProductName>P5K</SystemProductName>
            <BIOSVersion>1201</BIOSVersion>
        </SystemInformation>
    </WERReportMetadata>

    ---------------------------------------------------------------------------------------------------------------------


    Monday, October 1, 2012 3:20 AM

Answers

  • The main thing I saw when I looked at the dump is that your NVidia driver might be slightly outdated (I think there is a slightly newer release from August or September). Have you tried disabling timeout detection? The worst that will happen will be that the computer appears to stop responding, even though it is just the GPU that stops.

    0: kd> lmvm nvlddmkm
    start    end        module name
    8ee0e000 8f901000   nvlddmkm T (no symbols)          
        Loaded symbol image file: nvlddmkm.sys
        Image path: nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Tue May 15 01:34:51 2012 (4FB2071B)
        CheckSum:         00ADD7B9
        ImageSize:        00AF3000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Mini Kernel Dump does not contain unloaded driver list



    • Marked as answer by Leo Huang Monday, October 8, 2012 2:55 AM
    Wednesday, October 3, 2012 5:07 PM

All replies

  • This is error 0x117 indicates VIDEO_TDR_TIMEOUT_DETECTED. This is practically the same error as 0x116 - VIDEO_TDR_ERROR, but this indicates that you have non-default registry settings applied to detect timeouts and bugcheck when they occur.

    http://mikemstech.blogspot.com/2011/12/troubleshooting-0x116-videotdrerror.html

    Could you upload the files in c:\windows\minidump to skydrive, share to everyone, and post a link on this thread for further analysis?

    Monday, October 1, 2012 3:26 AM
  • Thank you, Mr. Burr.

    The dump files are here:  dump files .

    I read your article, and it's pretty enlightening.  Seems that the MP4 decompressors could be timing out the GPU.  I'm surprised it happened with both NVidia and ATI cards, but it may be more a fault with the registry settings than with the cards.  I look forward to hear what you can find, and to learn how to look into these types of bugs myself, being a Windows developer.  Thanks again.

    Tuesday, October 2, 2012 6:39 AM
  • The main thing I saw when I looked at the dump is that your NVidia driver might be slightly outdated (I think there is a slightly newer release from August or September). Have you tried disabling timeout detection? The worst that will happen will be that the computer appears to stop responding, even though it is just the GPU that stops.

    0: kd> lmvm nvlddmkm
    start    end        module name
    8ee0e000 8f901000   nvlddmkm T (no symbols)          
        Loaded symbol image file: nvlddmkm.sys
        Image path: nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Tue May 15 01:34:51 2012 (4FB2071B)
        CheckSum:         00ADD7B9
        ImageSize:        00AF3000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Mini Kernel Dump does not contain unloaded driver list



    • Marked as answer by Leo Huang Monday, October 8, 2012 2:55 AM
    Wednesday, October 3, 2012 5:07 PM
  • i have the same problem did you fix it ? how i can fix it ?


    Monday, October 15, 2012 10:26 PM