Community
cancel
Showing results for 
Search instead for 
Did you mean: 
534 Views

MFXInit returns MFX_ERR_UNSUPPORTED since Windows 10 (1903) update

We have been using Intel QSV for H264 Encode/Decode within our own video communications software application for quite some time without any problems.  Recently, I updated my PC to version 1903 of Windows 10.  MFXInit for both the H264 Encode/Decode now return MFX_ERR_UNSUPPORTED. 

This is the code we run, which used to work without any problems:

mfxVersion minHWversion = {0,1};

sts = MFXInit(MFX_IMPL_HARDWARE_ANY, &minHWversion, &Session);

As well as returning (MFX_ERR_UNSUPPORTED), the Visual Studio 2019 debugger also gives the following errors:

onecore\windows\directx\database\helperlibrary\lib\directxdatabasequeryimpl.cpp(53)\d3d9.dll!6FEA882A: (caller: 6FEA89DE) ReturnHr(106) tid(2f98) 80004002 No such interface supported
onecore\windows\directx\database\helperlibrary\lib\directxdatabasequeryimpl.cpp(180)\d3d9.dll!6FEA89F7: (caller: 6FEA885D) ReturnHr(107) tid(2f98) 80004002 No such interface supported
onecore\windows\directx\database\helperlibrary\lib\directxdatabasequeryimpl.cpp(163)\d3d9.dll!6FEA887F: (caller: 6FEA7949) ReturnHr(108) tid(2f98) 80004002 No such interface supported
onecore\windows\directx\database\helperlibrary\lib\directxdatabasehelper.cpp(705)\d3d9.dll!6FEA79E3: (caller: 6FEA8116) ReturnHr(109) tid(2f98) 80004002 No such interface supported
onecore\windows\directx\database\helperlibrary\lib\directxdatabasehelper.cpp(820)\d3d9.dll!6FEA8189: (caller: 6FE2A6A6) ReturnHr(110) tid(2f98) 80004002 No such interface supported
onecore\windows\directx\database\helperlibrary\lib\directxdatabasehelper.cpp(515)\d3d9.dll!6FEA8264: (caller: 6FE0C673) ReturnHr(111) tid(2f98) 80004002 No such interface supported
onecore\windows\directx\database\helperlibrary\lib\directxdatabasehelper.cpp(515)\d3d9.dll!6FEA8264: (caller: 6FE0C673) ReturnHr(112) tid(2f98) 80004002 No such interface supported

onecore\windows\directx\database\helperlibrary\lib\directxdatabasequeryimpl.cpp(180)\dxgi.dll!6B5AC110: (caller: 6B5ABF76) ReturnHr(16) tid(2f98) 80004002 No such interface supported
onecore\windows\directx\database\helperlibrary\lib\directxdatabasequeryimpl.cpp(163)\dxgi.dll!6B5ABF98: (caller: 6B5AB3C9) ReturnHr(17) tid(2f98) 80004002 No such interface supported
onecore\windows\directx\database\helperlibrary\lib\directxdatabasehelper.cpp(705)\dxgi.dll!6B5AB462: (caller: 6B5AB9D0) ReturnHr(18) tid(2f98) 80004002 No such interface supported
onecore\windows\directx\database\helperlibrary\lib\directxdatabasehelper.cpp(820)\dxgi.dll!6B5ABA43: (caller: 6B57282E) ReturnHr(19) tid(2f98) 80004002 No such interface supported
onecore\windows\directx\database\helperlibrary\lib\directxdatabasehelper.cpp(515)\dxgi.dll!6B5ABB0B: (caller: 6B594DF2) ReturnHr(20) tid(2f98) 80004002 No such interface supported
onecore\windows\directx\database\helperlibrary\lib\directxdatabasehelper.cpp(515)\dxgi.dll!6B5ABB0B: (caller: 6B594DF2) ReturnHr(21) tid(2f98) 80004002 No such interface supported

I am using a i7-7700K (Kaby Lake) with Intel HD Graphics 630.  At the time of the update I was using driver version (25.20.100.6374) which was working.  As the Windows 10 update broke the Intel QSV encode/decode, I upgraded the GPU driver to version (26.20.100.6912), which made no difference, it still doesn't work.

I am using Intel Media SDK 2018 R2.  I've run the media SDK analyzer and it outputs the following (I've removed 1.00 to 1.24 for clarity):

        1.25    HW      Yes             X       X
        1.25    SW      Yes             X       X
        1.26    HW      Yes             X       X
        1.26    SW      Yes             X       X
        1.27    HW      Yes             X       X
        1.27    SW      Yes             X       X
        1.28    HW      Yes             X       X
        1.28    SW      No
        1.29    HW      Yes             X       X
        1.29    SW      No

Graphics Devices:
        Name                                         Version                    State
        AMD Radeon RX 5700                  26.20.13001.9005    Offline
        NVIDIA GeForce GTX 1660           26.21.14.3136          Offline
        Intel(R) HD Graphics 630              26.20.100.6912        Running / Full Power

System info:
        CPU:    Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz
        OS:     Microsoft Windows 10 Pro
        Arch:   64-bit

Installed Media SDK packages (be patient...processing takes some time):
        Intel(R) Media SDK 2018 R2 - HEVC GPU accelerated Encoder
        Intel(R) Media SDK 2018 R2 - Media Samples
        Intel(R) Media SDK 2018 R2 - Software Development Kit
        Intel(R) Media SDK 2018 R2 - Documentation for HEVC
        Intel(R) Media SDK 2018 R2 - HEVC SW Encoder
        Intel(R) INDE Media SDK for Windows 6.0.0.388
        Intel(R) Media SDK 2018 R2 - HEVC SW Decoder

Installed Media SDK DirectShow filters:

Installed Intel Media Foundation Transforms:
        Intel(R) Hardware M-JPEG Decoder MFT : {00C69F81-0524-48C0-A353-4DD9D54F9A6E}

I have re-installed GPU drivers and DirectX, while DxDiag reports no errors.

I am struggling to find the reason for the MFXInit failure, other than the Windows 10 (1903) update corrupting my PC system in some way.  Has anyone seen or knows anything about the errors I am getting?  Any suggestions about how to resolve this issue would be greatly appreciated.

Thank you.

0 Kudos
5 Replies
Mark_L_Intel1
Moderator
534 Views

Hi Robert,

I think this is a driver/runtime issue which causes the failure of the library. Which way did you update the graphic driver: Microsoft, vendor or Intel download center?

Could you reproduce with our sample code?

You can also refer to following posts to see if they give you some clues:

https://software.intel.com/en-us/forums/intel-media-sdk/topic/800921

https://software.intel.com/en-us/forums/intel-media-sdk/topic/806265

Mark

534 Views

Hi Mark,

Thank you for the response.  I have fixed the problem but it required down grading windows from version (1903) to (1809) and then carrying out a Windows Reset.  I think my system messed up the drivers or something, not really sure how or when it happened but the Reset has fixed all my problems.

I will recount the story incase someone else has similar issues.

In order to upgrade our software to H265, I downloaded Intel(R) Media SDK 2018 R2 and started testing the H265 sample encoders and decoders. These were working fine on my Windows 10 (1809) system.  I then started to integrate H265 into our software application, however, no matter what I did, I could not get the MFXVideoUSER_Load() function to load the H265 plugin, it kept returning MFX_ERR_NOT_FOUND.  I decided to upgrade the Intel GPU driver from the current (Windows Update version: 25.20.100.6373) to the latest (Intel Download Center: 26.20.100.6890).  This made matters worse as now the MFXInit() function would return MFX_ERR_UNSUPPORTED for even our H264 implementation that had been working fine for years.  Also the H265 sample encoder/decoder stopped working.  I rolled back the Intel GPU driver to version 25.20.100.6373, which made H264 work again but H265 was still falling at the MFXVideoUSER_Load() function.

With making no progress with getting H265 running, I decided to upgrade Windows 10 from (1809) to (1903) as it had recently become available for installation.  Upgrading to version (1903) then caused H264 to be unsupported, while the Intel driver (25.20.100.6373) was still the same as the one that was working fine in version (1809).  It was at this point I posted the original message on this forum.

After Reseting Windows 10 and downgrading to (1809), H264 works fine again and our integrated H265 code that just would not work before, works absolutely fine without any further code changes.

Regards.

Mark_L_Intel1
Moderator
534 Views

Hi Robert,

Sorry for the late response. Did you resolved it yet?

There is other post about 1903, could you check if our developer's suggestion help?

I also submitted a bug report to check it again.

Please let me know if this solves your problem.

Mark

534 Views

Hi Mark,

My problem is resolved as per my response on (07/31/2019, Quote #3).

Downgrading windows 10 from (1903) to (1809) and doing a Windows Reset fixed all my H264 and H265 issues.  As everything appears to be working correctly I haven't needed to upgrade to the latest Intel graphics driver, I am currently using the driver delivered via Windows Update (25.20.100.6373).

I have no plans to upgrade Windows 10 to version 1903 in the near future as everything is working fine now.  I lost too much time with the previous problems that I do not want to take the risk again so soon.  The upgrade to Windows 10 (1903) did not cause my initial problems, but I had hoped the upgrade would fix them, however it actually made them even worse.  With the Windows 10 Reset, which resolved of all my H264/5 problems, I am hoping that when I eventually upgrade to Windows 10 (1903) again, I won't have the same problems.

Regards,

Mark_L_Intel1
Moderator
534 Views

Hi Robert,

I discussed with dev team today about this issue. They have conclude the root-cause was in Windows Update mechanism that probably was installing Legacy driver over DCH driver and this led to such error.

After we suggested to make reset of Windows OS, issue was gone.

It seems related to 1903 only, here is the method to reset OS:

https://support.microsoft.com/en-us/help/17085/windows-8-restore-refresh-reset-pc

Mark

Reply