Strange and I'm not seeing anything other than that this has now started from a relatively new system a few years ago to a few years later and the install may have picked up on something that has now changed - even to the point that a load sequence is now different from what it was in yesteryears. Two things you might try with to see if something else comes out in the wash:
FIRST:
1. The "command-line" tool (Tasklist.exe) run with the wanted "Syntax" allows you to obtain a list of active processes that are running. For each process, it displays the process name and process identifier (PID). For more information about the Task List or the related Task Kill and Process Viewer tools, click Tools in Help and Support Center.
2. In addition, "A Description of Svchost.exe in Windows XP (Q314056)."
Note: The article [Q314056] explains that at startup, Svchost.exe checks the services part of the registry to construct a list of services that it must load. Multiple instances of Svchost.exe can run at the same time. Each Svchost.exe session can contain a grouping of services. Therefore, separate services can run, depending on how and where Svchost.exe is started. This grouping of services permits better control and easier debugging.
3. When you start Windows, dozens of programs are already running - many of them invisible and running in the background. "AutoStart Viewer" allows you to see every autostart on your system, all on the one screen. In addition, it gives you complete control over the autostart references, and allows you to modify or delete them at will. Key features are:
? Over 50 different autostart locations monitored!
? Right-click menu allows you to take complete control over each autostart
? Add New Autostart feature allows you to add new programs to automatically start
? Save/Print functions allow you to take snapshots
? Resizable, easy-to-use interface that shows every autostart on the one display
? All sizes, positions and settings are remembered
SECOND:
Use the NTBTLOG.TXT file to potentially identify startup problems.
a. "Enable Boot Logging" to creates a text log file in the systemroot directory with this name and can be double-clicked for viewing. The log lists files that Windows attempts to load and precedes the path of each by identifying them as Loaded driver or Did not load driver. Restart the computer, and when prompted, press F8, and then select Enable Boot Logging on the Windows Advanced Options Menu. Else, the articles [Q833721] and [Q323427] discusses the procedure for editing the Boot.ini file to enable boot logging.
Note: If a critical system file is corrupted or missing, Windows might generate a STOP message or write an entry to the "Event logs" or both, which you may not even be aware of.
b. To check an item listed in the Did not load driver section:
? Check for zero byte files or files with date and time stamps that do not match the Windows installation date.
? Compare files in systemroot\System32 to the same files on the Windows CD or another computer running the same edition (and service pack(s)).
? Run the System File Checker (Sfc.exe) command-line tool to inspect system files, [Q310747].
Chowhound
Comic Vine
GameFAQs
GameSpot
Giant Bomb
TechRepublic