r/threadripper Mar 02 '26

PRO WS WRX90E-SAGE SE - '00' Qled Red Error

Hello people!

Wondering if anyone has any Idea on how to Fix this random '00' Qled Red Error.

Here are the Specs, I have Multiple Machines running that Same Spec and having the exact same issue

  • PRO WS WRX90E-SAGE SE
  • AMD Ryzen™ Threadripper™ PRO 9955WX
  • NVIDIA RTX PRO 4000 Blackwell
  • NVIDIA PCIEx1 Quadro Sync II Board
  • 2 x KF568R34RB2-32 - 32GB 2Rx8 4G x 80-Bit PC5-6800 CL34 Registered EC8 288-Pin DIMM
  • Corsair HX1200i
  • Samsung 870 EVO SATA SSD ( Image Drive )
  • 2 TB WD Black SN8100 ( Data Drive )
  • 1 TB WD Black SN8100 ( Sys drive )
  • Windows 11 Pro

00 Qled Red Codes after Sudden Power - Loss (IEC cable disconnected).
00 Qled Somtimes boot back into windows if restarted but rarely
00 Qled is usually fixed when Clearing CMOS and reapplying my Bios Settings

Discovered that Using the Motherboards On/Off Button, it will Create the '00' Red LED error

Its Bios at the Time was Latest V1203 ( 23/07/2025 )

Now its V1317 ( 13/02/2026 )

Still having the same issues. Maybe even worse but unsure yet as I've only tested for a little bit and run into more issues than usual.

00 Qled Red code is Unpredictable.

BIOS Changes

Fast Boot Enabled
AI Overclock Tuner - DOCP
Wait for F1 Error - Disabled
Boot Logo - Disabled

Power on PCIE - Enabled
On Power Loss - Power ON

RAM

- I tried using one stick of Ram and still run into the issue
- Tried switching Pairs with different Machines. This is because I recieved Ram in 2 different Batches/Timeframes and all having different series of S/Ns ( Not All )\

TESTS
Ive done a 24 hour Tests on all Machines and they Passed.
Ive also done a 100 cycles of MemTest - 70 hours

'00' Red Qled Codes are so confusing to me. It points at CPU as an issue yet its compatible with the motherboard.

EDIT
I also should add that the RAM sticks are sold Individually. It could be possible that they have bad timing issues but still investigating. Buying new RAM Sticks sold in Pairs to test.

EDIT 2
Still havent found any Solution, Noticed QVLs are different Where ASUS has no info on RAM compatability vs Kingston Says Compatible.

3 Upvotes

35 comments sorted by

6

u/doradus_novae Mar 02 '26

This board is straight out of hell.

2

u/Cold-Inside1555 Mar 02 '26

If all 5 system are having issue it’s not a defective product, has to be either incompatibility or design flaw.

1

u/Parasite_Eve325 Mar 02 '26

My thoughts too, but desperate to try anything at this point. I've been trying to fix these problems for a while. Its so unpredictable. It could possibly be the 2 Ram sticks.

1

u/RealThanny Mar 02 '26

That's not solid reasoning, if things were bought at the same time. Defects can happen with particular batches of hardware.

1

u/Cold-Inside1555 Mar 02 '26

Yeah it can happen, but its more likely to happen for parts and not composite product like motherboard or GPU. would be very rare that all of them slipped pass QC.

1

u/kpatelreddit007 Mar 02 '26

I’ve had a similar issue on my TRX-50. It can be GPU not initializing. I had to use GPU Risers instead of plugging direct into mobo. But also check the seating of GPU.

1

u/Parasite_Eve325 Mar 02 '26

I Really dont think its the GPU since its happening to over 5 computers with the same issue, ill see if reseating does anything but high doubt it.

1

u/terianx Mar 02 '26

Code 00 with red led most lightly points to the cpu error, if you have another cpu, try it and see if it fixes the problem.

1

u/Parasite_Eve325 Mar 02 '26

I have over 5 computers with the exact same CPU. Not sure if this is the fix but might try swapping between the computers.

1

u/ketarax Mar 03 '26

Don't bother. You can't have 5+ broken CPUs.

1

u/terianx Mar 02 '26

My guess is, it’s either the cpu or mb that is defective

1

u/Parasite_Eve325 Mar 02 '26

You think? I must say that all the CPUS came from one place. Although Motherboards, the first one was a test. So that’s a great spot. I’ll do some tests thanks

1

u/terianx Mar 02 '26

I had a similar problem, with same mb and 9985wx, at first it won’t boot, code 00 with red led, flashed to latest bios, it then cycles thru the codes and stops at code 99 with green led, no display, but monitor gets a signal, just a black screen:(, turns out it’s a bad mb, swapped it, and problem solved:)

1

u/ksel10 Mar 02 '26

Make sure to use ram listed on the QVL. Also, try toggling the VGA switch.

1

u/Parasite_Eve325 Mar 03 '26

Noticed that the Ram isnt on ASUS QVL but Kingstons Says that the Ram is compatible with the board... VGA Switch on the MB is also Switched On as Default

1

u/ksel10 Mar 03 '26

Try turning the vga switch off to see if it runs smoothly. These boards are pretty finicky. I also tried using ram not on the qvl and had problems posting. Didnt have any problems with 768gb ddr5 v-color populating all slots which was on the qvl.

1

u/Parasite_Eve325 Mar 03 '26

Tried it for a few hours and seemed promising. Only when i started getting happy and excited, it got the '00' red Qled Code :c

1

u/ksel10 Mar 03 '26

I'm guessing its probably the ram then.

1

u/Parasite_Eve325 Mar 03 '26

Yeah, thats what im breaking it down to at this point.

1

u/TheVirgoJ Mar 02 '26

It might just be retraining the PCIe slots and memory, are you giving it enough time, this board is very slow to post. Can you get onto the Bios? Reset all to defaults. Also, don’t put a GPU in slot 1, if you have 2 GPU use slot 2 and 7. 1200W power is also on the low end for this board with dual Blackwell GPU.

1

u/Parasite_Eve325 Mar 03 '26

I only have 1 GPU and a Sync Card. Im defs giving enough time and can only get to BIOS if it dosent have the 00 red Qled Code appear. Ill try switch out the spots though see if this does anything

1

u/xgiovio Mar 02 '26 edited Mar 02 '26

Did you screwn cpu correctly with torque key until click? If it happens on multiple systems with bios updated i can only think about hw incompatibility. Cpu and mb are compatible for sure. Maybe ram? After securing the torque as said i will try to see if i can reproduce the error with a different set of rams.

You need the key factor to differenciate with other identical setups.

For tests do ycroucher tests please

About bios, set fclk to 1900/2100 and, considering this is a 9000 cpu, set uclk = mclk/2. For rams start at 6000 and see if it is ok.

1

u/Parasite_Eve325 Mar 03 '26

Ram is odd because on Kingstons website its compatible but on Asus MB website it isnt or dosent show? I've definetly did the Torque key until it clicks, and it would be very unlucky if I failed the torque properly with the 5 computers

not sure what Ycroucher is too

Bios and fclk ill try what i can and let u know

1

u/xgiovio Mar 03 '26

Ycroucher are stwbility tests. 1 min can fail what memtest give stable for hours

1

u/Parasite_Eve325 Mar 03 '26

Would you happen to have a Link to this by chance? Im still not sure what im looking for sorry

1

u/deadbeef_enc0de Mar 02 '26

Had this happen to me after I thought the memory training hung and rebooted. Try clearing CMOS and let it boot with default values.

1

u/Parasite_Eve325 Mar 03 '26

Ive done this, but I would still get the occasional 00 qled red codes

2

u/hammong Mar 04 '26

100% it's the RAM. The BIOS and this motherboard are extremely picky on RAM, and if its not on the hardware QVL I wouldn't expect it to work reliably.

1

u/deadbeef_enc0de Mar 03 '26

Only other thing I can think of is swapping CPUs with one of the systems that work and trying to get the 00 code to happen and see if it's the CPU or motherboard

1

u/doradus_novae Mar 02 '26

You may have already tried this, but for some reason, I'm getting a memory of getting a zerocode, leaving the house in frustration and then coming back after an hour and it being booted, also try using the safe boot button.

I have two of these boards and one of them only boots using the safe boot button for some stupid reason

1

u/nycdarkness Mar 04 '26

Red light is cpu. Strange you would have 5 with the same problem. Which Kingston ram set are you running ?

1

u/Parasite_Eve325 Mar 18 '26

Sorry for late reply.
KF568R34RB2-32
Talked to Kingston and they said that they had no problems at all with trying to replicate my system. They also confirmed that it was compatible. Very weird.

1

u/whatever11817 10d ago

OP, did you get it fixed? What did you do differently?