This same file is causing my new HP Proliant ML350g8 to crash(BSOD) when booting with a Disaster recovery boot CD (using CA Arcserve)
The HP server support tech said this file is not an HP file........ but a Microsoft file..
I have seen other stuff out on the net that says this file is a Micorosft signed and date stamped file what ever that means
In any event it looks like I will not be able to get through this Diaster Recovery simulation until I can get this file/driver out of the mix