[mclimbin]

I ran the SFC, and chose the option to just verify if there are errors. Answer: Yes!

windows Rescource Protection found integrity violations. Details are included in the CBS.Log windir\logs\CBS\CBS.log. For example C:\windows\Logs\CBS\CBS.log

I checked the path above and found a file called cbs.log, but it says I don't have access to view it. I played around in the Properties folder but could not figure out how to get access.

Should I just run SFC so that it will fix the problems?

Edited by mclimbin, 17 February 2012 - 10:01 AM.

[Advertisements]

Should I just run SFC so that it will fix the problems?

Yes. Run SFC with Full Administer Rights, 1. Click on Windows 7 Start Button

2. Go to All Programs-> Accessories

3. Now right on Command Prompt and select “Run as Administrator” from context menu.


Remember you may have to run it more than once.

Edited by iammykyl, 17 February 2012 - 04:01 PM.

[iammykyl]

Should I just run SFC so that it will fix the problems?

Yes. Run SFC with Full Administer Rights, 1. Click on Windows 7 Start Button

2. Go to All Programs-> Accessories

3. Now right on Command Prompt and select “Run as Administrator” from context menu.


Remember you may have to run it more than once.

Edited by iammykyl, 17 February 2012 - 04:01 PM.

[mclimbin]

I ran it 4 times and got this message all 4 times:

Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log widndir\logs\cbs.log For example C:\Windows\Logs\CBS\CBS.log.

I was finally able to get access to the cbs log. Here are the last few entries for today. Let me know if this is helpful or if you need other info.

Verify complete
2012-02-17 15:16:32, Info CSI 000008d2 [SR] Verifying 100 (0x0000000000000064) components
2012-02-17 15:16:32, Info CSI 000008d3 [SR] Beginning Verify and Repair transaction
2012-02-17 15:16:33, Info CSI 000008d4 Repair results created:
POQ 352 starts:
0: Move File: Source = [l:192{96}]"\SystemRoot\WinSxS\Temp\PendingRenames\95721230caedcc01849d000054061817._0000000000000000.cdf-ms", Destination = [l:104{52}]"\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms"
1: Move File: Source = [l:162{81}]"\SystemRoot\WinSxS\Temp\PendingRenames\a5991230caedcc01859d000054061817.$$.cdf-ms", Destination = [l:74{37}]"\SystemRoot\WinSxS\FileMaps\$$.cdf-ms"
2: Move File: Source = [l:224{112}]"\SystemRoot\WinSxS\Temp\PendingRenames\b6c01230caedcc01869d000054061817.$$_microsoft.net_3296b36dbe4c7fa3.cdf-ms", Destination = [l:136{68}]"\SystemRoot\WinSxS\FileMaps\$$_microsoft.net_3296b36dbe4c7fa3.cdf-ms"
3: Move File: Source = [l:244{122}]"\SystemRoot\WinSxS\Temp\PendingRenames\c6e71230caedcc01879d000054061817.$$_microsoft.net_framework_83386eac0379231b.cdf-ms", Destination = [l:156{78}]"\SystemRoot\WinSxS\FileMaps\$$_microsoft.net_framework_83386eac0379231b.cdf-ms"
4: Move File: Source = [l:266{133}]"\SystemRoot\WinSxS\Temp\PendingRenames\f85c1330caedcc01889d000054061817.$$_microsoft.net_framework_v2.0.50727_e9368840261e60ee.cdf-ms", Destination = [l:178{89}]"\SystemRoot\WinSxS\FileMaps\$$_microsoft.net_framework_v2.0.50727_e9368840261e60ee.cdf-ms"
5: Move File: Source = [l:288{144}]"\SystemRoot\WinSxS\Temp\PendingRenames\09841330caedcc01899d000054061817.$$_microsoft.net_framework_v2.0.50727_redistlist_2e6ab8b35e9ef953.cdf-ms", Destination = [l:200{100}]"\SystemRoot\WinSxS\FileMaps\$$_microsoft.net_framework_v2.0.50727_redistlist_2e6ab8b35e9ef953.cdf-ms"

POQ 352 ends.
2012-02-17 15:16:33, Info CSI 000008d5 [SR] Verify complete
2012-02-17 15:16:33, Info CSI 000008d6 [SR] Verifying 100 (0x0000000000000064) components
2012-02-17 15:16:33, Info CSI 000008d7 [SR] Beginning Verify and Repair transaction
2012-02-17 15:16:34, Info CSI 000008d8 Repair results created:
POQ 353 starts:

POQ 353 ends.
2012-02-17 15:16:34, Info CSI 000008d9 [SR] Verify complete
2012-02-17 15:16:34, Info CSI 000008da [SR] Verifying 100 (0x0000000000000064) components
2012-02-17 15:16:34, Info CSI 000008db [SR] Beginning Verify and Repair transaction
2012-02-17 15:16:35, Info CSI 000008dc Repair results created:
POQ 354 starts:

POQ 354 ends.
2012-02-17 15:16:35, Info CSI 000008dd [SR] Verify complete
2012-02-17 15:16:35, Info CSI 000008de [SR] Verifying 49 (0x0000000000000031) components
2012-02-17 15:16:35, Info CSI 000008df [SR] Beginning Verify and Repair transaction
2012-02-17 15:16:35, Info CSI 000008e0 Repair results created:
POQ 355 starts:

POQ 355 ends.
2012-02-17 15:16:35, Info CSI 000008e1 [SR] Verify complete
2012-02-17 15:16:35, Info CSI 000008e2 [SR] Repairing 3 components
2012-02-17 15:16:35, Info CSI 000008e3 [SR] Beginning Verify and Repair transaction
2012-02-17 15:16:35, Info CSI 000008e4 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-c..t-xpsomandstreaming_31bf3856ad364e35_6.1.7601.17514_none_0d3e7fe8fbc0cf07\xpsservices.dll do not match actual file [l:30{15}]"xpsservices.dll" :
Found: {l:32 b:5svJ2OCoYyIOHiJY2OwT+PlRoCQ3nsncB5g6m9R66xk=} Expected: {l:32 b:QefAVzvUHscaQPszf4c7IyHGNzU0i9mqMCq7BN7h2tk=}
2012-02-17 15:16:35, Info CSI 000008e5 [SR] Cannot repair member file [l:30{15}]"xpsservices.dll" of Microsoft-Windows-Component-XpsOMAndStreaming, Version = 6.1.7601.17514, 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
2012-02-17 15:16:35, Info CSI 000008e6 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-font-truetype-mingliu_31bf3856ad364e35_6.1.7600.16385_none_170f5b78a1ae6145\mingliu.ttc do not match actual file [l:22{11}]"mingliu.ttc" :
Found: {l:32 b:GJ/VSsh9AsARl+zhOSPCP/WxMT8wJvoOUPpLEqH24ao=} Expected: {l:32 b:tkLDtHJJwUtuNYZoM+KYBp+eXXaghwuxjZqqT1x3TCg=}
2012-02-17 15:16:35, Info CSI 000008e7 [SR] Cannot repair member file [l:22{11}]"mingliu.ttc" of Microsoft-Windows-Font-TrueType-MingLiU, 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
2012-02-17 15:16:35, Info CSI 000008e8 Hashes for file member \SystemRoot\WinSxS\amd64_prnhp005.inf_31bf3856ad364e35_6.1.7600.16385_none_30e9a6119eda44e5\Amd64\hpfstw73.dll do not match actual file [l:36{18}]"Amd64\hpfstw73.dll" :
Found: {l:32 b:mau2KSPQqxqAItCQ97OfqB4ae+sGjFvRFm/Ej/GNKH8=} Expected: {l:32 b:7HRJIIizElJvZi1icuBOg4i6J5cK4KtFPQcyouasXqw=}
2012-02-17 15:16:35, Info CSI 000008e9 [SR] Cannot repair member file [l:36{18}]"Amd64\hpfstw73.dll" of prnhp005.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-02-17 15:16:36, Info CSI 000008ea Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-c..t-xpsomandstreaming_31bf3856ad364e35_6.1.7601.17514_none_0d3e7fe8fbc0cf07\xpsservices.dll do not match actual file [l:30{15}]"xpsservices.dll" :
Found: {l:32 b:5svJ2OCoYyIOHiJY2OwT+PlRoCQ3nsncB5g6m9R66xk=} Expected: {l:32 b:QefAVzvUHscaQPszf4c7IyHGNzU0i9mqMCq7BN7h2tk=}
2012-02-17 15:16:36, Info CSI 000008eb [SR] Cannot repair member file [l:30{15}]"xpsservices.dll" of Microsoft-Windows-Component-XpsOMAndStreaming, Version = 6.1.7601.17514, 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
2012-02-17 15:16:36, Info CSI 000008ec [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery"
2012-02-17 15:16:36, Info CSI 000008ed Hashes for file member \??\C:\Windows\System32\xpsservices.dll do not match actual file [l:30{15}]"xpsservices.dll" :
Found: {l:32 b:5svJ2OCoYyIOHiJY2OwT+PlRoCQ3nsncB5g6m9R66xk=} Expected: {l:32 b:QefAVzvUHscaQPszf4c7IyHGNzU0i9mqMCq7BN7h2tk=}
2012-02-17 15:16:36, Info CSI 000008ee Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-c..t-xpsomandstreaming_31bf3856ad364e35_6.1.7601.17514_none_0d3e7fe8fbc0cf07\xpsservices.dll do not match actual file [l:30{15}]"xpsservices.dll" :
Found: {l:32 b:5svJ2OCoYyIOHiJY2OwT+PlRoCQ3nsncB5g6m9R66xk=} Expected: {l:32 b:QefAVzvUHscaQPszf4c7IyHGNzU0i9mqMCq7BN7h2tk=}
2012-02-17 15:16:36, Info CSI 000008ef [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:30{15}]"xpsservices.dll"; source file in store is also corrupted
2012-02-17 15:16:36, Info CSI 000008f0 Hashes for file member \SystemRoot\WinSxS\amd64_prnhp005.inf_31bf3856ad364e35_6.1.7600.16385_none_30e9a6119eda44e5\Amd64\hpfstw73.dll do not match actual file [l:36{18}]"Amd64\hpfstw73.dll" :
Found: {l:32 b:mau2KSPQqxqAItCQ97OfqB4ae+sGjFvRFm/Ej/GNKH8=} Expected: {l:32 b:7HRJIIizElJvZi1icuBOg4i6J5cK4KtFPQcyouasXqw=}
2012-02-17 15:16:36, Info CSI 000008f1 [SR] Cannot repair member file [l:36{18}]"Amd64\hpfstw73.dll" of prnhp005.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-02-17 15:16:36, Info CSI 000008f2 [SR] This component was referenced by [l:186{93}]"Microsoft-Windows-Printer-Drivers-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.INF_prnhp005"
2012-02-17 15:16:36, Info CSI 000008f3 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-font-truetype-mingliu_31bf3856ad364e35_6.1.7600.16385_none_170f5b78a1ae6145\mingliu.ttc do not match actual file [l:22{11}]"mingliu.ttc" :
Found: {l:32 b:GJ/VSsh9AsARl+zhOSPCP/WxMT8wJvoOUPpLEqH24ao=} Expected: {l:32 b:tkLDtHJJwUtuNYZoM+KYBp+eXXaghwuxjZqqT1x3TCg=}
2012-02-17 15:16:36, Info CSI 000008f4 [SR] Cannot repair member file [l:22{11}]"mingliu.ttc" of Microsoft-Windows-Font-TrueType-MingLiU, 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
2012-02-17 15:16:36, Info CSI 000008f5 [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery"
2012-02-17 15:16:36, Info CSI 000008f6 Hashes for file member \??\C:\Windows\fonts\mingliu.ttc do not match actual file [l:22{11}]"mingliu.ttc" :
Found: {l:32 b:GJ/VSsh9AsARl+zhOSPCP/WxMT8wJvoOUPpLEqH24ao=} Expected: {l:32 b:tkLDtHJJwUtuNYZoM+KYBp+eXXaghwuxjZqqT1x3TCg=}
2012-02-17 15:16:36, Info CSI 000008f7 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-font-truetype-mingliu_31bf3856ad364e35_6.1.7600.16385_none_170f5b78a1ae6145\mingliu.ttc do not match actual file [l:22{11}]"mingliu.ttc" :
Found: {l:32 b:GJ/VSsh9AsARl+zhOSPCP/WxMT8wJvoOUPpLEqH24ao=} Expected: {l:32 b:tkLDtHJJwUtuNYZoM+KYBp+eXXaghwuxjZqqT1x3TCg=}
2012-02-17 15:16:36, Info CSI 000008f8 [SR] Could not reproject corrupted file [ml:520{260},l:40{20}]"\??\C:\Windows\fonts"\[l:22{11}]"mingliu.ttc"; source file in store is also corrupted
2012-02-17 15:16:36, Info CSI 000008f9 Repair results created:
POQ 356 starts:

POQ 356 ends.
2012-02-17 15:16:36, Info CSI 000008fa [SR] Repair complete
2012-02-17 15:16:36, Info CSI 000008fb [SR] Committing transaction
2012-02-17 15:16:36, Info CSI 000008fc Creating NT transaction (seq 4), objectname [6]"(null)"
2012-02-17 15:16:36, Info CSI 000008fd Created NT transaction (seq 4) result 0x00000000, handle @0xacc
2012-02-17 15:16:36, Info CSI 000008fe@2012/2/17:23:16:36.905 CSI perf trace:
CSIPERF:TXCOMMIT;3
2012-02-17 15:16:36, Info CSI 000008ff [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired
2012-02-17 15:26:37, Info CBS Reboot mark refs incremented to: 1
2012-02-17 15:26:37, Info CBS Scavenge: Starts
2012-02-17 15:26:37, Info CSI 00000900@2012/2/17:23:26:37.217 CSI Transaction @0x15ecc90 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195} with flags 00000002 and client id [10]"TI6.0_0:0/"

2012-02-17 15:26:37, Info CBS Scavenge: Begin CSI Store
2012-02-17 15:26:37, Info CSI 00000901 Performing 1 operations; 1 are not lock/unlock and follow:
Scavenge (8): flags: 00000017
2012-02-17 15:26:37, Info CSI 00000902 Store coherency cookie matches last scavenge cookie, skipping scavenge.
2012-02-17 15:26:37, Info CSI 00000903 ICSITransaction::Commit calling IStorePendingTransaction::Apply - coldpatching=FALSE applyflags=7
2012-02-17 15:26:37, Info CSI 00000904 Creating NT transaction (seq 5), objectname [6]"(null)"
2012-02-17 15:26:37, Info CSI 00000905 Created NT transaction (seq 5) result 0x00000000, handle @0x1150
2012-02-17 15:26:37, Info CSI 00000906@2012/2/17:23:26:37.964 CSI perf trace:
CSIPERF:TXCOMMIT;283278
2012-02-17 15:26:37, Info CBS Scavenge: Completed, disposition: 0X1
2012-02-17 15:26:37, Info CSI 00000907@2012/2/17:23:26:37.965 CSI Transaction @0x15ecc90 destroyed
2012-02-17 15:26:38, Info CBS Reboot mark refs: 0
2012-02-17 15:26:38, Info CBS Idle processing thread terminated normally
2012-02-17 15:26:38, Info CBS Ending the TrustedInstaller main loop.
2012-02-17 15:26:38, Info CBS Starting TrustedInstaller finalization.
2012-02-17 15:26:38, Info CBS Ending TrustedInstaller finalization.

[mclimbin]

Crash report: two crashes recently, on the 16th and one on the 18th. Both are the same type as the others, Kernal 41.

[iammykyl]

There are still many errors and looks to me to be related to Driver/Driver updates.

We can try a System repair or a clean install. http://www.sevenforu...ir-install.html
I would still back up Any important Data you want to keep.

[iammykyl]

Hi.

Been a little timesince our last post.

How are things going.

[iammykyl]

Is there anybody there, Moriarty?

[mclimbin]

Hi iammykyl,
Thanks for keeping up with me on this. The system is much more stable, but I still get a crash every now and then. I got one on the 19th when the computer was idle (no one was using it) and once more on the 23rd. On the 23rd I tried to shut it down and forced a program to close and then it shut off without shutting down correctly.

I've been considering buying an SSD. Since it would be a new, clean install, do you think it would solve these problems? Or do you think it will cause more problems?

I don't really need an SSD, but I have a couple hundred dollars and some spare time, so I thought it would be cool. I don't know if it will even improve my speed that much. What do you think?

[iammykyl]

Thanks for keeping up with me on this.

Your welcome, though I have not been able to solve the problem yet. The hardware appears to be OK so we are down to corrupted software/drivers.
I think the best solution would be to backup any DATA you require and do a clean install on your existing hard drive.

I don't really need an SSD, but I have a couple hundred dollars and some spare time, so I thought it would be cool. I don't know if it will even improve my speed that much. What do you think?

I agree, so no. A SSD does decrease load time and helps with micro stutter, gaming, but does very little for performance in every day usage. In your case, to expensive as you need capacity for your boot drive.

I would use your existing drive as prices are still very high and I have noticed a huge increase in rectified drives for sale, so the rumours of a drop in quality control may be correct.

This is about the size I would go for, http://www.newegg.co...N82E16822136697

Edited by iammykyl, 29 March 2012 - 09:15 PM.

[mclimbin]

Hi again imammykyl,

Thanks for the info about the SSDs. Understood.

I tried to do a system repair with the Win7 disk, but was unable to get it to work. I was not sure which option to choose once the PC booted up with the Windows disk. The "system restore" and the "system image recovery" options wouldn't work, since the system is the most stable it has ever been. Going back would make it worse! The memory test was not appropriate either, so I chose "startup repair." It ran for a few seconds and then said that no problems were found.

As for doing a total wipe and re-installing, to tell you the truth, I don't want to do that at this point. It would take a ton of work to re-install all my software and drivers and get everything back to the way it is now, so that my family and I can use it as we do now. If it were crashing every day or even every other day, I might be desperate enough to do that, but the system is fairly stable now, thanks to all the stuff we have done already (thanks to you, that is).

Do you know what I mean?

If you can think of anything else we can do to improve stability, I'd be interested in following up on that.

thanks again,
mc

[iammykyl]

I fully understand your reluctance to do a clean install, recovery is made simpler if restore points and images are created.

When you do get a new HDD, install the OS as a Duel Boot configuration, make the old OS the first boot option, let the family use that one and keep the new installation solely for yourself.

When you get the time, post the last current Who Crashed Log, I will then get another member to investigate and see if there are other options to effect a repair.

We changed Automatic Updates, it should be changed back to the defaults so you get any critical fixes.

AS you have continued responding on the thread, it has been a pleasure helping, only sorry I was unable to wholly solve the problem

Keep in touch.

[mclimbin]

So, hello, I'm back after only 3 days, as I had two crashes today. Event log says the same as before--Kernal-Power 41.

I'm now seriously considering your idea of buying another HDD and doing a dual boot configuration.

I'm not sure what you mean by Who Crashed log. Is that the same as the Event Log? What exactly would you like me to post?

[iammykyl]

I think a 2 drive set up is the way to go so investigating more with BSOD problems (software) should be abandoned. I still want to look at hardware though.

I propose drive one for the family all with individualize limited accounts, so they cannot make system alterations and you as admin, password protected..
The new drive two as solely for you with a partition for backing up the whole computer?

I'm not sure what you mean by Who Crashed log. Is that the same as the Event Log?

I think you did the Who Crashed in the other Topic and downloaded the results from the event viewer Log.

Have you any USB devices connect besides the Moue, Keyboard?
Have you installed a Card Reader, Web Cam, Fan Controller, etc?
Is your Back up drive connected when you get BSOD?

Turn off, take anti static measure, open both sides of the case. You need to check that the screws holding down the Mobo match the stand offs that are screwed into the Mobo mounting plate. Look at the back of the mounting plate, you should be able to see the threaded ends of the stand-offs. Make sure they match the pattern of screws in the Mobo and there are no extra ones.

Edited by iammykyl, 30 March 2012 - 11:57 PM.

[mclimbin]

Nope, I don't have a screw loose. There are no extra screws either. Everything looks good as far as I can tell.

Devices that are connected via usb:
printer (could connect that wifi--has a card reader)
mouse, keyboard
backup hard drive (always connected)

I did have a usb wifi adapter but it was not working well so I replaced it with an Asus pce-n15 pci-e wireless card. Works awesome by the way!

I have a usb webcam but have not installed it yet.

I just bought a portable HD, My Passport 500 gb, but I just started using it now.

[iammykyl]

Can't see than any of that hardware would be a problem.

Just looked all the way through your other BSOD topic, problems were never actually fixed.

I do think that a clean install is the only way to go, otherwise it will be just going around in circles.