M
Me
Continuing saga...
I've been experiencing sudden re-boots in XP Pro. Tried many things to
repair this. It happened again when I ran a virus scan on a CDR. I think
I've found a virus attached to an archived file. I duplicated this by
scanning the disc again, and sure enough -- reboots when it hits a file on
the CDR. (Scans too fast to identify which file.)
But...
Windows picked the failure up this time and issued an error report that,
when processed, showed up as an "error caused by a device driver" (unable to
identify what driver or device).
My inclination is to simply discard this CDR, but I am confused by this
"device driver" identification. There is data on the CDR that I want, but
not at this price; on the other hand . . .
Any thoughts?
I've been experiencing sudden re-boots in XP Pro. Tried many things to
repair this. It happened again when I ran a virus scan on a CDR. I think
I've found a virus attached to an archived file. I duplicated this by
scanning the disc again, and sure enough -- reboots when it hits a file on
the CDR. (Scans too fast to identify which file.)
But...
Windows picked the failure up this time and issued an error report that,
when processed, showed up as an "error caused by a device driver" (unable to
identify what driver or device).
My inclination is to simply discard this CDR, but I am confused by this
"device driver" identification. There is data on the CDR that I want, but
not at this price; on the other hand . . .
Any thoughts?