BSOD on boot - INACESSIBLE_BOOT_DEVICE


  1. Posts : 4
    Windows 10
       #1

    BSOD on boot - INACESSIBLE_BOOT_DEVICE


    Hi,

    All my woes started with an update, that did not want to install. It would attempt to finish the update installation on reboot, but then fail and "undo the changes." I later found out via event viewer that it was failing to create a restore point. I believe that's why the update install was failing, and I never did figure out why the restore point was failing, but I think the restore point saga is one for another post.

    On what ended up being my last attempt at getting it to install, there was a power loss at the "Restarting..." phase of the update installation (so it had already done the "Updating.." part). Upon reboot, BSOD with the message in the title.

    I wasn't able to get very far via the cmd prompt in recovery, uninstalling latest updates via recovery, etc, so I dug out the DVD today and tried further debugging. When I attempted automatic repairs today, it failed as per usual, but at least this time it gave me a log path (albeit not very useful), which is here:
    SrtTrail.txt - Google Drive

    So a binary is corrupted, makes sense, but it doesn't really tell you what. So my first thought after reading around was to run SFC, and I did that via "Repair" on the DVD.

    sfc /scannow /OFFBOOTDIR=D:\ OFFWINDIR=D:\Windows

    This failed because it said a previous repair was pending. After some digging, I found it determines this by looking for the file: Windows\WinSxs\Pending.xml. I removed this (I still have it if I need to put it back). After that, the above command ran successfully. Unfortunately, no problems found.

    So the other mainstream tip you find is to use DISM to remove pending installed packages. It fails for seemingly all packages that are pending install, I also tried removing pending uninstall, ie.:
    dism /image:\ /Remove-Package /PackageName:Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4400.1

    This failed, the log for which is here:
    dism.log - Google Drive

    I would definitely prefer not to nuke the partition, although I'm definitely at a stand-still. If anybody has any idea on why that package removal is failing, I'm all ears. I just saw in signing up & posting this the v2 script collector thing. I'm going to see if I can run that now off the DVD repair mode.

    Thanks!

    EDIT:
    It seems the v2 script collector is written in power-shell, which is a no-go for me using only the repair mode on the DVD or recovery partition which only have the traditional command prompt.

    Should I try the DM log collector .exe instead? I can't really look at it to say if it'll work in the DVD recovery mode given that it's a binary. But I have filesystem access via another OS, so I can get any logs that are needed.
    Last edited by Greg100; 01 Sep 2021 at 05:31. Reason: Update
      My Computer


  2. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #2

    For now, see if there are any .dmp files in C:\Windows\Minidump. If there are zip them to another folder then upload to a file sharing site and post a link to the zip here.
    Also check for C:\Windows\MEMORY.DMP. If it's there zip to to another folder then upload to a file sharing site and paste a link to it here. OneDrive or Google drive are good places to upload to.
      My Computers


  3. Posts : 4
    Windows 10
    Thread Starter
       #3

    Ztruker said:
    For now, see if there are any .dmp files in C:\Windows\Minidump. If there are zip them to another folder then upload to a file sharing site and post a link to the zip here.
    Also check for C:\Windows\MEMORY.DMP. If it's there zip to to another folder then upload to a file sharing site and paste a link to it here. OneDrive or Google drive are good places to upload to.
    I just checked and unfortunately while there's one .dmp located in C:\Windows\Minidump, both it and C:\Windows\MEMORY.DMP are dated (both name and modified data) 081721, which was before this issue happened.

    These crashes at startup happened maybe Saturday or Sunday at the earliest (28th of August). I may have been having the update install issue then (can't recall when that started), but not this boot issue (the one I'm really concerned about).

    Never-the-less, in the unlikely chance that there's info related to this crash startup, I've posted them
    here: 081721-11703-01.dmp
    and here: MEMORY.dmp

    - - - Updated - - -

    Hi,

    I retrieved some event logs today in the event that they help somebody, they don't really look interesting though. I grabbed the System, Application, and Setup event logs. I'll try to grab some kernel logs tomorrow including the "Kernel-PnP/Configuration" log grabbed in the v2 log collector script.

    If anybody needs any additional logs that they'd normally have if I was able to execute the v2 log collector just let me know, I can go through the v2 log collector script and figure out what needs to be done to obtain that log, although some of them may not work without that particular partition online (eg. dism /online ...), but it seems most of the tools have an "offline" mode for file paths, etc. so I should be able to get most anything.

    Application, Setup, and System Logs
      My Computer


  4. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #4

    Dump shows:

    Code:
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver has failed to complete a power IRP within a specific time.
    Arguments:
    Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
    	subsystem.
    Arg2: 000000000000012c, Timeout in seconds.
    Arg3: ffffc58aa316c040, The thread currently holding on to the Pnp lock.
    Arg4: fffff8024be6d9c0, nt!TRIAGE_9F_PNP on Win7 and higher
    FAULTING_MODULE: fffff8024d240000 vmbusr

    Microsoft Hyper-V Virtual Machine Bus Root Driver


    Are you using any Hyper-V virtual machines?
      My Computers


  5. Posts : 4
    Windows 10
    Thread Starter
       #5

    Ztruker said:
    Dump shows:

    Code:
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver has failed to complete a power IRP within a specific time.
    Arguments:
    Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
    	subsystem.
    Arg2: 000000000000012c, Timeout in seconds.
    Arg3: ffffc58aa316c040, The thread currently holding on to the Pnp lock.
    Arg4: fffff8024be6d9c0, nt!TRIAGE_9F_PNP on Win7 and higher
    FAULTING_MODULE: fffff8024d240000 vmbusr

    Microsoft Hyper-V Virtual Machine Bus Root Driver


    Are you using any Hyper-V virtual machines?
    Actually quite the opposite. I had Hyper-V explicitly disabled because I use Virtualbox, and it's necessary to disable Hyper-V in order to allow Virtualbox to access HW virtualization.

    That being said, I've seen on at least 2 different updates where after an update Hyper-V is enabled again. It's very frustrating, but it happened 2x at least in the last 1.5 years since I initially installed. So while I've explicitly disabled Hyper-V, I would say it's still quite possible that it's enabled. But I'm not [purposefully] making use of it.

    Should I try disabling virtualization in the BIOS so none of that could run in the OS?
      My Computer


  6. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #6

    Sorry for the long delay in responding, my wife has been very ill.

    Yes, trying disabling virtualization in the BIOS to see hwat that does.
      My Computers


  7. Posts : 4
    Windows 10
    Thread Starter
       #7

    Ztruker said:
    Sorry for the long delay in responding, my wife has been very ill.

    Yes, trying disabling virtualization in the BIOS to see hwat that does.
    No worries. I hope your wife is doing better.

    I tried disabling virtualization in the BIOS, no change, still BSOD On boot with same error.

    I did pull 2 more logs though in recovery mode:
    1. Microsoft-Windows-Kernel-PnP/Configuration (as this was requested in the "log collector v2" powershell script)
    I also wasn't sure if this could be of interest, so I pulled it too:
    2. Microsoft-Windows-Kernel-Boot/Operational

    I don't see anything that's really telling in either, but perhaps better eyes will.

    Thanks!
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 08:08.
Find Us




Windows 10 Forums