New
#11
Did you look in Device Manager to see if you can find something for it ?
You could also try running Speccy and see what it shows.
Speccy - System Information - Free Download
Did you look in Device Manager to see if you can find something for it ?
You could also try running Speccy and see what it shows.
Speccy - System Information - Free Download
Yes, I knew that! Actually, I had originally thought the same thing, however, I would still expect something to show up in google. And that is not really happening.Code:No, I meant if it really is a misspelling of Maxtor, maybe they got the part number wrong too.
You got that notification from what?? That's not a windows notification. Where did you see it?
Download and run the 32 or 64 bit version (as matches your OS) of DevManView. Hit Ctl-F to find and search for Maytor. Anything match?
Ok, ran DevManView, and noticed I do have a Maxtor 6L200R0 ATA Device, drive.
Did the search thing and found this entry.
Code:Maytor!6M210S0! ! ! ! ! ! ! ! ! ! ! ! ! ATA Device (Standard disk drives) disk DiskDrive Disk drives IDE\DiskMaytor!6M210S0!_!_!_!_!_!_!_!_!_!_!_!_!_CAI41G10\5&25bf7624&0&0.1.0 Channel 0, Target 1, Lun 0 0x00000000 0x00000000 No No 10/20/2015 8:42:53 AM 10/20/2015 8:42:53 AM {00000000-0000-0000-ffff-ffffffffffff} Disk drive 6.1.7600.16385 disk.inf disk_install.NT 6/21/2006 10/20/2015 8:42:52 AMYes, it was a standard Windows notification dialog. The kind you get when a driver for a new device has been installed.Code:You got that notification from what?? That's not a windows notification. Where did you see it?
1. So you clearly connected a disk drive at 10/20/2015 8:42:52 AM that was enumerated with the name Maytor. That's when the driver was installed. Was that the Maxtor? In any case, Maytor and 6M210S0 are coming from the vendor firmware
2. That device isn't currently connected. (Maybe you connected an external Hard drive? It probably had the "Maytor" disk inside)? If you re-connect it and look under Device Manager Disk Drives I'd expect disk name will show Maytor.
3. Where did you get the text in your code box? i meant that's not the actual Windows message that pop's up when you connect a hard drive. Where did you get that string of text?
/* EDIT */
I forget... it may also be possible that device enumeration is coming from the HD enclosure itself.
/* EDIT 2 */
From an HD enclosure or also could result from a USB/IDE adapter to a hard drive
That's the problem. I did no such thing. That is why I started this thread. Did not connect any hardware.Code:1. So you clearly connected a disk drive at 10/20/2015 8:42:52 AM that was enumerated with the name Maytor. That's when the driver was installed. Was that the Maxtor? In any case, Maytor and 6M210S0 is coming from the vendor firmware for that disk
Code:3. Where did you get the text in your code box? i meant that's not the actual Windows message that pop's up when you connect a hard drive. Where did you get that string of text?
Yes, that is the actual text from the Windows dialog box. Copy / Pasted to this thread. Clearly the computer had installed a driver, I saw activity in the sys tray, then this dialog appeared.
No, I did not plug in any external devices.
No hard drives, usb thumb drives, cameras, ipods, ipads, etc.
Then i learned something new! Thanks :) never knew one could simply copy/paste the pop up bubbleYes, that is the actual text from the Windows dialog box. Copy / Pasted to this thread. Clearly the computer had installed a driver, I saw activity in the sys tray, then this dialog appeared.
Zip and attach C:\WINDOWS\inf\setupapi.dev.log to your next post
See attached.
Works with most dialogs. I have seen a few that do not.Code:Then i learned something new! Thanks :) never knew one could simply copy/paste the pop up bubble
I think Ctrl-C on a dialog box is one of the least known "features" of Windows. But being able to copy paste in situations like this is very useful to get the text copied w/o typos.
Yes. That is a head scratcher!
Data shows you booted at 6:10am. Then there's nothing till the "Maytor" disk install at 8:42am. Windows thinks it's Hardware Initiated. I interpret that to mean it has nothing to do with a USB device connection. Do you have more then one internal disk? Now i'm confused too. Also, that's the first mention of the "maytor" disk since start of log on 4/27/2015.
/* EDIT */
I'm curious. Open Device Manager. For each internal disk under Disk category, right click->Properties. Details tab. Use the pull down menu to select Hardware Id. Copy/paste the result into next post. Repeat for Compatible Id. And what model internal disk(s)?
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
Selecting Hardware Ids for the Maxtor will showCode:ide\diskmaxtor_6l200r0__________________________bah41g10\5&25bf7624&0&0.1.0
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.Code:ide\diskmaxtor_6l200r0__________________________bah41g10 ide\maxtor_6l200r0__________________________bah41g10 ide\diskmaxtor_6l200r0__________________________ maxtor_6l200r0__________________________bah41g10
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"
Likewise compare "Maytor" hardware Ids as received by Windows to hw ids for your Maxtor listed aboveCode:IDE\DiskMaytor!6M210S0!_!_!_!_!_!_!_!_!_!_!_!_!_CAI41G10\5&25bf7624&0&0.1.0
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 momentCode:ide\diskmaytor!6m210s0!_!_!_!_!_!_!_!_!_!_!_!_!_cai41g10 ide\maytor!6m210s0!_!_!_!_!_!_!_!_!_!_!_!_!_cai41g10 ide\diskmaytor!6m210s0!_!_!_!_!_!_!_!_!_!_!_!_!_ maytor!6m210s0!_!_!_!_!_!_!_!_!_!_!_!_!_cai41g10
/* 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
Last edited by ComputerGeek; 22 Oct 2015 at 14:01.