After close to half a year the issue has not been resolved.

Timeline:
1) Jan 10 -> Started the forum under title "Always 100% and Crash Red"
2) Jan 13 -> Updated to <Deco X50-5G_V1_1.2.0 with IoT and CPU Optimization> the 100% CPU usage gone down but intermittent red light of death still occur
3) Mar 01 -> started this forum "Deco x50-5G Intermittent Red light of death
4) Mar 03 -> forum replied with step and taken offline as email [PIC: Vito]
5) Mar 06 -> Red light happened and furnish log
6) Mar 07 -> TPlink replied with beta software 1.1.7 debug firmware and qwinlog
7) Mar 10 -> Replied TPlink with Qwinlog when there is red light of death
8) Mar 12 -> Replied from TPlink will forward to R&D team for further investigation
9) Mar 26 -> Follow up and ask for a replacement
10) Mar 26 -> TPlink replied need more time as their R&D team lack of staff
11) Mar 30 -> Request again for 1 for 1 replacement
12) Mar 30 -> Attach all the receipt for purchase, serial number and request for replacement
13) Apr 02 -> TPlink replied with expectation to turn my PC into a debugging logger which 5 minutes the log sized 1GB told them it is not possible
14) Apr 03 -> TPlink replied Recommend to use wetransfer to transfer large log and said if confirm hardware or software issue will RMA, to capture log start the logging (include qwin) for few minutes unplug sim and replug sim and furnish the log
15) Apr 03 -> Red light occur and furnish modem and qwinlog via we transfer
16) Apr 06-> Resent due to Apr 04 is a china public holiday
16) May 06 -> Request for follow up
17) May 07 -> TPlink replied review all the log no discovery citing incomplete log - have contacted local team in Malaysia to setup and has no discovery request to flash "ver1-2-1-P1[20250415-rel40182]" and observe [this point already getting out of hand as am already following TPlink instruction on harvesting the log]
18) May 19 -> Redlight happened but could not harvest qwinlog, replied with modem log
19) May 20 -> Redlight happened again and sent modem log and request for identification of difference (comparing before and after logging with text comparison software)
20) May 23 -> Redlight happened and send log again
21) May 27 -> Morning happened once, but was rushing to work therefore did not take logging and evening as arrived home already red light of death, harvest logging and sent to TPlink

  @David-TP Do provide the step on how could I have RMA and also a replacement (not send my modem in and wait for a repair but a 1 for 1 replacement).

Looking forward.

Thank you.

  @Krane take it to nearby tp link service centre sir.