19,00,4C,55 boot loop after moving pc?

Mar 5, 2018
6
0
20
So here is my situation. My parents are divorced living in different cities 80 miles apart. Often times my dad is working when I see him so I decide to transport my computer back and forth. I did this for a year or so with no issues. I always transport it in its original packaging to minimalize damages. Up until now nothing has happened. Now whenever I transport my computer up or down, after plugging everything up, I get the boot codes 19,00,4C,55 in that order. This started Friday and then when I came back down today it started again. The way we fixed it was by shorting the pins for the CMOS and then removing the battery for 10 minutes. I really don’t want and shouldn’t have to do this every time I move my computer. I’ll list my specs below. Someone please help!

Specs:
Motherboard: MSI z170a gaming m5
CPU: Intel i7 6700k
GPU: GeForce GTX 1060
Memory: GeIL EvoPotenza 3x8(1 stick is faulty so I removed it)
Cooling: Kraken x62
PSU: Corsair CX750M

Update: shorting pins and removing CMOS battery has had no effect. Battery is not dead. Puts out 3 volts.
 
Solution
I have found the solution; booting with one ram stick, then enabling an XMP profile. After that, shutting down and putting in the other sticks boots up properly
MERGED QUESTION
Question from betaspydog : "19,00,0D,4C,55 boot loop after moving pc?"





First of all, did you make sure all the connections for power and data are connected properly? If that doesn't solve it make sure everything is tight, check the GPU CPU and check your system to make sure there arent any cuts in any wires.
 


Its possible there is a wire being poked or broken somewhere, try pulling all of the parts out of your case and reassembling it all on a non conductive surface and booting it up. It may take awhile but ti should narrow down to a short in a wire or not.
 
I have found the solution; booting with one ram stick, then enabling an XMP profile. After that, shutting down and putting in the other sticks boots up properly
 
Solution


Well, what an interesting fix. Glad you got it working.