Problem Installing SP1 - Windows 7 Home Premium 64 bit

That log is clear of any SFC errors, but there is one minor error in the background CBS data...

Code:

2013-08-07 20:09:09, Info                  CSI    0000009b Component change list:   { (null) -> 7.6.7600.256 Microsoft-Windows-WindowsUpdateClient-Aux.Deployment-LanguagePack, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral }
  { 7.5.7601.17514 -> 7.6.7600.256 Microsoft-Windows-WindowsUpdateClient-Aux.Resources, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral }
  { (null) -> 7.6.7600.256 Microsoft-Windows-WindowsUpdateClient-Aux.Deployment, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral }
  { 7.5.7601.17514 -> 7.6.7600.256 Microsoft-Windows-WindowsUpdateClient-Aux, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral }
2013-08-07 20:09:09, Info                  CSI    0000000d SMI Primitive Installer [done]
2013-08-07 20:09:10, Info                  CBS    Exec: Client did not specify to pend if necessary, no changes have been applied.
2013-08-07 20:09:10, Info                  CSI    0000009c@2013/8/7:19:09:10.351 CSI Transaction @0x131d800 destroyed
2013-08-07 20:09:10, Info                  CBS    Perf: InstallUninstallChain complete.
2013-08-07 20:09:10, Info                  CBS    Failed to execute execution chain. [HRESULT = 0x800f0806 - CBS_E_PENDING]
2013-08-07 20:09:10, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x800f0806 - CBS_E_PENDING]
2013-08-07 20:09:10, Info                  CBS    WER: Failure is not worth reporting [HRESULT = 0x800f0806 - CBS_E_PENDING]

I don't think it needs any attention :)

Looks to me like you have a bitflip or two in the registry....

Code:

2013-08-09 19:45:32, Info                  CBS    External EvaluateApplicability, package: Package_for_KB2779562~31bf3856ad364e35~amd64~~6.1.1.1, package applicable State: Installed, highest update applicable state: Installed, resulting applicable state:Installed
2013-08-09 19:45:32, Info                  CBS    Session: 30315824_2696343127 initialized by client WindowsUpdateAgent.
2013-08-09 19:45:32, Info                  CBS    Invalid enum string [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
2013-08-09 19:45:32, Info                  CBS    Manifest parsing error at line: 1, context: 
="neutral" proceqsorArchitecture="amd64" publicKeyToken="31bf385 [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
2013-08-09 19:45:33, Info                  CBS    Manifest parsing error at line: 1, context: 
="neutral" proceqsorArchitecture="amd64" publicKeyToken="31bf385 [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
2013-08-10 12:38:38, Error                 CSI    000002d8 (F) Manifest parsing failed:
    Status: STATUS_UNSUCCESSFUL
    Node: 2652 (0x00000a5c)
    Node (ln 656 col 96) xpath: /#document/assembly/registryKeys/registryKey/registryValue/@operationHint
    Strings: ([ml:52,l52]"%CommonProgramFiles%\Microsoft Shared\Ink\InkObj.dll")[gle=0x80004005]
2013-08-10 12:38:38, Error                 CSI    000002d9@2013/8/10:11:38:38.212 (F) d:\win7sp1_gdr\base\wcp\manifestparser\pcmc_manifestwalker.cpp(5009): Error STATUS_UNSUCCESSFUL originated in function CMicrodomManifestWalker::CommonReportError expression: (null)
[gle=0x80004005]
2013-08-10 12:38:38, Info                  CSI    000002da [SR] Cannot verify component files for Microsoft-Windows-TabletPC-Platform-COMRuntime, Version = 6.1.7601.18126, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)

It may be worth your while testing your RAM with Memtest86+ (www.memtest.org) - at least 6 passes is the usual recommendation - and see if it throws any errors.

Hmmm - maybe I'm reading it wrong then - Have you run a full CheckSUR or a manufacturer's test utility over the drive?

The same result could be caused by a bitflip in the manifest file, I think.

I'll post up a potential fix for that later, If I can get to it (I have rather a lot of outstanding ones to do!)

Sorry - only 2 hours sleep last night :-(
That should have been CHKDSK not CheckSUR