
So you may have to physically open the computer case and change the drive to a different sata port. This change reflects on which ports your HD and cdrom drives are plugged into on the motherboard and what your motherboard supports. However, 1-4 can be AHCI and 5-8 can be IDE. Typically in the bios if using 1-4 ports as IDE then 5-8 must also be IDE. Hopefully this sheds some light on this particular issue. Scroll down to Standard SATA AHCI Controller and your drives should be listed there. Confirm that they are AHCI you type devmgmt.msc in run and go to view and Devices by Connection. The drives should be AHCI and the dvd drive working. Now you go to run and type msconfig again and uncheck safe-boot and reboot the system. Windows automagically loads the drivers for you. Hit the key to go into bios and change the hard drive SATA controller configurations from IDE to AHCI save to bios and restart once more. Hit apply and You will get a prompt to restart into safe boot. Change to boot tab and put a check into safe boot. How to do that you right-click Start and Run and type msconfig. You have to boot into safemode to get windows to load the AHCI driver. Reg delete HKLM\System\CurrentControlSet\Services\atapi\Controller0 Be sure to create a system restore point first.

If others out there are in the same boat as me you first you have to delete the registry key I posted above in cmd and reboot the system. Windows 10 didn't bother to load the AHCI controller drivers so it cannot detect the drive. I tried changing them to AHCI and booting Windows 10 and it won't load. So this is a bios controller issue.The cdrom is SATA and that is the problem. I changed those prior to installing Windows 7. Not sure how they got mysteriously changed. The problem with my system is that Windows 10 was installled prior to not changing the hard drive controller configurations in the bios to AHCI instead of IDE. It's logging a ton of event id 51 errors."An error was detected on device \Device\CdRom0 during a paging operation."


Alright the above fix was for Windows 7/8 and now is causing a error in task viewer no surprise.
