Application or device that uses the NVMe interface does not work correctly in Windows 8.1 or Windows Server 2012 R2

Scenario 1

This issue occurs because the NVMe device and the StorNVMe interface support Physical Region Page (PRP) lists only for data transfer operations.

When Windows performs a data transfer operation, the device receives a memory starting address and the sector count that is transferred. Therefore, when the data buffer size is not a multiple of the sector sizes, READ and WRITE commands do not work correctly. More specifically, READ commands cause the device to transfer more data than the data buffer size, and WRITE commands cause the device to write to the disk with random kernel memory data in the data buffer.

Note Unlike other device protocols that support Scatter/Gather Lists that have buffer lengths in bytes, the PRP list for the data transfer only knows the sector count to be transferred. Therefore, StorNVMe converts the data transfer size to a sector size. 

Scenario 2

This issue occurs because the Stornvme.sys driver clears the report when the NVMe device generates the SMART Async event. Therefore, the device is in a loop of sending an Async event if the health state of the controller does not change.