OPTIONAL UPDATE KB4571744  - NEW nvmestor causes DRIVER_VERIFIER_DMA_VIOLATION over THUNDERBOLT3 on Intel 660p fw 004C

BEWARE, that this optional update HAS PROBLEM IN NVMESTOR-driver at least! I am currently very deeply testing new Thunderbolt3 device (OWC Express 4M2) on Intel NUC10 kit, where I had initially latest DSA pushed TB3 driver "769" aka "66" by Intel and tried more different M2 NVMe SSDs inside this 4 PCIe (x1) device. Most SSD worked badly in it though. Only Kingston KC2500 is almost perfect (tried WD Blue SN550, WD Black SN750, Intel660p Samsung 970evoplus, Crucial MP600, Apacer AS2280Q4, Adata SX8200...) so I tried first to update firmware on Intel660p (002C to 004C), but I ALSO unfortunatelly at single step did NUC10 BIOS update (44 to 45) and install of this OPTIONAL KB4571744 "preview" absolutelly not knowing there is new "nvmestor". Since this 3(!) changes, whole OWC TB3 box stopped working and I had idea that it must be rather something very bad with TB3 drivers (no experience with it yet), so then I tried to update them by anything I found (Intel TB3 DCH support, versions 789, 914, 987) but NOTHING helped, still BSOD "DRIVER_VERIFIER_DMA_VIOLATION" ...

I tried to find everything about "DRIVER VERIFIER", but it was never applied to any driver, never simply, everything clean. 

Only when I REMOVED Intel660p from this OWC TB3 box, then BSOD not happened and PC booted well (and stayed working even after TB3 init), although I had AGAIN very poor performance on remaining disks, it was definitelly FAR WORSE than "before something" - and that "something" was this OPTIONAL UPDATE preview... KB4571744 !! and UPDATED nvmestor driver inside (see screenshot) !!!

When I REVERTED this KB optional update, then previous nvmestor driver started again working even on this Intel660p (fw 004C) SSD and since then NO BSOD about DMA_VIOLATION...

It was all caused by NEW MS nvmestor + INTEL 660p fw 004C inside THUNDERBOLT3 box.

Anyway - after I solved this BSOD, I tried more NVMe drivers, (Intel generic iaStorAC, Samsung generic driver) but they also are working BADLY inside Thunderbolt3 box, for some unknown yet reason. Only KINGSTON KC2500 SSD works almost perfectly with default nvmestor driver and current "769" DCH TB3 driver (I plan to test them all again with reverted working "nvmestor" as t is in fact quite good and it is also pushed as default to TB3 inserted NVMe SSDs (its obviously quite difficult, as OS remembers driver with the SSD in registry, so it was needed to make cleanup and revert to "nvmestor" for all disks and tried NVMe drivers. 

Together with this "OWC Express 4M2" TB3 box (having 4x PCIe 1 lane slots), I have now also one "UNIBOS Portable SSD x4" (JHL6340) and here inside this box, the situation with NEW "nvmestor" + Intel660p was the same (BSOD DRIVER_VERIFIER_DMA_VIOLATION) few seconds after each plug-in of this portable/selfpowered TB3 enclosure. In fact, THANKS to this enclosure, I isolated issue with the nvmestor updated driver and Intel660p - BSOD happened ONLY on this Intel660p SSD and not with others, but performance was anyway VERY BAD.

I have lot of screenshots in attached file "OWC...", also few "minidumps", hopefully some with the new nvmestor DMA BSOD.