Solved

Trouble installing Windows 7 on newly built PC

I'm trying to install Windows 7 on a PC that I just finished building. I'm using an SSD that I wiped using Parted Magic. The SSD shows up in BIOS, but when I turn on the computer I get a black screen that says:

Marvell 88SE61xx Adapter - BIOS Version 1.1.0.L75

Adapter 1
Disks Information:
No hard disk is detected!

I tested this SSD in my other computer and the windows installer was working, so I don't think there is a problem with the SSD.
Here are some of the parts I'm using:
Motherboard: http://www.newegg.com/Product/Product.aspx?Item=N82E16813188121
Optical drive: http://www.newegg.com/Product/Product.aspx?Item=N82E16827135204
SSD: http://www.newegg.com/Product/Product.aspx?Item=N82E16820167127
5 answers Last reply Best Answer
More about trouble installing windows newly built
  1. Try disabling the Marvell IDE controller in BIOS
  2. dodger46 said:
    Try disabling the Marvell IDE controller in BIOS


    I'm not sure where to find that option in the BIOS but I'll keep looking.
  3. adun4184 said:
    dodger46 said:
    Try disabling the Marvell IDE controller in BIOS


    I'm not sure where to find that option in the BIOS but I'll keep looking.


    Aye, your Manual is pathetic! I was hoping to see some details of your BIOS, but nothing was to be found. Presumably it is a UEFI? Look under Boot options Tab for HDD priority or similar and make sure the SSD is selected. Unfortunately without a detailed account of the BIOS it's impossible to give accurate advice...
  4. I just called EVGA technical support and they said that it is most likely the BIOS chip (I think that's what they said) and that they would send me a replacement. Apparently this was a common issue a while ago and there are still some faulty motherboards out there.
  5. Best answer
    adun4184 said:
    I just called EVGA technical support and they said that it is most likely the BIOS chip (I think that's what they said) and that they would send me a replacement. Apparently this was a common issue a while ago and there are still some faulty motherboards out there.

    Oh well, that would explain things! At least we were 'fishing' in the right area... didn't expect a faulty BIOS chip though...
Ask a new question