Thanks so much,
I can reproduce it with following error message, could you confirm? My environment is skull Cannon NUC and Windows 10, driver 6373.
Encoding Sample Version 22.214.171.1248 Input file format NV12 Output video AVC Source picture: Resolution 720x576 Crop X,Y,W,H 0,0,720,576 Destination picture: Resolution 720x576 Crop X,Y,W,H 0,0,720,576 Frame rate 25.00 Bit rate(Kbps) 3000 Gop size 28 Ref dist 4 Ref number 4 Idr Interval 0 Target usage speed Memory type system Media SDK impl hw Media SDK version 1.27 Processing started Frame number: 286800 [ERROR], sts=MFX_ERR_GPU_HANG(-21), CEncTaskPool::SynchronizeFirstTask, SyncOperation failed at src\pipeline_encode.cpp:157 [ERROR], sts=MFX_ERR_GPU_HANG(-21), CEncodingPipeline::GetFreeTask, m_TaskPool.SynchronizeFirstTask failed at src\pipeline_encode.cpp:1748 [ERROR], sts=MFX_ERR_GPU_HANG(-21), CEncodingPipeline::Run, m_pmfxENC->EncodeFrameAsync failed at src\pipeline_encode.cpp:1961 [ERROR], sts=MFX_ERR_GPU_HANG(-21), wmain, pPipeline->Run failed at src\sample_encode.cpp:1301 Frame number: 286872 Encoding fps: 227 C:\Users\test\Documents\Intel® Media SDK 2018 R2 - Media Samples 126.96.36.1998\_bin\x64>
I didn't get it at the first run(about 20minutes), but I got it at the second run(about 30minutes) but I don't know when it happened since I saw it when I came back to screen.
It looks like 4 console spawned during the run time(see the attached screen capture), at the start, "Console 1" only spawned 2 consoles, and I think "console 4" and "console 5" were spawned after "console 2" and "console 3" crashed. When I came back, "console 5" was running but "console 4" was hanged.
I have submitted the bug and will keep you updated.
Sorry for the late response, I discuss with dev team about this issue and the original issue you reported. They start working on it now.
They will first check if these are bugs or not and if they are, they are going to fix them.
My apology, I might miss responding to this issue, dev team had a suggestion:
They want to see if you can try MSS 2018-R2.3 and see if this release can solve the issue.
Again my apology for not updating the solution, can you make a try on this release?
This is my mistake, my post was not relevant to your issue.
For your issue, the latest update is, we started the investigation, it is at early stage and I will give you update when we found something.
Our Windows application that does several simultaneous real-time encodings also suffers from MFX_ERR_GPU_HANG, even with the latest driver version 188.8.131.5236. Any news regarding a fix?
This issue was reported and tracked very well. Based on the record, we had a discussion on it about June, we decided to delay it since the other urgent project and resume when our resources are available.
Is your GPU hang issue is the same as Alek? If it is different, you can submit a different request either on Forum or online support center.
It's hard to tell from the outside whether the issue is identical or not. Our app certainly is different. We do multiple real time encodes and get the same -21 error.
Thanks for the comment.
Understood your situation. It should take time to create a reproducer, this would always be preferred so if you happen to have it, please post. Otherwise, I will focus on fixing this report.
I will add your comment to the report.