Boot Error When Changing SSD To AHCI
Aug 20, 2015I can't seem to get into the system after changing to AHCI in the BIOS. I have an SSD and I know that it will run really well in AHCI mode in Win 10?.
View 1 RepliesI can't seem to get into the system after changing to AHCI in the BIOS. I have an SSD and I know that it will run really well in AHCI mode in Win 10?.
View 1 RepliesBasically, I have a really bleepty BIOS that will only let me change the boot order with secure boot disabled and legacy boot enabled. I need secure boot because I just installed windows 10 onto a new drive and it won't activate. I have heard that this has something to do with secure boot being disabled. I still have the activated drive, which is the primary drive. Is there anything I can do to change the boot order?
View 7 Replieswhen I installed windows 7 Pro 64 bit on a new build, a few years ago, I had to install some specific drivers during the Windows 7 installation to ensure drives used AHCI mode. Do I still need to do anything during windows 10 clean install to new SSD drive in order to achieve this (I did not see anything in the clean install tutorial ) or is this all now taken care of in Windows 10?
View 9 RepliesI have Windows 10 Pro installed on an SSD in AHCI mode.
I would like to add a RAID 1 array to this system for storage but I understand some registry tweaks must be made before I can change my BIOS from AHCI to RAID mode or I'll end up hosing Windows.
I've read that the edits for older Windows at [URL] do not apply to Windows 10. know the registry edits that work for Windows 10?
I recently upgraded to Windows 10 and an SSD. I know you are supposed to run in AHCI for an SSD, and did a full Windows 10 install after enabling this setting in BIOS. Now my CD/DVD burner will spin up, but will not read disc's in Windows.
View 9 RepliesHow can I enable full user control without getting a ton of "failed to enumerate" errors after clicking apply? Can't even install printer software to Program Files.
Such hoops to jump through...
So at first, I was trying to resolve an issue with my BD-ROM drive described here: XPS 8700 - BD-ROM (HL-DT-ST DVDRW/BDROM CH20N) Not Recognized Windows 10 - Disk Drives (HDD, CD/DVD, Blu-ray) Forum - Disk Drives - Dell Community
However, when attempting to try different things, I am now in a position where I can no longer boot to Windows 10. More specifically, when I turn on my computer, I get an error saying no bootable drives found and it just lists my SATA 1, 2, 3, etc. drives with an option to restart or go to BIOS setup. In other words, I don't even see Windows anymore existing.
My basic computer specs:
Dell XPS 8700 SE
Intel Core i7-4700
Windows 10 with 1511 update
2TB hdd with 32GB mSATA SSD cache drive
16GB RAM
BD-ROM
I need to get Windows working again, and hopefully, get back my data. Here's what I did to cause the problems:
1) I went to Dell UEFI BIOS setup, and changed the SATA mode from "RAID" to "AHCI". Saved and exited BIOS.
2) After rebooting, Windows failed to load, had a consistent blue screen with the sad smiley face with error "IO1_INITIALIZATION_FAILED", automatic repair also failed.
3) I tried reverting back to "RAID" in SATA mode in BIOS, but it failed to change anything. Windows still wouldn't boot
4) I then entered into the special BIOS menu showing devices which listed my mSATA cache drive and hard drive and RAID settings. Since it showed that the cache drive was "Disabled", I thought I could fix my issues by re-creating the RAID array.
5) I tried to delete the current RAID setup shown in that BIOS menu, then chose the option to recreate the RAID0 array by selecting the option to create a "Striped Disk Array".
6) Once I did the above, Windows itself disappeared, and trying to undo the RAID0 option did not fix anything
So now I am no longer seeing Windows, not sure if my data on the hard drive still exists, and my cache drive (obviously) is not working.
doing a clean reinstall and losing all my previous data in Windows?
When I boot up my Windows 10 PC, I keep getting this error 0x0000020 and there are about 10 Error boxes. All starting with DX10, DX11, or DX12 in the title. [URL] .....
The entire box says: DX11: igoproxy.exe - Bad Image
C:WINDOWSSYSTEM32
vmgf2um.dll is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support. Error status 0xc0000020.
I recently upgraded a Toshiba A300 laptop (2009 model) from Win7 to Win10. I use a 125GB Kingston SSD as primary and a 280GB Hitachi as a secondary internal hard disk, in place of DVD drive, inside a cradle. This is a single OS installation, no dual boot. When I cold boot (from power on) and after the Bios logo, the "MBR Error 1" appears on screen and stops booting. To bypass I do a warm restart (Ctrl+Alt+Del) and the second (warm) boot loads Win 10. Also booting is ok from a Restart. Again error message appears only after a cold boot.
As a teaser I have to mention that, whenever I remove the cradle with the secondary Hitachi hard disk, the error does not appear during cold boot !!!. That is the error message appears only if the second hard disk is installed. This is an annoying situation only and does not affect any other operation, except booting.
Yesterday I removed dual booting Linux and after that my Windows 10 won't boot up. I have tried everything. The cmd commands: bootrec /FixMbr; bootrec /FixBoot; bootrec /RebuildBcd; Bcdboot commands and everything. Then I tried Refreshing PC what says: Drive where Windows is installed is locked. Please unlock it.....
Startup repair just scans for a short period and then says: Couldn't fix the problem. I can't Access normal Recovery options, so I'm using a recovery flash drive. I have tried several Live CDs but none of them won't fix the problem. I can access the UEFI Bios, but idk what to change there. I don't want to fresh install Windows, unless it's the only option, because it contains important data.
Windows 10 goes through the entire download/installation process, restarts, blue screens with a "system thread exception not handled (iastora.sys). It then restarts and shows this error for windows 10. Am I screwed? It goes back to the desktop and works somewhat (other than windows 8.1 bugs). I don't have any files on this computer that I need to keep. I just want it fixed!
View 1 RepliesI installed Windows 10 earlier but after about 10 minutes of using it my computer restarted itself automatically, and then it showed an error message saying that windows had "ran into a problem" on restart an it quotes the error code "0xc000007b".
I have taken a photo of it which can be seen here: [URL] ....
It then restarts again and gives me a list of options: [URL] ....
Should I reinstall the OS?
When I again turned on my pc, it says "disk read error". I do my job on my pc. I have too much work on it. There are too many files on my hdd.
View 1 RepliesI turned on my PC and got a Windows 10 error saying my PC needed to be repaired. I can go into the BIOS menu but I don't know what option to choose to reinstall Windows 10. I have it downloaded from the official website on a memory stick but I am thinking of buying Windows 8.1 from Amazon cause I do not like Windows 10 and want the full version. I would go with Windows 7 but I don't know what is and isn't legit on Amazon. I do not want an OEM version since I may be upgrading my PC and will want to reinstall Windows if I have to once again.
View 1 Repliesthe other day I realized I had a keylogger on my PC. I decided to use the windows 10 feature to wipe my HDD, deleting all the programs and installing win10 fresh again. After being finished with the restore, I booted my pc and was greeted to a message that said: something went wrong blah blah, with "INACCESSIBLE_BOOT_DEVICE" being the subtitle. I've tried rebooting my computer numerous times but no results. I've tried changing boot orders and shit in BIOS settings, to boot from USB but that didn't work either..
View 1 RepliesI upgraded ok with the update and successfully activated windows 10. I downloaded both 32bit and 64bit to usb using media creation tool as I wanted to clean install Windows 10 64bit on my 64bit compatible machine although am currently running 32bit windows 7 as that's what I had to hand when I built the PC. If I attempt to boot 32bit from usb it returns the error winload.efi missing. If I attempt to boot the 64bit version it just returns to windows boot manager.
Frustrated, I opted for the "reset this PC" function in settings instead as an alternative to the clean install and the reset failed, hung, then returned to the screen "what would you like to do". Once I selected "turn off PC" and it restarted and automatically continued the reset only to fail a second time. This time I choose to "return to windows 10" but it just hung. I had to rollback to windows 7 with repair dvd.
With windows 7 now installed again, I still cannot boot from either the 32 or 64 bit option in windows boot manager when I select to boot from the USB.It either returns to the boot manager or returns the winload.efi missing error.I have tried changing settings in bios to disable secure boot and fast boot but it makes no difference. I've read the Andre da Costa (sp?) wiki steps along with countless other how-to-clean-install windows 10 guides.
mobo: ga-ha81m-dsv2
Error 0xc0000359 winload.efi
I recently upgraded my laptop from W 7 to W 10. Now when I switch on I get a
'Runtime Error! Program: CWindowssystem32atibtmon.exe'
'This application has requested the Runtime to terminate in an unusual way.'
Then there's the top 'half' of a line that reads 'Please contact the application's support team for more '
The only option is to click 'OK' and everything continues as normal.
Every time I boot up my computer it does a repair on my computer then shows a error. The error says "automatic repair couldn't repaiclr your pc. Log file:EWindowsLogFilessrtSrtTrail.txt. I have windows 10
View 1 RepliesI have just recently upgraded from Windows 7 Home to Windows 10. I decided that I wanted a clean install so I went to the settings to reset. Now my computer won't boot windows and I'm given the "inaccessible_boot_drive" error. I cannot use my pc and don't have another pc for an ISO. what do I do?
View 1 RepliesI recently upgrade from Windows 7 to Windows 10 ( Build 10240). I had my overclock settings at 4.4 GHz/1.172 CPU Vin (specs listed at the bottom). My computer had no issues prior to switching to Windows 10. However, my computer always crashes and gives me the "overclock settings have failed" error within the first 10 minutes. This seems to only happen during the first boot session of my computer.
After restarting, the computer seems to run fine with no problems. I've tried restarting with default CPU settings and my usual OC settings. My computer runs for several hours with no issues. The issue comes back after I've turned the computer off for a long period of time (~3-5 hours).
I think its a Windows 10 issue, but I'm not sure.
Specs
OS: Windows 10 Pro 64-bit (Build 10240)
Mobo: MSI Z87-G41 PC Mate
CPU: i5-4690k
RAM: Kingston HyperX 8 GB
Since some weeks my usbs stopped working, including the mouse and keyboard. Fortunately I have remote desktop enabled and I could access to the computer. What I saw is that in every boot the usb chipset go to error state with code 10 (The message is: Insufficient system resources exist to complete the API).
I tried uninstalling and reinstalling the driver, updating it , disabling and enabling, using troubleshooter and reinstalling the usb.inf. The only that enables ok the usbs is disabling and enabling it, but when I reboot, error 10 again.
I don't know what to do. I found in other sites that the solution is only perform a repair install or format the computer and because I don't want formatting the computer I want to know if there are other options that would repair my usbs.
Inserted my new SSD to a SATA3 port and, next to my HDD 1TB, and went for a clean install right away. The system installed without problems (wiht the old HDD still attached), then i booted up the system (was a bit weird, because two versions were showing, however i formatted the old windows partition) and installed my programs. I saw that a 110 MB of data were still sitting on my old partition where the Windows 10 was earlier. Tried to delete those files but could not. However I shut down my pc and wanted to boot up again. Then it showed me a screen with "select proper boot device or restart computer". I went to BIOS to see if my SSD was set to primary boot device, but it was. But when i manaully select the boot device, my SSD, after starting up the computer, it boots into Windows and is running normally.
Can it be that there is no boot partition on my SSD and it wants to use the boot files from the HDD?? I also tried to unplug the HDD and boot up, but the same massage was showing up. But when i select the boot device manually it works.
After resetting my Microsoft windows 10, an error - inaccessible boot device appeared
View 4 RepliesUpgraded to Windows 10. Was working fine now NTFS_FILE_SYSTEM error boot loop. How do I get a repair disc to repair windows?
View 1 RepliesSo I installed windows 10 on my PC yesterday, I used to have windows 7. Today I turned on my PC and it says that I can choose to open my PC in windows 7 but not windows 10. So I thought OK I'll just try that, Then it said an error 0xc0000428 and it won't let me turn my PC on, I press enter and it enters the same loop of saying the error and selecting what version of windows I want to open.
View 1 RepliesI had a pretty much faultless Win 10 setup with all the latest patches installed then this morning I connected an external USB hard drive which I had used several times before but this time Windows said it needed to install a new driver. I let the driver install and then Windows stated it needed a restart to complete the installation.
When restarting I received the "Inaccessible_Boot_Device error message - Windows will restart for you" message. On restarting again I got: "Your PC couldn't start properly. Error code 0xc0000001." Windows tried to automatically repair itself displaying the Diagnosing message first and then Attempting Repair message, and finally reporting it could not fix the problem. I'm not sure if the new driver being installed created the problem or whether it was just a coincidence and something else has caused the fault.
I was able to boot to Recovery using a USB stick created with Microsoft's MediaCreationTool. Safe boot and all the other startup options didn't do anything apart from resulting in yet another failed boot. Getting to the command line, I was able to view the file that Windows creates when it tries to repair itself: c:windowssystem32logfilessrtsrttail.txt. That file shows that all tests were completed successfully until:
"Root cause found. A patch is preventing the system from starting
Repair action system files integrity check and repair
Result failed error code 0x490"
I tried: sfc /scannow and got:
"Verification 100% complete, Windows resource protection could not perform the requested operation"
I then tried sfc /verifyonly and got:
"Windows resource protection found integrity violations. Details are included in the cbs.log. Note that logging is currently not supported in offline servicing scenarios."
As the message suggested, no cbs.log files were created.
I have tried:
bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcd
which all complete successfully but doesn't work.
Also tried chkdsk which didn't find any errors and:
bootsect /nt60 ALL
which again seems to complete successfully but doesn't work.