My Build
PC has worked for months. Came to wake it up today and it wouldn't boot. Must have shut down. The power is running to the machine. The power light on the motherboard is working, but I get nothing. Almost as though it would act if the button on the case was busted. I can't do anything to get a sign of life out of it.
So far, I've tried checking that there's power in the outlet, that the motherboard is getting that power, and all checks out. Beyond that, I don't know what else I can do. There's no sign of life.
Awhile ago I used to have problems with the PC not starting up after a restart or shut down. It would get going, fans would start up, and the code readout would cycle a bunch of codes in a repeating cycle. I learned that I could get it to boot and not have those errors when I moved the memory sticks to different slots (i.e. from 2 and 4 over to 1 and 3 or vice versa). I always feared it would bite me in the ass for not actually figuring out what the issue was.
Gigabyte GA-Z97X-Gaming 7
MSI GTX 980 Ti 6g
2x 8g Corsair Vengeance 2400MHz DDR3
Intel Core i7 4790k 4.0GHz
EVGA Supernova 1050G
PC has worked for months. Came to wake it up today and it wouldn't boot. Must have shut down. The power is running to the machine. The power light on the motherboard is working, but I get nothing. Almost as though it would act if the button on the case was busted. I can't do anything to get a sign of life out of it.
So far, I've tried checking that there's power in the outlet, that the motherboard is getting that power, and all checks out. Beyond that, I don't know what else I can do. There's no sign of life.
Awhile ago I used to have problems with the PC not starting up after a restart or shut down. It would get going, fans would start up, and the code readout would cycle a bunch of codes in a repeating cycle. I learned that I could get it to boot and not have those errors when I moved the memory sticks to different slots (i.e. from 2 and 4 over to 1 and 3 or vice versa). I always feared it would bite me in the ass for not actually figuring out what the issue was.
Facebook
Twitter
Instagram