Win 7 X64 spooler issues.

[Galkins]

Have a machine running Win 7 home premium 64 bit, it had an HP MFC printer connected to it but then suddenly stopped working.

Some hours of looking about found the problem was the spooler service stopped starting,
checked c:\windows\system32\ and found spoolsv.exe was renamed spoolsv.exe.log, removed the wrong version of spoolsv.exe and put back in the correct version and spooler started up fine.

Problem is that every time the machine reboots the problem repeats itself. On checking the event log, aside from the message that the spooler failed to start the only other error I get is:
The Remote Procedure Call (RPC) Sync failed to start due to the following error:
This version of RPC Sync is not compatible with the version of windows you're running...


Any ideas on if the two are related and how to resolve the spooler problem?

 

[richc46]

The best and easy solution would be a quick system restore.
http://www.sevenforums.com/tutorials/700-system-restore.html

 

[Galkins]

I'd rather do a restore as a last resort, I'd prefer to know if this problem will re-occur and how or why it happened.

 

[richc46]

You may be able to fix it with an SFC scan.
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html
It is a form of corruption. It may have happened during a shutdown, power surge, etc. I do not know the exact cause, but we can take measure to correct the problem.

 

[Galkins]

SFC scan says it found corrupt files but was unable to fix. Posted to the cbi.log but beyond me as to what in the log to look for exactly.

 

[richc46]

I will get instructions on finding the log. But run the SFC several times, it has difficulty fixing all files at once.

 

[richc46]

If and when needed or for your own information. The cbs log
How to analyze the log file entries that the Microsoft Windows Resource Checker (SFC.exe) program generates in Windows Vista
For Vista and Seven

 

[Galkins]

Ok running out of fingers to count the number of times I've run SFC

Looking at the log it seems to be tcpmon.ini that is causing the problem, here's an excerpt

2010-10-28 02:09:38, Info CSI 00000122 [SR] Beginning Verify and Repair transaction
2010-10-28 02:09:41, Info CSI 00000123 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.1.7600.16385_none_2e6dc451c0fa9db5\tcpmon.ini do not match actual file [l:20{10}]"tcpmon.ini" :
Found: {l:32 b:as3OOcx5px0XiJa7f7s9BVvlW/FFlKR4NMU/T+UP/Kg=} Expected: {l:32 b:ENtKeUct91LKlHclgfWTvnCdCOHHwDe+SYrPzZTTezU=}
2010-10-28 02:09:41, Info CSI 00000124 [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2010-10-28 02:09:44, Info CSI 00000125 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.1.7600.16385_none_2e6dc451c0fa9db5\tcpmon.ini do not match actual file [l:20{10}]"tcpmon.ini" :
Found: {l:32 b:as3OOcx5px0XiJa7f7s9BVvlW/FFlKR4NMU/T+UP/Kg=} Expected: {l:32 b:ENtKeUct91LKlHclgfWTvnCdCOHHwDe+SYrPzZTTezU=}
2010-10-28 02:09:44, Info CSI 00000126 [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2010-10-28 02:09:44, Info CSI 00000127 [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.WindowsFoundationDelivery"
2010-10-28 02:09:44, Info CSI 00000128 Hashes for file member \??\C:\Windows\System32\tcpmon.ini do not match actual file [l:20{10}]"tcpmon.ini" :
Found: {l:32 b:as3OOcx5px0XiJa7f7s9BVvlW/FFlKR4NMU/T+UP/Kg=} Expected: {l:32 b:ENtKeUct91LKlHclgfWTvnCdCOHHwDe+SYrPzZTTezU=}
2010-10-28 02:09:44, Info CSI 00000129 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.1.7600.16385_none_2e6dc451c0fa9db5\tcpmon.ini do not match actual file [l:20{10}]"tcpmon.ini" :
Found: {l:32 b:as3OOcx5px0XiJa7f7s9BVvlW/FFlKR4NMU/T+UP/Kg=} Expected: {l:32 b:ENtKeUct91LKlHclgfWTvnCdCOHHwDe+SYrPzZTTezU=}
2010-10-28 02:09:44, Info CSI 0000012a [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:20{10}]"tcpmon.ini"; source file in store is also corrupted

 

[richc46]

Ill look it over, but for now ME Bad, I should have told you about 3 times, is enough.

 

[richc46]

Ok this is what I know for a fact
SFC should fix that file.
If it does not a repair install is needed.
It may or may not correct your problem, but my guess is that it will
So its the above or system restore
or wait for other answers.

Whatever you decide, I wish you the best and will offer any help that you may need.