3DS Not Turning On

[TeraTrillions]

Please help, my 3DS is not turning on!
I have a 2DS XL with CFW installed, and since yesterday, multiple errors have happened including the following:

1. The system shows an error when I press the power button, saying something about being unable to mount the CTRNAND.

2. The system boots up, but freezes and/or crashes a few moments later.

3. The system shows the blue power
light and a red light near the camera (Pink when the SD is not inserted) and immediately powers off after 1 second . (Displayed by image below)

Please note that my system has quite a bit of wear and tear on it as I have used it extensively since I bought it back in 2017.

I’ve seen stuff about a loose speaker ribbon but I don’t think that’s the case.

 

[zeldaxlink64]

Do you have boot.firm on the root of the SD, and do you have GodMode9.firm in the luma/payloads folder? If so, I would like you to perform a CTRTransfer.
If not, put those files there first!

Also, can you send a photo of both screens for the second error you encountered?

 

[TeraTrillions]

Do you have boot.firm on the root of the SD, and do you have GodMode9.firm in the luma/payloads folder? If so, I would like you to perform a CTRTransfer.
If not, put those files there first!

Also, can you send a photo of both screens for the second error you encountered?

I have replaced the boot.firm in the sd card since the errors started happening, and GodMode9.firm is definitely in the payloads folder. I checked the SD Card with h2testw, and the test showed no errors. Unfortunately I can’t get a picture of the 2nd error, it hasn’t shown in a while. How would I go about performing a CTRTransfer?

 

[zeldaxlink64]

I have replaced the boot.firm in the sd card since the errors started happening, and GodMode9.firm is definitely in the payloads folder. I checked the SD Card with h2testw, and the test showed no errors. Unfortunately I can’t get a picture of the 2nd error, it hasn’t shown in a while. How would I go about performing a CTRTransfer?

This is not a good sign... after some thought, I've been thinking that this might be a serious hardware issue with the RAM instead of just a software issue.

Most likely, this cannot be easily fixed, and the only option would be to replace the motherboard.