Had a look through your log. (I no longer need any info requested in my last post). Here's my best
guess analysis
You have an internal Maxtor. In DevMgr, right click
Properties then
Details tab. Use pull down menu select
Device Instance Path. Footnote:
Per Windows spec, every device connected to a machine has a Device Instance Path which guaranteed to be unique across all devices attached to the machine
Device Instance Path of your Maxtor
Code:
ide\diskmaxtor_6l200r0__________________________bah41g10\5&25bf7624&0&0.1.0
Selecting
Hardware Ids for the Maxtor will show
Code:
ide\diskmaxtor_6l200r0__________________________bah41g10
ide\maxtor_6l200r0__________________________bah41g10
ide\diskmaxtor_6l200r0__________________________
maxtor_6l200r0__________________________bah41g10
For unknown reason i can't explain, on the day in question: Windows performed device enumeration with the Maxtor and received a mangled set of Ids. The Ids are sent by Maxtor disk h/w and firmware over the PCI bus and received by the PCI bus chip controller. Don't know where they were mangled but once received, Windows saw it as a new disk so installed its drivers.
This is the "Maytor" Device Instance Path. IMO The strings basically vary by character substitution so IMO are mangled versions of each other. The mangled
Device Instance Path of your "Maytor"
Code:
IDE\DiskMaytor!6M210S0!_!_!_!_!_!_!_!_!_!_!_!_!_CAI41G10\5&25bf7624&0&0.1.0
Likewise compare "Maytor" hardware Ids as received by Windows to hw ids for your Maxtor listed above
Code:
ide\diskmaytor!6m210s0!_!_!_!_!_!_!_!_!_!_!_!_!_cai41g10
ide\maytor!6m210s0!_!_!_!_!_!_!_!_!_!_!_!_!_cai41g10
ide\diskmaytor!6m210s0!_!_!_!_!_!_!_!_!_!_!_!_!_
maytor!6m210s0!_!_!_!_!_!_!_!_!_!_!_!_!_cai41g10
No idea if this event indicates anything significant (like something is failing) vs. it's just a blip. I'd just keep an eye for any future strangeness. If it were me, I wouldn't be too worried about it for the moment
/* EDIT */
On quick look, i didn't see a firmware option for your drive. But you might try the Seagate tools to check firmware revision level and if there's an update. As Seagate/maxtor merged am
guessing the seagate tool is appropriate for the job