Windows Stop Code SCSI_DISK_DRIVER_INTERNAL (0x0000002D): Meaning and Troubleshooting
Quick Answer SCSI_DISK_DRIVER_INTERNAL is Windows bug check 0x0000002D. Microsoft says it appears very infrequently and recommends WinDbg’s !analyze extensio...
Quick Answer
SCSI_DISK_DRIVER_INTERNAL is Windows bug check 0x0000002D. Microsoft says it appears very infrequently and recommends WinDbg’s !analyze extension to help determine the root cause. Its dedicated page does not define the four parameters, explain a specific failure mechanism, or prescribe a universal repair. Microsoft Learn
The name points toward a storage-driver investigation, but it does not prove that a physical disk has failed or that the computer contains an older physical SCSI drive. For a real crash, preserve the dump, inspect the stack, and correlate the result with storage events and the system’s actual device configuration.
What Does the SCSI Wording Tell You?
SCSI is a set of storage command and device concepts used in Windows storage-driver architecture. A stop-code name containing SCSI_DISK_DRIVER suggests that storage code is relevant, but Microsoft’s 0x2D entry does not say which driver, controller, disk, or command was involved. Microsoft Learn
Do not infer a hardware fault from the name alone. A storage path can involve multiple layers, and a driver visible at the time of a crash may have encountered a problem introduced earlier. The dump is needed to identify the actual path.
Stop Code at a Glance
| Field | Documented information |
|---|---|
| Bug-check value | 0x0000002D |
| Symbolic name | SCSI_DISK_DRIVER_INTERNAL |
| Frequency | Microsoft says it appears very infrequently. |
| Parameter definitions | Not provided on the dedicated page. |
| Specific cause or fix | Not provided on the dedicated page. |
| Recommended debugger step | Use !analyze to help determine the cause. |
What Should You Investigate?
For an actual 0x2D dump, reasonable areas to examine include:
- The storage drivers and device path shown on the call stack.
- Errors logged by the storage controller or device near the crash.
- A recently changed storage driver or firmware version.
- Whether the crash repeats during the same read, write, startup, or shutdown operation.
- Whether manufacturer diagnostics report a problem with a specific device.
These are case-investigation directions, not Microsoft’s published list of causes for bug check 0x2D. The official page does not attribute every occurrence to a disk, cable, controller, or driver defect. Microsoft Learn
Step-by-Step: Investigate an Actual Crash
1. Confirm the complete stop code
Verify 0x0000002D from the original blue-screen record or memory dump. Similar-looking values and arguments belonging to other bug checks must not be confused with this stop code.
If the entry came from a Windows stop-code list, it is a reference item rather than evidence that a particular computer has failed.
2. Protect important data if storage errors are present
If the computer is also reporting repeated read errors, disappearing drives, or manufacturer diagnostic failures, preserve important data before making disruptive changes or running intensive tests. Those additional symptoms are the reason to prioritize data protection; the 0x2D label alone does not establish disk failure.
3. Preserve and analyse the crash dump
Open the dump in WinDbg:
!analyze -vRecord the four arguments, call stack, Windows build, and any module named by the analysis. Microsoft recommends !analyze for 0x2D. Because it publishes no 0x2D parameter table, do not assume a particular argument is a device object, disk address, status code, or SCSI request. Microsoft Learn
4. Inspect the call stack
Display a detailed stack:
kvIdentify the driver layers active when Windows stopped. Determine whether the stack contains a relevant storage request and whether the same component appears across repeated crashes. A driver name on the stack is a lead, not automatic proof that it originated the error.
5. Check Event Viewer and hardware diagnostics
Review Event Viewer → Windows Logs → System around the time of each crash for controller, disk, or driver errors. If the events point to a particular device, run diagnostics supported by its manufacturer. Compare those results with the dump before deciding whether the repair concerns a driver, controller, drive, or another component.
6. Apply the supported action
If repeated dumps and logs point to a third-party storage driver, check its vendor for a supported update or rollback. If hardware diagnostics identify a failing device, follow the manufacturer’s replacement and data-recovery guidance. If neither identifies a cause, provide the dump and system configuration to a specialist.
Guidance for Driver Developers
If you maintain a driver in the affected stack, inspect the request and completion path shown by the dump. Review its error handling, timeouts, object lifetime, and interactions with adjacent driver layers as the specific trace warrants.
Microsoft’s dedicated 0x2D page does not define which internal invariant failed. Do not build a diagnosis around an invented meaning for Arg1–Arg4. First establish the request and driver context from symbols, stack, and available dump data. Microsoft Learn
What Not to Assume
| Assumption | What the evidence actually supports |
|---|---|
| “My SSD must be dead.” | The code alone does not establish a device failure. |
| “This can happen only with a physical SCSI disk.” | The symbolic name does not describe the machine’s exact hardware. |
| “The first storage driver named by WinDbg is definitely faulty.” | Inspect the full stack and other evidence. |
| “CHKDSK is the specific 0x2D fix.” | Microsoft’s dedicated 0x2D page does not prescribe CHKDSK. |
| “Arg1 identifies the disk.” | Microsoft does not define 0x2D’s four parameters. |
Frequently Asked Questions
What is SCSI_DISK_DRIVER_INTERNAL?
It is the symbolic name for Windows bug check 0x0000002D, which Microsoft says appears very infrequently. Microsoft Learn
Does this blue screen mean my disk is physically damaged?
Not necessarily. Check the dump, storage events, and device diagnostics before reaching that conclusion.
Does the name identify a particular SCSI controller?
No. Microsoft’s 0x2D reference does not identify a controller or driver. Microsoft Learn
What do the four parameters mean?
Microsoft’s dedicated 0x2D page does not define them. Preserve their values without applying descriptions from another stop code. Microsoft Learn
Is 0x2D the same as PORT_DRIVER_INTERNAL?
No. PORT_DRIVER_INTERNAL is 0x2C; SCSI_DISK_DRIVER_INTERNAL is 0x2D. They are distinct entries. Microsoft Learn
Which WinDbg command should I run first?
Run !analyze -v, then inspect the stack and involved modules. Microsoft recommends !analyze for this code. Microsoft Learn
Summary
SCSI_DISK_DRIVER_INTERNAL (0x0000002D) is a very rare Windows bug check with limited official diagnostic detail. It suggests investigating the storage-driver path, but it does not identify a failed disk, controller, or parameter meaning. Use the dump, stack, storage events, and device diagnostics to establish the cause before choosing a fix. Microsoft Learn
Sources
Was this guide useful?
Your answer helps us keep BISONKB accurate and practical.