After H264 encoded 429484 frames, GraphEdit prompts "The Graph could not change state"

After H264 encoded 429484 frames, GraphEdit prompts "The Graph could not change state"

1280x720 NV12 format video captured from HDMI capture card is send to H264 encoder. If we set encoding size not 1280x720 (such as 960x540), After Continue encoding 429484 frames, GraphEdit prompts "The Graph cound not chang state".

We use tracer and get 300MB log file. Attache is part of log file (Start log, middle-time log, around 429484 frame log). Please help.

BTW, we modify H264 encoder to support ICQ (RateControlMethod=UNKNOWN(9) ).



Downloadapplication/octet-stream analyzer_error.log14.88 KB
Downloadimage/png GraphEidt.png366.71 KB
14 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.

We found:

If no resize used in H264 encoder, the encoder can work for a long time.

If resize used, the encoder can only encoding about 429484 (429480~429484) frames then failed.

We try other ratecontrol (AVBR), same bug appeared.

This troubles us for one month.


In above picture, I compare MSDK log with/withou resize.

In the left, no resize used, the encoder can continue work forever (working for many days).

In the right, 1280x720 resize to 960x540(we also try other size), the encoder continue work only 429484 frames( for 30Hz framerate,only 3.97 hours) then failed.

We wonder if resize bug cause encoder failed?





I use msdk orignal H264 encoder, same bug apperaed at 429484 frames.

My CPU is i3 4330 (CPU G1880 has same bug), Win7 32bit.


I attach new analyzer file with per-frame logging. To reduce log file size, only top 10 seconds and around frame 429484 10 seconds recodered.

The graph is: Capture -> H264 Encoder -> H264 Decoder -> render

Wish intel's help and guiding.



Downloadapplication/octet-stream analyzer(my)_1.log5.98 MB


I compare the encoder process of frame 429484 with other frame (from analyzer(my)_1.log). If red color notes can provide some hints?

MFX_ERR_ABORTED:The specified asynchronous function aborted due to data dependency on a previous asynchronous function that did not complete.


We modify avshws.dll (Source filter) to let it output 320x240@167Hz (No HDMI capture hardware need).

To install the Avshws, run the following command at CMD:(Please change E:\ to the actual path where the folder is)
"E:\devcon.exe install E:\avshws.inf AVSHWS"
The Operating System is Win7 32bit.

Use graph as follow. Setting encoder size to 1280x720. After run graph about 45 minuts, frame 429484 reached. Then graph stopped and MFX_ERR_ABORTED appeared in analyzer file.

We try this graph at two machines and got same results. One machine is G1880 the other is I5 3570K, both WIN 7 32bit.

Waiting Intel's debug.




Download avshws fileDownloadapplication/zip

By using above graph, we do more tests under intel Core CPU. The results are:

G1880(haswell)  failed at frame 429484

I3 4330(haswell) failed at frame 429484

I5 3570K(IVY)   falied at frame 429484

I3 2310(Sandy)  OK

What can we do next ?

Wish intel engineers try and debug

The sample DirectShow filters are not intended to be used for 'production' applications and may contain incomplete implementations for some usage cases, however we will certainly looking this finding further.

Can you provide information on the specific graphics driver being used on the failing systems?  (Can you send the output of the "mediasdk_sys_analyzer" tool that is in the <install dir>\tools\mediasdk_sys_analyzer director of the "Media SDK 2014 for Clients"?)


On the newer platforms, the "VPP" resize operation is performed differently than on the older Intel(r) 2nd Generation Core processor.  While the drivers themselves have been tested extensively, it is still unclear if the issue you are seeing is (only) an issue with the DirectShow sample filter usage of VPP, or if it is something in the drivers themselves.  We are working to reproduce your findings.  Thank you for your patience.


Thanks Tony for your care.

The failling system driver is 2014/3/11 version

Attachment is analyzer log file. For file size reduced, I only recode the parts arround frame 429484.

I compare frame 429484 with other frame and found the differ (red color notes in floor #7).

BTW, avshws(souce filter) is designed to produce 320x240 color bar. After encoder & decode, render display varies with CPU. That is:

For sandy CPU, render display color bar(It's OK)

For ivy&haswell CPU, render display green screen(Should be color bar)


Downloadapplication/zip analyzer-hws.zip137.88 KB

Good news:

We update HD graphics driver to version By using above graph, it continues to work more than 2 hours (far exceed 429484 frames).

We will do more tests and report the results.


After one week test, I am sure that resize bug is fixed under new driver

Leave a Comment

Please sign in to add a comment. Not a member? Join today