Seite 1 von 1

Windows crashes at USB connection

Verfasst: Mo 19. Dez 2011, 16:15
von thejackll
Hi - sometimes my phone will connect successfully, but the last few times I have tried it crashes windows and I see the BSOD. Unsettling.

Sequence of events:
Start MPE on phone
Plug in USB
computer crashes after 3-5 seconds

If I need to start the desktop MPE first or plug the phone in first, please advise.

Thanks.

- Model = Samsung Charge SCH-I510 (Verizon)
- USB type connection
- MPE-version 1.0.14
- Windows 7
- firmware version = ?
- no log file appears in MPE installation folder, this is taken from the "view log file" option in MPE -

Logdatei MyPhoneExplorer
************************
Programmversion: 1.8.2
Datum: 12/19/2011

09:08:38.77 Setting Port: 999
09:08:38.77 Setting Baud: 115200
09:08:38.77 Avaiable Ports: COM1=\Device\Serial0; COM5=\Device\BthModem1; COM6=\Device\BthModem0;
09:08:38.81 Main Load frmSplash
09:08:38.94 Load frmSplash...
09:08:40.33 Hauptfenster wird geladen
09:08:41.35 Sidebar fertig geladen
09:08:42.72 UC SMS wird geladen
09:08:43.02 UC Phonebook wird geladen
09:08:43.06 UC Phonebook fertig geladen
09:08:43.07 UC Calls wird geladen
09:08:43.11 UC Organizer wird geladen
09:08:43.23 Organizer initiated
09:08:43.26 Startpage=2
09:08:43.44 UC Filebrowser wird geladen
09:08:43.58 UC Filebrowser fertig geladen
09:08:43.58 UC AppBrowser wird geladen
09:08:43.60 UC Notes wird geladen
09:08:43.61 UC Calls wird geladen
09:08:43.80 RunADBCommand: start-server
09:08:48.29 ADB CommandResponse: * daemon not running. starting it now on port 5037 *
* daemon started successfully *

Verfasst: So 25. Dez 2011, 20:48
von FJ
In every case you get a bluescreen on PC then only a driver can be the reason. No PC-Application can raise a bluescreen directly. So uninstall the ADB-Drivers for your phone in devicemanager. Then install the newest version of KIES so you get fresh ADB-Drivers

Verfasst: Mo 26. Dez 2011, 18:49
von thejackll
I have tried installing Kies. That did not work.

I have also downloaded and installed Samsung drivers from 4 different sources. None of these have worked.

To be clear - after each separate driver was installed (presumably over the last one) I plugged in the phone and the BSOD showed up.

I am trying to educate myself about how this works, but I feel stupid because I'm not a computer geek and I don't know what questions to ask using the correct vocabulary.

The frustrating part is that it worked for nearly a month without a problem.

I called Samsung, and they claim that they do not have ADB drivers for my phone, and that it is not possible to sync except through Google, which I do not want to do. Their "Level 2" support person told me that I can't possibly need ADB drivers.

Verizon refuses to assist with any 3rd party applications, period.

However, when I search on this topic, it seems that plenty of other folks are successful at getting the drivers to install correctly. Many of them claim to have plugged in the phone and gotten the drivers from the phone itself.

I'm at the point where I am willing to accept pity and assistance from anyone with a little time on their hands and knowledge on how to get this to work.

Thanks in advance.

Verfasst: Do 12. Jan 2012, 22:58
von FJ
Maybe there is something on your computer which produces the crash in combination with the ADB-Drivers. Seems to be a difficult problem, but you could use also Bluetooth or WiFi -> this needs no drivers. In case you have no Bluetooth and no Wifi: A Bluetooth Stick costs about 15$. Compared to your difficulties till now i think it would be a good alternative