MagicAndre1981

You're welcome. Enjoy your Windows 7

ok, do this. nice to hear this in this case it is caused by the USB mouse/keyboard. Run latencymon and look what the highest spike is. Is it still green? If yes, it is ok and you can ignore it.

upload a hibernation trace, too.

I have no idea about the sleep issue. disable the hybrid sleep and use hibernation. Run RAMMap after Windows is booted, save the data and upload the zipped data. I can't see this from the trace.

it is a bit better: timing bootDoneViaExplorer="101374" bootDoneViaPostBoot="132174" osLoaderDuration="2325" postBootRequiredIdleTime="10000" postBootDisturbance="20800" booting to the desktop takes 101s and Windows is booted completely in 122s. <interval name="PreSMSS" startTime="0" endTime="14782" duration="14782"> <phase name="systemStart" startTime="3915" endTime="14526" duration="10610"> <pnpObject name="SRTSP" type="Driver" activity="Load" startTime="4392" endTime="6770" duration="2377" prePendTime="2377" /> <pnpObject name="\REGISTRY\MACHINE\SYSTEM\ControlSet001\services\SRTSP" type="unknown" activity="unknown" startTime="4413" endTime="6770" duration="2356" prePendTime="2356" /> again, the Symantec drivers are a bit slow. The SMSSInit phase still takes too long. The time difference between both csrss.exe shows me that loading the graphic drivers still takes too long. <interval name="SMSSInit" startTime="14782" endTime="42792" duration="28010"> <interval name="WinlogonInit" startTime="42792" endTime="95105" duration="52312"> - <winlogon numNotifications="3"> - <notification type="CreateSession" sessionId="1" startTime="57585" endTime="66330" duration="8745"> <subscriber name="GPClient" startTime="57585" endTime="66328" duration="8743" /> the group policies take 8.8 seconds which is faster but the WinlogonInit phase takes too long becasue RequestCredentials takes 24 seconds. Type in the password faster. The starting the services is faster: <services autoStartStartTime="54591" autoStartEndTime="81762" autoStartDuration="27171"> the applications at startup take 20 to finish. i can see that the memory usage is extremely high (2GB in use at the boot time). Look if you can remove more tools and if you can update Symantec.

can you ask someone if he can lend you a USB keyboard for testing purpose. So you can see if this fixes it.

you can slipstream the Sp1 with the reverse integration (audit mode, Sp1 install, sysprep, capture image with ImageX). Now DISM works. Vista Sp1 will be out of support on 12th July 2011. so slipstream the Sp2, too.

DISM works with Vista Sp1/Sp2 images. Which issue do you have?

zoom into the spikes, and cehck the summary table. There you only see the PS2 driver as cause. storport is HDD / RAID related: Source: http://msdn.microsoft.com/en-us/library/ff567541%28v=vs.85%29.aspx Do you use such devices? Also install the Sp1, you still use the Win7 RTM with an outdated kernel.

it's only a minor issue. I only wanted to point this out. Logout and a new login fixed it.

hal? the Interrupt (ISR) spikes are all caused by the PS2 driver. Do you still have any issues with the USB mouse?

the i8042prt.sys driver causes the spikes. This is the PS2 mouse/keyboard driver. I can see you use the Microsoft PS/2 Mouse/Standard PS/2 Keyboard. Can you connect them to USB?

upload the file to mediafire.com please. I can't access the file on megaupload

I visited the forum today and saw that I was not shown in the online list. So I logged out and logged in again and now I'm back in the list. Do you know why I had to do this?

to get the source code to the same level for the RTM and Sp1 branch and to prevent the issue with Sp2.

the Updates prevents your Windows 7 to get the 0xc0000034 error when installing the Sp1. So integrating the update into a Sp1 Image is useless.

Have you installed the mobile version of the AMD 11.5 driver? There is a version for desktop, for mainbaord IGPs and for notebooks. This is the latest Intel graphic card driver: http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=19940〈=eng

Use RegShot to make a RegistryShot, chaage the value and make a 2nd Shot. Now let the software compare both shots so that you can see the difference. This helps you to get any value you need.

link the DLLs static into the Exe. The exe is a bit larger but works on all system even if you don't have the redistributables installed. So it should work in PE, too.

timing bootDoneViaExplorer="123194" bootDoneViaPostBoot="162594" osLoaderDuration="2449" postBootRequiredIdleTime="10000" postBootDisturbance="29400" your Windows needs 123s to boot to the desktop and 152s to boot completely. This is too much. The first delay occurs in the PreSMSS Phase: <interval name="PreSMSS" startTime="0" endTime="14808" duration="14808"> this Phase takes 15s. I can see that those driver is a bit too slow to start: <pnpObject name="SRTSP" type="Driver" activity="Load" startTime="6062" endTime="8695" duration="2633" prePendTime="2633" /> <pnpObject name="\REGISTRY\MACHINE\SYSTEM\ControlSet001\services\SRTSP" type="unknown" activity="unknown" startTime="6148" endTime="8695" duration="2547" prePendTime="2547" /> what is this SRTSP driver? Can you install an update? next the AMD drivers are slow: <pnpObject name="amdkmdap" type="Driver" activity="Load" startTime="13909" endTime="19452" duration="5542" prePendTime="5542" /> <pnpObject name="\REGISTRY\MACHINE\SYSTEM\ControlSet001\services\amdkmdap" type="unknown" activity="unknown" startTime="14055" endTime="19452" duration="5397" prePendTime="5397" /> <pnpObject name="intelkmd" type="Driver" activity="Load" startTime="14926" endTime="18283" duration="3356" prePendTime="3356" /> <pnpObject name="NETwNs64" type="Driver" activity="Load" startTime="20532" endTime="22280" duration="1747" prePendTime="1747" /> Install the Catalyst 11.5 driver for your ATI Mobility Radeon HD 3400. Also update the Intel Wireless driver (NETwNs64 - Intel® WiFi Link 5100 AGN). The Intelkmd looks like the Intel graphic card driver (Mobile Intel® 4 Series Express). Update this driver, too. Which chip do you use most time? The Intel or the AMD? If you only use 1, disable the other. <interval name="WinlogonInit" startTime="36266" endTime="101416" duration="65149"> - <winlogon numNotifications="3"> - <notification type="CreateSession" sessionId="1" startTime="53334" endTime="74859" duration="21525"> <subscriber name="GPClient" startTime="53334" endTime="74858" duration="21524" /> <subscriber name="TermSrv" startTime="74858" endTime="74859" duration="1" /> </notification> - <notification type="Logon" sessionId="1" startTime="88650" endTime="100619" duration="11969"> <subscriber name="Profiles" startTime="88650" endTime="95054" duration="6403" /> <subscriber name="GPClient" startTime="95054" endTime="100614" duration="5559" /> The WinlogonInit Phase is slow because of the group policies you apply. It takes 21.5s to start the user session because the GP Client takes 21.4s to finish. I saw this message in the trace: "The specified domain either does not exist or could not be contacted. " So the server can't be found. Make sure the server is available when you logon. Also ask the admin about the group policies. Also starting all services takes too long (69s): - <services autoStartStartTime="42642" autoStartEndTime="111673" autoStartDuration="69031"> where the following services take some time to start: serviceTransition name="vpnagent" group="TDI" transition="start" totalTransitionTimeDelta="5604" serviceTransition name="FontCache3.0.0.0" group="" transition="start" totalTransitionTimeDelta="34532" serviceTransition name="VMAuthdService" group="" transition="start" totalTransitionTimeDelta="14568" You can stop the FontCache3.0.0.0 service and set the starttype to disabled. I only effects some WPF applications. You can also set the startype of the VMWare services to "on demand" and run them from a script (net start VMAuthdService) and run the script with the task scheduler a few minutes after the boot is done). the ExplorerInit and PostBoot take 50s. The Symnatec Endpoint protection and the large amount of tools like the LENOVO tools for your laptop cause the delay. Check which tools are not required all time and disable them with AutoRuns. You must also run the Prefetcher optimization I liked in the first topic. Your Prefetcher is completely unoptimized. It has a lot of misses which causes a large amount of HDD IO activity. I now look at the standby trace and tell you the results.

xperf doesn't show all. I helps to get some hints. I can see that the HDD is busy most the time and that those 3 drivers cause a lot of CPU usage. Write a PM to cluberti so that he can look at the latest trace. he is the genius here and knows more compared to us normal users. To get a better help you should contact the MS Support if we can't help ypu.

this not possible without breaking it (vLite, RT7Lite). Use StefanRTRs tool which removes the packages, this is safe but only removes a few things.

do the old Clean Boot approach and eliminate all 3rd party apps/services. I really don't see why the 3 drivers cause the high CPU usage.

theoretically the DWM is possible to do the same effects. But I don't see any sens for such visual effects/eye candy. They bring no work improvements.

build your own Windows Embedded Standard 7 version with the packages you need.