This stop message indicates that an attempt was made to complete an IRP (I/O request packet) more than once, possibly by more than one driver. The problem is most likely caused by faulty drivers. This is a tough bug to find because the simplest case, namely a driver that attempted to complete its own packet twice — is usually not the source of the problem. More likely, two separate drivers each believe that they own the packet, and each has attempted to complete it. The first request succeeds, and the second fails, resulting in this bug check. Tracking down which drivers in the system caused the error is difficult, because the trail of the first driver has been covered by the second.
Update to the latest drivers and firmware available for your hardware. Keep your applications and OS up to date with the latest patches. Microsoft states that using updated software is especially important for backup programs, multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.
M244617 provides information on how to use the Driver Verifier to troubleshoot Windows Drivers.
Performing a clean boot might also be helpful in troubleshooting this problem. See M281770, M310353, and M316434 for information on performing a clean boot.
See the links below for additional information on this problem.
Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net.
Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.