This is the reply i have received:
Greetings of the day!
I hope you are doing well. Our Development Team has reviewed the Memory Dump File and informed that this issue is due to File Access Manager (famv4.sys) driver denying our request to get an oplock on pre-fsctl path and causing a filter manager to crash.
We have sent the information to Microsoft filter dev and they are looking at it.
In the meantime, the only recommendation for a workaround for the issue:
1. Remove famv4.sys
2. Open a ticket with File Access Manager and ask why do they need to deny oplock requests?
3. Also could you please involve VisionWorks to see what is causing the issue, until we get an update from Microsoft.
Please let me know if you have any concerns related to the above process.
So let me start with the minor concerns I have...
1. This file is not on the system, not that we can see anyway and we have hunted everywhere for it.
2 & 3. This is utter bollocks, there is no VisionWorks software installed on this server, we dont and never have used it, not even a trial and certainly not on this system. If they are sure its this phantom driver that is the issue, then wh yare they involving Microsoft? Thats like me involving nPower as to why my SkyTV bill is so high...
I have asked them about their comments, they just skirt round the issue and replied with the following:
This issue is due to File Access Manager (famv4.sys) driver denying our (SEP)request to get an oplock on pre-fsctl path and causing a filter manager to crash. Engineering team has involved Microsoft to take a look into it as well.
We are not saying that Visionworks is causing the issue. The request to involve Visionworks is that they can take a look into this issue and provide a workaround as the you might not like to uninstall the application.
They really havent a clue, this is a complete joke.