@sugarfree FIXED IT
Turns out uninstalling redream does not clear the config files. manually going to opt/retropie/configs/dreamcast and clearing everything then removing and reinstalling redream though retropie setup has seemingly fixed it. redream menu now opens in game.

I was able to convert my .srm save file from lr-mupen64plus-next to an .sra file with this online tool.

https://drehren.github.io/ramp64-convert-web/

I then copied the .sra file into /opt/retropie/configs/n64/mupen64plus/save/

Then I launched ocarina of time with mupen64plus-GLideN64 and played it nonstop for about 2 hours without any crashes or major issues. GLideN64 may have had a few more video glitches than lr-mupen64plus-next was having, but not a single crash for that entire period of time, and that was picking up the game where I left off playing with lr-mupen64plus-next.

So it seems that I don't have these crashes with standalone emulators, but do with libretro emulators.

@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.

It's working for me now as well, thank you.

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

Are you using the RetroPie Pi3 image from retropie.org.uk/download ?

@buzz Thanks for your response.

I might be that. I used that specific version of mame because I already had some roms from the appropiate romset.

@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.

raspberry 3b+ , retroarch 1.8.4 , retropie 4.5.1. Touch wait for the solution.

@mitu Glad to know I'm not the only one having the issue with Arcade's Greatest Hits - The Atari Collection 1. The fact that both of these games play properly on ePSXe, using the same BIOS (SCPH1001.bin) and ROM files, leads me to believe that it's an issue with lr-pcsx-rearmed. I suppose, worst case scenario, I could try The Atari Collection 1 on SNES and Hot Wheels Turbo Racing on N64 if myself or anyone else can't figure out the issue on PSX.

Related links: Hot Wheels Turbo Racing psx black screen
PS1 games that have bugs in retropie

H264 runs perfectly. Thanks!

@jonnykesh At first I updated the standalone mupen64plus package from source but it didn't solve the problem so I updated the lr-mupen64plus package too.

In reddit someone wrote that it should work from now on with an update from the binarys.
I tried the mupen64plus update from binarys and now it works :D

@darksavior said in Pi3B, MAME, lr-MameForAll or lr-Mame03 - Segmentation Faults:

Games will have bugs or not run correctly. You might not have noticed it, but I did. It depends on the game.

I agree with that between 0.36 and 0.78 it nearly doubled and between lr-mame2000 and lr-mame2003 I would think a shoe in for the latter and is considered the gold standard in certain aspects except maybe vector where AdvMAME outshines them all. I do agree to that FBA seems to run Neo-Geo, Capcom, Konami games better. They just seem to run smoother for certain.

I do also use multiple emulators too depending on the game. Mainly lr-mame2003 roughly 300 or so games with aforementioned options of shader and analog d-pad support. AdvMAME for vector, FBA for Neo-Geo, etc.

The original author of mame4all-pi (squid) had a majority of the games running at 100% without frame skip. It's been a hobby of mine since the late 90's. I do faithfully download the split updates every few months merge it and join the torrent. That includes the CHD's & extras, etc. I think it's close to 400GB now. It's where I spend most of my time when it comes to emulation.

That's what I was pointing out is the binaries (ROMs) are mostly 100% identical between the two version which are only 3 years apart. I don't believe the driver/board support emulation improved that much between those versions but they went crazy with additions.

You would have to be more specific on what exact games you find buggy in 0.37b5 that work differently in 0.78? My main point is that mame4all-pi (not lr-mame2000) is still very relevant if not a choice not just for the familiarity and support for being so widely ported but also the input configuration is still superior out of the box it works. Meaning there's certain configuration scenarios lr-mame2003 can't do...yet or at least not easily as I believe you will loose hotkey functionality if you "nul" all the Retroarch inputs to rely on lr-mame2003 inputs alone to correct the issue. :)

@FrustratedUser

Glad to hear it.

@martincrocenzi said in Segmentation Fault Screen:

@zoop did you reboot the raspberry? when exactly do you get that screen? Can you detail the text or message you receive? Any capture or pic? Which Raspberry do you have? Which sd card? Any other specs? Whta do you mean with too aggressive?

Thanks!

I used a kit I ordered from Amazon for my PI setup. The details may be found here, including the details on the SD card: https://www.amazon.com/gp/product/B01LWURJMI/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1

Pi Model or other hardware: PI 3 Model B
Power Supply used: 5V/2.5A Power supply charger for Raspberry 3B
RetroPie Version Used (3.6, 3.8.1, 4.01 etc.. - do not write latest): 4.1
Built From: Pre made SD Image on RetroPie website

The overclock settings I am using without issues are (credit YouTube vid where I found them):

https://www.google.com/url?sa=t&source=web&rct=j&url=%23&ved=0ahUKEwjkiPON2a3SAhWD1CYKHQKjD00QwqsBCDUwAg&usg=AFQjCNF1sHlk2z9QIx28jtvfnGP_UlkifA&sig2=JVDtgTiyUALlhDTby_3i1A

Stable settings for me:

gpu_mem=400
arm_freq=1400
over_voltage=6
sdram_freq=500
core_freq=500
gpu_freq=400

When I bumped the arm_freq up to 1450 I received the aforementioned error. Resolving the issue on my end was as simple as modifying my config.txt to scale back the arm_freq to 1400 again and powering the system off then back on again. To my great relief everything just worked once the setting had been changed back to a stable configuration.

I do not 100% remember how the screen looked with the error. It may have just been a single line reading segmentation fault. All I remember for sure is there was a 'segmentation fault error' on the screen and I figured it had to be my OC settings. I just had to hope I had not corrupted my image or something..

Apologies for the delayed response, I hope you find what you're looking for and are able to resolve the issue. Best luck!