Michael Vickers

Thanks. I've uploaded the last memory.dmp to dropbox, under my name.

Hi Christopher. Thanks for the reply. I just got this array set up and stable on new hardware last week after a lot of headaches. I'm hesitant to run beta software on the server now while trying to trigger a bsod and not turn the array into scrambled eggs at the same time. I'm content to run with the workaround for the time being and watching to see if 1) you folks can replicate the error and 2) issue a fix for it.

I'm posting this info in case anybody else runs into the same thing. Host: Win2k8R2 x64 running DrivePool 2.1.1.561 Guest: Win2k8R2 x64 In Disk Management on the host computer map the DrivePool disk to a path. Here is an example where I've mapped my DrivePool disk to a path on the C drive (it's the second entry): https://www.dropbox.com/s/ns93g4guhaoae3m/Screenshot%202016-09-24%2014.43.41.png?dl=0. Share the folder containing the path. In my example I'm sharing C:\Volumes which contains the "P1" folder which is mapped to the DrivePool disk. In the guest machine either map a drive to that host share or browse the host share without mapping a drive. Browse into the DrivePool disk on the share. Create a new folder and give it a name. BSOD occurs in covefs.sys on the host. In my setup when I create the folder the BSOD occurs immediately. When I reboot and go to rename the folder the BSOD occurs again and the folder does not rename. The workaround is to share the DrivePool disk directly. For me the error does not occur when I map the DrivePool disk to a letter (in my example drive "P") and then share that drive letter in the host.