F5F Stay Refreshed Hardware Desktop Code 00 indicates a failure following server relocation.

Code 00 indicates a failure following server relocation.

Code 00 indicates a failure following server relocation.

S
Stampycat777
Member
66
02-17-2022, 01:46 PM
#1
Hello, We built a simulation rig using an ASUS WS WRX80E-SAGE SE WIFI motherboard, an AMD Threadripper Pro 5995X processor, and an RTX 4080 graphics card. The Windows Server ran smoothly for nearly two hours before we moved it. After shutdown for maintenance, the system restarted but encountered issues during startup: all POST codes appear, yet it powers down at error code 00 ("not in use") within about 30 seconds. We can't access the BIOS. Despite disassembling and reassembling multiple times, swapping out the power supply (Bequiet Dark Power Pro 13) and motherboard didn’t fix the problem. Now we’re trying to identify other possible causes and solutions. Anyone with similar experiences or troubleshooting tips would be appreciated. Thanks for your assistance!
S
Stampycat777
02-17-2022, 01:46 PM #1

Hello, We built a simulation rig using an ASUS WS WRX80E-SAGE SE WIFI motherboard, an AMD Threadripper Pro 5995X processor, and an RTX 4080 graphics card. The Windows Server ran smoothly for nearly two hours before we moved it. After shutdown for maintenance, the system restarted but encountered issues during startup: all POST codes appear, yet it powers down at error code 00 ("not in use") within about 30 seconds. We can't access the BIOS. Despite disassembling and reassembling multiple times, swapping out the power supply (Bequiet Dark Power Pro 13) and motherboard didn’t fix the problem. Now we’re trying to identify other possible causes and solutions. Anyone with similar experiences or troubleshooting tips would be appreciated. Thanks for your assistance!

E
Ender_Craft47
Posting Freak
866
02-17-2022, 02:31 PM
#2
Test one stick at a time in each RAM slot. If that fails, check the motherboard—removing the RAM usually fixes the problem, as the motherboard is the most common failure point besides XMP RAM slots. I’ve reviewed 40–50 boards, found many broken ones, and tried various fixes like water dips, resetting VRMs, cleaning thoroughly, but issues persist.
E
Ender_Craft47
02-17-2022, 02:31 PM #2

Test one stick at a time in each RAM slot. If that fails, check the motherboard—removing the RAM usually fixes the problem, as the motherboard is the most common failure point besides XMP RAM slots. I’ve reviewed 40–50 boards, found many broken ones, and tried various fixes like water dips, resetting VRMs, cleaning thoroughly, but issues persist.

T
TommyHU3_
Member
153
02-17-2022, 03:20 PM
#3
You likely attempted these steps but still need to try: Reset CMOS – use one RAM module. Inspect the cooler – take it out and reinstall. Take off the CPU and verify the socket. Reinsert the CPU and adjust the Torx screws gently. Wait 10 minutes after turning off. If nothing works as described, continue...
T
TommyHU3_
02-17-2022, 03:20 PM #3

You likely attempted these steps but still need to try: Reset CMOS – use one RAM module. Inspect the cooler – take it out and reinstall. Take off the CPU and verify the socket. Reinsert the CPU and adjust the Torx screws gently. Wait 10 minutes after turning off. If nothing works as described, continue...