Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[rheacock]

I bought a Maxtor 1.5T external USB 2.0 drive.  Since the latest upgrade of MC 12, 12.0.207, when the drive is plugged in, I get a BSOD every time.  The error seems to be the USB drivers.  I don't get the errory any other time, only when opening MC.

XP SP 2 - All current on MS patches
Pending D 3.4ghz
3G ram

With Maxtor attached, 4.1T disk space.

Any ideas?

[InflatableMouse]

No idea, but I would try splitting it up in 2 volumes to see what happens.

Have you tried completely removing MC12 and reinstalling it?

MC12 settings and library can be backed up so you won't have to go through all options. Search for a script from glynor.

[JimH]

A Blue Screen is a hardware problem.  Could be the drivers for the device.  We did see a Maxtor problem a year ago that was fixed by updating their drivers.

[rheacock]

I have un-installed and re-installed MC, no help.

I have not split the volumes, can't now, I have too much stuff on it.

If it were strictly a hardware issue, it would crash at other times.  The ONLY time the system crashes, is when I open, just open, MC with that drive turned on, I get the BSOD within 10 seconds. 

I can access any and all files using other tools, Windows Media Player, Nero, etc.  I can even access the files using MC from another machine on the network, works fine.

In my personal opinion, there is some major buffer overflow, memory leak, etc that's in major conflict between the USB Drivers and MC.

I've looked on Maxtor's site, there is no driver updates or flash updates for the drive.

Could it be the total volume of disk space on the machine?

[JimH]

If it were strictly a hardware issue, it would crash at other times. 

Unfortunately, this isn't true.  No two pieces of software affect a system in the same way.

Did you look for driver updates or contact Maxtor?

If you don't believe me, try reading this thread:
http://yabb.jriver.com/interact/index.php?topic=24031.0

There are 3 Maxtor problems listed there but you may find something useful in other posts.

[InflatableMouse]

Blue screens aren't per definition a hardware issue.

Do you have the event log error?

What STOP error does it generate? Have you tried finding more info about that specific error? Paste it here if you have it and I may be able to help you find more info about it.

[rheacock]

Reply to both posts:
Did you look for driver updates or contact Maxtor?
Yes, they have no updated drivers or firmware for the drive.

If you don't believe me, try reading this thread:
http://yabb.jriver.com/interact/index.php?topic=24031.0
I read through the entire list.  That's where I got the idea to check for firmware or driver updated from Maxtor.
I have no add-ons, I've installed no new software.  This is the first time I've ever seen a BSOD on this machine.

The stop error is:


Error code 100000d1, parameter1 07f7ee81, parameter2 00000002, parameter3 00000000, parameter4 ba478c41.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Microsofts web site says:

 
 
Details
Product: Windows Operating System
ID: 1003
Source: System Error
Version: 5.2
Symbolic Name: ER_KRNLCRASH_LOG
Message: Error code %1, parameter1 %2, parameter2 %3, parameter3 %4, parameter4 %5.
   
Explanation
A blue screen (Stop error) was reported. The message contains details about the error. A matching event with Event ID 1001 might also appear in the event log. This matching event displays information about the specific error that occurred.
 
   
User Action
No user action is required.
 
 
That's it.  Not very helpfull.

On the blue screen, it does reference something like USBSTORE.drv or something similar (Sorry, I'm not at home and didn't write it down).

I know there's a conflict with the hardware drivers.  It's definatly a conflict with MC.

Thanks again!

[JimH]

I know there's a conflict with the hardware drivers.

Yes.

It's definitely a conflict with MC.

No.  It is a driver issue.  There is no conflict with MC.  MC may be simply reading the disk faster than anything else you use.

Try Maxtor support.  They should be able to help.

[Matt]

Turn on all MC logging in Help > Logging.

Plugin the drive and let it tank.

Unplug the drive, reboot, and look at the previous log in MC.  Post the last 100 lines (or so) here.

I'm guessing a simple WMDM or USB enumeration if causing a hardware fault.  This is the only thing we do with devices on startup.  It should be safe, and we haven't heard of this problem before.  Still, the log might give a clue.

Thanks for the help.

[jmone]

I'm sure I've read somewhere (but now can not find it) that with the Std 1024KB file allocation size the MAX logical drive size that XP can address is 4TB

[KingSparta]

I bought a Maxtor 1.5T external USB 2.0 drive.

I have

2-Each Maxtor 300 Gig One Touch II Drives
2-Each Maxtor 300 Gig One Touch III Drives
2-Each Maxtor 1TB External Drives
1-Each Maxtor 1.5TB External Drive
1-Each Lacie 2TB External Drive

All Working Ok With Media Center 12

If you Have The Turbo With The Firewire 400 and Or Firewire 800 interface you may Try Cabling It Up that Way To See If It Is the Interface.

All My 1TB, 1.5TB And 2TB Drives Are Using The 800 Firewire Interface However, And Not USB (USB Is Too Slow).

[InflatableMouse]

No idea. The internet is stuffed with "maxtor 100000d1 usb" results.  Seems like you are not the only one.

Do you have any other usb devices for which you installed drivers? It can be a tedious process uninstalling those and disconnecting any other devices to pinpoint the exact cause. If you are not afraid of some deep troubleshooting you could turn on minidumps, install the Windows debugging tools and symbol files for your OS. That will allow you to analyze the crash dump file and in most cases it shows you the offending drivers/dll's with a useless (at least for us mortals) stack dump and offending cpu register values. It might at least show the drivers or dll's of another usb device, a bug in a driver corrupting memory. Armed with that info you can decide to up- or downgrade certain drivers etc.

0x100000d1 is the same as 0x000000d1. I've seen that behavior many times with 0x20, 0x50 and 0xab stop errors on terminal servers. As far as I'm concerned the starting 1 simply means a negative number.

[rheacock]

I got a Firewire 800 card today.  I'll give it a try tonight, see if it helps to get it off of USB.  If that dosn't work, I'll post the 100 lines or so from the log file, see what's up.

Thansks everyone for your help.