I've never really found a reason to use !irpfind, however, it would be useful for situations where you wanted to see which IRP stacks a driver may be part of.
You don't need to worry about IRPs with Stop 0xA, Stop 0xD1 and Stop 0x50. With those bugchecks, you'll what to check which instruction caused the error and investigate why that memory address is invalid. Typically, the driver may be referencing an invalid pointer or referenced an address which resides in paged pool. Paged pool can't be accessed at IRQL Level 2 or above.
