CD/DVD player not reading dvdr after clean install 7

imymeohmy

Reputable
Nov 25, 2014
5
0
4,510
Hiii, if someone can help solve my dilemna I will very thankful.
I have a VAIO vista and upgraded to windows 7. Everything worked well till one day my cd player stopped reading dvdrs., they just came up blank. After searching the internet I fixed it... fastforward a couple months and it stopped reading dvdrs again. This time I couldn't figure it out so I reformatted my computer but this time did a clean install of windows 7. It worked again. I ran into other small problems but fixed them downloading drivers and using windows7 companion cd.... now a day later it stopped reading dvdrs again. Can someone help?? I don't know what the problem is!!

Does anyone know what to do ...🙁
 
Solution
Regarding this, process of elimination is the best bet at identifying the culprit. So far, software has changed over the time you've had this issue, but from what I see hardware has not. If at all possible, try to swap out the drive for another one, ensuring that you place this drive in another computer. Run it for a while. See what happens. If the other computer experiences the same issue, you have a good shot at saying it's the drive itself that is causing these issues. If your rig generates this issue on the drive that you are using temporarily, you know that, at the very least, something about your rig is causing the issue. Once we know that, we can try and narrow it down a bit more until we find what is really causing this whole...
have you checked device manager to see if the driver is not working, should have a yellow! if there is a problem.

you could try restoring back to a time when the CD/DVD drive was working, using system restore.

char
 


  • I checked device manager and there's no yellow, I tried updating anyways
. I would do system restore but Im worried it's going to go back to before I installed the companion DVD which added all the necessary drivers that I needed for windows 7
 
Regarding this, process of elimination is the best bet at identifying the culprit. So far, software has changed over the time you've had this issue, but from what I see hardware has not. If at all possible, try to swap out the drive for another one, ensuring that you place this drive in another computer. Run it for a while. See what happens. If the other computer experiences the same issue, you have a good shot at saying it's the drive itself that is causing these issues. If your rig generates this issue on the drive that you are using temporarily, you know that, at the very least, something about your rig is causing the issue. Once we know that, we can try and narrow it down a bit more until we find what is really causing this whole thing. If it's not possible to do it's ok, t'would just be helpful.
 
Solution