Red CPU Light - X870 Riptied Wifi

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   New build PC worked great for a month then crashed when waking from hibernation. Rebooted to a Red CPU light, all fans and LEDs working.

Phantom Gaming X870 Riptide Wifi
Ryzen 7 9800X3d
2x G.SKILL Trident Z5 Neo RGB Series (F5-6000J3040G32GX2-TZ5NR)

Have tried:
Resetting CMOS
Reseating CPU
Reseating RAM
1 stick of RAM (tried both)

Thoughts/Suggestions?

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
71jaws000 Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: Yesterday Location: Nevada Status: Offline Points: 35	Post Options Post Reply Quote 71jaws000 Report Post Thanks(0) Quote Reply Topic: Red CPU Light - X870 Riptied Wifi Posted: Yesterday at 12:25am
	New build PC worked great for a month then crashed when waking from hibernation. Rebooted to a Red CPU light, all fans and LEDs working. Phantom Gaming X870 Riptide Wifi Ryzen 7 9800X3d 2x G.SKILL Trident Z5 Neo RGB Series (F5-6000J3040G32GX2-TZ5NR) Have tried: Resetting CMOS Reseating CPU Reseating RAM 1 stick of RAM (tried both) Thoughts/Suggestions?

Xaltar Members Profile Send Private Message Find Members Posts Add to Buddy List Moderator Group Joined: 16 May 2015 Location: Europe Status: Online Points: 25553	Post Options Post Reply Quote Xaltar Report Post Thanks(1) Quote Reply Posted: Yesterday at 2:09am
	If you have one on hand, try a different PSU, otherwise open a support ticket with ASRock: https://tw.asrock.com/events/tsd.asp You may want to contact AMD support too.


71jaws000 Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: Yesterday Location: Nevada Status: Offline Points: 35	Post Options Post Reply Quote 71jaws000 Report Post Thanks(0) Quote Reply Posted: 22 hours 52 minutes ago at 5:09am
	Thanks for the reply. Unfortunately, neither trying a different PSU nor known functioning RAM fixed it. Down to either the CPU or the MB, time to open a ticket. Thanks again.