|
|
 |
|
|
|
|
|
|
Description |
|
|
|
|
|
Unable to access the boot drive or partition. This is a fatal Windows error, typically called a Stop message, Bug Check, or more commonly the Blue Screen of Death (BSoD). The system is in a forced reboot state. Any unsaved work is likely lost.
|
|
|
|
|
|
Sample Screen |
|
|
|
|
|
A problem has been detected and Windows has been shut down to prevent damage to your computer.
UNMOUNTABLE_BOOT_VOLUME If this is the first time you've seen this Stop error screen, restart your computer. If this screen appears again, follow these steps:
Check to make sure any new hardware or software is properly installed. If this is a new installation, ask your hardware or software manufacturer for any Windows updates you might need.
If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadowing. If you need to use Safe Mode to remove or disable components, restart your computer, press F8 to select Advanced Startup Options, and then select Safe Mode.
Technical Information:
*** STOP: 0x000000ED
Beginning dump of physical memory
Physical memory dump complete.
Contact your system administrator or technical support group for further
assistance. |
|
|
|
Text may appear differently depending on where the error occurs.
Additional technical information (hex values) specific to a machine are not shown. |
|
|
|
|
|
Key Facts |
|
|
|
|
|
Full Title |
|
UNMOUNTABLE_BOOT_VOLUME
|
Stop Code |
|
0x000000ED
|
Type |
|
Fatal
|
|
Windows |
|
XP, Vista, 2008, 7, 8
|
Vendor |
|
Microsoft Corporation |
|
|
|
|
|
|
Solutions and Fixes |
|
|
|
|
|
Fix Cable or UDMA Configuration |
|
|
Check if your IDE cable is the wrong type. Most IDE drives today use Ultra-DMA that requires a 40-pin 80-wire cable. If you use an older style 40-wire cable, this problem can occur.
If your are using a old hard drive, the cable may not be the issue, but you might have turned on UDMA in the BIOS when the drive does not support UDMA. |
|
|
|
FaultWire Staff
Posted: 2-Sep-2009 |
|
|
Fix Corrupted File System |
|
|
Check if the 2nd parameter has the value 0xC0000032. This indicates the file system is corrupt and must be repaired. Use the recovery console and run checkdsk /r to repare the damaged file system. Check other solutions here to correct the cause of the file corruption (Microsoft article 297185). |
|
|
|
FaultWire Staff
Posted: 2-Sep-2009 |
|
|
|
Microsoft has identified a problem with the OSes listed below that require updating to the current service pack to fix this issue: In Windows XP pre-SP3 with NTFS volumes on IDE drives with caching enabled, this problem can occur. You will need to first fix the damaged volume by using the recovery console and running checkdsk /r to repair the damaged file system. Next install the current XP service pack (Microsoft article 315403). |
|
|
|
FaultWire Staff
Posted: 5-Oct-2008 |
|
|
|
The system file LSASS.EXE (Local Security Authentication Server) is missing or corrupt. Try replacing this file. LSASS is responsible for validating the user logon. |
|
|
|
FaultWire Staff
Posted: 2-Sep-2009 |
|
|
|
Install the latest Windows software updates. Don't forget to check for non-critical updates too!
To manually get updates, open Internet Explorer (you can't use a non-Microsoft browser for updates).
For IE 8 and later: Click on Safety, then Windows Update. Follow the instructions.

For IE 7 and older: Click on Tools, then Windows Update. Follow the instructions.

|
|
|
|
FaultWire Staff
Posted: 5-Oct-2008 |
|
|
Also see our list of common Fatal Error Solutions. |
|
|
|
|
|
Forum Help |
|
|
|
|
|
 |
Check out what others say about this issue and review or add your own comments and solutions!
Go to Forums on topic. |
|
|
|
|
|
|
Technical Details |
|
|
|
|
|
|
 The I/O subsystem attempted to mount the boot volume and it failed.
After the Stop code will be 4 hex values: {Parameter 1, Parameter 2, Parameter 3, Parameter 4}.
Parameter 1 specifies the device object of the boot volume.
Parameter 2 specifies the status code from the file system that describes why it failed to mount the volume.
Parameter 3 is not defined.
Parameter 4 is not defined.
|
|
|
|
|
|
|
Vendor Summary |
|
|
|
|
|
|
|
|
|
|
|
|
While BSoD fatal stop errors are identified by Microsoft Windows, they are often caused by
non-Microsoft applications, drivers and hardware issues. |
|
|
|
|
|
Research this Issue |
|
|
|
|
|
Getting search results...
|
|
|
|
|
|
Notes |
|
|
|
|
|
While we believe this information up to date and accurate, FAQware is not responsible for any inaccuracies. If you find something that is out of date or inaccurate, please let us know at
so we can correct it. |
|
|
|
|
|
|
 |
 |
 |
| | |
|
|