I have installed the latest version of windows mobile device center on my PC with Vista. I have sucessfully sync'd without issue.
My issue is that everytime I disconnect my 8525 from the cradle I get the annoying message that Windows mobile device center sync host has stopped. Has anyone figured out how to fix that issue?............It's just annoying as heck.
Here is the error:
Description:
Stopped working
Problem signature:
Problem Event Name: APPCRASH
Application Name: WmdHost.exe
Application Version: 6.1.6965.0
Application Timestamp: 465eef4e
Fault Module Name: unknown
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: 53502105
OS Version: 6.0.6000.2.0.0.256.6
Locale ID: 1033
Read our privacy statement:
http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409
anyone come up with something that will resolve this or am I doomed to wait for microsoft?
Related
Hi,
I have problem with PDA ACER n50 and with bluetooth activation.
The problem appeared after ROM upgrading from v1.00.09 to v1.00.18
New ROM was downloaded from official ACER ftp.
Description of problem:
----------------------
When I turn ON bluetooth I got after some seconds message:
Sorry! Bluetooth can no longer be used because the license is expired.
BDA: 00:00:00:00:00:00
Key: E3E534E1...
PDA System info:
----------------
OS version: v4.21
ROM revision date: 20050818
ROM version: v1.00.18
Firmware version: v0.94
Bootloader version: v1.13
bluetooth info:
Bluetooth for Windows CE
BT-PPC Version 1.7.0 Build 1900
My unsuccessful efforts:
-----------------------
soft reset
hard reset
change of system datetime
older bluetooth versions application
- Widcomm 1.4.1.59
- Broadcom 1.6.0 0600
registry modifications
I tried solve this problem from suggestions which I detected on this site
etc...
Can anybody help me with specific recommendation ?
i'd contact acer
otherwise you can prob get it running if you set your clock a few years back :S
Hi All,
i am really looking for some help here, as lst 3-4 hours were fully unsuccessful for me... My laptop (XP SP2) stopped recognizing my tytn via usb. Once i connect the device, i go thru the Found new hardware wizard. At the end of process (no matter i select automatic update, or direct) it will give me an error: windows mobile-based device could not be installed... an error occured during the instalation. The reason is that it is looking for the USB driver in c:/windows/inf/oem4.inf file. This file directs to usb8023x.sys, which is supposed to control the connection.
Last few blocks from setupapi look like:
#-166 Device install function: DIF_INSTALLDEVICEFILES.
#I124 Doing copy-only install of "USB\VID_0BB4&PID_0B04\00197735-4275-0151-1800-0050BF3F5173".
#-011 Installing section [RNDIS.NT.5.1] from "c:\windows\inf\oem4.inf".
#E358 An unsigned or incorrectly signed file "c:\windows\inf\oem4.inf" for driver "Windows Mobile-based Device" blocked (server install). Error 1168: Element not found.
#E122 Device install failed. Error 1168: Element not found.
#E157 Default installer failed. Error 1168: Element not found.
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [RNDIS.NT.5.1.Interfaces] from "c:\program files\microsoft activesync\drivers\wcerndis.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "USB\VID_0BB4&PID_0B04\00197735-4275-0151-1800-0050BF3F5173".
#E122 Device install failed. Error 2: The system cannot find the file specified.
#E154 Class installer failed. Error 2: The system cannot find the file specified.
#I060 Set selected driver.
#I125 Installing NULL driver for "USB\VID_0BB4&PID_0B04\00197735-4275-0151-1800-0050BF3F5173".
#E122 Device install failed. Error 2: The system cannot find the file specified.
[2007/04/15 00:59:57 1784.12 Driver Install]
#-019 Searching for hardware ID(s): usb\vid_0bb4&pid_0b04&rev_0000,usb\vid_0bb4&pid_0b04
#-018 Searching for compatible ID(s): usb\class_ef&subclass_01&prot_01,usb\class_ef&subclass_01,usb\class_ef
#-198 Command line processed: C:\WINDOWS\system32\services.exe
#I022 Found "USB\Class_EF&SubClass_01&Prot_01" in C:\WINDOWS\inf\oem4.inf; Device: "Windows Mobile-based Device"; Driver: "Windows Mobile-based Device"; Provider: "Microsoft Corporation"; Mfg: "Microsoft Corporation"; Section name: "RNDIS.NT.5.1".
#I023 Actual install section: [RNDIS.NT.5.1]. Rank: 0x00002000. Effective driver date: 10/28/2005.
#I022 Found "USB\Class_EF&SubClass_01&Prot_01" in C:\WINDOWS\inf\oem37.inf; Device: "Windows Mobile-based Device"; Driver: "Windows Mobile-based Device"; Provider: "Microsoft Corporation"; Mfg: "Microsoft Corporation"; Section name: "RNDIS.NT.5.1".
#I023 Actual install section: [RNDIS.NT.5.1]. Rank: 0x00002000. Effective driver date: 10/28/2005.
Would appreciate any help (reinstalling the XP is not an option for me...). TyTN is working with no problems being linked to other computers.
Have you used the installation disc?
Mike
Installation disk for what? The thing is that the most recent RNDIS and "Windows mobile-based device" are part of XP SP2 pack... The other thing is that everything was working perfectly well for me till yesterday. This does look like smth has got corrupted, but SP2 repair did not help.
USB problem...
Hey, I have the same problem for over 3 months now...
The strange thing is, IR an Bluetooth work well, it's a TyTn thing because a Qtek 9100 or 8310 are perfectly pairable.
I also have this with ALL PC's using activesync 4.x. I first thought it was my USB cable that was defective, but this seems to be OK (sync perfect with all qteks PSP etc)
Altough i haven't used it with my vista configuration yet i think it will have the same problem...
Now i'm stuck with the o so slow IR because there's no answer for this on any site... (long live google)
nobody has an idea?
I can't believe that
Anyone fixed this as at the moment I cannot connect my hermes to my XPSP2 machine.
Mine wasn't working, then it worked. Don't know what I did.
But know the USB internet connect option doesn't work.
sigh...i hate windows
sorry double post. can't find the delete post option
Hi, I hope someone might be able to help. I upgraded my Dell M65 to Windows Vista Business using the Dell Vista Upgrade. I can no longer sync my 6700. It worked on Windows XP Pro, with no problem.
I have updated, downloaded and re-updated the Windows Mobile Device Center. I have worked with support manager at UTStarcom (very good and dedicated) followed everything they suggested to no avail. Now they are waiting to hear from MS - it's been months and no response.
I tried to connect my wifes 6700 and that would not connect either.
Vista looks for the file it needs to "install" , but it reports " Could not load driver software."
Below is the Vista problem report:
Description
Windows was able to successfully install device driver software, but the driver software encountered a problem when it tried to run. The problem code is 10.
Problem signature
Problem Event Name: PnPDeviceProblemCode
Architecture: x86
Hardware Id: TCPIP\WINDOWS_MOBILE_DEVICE
Setup class GUID: {eec5ad98-8080-425f-922a-dabf3de3f69a}
PnP problem code: 0000000A
Driver name: wudfrd.sys
Driver version: 6.0.6000.16386
Driver date: 11-02-2006
OS Version: 6.0.6000.2.0.0.256.6
Locale ID: 1033
Extra information about the problem
Bucket ID: 11837167
Any help would be huge. It's been months since i synced, and it's frustrating. I have to copy all my files to sync to an old computer to sync.
Thank you in advance! -B
vista has a lot of problems syncing for some reason. i can sync no porblem but dont try flashing with vista. just doesn't work. you made sure you have the activesync doanloaded right? go to microsofts website and search for it.
Solution for Syncing
I was pouring thru threads and found an old thread suggesting the new WMDC version 6.1. I have been to the MS site many times and did not find it. However in the thread there was a link, and it seems to have worked.
I can now sync with no problem.
I will head your advice ion the flashing however.
Thanks!!
i know on mine and my Excalibur (smartphone) i had, it will just get stuck in bootloader. not a big problem just a pain.
Wifi Does not work. It worked (with some trouble) with original WM5 rom, then I tested some rom download form this forum, and stopped to work.
Hp Asset viewer report:
Driver rev : N/A
Firmware ver: N/A
Hardware rev: 1.0
IP Address: N/A
Mac Address: N/A
Radio Present: Yes
so it look like if wifi firmware was cleared.
Any idea how to solve?
thanks
Hello everyone.
First I would like to say I wouldn't be opening this thread if I hadn't done extensive research on this issue (aka Googling).
Anyway, recently I upgraded my computer and went from Windows 7 to Windows 8. Problems started right after installation, I was getting frequent blue screens of death. I figured it was a driver problem, so I installed all the windows updates and updated hardware drivers. While BSODs have become less frequent now, they are still present. I installed WinDbg to analyze crash dumps and I noticed that almost all of the crashes were caused by a module called "usb8023x.sys", which is a Remote NDIS USB Driver (the driver which allows the phone to act as an internet sharing device).
In case we have some knowledgeable people here, maybe this latest bugcheck analysis could give some hints of what's wrong
Code:
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: 0000000000000000
Debugging Details:
------------------
DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x133
PROCESS_NAME: System
CURRENT_IRQL: d
TAG_NOT_DEFINED_c000000f: FFFFF800A0DBBFB0
LAST_CONTROL_TRANSFER: from fffff800a11ebf4b to fffff800a106c440
STACK_TEXT:
fffff800`a0db5408 fffff800`a11ebf4b : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff800`a0db5410 fffff800`a10b0774 : fffff880`05b18db5 00000000`000f25ce fffff800`a0db5590 fffff780`00000320 : nt! ?? ::FNODOBFM::`string'+0x145a4
fffff800`a0db5490 fffff800`a1780eca : fffff800`a0db5b10 fffff800`a130a180 fffffa80`08111a40 fffffa80`08111ae8 : nt!KeUpdateTime+0x2ec
fffff800`a0db5670 fffff800`a106501e : 00000024`1d684872 fffffa80`096b8010 fffff800`a17aa580 00000000`00000000 : hal!HalpTimerClockInterrupt+0x86
fffff800`a0db56a0 fffff880`0a2e0d87 : fffffa80`096b8010 fffffa80`04dbf018 fffff800`a130a180 fffff800`a0db5b00 : nt!KiInterruptDispatchLBControl+0x1ce
fffff800`a0db5830 fffff800`a10951ea : 00000000`00000002 00000000`00ec6083 fffff800`a0db5939 00000000`00000000 : usb8023x!CancelSendsTimerDpc+0x5b
fffff800`a0db5870 fffff800`a1093655 : 00000000`00000000 fffff800`a1094cff 00000000`00140001 fffff800`a130e040 : nt!KiProcessExpiredTimerList+0x22a
fffff800`a0db59a0 fffff800`a1095668 : fffff800`a130a180 fffff800`a130cf80 00000000`00000003 00000000`0009045e : nt!KiExpireTimerTable+0xa9
fffff800`a0db5a40 fffff800`a1094a06 : fffffa80`00000000 00001f80`00300080 00000000`00000000 00000000`00000002 : nt!KiTimerExpiration+0xc8
fffff800`a0db5af0 fffff800`a10959ba : fffff800`a130a180 fffff800`a130a180 00000000`00183de0 fffff800`a1364880 : nt!KiRetireDpcList+0x1f6
fffff800`a0db5c60 00000000`00000000 : fffff800`a0db6000 fffff800`a0db0000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
usb8023x!CancelSendsTimerDpc+5b
fffff880`0a2e0d87 7549 jne usb8023x!CancelSendsTimerDpc+0xa6 (fffff880`0a2e0dd2)
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: usb8023x!CancelSendsTimerDpc+5b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: usb8023x
IMAGE_NAME: usb8023x.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 51198a2e
BUCKET_ID_FUNC_OFFSET: 5b
FAILURE_BUCKET_ID: 0x133_DPC_usb8023x!CancelSendsTimerDpc
BUCKET_ID: 0x133_DPC_usb8023x!CancelSendsTimerDpc
Followup: MachineOwner
---------
0: kd> lmvm usb8023x
start end module name
fffff880`0a2de000 fffff880`0a2e9000 usb8023x (pdb symbols) c:\cache\usb8023x.pdb\DBA9FFB075764A7EBBBC828D0809D82A1\usb8023x.pdb
Loaded symbol image file: usb8023x.sys
Mapped memory image file: c:\cache\usb8023x.sys\51198A2Eb000\usb8023x.sys
Image path: \SystemRoot\System32\drivers\usb8023x.sys
Image name: usb8023x.sys
Timestamp: Tue Feb 12 02:17:50 2013 (51198A2E)
CheckSum: 00006293
ImageSize: 0000B000
File version: 6.2.9200.16525
Product version: 6.2.9200.16525
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 2.0 Dll
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: usb8023.sys
OriginalFilename: usb8023.sys
ProductVersion: 6.2.9200.16525
FileVersion: 6.2.9200.16525 (win8_gdr.130211-1605)
FileDescription: Remote NDIS USB Driver
LegalCopyright: © Microsoft Corporation. All rights reserved.
Everything worked flawlessly on Win 7. I'm open to any kind of suggestions, because I don't know what's there left to do.
you should report your bug to windows
Oops... Report your issue to windows buddy
Sent from my GT-I9100 using Tapatalk 4
simms22 said:
you should report your bug to windows
Click to expand...
Click to collapse
Yeah, will probably do.