Hallo zusammen,


ich bin am verzweifeln... habe jetzt schon wochenlang das Problem, Egal mit was für einem Programm (Ich habe es schon mit den Programmen MyPhoneExplorer, Floats Mobilagent und SonyEricssonPCSuite probiert) ich das Handy (ich habe 2 T610 und T630) am PC
aktuallisiere bekomme ich von meinem PC (es ist ein AMD Phenom 4 Kerner
940 auf einem Gigabyte Mainboard) einen Bluescreen mit der Meldung


(Ausgelesen mit Debugging Tool)
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini050209-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sat May 2 18:41:17.156 2009 (GMT+2)
System Uptime: 0 days 1:16:20.086
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
.......................................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck xxx *
* *
*******************************************************************************
Use !xxx -v to get detailed debugging information.
BugCheck 44, {89535640, d64, 0, 0}
***** Kernel symbols are WRONG. Please fix symbols to do xxx.
*** WARNING: Unable to verify timestamp for USBPORT.SYS
*** ERROR: Module load completed but symbols could not be loaded for USBPORT.SYS
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
** Certain .pdb files (such as the public OS symbols) do not ***
** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
** ***
*** Type referenced: nt!_IRP ***
** ***
*************************************************************************
************************************************************************
** ***
** ***
** Your debugger is not using the correct symbols ***
*** ***
** In order for this command to work properly, your symbol path ***
** must point to .pdb files that have full type information. ***
** ***
** Certain .pdb files (such as the public OS symbols) do not ***
** contain the required information. Contact the group that ***
** provided you with these symbols if you need this command to ***
** work. ***
** ***
*** Type referenced: nt!_KPRCB ***
** ***
************************************************************************
*************************************************************************
** ***
** ***
** Your debugger is not using the correct symbols ***
** ***** In order for this command to work properly, your symbol path ***
** must point to .pdb files that have full type information. ***
** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
** contain the required information. Contact the group that ***
** provided you with these symbols if you need this command to ***
* work. ***
** ***
** Type referenced: nt!_KPRCB ***
** ***************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
using the _NT_SYMBOL_PATH environment variable. *
using the -y <symbol_path> argument when starting the debugger. *
using .sympath and .sympath+ *
*********************************************************************
********************************************************************
Symbols can not be loaded because symbol path is not initialized. *
*
The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
using .sympath and .sympath+ *
********************************************************************
Probably caused by : sptd.sys ( sptd+11d54 )
Followup: MachineOwner
---------

und den Bluescreen bekomme ich auch wenn ich die sptd.sys vom System lösche dann halt mit der Datei USBPORT.sys
Ich weis mir keinen Rat mehr, ich hoffe Ihr könnt mir helfen
vielen Dank schon im voraus
Jacki1311