You can configure the desired logging level by calling the micras tool with the desired logging level number specified after -loglevel. You can check the documentation for the micras tool and the available options in the Intel® Manycore Platform Software Stack (Intel® MPSS) for Windows
In my previous post, I haven't included the link to the documentation for the Intel® Manycore Platform Software Stack (Intel® MPSS) for Windows
You can check the available options in the documentation referenced in the link.
Just in case the version changes, the accurate link in which you will find the latest available documentation for download is the following: https://software.intel.com/en-us/articles/intel-manycore-platform-software-stack-mpss
thank you for your quick reply.
We are not currently running micras as we have our own monitoring system in place. I will look into getting micras started as a service so we can review its log should the error occur again.
That said, our monitoring never reported any errors while the windows event log was swamped with driver errors and I know that the application we run on the coprocessors was working as intended. I am not familiar with the kind of events micras can capture, but with what the MPSS user guide hints at, it should basically do the same as our custom monitoring solution.
So, to sum it up: The coprocessors were doing what they were intended to do and were able to communicate with the host via the virtual network adapters, but the windows driver logged a massive number of messages to the system event log.