With the end of Microsoft’s support for Windows XP in sight early next year, I began to look at how to upgrade my old system running winxp.<\/p>\n
I would have gone to Windows Vista when it came out in 2007, but the press and user reviews were almost universally bad — a sluggish piece of bloatware than made XP look very good. The in 2009, Windows 7 came out. It got all the good press that Vista lacked: it was speedy, robust and with serious eye candy with the Aero visual theme.<\/p>\n
Except from Windows XP the only one-step way to put 7 on your system was a clean install, meaning drag out all those disks for your programs. A tough order on an OS that came out in 2001.<\/p>\n
So I will upgrade in place to Vista and then later to Windows 7 and I wanted to be sure my system was running at its best.<\/p>\n
It was running well, booting up fast and with few crashes. But for the last week, every time it booted up there was a Svchost.eze error message which stated there was a memory glitch at 0x7C918FEA. <\/p>\n
I looked for the error ignoring that memory location. The error occurs in several different memory locations. What’s more, there were a lot of fixes on the internet, re-registering DLLs and turning off Windows Update then re-enabling it. I tried this over and over. No go. Windows Update was never happy. And Svchost.exe error occurred at every boot up.<\/p>\n
There were many products claiming to fix svchost errors, usually registry cleaners that allegedly fix every kind of Windows problem. I already own several registry cleaners. They fix some things, but are not miracle cures.<\/p>\n
One product even sounds like an infomercial, as it asks “what would you pay a technician to fix this problem? $200? $150?” Good copy, but I was skeptical.<\/p>\n