XP CD-ROM drivers corrupt?

[Pu7o]

LOL. I just noticed that soo many people are only registering to say thank you. Most of them have only Posts 1 behind their name.

Not to mention that it's very unlikely that erdiko is actually reading the replies.

UserAgent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.5) Gecko/20060703 Firefox/1.5.0.5 (Swiftfox)

[Jammaniaclord]

DUDE!!!!

THANK YOU SO MUCH!!! This totally worked and solved an issue i have had since last November, but JUST now got around to fixing it. I bought two new DVD burners from Lite-On before i read this, but that is ok, because my OLLLLLLLD Yamaha CRW-F1 model was freaky deaky, and needed replaced. rest in peace Yamaha CDRW's!!!!!

God bless you techies, you make the common user, ot average userr, as well as the pro's, happy people when they need a fix.


ROCK ON!!!!!!

I had a similar error, and the problem also showed on on the 'virtual drives' with the error in the device manager. I know that the drives work fine, and the virtual drives being messed up further proves it is some type of driver error. I uninstalled the drives.. rebooted, reinstalled the drivers, rebooted and still have the same error message.. EXCEPT the error code is 41, not 39.

While reformatting and reinstalling windows would probably fix the problem, it would be a lot easier to just fix this problem without going through migration of the settings for each user to the new installation, and installing the 50 GB worth of programs installed on the system. (and imagine activating a lot of them over again also (eg Adobe CS2, Acrobat 7, Install Shield 11, etc...)

To fix this problem, I performed the following:


Start Registry Editor (Start, Run and type in [tt]regedit[/tt] then click)

Find "[tt]UpperFilters[/tt]" and "[tt]LowerFilters[/tt]" (and "[tt]UpperFilters.bak[/tt]" "[tt]LowerFilters.bak[/tt]", if they exist) value under the following key in the registry, and delete it:

[tt]HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E965-E325-11CE-BFC1-08002BE10318}[/tt]

Quit Registry Editor.

Reboot.

NOTE: You might need to reinstall any CD recording apps you have, if they start to not work completely, after doing this.


http://www.armorise.com
http://www.voiceofreality.com

BBCode format added by Admin

UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; en) Opera 9.0

[icedragon]

I have tried all that is listed as well as a repair program listed on another site named 'XP_CD-DVD-Fix'

None of this has worked, anyideas will be greatly appreciated.

ty

UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)

[icedragon]

Well I guess we have to re-format. I even tried a repiar on windows, but now it wont get past the AMS part and even the work arounds I have found in the net for that doesn't work.....MS this is BS, time for linux

UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)

[russian_seabass]

dude, I just registered for this site pretty much just to thank you. I have had the problem of the corrupt CD-ROM drive forever and just a second ago I tried your method and it worked perfectly. Made me feel like a complete moron, knowing that I spent days trying to figure it out when it could've been done in a second, using such a simple method. Anyways, thanks again dude.

Sebastian

UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)

[werddrew]

I'm gonna be another one of those who registers just to say how AWESOME of a fix this is... I've run into this in the past and just ignored it, but today, at work, a guy brought his laptop to me with this problem. I thought we'd have to reformat but I gave it ONE last google and BAM. Worked like a freakin charm.

I know he's prolly never gonna read these, but when a guy gets something so awesomely right, you just GOT to give him props. So here it is.

UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)

[jimtnc]

Count me in there too, and a year after the fact. Thanks, Erdiko. I was about to spend some bucks to resolve this, but you saved the day. Gotta also say thanks to Google, or I may not have found this site. Bravo, dude!!!!

UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)

[Pooz]

Another successful registry hack done here for this problem! Thank you very much for the info!! BTW, both keys found.

UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)

[tjanis]

When the PC boots up, the CD-ROM and DVD drives are not present. Going into the Device Manager displays the error icon for both devices. In trying to reinstall the driver, it displays a Code 39, and when the devices are removed (uninstalled), the system rebooted, the system detects the drives, attempts to install something, yet when they go back in the Device Manager, the Code 39 is still present.
tart Registry Editor (Start, Run and type in regedit then click)

Followed the this fix

Find "[tt]UpperFilters[/tt]" and "[tt]LowerFilters[/tt]" (and "[tt]UpperFilters.bak[/tt]" "[tt]LowerFilters.bak[/tt]", if they exist) value under the following key in the registry, and delete it:

[tt]HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E965-E325-11CE-BFC1-08002BE10318}[/tt]

Quit Registry Editor.

Reboot.

Upon rebooting cdroms drivers were indicated installed properly and the system stated all is working. Not true the cdroms won't read. Not quite - after shutdown and restart it will read once then nothing. CD burner cannot detect device. Have unistalled and reinstalled with no joy. Restoring the registry values puts it back to the original error code.

Am frustrated and looking for suggestions. Tks, tim

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.6) Gecko/20060728 Firefox/1.5.0.6

[rajesh_psycho]

I had a similar error, and the problem also showed on on the 'virtual drives' with the error in the device manager. I know that the drives work fine, and the virtual drives being messed up further proves it is some type of driver error. I uninstalled the drives.. rebooted, reinstalled the drivers, rebooted and still have the same error message.. EXCEPT the error code is 41, not 39.

While reformatting and reinstalling windows would probably fix the problem, it would be a lot easier to just fix this problem without going through migration of the settings for each user to the new installation, and installing the 50 GB worth of programs installed on the system. (and imagine activating a lot of them over again also (eg Adobe CS2, Acrobat 7, Install Shield 11, etc...)

To fix this problem, I performed the following:


Start Registry Editor (Start, Run and type in [tt]regedit[/tt] then click)

Find "[tt]UpperFilters[/tt]" and "[tt]LowerFilters[/tt]" (and "[tt]UpperFilters.bak[/tt]" "[tt]LowerFilters.bak[/tt]", if they exist) value under the following key in the registry, and delete it:

[tt]HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E965-E325-11CE-BFC1-08002BE10318}[/tt]

Quit Registry Editor.

Reboot.

NOTE: You might need to reinstall any CD recording apps you have, if they start to not work completely, after doing this.


http://www.armorise.com
http://www.voiceofreality.com

BBCode format added by Admin

erdiko i just love u for this....ur solution worked like butter...thanks...i turned out to br ur fan for this....:)

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.6) Gecko/20060728 Firefox/1.5.0.6

[tjanis]

When the PC boots up, the CD-ROM and DVD drives are not present. Going into the Device Manager displays the error icon for both devices. In trying to reinstall the driver, it displays a Code 39, and when the devices are removed (uninstalled), the system rebooted, the system detects the drives, attempts to install something, yet when they go back in the Device Manager, the Code 39 is still present.
tart Registry Editor (Start, Run and type in regedit then click)

Followed the this fix

Find "[tt]UpperFilters[/tt]" and "[tt]LowerFilters[/tt]" (and "[tt]UpperFilters.bak[/tt]" "[tt]LowerFilters.bak[/tt]", if they exist) value under the following key in the registry, and delete it:

[tt]HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E965-E325-11CE-BFC1-08002BE10318}[/tt]

Quit Registry Editor.

Reboot.

Upon rebooting cdroms drivers were indicated installed properly and the system stated all is working. Not true the cdroms won't read. Not quite - after shutdown and restart it will read once then nothing. CD burner cannot detect device. Have unistalled and reinstalled with no joy. Restoring the registry values puts it back to the original error code.

Am frustrated and looking for suggestions. Tks, tim

Hello:

After additional searching and experimenting I was able to solve my problem. It turned out it was a conflict with Roxio's Easy Creator Basic. I have/had an older version and it worked fine or so i thought. I discovered that Roxio indicated it was not compatible with WinXP and though they had one patch they didn't guarantee it would work. Mine worked fine until apparently one of the recent WinXP updates caused some sort of problem which led to the situation I described in my post. After unistalling Easy Creator all was back to normal. PS I did try to reinstall it with the patch but it created a new problem - WinXP wouldn't start. It would begin and then go back to boot over again and this became a continuos loop.

Hope this helps anybody else who may encounter the problem. Tim

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.6) Gecko/20060728 Firefox/1.5.0.6

[ripitt]

hi, i looked at this thread because i have the same type of problem.

the idea to go to regedit and delete certain files as posted by 'erdiko' worked a treat for me, thanks for the help.

rich

UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; SV1)

[fastzcar]

This is a great fix. I originally found it on MS's site ( http://support.microsoft.com/kb/314060/EN-US/ ) about a year ago and it worked great for me....

This seems to happen on loads of Dell 'D' series Latitude notebooks. This could just be my perception of the issue though as all we use is Dell Latitudes. I am the only remote support tech for a company that has about 400+/- notebook users (not all notebook users are remote users though).

The first time I saw the issue I was completely baffled, and since I have been doing this for a while (14+ years) that doesn’t happen often. Anyway once I corrected it I had no time to 'play' as the user really wanted their system back. I did recreate the bad registry entries on another identical system. However the drive was still there and I couldn’t actually recreate the problem.

Today I ran into this again while porting a D600 image to a Dell D610. After futzing with it for a while my memory finally kicked in and I looked up my notes on the problem. I first exported the entire registry key at [tt]{4D36E965-E325-11CE-BFC1-08002BE10318}[/tt]. I then deleted the value data for both keys (NOT the values themselves) and (of course) it worked. Since I was now confident that I could fix the problem I decided that I wanted to play with it and see if I could come up with anything.

I imported the 'crap' code back in, rebooted and the issue was here again. In this particular XP load the registry is calling 'Cdr4_xp.sys' for the LowerFilters and 'pwd_2.sys' (read on about this file) for the UpperFilters value data. So I surmised that one of these files was corrupted and when the VXD loads it was causing the problem. I removed the first value data field of 'Cdr4_xp' and rebooted...the problem was still there. I replaced the buggy reg entry again and removed reference to the second value data field of 'pwd_2' and again rebooted the system. Still nothing; no drive will recognize.

So I decided that I would compare these files to my system (which doesn't and has never had this problem). I pulled up the properties for 'Cdr4_xp' and compared these with the file on my system. Same file version and size. So I went looking for 'pwd_2' and low and behold here is a surprise. I didn’t have this file at all. So I checked the 'problem' computer and it didn't have this file either! I did however have 'pwd_2k.sys" in the [tt]C:\windows\system32\drivers\[/tt] folder.

I *thought* (we all know where thinking gets us) that had I found the problem. My theory was that somehow the registry got ganked up and it’s calling the file by the wrong name (calling 'pwd_2' instead of 'pwd_2k'). I made the registry change to add the 'k' and now the value data is actually associating with a file. I rebooted the system (all smug and confident that I found the real problem) expecting the drive to work just fine; WRONG! The same problem....

At this point I decided that I would copy all the drivers and the registry key from my system (the one without the issue) to the problem system. After importing the files and reg key I checked the key and, yep, the key now matches my 'known good' setup. Rebooted the system and the @#$%in issue is still happening! At this point I decided I had followed the rabbit trail enough and decided to call it quits. I deleted my now heavily modified value data fields for UpperFilters and LowerFilters and shut the system down. Something stuck in my mind though and after writing most of this post I decided to double check my work. I rebooted the system. I was glad that I did! The value data entry’s for these values were now blank - but the drive again wouldn't work! I had to re-import the original registry settings, reboot, remove the value data entry’s again, and reboot again to correct the problem. It seems on this one XP didn't really care that the fields were blank; it only worked when I deleted the original value data info! Now that is WIERD!

Oh well! Wish I could have solved it for real. I am stashing this one away as a rainy day problem..... This is a great fix. I originally found it on MS's site ( http://support.microsoft.com/kb/314060/EN-US/ ) about a year ago and it worked great for me....

This seems to happen on loads of Dell 'D' series Latitude notebooks. This could just be my perception of the issue though as all we use is Dell Latitudes. I am the only remote support tech for a company that has about 400+/- notebook users (not all notebook users are remote users though).

The first time I saw the issue I was completely baffled, and since I have been doing this for a while (14+ years) that doesn’t happen often. Anyway once I corrected it I had no time to 'play' as the user really wanted their system back. I did recreate the bad registry entries on another identical system. However the drive was still there and I couldn’t actually recreate the problem.

Today I ran into this again while porting a D600 image to a Dell D610. After futzing with it for a while my memory finally kicked in and I looked up my notes on the problem. I first exported the entire registry key at [tt]{4D36E965-E325-11CE-BFC1-08002BE10318}[/tt]. I then deleted the value data for both keys (NOT the values themselves) and (of course) it worked. Since I was now confident that I could fix the problem I decided that I wanted to play with it and see if I could come up with anything.

I imported the 'crap' code back in, rebooted and the issue was here again. In this particular XP load the registry is calling 'Cdr4_xp.sys' for the LowerFilters and 'pwd_2.sys' (read on about this file) for the UpperFilters value data. So I surmised that one of these files was corrupted and when the VXD loads it was causing the problem. I removed the first value data field of 'Cdr4_xp' and rebooted...the problem was still there. I replaced the buggy reg entry again and removed reference to the second value data field of 'pwd_2' and again rebooted the system. Still nothing, no drive will not recognize.

So I decided that I would compare these files to my system (which doesn't and has never had this problem). I pulled up the properties for 'Cdr4_xp' and compared these with the file on my system. Same file version and size. So I went looking for 'pwd_2' and low and behold here is a surprise. I didn’t have this file at all. So I checked the 'problem' computer and it didn't have this file either! I did however have 'pwd_2k.sys" in the C:\windows\system32\drivers\ folder.

I *thought* (we all know where thinking gets us) that had I found the problem. My theory was that somehow the registry got ganked up and it’s calling the file by the wrong name (calling 'pwd_2' instead of 'pwd_2k'). I made the registry change to add the 'k' and now the value data is actually associating with a file. I rebooted the system (all smug and confident that I found the real problem) expecting the drive to work just fine; WRONG! The same problem....

At this point I decided that I would copy all the drivers and the registry key from my system (the one without the issue) to the problem system. After importing the files and reg key I checked the key and, yep, the key now matches my 'known good' setup. Rebooted the system and the @#$%ing issue is still happening! At this point I decided I had followed the rabbit trail enough and decided to call it quits. I deleted my now heavily modified value data fields for UpperFilters and LowerFilters and shut the system down. Something stuck in my mind though and after writing most of this post I decided to double check my work. I rebooted the system. I was glad that I did! The value data entry’s for these values were now blank - but the drive again wouldn't work! I had to re-import the original registry settings, reboot, remove the value data entry’s again, and reboot again to correct the problem. It seems on this one XP didn't really care that the fields were blank; it only worked when I deleted the original value data info! Now that is WIERD!

Oh well! Wish I could have solved it for real. I am stashing this one away as a rainy day problem.....

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.7) Gecko/20060909 Firefox/1.5.0.7

[chii07chobits]

I can't erase the UpperFilters and LowerFilter it says error also the default in 4D36E965-E325-11CE-BFC1-08002BE10318..I don't know if this solve my problem because when i click my cd drive and to properties it does not show any problem but when i put cd in my cd drive it cannot read nothings happening...somebody help me..it's driving me crazy i can't use cds in my computer pleaseee somebady????PLEASEE

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6

[Med]

Hi there all.

First of all a big thank you to erdiko.

Second, I'd like to add something that I noticed as a side effect of this problem.
I had this happen a few days ago on my 2nd puter. The problem started when the 2 m.o NEC 4571A started slowing down incredibly when copying DVDs. Really wierd...going from a typical 12-17min for a DVD9 (dual layer disc) all the way up to 50-55min per disc!

Naturally, I thought the worst (that I might have a lemon and it'd worn out already) cos it is copying continuously for 12hrs/day and has been for about three weeks straight...yes, I'm copying ALL my DVD collection! And BTW, I have a medium size (approx 20") standalone fan blowing on the open case while I copy to keep the unit nice and cool and prolong it's lifespan.

It was copying fine for just over two weeks then it got bad a few days ago, ie: EVERY disc was taking nearly an hour to do...and of course, all this when there was nothing else happening on the computer, ie: no other HDD activity etc. So I tried playing round, checking the HDD for errors etc but nothing. Then I started disabling a couple other things at startup like WinDVD Manager, Quicktime and crap like that. Then the bloody drive disappeared on next reboot.

Lucky I found this thread right at the top of the google search results. So, after deleting the reg entries it's cool and now copies real quick like before. Back to a 7 or 8GB disc done in 15 mins average. Happy as Larry now I tell ya.

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.7) Gecko/20060909 Firefox/1.5.0.7