#SAMSUNG SM961 DRIVER WINDOWS 10 INSTALL#

I can also install windows into one of the other drives and boot to it, but that's not what I want of course.

#SAMSUNG SM961 DRIVER WINDOWS 10 PLUS#

This should work but I don't want to go through the countless configurations and installations I did, plus I don't seem to be able to do it anymore because the windows bootable drive doesn't see the RAID volume.

#SAMSUNG SM961 DRIVER WINDOWS 10 WINDOWS 10#

I was once able to use my bootable windows 10 drive and install a fresh windows installation into the raid0 after the loading the raid driver. Run startup repair or troubleshoot using a device restart or advanced options (F8 and the rest) I also don't seem to be able to really break the raid array because when I change the mode and change back to RAID, I can still see the volume created.why? Anybody has this mobo and tried to run RAID0 with his M.2 drives? Please say yes.ДЄnyways, instead of booting into windows I get all kinds of BSOD: I think the problem resides here somewhere. I must be lost in the EFI and UEFI BIOS, CSM, and secure boot stuff. So, if you don't have data to lose then it is fine.

The only way to access it is the EZ tunning wizard!!! What?! Why!?Д«efore in normal BIOS I remember, you can freely switch back and forth very easily. But, even then I can't find it sometimes, to recreate or delete the raid volume.

Maybe only after I disabled CSM and rebooting I was able to see something. I don't see an option for it in the advanced PCH menu. One thing I should mention is the stupid way they have now to create the RAID volume. I understand having multiple drives could confuse things but the boot order should take care of this in the BIOS. Load the image into my newly created ~ 1TB raid volume, the thing which I thought everything will be fine after. I went through some trouble to get it to see it (loading Intel rapid storage driver) and then did what's expected. Unfortunately, Reflect didn't detect my raid array. I then booted into my bootable Macrium reflect drive, located my saved image and started looking for my raid volume.

I then went into the UEFI BIOS ( I must say I hate this one, used to be much easier), changed the SATA mode from AHCI to RAID and created my ~1TB RAID0 volume. I installed Macrium Reflect in my windows drive and created an image of the whole OS drive and saved it externally somewhere. I haven't experienced this boot problems in my entire 20 years life of building PC's.

#SAMSUNG SM961 DRIVER WINDOWS 10 PRO#

The minute I decided to add another sm961 pro into my mobo to create a RAID0 volume and migrate my windows installation into it, my nightmare started. What I thought would be a very straightforward process turned out to be otherwise. And one 512GB sm961 (The oem version of the samsung 960 pro ) where windows 10 pro is installed. I7 7700K GHz on ASUS Maximus extreme IX formula I think this is the best place I should put this. The really good thing is that the M.2 drive is much, much easier on the battery and is not the vampire the HDD was. Once I was running on Gandolph's virtual desktop, I was fortunate to be able to Quick Format the 1 TB HDD. If you plug the HDD in before booting Win10 will boot from it. The trick is not to plug in the HDD drive until you are in the boot process with Gandolph. I tried to boot from my Windows 7 install and access the HDD but it was 'hidden,' likely by Windows 10. It worked a treat, I used the old version and not the new (as of this writing). The only way to do it was with a little Black Hat app know as 'Gandolph's win 10 ењ†4' boot disk. It was a lost cause erasing the 1TB WD HDD drive of its Windows 10 installation though. It may have had something to do with removal of the battery. However, I had to plug in the laptop to the power source to get it to boot. Just so others know, that removing the HDD from the laptop enabled me to start from the new Samsung 961 OEM M.2 drive.

Samsung sm961 driver windows 10