Device Freezes: Phone, Computer Keeps Freezing (Stop 0x000000ED)

When your computer crashes and you see one of the following stop codes: Stop 0x000000ED (UNMOUNTABLE_BOOT_VOLUME) or Stop 0x0000007B (INACCESSIBLE_BOOT_DEVICE) the NTOSKRNL is confused. Either it cannot find the rest of itself, or it cannot read the file system at the location it believes it is stored.

When troubleshooting this error, your task is to find out why the Windows kernel is confused and fix the cause of the confusion. File system corruption might be the problem.

Insert the Windows installation disc. Launch the recovery console from the Windows installation disc and run the chkdsk /f /r command. It will detect if the File system is corrupted. If it is corrupted, run the Repair Windows option, which will replace the corrupted files with the original ones from the disk.

Note: if Windows doesn't boot, you can access the Windows installation disk by pressing F12 (F2 or F8), immediately after you restart or turn on the computer.

When your computer crashes and you see one of the following stop codes: Stop 0x000000ED (UNMOUNTABLE_BOOT_VOLUME) or Stop 0x0000007B (INACCESSIBLE_BOOT_DEVICE) the NTOSKRNL is confused. Either it cannot find the rest of itself, or it cannot read the file system at the location it believes it is stored.

Try reseating the data cables that connect the hard drive and its controller (on the motherboard) at both ends because improperly or poorly seated cabling means low data transfer and low data transfer means system instability.

If you don't know how, read this useful article.

When your computer crashes and you see one of the following stop codes: Stop 0x000000ED (UNMOUNTABLE_BOOT_VOLUME) or Stop 0x0000007B (INACCESSIBLE_BOOT_DEVICE) the NTOSKRNL is confused. Either it cannot find the rest of itself, or it cannot read the system file at the location it believes it is stored.

When troubleshooting this error, your task is to find out why the Windows kernel is confused and fix the cause of the confusion.

Check The SATA controller configuration in BIOS. If the SATA controller gets toggled from ATA to AHCI mode (or vice versa), then Windows will not be able to talk to the SATA controller because the different modes require different drivers. 

Try toggling the SATA controller mode in the BIOS:

Restart (or turn on the computer) and press DEL(ETE) or F12 before the Windows Logo appears. Once the BIOS interface appears find Integrated Peripherals, press ENTER and find (PCH) Sata Control mode (or Main -> Sata Mode). Choose between IDE and AHCI combination. If one doesn't work, the other will. Save the changes by  pressing F10 (which stands for Save and exit). 

DO NOT MODIFY BIOS ON YOUR OWN, UNLESS YOU KNOW WHAT YOU ARE DOING.

Note: You can reset the BIOS, either by carefully removing the battery on the motherboard or in the BIOS menu by pressing Setup defaults; Fail-safe defaults or Optimized defaults (F9 or F6 or F7).

When your computer crashes and you see one of the following lines: Stop 0x000000ED (UNMOUNTABLE_BOOT_VOLUME) or Stop 0x0000007B (INACCESSIBLE_BOOT_DEVICE) the NTOSKRNL is confused. Either it cannot find the rest of itself, or it cannot read the file system at the location it believes it is stored.

When troubleshooting this error, your task is to find out why Kernel is confused and fix the issue.

This error might be an outcome of your unsuccessful experiment with the RAID controller settings.

Try changing the RAID settings back to Autodetect (Usually Dell computers/laptops have this option). To do that, restart (or turn on the computer) and press DEL(ETE) or F12 before the Windows Logo appears to access the BIOS menu. Once it opens, highlight Drivers list and then SATA operation. Select RAID Autodetect (/ATA) and apply the changes (restart the computer).

Note: DO NOT MODIFY BIOS ON YOUR OWN, UNLESS YOU KNOW WHAT YOU ARE DOING, because you may cause additional problems.