Reboot and select proper boot device, win7

Xandos · 11 Oct 2010 at 10:14

Hi guys, sorry for the boring support thread.

I just installed a new heatsink (noctua d-14), and after rebuilding my PC I get the error: "reboot and select proper boot device". The O/S drive is visible in the BIOS, and can be plugged into another machine to view data.

The only thing that has changed is which SATA ports the various HDDs are plugged in to, and the BIOS reset itself for some reason, so could
have been some settings that got ruined. When I changed the storage configuration to RAID, it now gets past the previous error, and begins booting, get the win7 splash screen, but then it reboots!

I don't have a clue what's going on, and am in desperate need of help!

Thanks for reading.

Xandos · 11 Oct 2010 at 10:36

Yeah, I've got 3 other HDDs in the machine (before the problem), although at the moment I have just the single SSD (o/s) drive, and I have it plugged into SATA 1 at the moment.

Xandos · 11 Oct 2010 at 11:04

Many thanks for the reply.

Currently my O/S drive is in another machine backing up the drive, though I ran the win7 setup with all 3 other drives in it, and the drive/partition screen just showed the one partition for each of those 3 drives, leading me to assume that it's on the SSD (or doesn't exist hah), which I have tried plugged in to SATA 1....

I'm almost resigning myself to a reformat/install - might be quicker than messing with it all day and getting nowhere. But I would love to avoid that!

Xandos · 11 Oct 2010 at 14:19

Thanks for all the replies. I tried resetting CMOS, no avail. There were no installs of windows on the other drives.

I have now reinstalled windows (it's a work machine and I have a deadline, so I needed to be up and running asap), I'm sure someone more skilled could have fixed it in seconds haha.

Strangely that small partition thing wasn't on the SSD either, so don't know what was going on there....

After I'd installed windows something let me to believe that it might have been a lowly sata cable at fault here, but who knows.

Thanks for the help guys.

(now for the fun of reinstalling apps etc. woo)