RE: Problems after system restore: svchost.exe and Win 32 Services

download and install ps5000 xp signed drivers setup launcher maxtor. it
doesnt matter what hard drive you have this will fix your problems.

"Bob" wrote:

> Hi,
>
> I recently performed a system restore and have the same problem as stated by
> MJ in the posting on July 17, 2007 (subject line- Help!! I am ready to throw
> my laptop away....another svchost.exe e). This thread seems to have died so
> I thought I'd ask again.
>
> After the system restore two message boxes started appearing and if I
> cleared them I would lose my wireless internet connection. If I ignore them
> them, everything appears to work but the boxes are in the way. If I open
> internet explorer first then clear them, everything works.
>
> This message comes first: svchost.exe-Application Error
> The instruction at "0x71a58c02" referenced memory at "0x00006ec8". The
> memory could not be written.
>
> After open my user account I get: Generic Host Process for Win32
> Services message: Generic Host Process for Win32 Services encountered a
> problem and needed to close.
>
> I tried the fix from mragho@gmail.com and the Dial-A-Fix suggested by Shenan
> Stanley. No changes. I thought the problem was associated with Norton Ghost
> software because the initial reason I did the restore centered on
> performance issues that would arise when a reminder window would appear to
> tell
> me that the trial period had expired. (The problem arose well after the
> expiration notices started appearing and could be coincidental.)
>
> In addition to the fixes mentioned above, I ran the restore two
> different times to 2 different points, reinstalled McAfee and performed a
> scan, I deleted Ghost (when I did this I lost restore points), and ran the
> error checker (this found and repaired two bad clusters, but did not fix the
> problem).
>
> I did not try solution #2 from Shenan Stanley as it did not work for MJ.
>
> I also installed Update for Windows XP KB927891 (several times, although it
> does not appear in the update log). This is the fix recommended after
> sending an error report on the Win32 problem.
>
> Any additional help is appreciated.
>
> --
> Bob