External hard drive crashes system

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I've read several threads about similar problems and still need help. I have
a 250GB Seagate drive in an Ultra enclosure, using USB to connect. The first
drive worked for several weeks, then started to act up. I did the following:
different USB ports, different cable, different enclosure. Power on then
connect, connect then power on, and anything else I could think of. I talked
to Ultra; they said set the jumpers for Master (it was working set as Slave
before) so I did. Still no joy. I called Seagate, and Seagate said they
think the drive crashed and sent a new one. As soon as the new drive
finished formatting, BSoD. The Knowledge Base talks about Server 2003 with
the error code, and one particular virus with that error code. My virus
software says I'm good, and I'm running XP w/SP2.

What next?
 
Dan said:
I've read several threads about similar problems and still need help. I
have
a 250GB Seagate drive in an Ultra enclosure, using USB to connect. The
first
drive worked for several weeks, then started to act up. I did the
following:
different USB ports, different cable, different enclosure. Power on then
connect, connect then power on, and anything else I could think of. I
talked
to Ultra; they said set the jumpers for Master (it was working set as
Slave
before) so I did. Still no joy. I called Seagate, and Seagate said they
think the drive crashed and sent a new one. As soon as the new drive
finished formatting, BSoD. The Knowledge Base talks about Server 2003
with
the error code, and one particular virus with that error code. My virus
software says I'm good, and I'm running XP w/SP2.

What next?
Click to expand...


Dan:
Just so we understand the precise problem you're encountering...

On a normal boot with your USBEHD disconnected from the system, the system
boots normally without incident. And you encounter no problem *whatsoever*
with a perfectly functioning system. Correct so far?

But the problem arises when you connect your USBEHD. But what *exactly*
happens? The system won't boot? What is this KB article you refer to? What
"virus with that error code"?

You say you were able to format the USBEHD - I assume using Disk
Management - but then you got the BSOD? Out of nowhere? Immediately
following the format?

What happens if you install that Seagate HD as a secondary HD in your
system? Can it be successfully formatted and does it function without any
problems?

And you've used at least one different USB enclosure but encounter the same
problem?

Do other USB devices work OK in your system?
Anna
 
The virus listed is the HaxDoor virus. The reference was strictly to Server
2003 systems. I ignored it. With the first EHD I talked to Seagate Tech Spt
nad we went through the error log; nothing there to indicate a system problem.

The system works fine. When I connect the EHD, the system recognizes it and
then shuts down.

BSoD came immediately after formatting with Disc Management.

I have two other USB devices that work fine. I switched the cables around
in case I had a bad plug; the other devices still operate but the EHD does
not.

I have not put either hard drive on the internal ribbon. I reckon I'm lazy
there.

Seagate asked if I am running SP2; I am. I looked for other Windows updates
that may affect the system, but all I found were updates for Messenger and
Media player. The only software I installed after I got the EHD was Nero,
and I already uninstalled it to no effect.

Y'know, the worst thing about this is my wife asking why'd I buy it if it
doesn't work...
 
Dan said:
The virus listed is the HaxDoor virus. The reference was strictly to
Server
2003 systems. I ignored it. With the first EHD I talked to Seagate Tech
Spt
nad we went through the error log; nothing there to indicate a system
problem.

The system works fine. When I connect the EHD, the system recognizes it
and
then shuts down.

BSoD came immediately after formatting with Disc Management.

I have two other USB devices that work fine. I switched the cables around
in case I had a bad plug; the other devices still operate but the EHD does
not.

I have not put either hard drive on the internal ribbon. I reckon I'm
lazy
there.

Seagate asked if I am running SP2; I am. I looked for other Windows
updates
that may affect the system, but all I found were updates for Messenger and
Media player. The only software I installed after I got the EHD was Nero,
and I already uninstalled it to no effect.

Y'know, the worst thing about this is my wife asking why'd I buy it if it
doesn't work...
Click to expand...


Dan:
We'll ignore any possible virus-type issue here. We'll just assume that your
system is malware-free. If it isn't ... then that's another problem.

What do you mean when you say "When I connect the EHD, the system recognizes
it and then shuts down."? How do you know "the system recognizes it"?
Please, when you explain your problem, be as precise as you can be. I'm sure
you don't get a onscreen message indicating something like "The system
recognizes your USB device and now it's shutting down!". What exactly
happens?

And what do mean when you say "I have not put either hard drive on the
internal ribbon."? Your boot HD is obviously IDE-connected is it not? And,
as I recommended, it would behoove you to install the current USB-installed
HD as an internal HD to determine if there's any problem there.
Anna
 
By this, "I have not put either hard drive on the internal ribbon" I refer to
the two EHDs; the first, which is winging its way back to Seagate, and the
second which is sitting in its case taunting me... I was willing to assume I
didn't get two bad drives in a row, but okay, since it behooves me to do so,
I'll open the case and put the new HD in to check it out. I'll post again
afterward.

When I write "When I connect the EHD, the system recognizes
it and then shuts down" this is what I'm describing. I get a notification
(y'know, that neat little balloon pops up) telling me the system sees the
EHD. It shows the model #, tells me it's a USB device, then crashes.

By the way, I appreciate your help.

Be back soon.
 
Okay. I found it. It was a rootkit. Hacker-something-dot-spammer. One
stinking file that was corrupt. Everything appears to be fine now. It was
the last step before reformatting. Phew!

Let me express my appreciation, Anna, for your interest and knowledge.
You're very kind to us
not-quite-Luddites-but-certainly-not-as-knowledgeable-as-we-like-to-think
types. I will certainly recommend these boards to folks I know with
questions.

Y'all be good, and the best to you!

Dan
 
Back
Top