Problem Installing SP1 - Windows 7 Home Premium 64 bit

[NoelDP]

It's not an HD problem, as such - merely a file corruption problem.

 

[NoelDP]

FWIW - here's the errors that I'm trying to correct....

2013-09-28 15:11:40, Info                  CSI    00000626 [SR] Beginning Verify and Repair transaction
2013-09-28 15:11:41, Error                 CSI    00000627 (F) Manifest parsing failed:
    Status: STATUS_UNSUCCESSFUL
    Node: 16034 (0x00003ea2)
    Node (ln 3891 col 5) xpath: /#document/assembly/registryKeys/registryKey
    Strings: ([ml:8,l7]"keyName", [ml:0]"", [ml:33,l32]"urn:schemas-microsoft-com:asm.v1", [ml:33,l32]"urn:schemas-microsoft-com:asm.v2", [ml:33,l32]"urn:schemas-microsoft-com:asm.v3")[gle=0x80004005]
2013-09-28 15:11:41, Error                 CSI    [EMAIL="00000628@2013/9/28:14:11:41.153"]00000628@2013/9/28:14:11:41.153[/EMAIL] (F) d:\w7rtm\base\wcp\manifestparser\pcmc_manifestwalker.cpp(5009): Error STATUS_UNSUCCESSFUL originated in function CMicrodomManifestWalker::CommonReportError expression: (null)
[gle=0x80004005]
2013-09-28 15:11:41, Info                  CSI    00000629 [SR] Cannot verify component files for Microsoft-Windows-IE-HTMLRendering, Version = 8.0.7601.17514, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)

2013-09-28 14:59:42, Error                 CSI    000001f1 (F) Manifest parsing failed:
    Status: STATUS_UNSUCCESSFUL
    Node: 2607 (0x00000a2f)
    Node (ln 675 col 18) xpath: /#document/assembly/registryKeys/registryKey/@keyName
    Strings: ([ml:81,l81]"HKEY_CLAQSES_ROOT\Interface\{2EE48F22-AF3C-405F-8970-F71BE12EE9A2}\ProxyStubClsid")[gle=0x80004005]
2013-09-28 14:59:42, Error                 CSI    [EMAIL="000001f2@2013/9/28:13:59:42.147"]000001f2@2013/9/28:13:59:42.147[/EMAIL] (F) d:\w7rtm\base\wcp\manifestparser\pcmc_manifestwalker.cpp(5009): Error STATUS_UNSUCCESSFUL originated in function CMicrodomManifestWalker::CommonReportError expression: (null)
[gle=0x80004005]

2013-09-28 14:55:53, Error                 CSI    000000d8 (F) Manifest parsing failed:
    Status: STATUS_UNSUCCESSFUL
    Node: 7420 (0x00001cfc)
    Node (ln 1812 col 18) xpath: /#document/assembly/registryKeys/registryKey/@keyName
    Strings: ([ml:82,l82]"HKEY]CLASSES_ROOT\Interface\{3050F2A7-98B5-11CF-BB82-00AA00BDCE0B}\ProxyStubClsid\")[gle=0x80004005]
2013-09-28 14:55:53, Error                 CSI    [EMAIL="000000d9@2013/9/28:13:55:53.263"]000000d9@2013/9/28:13:55:53.263[/EMAIL] (F) d:\w7rtm\base\wcp\manifestparser\pcmc_manifestwalker.cpp(5009): Error STATUS_UNSUCCESSFUL originated in function CMicrodomManifestWalker::CommonReportError expression: (null)
[gle=0x80004005]

2013-09-28 14:17:51, Error                 CSI    00000587 (F) Manifest parsing failed:
    Status: STATUS_UNSUCCESSFUL
    Node: 17377 (0x000043e1)
    Node (ln 4195 col 18) xpath: /#document/assembly/registryKeys/registryKey/@keyName
    Strings: ([ml:82,l82]"HKEY_CLASSES_RMOT\Interface\{6A6841DF-3287-3D87-8060-CE0B4C77D2A1}\ProxyStubClsid\")[gle=0x80004005]
2013-09-28 14:17:51, Error                 CSI    [EMAIL="00000588@2013/9/28:13:17:51.235"]00000588@2013/9/28:13:17:51.235[/EMAIL] (F) d:\w7rtm\base\wcp\manifestparser\pcmc_manifestwalker.cpp(5009): Error STATUS_UNSUCCESSFUL originated in function CMicrodomManifestWalker::CommonReportError expression: (null)
[gle=0x80004005]

This hopefully should be contained within the following lines.....

2013-09-28 15:11:41, Info                  CSI    00000629 [SR] Cannot verify component files for Microsoft-Windows-IE-HTMLRendering, Version = 8.0.7601.17514, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
    Strings: ([ml:82,l82]"[B]HKEY]CLASSES[/B]_ROOT\Interface\{3050F2A7-98B5-11CF-BB82-00AA00BDCE0B}\ProxyStubClsid\")[gle=0x80004005]
    Strings: ([ml:81,l81]"HKEY_[B]CLAQSES[/B]_ROOT\Interface\{2EE48F22-AF3C-405F-8970-F71BE12EE9A2}\ProxyStubClsid")[gle=0x80004005]
    Strings: ([ml:82,l82]"HKEY_CLASSES_[B]RMOT[/B]\Interface\{6A6841DF-3287-3D87-8060-CE0B4C77D2A1}\ProxyStubClsid\")[gle=0x80004005]

Many of these appear to be caused by registry corruption in the HKCR Key (boldened)- and I can claim no experience in dealing with such errors.
The temptation is to simply attempt to delete the corrupted Keys and hope that the system can cope - which it may well do - but I have no idea how to cope with it if it doesn't work, and the indications are that it's possibly due to RAM problems, or other intermittent hardware faults.

I would suggest re-checking the RAM using MemTest86+ over at least 6 passes, and see if that holds up. If it does, a deep stress-test of the motherboard would be worth doing. There is something here that I've no experience of, and I have to admit to grasping at straws....

 

[andrew129260]

I'm not happy to say this, but that defiantly indicates exactly what I thought. It looks like its laying the blame on the sata controller. In a normal machine, there would be never be disk errors. If you find them, even on just one day, it means you do have problems. As a test though, do the following:

1.) Try buying new sata cables and replace the ones you have in your system. Then check the event viewer for awhile. If over a week you have no more errors, and your able to install service pack one that should mean this issue is solved.
If the errors continue, its highly possible the sata connector on the motherboard is bad.

A bad Sata controller or a bad sata cable can cause all kinds of weird issues with slowness, failed large installations and the like.

2.) Try a new hard drive with a new sata cable.
(This is assuming you have already tried a known good hard drive in your system)

From Microsoft's website on the error code:
http://www.microsoft.com/technet/su...=5.2.3790.1830&EvtID=11&EvtSrc=disk&LCID=1033
http://support.microsoft.com/kb/154690

@NoelDP

Isn't it possible it could be a hard disk/sata controller/sata cable problem?
If these are even slightly going bad, that would cause file corruption across the board at random times.
I have seen this happen before on some systems.
With them errors all being recorded as event ID 11, this concerns me.

 

[NoelDP]

You have a point - I hadn't had a close look at the evtlog snapshot.

It's certainly worth testing.

 

[IcecoldUK]

Hi guys,

Attached are the results of memtest86+ which I left running over night: 10hrs 48mins, 6 passes and no errors. I've completed a total of 19 passes over 3 separate tests, none of which have found any errors.

I'll purchase some new SATA Cables and see if the disk errors continue. I'll also try stress testing the motherboard, do you know of any program's you could recommend?

Jon

 

[IcecoldUK]

Sorry, I forgot the attach the memtest results!

Jon

 

[Layback Bear]

Just a thought.
Also replace the power cable to the drive. A fluctuating voltage can also cause goofy things to happen.

IcecoldUK what power supply do you have?

A poor power supply can cause many problems and the codes you get may not be related to the base problem.

 

[IcecoldUK]

Last night I ran a few stress tests on my motherboard using BurnInTest from Passmark. I ran the tests on all of the system components including the Hard Drives, CPU, RAM and Graphics Card, all of which passed.

@layback Bear

My current PSU is an Arctic Power 700W

I have started to wonder if the power supply could be a factor in all of this. My reason being that in some of my previous posts I have also referred to a problem with the Nvidia graphics card driver (nvlddmkm) crashing and successfully recovering. I have looked through countless forums as to the cause of this error, and while some suggest minor alterations to the graphics software settings, some are suggesting that it maybe caused by insufficient power. I've been using the same set-up since I built the system approx 3 years ago so I guess the PSU could be dying?

Jon

 

[andrew129260]

Try a known good power supply, (or buy a new one), and try new sata cables. See what happens.

Keep an eye on event viewer.