I just built a new system with an ASRock X79 Extreme6 motherboard. Everything went great until I booted the machine up and my hard drives were no where to be found in the BIOS.

1. Win 7 Iso Torrent
2. 775i65g Drivers Windows 7

It recognized my SATA dvd drives just fine, but the SATA hard drives aren't there are at all. I read in the setup manual that 'If you want to install Windows on a SATA hard drive you have to make a SATA driver floppy disk' This has to be a joke, right? I haven't had a floppy drive in a machine for well over five years, and I have never heard of a BIOS that is unable to recognize a SATA hard drive on its own. Does anyone know what the deal is here? It seems totally backwards to me that I have to install Windows to get my BIOS to recognize a SATA hard drive.

I've tried setting all of the BIOS options to SATA to IDE mode and compatibility mode and still nothing. Help, please! 'I read in the setup manual that 'If you want to install Windows on a SATA hard drive you have to make a SATA driver floppy disk' Maybe you can tell us what page that was on. I just looked through all 101 pages of that users manual and didn't find a mention of floppy disk. It doesn't explicitly tell you you need to use a floppy drive to do it in the manual.

But the BIOS does not natively recognize the SATA HDDs. And when you insert the setup disk that comes with the motherboard, it prompts you to make a driver disk to use when installing Windows. Do it my way as posted here (I should probably make a sticky) - The problem is Window 7 and not anything else, Widows lacks the drivers.

Probably not an issue in Windows 8. Let me know and Good Luck! First, thanks for the reply! Secondly, this problem is deeper than Windows, isn't it? My hard drives should show up in the BIOS, regardless of whether or not I have installed Windows. This is the part I don't understand. Why does Windows have anything to do with whether or not my BIOS can see a hard drive device attached via SATA?

First, thanks for the reply! Secondly, this problem is deeper than Windows, isn't it? My hard drives should show up in the BIOS, regardless of whether or not I have installed Windows.

This is the part I don't understand. Why does Windows have anything to do with whether or not my BIOS can see a hard drive device attached via SATA? Not if they're on Marvell and quite often if they're not formatted. Rather than driving yourself crazy, create a Flash Drive installer with the appropriate Intel RST Enterprise (F6) drivers, set the SATA - RAID and afterwards either leave as-is or back to AHCI.

See if the Windows installer 'sees' the HDD/SSD's and if not then worry. I assume that both the SATA and power is connected if for some reason they don't show-up.

Not if they're on Marvell and quite often if they're not formatted. Rather than driving yourself crazy, create a Flash Drive installer with the appropriate Intel RST Enterprise (F6) drivers, set the SATA - RAID and afterwards either leave as-is or back to AHCI. See if the Windows installer 'sees' the HDD/SSD's and if not then worry. I assume that both the SATA and power is connected if for some reason they don't show-up. These HDDs were transferred from an old build of mine.

They are all formatted and they all work. It's just crazy to me that the hardware and BIOS don't work together out of the box. I really can't wrap my mind around why the SATA controller would not be able to natively recognize an HDD. Aren't the protocols for this stuff standardized? In my last build these SATA drives just worked. I will give your solution with the Intel RST Enterprise drivers a shot, though.

If it works then great, but I just don't get it. EDIT: One more thing. One of these SATA drives has data on it that I do not want to lose.

Should I back this data up to an external drive before I move ahead with your solution? It seems like I will lose all the data on these drives, correct? Most folks do NOT properly install their OS, and IF those OLD HDD's were connected while a primary (SSD/HDD) was being installed then their MBR or GPT is corrupted. No the X79 has it's own/new and modified version of MBR/GPT; BootX is added.

Further, if these OLD HDD's are going to be used as 'DATA' drives then disconnect them until the 'Primary' SSD/HDD has its old partitions deleted and is (re)formatted. Take 5 seconds and read 'FIX' #'s 16.

I can assure you if the drives are good that following what I posted they'll work. BACKUP ALL DATA!!! It's best to have the drives formatted and cleaned. The OLD HDD if being used as a boot drive then MUST be reformatted and its' partitions deleted. Most folks do NOT properly install their OS, and IF those OLD HDD's were connected while a primary (SSD/HDD) was being installed then their MBR or GPT is corrupted.

No the X79 has it's own/new and modified version of MBR/GPT; BootX is added. Further, if these OLD HDD's are going to be used as 'DATA' drives then disconnect them until the 'Primary' SSD/HDD has its old partitions deleted and is (re)formatted. Take 5 seconds and read 'FIX' #'s 16. I can assure you if the drives are good that following what I posted they'll work. BACKUP ALL DATA!!!

It's best to have the drives formatted and cleaned. The OLD HDD if being used as a boot drive then MUST be reformatted and its' partitions deleted. Do I need to create a USB Win7 boot drive?

I have a Win7 OEM DVD. Does that do MBR by default? I have tried setting my SATA configuration to RAID and installing the linked RAID driver at the Win7 install screen. The RAID driver installs but Windows is still unable to detect the drive (neither the setup screen nor diskpart see it) I have disconnected all the HDDs with the exception of 1 (SSD), connected to an Intel SATA2 port (not Marvell, which I'm not sure I even have on this board). Is it possible I need to flash the firmware on my SSD?

Could I try a standard, non SSD SATA HDD in place of this SSD to test if it's the SSD firmware that's the problem? Every single X79 install I did was from a Flash Drive and using the Intel RST Enterprise drivers.

Again, if you read then I don't recommend using both the DVD and Flash Drive; I have seen instances where doing so required the folks to leave in the Flash Drive otherwise they get errors and boot failures. Don't 'rethink' what I posted. Sure, it's possible that both your SSD and HDD require updated Firmware. It's best to do that on another PC with both the SSD and HDD's not as boot drives and if the other PC is running in AHCI mode in most cases for the Firmware to install or properly install. If your SSD is a SATA3 type then use the Intel SATA3 port.

Marvell in (many) cases is not for booting and instead for data-only. ASUS using them differently and of SSD Caching for the HDD (boot) + SSD (cache) which I really don't recommend. AGAIN, the SSD/HDD or whatever WILL NOT show-up UNTIL THE PROPER Intel RST Enterprise SATA DRIVER IS LOADED!!! Once driver is loaded then like magic it'll (SSD) show-up, but not until. If you boot the Flash Drive, F8, then as soon as you see Install Windows at the bottom as I recall there should be something Load Drivers.

In that link, there's a very nice and needed video to watch 'How to make a MBR OS Flash Drive' and then you'll need to also add the Intel RST Drivers in a folder i.e. 'RAID' call it anything - BUT the drivers must be UNZIPPED FIRST!!! I'd also add the Chipset and NIC drivers in another folder. Use only the latest drivers and NOT from the ASRock CD/DVD. AGAIN, the SSD/HDD or whatever WILL NOT show-up UNTIL THE PROPER Intel RST Enterprise SATA DRIVER IS LOADED!!! Once driver is loaded then like magic it'll (SSD) show-up, but not until. If you boot the Flash Drive, F8, then as soon as you see Install Windows at the bottom as I recall there should be something Load Drivers.

Win 7 Iso Torrent

So, I tried that. The driver installs fine but still no drive. Again, I want to be sure you understand that the drives don't even show up in the BIOS itself. My SATA dvd drives show in the BIOS but my SATA hdds do not show.

I can't help but think there is something else wrong here. I'll keep trying though.

BIOS version 1.20 just came out today. So IMO update your BIOS.

Use ASRock's Instant Flash - 'Listed BIOS fixes', in my experience there always more that are 'unlisted': 1. Update CPU code.

Modify USB keyboard/Mouse can't work after resume from S3. So, I finally figured out the problem, and I feel really stupid for not double checking this. The hard drive is actually fried, which is why it's not being detected. I knew something was weird about the BIOS not recognizing the drive.

It had nothing to do with drivers. Just a fried hard drive and my stupidity! After installing brand new hard drives, the BIOS detects them without a problem (and without installing Windows). After that, I installed Windows and everything works fine (I didn't need to install SATA drivers either).

Even though it wasn't the solution to my problem, I chose your most recent post as the best answer to acknowledge your help and to close off the thread. Again, thanks for your help! If you installed as AHCI and by not using the (F6) driver as I suggested then the wrong driver is running and will eventually if not already corrupt your MBR. More than likely if the PC fails to wake from sleep properly this is the cause. To test, simply set the SATA - RAID if it BSOD's then the Intel RST Enterprise drives i.e. The wrong drivers are installed. This typically cannot be corrected after the fact.

Sorry you had a bad SSD, it happens. Will this also corrupt the non-windows drives, or is it only on the boot drive? I really don't want to reinstall Windows again, but I will if I must. Also, I should ask if this corruption will happen even if I keep my drives in AHCI mode (which they all are, and have been since installation).

775i65g Drivers Windows 7

Try as I suggested changing to RAID (BSOD), Sleep (Start menu / select Sleep), or simply start-up Windows repair (something like problem found and unable to repair). This Intel RST Enterprise (AHCI/RAID) is so far universal to the X79 Chipset, but maybe ASRock is fine (immune) with AHCI Windows then Intel RST replacement after the fact.

If I didn't build X79's then I too would have assumed, but incorrectly, that the (F6) or as I described wasn't required. Further, unless the Intel RST Enterprise is properly used (MBR) then you are, no doubts about it, losing significant performance - not to mention the MBR. IMO test with ATTO now, reinstall OS and compare ATTO with the latest Intel RST-E drivers. It's your rig, do as you want. I ran across this once the hard way and then I re-installed 'properly' and all the problems were corrected. Most X79's I've done were RAID 0 boot SSD so there's no choice but to install properly using the Intel RST-E driver; however, once I had a single SSD and later 'tried' to change to RAID to add a RAID 1 data drive.

I could add the RAID but Windows BSOD even with the Intel RST-E driver installed after the fact. Installing Windows is a cake walk. My best suggestion, and one that's often difficult to follow. I 'get' the need to play, but I also get the PITA of failures. Never install anything other than Windows, Drivers, normal/OC BIOS environment, and Testing Application(s) e.g. AIDA64 until there's a MINIMUM of 24 hour or better a 48 full burn-in followed by 4-6 full passes of Memtest86+, and the PC works as expected (booting, sleep, hibernation, shutdowns.

You name it). If a PC cannot endure those tests in the 'normal operational' environment then your time wasted is greatly reduced. ANS - yes IMO folks are crazy not to do a proper burn-in, and in most instances your ultra-fast RMA/Exchanges goes bye-bye after 30 days. In comparison, a typical non-cross-ship MOBO RMA is 3+ weeks from ship to receive date. You might as well find out now than later. I do a series of tests and validations, pretend you're building this PC for a paying customer and want repeat business. Nothing will piss them off faster than the PC going poof two days later, so why short change yourself?!

IMO makes no sense! Since I assume the 'plan' is to game for more than 1 to 2 hours, it seems crazy not to fully test for a lot longer period of time. Remember, Prime95 only stresses the CPU and to a limited extent the RAM only not to mention ignoring several instruction sets that aren't tested. AIDA64 tests them all.

Tests like 3DMark 11, PCMark 7 and 3DMark Vantage are primary benchmarks than ideal stressing test unless you have a copy that can 'loop' repeatably. Ditto with to benchmark vs testing the drives. I own a copy of, It's $39 USD and IMO worth the costs and has the ability to stress and test everything. Recently added features can be found. The free version I'm not sure what it limits or omits, but it's better than Prime95. On PC's I build, 48 hours for a PC and 96 hours for a Workstation. In this time you'll find 99% of any component issues.

Another 0.5% within. Reduce it's lifespan no, that is assuming you don't do something stupid like excessive voltages. Example, 1.45v on any SB-E or VCCSA 1.30v is simply crazy and will indeed shorten both it's life and permanently damage the SB-E CPU (at least a 2 or 3 bin for good loss). If it's running at stock (F5) then it should be good for years straight non-stop. I have servers that are running on average 80% 24/7/365 until they break. I have nothing to do or control of AIDA64's policies.

It's a quality product and does the job. You can certainly try/use the free version; all I know or remember it disables some read outs and perhaps tests. Remember, the objective now is to make the PC fail and hopefully any poor component(s) fail.

Better now than to baby it and have it fail after the easy exchange period. This is simple logic - go play and enjoy. Then try to find the weak link - if any. (2) days no toy, but afterwards a PC you can trust for years! Update 1: I tried changing my SATA mode from AHCI to RAID, and my machine did indeed BSOD immediately after the windows boot screen appeared. If I understand correctly, the BSOD is an indication that I am using an incompatible driver.

And further, that incompatible driver will, over time, probably corrupt my MBR. As I understand it, normal use will even corrupt the MBR - that is that even if I never attempted to switch from AHCI to RAID that the MBR will still be corrupted through normal booting/rebooting/usage. Because of this, I am planning to reinstall windows using the latest Intel x79 RAID driver.

I'll make another post when I've made further progress. Update 2 First, I ran memtest overnight and it passed 5x with no errors. I followed your instructions. So far I have: 1. Switched my SATA mode to RAID. Reinstalled Windows 7 using the latest Intel X79 SATA RAID driver.

I installed Windows on a Simple non-RAID volume. After installing Windows, I installed all of the motherboard drivers, including the Intel chipset driver and RST driver bundle. Installed latest GFX and Sound card drivers. I plugged in my other hard drives and re-partitioned them using Simple non-RAID volumes. Next I will download AIDA64 and begin the burn-in test for this machine.

Update 3 I downloaded the trial version AIDA64 to perform my stress test. I have managed to get it stress testing all 4 CPU cores and the GPU. With an ambient room temperature averaging around 70 F, my temperature readings as of 12 hours into the System Stability Test are (in degrees C): CPU Core 1 37 min, 61 max, 55 avg CPU Core 2 36 min, 60 max, 53 avg CPU Core 2 40 min, 63 max, 56 avg CPU Core 2 40 min, 63 max, 57 avg CPU Socket 44 min, 49 max, 46 avg Motherboard 41 min, 44 max, 42 avg GTX560 GPU 59 min, 74 max, 72 avg Those temps look to be within tolerance to me. I plan to let the test run for 48 hours.

Most folks do NOT properly install their OS, and IF those OLD HDD's were connected while a primary (SSD/HDD) was being installed then their MBR or GPT is corrupted. I installed a pair of SSDs in RAID 0 as my primary boot drive on the same motherboard the OP is talking about (Asrock X79 Extreme6). I didn't have to install any special drivers for the the UEFI bios to see the SSDs connected to the Intel sata3 ports. I also had 2 other mechanical drives connected to the Intel Sata2 ports.

I set up my RAID 0 array and Installed Windows 7 with these other drives connected without issue. What do you mean that my MBR is probably corrupted? I just made an install USB drive with Windows 7 and added an extra directory for the RAID0 drivers (no floppy required). I did encounter the common glitch where I had to change USB ports part way through because WIN7 installer stopped recognizing the USB drive, but other than that, no problems. I'm not noticing any performance issues either. Are you saying I am/have potentially damaged something because I had my two other HDDs connected while installing Windows?

One thing I noted is that when setting up the RAID 0 array, RSTe does not tell you the actual max array size. My drives listed as 238.4GB each, however the max array size was indicated as 453.1GB. However, I was able to manually enter an array size up to 476.9GB and RSTe accepted it. Xbox unleashx skins.