locked
Help with my DVD Drive. RRS feed

  • Question

  • Just got a new PC, running Vista Home premium.

    It has a TSSTcorp(Toshiba Samsung) CD/DVDW SH-S182D ATA device as the single CD/Dvd Drive.

    I am being told in my device manager

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

    Click 'Check for solutions' to send data about this device to Microsoft and to see if there is a solution available."

    I have obviously done this to no avail, I have tried uninstalling it and reinstalling it.

    If anyone has any technical advice as to 1) why in the hell its doing it in the first place
    2) what to do
    it would be a of a great help.

    All the drivers are up to date also.

    The device HAS been working as I used it to install alot of my periphrals, its just suddenly now it refuses to read. Before I call a premium rate helpline I thought I would ask here.

    Tuesday, March 20, 2007 9:38 AM

All replies

  • Wednesday, March 21, 2007 10:04 AM
  • FFury's link info works.  Re-installing the drivers may not work, but following the registry editing likely will.  I corrected this same problem yesterday myself.

    Link:   http://support.microsoft.com/kb/320553

     

     

     

    Wednesday, March 21, 2007 5:09 PM
  • Had the same problem, the solution FFury gave worked for me as well. Thanks for the help guys/gals
    Friday, May 18, 2007 10:50 PM
  • Hi, having the same problem but the link to the solution does not work.

    Any other ideas or info would be much appreciated.

    Thanks

     

    Monday, July 30, 2007 1:34 PM
  •  

    The Knowledge Base (KB) Article You Requested Is Currently Not Available

    sometimes we need more than a link

    I have the same problem & the link is dead

    Thursday, May 22, 2008 8:35 AM
  • MedievalFan or anyone else, I don't know if you are still interested in a solution to this problem.

    The solution is at this CURRENTLY AVAILABLE link:

    http://support.microsoft.com/kb/314060

    I had this problem just today and fixed it using the link above.

    Refer to the section specific to the Windows OS you have.


    Thursday, August 20, 2009 12:02 PM