New
#11
Yes, I have tried doing that around 5 times and still have files to repair. I just disabled verifier
Yes, I have tried doing that around 5 times and still have files to repair. I just disabled verifier
Here's the sfc log, in case it helps:
There was many corrupted files, which have now been repaired.Code:2013-02-23 14:19:45, Info CSI 00000799 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired
The above command will only scan and check for corrupted files, it will not attempt to repair these files. It's best to check that all the system files are not corrupted.Code:sfc /verifyonly
Install and perform full scans with:
- Malwarebytes : Free anti-malware download
- Microsoft Security Essentials | Protect against viruses, spyware, and other malware
Remember to install the free version of Malwarebytes not the free trail; untick the free trial box during installation. MSE is the most lightweight and compatible with the Windows 7 operating system.
You can also view this thread for a complete free and lightweight security protection combination:
Both scans found no threats, and I also got a new bsod a couple mins ago (driver irql not less or equal):
ps: sfc still finds corrupted files
For the corrupted files, you can try a Repair Install:
Code:BugCheck D1, {c1, b, 0, fffff8800492824e} *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : nvlddmkm.sys ( nvlddmkm+bc24e )Code:1: kd> lmvm nvlddmkm start end module name fffff880`0486c000 fffff880`05314000 nvlddmkm T (no symbols) Loaded symbol image file: nvlddmkm.sys Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys Image name: nvlddmkm.sys Timestamp: Sat Feb 09 23:13:08 2013 (5116D804) CheckSum: 00A90CB0 ImageSize: 00AA8000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
- Download Driver
- Start Type: Device Manager
- Expand Display Adapters
- Right-Click Driver Name, Uninstall
- Reboot
- Run Driver Sweeper
- Reboot
- Install Downloaded Driver
Driver Sweeper will scan for any left over files from the old driver, old driver files can cause conflicts with new driver installations. Create a System Restore point beforehand, in case any problems or issues arise.
Driver Sweeper:
Code:1: kd> !error c1 Error code: (Win32) 0xc1 (193) - %1 is not a valid Win32 application.
Downloading the lastest drivers now, will attempt both the repair install and the clean driver update. I'll post back as soon as I'm done
Thanks, post any updates :)
Just did the repair install. Going to download the video drivers now. Also, I'm currently running sfc to see if everything is in order
Last edited by avatarv2; 25 Feb 2013 at 11:31.
That's good to know, hopefully everything will be fine.