|
Before you get started reading, know that I've since performed a Windows reset install. However the root cause of the issue remains unknown and I want to know what happened as in all my searching I couldn't find anyone with this exact issue where the steps I took to fix things didn't succeed. Since I don't know the root cause I'm worried the issue might recur, so if anyone has any insight I'd really appreciate it. System Specs/OS CPU: i5 4690k (no overclock) Motherboard: ASUS z97 (I think) RAM: 16 GB GPU: AMD RX480 Drives: Samsung 850 EVO 500 GB SSD (PRGM_STRG F:), Samsung 830 250 GB SSD (BOOT C:), Samsung 1 TB HDD (SLOW_STRG G:), Seagate Backup Drive 2 TB (I:) OS: Windows 10 x64 (upgraded from Windows 7 x64) Location USA Have I Googled/Read the FAQ Oh dear god yes. I spent all of last night reading attempted fixes Problem Description The problem started when I loaded XCOM 2 up. Game loaded normally but then suddenly the monitor went blank and all my system fans kicked up to 100%. I've seen this happen before and I believe it's an overheating issue on the GPU (the RX480 is a very temperamental card). To remedy I immediately shut off power to the system and gave it a minute to cool off. Unfortunately when I booted the system back up I was greeted with this screen:  Well poo poo. INACCESSIBLE_BOOT_DEVICE sounds not great. Probably, something got messed up so the Recovery Console should be able to fix it...right? Nope. Attempted Fixes I tried the following in the Recovery Console: -Windows auto-repair -System restore -Recovery console's system/startup repair -Booting into Safe Mode with Networking -Booting into Safe Mode None of them worked. I did get this SrtTrail.txt log when I used the Recovery Console startup repair:  I attempted to Google for any answers about these errors and came up empty. I then figured that this might require some heavier lifting, so I did some reading. I figured whatever was wrong was with the master boot record/boot configuration data. After very carefully reading I found a series of commands that would delete and recreate these...but the cmd window kept insisting that C:\boot\bcr didn't exist. What the hell?   the gently caress?This is why I told you the volume names earlier. Somehow Windows now thought that PRGM_STRG was C: and BOOT was now F:. I have never seen anything like this before. I ran chkdsk on both drives (of course I didn't expect to find anything since they're SSDs) and it confirmed everything was running fine. I still couldn't figure out why this had happened but I figured if I instead targeted F:\boot\bcr I should be good. Oops.  Good job! I made it worse! And I had no recovery media. At this point I went and borrowed my girlfriend's Mac laptop to try and make a recovery USB. But this wouldn't work either. So I seemed right hosed at this point. I had gone from a looping boot into the recovery console to a looping failure to boot at all. On a complete shot in the dark, I tried using my Windows 7 install DVD's Recovery Console and asked it to repair the install. I figured this wouldn't work as I was now on Windows 10 and this was Windows 7, but if this didn't work I was going to have to reformat and reinstall anyway. Well what do you know, it worked and I was now back at the looping INACCESSIBLE_BOOT_DEVICE. I decided to say "screw it" and did a reset install of Windows 10 and that's where I'm at now. I have no idea how the original INACCESSIBLE_BOOT_DEVICE came about, nor do I know of any way I could've fixed it without reinstalling Windows as I tried everything I could think of. Recent Changes This is not a change but something I noticed. I have been doing weekly backups of my entire system using the Windows 7 backup/restore tool, but a few weeks ago the backup failed saying it couldn't make a system image of C:. I didn't think much of it and told the backup assistant to stop trying to make the system image but continue doing everything else. Is it possible this was the canary in the coal mine? If anyone can figure out a solution to this mystery, I'd appreciate it as I'm still scratching my head over it and don't know if the root cause could recur and force me to redo all this again. Relevant links I found while searching for solutions: http://www.tomshardware.com/forum/id-2760985/inaccessible-boot-device-reset.html https://answers.microsoft.com/en-us...b2963f25?auth=1 https://answers.microsoft.com/en-us/windows/forum/windows_8-performance/inaccessible-boot-device/446dfdf5-17a2-4505-9d1f-5415a0c3bc5f?db=5 http://www.thewindowsclub.com/inaccessible-boot-device-error-windows https://www.windowscentral.com/how-fix-update-causing-inaccessible-boot-device-error-windows-10 https://www.drivethelife.com/windows-10/fix-inaccessible-boot-device-on-windows-10.html https://www.easeus.com/resource/fix-windows-automatic-repair-loop.html http://windowsreport.com/windows-10-automatic-repair-couldnt-repair-pc/ https://answers.microsoft.com/en-us...81-8ca0630f8028
|
#
?
Jan 17, 2018 17:25
|
|
|
|
| # ? Apr 24, 2024 23:39 |
|
|
I'd run the standard zip edition of CrystalDiskInfo 7.5.1 to make sure those HDs are healthy: https://crystalmark.info/download/index-e.html
|
|
#
?
Jan 17, 2018 23:25
|
|
|
Zogo posted:I'd run the standard zip edition of CrystalDiskInfo 7.5.1 to make sure those HDs are healthy: Thanks! I'll take a look when I get home. I suspect my Windows 10 install was a bit hosed up though so I wouldn't be shocked if the root cause did end up being software. I was always getting weird bugs. The Edge browser never worked even after I used the Power Shell commands that were supposed to reset it (Edge would open and then immediately close/crash), the default colors for highlighting and the like were wrong (a very bright cyan instead of blue, making it impossible to read highlighted text), etc. axeil fucked around with this message at 23:43 on Jan 17, 2018 |
|
#
?
Jan 17, 2018 23:40
|
|
|
Zogo posted:I'd run the standard zip edition of CrystalDiskInfo 7.5.1 to make sure those HDs are healthy: Ran CrystalDiskInfo, here's what it's showing. Things look okay to me. 
|
|
#
?
Jan 18, 2018 01:59
|
|
|
Well this is fun. My Start Menu + Cortana + Taskbar is now refusing to work. I'm following the advice here: http://www.thewindowsclub.com/start-menu-does-not-open-windows-10 https://support.microsoft.com/en-us/help/929833/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system  Nevermind, apparently I passed an interrupt of some sort to cmd  . After it finished it showed no corruption.I also followed the advice here: https://answers.microsoft.com/en-us...c2503202?auth=1 and ran "$manifest = (Get-AppxPackage Microsoft.WindowsStore).InstallLocation + '\AppxManifest.xml' ; Add-AppxPackage -DisableDevelopmentMode -Register $manifest " in PowerShell but it didn't appear to do anything and I'm terrified of restarting the system. Any ideas? edit: Well I have no idea what fixed it but the start menu/Cortana are both back now. Weird. I'm running a full backup (including a system image) right now. Still very odd that this all seems to have resolved itself. axeil fucked around with this message at 05:34 on Jan 18, 2018 |
|
#
?
Jan 18, 2018 03:49
|
|
|
axeil posted:edit: Well I have no idea what fixed it but the start menu/Cortana are both back now. Weird. Yea, the HDs look okay. If that INACCESSIBLE_BOOT_DEVICE error comes back I'd disconnect all drives but the OS drive and then do a complete clean install of W10.
|
|
#
?
Jan 19, 2018 00:57
|
|
|
|
| # ? Apr 24, 2024 23:39 |
|
|
Zogo posted:Yea, the HDs look okay. Thanks! I've reinstalled all the software now and I'm re-running that full backup (the volume shadow drive service wasn't set to run, oops). Everything appears to be working fine, which makes this whole thing a huge mystery. Well at least I have a clean(ish) install of Windows now. Been wanting to do that for a while.
|
|
#
?
Jan 19, 2018 02:04
|
|