After intentionally triggering the problem once again by launching the Intel SSD Toolbox, I do see a relevant Warning in the Windows System Log of Event Viewer.
Event ID 129, Source: arcsas
Code:
Reset to device, \Device\RaidPort3, was issued.
That is followed by Event ID 40 and 41, also with Source: arcsas, which are informational level events.
Code:
The description for Event ID 40 from source arcsas cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\RaidPort3
Got LUN RESET for path #00, target #0000
the message resource is present but the message is not found in the string/message table
Code:
The description for Event ID 41 from source arcsas cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\RaidPort3
Got Target RESET for path #00, target #0000
the message resource is present but the message is not found in the string/message table
Any idea how to resolve these? It seems that launching the toolbox triggers the RAID controller to reset, but this apparently fails, and the associated D:\ drive becomes inaccessible. That explains the sluggish behavior of the computer, and the "hang" on trying to shutdown or restart.
Based on my research online, this type of issue can be based on a lot of things. It could be that the PCIe link power state is set to "turn off" to save power [not the case for me]; it can be a faulty SATA cable connection [also not the case for me] - it definitely is triggered by launching the Intel SSD Toolbox.
It could be that the firmware upgrade to the latest version actually introduced this issue. But I'm still reluctant to downgrade the firmware back to the prior version...
Any thoughts / other suggestions?
Thanks!