Partitioned C Drive, now PC won't boot into anything

[KiwiFalcon]

Basically, I partitioned my C Drive (stupid I know), and the computer acted really weird, programs wouldn't work, the desktop would randomly reset, I couldn't right click. So I needed to reinstall Windows. My computer would boot up, I could login and everything, so I decided to see if a reboot would help. I shut down my PC, and when I started it back up, nothing came up. The PC starts, fans are running, lights are on, but nothing shows up on screen. I have Windows 10 installed on a USB and DVD, I have tried to boot into both, nothing. I have disconnected the C Drive, and then boot into USB, nothing (well, 6 beeps). I have spent 5 hours now trying to fix this. I have tried to boot into the BIOS using the keys that HP says to use, nothing. I reset the CMOS, still nothing. I let it run for an hour straight, nothing. I disconnected both displays and reconnected them, nothing. The monitors are not faulty, unless they both broke in the 30 seconds it took to reboot. So what do I do?

 

[USAFRet]

Start over.
Reinstall the OS, and when you do it, delete ALL existing partitions during the install.
Let Windows install to the resulting single partition, creating what it needs.

What size is the drive, what size did you make the partitions, and why?

 

[KiwiFalcon]

See, that's what I want to do, but I can't reinstall it, because nothing shows up. Windows does not start, I can't boot into the bios, or UEFI, and neither my bootable USB or DVD worked.

The drive was 2TB, Windows didn't allow me to partition it below 495GB, but I used Partition Wizard to get it down to 100GB. I did this so I could make another partition using the unallocated space to store all my music and stuff. I realize now I should've left it at 495GB.

 

[USAFRet]

You can't get into the BIOS? Then something else is wrong.
Getting there happens long before the OS has a chance to mess up.

 

[KiwiFalcon]

I don't know what else could be wrong though. I'm not getting any beep codes, so it's not hardware, and the computer does turn on.

This happened right after I partitioned the drive below what Windows allowed. Could I have wiped some important part the BIOS or UEFI needs when I did that?

Or am I booting in the BIOS, and for whatever reason the monitors aren't showing anything?

 

[USAFRet]

I don't know what else could be wrong though. I'm not getting any beep codes, so it's not hardware, and the computer does turn on.

This happened right after I partitioned the drive below what Windows allowed. Could I have wiped some important part the BIOS or UEFI needs when I did that?

Or am I booting in the BIOS, and for whatever reason the monitors aren't showing anything?

Windows has nothing to do with the BIOS. That should appear even with no drives in the system.

 

[KiwiFalcon]

Then I might have * up my hard drive and not it won't work until I format it (which I can only do if windows is running).

I think I have a hard drive I can "borrow" and replace it then.

 

[KiwiFalcon]

So I put in a new drive, but all I got way 6 beeps. I have an HP Envy h8-1413c. Mobo is some sort of Gigabyte I think. I quick google tells me it means some critical part of the computer failed, but it kept running after the beeps so I don't really know.

 

[KiwiFalcon]

So I tried it with no drives, and just the disc, just the USB, and both. All give the same thing: 6 beeps.

 

[USAFRet]

So I tried it with no drives, and just the disc, just the USB, and both. All give the same thing: 6 beeps.

Then you have other issues.

Try testing the RAM. memtest
All sticks, and 1 stick at a time.

 

[KiwiFalcon]

Tested the sticks, first two were good, then I removed the third, and the computer started for like half a second and then stopped. Then the fan spun super fast, blew up a ton of dust, and then stopped, but the computer remained on. It kind of smells like burning, but I'm not sure. Now, it gives 5 beeps, stops for a bit, another 5, stops for a bit etc.

 

[KiwiFalcon]

Oh. I just fried my motherboard and RAM because I put it in backwards. That's why. No clear burn marks so I guess I'll wait and hope it got lucky, but if not oh well. At least a new motherboard might solve my original issue.

 

[USAFRet]

It's pretty hard/impossible to put the RAM in 'backwards'.