You were Correct ...no help whatsoever but Win10 got a Clean out I guess :)
this has been going on since Windows 8 I have read elsewhere , and Intel still hasn't fixed it ... and the postings at Intel say they can't reproduce the error.....
I Tried 3 different Raid Drivers in the 13 and 14 Series per your recommendations and still the same issue , except that I could no longer enable acceleration on the Array again with the 60GB SSD I have for that.
I also noticed in Event Viewer something was preventing the 4th Disk from being ejected by the Raid Controller ...very strange ....

So I Rolled the Drivers and RST Control Panel back to version 12.9.4.1000 you provide a link too , and the Array Disks are now seen in the Defrag App and there are no longer errors in the Event Viewer either.... not yet anyway. And 12.9.4 also let me turn acceleration back on too, so I guess I am stuck with 12.9.4.1000 for now.

Could it have anything to do with the Raid OROM on this X99A-II MB ? it is 14.8.0.2377 still on Bios 1101 that came out several days ago.

KB.

Thanks Fernando.... I do appreciate you looking at the Thread and the good Advice given as usual.

If it is all working (still testing) then I am not concerned about having the Latest and greatest , so will stay with 12.9.4.1000 for now.


KB

Just an update , thought I'd try a 15 series Driver since Intel said to wait for the latest release......

but latest driver 15.2.0.1020 does not fix this issue either , so I'm back on 12.9.4.1000

So far ALL Drivers above 13.x.x.x cause this issue.

KB

Zitat von Fernando im Beitrag #20

---

@Kbird:
Although I don't yet know the exact reason for the special issue you have running Win10 v1607 on your X99 chipset Intel RAID system, your experiences with different Intel RAID driver versions verify, that the latest Intel RST/RSTe drivers are not automaticly the best (not even when they are installed onto an up-to-date Intel Chipset system, which is natively supported by the related driver).
@all:
Just to avoid any misunderstanding: Kbird's problem is not a general one. Usually Intel X99 Chipset RAID systems are running fine with the latest Intel RST(e) RAID drivers of the v13 and v14 platform in combination with the OS Win10 "Anniversary Update".

---

just an update incase anyone else has this issue and sees this thread....

I am in Raid so I installed the latest 15.5.0.1051 to see if they helped with my Raid 0 Array HD Disks seen as SSD's , it does not unfortunately , so far only drivers before the 13 Series identify them properly eg 12.9.4.1000 even though the RAID BIOS is v14.8.0.2377

These installed fine and the RST Software seems to be working correctly

Asus X99A-II MB with the Chipset Raid Controller seen as PCI\VEN_8086&DEV_2822&REV_05

Another update :
Unfortunately nothing has changed for me in regards to the WD 640GB Hard Drives in Raid being seen as SSD's but I recently discovered that the 12.9.4.1000 Drivers crash in Win10 on Long, multi GB File transfers , causing the Computer to Crash.

Most recently a 106GB transfer caused the crash so I am using the Best Drivers as suggest for the X99 platform, which are RST(e) Driver 14.8.16.1063. This Driver when installed however, also changes the Driver for the Secondary controller to a C200+/C600, which causes the RST Software to lock up and you can't open it off the taskbar or elsewhere. Changing the Secondary Controller back to a Standard AHCI Controller and rebooting, fixed both these issues and the 106GB transferred fine.

So still defragging manually for me....

Asus X99A-II MB with the Chipset Raid Controller
Forum - Which are the "best" Intel AHCI/RAID drivers?

EDIT by Fernando: Text merged and unneeded blank lines removed (to save space)

It appears I am wrong about 14.8.16.1063 , transferring 103 GB from Disk to Disk went ok ...just lucky?
Tonight I was transferring about 100GB from my old computer (X58A) to the new one (X99) , it lasted about 3-4 mins and the computer crashed again , so now I am getting worried I will damaged the Raid Array.
Perhaps I will try transferring smaller amount in one operation and see if it helps.....if anyone has any other ideas please let me know , Thanks.

KB

EDIT by Fernando: Unneeded blank lines removed (to save space)

Just an update on this issue , I personally still have it ( WD 640GB Blacks) but another User on the Intel Forums with the same issue, had one WD 500GB drive fail on him so he replaced all 4 drives since he wanted larger capacity too nowadays and no longer has the issue , he believes it is probably due to the older WD drives being SATA2 interface (3GB) and the new ones being SATA3 (6GB) , so I am guessing it is a HDD Firmware issue and it not communicating properly with Drivers above 12.9.x.x

This is his post from over there (>LINK<):

Zitat von Mr-Scary

---

UPDATE: I had a slight failure on one of my drives in RAID0 almost 10 years old, so I built a new RAID0

REMOVED: RAID0x4 | (4) 500GB WD Blacks SATA2 | 32MB Cache | WD5001AALS
REBUILT W/: RAID0x5 | (5) 1TB WD Blacks SATA3 | 64MB Cache | WD1003FZEX

Now the Windows 10 Drive Optimizer is working fine.
Using driver: 14.5.0.1081 as per EVGA for the X99 FTW (no driver change.
However I did receive the Win10 Fall creator's update.
Windows 10 Home Version 1709, OS Build 16299.64

This may have been something to do with the newer SATA3 controller in the Western Digital drives. The old drives were SATA2.
This could also have something to do with having 5 drives rather then 4, or the fact they are now 1TB drives vs. 500GB
I hope this info helps Intel, or whoever in correcting the issue.

I would also like to note that this upgrade increased my speeds, and the drives are not recognized as SSD/s anymore.

---

EDIT by Fernando: Quoted text marked as being quoted and added the related link (to make it easier to find the original discussion at communities intel.com