I have come back to this and spent a good part of the morning searching. With some assistance from a colleague stating this is probably due to a query running repeatedly, I then looked deeper by double-clicking the error itself:
Notice the occurrences are 5 minutes apart for a trigger event.
Go to the Configuration tab and open statisticserver.ini file and locate the statisticserver_array_VOLUME_IO_DETAILED_STATISTICS_TRIGGER_ASYNC_READ_COUNT and statisticserver_array_VOLUME_IO_DETAILED_STATISTICS_TRIGGER_ASYNC_WRITE_COUNT and notice the intervals are both interval_5min:
Maybe since the default on this file is 5 minutes, it does not complete the initial search? Or, maybe both queries are competing for the same information? Additionally, the size of the file default is set to 8MB.
Since we are not using the system yet, I am going to set the trigger interval to 15 min. NOTE: to easily locate custom or manual changes within the configuration - locate the gray diamond:
Hopefully, this will lower the percentage.