View Single Post
  #5  
Old October 11th 18, 12:10 AM posted to alt.comp.hardware.pc-homebuilt
Paul[_28_]
external usenet poster
 
Posts: 1,467
Default Windows 10 fails to boot, then it reboots, bizarre self-fix

Mike wrote:
On 10/10/2018 10:27 AM, Paul wrote:

To fix "inaccessible boot device", you need to set
the StartOverride key to 0 from the regular value
of 3. When I tried this on 1803, it didn't work,
which means the damn recipe has changed again.

I had to use an old bounce technique to quickly
get it running again. It just means moving the
drive to another kind of storage port. I used
a SATA to IDE adapter for the SATA SSD and plugged
it into the IDE cable, and Windows 10 booted right
up. Then, I could go into Device Manager and delete
the two Code 10 entries so Windows would rediscover
the SATA ports that were using the wrong driver.
Then, when I moved the SSD back to a SATA port,
it worked again.


This info might come in handy in the future.

Please be more descriptive about the "code 10"
entries.

I have also tested in Windows 10, the removal of the
ENUM key in CurrentControlSet, and Windows 10 survived
that and booted up while re-discovering all the hardware.


I've got a bunch of currentcontrolset keys.
Which one are we talking about here?



Please be more descriptive about the "code 10" entries.


This picture is collected in WinXP, but would look
similar in a Win10 system. The SATA ports are broken
into a set_of_four controller and a set_of_two controller.
The two items pointed to, are part of the set_of_two
Intel 2920 block. Even though it's SATA, the text description
calls the ports Primary and Secondary.

https://i.postimg.cc/cC8SgRTw/code10_candidates.gif

The "Standard Dual Channel PCI IDE Controller" below those,
is the JMicron part. That's the one I connected an adapter
to the end of the motherboard ribbon cable, to make the
cable into a SATA interface, and from there, to the SSD drive.
The "Standard Dual Channel PCI IDE Controller" only has one
operating mode (IDE) and there is little danger of the
driver being inappropriate on that one (definition stays
the same forever, after the OS is installed). The other six,
their DEV identifier changes as a function of BIOS setting.
The CC value does too (Class Code, a BIOS thing).

*******

I've got a bunch of currentcontrolset keys.
Which one are we talking about here?


https://s9.postimg.cc/vwioz43f3/WIN10_delete_ENUM.gif

Paul