| Previous | Next |
| EXFAT_FILE_SYSTEM | INVALID_MDL_RANGE |
VOLSNAP_OVERLAPPED_TABLE_ACCESS
The VOLSNAP_OVERLAPPED_TABLE_ACCESS bug check has a value of 0x0000012D. This indicates that volsnap tried to access a common table from two different threads which may result in table corruption and eventually corrupt the table.
Important
This topic is for programmers. If you are a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.
VOLSNAP_OVERLAPPED_TABLE_ACCESS Parameters
None
Dump evidence for VOLSNAP_OVERLAPPED_TABLE_ACCESS
For VOLSNAP_OVERLAPPED_TABLE_ACCESS, 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 “VOLSNAP_OVERLAPPED_TABLE_ACCESS”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.
Analysis order for VOLSNAP_OVERLAPPED_TABLE_ACCESS
- Run WinDbg
!analyze -v, then inspect the documented meaning of each VOLSNAP_OVERLAPPED_TABLE_ACCESS parameter instead of relying only on the probably-caused-by line. - Find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with volsnap / overlapped / table / access.
- For VOLSNAP_OVERLAPPED_TABLE_ACCESS, 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 VOLSNAP_OVERLAPPED_TABLE_ACCESS before collecting the dump and event logs. For VOLSNAP_OVERLAPPED_TABLE_ACCESS, 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.