The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Windows 10: white box "is not accessible" on blue screen ?

    Discussion in 'Windows OS and Software' started by gulf-of-mexico, Aug 28, 2016.

  1. gulf-of-mexico

    gulf-of-mexico Notebook Enthusiast

    Reputations:
    0
    Messages:
    18
    Likes Received:
    1
    Trophy Points:
    6
    Setup a Dell 7710 with Windows 10 and two SSDs:
    Operating System: Samsung 950 Pro 512 GB NVME PCIE (bitlocker, TPM)
    Second Drive: Samsung 850 Pro 1 TB SSD SATA (bitlocker set to autounlock)
    Both encrypted with bitlocker
    Dell BIOS is latest version.

    Worked perfectly for a week.

    Now after a week, sometimes when turning notebook on, I get a white box (with no indication what it is referring to, just a white entry box but with no label) on a solid blue background and then "is not accessible" but it doesn't say what isn't accessible. If I power down and power back up it usually works fine then with no error message.

    Has anyone experienced this before?

    I feel like this is bitlocker, but with no text I'm not 100% sure (it looks similar to what bitlocker would look like when you need to enter a recovery key, but with no heading and no description of which drive, just a white text entry box and "is not accessible" which is making it a bit difficult to search for "white box on blue background" "is not accessible" :(

    It's set with secure boot on and usb boot disabled, UFEI with one option to boot windows in bios. I guess I should say in the title "blue background" rather than "blue screen" although since the computer won't boot, I'm not sure what it is when it happens.
     
    Last edited: Aug 28, 2016
    gulf-of-mexico, Aug 28, 2016
    #1
  2. katalin_2003

    katalin_2003 NBR Spectre Super Moderator

    Reputations:
    14,958
    Messages:
    5,671
    Likes Received:
    1,519
    Trophy Points:
    331
    Have you checked the Event Viewer (eventvwr.exe) ?
     
    katalin_2003, Aug 28, 2016
    #2
    toughasnails likes this.
  3. gulf-of-mexico

    gulf-of-mexico Notebook Enthusiast

    Reputations:
    0
    Messages:
    18
    Likes Received:
    1
    Trophy Points:
    6
    Thanks, I'm digging through Event Viewer, system section now, but not finding anything obvious.

    It appears when I get the blank blue screen with unlabeled white entry box trying to start, that if I hit the power button to shut down the following is then logged:
    Critical "The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."

    (Windows Shut down appears totally normal at least so I'm assuming this is happening after it fails to start and I get the unlabled white box and have nothing else to do except hit the power button and try again to start...)

    I also see an error Windows failed fast startup with error status 0xC000009A.
     
    gulf-of-mexico, Aug 28, 2016
    #3
  4. katalin_2003

    katalin_2003 NBR Spectre Super Moderator

    Reputations:
    14,958
    Messages:
    5,671
    Likes Received:
    1,519
    Trophy Points:
    331
    You need to look at events errors that occurred before the unclean shutdown log.

    As for the 0xC000009A error, it might be related to an application set to start with your session. Are you running any anti-virus program?
     
    katalin_2003, Aug 28, 2016
    #4
    custom90gt and toughasnails like this.
  5. gulf-of-mexico

    gulf-of-mexico Notebook Enthusiast

    Reputations:
    0
    Messages:
    18
    Likes Received:
    1
    Trophy Points:
    6
    Yes, running Avast anti-virus.

    There doesn't seem to be any related Error or Critical logged.

    There are a few warnings logged:
    The driver \Driver\WUDFRd failed to load for the device
    (a search seems to reveal that that's USB realted though rather than pertaining to the nvme pcie or sata ssd, possibly when I inserted a USB windows media to troubleshoot. I also have a logitec wirelss mouse usb adapter in the other usb slot.)
     
    Last edited: Aug 28, 2016
    gulf-of-mexico, Aug 28, 2016
    #5
  6. gulf-of-mexico

    gulf-of-mexico Notebook Enthusiast

    Reputations:
    0
    Messages:
    18
    Likes Received:
    1
    Trophy Points:
    6
    I have the latest samsung NVME driver installed for the 950.

    I'm not sure if the error relates to bitlocker or not, but possibly I'll try de-encrypting both drives and then re-encrypting them.
     
    gulf-of-mexico, Aug 28, 2016
    #6
  7. gulf-of-mexico

    gulf-of-mexico Notebook Enthusiast

    Reputations:
    0
    Messages:
    18
    Likes Received:
    1
    Trophy Points:
    6
    gulf-of-mexico, Aug 28, 2016
    #7
  8. gulf-of-mexico

    gulf-of-mexico Notebook Enthusiast

    Reputations:
    0
    Messages:
    18
    Likes Received:
    1
    Trophy Points:
    6
    OK, it appears I was wrong regarding the unexpected shutdown message.

    Going to Control Panel -> Power Options -> System Settings "Choose what the power buttons do"
    Unchecking " Turn on fast startup (recommend)"
    resolves the "The system has rebooted without cleanly shutting down first" message.

    Powering off and then on again a few times, I didn't see logged again with fast startup disabled.

    Then Checking " Turn on fast startup (recommended)" again and powering off and on I get the following error and critical messages logged:

    Windows failed fast startup with error status 0xC000009A. Kernel-Boot

    The previous system shutdown at 9:37:01 PM on ‎8/‎28/‎2016 was unexpected.     Eventlog

    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.     Kernel-Power

    Audit events have been dropped by the transport. 0     Eventlog
     
    gulf-of-mexico, Aug 28, 2016
    #8