/ Sign-up
Your question

Doing a clean Win 7 install, and get to a screen that says "A required CD/DVD device driver is missing"...

  • DVD
  • CD-Rom
  • AMD
  • CPUs
  • Device Driver
  • Windows 7
  • MSI-Microstar
Last response: in Windows 7
September 30, 2013 7:49:47 PM

System details:

CPU: AMD A8-5600K
SSD: Samsung 120GB 840 series
DVD: LG model GH24NS95

First off, I can't find a plain old driver for the CD/DVD. LG just packages application software that Win 7 doesn't recognize (I tried the disk). I saw in another thread that even though Win 7 says it is looking for the CD/DVD, it might actually be looking for the HDD. I can't find any drivers for the Samsung 840 that Win 7 will recognize. I can't get past this screen and I am perplexed. Any help would be very much appreciated.


More about : clean win install screen required dvd device driver missing

a b $ Windows 7
a b à CPUs
a b À AMD
September 30, 2013 9:47:20 PM

I believe it might be looking for the chipset driver.

There is a RAID driver that contains the driver for the AHCI
October 1, 2013 5:58:34 PM

Where would I find that RAID driver that contains the AHCI? I can't seem to locate it on the MSI mobo driver disk. Can I download it from somewhere and load it from a USB drive? Dang. This is immensely frustrating. Any help would be appreciated.

Related resources
October 1, 2013 6:28:33 PM

I have read lots of threads related to this topic and none seem to work. I have changed the boot order to make sure that the CD-ROM is first. I have changed the SATA settings from AHCI ti IDE and back again. I have switched between UEFI and UEFI And Legacy support. I have cleaned and formatted my SSD with a single partition and then gone back and wiped that partition out. Nothing seems to work. Doesn't anyone have anything?
October 1, 2013 11:43:32 PM

OK. I used a Windows 7 install disk from a previous computer build and it worked fine. I then just used the license key from my new disk and it updated to the latest version of windows. I really don't know what the problem was. I suspect it was some sort of port conflict, but at least this worked.