Hello,
As Ted mentioned, it is possible that the display controller inside the LCD itself has been affected and may need resetting.
For EVE itself, you may see an error condition indicated if the REG_CMD_READ and REG_CMD_WRITE never become equal (e.g. if the device is waiting on more data to complete a command and those bytes went missing due to noise on the SPI lines). Or if REG_CMD_READ gives an error condition (0xFFF) where bad command values were encountered (e.g. if noise corrupts the address or some data in a burst write causing a non-4 byte aligned command). Or you may also see a swap fail to complete by reading the swap register.
Therefore, it is worth ensuring you check the read and write pointers with a software timeout in case they don't become equal and a way to jump out the loop if the error condition is flagged.
You can also read back or CRC data in the RAM as well if you suspect corruption.
However, as your application is still running well in this case, it is likely that EVE is running correctly and outputting the screen on its RGB lines and that the panel itself may be affected. As Ted mentioned, additional grounding and protection against the data being corrupted may be needed to prevent it happening,
Best Regards, BRT Community