What does BSOD 320 (STORAGE_DEVICE_ABNORMALITY_DETECTED) mean?

 
Could be also:
ConstantTypeOS
ERROR_INVALID_CAPWin32 errorWindows
Previous Next
ERRATA_WORKAROUND_UNSUCCESSFUL VIDEO_ENGINE_TIMEOUT_DETECTED

STORAGE_DEVICE_ABNORMALITY_DETECTED

The STORAGE_DEVICE_ABNORMALITY_DETECTED bug check has a value of 0x00000140. This indicates that the storage driver stack encountered rate of responsiveness violations, exceeding the threshold, or other failures to respond.

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.

STORAGE_DEVICE_ABNORMALITY_DETECTED Parameters

None

Dump evidence for STORAGE_DEVICE_ABNORMALITY_DETECTED

For STORAGE_DEVICE_ABNORMALITY_DETECTED, 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 “STORAGE_DEVICE_ABNORMALITY_DETECTED”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.

Analysis order for STORAGE_DEVICE_ABNORMALITY_DETECTED

  • Run WinDbg !analyze -v, then inspect the documented meaning of each STORAGE_DEVICE_ABNORMALITY_DETECTED 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 storage / device / abnormality / detected.
  • For STORAGE_DEVICE_ABNORMALITY_DETECTED, 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 STORAGE_DEVICE_ABNORMALITY_DETECTED before collecting the dump and event logs. For STORAGE_DEVICE_ABNORMALITY_DETECTED, 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.