HL-DT-ST DVRAM GT30N Issues with reading disks.

Maybe someone could put me out of my misery? I have a Lenovo W510 running Windows 7 Pro x64. My problem is with the optical drive, or its related software. I recently went to burn a Memtest iso in an effort to troubleshoot a display driver problem I was experiencing. The strange thing is that the iso did burn, but when it is placed into the optical drive, the windows auto start screen comes up for a blank disk (doesn't recognize that data is present). If I insert an audio disk that was burned on the drive, it does the same thing, even though it has music on it (verified by playing on a CD player) yet, if I put a commercially made audio disk in, it plays with no problems.

Anyone experience anything like this before, and can offer a solution?

Thanks for the reply and suggestion. Cleaning the lens was the first thing I did. It wasn't really dirty, but I cleaned it anyway. Last night I experimented a little, and it can actually read disks burned by another computer/drive. It seems like it just won't read the disks that were burned on it. I uninstalled the driver, and it reinstalled showing that the drive was working properly, went through the removing upper (no upper in my case) and lower filters in the registry without any effect. This thing has got me stumped.

That's the problem. A disk burned on this PC works with no problem in another PC, or a CD player for audio disks, but when it is placed in this drive (the one that actually burned it), I get the blank disk message. The drive will read pre recorded CDs, and disks that have been burned on other machines.

I would agree but the odd thing is that disks created in other drives are readable in this drive. The last disks I burned were using InfraRecorder. The only disks this drive can't seem to read are the ones that were burned on it.

Somehow this was marked solved? It is not, despite the assistance given. Perhaps I hit the "Mark Solved" by mistake instead of "Post Quick Reply"? If ANYONE has a handle on what this problem is rooted in, I would greatly appreciate some insight.

I would think that if the problem was hardware, it would appear on all disks. What kind of hardware problem would present itself on only the disks that were written by the drive itself? Kind of a conundrum.