Help with understanding: sfc /scannow results

[Zappastixs]

Hi

I've got problems with Windows 7 Professional Notebook that I've had for around 8 years.

I've used this old girl every day for hours on end including a great deal with video and audio editing.

On the whole this ASUS N73S machine has rarely let me down, BUT around two months ago (I think after a Windows update)
I now keep receiving "low on memory" pop ups with close desktop message - plus chrome.exe unknown exception oxe0000008
occurred at location 0xfcd84a06d - and often when I restart - and I leave it for a while and then return, I find a static BSOD
sitting there.

The BSOD hasn't happened for a few days, but stupidly I didn't write down the BSOD error reference at anytime.

I've run Speccy - to try and find what would hog the memory - I've also ran Windows Memtest. Nothing was found.

Last night I was about to send this Post when I thought I haven't tried sfc /scannow that I haven't had to use for a few years.

From memory, I thought when I have used this before (loads of times with XP Pro) I always rebooted to start it, but I couldn't
remember so I used elevated command prompt that was the first Google help I came across.

It might be because I've never used command prompt before - but I was surprised at the amount of errors that had been fixed
and on display, but shocked with the errors it couldn't fix because sfc /scannow had always fixed whatever.

I would appreciate if someone can shed some light on the sfc /scannow errors that it cannot fix MORE SO when the results
for unfixed errors state this:"source file in store is also corrupted"

Is there anyway round this?

I thought the idea of sfc /scannow was that Windows kept a perfect copy to compare and fix when needed - how can the
Windows copy become corrupted?

----------------------------------------------------------------------------------------------------------------------
I am a tad confused with the very last line of report when it states this;

2017-11-01 01:08:22, Info CSI 00000377 [SR] Verify and Repair Transaction completed.
All files and registry keys listed in this transaction have been successfully repaired


How can "All files and registry keys listed in this transaction"
have been successfully repaired - when sections are corrupted?
----------------------------------------------------------------------------------------------------------------------

Also one other issue that is confusing - confusing because this machine has INTEL installed
but the 4 error messages that cannot be fixed state this about processor: PROCESSOR_ARCHITECTURE_AMD64


Altogether sfc /scannow displayed around 144 Verify complete - but I have included just five to give you an idea.

After that I've included the errors that can't be fixed - including just a few lines either side.


2017-11-01 00:51:58, Info CSI 00000009 [SR] Verifying 100 (0x0000000000000064) components
2017-11-01 00:51:58, Info CSI 0000000a [SR] Beginning Verify and Repair transaction
2017-11-01 00:52:00, Info CSI 0000000c [SR] Verify complete
2017-11-01 00:52:02, Info CSI 0000000d [SR] Verifying 100 (0x0000000000000064) components
2017-11-01 00:52:02, Info CSI 0000000e [SR] Beginning Verify and Repair transaction
2017-11-01 00:52:03, Info CSI 00000010 [SR] Verify complete
2017-11-01 00:52:05, Info CSI 00000011 [SR] Verifying 100 (0x0000000000000064) components
2017-11-01 00:52:05, Info CSI 00000012 [SR] Beginning Verify and Repair transaction
2017-11-01 00:52:06, Info CSI 00000014 [SR] Verify complete
2017-11-01 00:52:07, Info CSI 00000015 [SR] Verifying 100 (0x0000000000000064) components
2017-11-01 00:52:07, Info CSI 00000016 [SR] Beginning Verify and Repair transaction
2017-11-01 00:52:09, Info CSI 00000018 [SR] Verify complete
2017-11-01 00:52:10, Info CSI 00000019 [SR] Verifying 100 (0x0000000000000064) components
2017-11-01 00:52:10, Info CSI 0000001a [SR] Beginning Verify and Repair transaction
2017-11-01 00:52:12, Info CSI 0000001c [SR] Verify complete



PROCESSOR_ARCHITECTURE_AMD64

2017-11-01 00:55:55, Info CSI 0000011a [SR] Verifying 100 (0x0000000000000064) components
2017-11-01 00:55:55, Info CSI 0000011b [SR] Beginning Verify and Repair transaction
2017-11-01 00:55:58, Info CSI 0000011d [SR] Cannot repair member file [l:22{11}]"PINTLGB.IMD" of Microsoft-Windows-IME-Simplified-Chinese-Core, Version = 6.1.7601.23572, 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
2017-11-01 00:55:58, Info CSI 0000011f [SR] Cannot repair member file [l:22{11}]"PINTLGB.IMD" of Microsoft-Windows-IME-Simplified-Chinese-Core, Version = 6.1.7601.23572, 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
2017-11-01 00:55:58, Info CSI 00000120 [SR] This component was referenced by [l:164{82}]"Package_498_for_KB4041686~31bf3856ad364e35~amd64~~6.1.1.0.4041686-1820_neutral_LDR"
2017-11-01 00:55:58, Info CSI 00000121 [SR] This component was referenced by [l:162{81}]"Package_162_for_KB4041686~31bf3856ad364e35~amd64~~6.1.1.0.4041686-482_neutral_LDR"
2017-11-01 00:55:58, Info CSI 00000124 [SR] Could not reproject corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\IME\IMESC5\DICTS"\[l:22{11}]"PINTLGB.IMD"; source file in store is also corrupted
2017-11-01 00:55:59, Info CSI 00000127 [SR] Verify complete


THIS SECTION IS THE ONLY PART THAT INCLUDES A NAME 'but' ALSO SHOWS IT WAS REPAIRED.

2017-11-01 01:02:31, Info CSI 00000206 [SR] Verifying 100 (0x0000000000000064) components
2017-11-01 01:02:31, Info CSI 00000207 [SR] Beginning Verify and Repair transaction
2017-11-01 01:02:35, Info CSI 00000209 [SR] Repairing corrupted file [ml:520{260},l:74{37}]"\??\C:\Windows\system32\drivers\en-US"\[l:28{14}]"usbhub.sys.mui" from store
2017-11-01 01:02:35, Info CSI 0000020c [SR] Repairing corrupted file [ml:520{260},l:74{37}]"\??\C:\Windows\system32\drivers\en-US"\[l:28{14}]"usbhub.sys.mui" from store
2017-11-01 01:02:36, Info CSI 0000020f [SR] Verify complete


PROCESSOR_ARCHITECTURE_AMD64

2017-11-01 01:08:15, Info CSI 0000035b [SR] Verifying 100 (0x0000000000000064) components
2017-11-01 01:08:15, Info CSI 0000035c [SR] Beginning Verify and Repair transaction
2017-11-01 01:08:20, Info CSI 0000035e [SR] Verify complete
2017-11-01 01:08:20, Info CSI 0000035f [SR] Verifying 2 components
2017-11-01 01:08:20, Info CSI 00000360 [SR] Beginning Verify and Repair transaction
2017-11-01 01:08:20, Info CSI 00000362 [SR] Verify complete
2017-11-01 01:08:20, Info CSI 00000363 [SR] Repairing 3 components
2017-11-01 01:08:20, Info CSI 00000364 [SR] Beginning Verify and Repair transaction
2017-11-01 01:08:20, Info CSI 00000366 [SR] Cannot repair member file [l:22{11}]"PINTLGB.IMD" of Microsoft-Windows-IME-Simplified-Chinese-Core, Version = 6.1.7601.23572, 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
2017-11-01 01:08:20, Info CSI 00000368 [SR] Cannot repair member file [l:22{11}]"PINTLGB.IMD" of Microsoft-Windows-IME-Simplified-Chinese-Core, Version = 6.1.7601.23572, 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
2017-11-01 01:08:20, Info CSI 00000369 [SR] This component was referenced by [l:164{82}]"Package_498_for_KB4041686~31bf3856ad364e35~amd64~~6.1.1.0.4041686-1820_neutral_LDR"
2017-11-01 01:08:20, Info CSI 0000036a [SR] This component was referenced by [l:162{81}]"Package_162_for_KB4041686~31bf3856ad364e35~amd64~~6.1.1.0.4041686-482_neutral_LDR"
2017-11-01 01:08:21, Info CSI 0000036d [SR] Could not reproject corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\IME\IMESC5\DICTS"\[l:22{11}]"PINTLGB.IMD"; source file in store is also corrupted
2017-11-01 01:08:21, Info CSI 0000036f [SR] Repairing corrupted file [ml:520{260},l:74{37}]"\??\C:\Windows\system32\drivers\en-US"\[l:28{14}]"usbhub.sys.mui" from store
2017-11-01 01:08:21, Info CSI 00000372 [SR] Repair complete
2017-11-01 01:08:21, Info CSI 00000373 [SR] Committing transaction
2017-11-01 01:08:22, Info CSI 00000377 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired



Many thanks in advance.

Stephen

 

[Megahertz07]

Fist off all, schedule a disk check. Open Explorer, right click on the drive, properties - Tools tab - Error check - Check now - Auto fix - start. It will say that the disk is in use and if you want to schedule for next boot = Yes

In your place, I would do a Factory Recover.
It seems drastic, but as you have some corrupted files and the backup is also corrupted, it will take less time than trying to fix them.
- Backup your data on an external disk
- Launch Factory Recover (from Windows or from BIOS)
- Open device manager and look for missing drivers
- Install SP1 if you version isn't SP1
- For the updates MS releases SP2 for Windows 7 - Windows 7 Help Forums
- Restore your data.

You have a good laptop. Why don't you install a SSD? You have no idea what a SSD can improve the laptop.
The HDD you can install on an external enclosure or on a ODD replacement enclosure.