How to Fix Windows Stop Code 0x00000072: ASSIGN_DRIVE_LETTERS_FAILED
Quick Answer ASSIGN_DRIVE_LETTERS_FAILED (0x00000072) is a Windows bug check associated with a failure during drive-letter assignment. Microsoft describes th...
Quick Answer
ASSIGN_DRIVE_LETTERS_FAILED (0x00000072) is a Windows bug check associated with a failure during drive-letter assignment. Microsoft describes this bug check as very infrequent. The stop code alone does not identify the underlying cause or prove that a disk has failed.
Start by recording when the crash occurs and checking whether Windows can boot. If the error occurs during startup or Windows installation, investigate recovery options, storage-device detection, recent driver or hardware changes, and relevant diagnostic logs. Avoid changing partitions or drive letters until the affected volume and the cause have been identified.
What Does Error 0x00000072 Mean?
Windows uses bug check codes when it encounters a condition that requires the operating system to stop. The code 0x00000072 is named ASSIGN_DRIVE_LETTERS_FAILED.
Drive letters such as C: and D: identify volumes in Windows. The operating system must be able to identify and access the appropriate volumes during startup and other system operations.
Microsoft's public documentation identifies the bug check but does not provide a universal end-user repair procedure. Troubleshooting should therefore be based on when the crash happens and what the system logs or hardware checks reveal.
Official reference: Microsoft Learn: Bug Check 0x72 — ASSIGN_DRIVE_LETTERS_FAILED.
Common Symptoms
- A blue screen displays the stop code
0x00000072. - Windows restarts unexpectedly or repeatedly fails during startup.
- The error appears while installing, upgrading, or recovering Windows.
- The computer starts successfully after a restart but crashes again later.
- The system has other storage-related symptoms, such as a missing volume or inconsistent drive detection.
These symptoms are not exclusive to this bug check. Record the exact message and the operation being performed when the failure occurs.
Possible Causes
The following are areas to investigate, not confirmed causes of every occurrence of this stop code.
- Storage configuration: Windows may be encountering a problem while identifying or accessing volumes.
- Driver changes: A recently installed or updated storage-controller or chipset driver may be relevant.
- Hardware or connection problems: An SSD, hard drive, controller, cable, or connection may be malfunctioning.
- Recent disk changes: A disk migration, partition modification, or hardware replacement may provide useful clues.
- Windows installation or recovery failure: Setup logs may identify a specific operation that failed before the crash.
Do not assume that a drive-letter conflict, damaged partition, or faulty disk is responsible without supporting evidence.
Before You Begin
- Write down the complete stop code and any additional blue-screen message.
- Determine whether the error occurs during normal startup, after sign-in, during Windows Setup, or when using recovery media.
- If Windows still starts, back up important files before attempting repairs.
- Identify the relevant disk and volumes before using storage-management tools.
How to Fix ASSIGN_DRIVE_LETTERS_FAILED
1. Restart Windows and Disconnect Nonessential Devices
If the error occurred once, restart the computer normally if possible.
- Disconnect nonessential USB storage devices, hubs, docks, and other peripherals.
- Leave the keyboard, mouse, display, and devices required to operate the computer connected.
- Restart Windows and check whether the error returns.
- If Windows starts, back up important files and review any recent system changes.
If the computer repeatedly crashes before Windows starts, proceed to Windows Recovery Environment instead of repeatedly forcing restarts.
2. Run Startup Repair if Windows Cannot Boot
Windows Recovery Environment (Windows RE) includes recovery tools for certain startup problems.
- Allow Windows to enter automatic recovery if it appears after a startup failure.
- If necessary, start from official Windows installation or recovery media appropriate for your system.
- Select Repair your computer when that option is available.
- Open Troubleshoot and then Advanced options.
- Select Startup Repair, if available, and follow the instructions.
- Restart the computer and check whether Windows boots normally.
Startup Repair may resolve certain startup problems, but it is not a guaranteed fix for this specific bug check.
For further guidance, consult Microsoft's Windows recovery options.
3. Check Recent Driver and Hardware Changes
If the error started after installing hardware or updating a driver, investigate that change first.
- Identify any recently replaced storage devices or other hardware.
- Check whether a storage-controller or chipset driver was updated shortly before the first crash.
- If Windows starts, open Device Manager and inspect relevant disk-drive and storage-controller entries.
- Obtain appropriate drivers from Windows Update or the computer or component manufacturer's official website.
- If evidence points to a recently updated driver, use the supported driver rollback procedure when available.
Avoid removing storage-controller drivers indiscriminately. Windows may depend on them to access the system disk, and removing a required driver can prevent startup.
4. Check Whether the Storage Device Is Detected
If the computer fails during startup or Windows installation, determine whether the intended storage device is detected consistently.
- Check whether the SSD or hard drive appears in the computer's firmware storage information, if available.
- Investigate intermittent detection, disk errors, or unusual drive noises.
- If you suspect a physical connection problem, follow the manufacturer's service instructions or contact a qualified technician.
- Do not randomly switch SATA, RAID, AHCI, or other storage-controller settings. A configuration change can make an existing Windows installation unbootable.
If the storage device is missing or may be failing, address that issue before attempting Windows reinstallation or partition repairs.
5. Review Windows Setup Logs
If the error occurs during Windows installation or upgrade, examine the available setup logs. These can provide evidence about the operation that failed before the crash.
Depending on the setup phase, logs may be present in locations such as:
C:\$WINDOWS.~BT\Sources\Panther\setupact.logC:\$WINDOWS.~BT\Sources\Panther\setuperr.logC:\Windows\Panther\setupact.logC:\Windows\Panther\setuperr.log
Not every file will exist on every system. In recovery environments, the installed Windows volume may also have a different drive letter from the one used during normal operation.
- Locate the relevant log files for the failed installation or upgrade.
- Open them in a text editor.
- Look for error entries around the time of the failure.
- Compare the surrounding messages in
setupact.logandsetuperr.log, where available. - Use any specific error codes or component names to guide further troubleshooting.
Refer to Microsoft's documentation on Windows upgrade log files and Windows Setup log files and event logs.
6. Examine Crash Dumps if Windows Starts
If Windows restarts successfully after the blue screen, a crash dump may help an IT technician identify the failing component.
Common dump locations include:
C:\Windows\MinidumpC:\Windows\MEMORY.DMP
These files may not exist if dump collection was not configured or the system could not write a dump. When a dump is available, it can be analyzed using Microsoft's Windows debugging tools.
See the official Windows debugging documentation.
Advanced Troubleshooting
Repair Windows System Files
If Windows starts and there is evidence of system-file corruption, use the built-in DISM and System File Checker tools.
Open Command Prompt or Windows Terminal as an administrator and run these commands separately, in order:
DISM.exe /Online /Cleanup-Image /RestoreHealthsfc /scannowDISM attempts to repair the online Windows image. SFC scans protected system files and attempts to repair corrupted files.
These commands are not specific fixes for stop code 0x00000072. They may help when Windows component corruption is involved, but they will not necessarily resolve a hardware or storage-driver problem.
If Windows cannot boot, do not run the commands unchanged in a recovery command prompt. The /Online option targets the currently running Windows environment, which may be the recovery environment rather than the installed operating system. Offline repairs require identifying the correct Windows installation and using the appropriate syntax.
Consider System Restore
If the problem began after a recent system change and a suitable restore point exists, System Restore may help return Windows system settings and installed software to an earlier state.
- Open Windows Recovery Environment.
- Select Troubleshoot and then Advanced options.
- Select System Restore, if available.
- Review the available restore points and follow the instructions.
System Restore does not guarantee recovery from hardware faults and is not a substitute for backing up important files.
How to Verify the Fix
- Restart Windows and confirm that it reaches the sign-in screen or desktop.
- Repeat the activity that originally triggered the crash, if it is safe to do so.
- Confirm that expected disks and volumes are accessible.
- Check Device Manager for relevant storage-device or controller errors.
- If the failure occurred during installation, verify that Setup completes and review its logs if the error persists.
- Back up important files after recovering the system.
When to Seek Professional Assistance
Contact a qualified technician or the computer manufacturer if the computer repeatedly crashes before Windows starts, the storage device is not consistently detected, or the error persists after basic troubleshooting.
If a disk may be physically failing and contains important data, avoid repeated repair attempts, formatting, or operating-system reinstallation until the data has been protected or recovered.
Frequently Asked Questions
Does error 0x00000072 mean the hard drive has failed?
No. The stop code alone does not prove physical disk failure. Investigate hardware detection, recent changes, and available diagnostic evidence before deciding that a drive needs replacement.
Can assigning a different drive letter fix this error?
Not necessarily. A blue-screen bug check is not the same as an ordinary Disk Management drive-letter issue. Change a drive letter only when a specific volume problem has been identified and the consequences are understood.
What if Windows cannot start at all?
Use Windows Recovery Environment and try Startup Repair if available. If the system continues to crash, check storage-device detection and obtain professional assistance when necessary.
Should I reinstall Windows?
Reinstallation should not be the first troubleshooting step. It may not resolve a hardware or driver problem and can result in data loss. Identify the likely cause and back up important data before considering reinstallation.
Where is the official documentation for this stop code?
Microsoft provides the technical description in its Bug Check 0x72 reference. Additional Windows recovery, setup-log, and debugging documentation can help investigate the circumstances surrounding the crash.
Sources
Was this guide useful?
Your answer helps us keep BISONKB accurate and practical.