Directly on the PlayDate hardware (Rev B according to the rev checker shared below) I'm getting a lot of crashes in general, but they seem a bit sporadic. One very reliable source of crashes is simply opening the settings menu. If I hard power off the playdate and leave it powered off for a bit when I power it back on I can usually get into the menu for a bit, but once the crashes start they generally are pretty much 100%.
Given that the system crashes when I open the settings menu I can't really submit a crash report (maybe I can connect over usb and trigger one or catch some logs that way?) so I sadly don't really know how to get any more info.
If I had to guess it sort of seems like an initial crash (like the one that I seem to be able to reliably trigger by hitting all 106 notes in the song "Biolum Sample-Q5S" in Otto's Galactic Groove in story mode on hard, unless that's just another symptom) leaves something in a weird state that isn't cleared out by the crash even though a full shutdown + startup restores the normal state?
If I can work out a reliable full repro I'll update this or add a reply with the details, but sadly 100%ing a specific song in a specific game is all I have so far 
The initial crashes that set off this whole cycle do seem to mostly happen when I'm playing Otto's Galactic Groove, but I'm not sure if that's because it's causing the crashes or just because I've mostly been playing it (because it's my favorite game of S2 so far!).
Awesome thanks! I'll sideload that on and check it within the next day or two 
Updated the OP, but that reports me as being Rev B. I've also tried several other things:
- Booting into recovery mode. This appears to have unpacked and installed something, but now I crash 100% of the time I open the settings or catalog menus
- Using the simulator to boot to the Recovery Disk which seems to contain a single file called
VERSION.TXT that says 57176cb0-2.6.2-release.177516-buildbot. I assume this is the "stable version" that recovery mode above tried to install? (Possibly unsuccessfully?)
- Show Device Info in the simulator doesn't show me running out of memory or anything when I trigger a crash via settings or catalog, just a spike in cpu (which I would expect).
(first spike there is crash via catalog, second is crash via settings)
- Boot to Data Disk via the simulator. This gives me an error from 2023 in the
errorlog.txt (so probably not relevant), the crashlog is maybe interesting though so I'll include that here in full:
--- crash at 2042/08/26 03:12:40---
build:1fd086bf5715-2.0.3-release.158184-buildbot
r0:30000354 r1:200028e4 r2:0000009c r3: 300002ec
r12:a5a5a5a5 lr:240402cf pc:240402ce psr: 61000000
cfsr:1fe774e9 hfsr:8054405e mmfar:af5ffdff bfar: 04e80096
rcccsr:00000000
heap allocated: 272803883
Lua totalbytes=1404157914 GCdebt=16777992 GCestimate=-29652113 stacksize=1436556900
--- watchdog reset at 2025/05/31 13:55:40---
build:5cd9814a-2.4.2-release.166897-buildbot
r0:200098d4 r1:901a356c r2:00000000 r3: 901a3584
r12:00666666 lr:24099847 pc:24095ada psr: 81070200
rcccsr:00000000
heap allocated: 272771113
Lua totalbytes=1404124891 GCdebt=16777992 GCestimate=-29652113 stacksize=1436589796
--- watchdog reset at 2025/05/31 13:58:40---
build:1ed19c6c-2.7.3-release.185782-buildbot
r0:3000fa2c r1:0000000f r2:00000042 r3: 30000350
r12:a5a5a5a5 lr:24030c8b pc:2403f0ba psr: 61000000
rcccsr:00000000
heap allocated: 272771113
Lua totalbytes=1404124891 GCdebt=16777992 GCestimate=-29652113 stacksize=1436589796
--- watchdog reset at 2025/06/07 13:31:03---
build:83b01743-2.7.4-release.186568-buildbot
r0:00000000 r1:000003e8 r2:00008001 r3: 3000eef0
r12:00004000 lr:2402712f pc:2402431e psr: 01000000
rcccsr:00000000
heap allocated: 272771113
Lua totalbytes=1404124891 GCdebt=16777992 GCestimate=-29652113 stacksize=1436589796
--- forced reset at 2025/06/18 02:36:14---
build:57176cb0-2.6.2-release.177516-buildbot
r0:00000003 r1:ffffffff r2:e000ed00 r3: 00013f60
r12:00000000 lr:24009c35 pc:2400b414 psr: 2100000f
rcccsr:00000000
heap allocated: 272771113
Lua totalbytes=1404124891 GCdebt=16777992 GCestimate=-29652113 stacksize=1436589796
It seems odd that that first one is in the (distant) future, but otherwise these seem to have started around May 31.
I'm not really sure why it doesn't seem to log anything for the crashes when I open settings or the catalog though.
I think my next step here is to do a factory reset on the PD. I backed up my games and save data so I'm going to give that a shot and report back 
Hmmm... It seems like the only way to do a factory reset is to trigger it from the settings menu, which it turns out is a little problematic when the settings menu crashes (or maybe it's not technically a crash, since it doesn't go in the crash log?) and drops you back to the home screen 
