I am experiencing BlueScreens for the component FirePM.sys multiple times a day.
Here is the information corporate support staff has extracted from the Windows minidumps.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005
I am using Host Intrusion Prevention 22.214.171.1240 (en_US) as part of our corporate policy.
Can you assist me with a solution to retain a workable Desktop ?
Some reports were that Microsoft was blaming this on the TDSS Rootkit and atapi.sys and its interaction with MS10-015...........
Don't know if they have backed off of that and the TDSS detection seems complicated. If you can get a system back up and you can pull the HD out and use a USB to IDE connector to scan it, you might be able to see if its infected.
You might also be able to check some registry stuff.........