> I have checked the two PCs for Uglyware. One PC did have remnants of some
> stuff which I have since removed. The other appears to be clean. Both are
> scanned daily using Symantec and both have been checked using other software.
>
> This error began showing up on one PC during an upgrade to MS Office Std
> 2003 from Office 97. I enabled extended logging and started the Automatic
> Updates service. The log shows MSI PatchInfo returned 0x8007066f and the
> message 'Unknown Patch'. These are the last entries in the log before the
> crash.
>
> 2007-07-06 14:41:56:629 1668 6d4 Perf, Used cached state for primary patch
> {CB5C177A-7FDB-45E9-AC22-0D8BF529AE57} for product
> {90120406-6000-11D3-8CFE-0150048383C9} for context 4
> 2007-07-06 14:41:56:629 1668 6d4 Perf, Used cached state for primary patch
> {CB5C177A-7FDB-45E9-AC22-0D8BF529AE57} for product
> {90120408-6000-11D3-8CFE-0150048383C9} for context 4
> 2007-07-06 14:41:56:629 1668 6d4 EEHndlr MSI PatchInfo for product
> {90120409-6000-11D3-8CFE-0150048383C9} and patch
> {CB5C177A-7FDB-45E9-AC22-0D8BF529AE57} returned 0x8007066f with state ''
> 2007-07-06 14:41:56:629 1668 6d4 EEHndlr MSI PatchInfo for product
> {90120409-6000-11D3-8CFE-0150048383C9} and patch
> {CB5C177A-7FDB-45E9-AC22-0D8BF529AE57} returned 'Unknown Patch'
> 2007-07-06 14:41:56:629 1668 6d4 Perf, PatchStateForProduct, time, 0, patch,
> primary, {CB5C177A-7FDB-45E9-AC22-0D8BF529AE57}, product,
> {90120409-6000-11D3-8CFE-0150048383C9}, context, 4
>
> I believe the product code refers to MS Office Standard Edition 2003. I have
> not been able to identify the patch as of yet.
>
> I am planning to enable extended logging on the other PC later today to see
> if the same error is being encountered on that computer. The crash began
> occurring on the second computer immediately after the Windows Update Agent
> was updated.
>
>
>
> "Lawrence Garvin (MVP)" wrote:
>
> > "BG72" <BG72[ at ]discussions.microsoft.com> wrote in message
> > news:F0728ABA-1952-46BA-9B4D-22282BDB0524[ at ]microsoft.com...
> > >I have two (out of 40+) client PCs (Win2K SP4) with WSUS Client 3.0 where
> > > svchost.exe for Automatic Updates service crashes with the message
> > > "Application popup: svchost.exe - Application Error : The instruction at
> > > "0x7c58e58e" referenced memory at "0xffffffff". The memory could not be
> > > "read"." We are using WSUS Server 2.0 SP1. I have reinstalled the Client
> > > 3.0
> > > and hotfix 927891. This did not correct the error. Any help on this issue
> > > would be greatly appreciated.
> >
> >
> > Have ya scanned these machines for Uglyware?
> >
> > Quite often memory reference errors are a result of malware trying to do
> > something illegal.
> >
> > Particularly if it's trying to reference memory at address 0xFFFFFFFF <!!!>
> > and is, ostensibly, running in the context of svchost.exe.
> >
> > --
> > Lawrence Garvin, M.S., MCTS, MCP
> > Independent WSUS Evangelist
> > MVP-Software Distribution (2005-2007)
> >
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E> >
> > Everything you need for WSUS is at
> >
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx> >
> > And, almost everything else is at
> >
http://wsusinfo.onsitechsolutions.com> > .....
> >
> >
> >