Jump to content

Hello, I am trying to finish my build but keep running into some issues with the system stuck on ACPI Initialization (code 78). 
 

Spec Details - 

Motherboard - Asus Pro WS WRX80E

CPU - AMD Threadripper Pro 5955WX

GPU - A2000, RTX 2070, RTX 3070

RAM - 1. 32GB kit - Sk Hynix 16 GB 2Rx8 PC4-3200AA -RE2-12

2. 128GB kit - Crucial 16 GB DDR4-3200 UDIMM 1.2 V CL 22

BIOS - Version 1201 2023/06/07

PSU - Asus ROG Thor 1200 Watts

OS - no OS (haven’t decided)

 

Details on the issue -

 

Then CPU was harnessed from a Lenovo P620 in working condition with the Sk Hynix kit.

 

The motherboard in the current system has been replaced since the initial purchase had an error code ‘C0’ which has no reference in the manual nor Asus support had a clue. Got a replacement and now run into POST code ‘78’ (ACPI Initialization) with the DRAM amber/yellow led ‘ON’. 

 

Troubleshooting steps thus far -

 

1. Reseated the RAM

2. Reseated the CPU

3. Re wired the cables

4. Tried different RAM configurations in different slots (yes the same pairs of sticks)

5. Re flashed the BIOS with no errors (no way to tell as the instructions for flashback mention of the BLUE led on the IO blinks and then goes out indicating success)

6. Reset BIOS (CMOS clear)

7. Tried all the GPU’s I had (not in pairs obviously)

8. Going to swap the CPU and Sk Hynix RAM back to the Lenovo P620 to check if I haven’t damaged anything in the swap process

 

Anybody has any idea on how to get this resolved?

Link to comment
https://linustechtips.com/topic/1552020-post-code-78-with-dram-amberyellow-light/
Share on other sites

Link to post
Share on other sites

Rma the board again

 

Wouldnt be surprised if its another dud cause i dont think 78 is a code youd encounter from an overclocking fail or the board refusing to recover

 

Had an msi z77 that i bought as broken and kept getting stuck at code 63, tried deep cleaning but to no avail, seems to be chipset related so i suspect thats a dead board

 

Anything that isnt a code that youd get stuck on from a failed overclock (4f, 55, etc.) And consistently gets stuck there even without an overclock is likely just a defective mobo

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×