Double-click on it and set its value to 0 (That's zero and not alphabet O). PS: If you don't want to edit the registry manually and want a ready-made registry script to do the task automatically, download following ZIP file, extract it and run the extracted REG file.
It'll ask for confirmation, accept it: You can also try following method suggested by one of our readers: 1. Run msconfig again, go to Boot tab, unmark Safe boot option and restart PC.
Or you can reinstall Windows but that would require lots of time and efforts.
Then how to switch SATA hard disk mode from IDE to AHCI or RAID in BIOS after installing Windows so that you would not need to repair or reinstall Windows? You just need to tell Windows that hard disk mode is going to change upon reboot using Windows Registry and Windows will automatically detect the mode and will install the required drivers and you'll be able to successfully change the SATA mode in BIOS without any need to reinstall Windows.
So without wasting time lets start the tutorial: 1. Now go to following keys one by one: In right-side pane, look for a DWORD "Start". Now enter into BIOS settings and change SATA hard disk mode to AHCI or RAID according to your requirements. As soon as Windows will start booting, it'll automatically detect the change and will install the appropriate drivers.
First DO NOT change SATA hard disk mode settings in BIOS, leave it to the default settings which were used while installing Windows. Now start Windows and type regedit in RUN or Start Menu search box and press Enter. Double-click on it and set its value to 0 (That's zero and not alphabet O). If you are using RAID or other interface, do the same thing for following key as well: In right-side pane, look for a DWORD "Start". It'll reset the hard disk mode settings in Windows registry. Once the drivers are installed, Windows will boot without any problem and you'll not need to reinstall Windows just to change SATA hard disk mode.
I let Windows Update do its thing while I was out and came back to a freshly updated and restarted computer. Later that evening, I got booted out of a fullscreen game I was playing and was greeted with: Since then, two times a day, I get an error like that. I took a screenshot of the task manager showing the processes that close out when I click OK on that dialog box: already tried SFC /scannow. Specs: Windows 7 64-bit i5-3750K Gigabyte Z77-DS3H 7950 HD I finally stopped being lazy a few days ago and caught up on updating my PC.
I let Windows Update do its thing while I was out and came back to a freshly updated and restarted computer. Later that evening, I got booted out of a fullscreen game I was playing and was greeted with: Since then, two times a day, I get an error like that. I took a screenshot of the task manager showing the processes that close out when I click OK on that dialog box: already tried SFC /scannow. Specs: Windows 7 64-bit i5-3750K Gigabyte Z77-DS3H 7950 HD Interesting..since this week I too started receiving an identical error, and have never had it before.
It generally appears out of nowhere during the day, generally only one or two times. I have no Windows 7 installation disk, since have an OEM version, with only a 'recovery' partition on the drive.
Today we are going to address a very common but one of the most irritating problems in this tutorial.
Consider following scenario: You got a new computer system in which the SATA hard disk controller mode in BIOS settings was set to IDE ( or IDE Compatibility or Standard IDE) instead of AHCI (Advanced Host Controller Interface) or RAID for better compatibility. After sometime you realized it and changed the SATA mode from IDE to AHCI or RAID in BIOS and BOOM!!! Windows will no longer start and will show a BSOD (Blue Screen Of Death) containing error code "". Because Windows can't load the new drivers for AHCI or RAID interface.
Actually when Windows is installed, it automatically disables unused storage drivers to speed up Windows startup process.
As a temporary fix, you can reset the SATA mode from AHCI or RAID to IDE in BIOS but you'll find yourself in the same situation.