Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Help Reading CBS.Log


15 Sep 2013   #1

Windows 7 Home Premium x64
 
 
Help Reading CBS.Log

Not quite sure what forum this problem should go in, so I'm putting it here in general I guess.

So long story (Skip to bottom for actual current question). I downloaded Final Fantasy VII off steam and tried to play it. The game repeatedly crashed without error message. I tried to skip the launcher and try opening the game file directly. That gives me an error message of "d3dx9_29.dll is missing...." So I try rebooting.

So I check the integrity of the game files. They say no problem, but it doesn't work so I delete them and redownload again anyway. Now the game's launcher will open, but the game file still gives the same error message and clicking on the play button just causes the screen to flash for a second and then the launcher comes back up with no message whatsoever.

Well, that looks like a DirectX problem maybe so I try to update directX. Running the .exe from Windows gives me a message that "An internal system error occurred. Please refer to DXError.log and DirectX.Log in your Windows folder to determine problems." OK. That seemed straightforward enough... But DXError.log doesn't exist on my computer and DirectX.Log only has two lines:

"02/17/12 23:04:22: infinst: Installing C:\Users\ADMINI~1\AppData\Local\Temp\DXFA36.tmp\d3dx9_32_x64.inf [DefaultInstall]

02/17/12 23:04:22: infinst: Installed file C:\Windows\system32\d3dx9_32.dll
"

Well, nothing useful there maybe. So I did some research online and ran checkdisk and sfc. Checkdisk came up clean but SFC found errors that it couldn't fix and told me to consult CBS.log. Well that seemed hard, so I just ran SFC twice more to see if it would change its mind and repair whatever anyway. (it didn't). Still get the message "Windows Resource Protection found corrupt files but was unable to fix some of them."

So, I've opened CBS.log and yeah, good luck reading that. But the internet tells me that using:

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"

in cmd will let me just grab the legible parts of the data. And I think I have found the errors it's mentioning, though I'm not sure how this ends up relating back to the original problem at all. I think I'm copying the relevant info, though I can post the whole illegible log if it will help.

So, my current question is this: What does the below text actually mean? (Also, does it actually relate at all to my initial problem?)
Code:
2013-09-16 00:25:39, Info                  CSI    000002e2 [SR] Beginning Verify and Repair transaction
2013-09-16 00:25:41, Info                  CSI    000002e5 [SR] Cannot verify component files for Microsoft.VC80.MFCLOC, Version = 8.0.50727.6195, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
2013-09-16 00:25:42, Info                  CSI    000002e8 [SR] Verify complete
2013-09-16 00:25:42, Info                  CSI    000002e9 [SR] Verifying 100 (0x0000000000000064) components
2013-09-16 00:25:42, Info                  CSI    000002ea [SR] Beginning Verify and Repair transaction
2013-09-16 00:25:44, Info                  CSI    000002ec [SR] Verify complete
2013-09-16 00:25:44, Info                  CSI    000002ed [SR] Verifying 100 (0x0000000000000064) components
2013-09-16 00:25:44, Info                  CSI    000002ee [SR] Beginning Verify and Repair transaction
2013-09-16 00:25:45, Info                  CSI    000002f0 [SR] Verify complete
2013-09-16 00:25:45, Info                  CSI    000002f1 [SR] Verifying 100 (0x0000000000000064) components
2013-09-16 00:25:45, Info                  CSI    000002f2 [SR] Beginning Verify and Repair transaction
2013-09-16 00:25:47, Info                  CSI    000002f4 [SR] Verify complete
2013-09-16 00:25:47, Info                  CSI    000002f5 [SR] Verifying 100 (0x0000000000000064) components
2013-09-16 00:25:47, Info                  CSI    000002f6 [SR] Beginning Verify and Repair transaction
2013-09-16 00:25:48, Info                  CSI    000002f9 [SR] Cannot verify component files for policy.8.0.Microsoft.VC80.CRT, Version = 8.0.50727.6195, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:24{12}]"win32-policy", TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
2013-09-16 00:25:48, Info                  CSI    000002fc [SR] Cannot verify component files for policy.8.0.Microsoft.VC80.MFCLOC, Version = 8.0.50727.6195, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:24{12}]"win32-policy", TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
2013-09-16 00:25:48, Info                  CSI    000002ff [SR] Cannot verify component files for policy.8.0.Microsoft.VC80.MFC, Version = 8.0.50727.6195, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:24{12}]"win32-policy", TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
2013-09-16 00:25:48, Info                  CSI    00000302 [SR] Cannot verify component files for policy.8.0.Microsoft.VC80.OpenMP, Version = 8.0.50727.6195, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:24{12}]"win32-policy", TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
2013-09-16 00:25:49, Info                  CSI    00000304 [SR] Verify complete
2013-09-16 00:25:49, Info                  CSI    00000305 [SR] Verifying 27 (0x000000000000001b) components
2013-09-16 00:25:49, Info                  CSI    00000306 [SR] Beginning Verify and Repair transaction
2013-09-16 00:25:50, Info                  CSI    00000308 [SR] Verify complete
2013-09-16 00:25:50, Info                  CSI    00000309 [SR] Repairing 5 components
2013-09-16 00:25:50, Info                  CSI    0000030a [SR] Beginning Verify and Repair transaction
2013-09-16 00:25:50, Info                  CSI    0000030d [SR] Cannot verify component files for Microsoft.VC80.MFCLOC, Version = 8.0.50727.6195, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
2013-09-16 00:25:50, Info                  CSI    00000310 [SR] Cannot verify component files for policy.8.0.Microsoft.VC80.CRT, Version = 8.0.50727.6195, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:24{12}]"win32-policy", TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
2013-09-16 00:25:50, Info                  CSI    00000313 [SR] Cannot verify component files for policy.8.0.Microsoft.VC80.MFCLOC, Version = 8.0.50727.6195, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:24{12}]"win32-policy", TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
2013-09-16 00:25:50, Info                  CSI    00000316 [SR] Cannot verify component files for policy.8.0.Microsoft.VC80.MFC, Version = 8.0.50727.6195, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:24{12}]"win32-policy", TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
2013-09-16 00:25:50, Info                  CSI    00000319 [SR] Cannot verify component files for policy.8.0.Microsoft.VC80.OpenMP, Version = 8.0.50727.6195, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:24{12}]"win32-policy", TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
2013-09-16 00:25:50, Info                  CSI    0000031b [SR] Repair complete



My System SpecsSystem Spec
.

16 Sep 2013   #2

Desk1 8 Pro / Desk2 7 Home Prem / Laptop 8.1 Pro all 64bit
 
 

Hello and welcome Bwertz mate I am not conversant with those sorts of files but I did find this and it looks very much like the OS has become corrupted I am not real sure.
How to analyze the log file entries that the Microsoft Windows Resource Checker (SFC.exe) program generates in Windows Vista

If you need to repair then this might help Startup Repair
My System SpecsSystem Spec
Reply

 Help Reading CBS.Log




Thread Tools



Similar help and support threads for2: Help Reading CBS.Log
Thread Forum
What are you reading? Chillout Room
Reading a old HD Hardware & Devices
Solved Dir CMD not reading as it did General Discussion
What are you reading Chillout Room
Reading fan RPM's Hardware & Devices
not reading DVD Installation & Setup
CPU reading? Performance & Maintenance

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 03:18 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33