thanks, i know how to install moded drivers, just wanted to test latest drivers with windows 10 1709 support

i uploaded all the results in this topic Performance of the Intel RST/RSTe AHCI/RAID Drivers (23)

Surprisingly, the most recent Windows Insider Build 17083.1000 does install the v15.44.0.1006 dated 10/24/2017 Intel RAID driver on my X58 + ICH10R system. This definetly didn't work with former modded RAID drivers from the v15.X branch before and resulted even in a boot loop (only a saved restore point could save you out of this mess). No benchmarks so far, but I thought of sharing this piece of information. It was also the first Insider build of RS4 which installed fine at all.

The latest RS4 Insider Preview installed v15.44.0.1006 by default (I did an in-place-upgrade from 16299.192 where I used the 13.44 driver which came with RS3). That's why I am so surprised because all of your modded + signed drivers of the v15 branch which I tried before (not the latest though and with older Windows 10 builds) ended in a boot loop (the installation went fine and the device was recognized as DEV_2822, but the first reboot ended with a non-booting system and a never ending rolling circle). The board is an Asus P6T Deluxe V2, but I crossflashed it with a modded P6TWS PRO BIOS. My currently used RAID ROM is 10.1.1008 (cannot be upgraded as a limitation of the Asus P6TWS PRO BIOS). Last year I've experimented with the Asus P6X58D-E BIOS which allows newer RAID ROMs to be inserted (tested working up to Intel RST(e) RAID ROM v15.0.3.2675, the probably best combination was the 13.2 ROM + matching driver) but it does not work as reliably with my Xeon X5650 as with the Xeon E5645 before due to a bug with the always-on turbo multiplier.

I've tried now ATTO and Chrystal Disk Mark for some benchmarks, but both programs crash the whole system. :(

Well, as my system is heavily modded and now running on an Beta OS, there are lots of variables at play. It could be an issue with the Insider Preview itself with these programs, as gaming seems to be fine so far. I'll try out other workloads. Copying large amounts of data could potentially show these problems as well. I also could try out one of my P6X58D-E BIOS versions with a 15.X Intel RAID OROM. Maybe they work better together.

You are right about the iaStorF.sys - I cannot find it under Windows\System32\drivers, the device manager tells me that it uses solely the iaStorAV.sys.

Maybe Microsoft put some pressure on Intel to make these older systems compatible with some OS changes?! Either way, I'll test it further and will report my findings, if something remarkable happens.

But you are cynical. :) I can imagine the shitstorm if Microsoft does not support such capable and still relevant older hardware. At least these crashes need to go away even though performance might not be optimal in the end.

By the way, reporting back from my testing: the same crashes occur on my modded P6X58D-E BIOS with Intel RST(e) RAID ROM v15.1.0.2545. Also the problem shows when copying large amounts of data from one partition to the other.

I've just installed your modded in-box driver from the 13.44 branch and the crashes are gone. So you were absolutely right about the culprit being the 15.44 driver. The performance in 4K reads (that part worked with the newer driver) is three times lower though (2.2 vs. 6.6 MB/s). But my settings with the P6X58D-E BIOS are not the same (lower RAM / CPU speeds). Switching back to the P6WS Pro BIOS and calling it a day, I guess. Thank you very much for the hint! :)