jbclem said:
I finally got back to this problem, I hope you're still watching...
I've tried a bunch of different types of CDs and DVD's. On a few of them I
can see folders, and the files inside the folders. On one I could read a
text file, but the rest of the them even when I could see a file I couldn't
read/view it or run it.
Looking at the Event viewer/System just now...Nothing generated in Event
Viewer even though I was trying to play an audio CD that had opened up WMP
and was flipping through the tracks, giving one split second burst of sound
then on to the next track.
I next tried a disk onto which yesterday I had burnt(with this Asus device)
a television program (I booted up the computer with a bootCD and the Asus
CD-ROM device worked absolutely normally). Using VLC all I got was a blank
window with the heading "select one or more files to open". The Event View
did produce a bunch of identical "warnings" that said: "an error was
detected on device\Device\CdRom0 during a paging operation". Strangely,
when I tried this disk a second and third time it didn't generate those
warnings.
After I hard burnt this television program, and two movies (on a different
disk), I played them and they played perfectly while in the miniXP from the
bootupCD. Thus it really seems that the device itself is working fine, and
the problem is restricted to the Windows XP installation.
I also tried (again) uninstalling the device in Device Manager, rebooting
the computer, but the nothing changed.
That's more or less what I found in this article. They tried uninstalling
the device. The storage installation idea, helps with UDMA issues (takes a
device out of PIO mode and puts it back in higher speed access mode UDMA).
Other than that, I'd be concerned that whatever "driver" is there now, will
just reinstall itself.
http://techsnsecurity.blogspot.com/2012/02/an-error-was-detected-on-device.html
You can do
devcon gencdrom stack
using the 32 bit version of devcon from Microsoft.
http://support.microsoft.com/kb/311272
That's to check for anything out of the ordinary. A reinstalled device
could still pick up a filter driver, all on its own. I use the
Acronis Capacity Manager driver for 3TB hard drives, and it
installs itself for everything. I would not expect that
driver to go away, without work. In fact, for that one, at
one time, you had to use a separate removal tool, because
there was no uninstaller for it.
If you do
devcon gencdrom stack > output.txt
notepad output.txt
that will store the few lines from that command, into a text
file for you. You can then open that text file in Notepad,
and copy and paste what you see in there.
*******
Devcon is just an easy way to get the same information as you can
see in Regedit. In the above web page, that person is checking the
UpperFilter entry, and his reads "GearAspiWDM". That would be Apple
iTunes, old version, which installs a third party CD burner program from
Gear Software (Apple doesn't do it that way any more). Aspi is the
old stack for burning stuff, using SCSI command blocks (CDB). The
SCSI stack is used to make it easy for third parties to add drivers
for storage. At one time, Windows was cursed with multiple versions
of ASPI files, some of which the user was expected to install themselves
(get the Adaptec files). I don't recollect having to know anything
about ASPI on this machine.
http://en.wikipedia.org/wiki/Aspi
A free utility Nero Infotool.exe used
to list all the ASPI related stuff in your OS, in an attempt
to make it easier to figure out the ASPI stuff. Again,
I haven't needed this in some time, and can't remember
any details. It appears Nero itself installed an ASPI
driver. That's the only one listed.
*******
For someone here, they reseated the cables on the drive (with the
power off).
http://forums.storagereview.com/index.php/topic/21796-event-id-51-cd-rom-error/
It's possible to have a rootkit on a computer (invisible malware),
which infects atapi.sys. You would need a rootkit scanner to have
a chance to find it. Kaspersky makes TDSSkiller for example, which
removes TDSS/Alureon. While Malwarebytes has MBAR for Rootkits,
I really don't know which is the most effective product for those.
*******
Let's hope it is just a loose cable.
The specs for the drive, say that it is SATA. And the
24 in the part number (24B1ST) tell me it's a relatively
new 24x speed drive. If this was a ribbon cable drive,
I could have more faith in a "reseat the cable" fix.
But with SATA, and the fact you've been able to
read some stuff, this sounds more like a software
problem. And that "paging error" thing, that's just
not normal at all. It smells a bit like malware.
I was going to go on a tirade about ribbon cables, but
now that it looks like SATA, I can save that for another day.
This program from Kaspersky (TDSSKiller), sniffs for rootkits.
I've run this once on the machine here (as a test), and I think
it leaves files on the machine.
http://support.kaspersky.com/viruses/disinfection/5350?qid=208280684#block1
TDSS is usually pretty good about patching bugs. When Microsoft
sent out a Windows Update, with a new version of atapi.sys,
it caused TDSS infected machines to have problems. The people
running all the machines with TDSS on them (botnet), pushed out a
patch within two days, such that any more attempts to install the
Windows Update in question, would suffer no side effects. You
could say it is "actively developed" malware.
*******
Now, this one, it was the combination of Roxio and Nero, and
it managed to create that paging error thing. Unbelievable.
I would never have thought such a software could "make up" a
paging error.
http://www.bleepingcomputer.com/forums/t/315508/dvd-drive-wont-burn/
And the evidence might be present in the devcon output, as if
there were filter drivers present, the names in there would
hint at possible software culprits.
That one message from Event Viewer, is a gold mine in terms
of searching for examples.
Paul
