Non repairable files

Hi Britton

Looking at the cbs.log does say that winload.exe and winresume.exe have mismatched hash or corrupted. This are system critical files. I presume this was why you did a clean install ??

In an case could you provide the below.

1. Could you post the SMART value of your HDD / SSD.

2. Could you also post the System as well as Application logs from the system event viewer.

Well first as per the logs your system has shutdown due to high temp...as per ACPI its critical temp and passive temps were at 375K ie; 101 degC... i would suggest you clean the fans..

Secondly... i would suggest you do the sfc scan in offline mode... ie; via the Windows 7 DVD rather than doing the SFC while in windows.

Let me know your feedback once you have done these.

Seems that the custom boot animation bollixed your bcd file which governs the animation. The standard fix is here: Windows 7 Boot screen displays Vista Green Loading Bar - Microsoft Community.

I should tell you that most of the time this has happened I have had to reinstall.

However maybe proceeding to fix the custom animation you want will resolve it, if you still want it anyway.

Otherwise you can try System Restore to before you ran it.

Hi Britton

To use SFC in offline mode you do the following

1. Boot from your Windows 7 DVD
2. On the first screen of Setup choose Next
3. In the lower left of the screen choose "repair your computer"
4. On the System Recovery Options screen choose your installation of Windows and then click next
5. Click "Command prompt"
6. Type in the following command: SFC.EXE /scannow /offbootdir:c:\ /offwindir=c:\windows
7. When complete type in exit to see if Windows starts up now.

Ps: Before doing this .. do check the drive mount points using the command "diskpart" and "list volume"... to confirm the exact drive letter where your windows resides..


Advanced Configuration and Power Interface (ACPI) specification provides an open standard for device configuration and power management by the operating system.

These are taken from the system logs... these are the latest that had happened... The first one below shows the thermal zone TZ00 which is the area where the CPU resides.

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 22/12/2012 7:10:35 AM
Event ID: 89
Task Category: (86)
Level: Information
Keywords: (32)
User: SYSTEM
Computer: DataTechV
Description:
ACPI thermal zone ACPI\ThermalZone\TZ00 has been enumerated.
_PSV = 0K
_TC1 = 0
_TC2 = 0
_TSP = 0ms
_AC0 = 353K
_AC1 = 328K
_AC2 = 273K
_AC3 = 273K
_AC4 = 273K
_AC5 = 0K
_AC6 = 0K
_AC7 = 0K
_AC8 = 0K
_AC9 = 0K
_CRT = 375K
_HOT = 0K
_PSL - see event data.

The second one below shows the thermal zone TZ01 which is the area where the GPU (Graphics card) resides.

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 22/12/2012 7:10:35 AM
Event ID: 89
Task Category: (86)
Level: Information
Keywords: (32)
User: SYSTEM
Computer: DataTechV
Description:
ACPI thermal zone ACPI\ThermalZone\TZ01 has been enumerated.
_PSV = 375K
_TC1 = 1
_TC2 = 5
_TSP = 1000ms
_AC0 = 0K
_AC1 = 0K
_AC2 = 0K
_AC3 = 0K
_AC4 = 0K
_AC5 = 0K
_AC6 = 0K
_AC7 = 0K
_AC8 = 0K
_AC9 = 0K
_CRT = 375K
_HOT = 0K
_PSL - see event data.

Ofcourse these maybe isolated incident ...could have happened when you would be running CPU/GPU intensive games or likes.. This maynot be of concern ...if your cleaning the fans ... regularly... just wanted to point out something that was in the logs for your information.

Hi britton

I have understood you clearly ...

The CBS logs have shows two files as corrupted .... winload.exe and winresume.exe..... which was repaired ... and then as per your last comments you did a SFC again which could have replaced the boot animation to the original.. hence my advice to do the sfc in offline mode ... do the repair and then you can get back to putting your custom animation.

0: Create File: File = [l:262{131}]"\SystemRoot\WinSxS\amd64_microsoft-windows-b..vironment-os-loader_31bf3856ad364e35_6.1.7601.17556_none_b923808583650cfb\winload.exe", Attributes = 00000080
1: Move File: Source = [l:166{83}]"\SystemRoot\WinSxS\Temp\PendingRenames\961a4096ccdfcd01cd3700000404fc06.winload.exe", Destination = [l:262{131}]"\SystemRoot\WinSxS\amd64_microsoft-windows-b..vironment-os-loader_31bf3856ad364e35_6.1.7601.17556_none_b923808583650cfb\winload.exe"
2: Create File: File = [l:266{133}]"\SystemRoot\WinSxS\amd64_microsoft-windows-b..vironment-os-loader_31bf3856ad364e35_6.1.7601.17556_none_b923808583650cfb\winresume.exe", Attributes = 00000080
3: Move File: Source = [l:170{85}]"\SystemRoot\WinSxS\Temp\PendingRenames\961a4096ccdfcd01ce3700000404fc06.winresume.exe", Destination = [l:266{133}]"\SystemRoot\WinSxS\amd64_microsoft-windows-b..vironment-os-loader_31bf3856ad364e35_6.1.7601.17556_none_b923808583650cfb\winresume.exe"
4: Hard Link File: Source = [l:262{131}]"\SystemRoot\WinSxS\amd64_microsoft-windows-b..vironment-os-loader_31bf3856ad364e35_6.1.7601.17556_none_b923808583650cfb\winload.exe", Destination = [l:70{35}]"\??\C:\Windows\System32\winload.exe"
5: Hard Link File: Source = [l:266{133}]"\SystemRoot\WinSxS\amd64_microsoft-windows-b..vironment-os-loader_31bf3856ad364e35_6.1.7601.17556_none_b923808583650cfb\winresume.exe", Destination = [l:74{37}]"\??\C:\Windows\System32\winresume.exe"
6: Checkpoint
7: Move File: Source = [l:192{96}]"\SystemRoot\WinSxS\Temp\PendingRenames\b73e4796ccdfcd01cf3700000404fc06._0000000000000000.cdf-ms", Destination = [l:104{52}]"\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms"
8: Move File: Source = [l:162{81}]"\SystemRoot\WinSxS\Temp\PendingRenames\b73e4796ccdfcd01d03700000404fc06.$$.cdf-ms", Destination = [l:74{37}]"\SystemRoot\WinSxS\FileMaps\$$.cdf-ms"
9: Move File: Source = [l:214{107}]"\SystemRoot\WinSxS\Temp\PendingRenames\78014c96ccdfcd01d13700000404fc0
2012-12-21 17:43:25, Info CSI 6.$$_system32_21f9a9c4a2f8b514.cdf-ms", Destination = [l:126{63}]"\SystemRoot\WinSxS\FileMaps\$$_system32_21f9a9c4a2f8b514.cdf-ms"
10: Create File: File = [l:272{136}]"\SystemRoot\WinSxS\amd64_microsoft-windows-b..os-loader.resources_31bf3856ad364e35_6.1.7600.16385_en-us_d28dabacfdb4dd1a\winload.exe.mui", Attributes = 00000080
11: Move File: Source = [l:174{87}]"\SystemRoot\WinSxS\Temp\PendingRenames\78014c96ccdfcd01d23700000404fc06.winload.exe.mui", Destination = [l:272{136}]"\SystemRoot\WinSxS\amd64_microsoft-windows-b..os-loader.resources_31bf3856ad364e35_6.1.7600.16385_en-us_d28dabacfdb4dd1a\winload.exe.mui"
12: Create File: File = [l:276{138}]"\SystemRoot\WinSxS\amd64_microsoft-windows-b..os-loader.resources_31bf3856ad364e35_6.1.7600.16385_en-us_d28dabacfdb4dd1a\winresume.exe.mui", Attributes = 00000080
13: Move File: Source = [l:178{89}]"\SystemRoot\WinSxS\Temp\PendingRenames\78014c96ccdfcd01d33700000404fc06.winresume.exe.mui", Destination = [l:276{138}]"\SystemRoot\WinSxS\amd64_microsoft-windows-b..os-loader.resources_31bf3856ad364e35_6.1.7600.16385_en-us_d28dabacfdb4dd1a\winresume.exe.mui"
14: Move File: Source = [l:226{113}]"\SystemRoot\WinSxS\Temp\PendingRenames\f9865596ccdfcd01d43700000404fc06.$$_system32_en-us_429cd25484dc6f94.cdf-ms", Destination = [l:138{69}]"\SystemRoot\WinSxS\FileMaps\$$_system32_en-us_429cd25484dc6f94.cdf-ms"
15: Hard Link File: Source = [l:276{138}]"\SystemRoot\WinSxS\amd64_microsoft-windows-b..os-loader.resources_31bf3856ad364e35_6.1.7600.16385_en-us_d28dabacfdb4dd1a\winresume.exe.mui", Destination = [l:94{47}]"\??\C:\Windows\System32\en-US\winresume.exe.mui"
16: Hard Link File: Source = [l:272{136}]"\SystemRoot\WinSxS\amd64_microsoft-windows-b..os-loader.resources_31bf3856ad364e35_6.1.7600.16385_en-us_d28dabacfdb4dd1a\winload.exe.mui", Destination = [l:90{45}]"\??\C:\Windows\System32\en-US\winload.exe.mui"

POQ 126 ends.
2012-12-21 17:43:25, Info CSI 0000034e [SR] Repair complete
2012-12-21 17:43:25, Info CSI 0000034f Creating NT transaction (seq 2), objectname [6]"(null)"
2012-12-21 17:43:25, Info CSI 00000350 Created NT transaction (seq 2) result 0x00000000, handle @0x1228
2012-12-21 17:43:25, Info CSI 00000351@2012/12/21:22:43:25.243 CSI perf trace:
CSIPERF:TXCOMMIT;28693
2012-12-21 17:43:25, Info CBS Reboot mark refs incremented to: 1

Second for Windows search ... follow this link. Though this is not completely related to the error you are having... this method should resolve the access denied error.

Third for the temps like i said.. there were almost 4 to 5 entries in the system logs..this maynot be important.. just thought i would inform you. And like you said.. its just an isolated case..

Britton

On second thought.... For your Windows Search error... try this step...

1. Check your Permissions for Progam Data folder, microsoft folder and the search folder... It should have System or Administrators atleast... if not go to the next step
2. Delete the whole search folder
3. Open properties of the Program Data folder, security tab than click on Advanced. Click on change permissions and then check the box of "include inheritable permissions from this objects parent". This restores all the permissions. Repeat this for the "microsoft" folder too.
4.After that windows search will recreate the search folder with correct permissions.