This installs automatically as a minoport driver along witht he installlation of the onboard wireless. Since my systems crashes and burns so frequently the event log depicts this as one of the reason for a slow restart. I dont use this device so how do I stop it from installing or if I cant how can I remove it and the after crash slow restart performance log enter error - Can I just delete the device and driver???? Driver File Name : \Driver\usbehci Driver Friendly Name : EHCI eUSB Miniport Driver Driver Version : 6.1.7600.16445 (win7_gdr.091023-1601) Driver Total Time : 1952ms Driver Degradation Time : 1552ms Incident Time (UTC) : ‎2010‎-‎08‎-‎04T09:11:01.846076700Z Device Name : PCI\VEN_1002&DEV_4396&SUBSYS_2A92103C&REV_00\3&267a616a&0&9A Device Friendly Name : Standard Enhanced PCI to USB Host Controller Device Total Time : 2003ms

Nobody have this issue or a solution?

this means the USB driver blocks the start for 1.5 seconds. This is not too much. Is your boot completely slow?"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

Yes 1.5 seconds is not that long but it appears as a failure of performance however in the same catagory I also publish request for help about a Foundation Driver System32\Drivers\WUDFdr.sys taking 8.9 seconds which is too long - HEre is that post pasted: Here is one of many event log details and it shows the the location and filename of the Drivers Foundation Service that is taking 8.9 seconds to load after a bsod crash and thus appearing in the diagnotics -performance log. the file WUDFDd.sys is the identified file. This is a new installation and when I look the file properties it does concur with the error info but I dont know how to fix or inprove or replace the .sys file driver used. The dependancies are running but during a crashed restart I cant view the services it is dependent upon but if they were not available for a threshold duration it would make sense they are started because they do not also appear in this event area regarding service restarts being to slow. Log Name: Microsoft-Windows-Diagnostics-Performance/Operational Source: Microsoft-Windows-Diagnostics-Performance Date: 8/3/2010 11:45:10 AM Event ID: 351 Task Category: Standby Performance Monitoring Level: Critical Keywords: Event Log User: LOCAL SERVICE Computer: h1.H1 Description: This driver responded slower than expected to the resume request while servicing this device: Driver File Name : \Driver\WUDFRd Driver Friendly Name : Windows Driver Foundation - User-mode Driver Framework Reflector Driver Version : 6.1.7600.16385 (win7_rtm.090713-1255) Driver Total Time : 8861ms Driver Degradation Time : 8461ms Incident Time (UTC) : ‎2010‎-‎08‎-‎03T18:48:01.377153500Z Device Name : WpdBusEnumRoot\UMB\2&37c186b&1&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_GENERIC-&PROD_MS#MS-PRO&REV_1.00#20060413092100000&3# Device Friendly Name : MS/MS-Pro Device Total Time : 8861ms Device Degradation Time : 8461ms Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Diagnostics-Performance" Guid="{CFC18EC0-96B1-4EBA-961B-622CAEE05B0A}" /> <EventID>351</EventID> <Version>1</Version> <Level>1</Level> <Task>4003</Task> <Opcode>35</Opcode> <Keywords>0x8000000000010000</Keywords> <TimeCreated SystemTime="2010-08-03T18:45:10.686817800Z" /> <EventRecordID>39</EventRecordID> <Correlation ActivityID="{00000100-0000-0003-25D6-F7273533CB01}" /> <Execution ProcessID="1400" ThreadID="1884" /> <Channel>Microsoft-Windows-Diagnostics-Performance/Operational</Channel> <Computer>h1.H1</Computer> <Security UserID="S-1-5-19" /> </System> <EventData> <Data Name="StartTime">2010-08-03T18:48:01.377153500Z</Data> <Data Name="NameLength">15</Data> <Data Name="Name">\Driver\WUDFRd</Data> <Data Name="FriendlyNameLength">65</Data> <Data Name="FriendlyName">Windows Driver Foundation - User-mode Driver Framework Reflector</Data> <Data Name="VersionLength">38</Data> <Data Name="Version">6.1.7600.16385 (win7_rtm.090713-1255)</Data> <Data Name="TotalTime">8861</Data> <Data Name="DegradationTime">8461</Data> <Data Name="PathLength">39</Data> <Data Name="Path">C:\Windows\system32\DRIVERS\WUDFRd.sys</Data> <Data Name="ProductNameLength">37</Data> <Data Name="ProductName">Microsoft® Windows® Operating System</Data> <Data Name="CompanyNameLength">22</Data> <Data Name="CompanyName">Microsoft Corporation</Data> <Data Name="DeviceNameLength">121</Data> <Data Name="DeviceName">WpdBusEnumRoot\UMB\2&amp;37c186b&amp;1&amp;STORAGE#VOLUME#_??_USBSTOR#DISK&amp;VEN_GENERIC-&amp;PROD_MS#MS-PRO&amp;REV_1.00#20060413092100000&amp;3#</Data> <Data Name="DeviceFriendlyNameLength">17</Data> <Data Name="DeviceFriendlyName">MS/MS-Pro </Data> <Data Name="DeviceTotalTime">8861</Data> <Data Name="DeviceDegradationTime">8461</Data> </EventData> </Event>

Make a standby/resume hibernation trace: http://www.msfn.org/board/index.php?showtopic=140247 and upload the trace files. André"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

Hi, As for this performance issue, we generally need to analyze the performance monitor logs and memory dump files to locate the root cause. Unfortunately, debugging is beyond what we can do in the forum because of the nature of forum support. A support call to our product service team is needed for the debugging service. I'd like to recommend that you contact Microsoft Customer Support Service (CSS) for assistance so that this problem can be resolved efficiently. To obtain the phone numbers for specific technology request please take a look at the web site listed below: http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS If you are outside the US please see http://support.microsoft.com for regional support phone numbers. Regards, Linda Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, As for this performance issue, we generally need to analyze the performance monitor logs and memory dump files to locate the root cause. Unfortunately, debugging is beyond what we can do in the forum because of the nature of forum support. not true, I can look at the xbootmgr trace."A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/