I seriously feel like ripping my hair out right now.
It started about 2 days ago. My PC was working fine the night before, and I shut it down like usual. When I returned to my PC, the boot up process would hang on the "Starting Windows" screen with the glowing Windows logo. After about what seemed like 1 to 2 minutes, a BSOD flashed for less than a second, and the system rebooted to a option for start up repair. I then disabled rebooting upon system failure, and I received the following BSOD message:
"A problem has 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 of 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 Start up Options, and then select Safe Mode.
Technical Information:
*** STOP: 0x000000ED (0xFFFFFA800D3F8CD0, 0XFFFFFFFFC0000185, 0X0000000000000000, 0X0000000000000000)"
After seeing this, I tried to boot into start up repair as was reccomended. After selecting it and loading, the startup repair hung on a black screen without a cursor for around 7 minutes. After 7 minutes, the cursor as well as the default Windows 7 startup repair background loaded. After waiting for about 4 hours, the UI had still not appeared, and I shut down the system. I then inserted my Windows 7 install USB, and booted to it. However, unlike the start up repair, the background or cursor did not manage to load in. The screen would hang on a simple black screen for hours on end. I created a bootable USB to boot into Hiren's BootCD. There, I ran Windows Mini XP but unfortunately the usb mouse and keyboard did not work, nor did a PS2 keyboard. I tried to boot into start up repair around 9 times after that because I was desperate, but for some reason the ninth retry ended up working after a while. Although I booted into the start up repair, my OS was not detected, and I did not know which drivers to load. Because of this, I could not restore my PC to a previous restore point. Instead, I used the CMD to mark the system partition as active, but it was of no use because I had already entered the recovery tools UI. One thing I noticed was that the entire UI took ages to load, and even the CMD was extremely slow when using DISKPART commands. I restarted my PC and attempted to launch start up repair again, but no matter how many times I tried I could no longer access it. After seeing that would not work, I tried my Live Linux USB with ubuntu 14.10 (and 15.04). Before starting the Live Session, I ran the hard drive check and memtest. Neither reported any issues. Once the session had launched, I went into the file browser and could see "1.0 TB Volume". When I clicked to open it, after about one minute of waiting an error message popped up stating it could not mount (Just like the BSOD's error). The error read:
"Unable to access "1.0 TB Volume"
Error mounting /dev/sda2 at /media/it/A8848D76848D4830: Command-line 'mount -t "ntfs" -o
"uhelper=udisks2,nodev,nosuid,uid=999,gid=999" "/dev/sda2" "/media/it/A8848D76848D4830"' exited with non-zero exit status 13: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Failed to read NTFS $Bitmap: Input/output error
NTFS is either inconsistent, or there is a hardware fault, or it's a SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows
then reboot into Windows twice. The usage of the /f parameter is very important! If the device is a SoftRAID/FakeRAID then first activate it and mount a different device under the /dev/mapper/ directory, (e.g. /dev/mapper/nvidia_eahaabcc1). Please see 'dmraid' documentation
for more details."
There was another volume labeled "105MB Volume", which I assume to be the system partition. Unlike the 1.0 TB Volume, I could access the files with this volume. Inside I found;
1. Boot (folder)
5. BOOTSECT.BAK
I'm not sure what to do with any of these files or logs. Other things I tried included booting from last known good configuration which resulted in the BSOD, and booting into safe mode which hung on CLASSPNP.sys for a while and then rebooted the PC. I have no idea what to do anymore as I have tried everything within my knowledge. Any other thread about this issue that I have seen has slight variations to my error, and mine seems unique. I would greatly appreciate any help!
It started about 2 days ago. My PC was working fine the night before, and I shut it down like usual. When I returned to my PC, the boot up process would hang on the "Starting Windows" screen with the glowing Windows logo. After about what seemed like 1 to 2 minutes, a BSOD flashed for less than a second, and the system rebooted to a option for start up repair. I then disabled rebooting upon system failure, and I received the following BSOD message:
"A problem has 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 of 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 Start up Options, and then select Safe Mode.
Technical Information:
*** STOP: 0x000000ED (0xFFFFFA800D3F8CD0, 0XFFFFFFFFC0000185, 0X0000000000000000, 0X0000000000000000)"
After seeing this, I tried to boot into start up repair as was reccomended. After selecting it and loading, the startup repair hung on a black screen without a cursor for around 7 minutes. After 7 minutes, the cursor as well as the default Windows 7 startup repair background loaded. After waiting for about 4 hours, the UI had still not appeared, and I shut down the system. I then inserted my Windows 7 install USB, and booted to it. However, unlike the start up repair, the background or cursor did not manage to load in. The screen would hang on a simple black screen for hours on end. I created a bootable USB to boot into Hiren's BootCD. There, I ran Windows Mini XP but unfortunately the usb mouse and keyboard did not work, nor did a PS2 keyboard. I tried to boot into start up repair around 9 times after that because I was desperate, but for some reason the ninth retry ended up working after a while. Although I booted into the start up repair, my OS was not detected, and I did not know which drivers to load. Because of this, I could not restore my PC to a previous restore point. Instead, I used the CMD to mark the system partition as active, but it was of no use because I had already entered the recovery tools UI. One thing I noticed was that the entire UI took ages to load, and even the CMD was extremely slow when using DISKPART commands. I restarted my PC and attempted to launch start up repair again, but no matter how many times I tried I could no longer access it. After seeing that would not work, I tried my Live Linux USB with ubuntu 14.10 (and 15.04). Before starting the Live Session, I ran the hard drive check and memtest. Neither reported any issues. Once the session had launched, I went into the file browser and could see "1.0 TB Volume". When I clicked to open it, after about one minute of waiting an error message popped up stating it could not mount (Just like the BSOD's error). The error read:
"Unable to access "1.0 TB Volume"
Error mounting /dev/sda2 at /media/it/A8848D76848D4830: Command-line 'mount -t "ntfs" -o
"uhelper=udisks2,nodev,nosuid,uid=999,gid=999" "/dev/sda2" "/media/it/A8848D76848D4830"' exited with non-zero exit status 13: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Failed to read NTFS $Bitmap: Input/output error
NTFS is either inconsistent, or there is a hardware fault, or it's a SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows
then reboot into Windows twice. The usage of the /f parameter is very important! If the device is a SoftRAID/FakeRAID then first activate it and mount a different device under the /dev/mapper/ directory, (e.g. /dev/mapper/nvidia_eahaabcc1). Please see 'dmraid' documentation
for more details."
There was another volume labeled "105MB Volume", which I assume to be the system partition. Unlike the 1.0 TB Volume, I could access the files with this volume. Inside I found;
1. Boot (folder)
- A ton of folders labeled with different languages (ex. en-US)
- BCD
- BCD.Backup.0001
- BCD.LOG
- BCD.LOG1
- BCD.LOG2
- BOOTSTAT.DAT
- memtest.exe
- tracking.log
- bcdinfo.txt
- bootfailure.txt
- disklayout.txt
- SrtTrail.log
- SrtTrail.txt
5. BOOTSECT.BAK
I'm not sure what to do with any of these files or logs. Other things I tried included booting from last known good configuration which resulted in the BSOD, and booting into safe mode which hung on CLASSPNP.sys for a while and then rebooted the PC. I have no idea what to do anymore as I have tried everything within my knowledge. Any other thread about this issue that I have seen has slight variations to my error, and mine seems unique. I would greatly appreciate any help!
My Computer
- Computer type
- PC/Desktop
- Computer Manufacturer/Model Number
- Custom Build
- OS
- Windows 7 Ultimate x64
- CPU
- Intel i7 4770k
- Motherboard
- Asus ROG Maximus VI Hero
- Memory
- 16gb DDR3
- Graphics Card(s)
- Nvidia GTX 770
- Hard Drives
- 1.0 TB WD Black
- Antivirus
- MBAM, Widows Defender
- Browser
- Firefox, Chrome
