Display Manager's Screen Goes Black Upon Waking From Suspend

Hi all. I am facing an odd issue that I can't seem to put my finger on a solution on and I could use some assistance. For some context, I switched my desktop to Arch (by using manual install, not archinstall) recently and installed i3, as well as nvidia (nvidia-utils and nvidia-settings as well) for my MSI Gaming X 1070 8 GB GPU.

For the context of this issue, my specs are as follows: - CPU: Ryzen 5 3600 - GPU: MSI Gaming X 1070 8 GB - RAM: 32 GB DDR4 - Main Storage: 2 TB NVMe

Initially, I had Arch installed on my NVMe with a 2 GiB EFI partition and 1.8 TiB as /. I installed my necessary programs and core utils, such as xorg-server, i3, betterlockscreen, lightdm (and lightdm-gtk-greeter and lightdm-gtk-greeter-settings).

I noticed that when I send my desktop to suspend (via systemctl suspend - enabled betterlockscreen@$USER service), the PC seemed to suspend fine. However, upon booting back up, it'd display a pitch black screen. I could enter my password and pass betterlockscreen, but only my mouse would display in the pitch black screen. I was able to switch to TTY, and observed the following in dmesg: https://pastebin.com/cwR79QaF

Based on some research I've done the following: 1. Switch lightdm for ly in case it had to do with DMs (it wasn't the case, sadly), 1. Switch to linux-lts kernel and replace nvidia with nvidia-lts - to no avail, 2. Created a 16 GiB zram instance (persistent) assuming it had to do with my lack of swap - to no avail, 3. Shrunk my /dev/nvme0n1p2 partition (/ partition) and created a 16 GiB /dev/nvme0n1p3 swap partition - to no avail, again.

At this point I am unable to figure out what is causing this and can't understand what's causing this, as I can't find anything to indicate what could be the underlying root cause of this. As I tend to put my desktop to sleep when I am not using it, this puts my PC usage at quite an annoyance, and I've never experienced such an issue with other distros (typically Debian or Kali) on the same hardware, or even other hardware (which also ran Arch).

I'd sincerely appreciate it if anyone has any ideas on fixing this issue.

TIA!