Sleep, hibernate crash. SFC verify shows ~1000 files WinSxS\FileMaps\

[Dick99999]

Sleep and hibernate suddenly stopped working. After some 10-20 minutes my Win 7 Home (all patches installed) crashes. Cannot see it crashing, only see some disk activity. But the Nirsoft bluescreen viewer shows consistently: DRIVER_POWER_STATE_FAILURE

I ran SFC and it shows that some 1000 files have to be replaced, almost all of them are located in \SystemRoot\WinSxS\FileMaps\...... WinSxS exists and houses some 7500 folders.
Should I really trust SFC and try to let it replace those 1000 files?

I know for sure that perhaps a month ago there was nothing to restore. Hibernate worked at that time. The only big installation I did was Office 2013 preview. And I uninstalled it.

Any help is greatly appreciated.

an exanple of the SFC scan

    6: Move File: Source = [l:312{156}]"\SystemRoot\WinSxS\Temp\PendingRenames\0f062c9202e2cd01e20e00007c1f741f.$$_system32_windowspowershell_v1.0_modules_webadministration_db64c88f44b4aab8.cdf-ms", Destination = [l:224{112}]"\SystemRoot\WinSxS\FileMaps\$$_system32_windowspowershell_v1.0_modules_webadministration_db64c88f44b4aab8.cdf-ms"
    6: Move File: Source = [l:312{156}]"\SystemRoot\WinSxS\Temp\PendingRenames\64fae7c103e2cd01be1e00007c1f741f.$$_system32_windowspowershell_v1.0_modules_psworkflowutility_7f347514a8530874.cdf-ms", Destination = [l:224{112}]"\SystemRoot\WinSxS\FileMaps\$$_system32_windowspowershell_v1.0_modules_psworkflowutility_7f347514a8530874.cdf-ms"
    6: Move File: Source = [l:316{158}]"\SystemRoot\WinSxS\Temp\PendingRenames\e8e09ec702e2cd01fc1100007c1f741f.$$_system32_migwiz_replacementmanifests_microsoft-windows-ndis_b44547c729f73574.cdf-ms", Destination = [l:228{114}]"\SystemRoot\WinSxS\FileMaps\$$_system32_migwiz_replacementmanifests_microsoft-windows-ndis_b44547c729f73574.cdf-ms"
    6: Move File: Source = [l:326{163}]"\SystemRoot\WinSxS\Temp\PendingRenames\5338396502e2cd01260c00007c1f741f.program_files_windows_sidebar_gadgets_picturepuzzle.gadget_en-us_js_ee4c57e840f5e5a0.cdf-ms", Destination = [l:238{119}]"\SystemRoot\WinSxS\FileMaps\program_files
    6: Move File: Source = [l:334{167}]"\SystemRoot\WinSxS\Temp\PendingRenames\7a524ca902e2cd01251000007c1f741f.$$_system32_bestpractices_v1.0_models_microsoft_windows_webserver_en-us_605b350b9dff245b.cdf-ms", Destination = [l:246{123}]"\SystemRoot\WinSxS\FileMaps\$$_system32_bestpractices_v1.0_models_microsoft_windows_webserver_en-us_605b350b9dff245b.cdf-ms"
    70: Move File: Source = [l:282{141}]"\SystemRoot\WinSxS\Temp\PendingRenames\7e84e63802e2cd01ae0a00007c1f741f.program_files_common_files_system_msadc_en-us_58bb034fa66b57cc.cdf-ms", Destination = [l:194{97}]"\SystemRoot\WinSxS\FileMaps\program_files_common_files_system_msadc_en-us_58bb034fa66b57cc.cdf-ms"
    71: Move File: Source = [l:266{133}]"\SystemRoot\WinSxS\Temp\PendingRenames\7e84e63802e2cd01af0a00007c1f741f.program_files_common_files_system_ado_149a784bc852a2c0.cdf-ms", Destination = [l:178{89}]"\SystemRoot\WinSxS\FileMaps\program_files_common_files_system_ado_149a784bc852a2c0.cdf-ms"
    72: Move File: Source = [l:278{139}]"\SystemRoot\WinSxS\Temp\PendingRenames\7e84e63802e2cd01b00a00007c1f741f.program_files_common_files_system_ado_en-us_9c12689ac1360dc2.cdf-ms", Destination = [l:190{95}]"\SystemRoot\WinSxS\FileMaps\program_files_common_files_system_ado_en-us_9c12689ac1360dc2.cdf-ms"
    73: Move File: Source = [l:270{135}]"\SystemRoot\WinSxS\Temp\PendingRenames\dfe5e83802e2cd01b10a00007c1f741f.program_files_common_files_system_en-us_48bd774a3f1387ec.cdf-ms", Destination = [l:182{91}]"\SystemRoot\WinSxS\FileMaps\program_files_common_files_system_en-us_48bd774a3f1387ec.cdf-ms"
    74: Move File: Source = [l:272{136}]"\SystemRoot\WinSxS\Temp\PendingRenames\9fa8ed3802e2cd01b20a00007c1f741f.program_files_common_files_system_ole_db_48d1b11cd4e5cabe.cdf-ms", Destination = [l:184{92}]"\SystemRoot\WinSxS\FileMaps\program_files_common_files_system_ole_db_48d1b11cd4e5cabe.cdf-ms"

 

[gregrocker]

It's hard to say for sure especially if you're running the inherently corrupt factory preinstall. If SFC won't repair the files then the next stop is http://www.sevenforums.com/tutorials/3413-repair-install.html?ltr=R after checking for infection with a full Malwarebytes scan. But you'd be immensely better off if you did what most tech enthusiasts do and http://www.sevenforums.com/tutorials/219487-clean-reinstall-factory-oem-windows-7-a.html#post1839164

I'd immediately establish a Clean Boot and Work through these other http://www.sevenforums.com/tutorials/220165-troubleshooting-steps-windows-7-a.html