Computer won't boot to anywhere

[Patrick_Lindber]

Hi! I'm building a new computer with these specs:

Asus Maximus VII Hero
Intel Core i7 4770K
MSI GeForce GTX 770 Twin Frozr Gaming OC
Kingston HyperX Fury Black (8GB - 2x4GB kit)
WD 5000AAKS
Hitachi-LG CH20N
Corsair RM850
NZXT Phantom Full Tower

When I turned the computer on the first time,
it didn't do anything. LEDs, fans and the cool
lights of the motherboard worked, but it didn't
go to BIOS. I waited for minutes and nothing
happened. The hard drive is "stealed" from
non-functioning Acer Aspire AX3400 like the
disc drive too. There's an Ubuntu installed on
the hard drive, but I will install Windows
8.1 Pro in it. Any help will be appreciated 🙂

[HiVizMan]

Do you have the 12 EPS CPU connectors fitted?

What is the two digit diagnostic code that is shown on the LED poster when you power on?

[Patrick_Lindber]

The code was 00. Then I found out -thanks to You- to connect the 12V CPU power connector 🙂
Now the computer started, then turned off. Then it started again and beeped. But now it shows Q-code b2 and it isn't going anywhere.

[Patrick_Lindber]

The code was 00. Then I found out -thanks to You- to connect the 12V CPU power connector 🙂
Now the computer started, then turned off. Then it started again and beeped. But now it shows Q-code b2 and it isn't going anywhere.

[MeanMachine]

Patrick Lindberg wrote:
The code was 00. Then I found out -thanks to You- to connect the 12V CPU power connector 🙂
Now the computer started, then turned off. Then it started again and beeped. But now it shows Q-code b2 and it isn't going anywhere.

Hi Patrick. The solution to your problem can be rectified in your Bios once you get in but first:
What OS are you using ?.
Have you tried booting from your installation disk?
Try holding F2 during boot.
Here is some helpful info to better understand UEFI v Legacy boot options.
A good tutorial and source of info go here:https://www.youtube.com/watch?v=amwujljr7pY
http://technet.microsoft.com/en-au/library/hh825112.aspx

"Legacy ROM" refers to the format of the OPROM on the storage controller. There are two firmware standards for PCs, the legacy BIOS standard and the new EFI/UEFI standard.

Since the specification for BIOS and EFI are different it is possible to mismatch a BIOS OPROM with an EFI firmware. EFI contains the ability to load and execute BIOS compatible devices, but BIOS does not contain the ability to load EFI devices.

EFI ROMs are necessary for some of the new firmware level security features as well as for proper EFI boot sequences. For example, installing Windows from an optical disk which is attached to a non-EFI compatible storage controller can cause problems if it is installed to a storage controller which has an EFI compatible ROM.

When the storage boot control option is set to "Legacy Mode" it will be able to boot from all bootable devices that are attached to the system, regardless of whether or not they actually have bootable volumes on them. The UEFI mode scans for only GPT with bootable volumes and will list in the boot priority only those that are found. Thus, in UEFI mode,it's unlikely that anyone will ever see the good old "boot device not found, please insert system disk and press enter"

Don't Stress, We will get you going.

[Patrick_Lindber]

Oh, now it works! I found out to suppose the "stealed" hard drive to be the problem, thanks to MeanMachine. Then I connected it to the AX3400 and did something formatting-like operations with Ubuntu's GParted (booting from the DVD) to it. Then I somehow got progress when I connected it to my build (and connected my screen this time to the graphics card so that it has those PCIe power connectors plugged in 😉 ). Anyway, it works now and I'm learned that I won't save a few coins with the cheapest component next time. Thank You, MeanMachine and HiVizMan, from Your professional and friendly help! 😮

[MeanMachine]

You are most welcome Patrick and glad to here you are up and running. :):)
Thank you for your feedback.

[HiVizMan]

Pleased you are sorted.