Page 1 of 1

DVD Rom Drivers Gone Corrupt!

PostPosted: Tue Dec 07, 2004 10:33 pm
by MysteryMan
After months of trouble free use, my DVD Writer has suddenly stopped working in Windows XP.

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

If I try to 'Update Driver' it says that it cannot find a better one!

If I uninstall then the next time it boots it detects the drive and installs but still doesn't work.

It is a Pioneer DVR-106 and I cannot find a driver for it as it is built into Windows XP.

Heeeeeeeeeeeeeeeeeeeeellllllllllllllllllllllllllllppppppppppppppppppp!

PostPosted: Tue Dec 07, 2004 10:58 pm
by Gecko
Try from Pioneer

PostPosted: Tue Dec 07, 2004 11:32 pm
by MysteryMan

PostPosted: Wed Dec 08, 2004 12:46 am
by PCguy

PostPosted: Wed Dec 08, 2004 12:53 am
by Gecko
You might want to read from Microsoft about Code 39 errors.

PostPosted: Thu Dec 09, 2004 1:27 pm
by MysteryMan
Tried the Registry fix - only the Lowerfilters value was there. Deleted it and rebooted, but, no difference!

Ran a Windows 'Repair' on the PC, which seemed to re-install a load of drivers.

The good news is that this fixed the problem with the CD/DVDdrive.

The bad news is that I now have the same error message showing up for the 'BIOS Motherboad Monitor' whatever that is and also my modem/Broadband connection doesn't work anymore.

Having uninstalled/re-installed the drivers a load of times, as suggested by VirginNet techies, it seems to be knackered.

I have reached the point where it looks like a rebuild of the PC is required (oh joy!)

PostPosted: Thu Dec 09, 2004 2:49 pm
by Un4g1v3n
Or just reinstall Windows XP.

Format your harddrive and reboot it with the Windows XP cd in the cd drive. XP setup should commence normally. By formatting and then reinstalling windows, it gets rid of all the old information that windows saved and will make new info for the computer to use. Also it should auto-detect all your devices and load drivers for them.

If this doesnt work, THEN you should rebuild your computer, or do whatever it is you planned to do.

Hope this helps.

PostPosted: Thu Dec 09, 2004 4:40 pm
by venney
MysteryMan your display pic reminds me of Gaston from disneys beauty and the beast lol, you know the sleezy bloke thats got his eye on Bell. Doesnt look like him but reminds me of him!
Same sort of drawing.
Whats your pic from?

Venney
:)

PostPosted: Thu Dec 09, 2004 7:26 pm
by Un4g1v3n
venny - lol. i know who you're talking about, but that post was pointless. sorry to say. funny though :)

PostPosted: Thu Dec 09, 2004 11:18 pm
by Gecko
Before you reinstall XP you can try windows built-in System file checker.

Put your windows XP CD in your CD Rom drive
Click > Start > Run type “command” (without the quotes) and press enter.
Now at the command prompt type “sfc /scannow” (without the quotes) and press enter.

This will start the system file checker and replace any changed or damaged
system files with ones from the XP CD.

If you system now runs ok then go to windows update and let Microsoft update anything needed.

Update on situation....

PostPosted: Wed Dec 15, 2004 4:37 pm
by MysteryMan
Firstly, to Venney..... the display picture is a caricature of the late, great Frank Zappa. Sorry, can't remember where it came from. Aficianados will also recognise my username as further homage to a unique talent!

Right, back to the plot.....
No amount of re-installing would get my Modem to work again, so, I took the plunge and re-installed XP from scratch.

During the week or so since then, I have seen similar problems showing up with various pieces of hardware (USB Enhanced Controller, BIOS Motherboard Monitor and a few others that I cannot remember).

They all showed up with Driver problems (normally Code 39 with the occassional 37 thrown in for good measure!) and the weird thing is that they all seem to have corrected themselves over time!!!!

Whilst I am glad that there are no problems being flagged up at the moment and everything seems to be working OK, I am a bit nervous and wonder if this is a symptom of something else - maybe it's a RAM or Motherboard problem that will come back at some point. Maybe it is a virus or something.

Does any of this make sense or sound familiar to anyone?