I see! I'll play around with it, then.

@mitu Ah thank you! Sorry about all the confusion The answer was simple, and found in your documents. https://retropie.org.uk/docs/PC-Engine/ *PC Engine CD It is important that the image file (usually .bin) and the CUE file (.cue) match. CUE files are just text files containing a description of the CD. If you have files named like: Akumajou Dracula X.bin Akumajou Dracula X.cue then ensure the first line of the CUE file contains: FILE "Akumajou Dracula X.bin" BINARY Any of the following are wrong and will not work: extension has incorrect case FILE "Akumajou Dracula X.BIN" BINARY file name has incorrect case FILE "AKUMAJOU DRACULA X.bin" BINARY does not match the actual file name FILE "Akumajou_Dracula_X_-Chi_no_Rinne(NTSC-J)_[KMCD3005].bin" BINARY*

@Guto-Du it's a possibility it's defective. Try over volting the pi (without over clocking) to see if it's more stable. If it is then your pi isn't stable at factory settings and should be sent back for replacement. I have seen multiple reports of pi zero's not stable at factory clock speeds. I think the quality control on the pi zero might be slightly less than other models. Probably because it's a $5 computer.

@helmar I don't know. First of all, I've never used mame4all. I use advmame and lr-mame2010, using the roms/arcade/ directory to select any of the arcade emulators to use with runcommand. There probably is a configuration to edit for mame4all, but I don't know anything about the ESC menu or why it would freeze. If the navigation key binds get misappropriated, then a solution would probably be finding then editing or deleting the bindings manually, using the terminal. There may be other ways to reset default binds dependent on the emulator and configs.

@Jiryn It could be that those cards are not compatible with the pi3, or they could be bad. Stick them back in your pc and run a check disk on them. Here is a list of compatible sd cards https://elinux.org/RPi_SD_cards Your cards do not show up there but a 256 Samsung EVO PLUS is listed as compatible. If you want more space you will likely need to consider using a usb mounted hdd or thumb drive. Here is another relevant discussion https://retropie.org.uk/forum/topic/783/largest-size-micro-sd-card

@quicksilver Not really, I’ve already rewired from the power input to the switch board, and modified the base a bit.

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

@Dustin_3487 said in Game freezing issue.: All I see is raspberry pi being sold at multiple websites, a lot of them with games pre installed so I figured they were allowed to do it. That doesn't mean it's legal. You should just ask for a refund.

Turns out I am wrong. Issue still persists. I tried using a separate micro SD card with the same v4.4 retropie build and got the same results. I tried disabling WiFi and bluetooth. This dropped the temps from 75+ C down to an acceptable 50-60C. Regardless the unhandled exception, freezing, and segmentation faults still continued. I surmise the pi zero w I bought new is defective. @Chameleon said in Retropie Freezing / Errors: I know this is an old thread but I want to keep related information in the same location. I encountered the above unhandled alignment bus error. I then found this post: "Bus error on Raspberry Pi 2 armv7 command line app #22384" https://github.com/dart-lang/sdk/issues/22384 I then went to rasp-config via emulation station UI and changed the localisation setting to my locale. Example: AMERICA > pick a city So far I do not see this alignment exception pop up. It would pop up fairly fast prior simple idling on the emulation station menu. Hope that helps.

@park757 try the official PSU as recommended. One without an in-line switch.

@dankcushions Here's my pastebin: https://pastebin.com/NR8ixXeM If anybody sees anything interesting in there please let me know. I can't figure anything out in this file sadly. I don't know if it's of any interest but I plugged in my USB pendrive, ran RetroPie, hit F4 to exit EmuStation, ran the command dmesg > /tmp/dmesg.txt, ran emulationstation, played a PSX game which froze pretty much instantly, exited the game, took the file via WinSCP and there it is.

@sebretro said in Periodic stuttering/freezing with RetroPi4.4 on a Raspberry 3B+ in every game (1-2seconds): Does anyone have know about this problem? Thank you for your help. Looks like an insufficient power problem - the RPI underclocks itself not having enough power. Take the PI out of the case and do some testing to see if you get the same problems. The NesPI cases are notorious for this kind of problems.

Well something happened that might point to the cause of the problem. I have been using it for the past 3 hours no issues. I decided to plug some earphones in so obviously, the board moved a bit. Well as soon as the board moved, it started to disconnect the controllers and a few seconds after, it froze! So now I think it is in fact the power cord from the PSU that's causing all these issues! I'll replace it and see if it goes away...

@mitu it came back :/

@mitu na all roms are running on the sd card, 32GB sandisk. I have a few of them that I cycle through during updates etc. All of them have shown the same behavior. I haven't changed default config.txt. I'm using an LCD monitor with hdmi, not sure if that was the screen question :) Also the map message only happens with Galaga so far, Berzerk does not show that it just completely freezes, screen does not go black like Galaga does.

@mitu It's possible but I think it was my installation of lr-pcsx-rearmed because I had another psx game crash on me which now works fine since updating it.

I have similar problem. I thought its my adapter to the monitor. I use a dongle for keyboard too. What was the interval when you got this screen freeze? I get it maybe once in a hour. Maybe its a different story on my side.

@thekraftyman if you log out of Ubuntu and then log back in with "wayland mode" that will fix the gl driver issue