New
#11
I was having problems hanging with the driver installed on the update too. I am running RST 13.6.3.1001 with no apparent issues (I have many others with this update though).
I was having problems hanging with the driver installed on the update too. I am running RST 13.6.3.1001 with no apparent issues (I have many others with this update though).
Same exact thing. Took me a half a dozen reformats to dial in on the issue. Irst and/or intels raid drivers simply hang windows 10.
Even the ms installed ones seem to hang if you try to enable cacheing or disable buffer flushing via device manager.
Shame. Feel like I'm running handicapped but no way on earth I'm touching anything data related again for a few months.
Amazing a company like Intel who has to have an all but sibling like relationship with ms and had known about and more about win10 than almost anyone still falls flat with release drivers. Same with nvidia tbh.
I hate tin foil hat types but they were onto something when they said they're going to wait a half a year before upgrading.
Millions upon millions with millions in between yet quality control testing must get the smallest budget ever. Less than toiletries I reckon. 3 man team... Obviously.
Before my upgrade from 8.1 to 10 Pro I was running RST 14.0.0.1143. My system is on a 2-SSD RAID 0 partition. I upgraded with no problems and have had none 2 days running, including stress testing at 4.5GHz overclock. OK, I had an expected BSOD because of the OC at one point , but the file system is working fine.
Thomash,
It looks like you've just went through what I've been trying to investigate first in the hopes of avoiding issues. I was thinking of upgrading to Win 10 as well & I have the same C600/X79 Chipset on ASUS Rampage Formula MB. I have 2 Samsung EVO 500GB SSDs in RAID 0 for my primary drive, but no second RAID for storage (just 2 single 240GB SSDs from my last RAID 0 installed individually). I noticed you had issues with the older WDC drives, but did your two OCZ Vertex SSD drives have issues with RAID 0 on the drivers in Post#2 above in Win 10? Also, I've been using RSTe/AHCI CIM_CLI 3.8.1111 drivers because they pass trim commands on SSD/RAID configs. Do these drivers support this as well, or are you concerned with TRIM? Just wondering as I don't want to loose my SSD/RAID0 just to upgrade to Win 10.
That is not universally true. I have 2 840 Pro SSD in RAID0 for my boot disk. I had hangs after I updated from Windows 7 (not sure if they were disk driver, but I think so), but after a clean install everything is fine. It has been running for a couple of days with no issues nd I have buffer flushing disabled and write-back cache enabled.
I don't think Intel is to blame, I think Microsoft is.
.
I had no apparent issues with the SSD drives with any of the drivers I tried. It was only the storage volume with the WD disks that was causing the issue. Still, I can't guarantee anything, since it seems that this behaviour is depending on some property of the drives that I have no idea what is.
In short I would guess it'll probably work for you with an SSD RAID0 volume for your system drive, but I can't be sure, and all bets are off when it comes to a second RAID0 with mechanical drives.
If you have a link to the drivers with TRIM support that you've been using, I'd be happy to give them a try.
I've been using these drivers for some time now and have personally verified that TRIM is working a couple different ways. One is to verify TRIM is on using FSUTIL, and the second with a "TRIM Check" program that write a block of data and then targets it for delete. You run the program again in about 30 seconds or so and it verifies the block of data was processed by TRIM (I think that's how it works). In any case, everything I can find shows me TRIM is working on my RAID 0 config. The issue is I haven't been able to find a WIN 10 version of this driver that will keep TRIM working on RAID0 in Windows 10. The link below is to the drivers, but it only goes up to Win8.1, no Win 10. Here's the link:
Intel Download Center
You can read the release notes for the driver and it lists that TRIM support for SSDs in RAID 0/1/10 has been added to this series of driver (3.8.0.111 is actually one release later than the first to support this feature). I've pasted an excerpt from the release notes below. The release notes can be found on the same page as the driver download page (link above).
If you find a Win10 version of this driver that supports TRIM for SSDs in RAID 0/1/10 I would sure love to hear about it!!!
=============
Fixes/Updates
=============
Version 3.8.0.1111
1. Resolves TRIM commands may not be processes properly to SSDs on Windows*8 or Windows* Server 2012
2. Resolves the issue of the I/O appears to exceed a timeout period and SATA link may reset if the system clock change occurs while an I/O is in the progress.
3. Resolves issue of running heavy I/O to SSDs while enabling TRIM may result in the system running out of memory.
4. Adds support of the UEFI driver reporting the physical port a device is connected to
5. Adds support to configure RAID volumes using Intel(R) RSTe UEFI Human Interface Infrastructure (HII)
6. Adds support for Windows Server 2012 R2 and Windows 8.1
Version 3.7.0.1093
1. Adds support for configuring RAID when EFI Optimixed Boot is Enabled with UEFI 2.3.1/HII-capable system BIOS (See BIOS release notes)
2. Adds TRIM support when SSDs are configured as RAID 0/1/10
3. Adds the capability to view expander and update expander fw in Windows 8 and Server 2012.
4. 3.7 drops support for Windows Vista
Had similar issues on a Z77 sabertooth board running 2 Intel 520m disks in raid0.
Upgraded to Win10 and everything was fine, installed all drivers etc. But then all of a sudden the OS started locking up a couple of second to some minutes after booting. Also had disk error in the event log. Did several reinstalls but never saw the connection to the RST drivers. Reinstalled Win7 and the same shit happend again. Reinstalled a couple of times and finally narrowed it down to the intel drivers. So i guess the new ones are a mess on some boards and chipsets?
Software RAID is more trouble than it's worth most of the time.
You should consider a hardware RAID in the future.