Inaccessible Boot Device after cmos clear

[DAXgs2]

I have lost it, I feel like I have been in so many circles, that I am missing the joke right in front of me..

Long story short.. I purchased 2 new ram sticks (2x8gb) to match a pair I already have installed. I already had 32 GB's of DDR4 2133, but 2 different brands, I wanted the same. So I installed them, and fans and all the basics would start, and I was given an error code. After much reading, I decided that I should try clearing cmos ad removed the battery for about 20 seconds. I also just went ahead and went back to my original configuration of ram. (4x8gb) Now everything boots and my display works, but I am getting INACCESSIBLE BOOT DEVICE, After reading some into this, I have established that this has to do with a setting in my bios, but I feel like I have tried it all. The only way I can get my PC to boot, is by changing the SATA port settings from AHCI to RAID.

When I do this, everything boots fine. With the exception of a menu during boot telling me information about my RAID. Which is not how it was before.

I have tried changing boot orders, removing ram sticks, removing all non essential hard drives, even put in a new battery and restoring defaults in bios several times. I am lost here! Like I said, I got it working with it set to RAID, but I do not like having the menu show at boot! Is there some other setting I am missing??



MSI M5 bios v. 1.80
Intel i7 6700k
GTX 980Ti
32 GB (4x8) 2133 DDR4
PNY 240 GB SSD (main)
Seagate Barracuda 3 TB 7,200. (storage)
Windows 10 Home 64 bit.


Thanks!

Thanks for any help.

 

[Colif]

I assume PC was unplugged when you made all these changes?

if you didn't have RAID before, you shouldn't need it now. Set it back to what it was before.

On another PC, download the Windows 10 media creation tool and use it to make a win 10 installer on USB - its a boot disc for now.

change boot order so it boots from USB and then SSD
boot from installer
on screen after language options, choose repair this PC, not install
choose troubleshoot
choose advanced
open command prompt and type chkdsk /f and press enter. Might take a while. http://www.toppctech.com/inaccessible-boot-device-error-fixed/

 

[DAXgs2]

I assume PC was unplugged when you made all these changes?

if you didn't have RAID before, you shouldn't need it now. Set it back to what it was before.

On another PC, download the Windows 10 media creation tool and use it to make a win 10 installer on USB - its a boot disc for now.

change boot order so it boots from USB and then SSD
boot from installer
on screen after language options, choose repair this PC, not install
choose troubleshoot
choose advanced
open command prompt and type chkdsk /f and press enter. Might take a while. http://www.toppctech.com/inaccessible-boot-device-error-fixed/

Thanks for your replay. I will try all of this now. Yes, of course everything was unplugged when doing anything. I also already have the usb disk, so will go ahead and try now and post any results.

 

[DAXgs2]

Booted into cmd promt and typed chkdsk /f and it says the drive is write protected. Upon running /c, "CHKDSK FOUND BAD ON DISK UPPER CASE TABLE"

But cant run /f because of write protection..

 

[Colif]

Try this in command prompt

Method 1: I suggest you to run bootrec.exe through command prompt
Type the below command separately to fix issue with boot corruption
1. Bootrec.exe/ScanOs
2. Bootrec.exe/RebuildBcd

http://answers.microsoft.com/en-us/windows/forum/windows_10-update/windows-10-boot-looping/9d1fa83c-d20b-4f12-8699-4e9db4b1bf37

how old is the SSD? i can tell PC is new but is SSD?

Read-only CHKDSK found bad on-disk uppercase table - using system table". It goes on to verify files (stage 1 of 3), indexes (stage 2 of 3), and security descriptors (stage 3 of 3). The report filed is "Errors detected in the uppercase file". with the recommendation "Windows has checked the file system and found problems.Run chkdsk with the /F (fix) option to correct these". But when I do that I encounter the message "The type of the file system is NTFS. Cannot lock current drive. Windows cannot run disk checking on this volume because it is write protected.

this suggests you probably best fresh installing, and it could be your SSD: http://answers.microsoft.com/en-us/windows/forum/windows_8-hardware/unable-to-install-os-as-disk-is-write-protected/e3a622be-d159-4a59-b6d2-58d0e9d86806

 

[DAXgs2]

Try this in command prompt

Method 1: I suggest you to run bootrec.exe through command prompt
Type the below command separately to fix issue with boot corruption
1. Bootrec.exe/ScanOs
2. Bootrec.exe/RebuildBcd

http://answers.microsoft.com/en-us/windows/forum/windows_10-update/windows-10-boot-looping/9d1fa83c-d20b-4f12-8699-4e9db4b1bf37

how old is the SSD? i can tell PC is new but is SSD?

Read-only CHKDSK found bad on-disk uppercase table - using system table". It goes on to verify files (stage 1 of 3), indexes (stage 2 of 3), and security descriptors (stage 3 of 3). The report filed is "Errors detected in the uppercase file". with the recommendation "Windows has checked the file system and found problems.Run chkdsk with the /F (fix) option to correct these". But when I do that I encounter the message "The type of the file system is NTFS. Cannot lock current drive. Windows cannot run disk checking on this volume because it is write protected.

this suggests you probably best fresh installing, and it could be your SSD: http://answers.microsoft.com/en-us/windows/forum/windows_8-hardware/unable-to-install-os-as-disk-is-write-protected/e3a622be-d159-4a59-b6d2-58d0e9d86806

Trying bootrec now, however upon first trial, it told me windows has not been found on any drives... I was going to try changing the boot priority, but upon restart it started right up normally... This has happened once before, so I am not going to hold my breath, but still wonder why it just works all of a sudden.

As for the the SSD, it is maybe 3 weeks old.

edit: Will wait for you to get back to me before I shut down or anything since I am in on a normal boot and do not want to mess it up again by restarting.

Ran cmd in administrator and Wont let me do /f since the disk in in use, but it also found no errors...

 

[Colif]

so it started without the raid message? check answer 2 here to confirm what your drives are running as: http://superuser.com/questions/757936/check-if-my-ssd-in-runing-on-ahci-mode-inside-windows-7

Since its working... run HDTune Trial and Crystal Disk Mark on your SSD.

think i need a second opinion in this thread. I probably missing something obvious.

 

[DAXgs2]

Here is exactly what happened. I typed Bootrec.exe/ScanOs into cmd, and it said Windows was not found on any drive. I restarted, and figured I would try the default configuration for boot priority, so I just "restored default" settings in bios to reset the boot priority. Please note, that I have reset bios to default settings before, so this could not have been the magic fix.

Anyways, once the PC started booting, I was trying to get back to CMD, and clicked the wrong button, which took it to trying to repair itself. Which if the past was any indication, I would be sitting here for 3 hours doing nothing, so I did a hard restart from this menu, and it just booted up normal. Not in RAID, it is in AHCI, and I verified it through device manager.

It reads: MYPC > IDE ATA/ATAPI controller > Standard SATA AHCI Controller

This is why I am frustrated! It seems so silly. In the end, I feel like the fix will be my speakers are plugged into the wrong jack.,,

 

[Colif]

May have just been the order you did them in. bootrec may not be able to work with raid, so couldn't see the drive.., I have to look into ahc/raidi one day.

I don't understand how you could run 1 drive as raid, I would have expected you to have more. I have always avoided raid as I didn't want to lose everything if 1 disc died and never been rich enough to have multiple drives to act as mirrors.

Now I guess you need to work out why extra ram isn't working

 

[DAXgs2]

Well the ram is working now. Only issue has been the boot up. But I am going to try restarting and see where that gets me. Hopefully no issues, but again, I am not holding my breath.

 

[Colif]

Well the ram is working now. Only issue has been the boot up. But I am going to try restarting and see where that gets me. Hopefully no issues, but again, I am not holding my breath.

Will these be the famous last words? we find out shortly

 

[DAXgs2]

5 Restarts and 2 shut downs later, it booted normal every time! So either the magic computer ghost fixed it or the hard reset I did when I went into the wrong menu. Either way, I feel extremely uneasy because I feel like the problem could come back anytime. I guess if and when it does, I will just format and start over.

Thank you very much for your help! I will update with any future information.

 

[Colif]

Stay out of BIOS and Registry, my main rules for myself. PC will work fine if you stay out