(Same post from here: https://forums.raspberrypi.com/viewtopic.php?t=325244)

Good Evening, I am working in a factory developing a simple cycle time display system for operators on our floor. After successfully prototyping with a Raspberry Pi 3B+, developing an operator display, getting it hooked up to sensors and sending timestamps/info to our database, we decided to purchase enough units to cover one production line. Here is our sources for our purchases: (Several Items are repeated due to stock issues)

RasPi 3B+: https://www.amazon.com/gp/product/B07BDR5PDW

MicroSD Cards: https://www.amazon.com/dp/B06XWN9Q99 https://www.amazon.com/SanDisk-Ultra-UHS-I-Memory-Adapter/dp/B00M55C0NS

Case: https://www.amazon.com/SmartiPi-Touch-Pro-Raspberry-Touchscreen/dp/B08VSFB6F5

Power Supply: https://www.amazon.com/dp/B00MARDJZ4

Official Display: https://www.amazon.com/Raspberry-Pi-7-Touchscreen-Display/dp/B0153R2A9I https://www.amazon.com/gp/product/B073S3LQ6Q

However, we are running into major problems with the Official Display that were not encountered during the prototyping phase, our system starts, displays the rainbow screen, the terminal, and the startup splash(per usual), after a short time on the startup splash, the screen's output breaks as described in the videos below, the color inverts/reverts and settles in an RGB state.

https://youtu.be/QshpTHzpXl0 https://youtu.be/LtnYX0Qw6M0

Tests plugging in the RasPi's HDMI cord to an HDMI capable monitor have no issue. The system starts normally provided that the RasPi-display optical strip is removed.

We are using this guide to setup the cases: https://smarticase.com/prosetup

Check the post on the forums for photos of the system's interior, I believe we have everything appropriately tightened and embedded.

I would like to note that this is fresh material ordered off of amazon. I have shown two videos of two different subdisplays acting like this, maintenance has tested this with five different subdisplays, all have been behaving like this. I'll pray that this is a hardware issue related to this batch or there is an oversight that I didn't account for, if any has any recommendations on what to do next, I'll give as much info as I can.