Windows 7 Files Corrupt with autorun

I've got the same problem with my computer as Max described.

The files are missing as described by Max here - Windows Files Corrupt


and here



Windows Files Corrupt


Quote:

Found the four files from the log but these files which are shown as missing on autorun, I could not find.
Here are the file names:
synth3dvsc.sys
tsusbhub.sys
rdvgkmd.sys
All should be in this folder:
C:\Windows\System32\drivers

Click to expand...

As requested by Noel I started a new thread.
My CheckSUR and CBS logs will be included as soon as possible.

To Noel: For avoiding any mistakes, could you link me a correct guide for "CheckSUR and CBS", please?


Can you or someone else help me out with this one, please?



Best Regards

Hi


can't edit the first post, so I need to reply.


To Noel: For avoiding any mistakes, could you link me a correct guide for "CheckSUR and CBS", please?


and I ran SFCFix.exe at first, like described in the other thread. The log is attached below.

wben353 said:

Try running SFCFix.exe by Niemero with your windows disk in drive http://www.sysnative.com/niemiro/apps/SFCFix.exe

Click to expand...

The SFCFix log doesn't tell us much

CheckSUR:...
Please download and save the CheckSUR tool from http://support.microsoft.com/kb/947821
(you'll need to look in the details for Windows 7, downloading from the Microsoft Download Center)

Run it - The tool can take anywhere from 5 mins to a couple of hours to run (or 'Install') depending on how much it has to do, and may exit silently - it may appear to freeze for most of that time, but be patient.
The result is logged in the C:\Windows\Logs\CBS\CheckSUR.log file - and an archive …\checksur.persist.log file

Then zip the CheckSUR.log and upload it to your reply

CBS log:
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.

Upload the CBS.log file (compressed, please!) to your reply - if it's bigger than 8MB, you'll need to upload it to your OneDrive or DropBox Public folder, and post a link.

Hello,


here the first log


CheckSUR



File-Upload.net - CheckSUR.rar


or dropbox if you like Dropbox - CheckSUR.rar - Simplify your life


CBS log will follow next.


Best Regards

There's nothing showing in the CheckSUR log - and I can't see any major problems in the CBS logs present.

It looks like the SFC is likely to come back clean as well.

Hi


Here the CBS / SFC /SCANNOW log


on Dropbox Dropbox - cbslog and sfcdetails - Simplify your life


and for dowloading File-Upload.net - cbslogandsfcdetails.rar



I don't know if you need the CBS from

C:\Windows\Logs\CBS\CBS.log

Click to expand...

folder,

so I included that folder as well. Did SFC a few times, and attached all logs I could find. Hope thats ok.


Best Regards

As expected, there's no problems in the SFC scan.

I suspect that the root of your error messages is a registry key that wasn't properly dealt with by an update or uninstall - You would have to produce the trace log for the whole time around the errors, showing what is attempting to launch these files.

Many of them only exist on my machine inside the WinSXS folder - which means that they are not part of the basic OS, and may only be required for either compatibility purposes, or for potential edition upgrades...

Unfortunately, my abilities at reading such logs is as limited as 24pt font on a postage stamp - you may want to start a new thread for that, probably in the Performance & Maintenance section of the forum.

Ok. Thank you very much for your help.

I haven't got as much experience as you, so could you please simplify your post for me, please?



I should start a new thread then? Because the files are still missing.


Best Regards

The files may be missing - but since SFC is happy, then it's probably a 'normal' state of affairs.

I wouldn't worry about it unless you are seeing actual errors in applications or the OS - if you are, then post those errors.

It's not unusual for something like Autoruns or Process Explorer to show errors of this kind when there is nothing actually wrong - it's simply picking up on links to files that could potentially exist (and may be of benefit).
If there are no complaints from the originating program, then either it's possibly poorly written, or may have been testing for the existence of the file to determine which fork to take in the following command sequence.