Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Darrell_H_
New Contributor I
185 Views

Handle leaks when using the media sdk.

Hi everyone. I'm using the Intel media sdk to decode an H.264 live video stream for broadcasting with an Intel graphics card, on an x64 Windows 7.
The streaming process meets serious handle leaks when it keeps initializing the decoder, decoding with it, and then closing it.
The handle count can grow up to more than 20 throusand and keeps growing.

I use 64-bit WinDbg to track down the leaks. I find that the huge amount of handles are mostly handles to Windows events, and WinDbg reveals the increasing event handles are opened by OpenEvent() function in the function invocation herarchy under MFXVideoDECODE_Init().

Here's WinDbg commands I use to track down the problem, and their outputs.

The following is the status of handles after the process has run for a while.

<code>


0:055> !handle
...
929 Handles
Type               Count
None               5
Event              656
Section            14
File               51
Directory          2
Mutant             14
WindowStation      2
Semaphore          76
Key                12
Thread             71
Desktop            1
IoCompletion       9
Timer              3
KeyedEvent         1
TpWorkerFactory    12

</code>

 

And the following is the status of one of the increasing handles to the event. Apparently the handle count of the event is too large.

<code>

0:055> !handle 718 f
Handle 718
  Type             Event
  Attributes       0x10
  GrantedAccess    0x1f0002:
         Delete,ReadControl,WriteDac,WriteOwner,Synch
         ModifyState
  HandleCount      502
  PointerCount     509
  Name             \BaseNamedObjects\IGFXKMDNotifyBatchBuffersComplete
  Object Specific Information

</code>

 

And the call stack of the thread opening the event. In the listing, we see the increasing handles are opened by OpenEvent() function, while MFXVideoCORE_GetHandle() is under invocation.


<code>

0:055> !htrace 718
--------------------------------------
Handle = 0x0000000000000718 - OPEN
Thread ID = 0x0000000000000258, Process ID = 0x0000000000000d3c

0x0000000076fc171a: ntdll!NtOpenEvent+0x000000000000000a
0x000007fefd1c74aa: KERNELBASE!OpenEventA+0x00000000000000da
0x000007fedffef126: igdumdim64!OpenAdapter+0x000000000025e126
0x000007fedff26d95: igdumdim64!OpenAdapter+0x0000000000195d95
0x000007fedfef1a23: igdumdim64!OpenAdapter+0x0000000000160a23
0x000007fedfed74b2: igdumdim64!OpenAdapter+0x00000000001464b2
0x000007fee4326320: d3d9!DebugSetLevel+0x000000000006e500
0x000007fee42c4b61: d3d9!DebugSetLevel+0x000000000000cd41
0x000007fee42d66fd: d3d9!DebugSetLevel+0x000000000001e8dd
0x000007fef8985c8a: dxva2!DXVA2CreateVideoService+0x000000000000216a
0x000007fef898549f: dxva2!DXVA2CreateVideoService+0x000000000000197f
0x0000000005841ddb: libmfxhw64!MFXVideoVPP_GetVPPStat+0x000000000016679b
0x00000000056d220a: libmfxhw64!MFXVideoCORE_GetHandle+0x000000000001219a
0x00000000056d1b93: libmfxhw64!MFXVideoCORE_GetHandle+0x0000000000011b23
--------------------------------------
...

</code>

 

I set a break point in the bottom of the stack, where MFXVideoCORE_GetHandle() is located, and find out it is only called under one function invocation hierarchy:


<code>

0:055> bp libmfxhw64!MFXVideoCORE_GetHandle+0x0000000000011b23
0:055> g
...
Breakpoint 0 hit
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\Program Files (x86)\Intel\Media SDK\libmfxhw64.dll -
libmfxhw64!MFXVideoCORE_GetHandle+0x11b23:
00000000`06e01b93 8bf8            mov     edi,eax
0:033> kb
RetAddr           : Args to Child                                                           : Call Site
00000000`06e2db48 : 00000000`04f54310 00000000`04f54030 00000000`04a50698 00000000`00000000 : libmfxhw64!MFXVideoCORE_GetHandle+0x11b23
00000000`06e059ba : 00000000`00000000 00000000`01df4ed0 00000000`00000001 00000000`04f55f10 : libmfxhw64!MFXVideoVPP_GetVPPStat+0x22508
000007fe`f799fb4b : 00000000`0465aeb0 00000000`00000000 00000000`0f1bf9d0 00000000`0f1bf1f0 : libmfxhw64!MFXVideoDECODE_Init+0x1aa
000007fe`f799e32a : 00000000`01deffd0 00000000`01df4ed0 00000000`01df4ed0 cccccccc`cccccccc : IntelMediaDecoder!MFXVideoDECODE::Init+0x3b
...

</code>

 

I extracted the main operation procedure of the source code as follows.

 

<code>

while (m_isRunning)
{
    mfxStatus sts = MFX_ERR_NONE;

    MFXVideoDECODE *m_pMFXDecoder = new MFXVideoDECODE(m_mfxSession);

    mfxVideoParam m_mfxVideoParams;
    MSDK_ZERO_MEMORY(m_mfxVideoParams);
    m_mfxVideoParams.mfx.CodecId = MFX_CODEC_AVC;
    m_mfxVideoParams.IOPattern = (mfxU16)MFX_IOPATTERN_OUT_VIDEO_MEMORY;
    m_mfxVideoParams.AsyncDepth = 1;

    sts = m_pMFXDecoder->DecodeHeader(&m_mfxBS, &m_mfxVideoParams);
    sts = m_pMFXDecoder->Query(&m_mfxVideoParams, &m_mfxVideoParams);
    sts = m_pMFXDecoder->QueryIOSurf(&m_mfxVideoParams, &Request);

    sts = m_pMFXDecoder->Init(&m_mfxVideoParams);

    // decoding...

    MSDK_SAFE_DELETE(m_pMFXDecoder);
}

</code>

 

So can someone help me find out how to stop the handles from endlessly increasing and ensure the streaming still functions properly?
Thanks!

 

0 Kudos
13 Replies
Jiandong_Z_Intel
Employee
185 Views

Hi Darrell,

Which product are you using ? Media Server Studio ?

For better understand your system. Please send mediasdk_system_analyzer log to me,  you can find mediasdk_system_analyzer under following folder.

<installed folder>\mediasdk\tools\mediasdk_system_analyzer.

Thanks

Zachary

Darrell_H_
New Contributor I
185 Views

Jiandong Z. (Intel) wrote:

Hi Darrell,

Which product are you using ? Media Server Studio ?

For better understand your system. Please send mediasdk_system_analyzer log to me,  you can find mediasdk_system_analyzer under following folder.

<installed folder>\mediasdk\tools\mediasdk_system_analyzer.

Thanks

Zachary

 

Hi Zachary. I am not using Media Server Studio. I directly copied the SDK lib files libmfx.lib, libmfxmd.lib, and libmfxsw64.dll, and associated SDK header files into my Visual Studio project and then compiled them.

I list the mediasdk_system_analyzer log of the system running the decoder below:

Intel Media SDK System Analyzer (64 bit)


The following versions of Media SDK API are supported by platform/driver:

        Version Target  Supported       Dec     Enc
        1.0     HW      Yes             X
        1.0     SW      No
        1.1     HW      Yes             X
        1.1     SW      No
        1.3     HW      Yes             X
        1.3     SW      No
        1.4     HW      Yes             X
        1.4     SW      No
        1.5     HW      Yes             X
        1.5     SW      No
        1.6     HW      Yes             X
        1.6     SW      No
        1.7     HW      No
        1.7     SW      No
        1.8     HW      No
        1.8     SW      No

Graphics Devices:
        Name                                         Version             State
        Intel(R) HD Graphics                         9.18.10.3071        Active

System info:
        CPU:    Intel(R) Celeron(R) CPU 1037U @ 1.80GHz
        OS:     Microsoft Windows 7
Installed Media SDK packages (be patient...processing takes some time):


Tips:
 - SW target does not work: make sure Media SDK DLL (e.g. libmfxsw64.dll)
   is located in your executable path or in system path

Analysis complete... [press ENTER]

 

Darrell_H_
New Contributor I
185 Views

Hi everyone. I modified the SDK sample sample_decode, making it continually invoke MFXVideoDECODE_Init() and MFXVideoDECODE_Close().
When sample_decode is running, I see the handles in the process keep increasing, and with WinDbg I see the huge amount of handles are still opened with OpenEvent() in MFXVideoDECODE_Init().
The product I installed is w_inde_2015.2.027.exe, and the sample version is MediaSamples_Windows_6.0.0.68.msi.
The modified code is as below. Would someone please help me with this problem? Thanks!

#if defined(_WIN32) || defined(_WIN64)
int _tmain(int argc, TCHAR *argv[])
#else
int main(int argc, char *argv[])
#endif
{
    sInputParams        Params; // input parameters from command line
    mfxStatus sts = MFX_ERR_NONE; // return value check

    sts = ParseInputString(argv, (mfxU8)argc, &Params);
    MSDK_CHECK_PARSE_RESULT(sts, MFX_ERR_NONE, 1);

    bool con = true;
    while (con)
    {
        CDecodingPipeline   Pipeline;    // pipeline for decoding, includes input file reader, decoder and output file writer

        if (Params.bIsMVC)
            Pipeline.SetMultiView();

        sts = Pipeline.Init(&Params);
        MSDK_CHECK_RESULT(sts, MFX_ERR_NONE, 1);

        // print stream info
        /*Pipeline.PrintInfo();

        msdk_printf(MSDK_STRING("Decoding started\n"));*/

        Sleep(1);
    }

    /*for (;;)
    {
        sts = Pipeline.RunDecoding();

        if (MFX_ERR_INCOMPATIBLE_VIDEO_PARAM == sts || MFX_ERR_DEVICE_LOST == sts || MFX_ERR_DEVICE_FAILED == sts)
        {
            if (MFX_ERR_INCOMPATIBLE_VIDEO_PARAM == sts)
            {
                msdk_printf(MSDK_STRING("\nERROR: Incompatible video parameters detected. Recovering...\n"));
            }
            else
            {
                msdk_printf(MSDK_STRING("\nERROR: Hardware device was lost or returned unexpected error. Recovering...\n"));
                sts = Pipeline.ResetDevice();
                MSDK_CHECK_RESULT(sts, MFX_ERR_NONE, 1);
            }

            sts = Pipeline.ResetDecoder(&Params);
            MSDK_CHECK_RESULT(sts, MFX_ERR_NONE, 1);
            continue;
        }
        else
        {
            MSDK_CHECK_RESULT(sts, MFX_ERR_NONE, 1);
            break;
        }
    }*/

    msdk_printf(MSDK_STRING("\nDecoding finished\n"));

    return 0;
}


Darrell_H_
New Contributor I
185 Views

by the way, the command I use to run the sample is

 

sample_decode h264 -i test.h264 -o output.yuv -d3d -hw

Jiandong_Z_Intel
Employee
185 Views

Hi Darrell,

It looks like your graphic driver is not an up-to-date one.

Can you please download from following URL and setup up-to-date driver ?

https://downloadcenter.intel.com/product/81505   select "Intel® HD Graphics Production Driver for Windows* 7/8.1 64-bit (N-Series)".

Let's see if the same issue still happened.

Thanks

Zachary

 

 

Darrell_H_
New Contributor I
185 Views

Hi Zachary,

I've upgraded the graphics driver to version 10.18.10.4276, published on Aug 17th 2015.
Now I modified sample_decode and made it repeat the procedure of initializing the decoder, decoding with it, and closing it.
The handles are still increasing, but via WinDbg, I see they are not opened by OpenEvent() in MFXVideoDECODE_Init(), the new handles are opened by CreateEvent() in MFXVideoDECODE_DecodeFrameAsync().

The code in sample_decode I modified is as below.

#if defined(_WIN32) || defined(_WIN64)
int _tmain(int argc, TCHAR *argv[])
#else
int main(int argc, char *argv[])
#endif
{
    sInputParams        Params; // input parameters from command line
    mfxStatus sts = MFX_ERR_NONE; // return value check

    sts = ParseInputString(argv, (mfxU8)argc, &Params);
    MSDK_CHECK_PARSE_RESULT(sts, MFX_ERR_NONE, 1);

 bool con = true;
 while (con)
 {
  CDecodingPipeline   Pipeline;    // pipeline for decoding, includes input file reader, decoder and output file writer

  if (Params.bIsMVC)
   Pipeline.SetMultiView();

  sts = Pipeline.Init(&Params);
  MSDK_CHECK_RESULT(sts, MFX_ERR_NONE, 1);

  // print stream info
  /*Pipeline.PrintInfo();

  msdk_printf(MSDK_STRING("Decoding started\n"));*/

  for (;;)
  {
   sts = Pipeline.RunDecoding();

   if (MFX_ERR_INCOMPATIBLE_VIDEO_PARAM == sts || MFX_ERR_DEVICE_LOST == sts || MFX_ERR_DEVICE_FAILED == sts)
   {
    if (MFX_ERR_INCOMPATIBLE_VIDEO_PARAM == sts)
    {
     msdk_printf(MSDK_STRING("\nERROR: Incompatible video parameters detected. Recovering...\n"));
    }
    else
    {
     msdk_printf(MSDK_STRING("\nERROR: Hardware device was lost or returned unexpected error. Recovering...\n"));
     sts = Pipeline.ResetDevice();
     MSDK_CHECK_RESULT(sts, MFX_ERR_NONE, 1);
    }

    sts = Pipeline.ResetDecoder(&Params);
    MSDK_CHECK_RESULT(sts, MFX_ERR_NONE, 1);
    continue;
   }
   else
   {
    MSDK_CHECK_RESULT(sts, MFX_ERR_NONE, 1);
    break;
   }
  }

  msdk_printf(MSDK_STRING("\nDecoding finished\n"));

  Sleep(1);
 }

    return 0;
}

 

The new analyzer log is as follows.

Intel Media SDK System Analyzer (64 bit)


The following versions of Media SDK API are supported by platform/driver:

        Version Target  Supported       Dec     Enc
        1.0     HW      Yes             X
        1.0     SW      No
        1.1     HW      Yes             X
        1.1     SW      No
        1.3     HW      Yes             X
        1.3     SW      No
        1.4     HW      Yes             X
        1.4     SW      No
        1.5     HW      Yes             X
        1.5     SW      No
        1.6     HW      Yes             X
        1.6     SW      No
        1.7     HW      Yes             X
        1.7     SW      No
        1.8     HW      Yes             X
        1.8     SW      No

Graphics Devices:
        Name                                         Version             State
        Intel(R) HD Graphics                         10.18.10.4276       Active

System info:
        CPU:    Intel(R) Celeron(R) CPU 1037U @ 1.80GHz
        OS:     Microsoft Windows 7
Installed Media SDK packages (be patient...processing takes some time):


Tips:
 - SW target does not work: make sure Media SDK DLL (e.g. libmfxsw64.dll)
   is located in your executable path or in system path

Analysis complete... [press ENTER]


Please help me check on this problem. Thanks.

185 Views

Hi Darrell,

Thank you for bring this issue to our attention. We were able to reproduce this issue and it is a driver bug. We will further investigate this issue and hope to fix with our next driver update.

Thanks,  

Darrell_H_
New Contributor I
185 Views

Harsh Jain (Intel) wrote:

Hi Darrell,

Thank you for bring this issue to our attention. We were able to reproduce this issue and it is a driver bug. We will further investigate this issue and hope to fix with our next driver update.

Thanks,  

 

Hi Harsh.

OK, reply received, waiting for your driver update.

Thank you very much.

Darrell_H_
New Contributor I
185 Views

Harsh Jain (Intel) wrote:

 

 

Hi Harsh,

can you just develop and send me a temporary version of the driver first? A version with which the handle leaking bug is fixed.

Because my project is urgent and I must have this issue fixed with it as soon as possible.

Thanks.

185 Views

Hi Darrell,

Thank you for letting us know time requirement for fix on this issue. Currently, our Driver team have been notified on this issue. I will update once, I have any more information. 

Thank you, 

Darrell_H_
New Contributor I
185 Views

Hi Harsh,

OK, thank you, I wait for your reply.

Altug_S_
Beginner
185 Views

I also see a memory leak that seems to be originated from inside the MFX functions.

By using an i7-3770K processor, I decode 12SD+4HD live channels in realtime. DecodeFrameAsync and delayed SyncOperation mainly. Memory increases gradually, Windows debugging tool UMDH.exe shows the following backtrace. Intel sys_trace output also included.

Driver version is the same as the handle leaking one. Is this the same driver issue, which is to be fixed with the next release?

Regards,

Altuğ

 

+  8e7b4a ( 90e084 - 2653a) 487042 allocs    BackTraceD0CBEE0
+  473da5 ( 487042 - 1329d)    BackTraceD0CBEE0    allocations

    ntdll!MD5Final+0000A63D
    igdumdim64!OpenAdapter+0009FDAF
    igdumdim64!OpenAdapter+000A06F7
    igdumdim64!OpenAdapter+000A169E
    igdumdim64!OpenAdapter+00101E14
    igdumdim64!OpenAdapter+0010034D
    igdumdim64!OpenAdapter+000F9691
    igdumdim64!OpenAdapter+0011673D
    igdumdim64!OpenAdapter+000BC375
    d3d9!DecodeExecuteLH+0000014E
    d3d9!CDecodeDevice::DecodeExecute+00000136
    dxva2!DXVA2CreateVideoService+00002CD2
    igfxcmrt64!CmDevice_RT::LoadProgram+00000128
    igfxcmrt64!CmQueue_RT::Enqueue+00000299
    igfxcmrt64!CmQueue_RT::EnqueueCopyGPUToCPUFullStride+0000002E
    libmfxhw64!???+00000000 : 7FEE29E3ACE
    libmfxhw64!MFXVideoCORE_GetHandle+0000BB4F
    libmfxhw64!MFXVideoCORE_GetHandle+0000B7DC
    libmfxhw64!MFXVideoVPP_GetVPPStat+00004EBE
    libmfxhw64!MFXVideoVPP_GetVPPStat+00073869
    libmfxhw64!MFXVideoVPP_GetVPPStat+0000C35C
    libmfxhw64!MFXVideoVPP_GetVPPStat+003A6713
    libmfxhw64!MFXVideoVPP_GetVPPStat+003A68BA
    kernel32!BaseThreadInitThunk+0000000D
    ntdll!RtlUserThreadStart+00000021

+  8e7b4a ( 90e084 - 2653a) 487042 allocs    BackTraceD0CBC60
+  473da5 ( 487042 - 1329d)    BackTraceD0CBC60    allocations

    ntdll!MD5Final+0000A63D
    igdumdim64!OpenAdapter+0009FDAF
    igdumdim64!OpenAdapter+000A06F7
    igdumdim64!OpenAdapter+000A169E
    igdumdim64!OpenAdapter+00101E14
    igdumdim64!OpenAdapter+0010034D
    igdumdim64!OpenAdapter+000F9675
    igdumdim64!OpenAdapter+0011673D
    igdumdim64!OpenAdapter+000BC375
    d3d9!DecodeExecuteLH+0000014E
    d3d9!CDecodeDevice::DecodeExecute+00000136
    dxva2!DXVA2CreateVideoService+00002CD2
    igfxcmrt64!CmDevice_RT::LoadProgram+00000128
    igfxcmrt64!CmQueue_RT::Enqueue+00000299
    igfxcmrt64!CmQueue_RT::EnqueueCopyGPUToCPUFullStride+0000002E
    libmfxhw64!???+00000000 : 7FEE29E3ACE
    libmfxhw64!MFXVideoCORE_GetHandle+0000BB4F
    libmfxhw64!MFXVideoCORE_GetHandle+0000B7DC
    libmfxhw64!MFXVideoVPP_GetVPPStat+00004EBE
    libmfxhw64!MFXVideoVPP_GetVPPStat+00073869
    libmfxhw64!MFXVideoVPP_GetVPPStat+0000C35C
    libmfxhw64!MFXVideoVPP_GetVPPStat+003A6713
    libmfxhw64!MFXVideoVPP_GetVPPStat+003A68BA
    kernel32!BaseThreadInitThunk+0000000D
    ntdll!RtlUserThreadStart+00000021

+  8e7b36 ( 90e084 - 2654e) 487042 allocs    BackTrace12CFCD20
+  473d9b ( 487042 - 132a7)    BackTrace12CFCD20    allocations

    ntdll!MD5Final+0000A63D
    igdumdim64!OpenAdapter+0009FDAF
    igdumdim64!OpenAdapter+000A06F7
    igdumdim64!OpenAdapter+000A169E
    igdumdim64!OpenAdapter+00101E14
    igdumdim64!OpenAdapter+0010034D
    igdumdim64!OpenAdapter+000F9691
    igdumdim64!OpenAdapter+0011673D
    igdumdim64!OpenAdapter+000BC375
    d3d9!DecodeExecuteLH+0000014E
    d3d9!CDecodeDevice::DecodeExecute+00000136
    dxva2!DXVA2CreateVideoService+00002CD2
    igfxcmrt64!CmDevice_RT::LoadProgram+00000128
    igfxcmrt64!CmQueue_RT::Enqueue+00000299
    igfxcmrt64!CmQueue_RT::EnqueueCopyGPUToCPUFullStride+0000002E
    libmfxhw64!???+00000000 : 7FEE29E3ACE
    libmfxhw64!MFXVideoCORE_GetHandle+0000BB4F
    libmfxhw64!MFXVideoCORE_GetHandle+0000B7DC
    libmfxhw64!MFXVideoVPP_GetVPPStat+000ED31E
    libmfxhw64!MFXVideoVPP_GetVPPStat+000ED616
    libmfxhw64!MFXVideoVPP_GetVPPStat+000ED79B
    libmfxhw64!MFXVideoVPP_GetVPPStat+0000C35C
    libmfxhw64!MFXVideoVPP_GetVPPStat+003A6713
    libmfxhw64!MFXVideoVPP_GetVPPStat+003A68BA
    kernel32!BaseThreadInitThunk+0000000D
    ntdll!RtlUserThreadStart+00000021

+  8e7b34 ( 90e084 - 26550) 487042 allocs    BackTrace12CFCAA0
+  473d9a ( 487042 - 132a8)    BackTrace12CFCAA0    allocations

    ntdll!MD5Final+0000A63D
    igdumdim64!OpenAdapter+0009FDAF
    igdumdim64!OpenAdapter+000A06F7
    igdumdim64!OpenAdapter+000A169E
    igdumdim64!OpenAdapter+00101E14
    igdumdim64!OpenAdapter+0010034D
    igdumdim64!OpenAdapter+000F9675
    igdumdim64!OpenAdapter+0011673D
    igdumdim64!OpenAdapter+000BC375
    d3d9!DecodeExecuteLH+0000014E
    d3d9!CDecodeDevice::DecodeExecute+00000136
    dxva2!DXVA2CreateVideoService+00002CD2
    igfxcmrt64!CmDevice_RT::LoadProgram+00000128
    igfxcmrt64!CmQueue_RT::Enqueue+00000299
    igfxcmrt64!CmQueue_RT::EnqueueCopyGPUToCPUFullStride+0000002E
    libmfxhw64!???+00000000 : 7FEE29E3ACE
    libmfxhw64!MFXVideoCORE_GetHandle+0000BB4F
    libmfxhw64!MFXVideoCORE_GetHandle+0000B7DC
    libmfxhw64!MFXVideoVPP_GetVPPStat+000ED31E
    libmfxhw64!MFXVideoVPP_GetVPPStat+000ED616
    libmfxhw64!MFXVideoVPP_GetVPPStat+000ED79B
    libmfxhw64!MFXVideoVPP_GetVPPStat+0000C35C
    libmfxhw64!MFXVideoVPP_GetVPPStat+003A6713
    libmfxhw64!MFXVideoVPP_GetVPPStat+003A68BA
    kernel32!BaseThreadInitThunk+0000000D
    ntdll!RtlUserThreadStart+00000021

 

 

C:\Users\User\Desktop\ms2>C:\Users\User\Desktop\shared\msdk2013-tools\mediasdk_sys_analyzer\x64\sys_
analyzer.exe
Intel Media SDK System Analyzer (64 bit)


The following versions of Media SDK API are supported by platform/driver:

        Version Target  Supported       Dec     Enc
        1.0     HW      Yes             X       X
        1.0     SW      No
        1.1     HW      Yes             X       X
        1.1     SW      No
        1.3     HW      Yes             X       X
        1.3     SW      No
        1.4     HW      Yes             X       X
        1.4     SW      No
        1.5     HW      Yes             X       X
        1.5     SW      No
        1.6     HW      Yes             X       X
        1.6     SW      No

Graphics Devices:
        Name                                         Version             State
        Intel(R) HD Graphics 4000                    10.18.10.4276       Active
        VNC Mirror Driver                            1.7.0.0             08

System info:
        CPU:    Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz
        OS:     Microsoft Windows 7 Professional
        Arch:   64-bit

Installed Media SDK packages (be patient...processing takes some time):

Installed Media SDK DirectShow filters:

Installed Intel Media Foundation Transforms:
  Intel« Hardware M-JPEG Decoder MFT : {00C69F81-0524-48C0-A353-4DD9D54F9A6E}
  Intel« Hardware VC-1 Decoder MFT : {059A5BAE-5D7A-4C5E-8F7A-BFD57D1D6AAA}
  Intel« Hardware H.264 Decoder MFT : {45E5CE07-5AC7-4509-94E9-62DB27CF8F96}
  Intel« Hardware MPEG-2 Decoder MFT : {CD5BA7FF-9071-40E9-A462-8DC5152B1776}
  Intel« Quick Sync Video H.264 Encoder MFT : {4BE8D3C0-0515-4A37-AD55-E4BAE19AF471}
  Intel« Hardware Preprocessing MFT : {EE69B504-1CBF-4EA6-8137-BB10F806B014}

 


Tips:
 - SW target does not work: make sure Media SDK DLL (e.g. libmfxsw64.dll)
   is located in your executable path or in system path

Analysis complete... [press ENTER]

 

185 Views

Hi Altug,

Apologies that you are seeing this issue. With every driver release supports 2 hardware generations (current and previous). Current is Skylake (6th gen) and previous is Broadwell (5th gen) along with Haswell (4th gen) Win10 support. You are using i7-3770K (IvyBridge/3rd gen) processor which is three generations old . Unfortunately we have limited support on 3rd gen and could take longer turn around time for fix. Hence, to resolve this issue, I suggest following pointers 1) Workaround it in your application or 2) Upgrading to latest hardware. 

Any further questions please start a new thread on Media forum - https://software.intel.com/en-us/forums/intel-media-sdk, it will be easier for us to track and respond. 

Thanks, 

 

Reply