Windows startup error (8.1 & 10) device changed, etc.

K

kartracer

Suspended / Banned
Messages
1,178
Edit My Images
No
I had the startup error where Windows indicates a device has changed and I need to run repair. Went into advanced options tried auto repair, etc. Sometimes the repair option did not work and sometimes it seemed to work but was unable to complete as it could not update the device (which seemed to be offline) after running.

It seems to be related to a second SSD which I use for data storage. When I unplug the second SSD Windows usually starts up. Upgraded to version 10 and was surprised to have the same problem recur.

The actual error code is 0xc000000f - a required device isn't connected or can't be accessed.

Only thing I can think of is to backup the data disk, format and restore to remove anything that might be indicating its a boot device and confusing WIndows.

Am I on the right track, or any other suggestions?
 
Last edited:
Check the connections to the SSD's and replace any cables that look remotely iffy.
This might sound a bit daft but spent over a week trying to get my PC to run properly, it kept falling over, sometimes it would start and sometimes not, tried to reinstall windows without success ( it said the disc was corrupt-it wasn't) it was a bit like a car with an intermittent fault.
In the end I gave up and bought a new PC , I started to dismantle the old one to salvage bits and when I disconnected the SSD the cable did not seem to seat properly, I replaced it with a new cable which just clicked into place and the d**n thing has worked fine ever since
 
Last edited:
troutfisher said:
Check the connections to the SSD's and replace any cables that look remotely iffy.
This might sound a bit daft but spent over a week trying to get my PC to run properly, it kept falling over, sometimes it would start and sometimes not, tried to reinstall windows without success ( it said the disc was corrupt-it wasn't) it was a bit like a car with an intermittent fault.
In the end I gave up and bought a new PC , I started to dismantle the old one to salvage bits and when I disconnected the SSD the cable did not seem to seat properly, I replaced it with a new cable which just clicked into place and the d**n thing has worked fine ever since
Click to expand...

Well, that's a good point. Forgot to mention when I had the problem on Win 8.1 I decided to upgrade (actually downgrade from i7 to new i5) and replaced all the system except the video card and SSD's. SO I was disheartened when the problem followed over onto the new system. I have plenty of SATA cables so will swap them out and try. Thank you.
 
It sounds like a driver issue. Indeed, whatever the initial problem was ... You have by changing all the hardware made it worse.

I suspect the initial problem probably related to SATA mode changing... Maybe a BIOS corruption resulted in BIOS reverting to default settings and SATA mode changing from IDE to AHCI.

Backup your data and start again with a fresh install.
 
Bios corruption isn't a thing but I'd agree that a clean install is best. If it takes more than 2 hours to troubleshoot, you might as well have reinstalled
 
landwomble said:
Bios corruption isn't a thing but I'd agree that a clean install is best. If it takes more than 2 hours to troubleshoot, you might as well have reinstalled
Click to expand...

I beg to differ. 50 or so desktops at work and after a power cut there are BIOS checksum errors on at least one or two of them. Usually an indicator that the CMOS battery needs replacing.
 
Maybe was a problem with BIOS/batter on the old m/board. However not its a new m/board and presumably a new battery. I reinstalled Windows 8.1 and 10 from scratch on the new hardware.
 
If you read my original reply, whatever the cause of the original problem on the old hardware (all things being equal I suspect a switched BIOS setting or a corrupt registry setting/driver), I was explaining that by switching out the hardware to new hawdware you potentially go from having one isolated problem to a myriad of problems... the new board will have different default BIOS settings and a different chipset and chances are your existing Windows install won't have the required driversdrivers/configuration available on boot to boot successfully with the new hardware.

How did your reinstall go? Successful?
 
Last edited:
afasoas said:
If you read my original reply, whatever the cause of the original problem on the old hardware (all things being equal I suspect a switched BIOS setting or a corrupt registry setting/driver), I was explaining that by switching out the hardware to new hawdware you potentially go from having one isolated problem to a myriad of problems... the new board will have different default BIOS settings and a different chipset and chances are your existing Windows install won't have the required driversdrivers/configuration available on boot to boot successfully with the new hardware.

How did your reinstall go? Successful?
Click to expand...

The reinstall of Win 8.1 on a bare drive and upgrade to Win 10 went without any problem at all. However, the 0xc000000f error surfaced within a week or two in both cases.
 
Okay, that's a bit clearer.

When the error code is displayed, is there a faulting module displayed with it?
 
afasoas said:
I beg to differ. 50 or so desktops at work and after a power cut there are BIOS checksum errors on at least one or two of them. Usually an indicator that the CMOS battery needs replacing.
Click to expand...
BIOS battery is a once in ten years thing and nothing to do with your operating system...
 
I had similar problems, all is fine since I did a clean installation of Windows 10, - it seems to be an error when doing an Upgrade, - Hope this helps.
 
landwomble said:
BIOS battery is a once in ten years thing and nothing to do with your operating system...
Click to expand...

This is why I have to tweak the registry to enable Windows drivers for AHCI SATA support before changing the BIOS SATA mode from IDE to AHCI*? This is why people have countless problems with secure boot? ... No ladies and gents, you heard it here first. The computers startup configuration does not affect the OS.

*IDE mode makes the Intel Rapid Storage Driver fully utilize an entire CPU core

I will recall the sagely advice I received here next time I am changing BIOS settings in order to get a colleagues desktop to boot again following a power cut.
 
Last edited:
You must log in or register to reply here.
Back
Top