- BLACKBERRY LINK ERROR 1935 FOR MAC
- BLACKBERRY LINK ERROR 1935 DRIVERS
- BLACKBERRY LINK ERROR 1935 DRIVER
BLACKBERRY LINK ERROR 1935 DRIVERS
Some of the text on that site is in French (because it's in France ), but the reason I like it is it isn't full of advertising and garbage and it's not one of those scam drivers sites that is constantly trying to sell you things before they let you download anything and who knows what they are hosting there anyway. Here are some links from station-drivers for USB 3.0 drivers: You can go into Device Manager to figure out what type of USB chipset is in there and then if your board (or add-in card) manufacturer doesn't have anything newer, try a place like. Those with USB 3.0 only may want to try updating their USB driver. So for starters, make sure there is an exception rule to allow the Link application to communicate.
BLACKBERRY LINK ERROR 1935 DRIVER
The NDIS thing is a USB network driver - apparently Link treats its connection to a PC more like a network connection than a wired connection, which I imagine is because they are also doing networking sorts of communications with Link features like the remote control thing, and the WiFi sync thing.īut the downside of that is that you have to pay attention to things that normally only pertain to network communications, like the Windows Firewall. Last edited by Superfly_FR 05-20-13 at 05:46 AM. P.S: this is a brand new HP p6-2393ef desktop.
I strongly suggest anyone having trouble to try this before anything else. Will report if more stable so far so good.Īfter 1 hour 7 hours TWO DAYS, The least I can say is that I believe this is related. Now plugged on USB2 (for non-techs information, usually at the back of the desktop, with no special mention written). I'll check about the USB3 possibility, as I use the desk front USB connectors (I presume they should be the fastest) and I'll report back.Įdit : Yes I was plugged into USB3 port. As an example, creating a folder should be instant in file explore while it's not (maybe up to 2 sec witch is nowhere close to normal). I can feel there are underlying problems. I have zero trouble when my Z10/Q10 are unplugged and Link is not running.Īs soon as I plug My Z. Stangely, I've found it issued first by RIM (BlackBerry) then by Microsoft. The usb80236.sys usb/NDIS driver - Version is. I ran WhoCrashed and - by chance - saw an entry that pointed it out ( by chance, because it doesn't seem to be dumped at each crash). Similar problems here (W8/64 bits) but I'm not sure Link is the problem. Not only do their staff typically not have detailed diagnostic skills, the companies simply aren't willing to expend hours with a single customer trying to track down complex intertwined problems like that. Matter of fact, TONS of tech-support organizations and departments of computer product vendors essentially tell customers the same thing. (or buy another computer, which IMHO is kind of dumb) Windoze can be an impossible morass when conflicts like that happen, it can be virtually impossible to un-wind what is conflicting with what, which is why so many people just throw up their hands and re-install the OS when they run into stuff like that.
BLACKBERRY LINK ERROR 1935 FOR MAC
I also find that USB is an area with a lot of issues because every cr*p vendor in the world wants to throw drivers into the USB stack that jump in whenever a state change happens, monitoring every device addition/removal, and a lot of those things are either junk, or after you have a couple of dozen of 'em it inevitably becomes a giant disaster-prone hairball.Ī friend of mine complained that she was no longer able to backup her Torch using Desktop Manager on her XP PC, and after some hours of screwing around trying to figure out what caused the problem, I just gave up and installed DM for Mac on her iMac and had her back it up there.
The reason I asked about USB 3.0 is that it's a newer thing that is likely to have seen less QC testing done with that environment.ĪSUS is usually a good board vendor but since your environment is not 'moderated' by vendor testing and qualification, it's much more "Wild West" than a branded system from a major vendor would be, and in general will often be more sensitive to quirks. The Link installer could have installed drivers that catalyzed something going on with the machine, no need to have something plugged-in for that to happen. If it was a USB driver issue I'd guess it would happen more if the phone were plugged in.Not necessarily. Strange thing is that it will crash even without the phone being plugged in.
0 kommentar(er)
