It would start for 3 seconds then it would turn off and repeat again after another few seconds. Is the mobo dead or even the PSU? What's the best way to test out these parts?
Hardware Just put together a PC, but now it won't start up.
- Thread starter RemixDeluxe
- Start date
- Views 998
- Replies 13
I'm not a expert, but it might be your PSU. Is your fans running? If there are any, are there lights on the mobo that turn on? Do they turn off when your monitor's display turns off too?
Sounds like your mobo may be shorting out? Make sure the risers are keeping it from touching any part of the case.
Sorry if this is a dumb suggestion, but this happened to me the last time I built a computer.
This might be an even more stupid question: if you just built it, did you install an operating system?
What if the C isn't set correctly? I've seen inf. boot loops in so many ways, from so many mishaps.
Did you put new thermal past between the cpu and heatsink. If not then it will overheat and go into protection mode within a few seconds. Also it's common for people to accidentally plug the pci power cables into the motherboard instead. Did you put stand offs between the motherboard and the chassis? Do you have the cpu fan plugged into the connection on the motherboard that is marked for cpu fan? If not then the bios will think that the cpu fan isn't running and go into protection mode. It might help if you were to post some close up pics of everything
Best way.
Identical machine to swap individual parts into to test individually.
Best you likely have.
Start from minimum build (motherboard on a non conductive table/surface + one stick of ram + cpu) and build up from there.
If said motherboard has some diagnostics then they can help too -- beep codes are classic but some newer ones, especially enthusiast hardware, has LEDs and 7 segment displays and more besides.
I don't like to speculate at these points but all those others suggested I have seen. You also have the usual make sure everything is seated properly test. I assume you picked parts that should work together -- if the motherboard supports the CPU but only after an update it will not boot to receive the update to in turn support it.
Identical machine to swap individual parts into to test individually.
Best you likely have.
Start from minimum build (motherboard on a non conductive table/surface + one stick of ram + cpu) and build up from there.
If said motherboard has some diagnostics then they can help too -- beep codes are classic but some newer ones, especially enthusiast hardware, has LEDs and 7 segment displays and more besides.
I don't like to speculate at these points but all those others suggested I have seen. You also have the usual make sure everything is seated properly test. I assume you picked parts that should work together -- if the motherboard supports the CPU but only after an update it will not boot to receive the update to in turn support it.
Sorry for the long radio silence.
Everything is fine now, I used this split cable for the power rather than a normal one and the PC is running smoothly now. I also readjusted the RAM so that may have also been a part of the issue but I'm not certain. All in all I'm just relieved I didn't fry the mobo and all the parts are working as they should. Thank you guys for the help.
Everything is fine now, I used this split cable for the power rather than a normal one and the PC is running smoothly now. I also readjusted the RAM so that may have also been a part of the issue but I'm not certain. All in all I'm just relieved I didn't fry the mobo and all the parts are working as they should. Thank you guys for the help.
Last edited by RemixDeluxe,
I have one concerning question. Is it possible to manage which drive gets booted first from Windows or does it have to be managed from the BIOS.
The reason I ask is because my BIOS cannot see my SSD even though that is where my OS is installed. Any solutions to fix this?
The reason I ask is because my BIOS cannot see my SSD even though that is where my OS is installed. Any solutions to fix this?
Have you tried plugging the SSD into another SATA port? Perhaps you have 2 SATA controllers onboard and the BIOS only supports booting from one of them.
You can technically install the Windows bootloader to another drive, and point it to your SSD install. That way it doesn't matter whether the BIOS sees the drive or not.
Do it from the BIOS until you can download programs. There is a program for dual-booting, the name escapes me. I'll edit when I find it on google.
--------
Easy BCD. Google it.
Last edited by H1B1Esquire,
Similar threads
-
Xdqwerty
what are you looking at? -
BakerMan
I rather enjoy a life of taking it easy. I haven't reached that life yet though. -
Psionic Roshambo
-
-
-
@
SylverReZ:
@Xdqwerty, People who create revival services for the Wii end up in disaster, same goes for Pretendo lol.+1 -
-
-
-
-
@
SylverReZ:
It got shutdown because somebody "accidentally" leaked the database for the amount of people using the beta.
-
@
SylverReZ:
RiiShop is the laziest way of downloading Wii games. Did somebody not think of this through?
-
@
BakerMan:
although i ended up accidentally changing my nand with no way of going back bc i didn't know you needed a gamecube controller to restore it (i have a wii minus/1.1, which doesn't have gamecube controller support)
-
@
SylverReZ:
@BakerMan, I think you're talking about the recovery mode that the SaveMii used, and also was to restore softbricked systems.
-
@
SylverReZ:
If your NAND was hardbricked, then just buy another Wii. Or go with the dirty NAND flasher method.
-
@
BakerMan:
and if i find the sd card i have my NAND backed up on, i can not only restore the NAND if i solder the right part in, but i can also put my NAND on dolphin, then i can play dolphin online, like PMEX Remix or MKWii Riibalanced
-
-
-
-
@
BakerMan:
ngl i feel like if a bunch of my friends have wiis and know how to get wiimmfi and back up their NAND, then we could do a PMEX Remix tournament
-
-
-
-
-
-
-
-