Davinci Resolve 12.5 crashes exporting 4K H.264

When exporting QuickTime H.264 at 3840 x 2160/25fps error: DaVinci Resolve has stopped working... appears, please help!

This is a freshly installed OS Windows 8.1 x64 and DaVinci Resolve 12.5.1 install

GeForce GT 750M x2 SLI Dissabled
Intel Core i7 4700MQ 2.40
RAM 16G

Fault bucket 120529877086, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: Resolve.exe
P2: 12.5.1.34
P3: 57aaff80
P4: mfh264enc.dll
P5: 6.3.9600.17415
P6: 5450576f
P7: c0000005
P8: 00000000000179ea
P9:
P10:

[Dwaine Maggart]

Did the issue happen immediately after you started the render?

What audio settings were used?

What h.264 settings were used?

Single Clip or Individual Source Clip render mode?

A log file would be helpful.

Did the issue happen immediately after you started the render?
Yes, 1-2 seconds after start
What audio settings were used?
default - Linear PCM
What h.264 settings were used?
default
Single Clip or Individual Source Clip render mode?
default - Single Clip
A log file would be helpful.
is there a path?

check the attached "Report.wer"

[Dwaine Maggart]

This post describes how to get log files:

viewtopic.php?f=21&t=48885

Davinci Resolve 12.5 crash log files requested

https://drive.google.com/folderview?id= ... sp=sharing

[Dwaine Maggart]

Thanks.

Please provide a project export .drp of the Testing Output project.

You can do this from the Resolve Project Manager page, by right clicking the project, and selecting Export.

New Resolve LOGS files provided and Davinci project also

[Dwaine Maggart]

The failure is indicated by this message in the logs:

FFMPEG Decoder cannot be initialized with property successfully

Your project works fine on Resolve 12.5.1 running on Windows 10.

Your project fails here in the same fashion running on Windows 8.1

I believe the failure is explained by this Microsoft article:

https://support.microsoft.com/en-us/kb/2829223

The failure is indicated by this message in the logs:

FFMPEG Decoder cannot be initialized with property successfully

Your project works fine on Resolve 12.5.1 running on Windows 10.

Your project fails here in the same fashion running on Windows 8.1

I believe the failure is explained by this Microsoft article:

https://support.microsoft.com/en-us/kb/2829223

thanks for this really exceptional statement!

it's very helpful and exemplary, when developer communicate stuff like this in a transparent way!

[Dwaine Maggart]

The development team verifies that you need Windows 10 to be able to write UHD H.264 files.

That means Windows 7 will not work for this as well.

amazingly fast answers and support... very happy, thank you so much! I will have to upgrade to windows 10 shortly! However, I can export 4K H.264 in premiere cc2015, then... why is Davinci restricted to windows support for H.264?

The development team verifies that you need Windows 10 to be able to write UHD H.264 files.

That means Windows 7 will not work for this as well.

Have the same error when try exporting 4K h.264 ("recording failed with error: failed to encode the video frame ")
So I don't understand why Premiere can export 4k using h.264 (windows 8.1) and Davinci not?

[Dwaine Maggart]

Perhaps Premiere is using the Apple QuickTime package, or similar, to generate the files.

Resolve 12.5.1 and higher no longer use the Apple QuickTime package, so is more finicky about OS level support for some things.

Perhaps Premiere is using the Apple QuickTime package, or similar, to generate the files.

Resolve 12.5.1 and higher no longer use the Apple QuickTime package, so is more finicky about OS level support for some things.

Ok, but with this setting Davinci export work:
QuickTime>MPEG4 Video>3840x2160 Ultra HD.
Isn't QuickTime?

[Dwaine Maggart]

Right, in UHD, MPEG4 works and H.264 doesn't work in Windows 8.1.

I suspect that means the 2 modes require different underlying OS support.

Win10 is the only option for UHD H.264 to work.

Right, in UHD, MPEG4 works and H.264 doesn't work in Windows 8.1.

I suspect that means the 2 modes require different underlying OS support.

Win10 is the only option for UHD H.264 to work.

I registered specifically to say thank you for your responses in this thread. I tried so many things and finally a search of an error string from the logs brought me here. Finally, mystery solved.