Hello everybody 
I am experiencing a weird issue with my Framework 13 AMD 7040 running Arch Linux and GNOME:
Waking it up after I had locked it and the screen turned off, the screen turns back on showing GDM in a corrupted state. In that state I cannot interact with the login field and therefore login at all, the profile picture is missing, the settings menu on the top right is missing many of its buttons and the mouse cursor sometimes becomes just a white square.
If that happens I have to hard-reboot my Framwork twice. After the first reboot, unlocking my LUKS partition ends up with me being thrown into an emergency shell because the partition cannot be read.
From there I do a second reboot which now checks and repairs some corrupted sectors after I have unlocked my LUKS partition and proceeds to boot as expected.
The machine is running on the latest 3.05 BIOS and also uses the “GAME OPTIMIZED” settings from the BIOS to allocate more RAM to the GPU.
This happens on battery and during charging.
Unfortunately I have no picture of it yet. Once it happens again I will attach one to this thread.
Any ideas what could cause this?
I would look for an SSD firmware update for your SSD. Note: these aren’t often posted to LVFS even though fwupd knows how to upgrade them so you would need to check the manufacturer website.
Thanks for the hint @Mario_Limonciello!
There is a firmware update for my Crucial P1 SSD on their website: P1 SSD support | Crucial.com
I did download the image and created a bootable media, but unfortunately it does not boot.
After consulting the firmware update instructions (https://content.crucial.com/content/dam/crucial/ssd-products/ssd-family/documents/crucial-firmware-update-generic/crucial-firmware-update-all-en.pdf) I read that Crucials disk image is not compatible with UEFI boot modes.
Since there seems to be no option to enable some kind of legacy boot mode on the Framwork (or am I overseeing something?) it seems I will not be able to try this solution out in the near future. 
One sidenote though: While I was in the UEFI looking for the legacy boot option I found an option called “PCIe Dynamic Link Power Management”. It was enabled and I did disable it because I think I remember reading about SSD issues due to power management somewhere else.
Let’s see if that helps, but please if there are any other ideas do not hesitate to tell them! 
If you’re having a hard time booting their updater you should probably contact them for advice.
Maybe you can extract the payload from that manufacturer image and install it using fwupdtool install-blob?
Thanks for the hint with fwupdtool install-blob!
I did extract the firmware blob from their updater ISO as described here: Using fwupdmgr to update NVME firmware – nullr0ute's blog
After extracting I saw that the firmware in their updater is actually older than the one I have installed on my NVMe (P3CR013 on their updater vs. P3CR020 on my drive).
fwupdtool itself also reports no firmware updates.
EDIT: In the meantime the issue also sometimes only shows a black screen instead of the corrupted GDM lockscreen. I cannot reproduce when which of these two is happening and why.
I might have found the issue and a solution for it.
Researching around that problem led me to the topic of SSDs which are having issues with their power saving modes (APST - Autonomous Power State Transitions).
I ended up adding the kernel parameter nvme_core.default_ps_max_latency_us=0 as described in Solid state drive/NVMe - ArchWiki to completely disable APST.
So far the issues has been gone, but comes with the price tag of having a bit higher power consumption. Looks like there might be no other solution for my current setup.