ASRock creator wrx80 shows error code "2d" after exchanging RAM and coolers

  • Hi there and welcome to PC Help Forum (PCHF), a more effective way to get the Tech Support you need!
    We have Experts in all areas of Tech, including Malware Removal, Crash Fixing and BSOD's , Microsoft Windows, Computer DIY and PC Hardware, Networking, Gaming, Tablets and iPads, General and Specific Software Support and so much more.

    Why not Click Here To Sign Up and start enjoying great FREE Tech Support.

    This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
Welcome to our Community
Wanting to join the rest of our members? Feel free to sign up today.
Sign up
Status
Not open for further replies.

lekon44

PCHF Member
Aug 14, 2024
6
0
26
I'm part of a research group that recently assembled a novel workstation to run finite element simulations.

Specs:
AMD Threadripper Pro 5955 WX
x4 128GB RAM
Geforce GT 730
Noctua NH-D9 TR5 cooler

We assembled the PC, and noted that the workstation was running the finite element simulations slower than expected.
It turned out that one of our group members had installed the 4 RAM modules in the wrong slots (C1, D1, E1, F1) as opposed to (A1, B1, G1, H1), cf. ASRock manual.


I then did the following:
- Turned off power and unplugged PC
- Grounded myself
- Unscrewed the Noctua cooler to get better access to the RAM modules

- Changed placement of the RAM modules (avoided touching the golden pins, and didn't apply excessive force)

- Put the cooler back into place, avoiding excessive torque and following ASRock manual instructions.



Now, upon restarting, the motherboard shows error code "2d". The manual says for error codes 00-19 “Please check if the CPU is installed correctly and then clear the CMOS"


Things I have tried to debug are:
- Tightening the screws on the cooler
- Flush CMOS

Next, I would try to reseat the CPU. Please advise if you have better ideas.

Thanks!
 
I'm a student but yes if this works then the research group will of course benefit from it.
 
For clarity did you build this pc ? If so did you install the mobo chipset drivers ?
 
A group member ordered the parts and built the PC. I only exchanged the RAM modules. I assume that chipset drivers were installed as the PC was posting before I exchanged the RAM, but can double-check.
 
- Put the cooler back into place, avoiding excessive torque and following ASRock manual instructions.

You don`t mention it so have to ask, before reseating the CPU cooler did you properly clean off the old thermal compound with an appropriate cleaning agent ( Industrial strength alcohol or similar) and a lint free cloth or coffee filter papers and then correctly apply a fresh amount of good quality TIM such as Arctic Silver 5, application etc guide here

Things I have tried to debug are:
- Tightening the screws on the cooler

Too much or uneven pressure atop of a CPU can cause all sorts of problems so if you do need to redo the TIM take extra care with how much you tighten the four fitting points.

Try one stick of RAM at a time in slot C1 and make sure that you have a keyboard hooked up when testing else the power on self test will fail.
 
You don`t mention it so have to ask, before reseating the CPU cooler did you properly clean off the old thermal compound with an appropriate cleaning agent ( Industrial strength alcohol or similar) and a lint free cloth or coffee filter papers and then correctly apply a fresh amount of good quality TIM such as Arctic Silver 5, application etc guide here



Too much or uneven pressure atop of a CPU can cause all sorts of problems so if you do need to redo the TIM take extra care with how much you tighten the four fitting points.

Try one stick of RAM at a time in slot C1 and make sure that you have a keyboard hooked up when testing else the power on self test will fail.

I cleaned the old thermal compound using Isopropanol and cleanroom wipes (which are ultra-clean). I applied a small drop of thermal paste in the centre according to e.g. instructions on YT.

Re. screws, I don't have a torque wrench, but made sure that I turned all four screws an identical number of turns.

Re. RAM, I cleaned the contact points of 1 RAM (also with Isopropanol), inserted in C1, and cleared CMOS.

The posted error is still the same, unfortunately.
 
With the exception of how the thermal compound was applied I see no reason why you would be having issues, and if it were related to a bad compound application it would be flagged as an overheating problem and not the suggested hardware/CPU issue, the latter of which includes the CPU socket and possibly even the power supply.

For anyone else that may read this thread, applying thermal compound should be applied according to any information from the compound provider, the CPU manufacturer or a combination of both, never YT.
 
You have pretty much covered everything I`m afraid 🙁

Long shot but about all that you have left;

Disconnect the PC and all associated hardware from the wall socket.

Press and hold in the case power button for twenty or so seconds to get rid of any residual charge in the system.

Ground yourself then remove the CMOS battery from the MB.

Other than the CPU in the socket, HS and cooling fan + its connection to the header on the MB ( CPU Fan 1 ) remove all other hardware, RAM, GPU, drives, any add on cards etc, leave like that overnight.

Next, for good measure press and again hold in the case power button, put a different stick of RAM in slot C1, put the add on GPU into PCI-E slot 2, make sure that all power connectors from the PSU** to the CPU and the MB itself are securely connected to the PSU and MB, put the CMOS battery back in, hook up the keyboard, screen to the GPU and the PSU cord to the wall socket.

Power up with fingers crossed.

** If no luck, post the brand and model name or number of the PSU for us.
 
Not heard back from you lekon44, do you still require assistance or is the issue now resolved, an update would be appreciated.
 
Thanks for the suggestions. As I didn't know what to do, I've handed the PC over to a repair shop. While I don't know if they can do anything beyond what I've already tried, it's still worth a try.

I will keep you updated about the error source.
 
To avoid us having to ask for an update every couple of days we will close this thread until the OP has the time available to work towards resolving the issue, PM a member of staff when you are ready and the thread can be reopened.
 
Status
Not open for further replies.