| Previous | Next |
| IRQL_GT_ZERO_AT_SYSTEM_SERVICE | FATAL_UNHANDLED_HARD_ERROR |
STREAMS_INTERNAL_ERROR
Legacy STREAMS internal error for STREAMS_INTERNAL_ERROR
STREAMS_INTERNAL_ERROR is bug check code 0x0000004B. STREAMS is historical Unix-style stream I/O vocabulary that appears in old Windows bug-check definitions. This code is useful mostly when the dump points at legacy networking, transport, or compatibility components rather than at modern WDF or NDIS paths.
How to read it in a dump
- The stack decides whether any real STREAMS-like compatibility code is involved.
- On modern Windows systems, this name is usually more historical than operational.
- Do not invent a modern protocol meaning without a driver stack that supports it.
What to check
- Inspect loaded legacy transport, emulator, compatibility, or file-system/network filter drivers.
- If no matching component appears in the stack, treat the name as a historical bucket and focus on the crashing module.
- Compare with XNS_INTERNAL_ERROR and LM_SERVER_INTERNAL_ERROR for old networking-era codes.
References
Dump evidence
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 “this result”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.
Analysis order
- Run WinDbg
!analyze -v, then inspect the documented meaning of each 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 streams / internal.
- 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 this result before collecting the dump and event logs. 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.