Broadband modem usb instigated crash

  • Thread starter Thread starter Mike Norris
  • Start date Start date
M

Mike Norris

Windows XP service pack2 all current updates loaded
I've had a Wanadoo Speedtouch broadband modem v 3.01 running fine for over 6
months on a cable connection, however it now crashes the machine ...
.... if attached at startup the machine hangs

If not attached the machine starts up normally and everything works
including all 6 USB ports.

First attempt
I've tried uninstalling then re-installing the the modem but when the
software asks you to plug in the modem ... as you do so the machine crashes,
switches off.
If the modem is removed from the port when the computer restarts it starts
normally with no error messages and everything else functions normally

Second attempt
got a new modem same as the first with updated software v3.5
exactly the same thing happens as with the first modem.
aslo tried new splitter with the same effects
then new usb cable with same effects

Third attempt
tried to do a system restore to before all the problems
system restore would NOT let me go back more than 3 weeks
(this computer should have a LARGE restore history)

Fourth attempt
decided to trash the c-drive
fully trashed and deep reformatted the c-drive ...
brand new motherboard drivers etc!
re-installed Windows XP Service pack 2 and updates
connected ONLY the modem when prompted to do so ....
CRASH! ... exactly the same as before

Fifth attempt
got wireless USB modem with new software ...
same results

Computer is otherwise functioning normally ...
my dial-up modem still gets me connected to the net as it always has done
all usb ports are otherise functioning normally with any peripheral I can
use with them.

I've run out of ideas ...... HELP!
 
Check to see if there are updated drivers for the modem.

Alternatively, if you can hook it up via Ethernet, that would be preferred
to a USB connection...
 
already tried 3 different drivers including latest one ... same result
changed the splitter, tried 3 different modems, cables & a wireless modem
with same results

??????????????????????????
 
Mike,
Take Gary's advice. I was having the same, very frustrating problems as
yourself, and went to an ethernet connection. It is much more seemless and
you buy-pass the tempramental USB drivers. I'm not sure why anyone would go
USB if you have a network card (allows ethernet connection).
 
It's a stand alone computer no networking and I'm trying to solve this
problem ..
not start others!
 
Network card drivers are significantly more mature than drivers for your
broadband USB device. For a mere $10 (cost of a network card), you'd
probably solve the problem a lot faster than trying to get finicky USB
drivers to work.

Your unwillingness to solve the problem the easiest way possible will likely
prolong the existing problem, but that's your choice.
 
I am well aware of your suggestion but ...
'workarounds' ... like this can never be acceptable as the problem is still
there!

If you can't help with the query then leave be!
 
Have fun finding drivers when a new OS comes out. That wouldn't be an issue
with ethernet cards.
 
In
Mike Norris said:
I am well aware of your suggestion but ...
'workarounds' ... like this can never be acceptable as the problem is
still there!
Click to expand...

Setting up something using recommended/best practices isn't a workaround.
What you want is a fix for a problem that wouldn't exist if you used the
aforementioned recommended config.
If you can't help with the query then leave be!
Click to expand...

Now, now. Play nice with the other kids when you're asking for free tech
support from volunteers. It appears that all those who have replied are
suggesting the same thing - and you're free to ignore any advice you like,
of course, but it should tell you something that there is such unanimity of
response. If you need more help with your finicky USB-attached device &
aren't getting help here, you should contact the manufacturer for technical
support. Personally, I would just use Ethernet.
 
Now I'm NOT playing nasty ... but you MVP's would do well to address the
given problem
rather than do suggest workarounds ... even though it is a solution it
doesn't correct the fault

the point I'm trying to make is that (if you read the scenario)
something has caused this problem ... it has worked fine for 6 months!
no-one ... has even suggested a possible cause
although reading betwen the lines you think it might be a driver problem

I don't think it is as one of the modems & drivers work fine on a different
XP computer
as I have now tested ... but still cause the problem on the original
machine.

I have never come across a problem such as this in my extensive experience
so I look for help ... and find an unwillingness to address the actual
problem!
NOT GOOD!

"Lanwench [MVP - Exchange]"
 
If it worked before, try restoring to a restore date prior to a date where
it stopped working properly via System Restore (Start, All programs,
Accessories, System Tools, System Restore)

--
Jason Tsang - Microsoft MVP

Find out about the MS MVP Program -
http://mvp.support.microsoft.com/default.aspx

Mike Norris said:
Now I'm NOT playing nasty ... but you MVP's would do well to address the
given problem
rather than do suggest workarounds ... even though it is a solution it
doesn't correct the fault

the point I'm trying to make is that (if you read the scenario)
something has caused this problem ... it has worked fine for 6 months!
no-one ... has even suggested a possible cause
although reading betwen the lines you think it might be a driver problem

I don't think it is as one of the modems & drivers work fine on a
different XP computer
as I have now tested ... but still cause the problem on the original
machine.

I have never come across a problem such as this in my extensive experience
so I look for help ... and find an unwillingness to address the actual
problem!
NOT GOOD!

"Lanwench [MVP - Exchange]"
In

Setting up something using recommended/best practices isn't a workaround.
What you want is a fix for a problem that wouldn't exist if you used the
aforementioned recommended config.

Now, now. Play nice with the other kids when you're asking for free tech
support from volunteers. It appears that all those who have replied are
suggesting the same thing - and you're free to ignore any advice you
like, of course, but it should tell you something that there is such
unanimity of response. If you need more help with your finicky
USB-attached device & aren't getting help here, you should contact the
manufacturer for technical support. Personally, I would just use
Ethernet.
Click to expand...
Click to expand...
 
In
Mike Norris said:
Now I'm NOT playing nasty ... but you MVP's would do well to address
the given problem
rather than do suggest workarounds ... even though it is a solution it
doesn't correct the fault
Click to expand...

Perhaps not. But it's a better configuration and wouldn't produce this
error.
the point I'm trying to make is that (if you read the scenario)
Click to expand...

I did.
something has caused this problem ... it has worked fine for 6 months!
Click to expand...

I can't say what it is, unfortunately. I wouldn't know, I wouldn't use USB,
and if you want to, you're probably going to have to play with this further.
I offered my suggestion because it would get rid of this problem entirely,
and would be better anyway. You could call PSS if you wanted one-on-one
support from Microsoft on this issue, but there's a per-incident charge. In
here, everyone's volunteering their time to try to help others, and you take
what you get, and often you get very good help. You're under no obligation
to take anyone's advice, including mine. ;-)
no-one ... has even suggested a possible cause
although reading betwen the lines you think it might be a driver
problem
Click to expand...

Yes, it seems to be a driver problem.
I don't think it is as one of the modems & drivers work fine on a
different XP computer
as I have now tested ... but still cause the problem on the original
machine.
Click to expand...

Then it's a driver problem on this specific PC, or your USB settings are
funky, and perhaps the hardware vendor will be able to help.
I have never come across a problem such as this in my extensive
experience so I look for help ... and find an unwillingness to
address the actual problem!
Click to expand...

Sorry I can't help you with the specifics. If you haven't made any other
changes you don't want 'undone' you can try Jason's suggestion of System
Restore.
NOT GOOD!

"Lanwench [MVP - Exchange]"
In

Setting up something using recommended/best practices isn't a
workaround. What you want is a fix for a problem that wouldn't exist
if you used the aforementioned recommended config.

Now, now. Play nice with the other kids when you're asking for free
tech support from volunteers. It appears that all those who have
replied are suggesting the same thing - and you're free to ignore
any advice you like, of course, but it should tell you something
that there is such unanimity of response. If you need more help with
your finicky USB-attached device & aren't getting help here, you
should contact the manufacturer for technical support. Personally, I
would just use Ethernet.
Click to expand...
Click to expand...
 
It seems you STILL have NOT read my original message ...

.... it details my failed attempt to System Restore ....

_________________________________________________________________


"Lanwench [MVP - Exchange]"
In
Mike Norris said:
Now I'm NOT playing nasty ... but you MVP's would do well to address
the given problem
rather than do suggest workarounds ... even though it is a solution it
doesn't correct the fault
Click to expand...

Perhaps not. But it's a better configuration and wouldn't produce this
error.
the point I'm trying to make is that (if you read the scenario)
Click to expand...

I did.
something has caused this problem ... it has worked fine for 6 months!
Click to expand...

I can't say what it is, unfortunately. I wouldn't know, I wouldn't use
USB, and if you want to, you're probably going to have to play with this
further. I offered my suggestion because it would get rid of this problem
entirely, and would be better anyway. You could call PSS if you wanted
one-on-one support from Microsoft on this issue, but there's a
per-incident charge. In here, everyone's volunteering their time to try to
help others, and you take what you get, and often you get very good help.
You're under no obligation to take anyone's advice, including mine. ;-)
no-one ... has even suggested a possible cause
although reading betwen the lines you think it might be a driver
problem
Click to expand...

Yes, it seems to be a driver problem.
I don't think it is as one of the modems & drivers work fine on a
different XP computer
as I have now tested ... but still cause the problem on the original
machine.
Click to expand...

Then it's a driver problem on this specific PC, or your USB settings are
funky, and perhaps the hardware vendor will be able to help.
I have never come across a problem such as this in my extensive
experience so I look for help ... and find an unwillingness to
address the actual problem!
Click to expand...

Sorry I can't help you with the specifics. If you haven't made any other
changes you don't want 'undone' you can try Jason's suggestion of System
Restore.
NOT GOOD!

"Lanwench [MVP - Exchange]"
In Mike Norris <[email protected]> typed:
I am well aware of your suggestion but ...
'workarounds' ... like this can never be acceptable as the problem
is still there!

Setting up something using recommended/best practices isn't a
workaround. What you want is a fix for a problem that wouldn't exist
if you used the aforementioned recommended config.

If you can't help with the query then leave be!

Now, now. Play nice with the other kids when you're asking for free
tech support from volunteers. It appears that all those who have
replied are suggesting the same thing - and you're free to ignore
any advice you like, of course, but it should tell you something
that there is such unanimity of response. If you need more help with
your finicky USB-attached device & aren't getting help here, you
should contact the manufacturer for technical support. Personally, I
would just use Ethernet.

Network card drivers are significantly more mature than drivers for
your broadband USB device. For a mere $10 (cost of a network
card), you'd probably solve the problem a lot faster than trying
to get finicky USB drivers to work.

Your unwillingness to solve the problem the easiest way possible
will likely prolong the existing problem, but that's your choice.

--
Jason Tsang - Microsoft MVP

Find out about the MS MVP Program -
http://mvp.support.microsoft.com/default.aspx

It's a stand alone computer no networking and I'm trying to solve
this problem ..
not start others!

Mike,
Take Gary's advice. I was having the same, very frustrating
problems as yourself, and went to an ethernet connection. It is
much more seemless and
you buy-pass the tempramental USB drivers. I'm not sure why
anyone would go
USB if you have a network card (allows ethernet connection).

:

already tried 3 different drivers including latest one ... same
result changed the splitter, tried 3 different modems, cables &
a wireless modem
with same results

??????????????????????????



Check to see if there are updated drivers for the modem.

Alternatively, if you can hook it up via Ethernet, that would
be preferred
to a USB connection...

--
Gary Tsang
Microsoft MVP - Windows XP Shell/User
http://www.microsoft.com/mvp


Windows XP service pack2 all current updates loaded
I've had a Wanadoo Speedtouch broadband modem v 3.01 running
fine for
over 6
months on a cable connection, however it now crashes the
machine ... ... if attached at startup the machine hangs

If not attached the machine starts up normally and everything
works including all 6 USB ports.

First attempt
I've tried uninstalling then re-installing the the modem but
when the
software asks you to plug in the modem ... as you do so the
machine crashes,
switches off.
If the modem is removed from the port when the computer
restarts it starts
normally with no error messages and everything else functions
normally

Second attempt
got a new modem same as the first with updated software v3.5
exactly the same thing happens as with the first modem.
aslo tried new splitter with the same effects
then new usb cable with same effects


Fourth attempt
decided to trash the c-drive
fully trashed and deep reformatted the c-drive ...
brand new motherboard drivers etc!
re-installed Windows XP Service pack 2 and updates
connected ONLY the modem when prompted to do so ....
CRASH! ... exactly the same as before

Fifth attempt
got wireless USB modem with new software ...
same results

Computer is otherwise functioning normally ...
my dial-up modem still gets me connected to the net as it
always has done
all usb ports are otherise functioning normally with any
peripheral I can
use with them.

I've run out of ideas ...... HELP!
Click to expand...
Click to expand...
Click to expand...
 
On Mon, 17 Oct 2005 00:15:16 +0200, "Mike Norris"
I am well aware of your suggestion but ... 'workarounds' ...
like this can never be acceptable as the problem is still there!
Click to expand...

I would definitely recommend a NAT router over direct exposure via
some sort of "ADSL modem", irrespective of whether this fixes the
specific problem or not.

Not only that, but direct connection to broadband exposes Windows more
directly to attack. Combine that with ICS and File and Print Sharing,
and you have a recipe for disaster - the first clean-up bill will blow
away the "savings" on buying the cheaper "modem" vs. router.

Agreed. Even with a single standalone PC with no WiFi and Bluetooth
risks, I'd choose a NAT router over "broadband modem" any day. With a
router, the router does the work and all the PC needs to do is drive
the standard network adapter - something that's been easy and stable
since Windows 95 at least. With a "modem", you have to have
OS-version-compatible "special" code to get everything to work.

It really is a no-brainer - for ADSL. YMMV with cable, in that I
don't know the availability of combo cable+routers :-(

Perhaps we're misreading the situation as a driver issue, when it's
really a malware issue? If you connect the "modem" to the PC but
ensure the "modem" is NOT connected to the 'net, does it still crash?

If it does, back to the driver witch-hunt.

If it does not crash anymore, then this is almost certainly a generic
malware problem, and I'd dig there instead.

Debatable assertion, that. The deeper the System Restore, the more
collateral damage; even 3 days can be too deep for comfort.

This is the first test that points even slightly away from malware as
the cause. However, whatever method whereby the malware infected your
previous installation may have facilitated infection of the new one,
plus you may have restored malware with "data" backups. If a remote
malware source has your system fingerprinted, it may automatically
re-assert the malware whenever you go online.

At this point, I'd definitely give up on all this USB "modem" junk if
it were possible to do so. In ADSL, you get combination router and
ADSL "modem" units that cost less than stand-alone pure routers
(especially of the enterprise/Cisco variety). We don't have cable
here, so I don't know whether you get the equivalent for cable, or
whether the cost difference is as comfy as it is for ADSL.

One possibility comes to mindl; underpowering of the USB stack. Do
these USB "modems" have their own power? Are you running a lot of USB
devices via an unpowered hub?

Those contexts would give you generic USB issues, with the "modem" as
the "straw that breaks the camel's back" and as the problem is at the
"analog" level, it may not present with clear-cut edges.

OK - while connected, do you have problems?
Does your ISP issue the same IP for both connect methods?

If you are seldon online via modem, and/or you connect via a different
ISP or IP address, then success doesn't rule out a malware factor.

I'm still thinking power load vs. specific modem issues there.

Thinking in terms of what is common to what does not work, and how one
could avoid that entire class of problem. USB per se is usually quite
reliable in XP, but power issues can be nebulous.
 
On Mon, 17 Oct 2005 12:01:57 +0200, "Mike Norris"
Now I'm NOT playing nasty ... but you MVP's would do well to address the
given problem rather than do suggest workarounds
Click to expand...

No. Expending great effort to keep something alive is time wasted, if
that something sucks - plus, when attempts to isolate specific problem
detail fail as spectacularly as in this case, one may be forced to
perform a wider excision of the problem.

As a geek, I also resent having to walk away from a problem without
pinning down what it is - but I also appreciate detecting bad
situations early, so that I can avoid large messes in future.
the point I'm trying to make is that (if you read the scenario)
something has caused this problem ... it has worked fine for 6 months!
Click to expand...

Yep. What's changed?
- malware infection
- code/compatibility drift from patches, installs changing .DLLs
- code corruption from AutoChk/ChkDsk "fixing" things
- code corruption from antivirus "cleaning" infected files
- additional unrelated USB devices increasing power draw
- server-side changes made by your ISP
- damage to your cable service cabling

The desire to avoid large baroque driver and Internet access code,
stems from the desire to reduce exposure to compatibility drift that
can occur as the OS and other code is changed via SPs, patches,
side-effects from other installations, etc.

In this respect, the urge to simplify by keeping the details of the
broadband connection off-board at the router, is on-topic. That such
an approach strengthens you against malware is useful too, and may
even be a bulls-eye of malware is in fact the problem here.
 
In
Mike Norris said:
It seems you STILL have NOT read my original message ...
Click to expand...

Ah, sorry - you're right.
... it details my failed attempt to System Restore ....
Click to expand...

Then you're back to the drawing board, it would seem. Sorry.
_________________________________________________________________


"Lanwench [MVP - Exchange]"
In
Mike Norris said:
Now I'm NOT playing nasty ... but you MVP's would do well to address
the given problem
rather than do suggest workarounds ... even though it is a solution
it doesn't correct the fault
Click to expand...

Perhaps not. But it's a better configuration and wouldn't produce
this error.
the point I'm trying to make is that (if you read the scenario)
Click to expand...

I did.
something has caused this problem ... it has worked fine for 6
months!
Click to expand...

I can't say what it is, unfortunately. I wouldn't know, I wouldn't
use USB, and if you want to, you're probably going to have to play
with this further. I offered my suggestion because it would get rid
of this problem entirely, and would be better anyway. You could call
PSS if you wanted one-on-one support from Microsoft on this issue,
but there's a per-incident charge. In here, everyone's volunteering
their time to try to help others, and you take what you get, and
often you get very good help. You're under no obligation to take
anyone's advice, including mine. ;-)
no-one ... has even suggested a possible cause
although reading betwen the lines you think it might be a driver
problem
Click to expand...

Yes, it seems to be a driver problem.
I don't think it is as one of the modems & drivers work fine on a
different XP computer
as I have now tested ... but still cause the problem on the original
machine.
Click to expand...

Then it's a driver problem on this specific PC, or your USB settings
are funky, and perhaps the hardware vendor will be able to help.
I have never come across a problem such as this in my extensive
experience so I look for help ... and find an unwillingness to
address the actual problem!
Click to expand...

Sorry I can't help you with the specifics. If you haven't made any
other changes you don't want 'undone' you can try Jason's suggestion
of System Restore.
NOT GOOD!

"Lanwench [MVP - Exchange]"
message

In Mike Norris <[email protected]> typed:
I am well aware of your suggestion but ...
'workarounds' ... like this can never be acceptable as the problem
is still there!

Setting up something using recommended/best practices isn't a
workaround. What you want is a fix for a problem that wouldn't
exist if you used the aforementioned recommended config.

If you can't help with the query then leave be!

Now, now. Play nice with the other kids when you're asking for free
tech support from volunteers. It appears that all those who have
replied are suggesting the same thing - and you're free to ignore
any advice you like, of course, but it should tell you something
that there is such unanimity of response. If you need more help
with your finicky USB-attached device & aren't getting help here,
you should contact the manufacturer for technical support.
Personally, I would just use Ethernet.

Network card drivers are significantly more mature than drivers
for your broadband USB device. For a mere $10 (cost of a network
card), you'd probably solve the problem a lot faster than trying
to get finicky USB drivers to work.

Your unwillingness to solve the problem the easiest way possible
will likely prolong the existing problem, but that's your choice.

--
Jason Tsang - Microsoft MVP

Find out about the MS MVP Program -
http://mvp.support.microsoft.com/default.aspx

It's a stand alone computer no networking and I'm trying to
solve this problem ..
not start others!

Mike,
Take Gary's advice. I was having the same, very frustrating
problems as yourself, and went to an ethernet connection. It
is much more seemless and
you buy-pass the tempramental USB drivers. I'm not sure why
anyone would go
USB if you have a network card (allows ethernet connection).

:

already tried 3 different drivers including latest one ...
same result changed the splitter, tried 3 different modems,
cables & a wireless modem
with same results

??????????????????????????



Check to see if there are updated drivers for the modem.

Alternatively, if you can hook it up via Ethernet, that would
be preferred
to a USB connection...

--
Gary Tsang
Microsoft MVP - Windows XP Shell/User
http://www.microsoft.com/mvp


message Windows XP service pack2 all current updates loaded
I've had a Wanadoo Speedtouch broadband modem v 3.01 running
fine for
over 6
months on a cable connection, however it now crashes the
machine ... ... if attached at startup the machine hangs

If not attached the machine starts up normally and
everything works including all 6 USB ports.

First attempt
I've tried uninstalling then re-installing the the modem but
when the
software asks you to plug in the modem ... as you do so the
machine crashes,
switches off.
If the modem is removed from the port when the computer
restarts it starts
normally with no error messages and everything else
functions normally

Second attempt
got a new modem same as the first with updated software v3.5
exactly the same thing happens as with the first modem.
aslo tried new splitter with the same effects
then new usb cable with same effects


Fourth attempt
decided to trash the c-drive
fully trashed and deep reformatted the c-drive ...
brand new motherboard drivers etc!
re-installed Windows XP Service pack 2 and updates
connected ONLY the modem when prompted to do so ....
CRASH! ... exactly the same as before

Fifth attempt
got wireless USB modem with new software ...
same results

Computer is otherwise functioning normally ...
my dial-up modem still gets me connected to the net as it
always has done
all usb ports are otherise functioning normally with any
peripheral I can
use with them.

I've run out of ideas ...... HELP!
Click to expand...
Click to expand...
Click to expand...
 
Ok .... at last someone who can pont me in a different direction ...

will tackle the problem from the angles you have suggested

Thanks.
 
On Tue, 18 Oct 2005 16:48:23 +0200, "Mike Norris"
Ok .... at last someone who can pont me in a different direction ...
will tackle the problem from the angles you have suggested
Click to expand...

Cool! Let us know how it pans out - it sounds like a toughie ;-/
 
I'm sorry I don't have access to the original post, so i'll interject my
comments here, using
the quoted posts below.

When a device that has been working well months suddenly starts causing
problems,
you should suspect hardware issues, virus', malware, incompatable drivers or
updates,
or recently installed software.
Did you install anything right before (within 2 or 3 boots) the problem
started?
Do you know which Windows Updates the auto updater may have installed
right before the problem began?
Did you use chkdsk or your hdd(s)' manufacturer's diagnostic tool to rule
out the possibility
of data corruption from bad clusters or a failing hdd?

Do you use multiple anti-malware apps to check for malicious apps?
I say Multiple, 'cause no 1 title is aware of everything that could be a
threat to your system.
Check other posts to find out what the favorites are ( Spybot Search &
Destroy and Ad Aware SE) and try them, if you dont have enough reliable
apps.

Did you have your anti-virus do a thorough scan?
Don't rely on one av app, back it up with a couple of the free online av
scans available
from companies such as symantec or mcafee.

Did you check running processes and BHO's for malicious apps that may have
been missed
by your anti-malware app.
Spybot S&D will also show you the running processes and thier child
processess.

Did you check The System Information Tool (Components | Problem Devices
tree) for
problem devices? Problem Devices may be listed OK in the device manager,
so rely more on The System Information Tool , instead.

When you get to the point that you're certain that you've ruled out malware,
virus'
and HDD corruption, then the only thing left is a full hardware and software
troubleshooting.

You'll need to take your computer apart :)
All you want is the Motherboard, PSU, Video Card, HDD, keyboard & mouse.
Make sure all onboard devices, except usb, are disabled.

Install XP, but do NOT install any patches, updates, service packs or
anything else.
Install your broadband modem (make sure it's not connected to the net) use a
port
on the tower, not a hub, make sure XP's firewall is active.

If it doesn't crash, then install the motherboard drivers from the cd that
came with it and reboot.
It'll probably just ide and usb drivers.

Does it crash?
If not, Install the Motherboard's chipset's updates
(the chipset manufacturer's website would probably be the best place to get
them, especially
if it's an nvidia chipset). Reboot.

Does it crash?
If not, continue install drivers, and the such, one at a time, and testing
the modem.
Leave SP2, and all XP updates for last.
If you get to XP's updates with no crashes, then install SP2 and all Updates
ONE AT A TIME,
reboot and testing the modem in between each install.
When the crash occures, suspect the most recently installed update and
uninstall it and reboot to see if the crashes stop.

If, on the other hand, the crashes occure the moment the broadband modem is
installed,
i.e. before you can even install the motherboard drivers from the cd,
then try installing them and the chipset updates.
If that doesn't help, then you need to suspect either hardware failure or
incompatability.
You can check by using a different hdd & video card.
If neccessary, go back to the original motherboard.
Also check your bios settings.

If the Crashes continue to happen, then the only thing you haven't switched
out is the Broadband modem, take the new one back and get a different
make/model modem.
 
Back
Top