SFC /SCANNOW Command - System File Checker

Page 50 of 99 FirstFirst ... 40484950515260 ... LastLast

  1. Posts : 9
    Windows 8 64-bit
       #490

    So I've made an interesting discovery.

    My keyboard is completely unresponsive in the Startup Options screen. I tried plugging it in different USB ports but to no avail. But it works fine otherwise.

    This could be related to the previous BSOD errors I was having related to Hidclass.sys after running Driver Verifier, which - I think - means I'm having issues with USB drivers. But I have no idea how I would go about resolving that problem, as those seem strangely difficult to update/fix.

    I know this is not on-topic with the thread, but do you have any recommendations for me?
    Last edited by Clovis5119; 14 Aug 2013 at 22:17.
      My Computer


  2. Posts : 70,196
    64-bit Windows 10 Pro
    Thread Starter
       #491

    Do you have an old PS/2 keyboard that you could use temporarily to see if you are able to run a SFC scan at boot with?

    If not, then you could try doing a system restore (at boot if needed) using a restore point (if available) dated before this issue to see if it may help before having to move on to more drastic measures.
      My Computer


  3. Posts : 47
    Windows 7 Ultimate 64-bit
       #492

    SFC /SCANNOW Command


    This is an awesome thread! Man! Brink, I wanna be just like you when I grow up!!!
      My Computer


  4. Posts : 9
    Windows 8 64-bit
       #493

    Brink said:
    Do you have an old PS/2 keyboard that you could use temporarily to see if you are able to run a SFC scan at boot with?

    If not, then you could try doing a system restore (at boot if needed) using a restore point (if available) dated before this issue to see if it may help before having to move on to more drastic measures.
    Hi Brink,

    I was able to launch the command prompt at boot but the SFC scan still returned the same error.

    I doubt a system restore will be of much use. I had been having regular BSOD issues (at a rate of about 1 per 2 days) since I built this PC. After figuring out how to read my minidump files, I found that almost all were being caused by my Network driver, which I have since updated, causing a drastic reduction in the rate of crashes.

    The BSODs since always return one of the the following errors and usually occur during boot or very shortly after boot: PFN_LIST_CORRUPT, MEMORY_MANAGEMENT, DRIVER_IRQ_NOT_LESS_OR_EQUAL. I ran Memtest and the Windows Memory Diagnostic Tool but both came out clean. I also made sure that my RAM was receiving the proper voltage and that all of my drivers were up to date.

    Yesterday I tried to run Driver Verifier but it caused the PC to crash upon each boot attempt until the OS automatically forced a system restore to two days prior. I found that the crashes were being caused by a Daemon Tools driver and removed the application.

    I then tried to run Driver Verifier again. This time the computer could boot to the Desktop but would then crash within 5 seconds of doing so, reporting an DRIVER_VERIFIER_IOMANAGER_VIOLATION (Hidclass.sys) error.

    And that's basically where I am right now.
      My Computer


  5. Posts : 70,196
    64-bit Windows 10 Pro
    Thread Starter
       #494

    Clovis,

    You might consider doing a clean install to start fresh.

    Otherwise, you might post in the BSOD Help and Support forum area to see if we may be able to help with that issue.
      My Computer


  6. Posts : 9
    Windows 8 64-bit
       #495

    Hi Brink,

    I was able to run the System File Checker.

    Once the process was completed, SFC reported there were some files it could not repair.

    I followed the directions in Option Three to find the files the system could not repair, but sfcdetails.txt turned out empty. I've attached a copy of CBS.log to this post.

    Thoughts?
      My Computer


  7. Posts : 70,196
    64-bit Windows 10 Pro
    Thread Starter
       #496

    Hello Clovis,

    Did you run SFC at boot, in Safe Mode, or in Windows 7? If not in Windows 7, then you may not get a log file.

    If you are still getting BSODs, then I would recommend to post a new thread BSOD Help and Support forum area to get that sorted first.

    Blue Screen of Death (BSOD) Posting Instructions
      My Computer


  8. Posts : 9
    Windows 8 64-bit
       #497

    Brink said:
    Hello Clovis,

    Did you run SFC at boot, in Safe Mode, or in Windows 7? If not in Windows 7, then you may not get a log file.

    If you are still getting BSODs, then I would recommend to post a new thread BSOD Help and Support forum area to get that sorted first.

    Blue Screen of Death (BSOD) Posting Instructions
    Ran it in Safe Mode.
      My Computer


  9. Posts : 70,196
    64-bit Windows 10 Pro
    Thread Starter
       #498

    Ah, that's why there's no log then.
      My Computer


  10. Posts : 56
    Windows 7 Home Premium 64bit
       #499

    Did a sfc /scannow . I got the file using copy cbs.log a.txt
    Question: How can I read it. What tells me what was replaced.
    or what was not replaced?

    It said, it was successful
    Joe
    Last edited by Joeaa; 25 Aug 2013 at 19:57.
      My Computer


 
Page 50 of 99 FirstFirst ... 40484950515260 ... LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 22:39.
Find Us