MagicAndre1981

Windows 7 = Vista R2/SE. Ask the second question in the XP forums.

upload it to Rapidshare.com or Mediafire.

The cause of the slow login is COMODO (cmdagent.exe) which scans all commands + MSE + you highly fragmented HDD which is used by 100%. same suggestion like aboto. use Aivra AntiVir + Windows included Firewall and run the optimization again.

use a different tools (free tool) like Aivra AntiVir and the in Windows included Firewall.

the files are no real boot traces. Install the WPT and run the xbootmgr command.

I like the new theme.

timing bootDoneViaExplorer="45239" bootDoneViaPostBoot="138339" Your Windows takes 45 to boot to the desktop and 128s to boot completely. <interval name="PreSMSS" startTime="0" endTime="5088" duration="5088"> This takes 5. Which is ok. <interval name="SMSSInit" startTime="5088" endTime="15581" duration="10492"> Provider Name, Task Name, Time (s) , smss:InitializeRegistry, , , 5.941076308, win:Start , , 8.476292276, win:Stop so initializing of the registry take a bit too long. <interval name="WinlogonInit" startTime="15581" endTime="29551" duration="13970"> from what I can see is that KasperSky service starts too slowly: serviceTransition name="AVP" group="" transition="start" totalTransitionTimeDelta="32507" interval name="ExplorerInit" startTime="29551" endTime="45239" duration="15687"> this also takes too long, because of Kaspersky: - <interval name="PostExplorerPeriod" startTime="45239" endTime="138339" duration="93100"> Remove the googleupdater and remove the amount of index folders. The Windows Search service also takes too long to start. I think that Kaspersky is the cause of the slowdown. Remove it.

look at the PATH environment variable and check if the path to the WPT was added.

you have the 64Bit wimgapi.dll in your vLite folder. Delete it.

Hi, timing bootDoneViaExplorer="49970" bootDoneViaPostBoot="116070" Your Windows needs 50s to boot to the desktop and 106 seconds to boot completely. <interval name="PreSMSS" startTime="0" endTime="8469" duration="8469"> Your takes 8.5s, this is ok. <interval name="SMSSInit" startTime="8469" endTime="22670" duration="14200"> this takes 14s which is bit too long. I can see that the time difference between the both csrss.exe is 4s which means it takes 4s to initialize the graphic card driver. Are you using the latest driver or your NVIDIA GeForce GTX 285? <interval name="WinlogonInit" startTime="22670" endTime="40805" duration="18134"> your takes 18s, which is also too long. I found this: - <notification type="Logon" sessionId="1" startTime="29088" endTime="38339" duration="9251"> <subscriber name="Profiles" startTime="29088" endTime="38332" duration="9244" /> So loading the profile takes too long. To see what happens there, download ProcessMonitor and activate bootlogging. Make a new boottrace with xbootmgr and reboot. Start ProcessMonitor again and save the data into a PML file. Zip both files (xbootmgr and PML file) and upload it. <interval name="ExplorerInit" startTime="40805" endTime="49970" duration="9164"> this takes 9.2 seconds. This is also a bit too long. I can see that you use MSE/Commodo which causes a high CPU usage. remove both and see if it it faster. <interval name="PostExplorerPeriod" startTime="49970" endTime="116070" duration="66100"> So starting all startup applications takes too long (56seconds). So use AutoRuns and try to remove all unneeded applications like the google and JAVA update checker.

the AMD Powermanagement driver is already part of Windows since Vista. You don't need to install a driver.

You can't integrate Sp2 with vLite, you must use WinIntegrator from StefanRTR

make a full trace: and give me the trace file.

is the laptop very hot when you have this issue?

ntkrnlmp.exe!PopThermalLogMetricsInformation ACPI.sys!StartTimeSlicePassive Which cooler do you use for your Intel i7? What's the temperature when you have the high DPC usage? I can see core 3 is busy doing all the DPC stuff.

can you upload the etl file?

still the internal defrag, because of this: http://www.msfn.org/board/index.php?showtopic=140262 Hopefully SSD will the cheaper soon, so that all those defrag tools become obsolete.

it looks like the O&O Bootdefrag.

Hi Francis, your Windows takes 210s to boot to the desktop and 299s to boot completely. This is way too much. interval name="PreSMSS" startTime="0" endTime="12766" duration="12766"> The PreSMSS subphase begins when the kernel is invoked. During this subphase, the kernel initializes data structures and components. It also starts the PnP manager, which initializes the BOOT_START drivers that were loaded during the OSLoader phase. When the PnP manager detects a device, it loads and initializes the device’s drivers. This takes for you ~13s. The driver sptd (part of Demon tools, alcohol) takes 4 s to start. Update the driver, please: http://www.duplexsecure.com/downloads/ <pnpObject name="\Driver\sptd" type="Driver" activity="Init" startTime="74" endTime="4117" duration="4043" <interval name="SMSSInit" startTime="12766" endTime="151750" duration="138984"> The SMSSInit subphase begins when the kernel passes control to the session manager process (Smss.exe). During this subphase, the system initializes the registry, loads and starts the devices and drivers that are not marked BOOT_START, and starts the subsystem processes. SMSSInit ends when control is passed to Winlogon.exe. This takes most time (over minutes). I've checked it and found this: smss:BootExecuteList starts at 17s and runs till 128s. I looked in the processlist which tool runs during this time and found this: OODBS. From what I can see this is the BootTimeDefrag from O&O Defrag. interval name="WinlogonInit" startTime="151750" endTime="181256" duration="29506"> The WinLogonInit subphase begins when SMSSInit completes and starts Winlogon.exe. During WinLogonInit, the user logon screen appears, the service control manager starts services, and Group Policy scripts run. WinLogonInit ends when the Explorer process starts. <services autoStartStartTime="166812" autoStartEndTime="339865" autoStartDuration="173052"> The start of the services takes too long. <serviceTransition name="Schedule" group="SchedulerGroup" transition="start" totalTransitionTimeDelta="160760" . The service "Taskscheduler" takes too long to start. serviceTransition name="AVP" group="" transition="start" totalTransitionTimeDelta="70493" . This is the Kaspersky service which takes too long to start. serviceTransition name="hpqddsvc" group="" transition="start" totalTransitionTimeDelta="144772" . A HP printer service is also starting too long. The ICQService also takes 4s to start. Nero BackitUp takes 4.5s to start. serviceTransition name="QBCFMonitorService" group="" transition="start" totalTransitionTimeDelta="23474" . This service is part of Quickbooks 2009 and takes too long to start. serviceTransition name="StarWindServiceAE" group="" transition="start" totalTransitionTimeDelta="107178" StarWind AE Service which is part of Alcohol 120% takes too long. serviceTransition name="VAIO Event Service" group="" transition="start" totalTransitionTimeDelta="12134" Do you need this Sony service? if not, remove it. The services also cause the 2 last 2 phases too proced too slowly. <interval name="ExplorerInit" startTime="181256" endTime="210697" duration="29440"> <interval name="PostExplorerPeriod" startTime="210697" endTime="299397" duration="88700"> The ExplorerInit subphase begins when Explorer.exe starts. During ExplorerInit, the system creates the desktop window manager (DWM) process, which initializes the desktop and displays it for the first time. The PostExplorerPeriod are the startup applications. So, REMOVE ALL crap tools like this: "C:\Program Files\Uniblue\SpeedUpMyPC\", Alcohol, O&O Defrag, Kaspersky, the sony services and other useless things. After doing this, run the boot optimization from here: http://www.msfn.org/board/index.php?showtopic=140262 which trains the ReadyBoot prefetcher (your is damaged): and after doing this, NEVER ever run O&O Defrag, again. It breaks the prefetcher and dramatically slows down Windows! best regards André

the MS ISOs were cleaned (compcln or DISM in Windows 7) thats why you don't see it under installed updates. When you do the offline integration correctly you see it under installed updates. But you miss the 2nd step.

upload the dmp files from the folder C:\Windows\Minidump

zip it and upload it (on your SkyDrive if you have a LiveID or Rapidshare.com) and post a link here.

90s are still a bit to high, make a boot trace (http://www.msfn.org/board/index.php?showtopic=140247), zip and and upload it. Maybe I can find something to reduce the time again.

Hi Chris, your PC is too old. Only 1250MB RAM, an old Athlon XP (single core), a Radeon 9200 (no directX 9 so no Aero). And you are missing several updates. You use an early LDR kernel update from sep 2009. Stay at Xp or buy a new PC.

no this is not normal. are you using the latest BIOS? @reyesjriii and tomek1988 have you both made the dump?