| Previous | Next |
| OFS_FILE_SYSTEM | SETUP_FAILURE |
RECOM_DRIVER
Legacy RECOM driver failure for RECOM_DRIVER
RECOM_DRIVER is bug check code 0x00000084. This bug check name is a historical driver bucket. It is useful only when the dump stack or loaded-module list identifies the specific driver path that raised it; the name alone does not identify a modern Windows subsystem.
How to read it in a dump for RECOM_DRIVER
- Arguments and symbolic name are secondary to the crashing module and stack.
- Treat it as a driver-originated stop unless the dump shows a more specific subsystem.
- Avoid writing a root cause from the constant name alone.
What to check for RECOM_DRIVER
- Start with !analyze -v and lmvm for the suspect module.
- Check whether an old or vendor-specific driver is loaded.
- Use Driver Verifier if a reproducible driver path is identified.
References for RECOM_DRIVER
- Microsoft Driver Verifier documentation
- Microsoft Bug Check Code Reference
- Crash dump files and WinDbg
Dump evidence for RECOM_DRIVER
For RECOM_DRIVER, preserve the complete dump, the four bug-check parameters, the exact Windows build, loaded-module list, and the event timeline immediately before the stop. AllStat summarizes the condition as “RECOM_DRIVER”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.
Analysis order for RECOM_DRIVER
- Run WinDbg
!analyze -v, then inspect the documented meaning of each RECOM_DRIVER parameter instead of relying only on the probably-caused-by line. - For RECOM_DRIVER, find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with recom / driver.
- For RECOM_DRIVER, keep third-party filter, security, storage, graphics, and virtualization drivers in the module inventory; removing evidence before dump analysis can obscure the responsible path.
Do not repeatedly reboot a machine affected by RECOM_DRIVER before collecting the dump and event logs. For RECOM_DRIVER, recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.
Dump evidence for RECOM_DRIVER
For RECOM_DRIVER, preserve the complete dump, the four bug-check parameters, the exact Windows build, loaded-module list, and the event timeline immediately before the stop. AllStat summarizes the condition as “RECOM_DRIVER”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.
Analysis order for RECOM_DRIVER
- Run WinDbg
!analyze -v, then inspect the documented meaning of each RECOM_DRIVER parameter instead of relying only on the probably-caused-by line. - For RECOM_DRIVER, find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with recom / driver.
- For RECOM_DRIVER, keep third-party filter, security, storage, graphics, and virtualization drivers in the module inventory; removing evidence before dump analysis can obscure the responsible path.
Do not repeatedly reboot a machine affected by RECOM_DRIVER before collecting the dump and event logs. For RECOM_DRIVER, recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.
Looking for a different code? Search another status or error code.