@mitu i don’t think the pi3 is capable of doing 4k (as in, the driver won’t permit it). even with the mesa driver i’ve not had to set anything to get it to work on my 4k display - it ran 1080p by default @daiana_75 please fill out https://retropie.org.uk/forum/topic/3/read-this-first

@rmills55 Post your /boot/config.txt file to check for any overclock settings. and it can see i have about 60gb available. I was referring to the RAM allocated to the system, not the space on the card.

@mitu That's what I have been using. The only reason I wanted a libretro core was because my pi would often crash when launching other games/emulators after using Drastic. If there is a way to completely unload Drastic after closing it that would be great but thanks for your help 👍

Change your Emulation Station theme to Carbon, and/or cut way back on your collections. Had the same issue, took me a day to figure out

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.

@rbaker I checked it and nothing helped , I used brand new Kingston microSD card so it must not be reason . Anywan I will buy new one during black friday I just want to know now , can I use Pi 3 Model B heatsinks with Pi 3 Model B + if so I ahve some of them

@Nicky_S14 said in An error in the cmd is causing crashes, any ideas?: as it works on other cards! I'd say your card or filesystem on the card is corrupted. If flashing the RetroPie image on the card doesn't solve this problems, you should get another card.

@ddoherty958 said in Wifi calamity: @simonster The strange thing is I'm not entirely sure. You can show your Pi's model and revision with this command: cat /proc/device-tree/model (Just trying to fill the forum with useful information. 😌 )

Just got this error while scraping

@dnbarnes1983 Emulationstation is a general game launcher frontend - it's also used by Recalbox. You didn't specify in any of your posts you have RetroPie installed and which version.

I think github itself is having issues because I got the same error when syncing something else from github entirely.

@son_of_diablo It happens more than you realise, especially when you're starting to add ROMs and experimenting.

@sano You know what dude? I solved the problem myself :D . You know PPSSPP for Windows for e.g. It's in the same form as the one I mentioned. But now, I want to mess with es_systems.cfg, to run it through the Emulationstation menu. You see, the reason of can only boot one file error, was that in the es_systems.cfg file, there was line like this: <command>/opt/retropie/emulators/ppsspp/PPSSPPDL</command> And when I was trying to open .iso file through th ES menu, RetroPie was cofused, whether it should run PPSSPPDL, or .iso file. That was the reason of occuring can only boot one file error message. Coming back to es_systems.cfg, how to edit it in order to run PPSSPPDL, through psp section??? Hardware list, if necessary: Raspberry Pi 2 Model B 32GB Sandisk SD Card TP-LINK 150Mbps Wireless Nano USB Adapter (Model TL- WN725N) Esperanza Bluetooth USB Dongle (model wasn't specified on the box, I'm really sorry...) PPSSPPDL (non-libretrocore version, but I told you about it before)

@cesarabandeira I'm not sure how you got the dependency issue, but it must be due to some packages installed. Can't reproduce it on my rpi. Might just be easiest to back up settings and use a fresh image - or maybe aptitude could help (probably need to install it).

@buzz Cool. Thank you!!!

The way I did it, choosing the desktop with autologin has worked so far. But now I know how to retrace my steps. Invariably, I post these an entire house away from where I'm working on the pi, so I never have the various screens right there next to me and I panic. Visual/experience learner over here :-D. Thanks again for your help. I actually posted a follow-up on the reddit thread of mine as well.