Issues with Elecrow 7" display and black screen in Configuration

[shark]

I have some experience with Raspberry pi, but this is my first project with Retropie. I want to build a small, portable game system using the Elecrow 7" display. This display is designed to allow the Pi to be mounted on the back, with "U-shaped" HDMI and USB adapters that allow the Pi to be connected on the back of the display without any cables protruding. You can supply power to both the Pi and the LCD using the USB-C input on the Pi. The kit also includes small speakers. According to the docs, the max resolution supported is 1024 x 600.

I have written the retropie-buster-4.8-rpi4_400.img to the SD card and added the settings to the /boot/config.txt file according to the instructions that came with the display. I have enabled SSH and WiFi and I have successfully used Putty to connect and login to the Pi.

The screen looks great until I select the "Configuration" option from the launcher to access options for Audio, Bluetooth, etc.. At that point the screen will quickly flash the image, make a short "pop" sound on the speaker, and then the screen goes black. After a few seconds it will "flash and pop" again. I have to escape out to get the display back. Has anyone experienced this issue with a Raspberry Pi 4 and the Elecrow 7" display?

Hardware
Raspberry Pi 4 Model B
Elecrow 7" LCD Display link text
CanaKit 5.1V 3.5A Power Supply
PS4 controller (currently wired)

/boot/config.txt settings

hdmi_force_edid_audio=1
max_usb_current=1
hdmi_force_hotplug=1
config_hdmi_boost=7
hdmi_group=2
hdmi_mode=87
hdmi_drive=2
display_rotate=0
hdmi_cvt 1024 600 60 6 0 0 0

The LCD docs also state to comment out the following line if running Pi 4 on Buster:

dtoverlay=vc4-kms-v3d

However I have found that Retropie will not load at all without that line.

[shark]

@shark

Wow, on a hunch I changed the following line in /boot/config.txt and it has corrected the issue.

overscan_scale=0

From what I read this is supposed to be the default setting, but it was set to 1 in my config file. Sometimes all it takes to figure out an issue is to write out a lengthy forum post LOL!