CDs burn with no errors, but then finalized cd is blank

[dancebabe295]

Sooo I got a whole new drive and installed it and it is still doing the same thing. Still reads DVD's and CD's but won't write anything on blank ones. Gahhh, any other ideas?

[CCT]

It is NOT without possibility that the replacement is in the same condition as the original.

That being said, one last round of 'checks' per Step 8 @; http://www.ehow.com/how_4518206_fix-...ve-issues.html


and this -> http://support.microsoft.com/kb/320174

[dancebabe295]

Alright, I tried all the things in Step 8. There were only two lower filters at the HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/Class/4D36E965-E325-11CE-BFC1-08002BE10318 so I deleted them and at the HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Policies\Explorer, there was no Explorer file inside of policies, only a file "Default, type REG_SZ, value not set". At HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\policies\Explorer, there are two files, "Default, type REG_SZ, value not set", and "BindDirectlyToPropertySetStorage, type REG_DWORD, value is set at 0". I then uninstalled the CD/DVD drive and IDE ports then re-installed them by searching for the hardware changes just like it says to do. Tried to burn again, and still end up with a blank cd.

Inside c:\windows\inf\cdrom.inf, there is a cdrom and a cdrom.dnf file. When I selected to install the cdrom file, I received the error "The INF file you selected does not support this method of installation."

In the second link, the solution download was for xp, and I am running vista. I did, however, select the link for vista solutions and ran the Microsoft Automated Troubleshooting Service. When it was done, it said "Troubleshooting is complete, however, we did not detect any issues common to this problem and therefore, no fixes were applied." I can view the detail troubleshooting report though, so here is what it says:

1.Class filter drivers are corrupt - Checked
One or more class-specific filter drivers are missing/corrupt

Repair class filter drivers - Not Run
Remove missing/corrupt class filter driver references

2.Device filter drivers are corrupt (TSSTcorp CD/DVDW TS-L632D ATA Device) - Checked
One or more device-specific filter drivers are missing/corrupt

Uninstall device - Not Run
Uninstall the problem device

3.Device is not working properly (TSSTcorp CD/DVDW TS-L632D ATA Device) - Checked
This device is experiencing a problem that is preventing it from working properly

Rescan devices - Not Run
Check for changes in available devices

Uninstall device - Not Run
Assign drive letters to all drives that do not have drive letter

4.Drive is disabled (TSSTcorp CD/DVDw TS-L632D ATA Device) - Checked
the CD/DVD drive have been disabled in Device Manager

Enable the device - Not Run
The device must be enabled before it can be used

5.Drive is not assigned a drive letter - Checked
The CD/DVD drive is not accessible via an assigned drive letter

Assign drive letter - Not Run
Assign drive letters to all drives that do not have drive letter



Though it says all these problems are occurring, #5 is confusing because the drive shows up in My Computer as drive D, just like normal, and so is #4, becuase the drive is enabled in Device Manager.

[CCT]

I suggest you try and 'fix' any corrupt system files via System File Checker.

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

I would also suggest you clean the driver cache first so the system rebuilds from the install disk (you have to have an install disk - if not, disregard this post)

the commands' are:

sfc /purgecache

then

sfc /scannow

[dancebabe295]

Alright, here is the finished cmd screen:

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Windows\system32>sfc/scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some of th
em.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
C:\Windows\Logs\CBS\CBS.log

C:\Windows\system32>Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Windows\system32>sfc/scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some of th
em.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
C:\Windows\Logs\CBS\CBS.log

C:\Windows\system32>



I went to look at the detailed log, but it says "Access is denied."

Also, I am away at school and my install disk is somewhere at home =(

[CCT]

CBS.log analysis Vista -> http://support.microsoft.com/kb/928228

[dancebabe295]

I did everything it told me to, and it came back with nothing. No log or anything. I tried typing it in four different times just to make sure I typed it all correctly and still nothing

[CCT]

You are at the point where, if it were me, I'd copy everything I valued off and re-install (thank goodness it still reads).

Did you follow street1's advice in post 8 ?

I am out of ideas.

[slgrieb]

Actually, I'm still inclined toward the hardware explanation, the only reason I'm a little ambivalent is some of the messages generated by the MS repair utility. There is certainly malware that can disable a CD drive, but I just don't know of any that leaves other functions intact but prevents burning. I also can't find information on a nasty that really seems to fit the profile.

If I understood you correctly, dancebabe, your replacement drive is used, so I think a defective replacement drive is really likely. TSST makes really crappy drives, and I doubt if the drive was tested before it was sold.

A well set up shop could test the drive with a different computer, but there isn't any easy way for most people to do it because they don't have the adapters and connectors you'd need to plug the drive into, say, a desktop system. But you might be able to try it in another laptop.

I can't rule out some weird Windows glitch, but I just don't think that's what's happening. I'd try to return the drive and pick up a new (unused) replacement for the replacement.