Hi, I have an issue that's a little frustrating and something I haven't dealt with before. My computer, which has been working great since 2016, failed to boot one day. I reseated all the ram, no luck, and then I reseated the M2 drive and it booted. It did fine for a while going to sleep and waking up, then we ended up shutting it off again and the problem came back. I reseated the drive it booted, power failure causing the computer to go off and problem came back. This time though, reseating isn't working. I even tried putting in a new M2 drive and it failed.
When it fails it goes through the start up lights on the vga, ram, cpu, and hangs at boot device. It'll typically flash up a 99, A2, some random numbers, back to a 99, and then hang on a 55 before turning off.
The components in use right now are a Z170 Deluxe Motherboard and a Samsung M2 Drive. I also Have a normal drive for photo storage.
Asus says 55 means memory, but it jumps through the Ram start up no problem. The red LED is clearly on the boot device when it hangs up. Is there a reason reseating the M2 drive would somehow cure a Ram issue since that's the only thing that made it work again?
I've also read something about someone having an issue with the computer not putting the M2 into the boot priority. I've seen how it fails when it has nothing there and it fails much faster than when the drive is in, so I doubt this is the issue. Just wanted to ask in case it could be related.
Also, I don't think this is the CPU getting hot as others had an issue with. Reseating the M2 drive shouldn't have fixed a heat issue.
When it fails it goes through the start up lights on the vga, ram, cpu, and hangs at boot device. It'll typically flash up a 99, A2, some random numbers, back to a 99, and then hang on a 55 before turning off.
The components in use right now are a Z170 Deluxe Motherboard and a Samsung M2 Drive. I also Have a normal drive for photo storage.
Asus says 55 means memory, but it jumps through the Ram start up no problem. The red LED is clearly on the boot device when it hangs up. Is there a reason reseating the M2 drive would somehow cure a Ram issue since that's the only thing that made it work again?
I've also read something about someone having an issue with the computer not putting the M2 into the boot priority. I've seen how it fails when it has nothing there and it fails much faster than when the drive is in, so I doubt this is the issue. Just wanted to ask in case it could be related.
Also, I don't think this is the CPU getting hot as others had an issue with. Reseating the M2 drive shouldn't have fixed a heat issue.