@mozvillat Please add some info about your setup, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.

Get a verbose log from the error run and post it on pastebin.com.

@Rascas the issue is max_framebuffers=2 on retropie. It should be max_framebuffers=1 when using a single display. This resolved my issue.
Tried all different cables, monitor inputs, monitor outputs, rebuilding libcec. only solution was max_framebuffers=1.

Thread here shows it should be set to match your displays. https://www.raspberrypi.org/forums/viewtopic.php?t=245789

I'll accept maybe it's an oddity with my display, but since making that change i've been unable to reproduce it.

Think the corruption was perhaps bad luck... but I've seen a few reports of recent kernel/raspbian updates causing this.

@akamming I confirm the same problem and the same error. It seems to be related to some parameter in the config files (maybe retroarch or core options).

I've not tested on my odroid xu for some weeks. May be a recent change broke something. I'll check when I next get a chance.

May be a retroarch issue.. you could try rolling back the RetroPie-Setup script and building the previous version. I don't have time now however to give instructions to do this sorry.

@garradam not safely shutting down can potentially cause corruption of your sd card. If your pi freezes you should remotely access your pi through ssh and safely shutdown that way. Often times it's only emulation station that isnt responding. There are a number of easy to use ssh apps for smartphones that are very convenient to use.

Hi !

It is misteriously back to normal working.

Thanks for responding!

H264 runs perfectly. Thanks!

This is really strange, I haven't used samba for a long time. Maybe it has to do with some RP update? It completely ruined my sanity last night :P