The runcommand dialog prompt which you get is actually present since the game start, it's just obscured by the emulator that starts and overlays on-top of it. The dialog being present after the game ends means that the emulator hasn't actually exited/stopped - in order for EmulationStation to pick-up and start - and it's stuck somewhere.

This may be a sdcard issue - emulator tries flush some state to the disk on stopping the game or saving the options file and not being able to will block the emulator. Your log file is strangely formatted (did you copy/pasted from a SSH session or OCR-ed a photo ?), but it doesn't show the emulator actully stopping, which would show something like:

.... ^C[INFO] [Core]: Content ran for a total of: 00 hours, 00 minutes, 04 seconds. [INFO] [Core]: Unloading game.. [INFO] [PulseAudio]: Pausing. [INFO] [Core]: Unloading core symbols.. [INFO] [Core]: Saved core options file to "/opt/retropie/configs/all/retroarch-core-options.cfg". [INFO] Threaded video stats: Frames pushed: 244, Frames dropped: 0.

If you have SSH available, you can the emulator through strace and the post the strace log archived somewhere (it's going to be too large to post the contents as is), just to see where it's stuck. Stop EmulationStation and run:

strace -f -o strace.log /opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-fbneo/fbneo_libretro.so --config /opt/retropie/configs/arcade/retroarch.cfg "/home/pi/RetroPie/roms/arcade/frogger.zip"

then exit the game. When it gets stuck, then save the strace.log file and upload it somewhere.

EDIT: strace is not installed by default on RetroPie, but you can install it by running sudo apt -y install strace. I also advise to update RetroPie in order to get the latest version of RetroArch and OS packages available.

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

Post your /boot/config.txt and /boot/cmdline.txt.

Please provide the info requested in https://retropie.org.uk/forum/topic/3/read-this-first.

Would be useful to give a meaningful title to your post, instead of 'help' - this is the Help & Support forum after all.

@mitu Yea tbh I'm not sure what it uses, I just thought I would take a chance incase anyone knew.

@dankcushions said in Commands to quit frozen/bad roms? (not Ctrl + C or F4):

so the thing to note here is lr-mame is in the 'experimental' section of the retropie package manager. experiments fail :P

It wouldn't be an experiment if we knew what was going to happen :)

lr-mame2003-plus seems very reliable for me, with helpful features over lr-mame2003. Is there a list of remaining issues, or a process for that to go through before it becomes a regular optional or main package?

@Tango Another thing you can do to cleanly shut down your system if it's too stuck to get back to the command line is SSH into your pi and run the command sudo shutdownThere are a lot of apps and programs for SSHing in. One example is JuiceSSH for Android. There are times it can be too frozen to even allow an SSH tunnel, but other times it's the only way to get a clean shut down. Just know that sudo shutdown "schedules" a shutdown a few minutes out, so if you use this method wait a few minutes to see the shut down actually commence.

@mitu It works now. Thanks alot!

@pbufkin45 Use a keyboard or access the PI system over SSH.

We don't support 3rd pary/prebuilt images.

@berserkerbx23 said in Gamepad configuration screen at startup freezes.:

now do I need to update or do anything else to it?

Sure, you can update and get the latest versions of everything.

Yeah I noticed those. I just left them at the default settings. I will try to disable them.

@dankcushions said in Zero: Exit a game, system freezes, screen is dim, can't SSH in...:

the reason for adding over_voltage is to INCREASE stability; higher clocks demand more power. however it also raises temps...

for shader performance i would have thought only GPU and maybe memory performance overclocks are relevant.

I tried some new settings last night, and ran it for a good solid 20 minutes switching from game to game like I was doing before (where I could ALWAYS get it to freeze at some point) – and it seemed to be good. Think I dropped each "recommended overclock" number by 25 (475, 475, 475), AND changed the two voltages to 3. Think temp was still around 60º which is normal while you're using it I believe. I will test it even more tonight (including writing down the FPS numbers to see how they compare to the full 500 overclock - I think SNES was still down to like 54-57 instead of 60 FPS...which would be fine as long as it doesn't crash).

CRT-Pi Shader performance I gave up on for SNES and Genesis to be honest. It's just too much on the pi Zero even with the full overclock to get to that magic 60 FPS. I'm trying to keep CRT-Pi for NES (as it helps 8-bit look better to a much greater degree than 16-bit IMO), but will have to see if I get any of the weird pausing which plagued the non-overclocked Pi Zero with lr-quicknes + CRT-Pi.

should be fixed now for new installs.

Picture: http://imgur.com/YVTDMXC