Vista - cd rom problems in x64 vista

Windows cannot access either of my dvd rom drives, the following message is
displayed in device manager.

Windows cannot load the device driver for this hardware. The driver may be
corrupted or missing. (Code 39)

It seemed to happen after I installed Nvidia's Nforce4 drivers. I
uninstalled the nvidia drivers and the problem still exists. I also tried
replacing the cdrom.sys file to no avail. Any thoughts??

"@ngeLCD" wrote:

> Windows cannot access either of my dvd rom drives, the following message is
> displayed in device manager.
>
> Windows cannot load the device driver for this hardware. The driver may be
> corrupted or missing. (Code 39)
>
> It seemed to happen after I installed Nvidia's Nforce4 drivers. I
> uninstalled the nvidia drivers and the problem still exists. I also tried
> replacing the cdrom.sys file to no avail. Any thoughts??

I just bought a Gateway GT5412 and it has the same issue with the factory
installed DVD drive. Actually, I bought the first at Fry's, then took it
back because I thought it was a hardware failure...got a new one at Circuit
(Fry's was out) and it has the same issue. Gateway suggested I could 'try'
restoring the sytem and that just teed me off...not good, bad product.

I had this problem with my 32 bit Vista. I fixed it with system restore. I
went back to the day before I noticed the problem.
--


"@ngeLCD" wrote:

> Windows cannot access either of my dvd rom drives, the following message is
> displayed in device manager.
>
> Windows cannot load the device driver for this hardware. The driver may be
> corrupted or missing. (Code 39)
>
> It seemed to happen after I installed Nvidia's Nforce4 drivers. I
> uninstalled the nvidia drivers and the problem still exists. I also tried
> replacing the cdrom.sys file to no avail. Any thoughts??

I have a very similar problem to you, I have a dvd burner- Lite-ON DVDRW
SHW-160P6S ATA, and a DVD drive - JLMS XJ-HD166S, both have up to date
drivers and are recognized by device manager and in bios, although neither
one will appear in "my computer" or will pick up when a cd is put(when
windows is running), any help would be appreciated! Thanks

On Feb 19, 11:47 pm, GAdog <G...@discussions.microsoft.com> wrote:
> "@ngeLCD" wrote:
> >Windowscannot access either of mydvdromdrives, the following message is
> > displayed in device manager.
>
> >Windowscannot load the device driver for this hardware. The driver may be
> > corrupted or missing. (Code 39)
>
> > It seemed to happen after I installed Nvidia's Nforce4 drivers. I
> > uninstalled the nvidia drivers and the problem still exists. I also tried
> > replacing the cdrom.sys file to no avail. Any thoughts??
>
> I just bought a Gateway GT5412 and it has the same issue with the factory
> installedDVDdrive. Actually, I bought the first at Fry's, then took it
> back because I thought it was a hardware failure...got a new one at Circuit
> (Fry's was out) and it has the same issue. Gateway suggested I could 'try'
> restoring the sytem and that just teed me off...not good, bad product.

I went throught the same problem with a computer I built. All
functions worked until I downloaded the updates then the dvd drivers
became corrupted on my new and old computer. You have to reload vista
and do not update until the driver problem is fixed and who knows how
long that is going to be. It took me many reloads and much frustration
to find a way to use vista. Microsoft appears to have a big problem
brewing in this area.

I have a similar problem: I have an XPC Barebones SD37P2 with a PIONEER
DVD-RW DVD-111D ATA installed. During a recent Vista update the driver (or
registry) had become corrupted. Microsoft Vista could not find an online
solution. A volume error check did not resolve the problem. The problem
however is that the driver is Microsoft's (cdrom.sys), generic and undamaged
; as I am able to copy the driver into another folder; yet Windows will not
let me recopy the driver back into the System32\drivers folder. This is then,
by all evidence, a registry problem.

I tried finding
"HKEY_LOCAL_MACHINE/System/CurrentControlSet/Control/Class/{4d36e965-e325-11ce-bfc1-08002be10318}" in Regedit, but no such animal.

I also have the same problem with the Teredo Tunneling Pseudo Interface
driver which is MS's Tun Miniport Adapter.

Hasn't anyone a solution hereto?