Windows Resource Protection found corrupt files but was unable to fix

tsilva · 25 Dec 2013

Hello!

Last month something happenned to my pc that i'm not really sure about what happenned. My pc was fine one day, i went to sleep, and the next day it wouldn't boot. In the "Starting Windows" it gave me a quick BSOD and my pc would restart. But eventually after searching the web i found a solution, a guy told me to go to the BIOS and change the disk mode from IDE to AHCI, and that worked! But then, i ran the "sfc /scannow" just to make sure that everything was ok, and gave me the message "Windows Resource Protection found corrupt files but was unable to fix some of them". Later on, i found another forum, where a guy would analyze my CBS.log that the "sfc /scannow" would make after analising my computer, and he would give a script to correct the errors every time i ran the "sfc /scannow". We were working this out at a good pace, but then he said he had an assignment to make and it's been a month since the last time we spoke. I wouldn't mind waiting because my computer was working fine. But a few days ago my computer started "misbehaving" again. Now, everytime i boot up my computer starts analising my disk (i think) through CHKDSK. This happens everytime! The CHKDSK says i have some bad files and such, but it doesn't do anything to them, it's like it removes the same files in every analysis. I have to skip the CHKDSK to get to Windows, and if i didn't do that, i would be stuck in a loop between CHKDSK and restart (the computer restarts in the end of the CHKDSK analysis, if you don't know). And when i get to Windows it gives me two errors saying "C:\Windows\Fonts\upcli.ttf" and "C:\Windows\Fonts\upclbi.ttf" are illegible. And today, my computer couldn't even find my router, but i fixed that by uninstalling the wireless controller and install it again. And right now, my computer is really really slow! Writing something on google it freezes or opening a folder, i have to wait a few seconds! It's like it slows down for a few minutes. Everything is really slow and a few minutes later it's everything with the normal speed, but this keeps happening. The "sfc /scannow" know stucks at 18% and says it couldn't finish. I'm really frustated, it's like everytime i fix something a new problem will appear at some point in time. I could really use your help.

Sorry for the enormous post and sorry if this is not the correct topic for Windows Update, i wasn't sure.

Best regards

NoelDP · 25 Dec 2013

Please follow the Windows Update Posting Instructions and post the requested data

tsilva · 25 Dec 2013

Sorry, didn't notice that. I'm already runninf SURT but it's taking too long to update, is it normal? And where do i have to "Leave it to run uninterrupted." ?

NoelDP · 25 Dec 2013

It often takes anywhere from 15 minutes to 3 hours - I think the record for a successful run is about 6 hours, but much depends on the computer's specs, and the number of problems it finds.

Please be patient.

tsilva · 25 Dec 2013

Oh, thank you. I thought it was my computer's fault, because like i told you earlier, i don't know what's happening to my computer because from time to time it really slows down and i have to wait a few minutes for him to get back to normal speed. Is it better to leave the computer alone to do the update or can i continue to do my stuff?

NoelDP · 25 Dec 2013

Keep on working - but be prepared for it to slow down occasionally as it goes through its cycles.

tsilva · 25 Dec 2013

Okay, thank you :) I'll post everything after i finish doing everything in the Posting Instructions.

tsilva · 25 Dec 2013

Hello again.

So, i executed the SURT, and that completed well and didn't me give any error.
Next, i executed the "sfc/ scannow", but like i told on my first post it gets stuck, but this time it was at 20%, and says "windows resource protection could not perform the requested operation".
I tried to update but gave me an error. The image is in Portuguese, if you want any translation, tell me please.
Attachment 298765
And here's the CBS log:
Attachment 298766

NoelDP · 26 Dec 2013

Please post the CheckSUR.log file as well - that's necessary to establish the results of the tool's scan.

The SFC scan broke down with the following error...

Code:

2013-12-25 23:46:28, Info                  CSI    0000011f [SR] Beginning Verify and Repair transaction
2013-12-25 23:46:36, Error                 CSI    00000120 (F) STATUS_FILE_CORRUPT_ERROR #1838374# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = (AllowFileNotFound|AllowSharingViolation|AllowAccessDenied), handle = {provider=NULL, handle=0}, da = (SYNCHRONIZE|FILE_READ_ATTRIBUTES|FILE_READ_DATA), oa = @0xa7ce40->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[128]"\SystemRoot\WinSxS\amd64_microsoft-windows-font-truetype-lilyupc_31bf3856ad364e35_6.1.7600.16385_none_767d64eb7a9abcc4\upcll.ttf"; a:(OBJ_CASE_INSENSITIVE)}, iosb = @0xa7cef0, as = (null), fa = 0, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), cd = FILE_OPEN, co = (FILE_NON_DIRECTORY_FILE|FILE_SYNCHRONOUS_IO_NONALERT), eab = NULL, eal = 0, disp = Invalid)
[gle=0xd0000102]
2013-12-25 23:46:36, Error                 CSI    00000121@2013/12/25:23:46:36.973 (F) d:\win7sp1_gdr\base\wcp\sil\merged\ntu\ntsystem.cpp(2057): Error STATUS_FILE_CORRUPT_ERROR originated in function Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile expression: (null)
[gle=0x80004005]
2013-12-25 23:46:37, Error                 CSI    00000122 (F) STATUS_FILE_CORRUPT_ERROR #1838373# from Windows::Rtl::SystemImplementation::CDirectory::OpenExistingFile(...)[gle=0xd0000102]
2013-12-25 23:46:37, Error                 CSI    00000123 (F) STATUS_FILE_CORRUPT_ERROR #1838372# from Windows::Rtl::SystemImplementation::CDirectory_IRtlDirectoryTearoff::OpenExistingFile(flags = (MissingFileIsOk|SharingViolationIsOk|AccessDeniedIsOk), da = (SYNCHRONIZE|FILE_READ_DATA), oa = @0xa7d4e8->SIL_OBJECT_ATTRIBUTES {s:40; on:"upcll.ttf"; a:(OBJ_CASE_INSENSITIVE)}, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), oo = (FILE_SYNCHRONOUS_IO_NONALERT|FILE_NON_DIRECTORY_FILE), file = NULL, disp = Invalid)
[gle=0xd0000102]

I suspect that this may be the result of filesystem problems rather than actual file corruptions - please run a CHKDSK and see what it has to say - followed by another SFC scan...

Please run a full CHKDSK and SFC scan....

Click on Start > All Programs > Accessories
Right-click on the Command Prompt entry
Select Run as Administrator and accept the UAC prompt - the Elevated Command Prompt window should pop up.

At the Command prompt, type

CHKDSK C: /R

and hit the Enter key.
You will be told that the drive is locked,
and the CHKDSK will run at he next boot - hit the Y key, press Enter, and then reboot.

The CHKDSK will take a few hours depending on the size of the drive, so be patient!

After the CHKDSK has run, Windows should boot normally (possibly after a second auto-reboot) -
then run the SFC.

SFC -System File Checker - Instructions
Click on Start > All Programs > Accessories
Right-click on the Command Prompt entry
Select Run as Administrator and accept the UAC prompt - the Elevated Command Prompt window should pop up.

At the Command prompt, type

SFC /SCANNOW

and hit the Enter key

Wait for the scan to finish - make a note of any error messages - and then reboot.

Copy the CBS.log file created (C:\Windows\Logs\CBS\CBS.log) to your desktop (you can't manipulate it directly) and then compress the copy and upload it to your reply

tsilva · 26 Dec 2013

Ok, i'll do that. Sorry, heres the "CheckSUR.log".
Attachment 298810
Tell me if that's the only file you need, because, there's other files that i don't know if you need, like, "CheckSUR.persist" and some Winrar files that say "CbsPersist_(random huge number)"