07-19-2011 09:37 AM
I have a new W520 and my Gobi 3000 broadband modem keeps dissapearing. I get an errors about a USB device problem and in Hardware Devices it is listed with a USB error code 43. I have to power down the computer and reboot to get it to show back up. Sometimes it takes 30 minutes after booting to dissapear and other times a few hours. Very sporadic.
Interestingly, it never dissapears when I am using the modem and have an active connection to AT&T. It only dissapears while I am connected via wifi. This is most confusing to see a device malfunction only when it is not in use. It is annoying that I have to shutdown and reboot to switch over to it when I lose my wifi signal.
I am using an exisiting AT&T sim with a laptop connect account I have had for years. When the Gobi 3000 is connected it works very well.
Any suggestions before I call Lenovo technical support? My guess is that either the drivers are immature, or I have a defective Gobi 3000.
07-19-2011 10:58 AM
please try these 2 things
1. in device manager, double click on the device, go to the power management tab, and UNCHECk the option for "allow the computer to turn off this device to save power"
2. in power manager, DISABLE the option for USB selective suspend. this option is in the advanced settings of your power profile.
try 1 first, if that doesn't work then try 2. I'm not suggesting this is a long-term solution, i'm just trying to collect information about what the problem could be.
07-20-2011 07:04 AM
Number 1 above appears to have stopped the Gobi 3000 from dissapearing from the system. I unchecked the box "allow the computer to turn off this device to save power" and used the laptop all evening on wifi, left it on overnight, and then more use this morning on wifi. The Gobi 3000 is still listed in Device Manager without any USB errors.
My first inclination is that this is a driver problem, but if that was true I would have expected to see more users complain about it. Therefore, could this be a hardware problem? Maybe I have a bad Gobi 3000 unit?
Thanks for the help. Much appreciated. At least I have a workaround for now.
07-20-2011 07:17 AM
I think the issue is described here: http://support.microsoft.com/kb/2484742
I'm not really sure what Microsoft's plans are to fix it, or if a fix has to come from Intel with a new chipset driver/firmware.
07-31-2012 03:59 PM
We have 4 Lenovo X220's with the Sierra Wireless MC8355 Gobi 3000 HS-USB Mobile Broadband device installed. Running W7/64.
Same symptoms. The "fix" or "workaround" mentioned does work.... for awhile.
Problems seem to return. We have placed a call with Lenovo and we even got a "Crit Sit" team that is SUPPOSED to call us back to help resolve. (still waiting, a week later).
It amazes me that nobody has found a permanent solution to this problem.
Does anyone know WHY Lenovo has not found a solution to a problem that is ongoing for well over a year now?
08-01-2012 10:38 AM - edited 08-01-2012 10:47 AM
To "someotherguy", See your response from 7.19.2011 above.
Also, from this forum....
Specifically the response from "swsBro" on 5.04.2012 within that link :
Solution for windows 7 --- x86 and x64
To resolve this issue, go to device manager.
Expand --> Unversal Serial Bus Controllers
Find --> Serra Wireless MC8355 -Gobi 3000
Right Click the driver and Uninstall, also, check the box "Delete the driver software for the device"
Then right click on the Computer Name, and "Scan for hardware changes"
The computer will go out to the internet and re-install the drivers for the GoBi 3000, without creating a seperate "Univrsal Serial Bus controller"
When the computer recover from sleep the GoBi 3000 will also wake up...
****i've done these steps and it seems to resolve, but then the problem returns at some point.
08-01-2012 10:53 AM
I really can't explain why the tips worked for others but not you.
As a last resort, I recommend following the steps in the Microsoft KB article here:
I don't have any other advice about this issue...
08-02-2012 12:06 PM
Well thanks for looking into it for me. I guess my underlying question is WHY this would be happening in the first place. Sounds like it is still too rare of an occurence to have a solid answer for at this time.