Chkdsk Error (766f6c756d652e63 3f1)


  1. Posts : 16
    Microsoft Windows 7 Ultimate x64 / 6.1.7601 Service Pack 1 Build 7601
       #1

    Chkdsk Error (766f6c756d652e63 3f1)


    Hi folks, hoping someone can help me with the proverbial, Windows 7, "chkdsk" error (766f6c756d652e63 3f1).

    After an exhaustive Google search, I see that many folks suffer from this, but in all the forums researched, no one has really come up with a definitive answer.

    I mean, there are a ton of usual posts where someone boasts out in glee, that, hey, this worked for me, and then you try it, and it doesn’t work. The usual.

    So, the whole story is this:

    Any time I setup my C: drive, to do a full disk check, which requires the usual reboot, the reboot comes back up, and I get the same message on the screen, (see attached photo).

    And even though, the majority of all forums discussing this error agree that, it actually does not have anything to do with installed software, I have tried every single listed fix, in every forum that I have researched, to no avail.

    For instance, I have:

    Within Windows 7, went into “Disk Management”, and saw that the “System Reserve” section of my C: drive was not assigned a drive letter. A lot of the fixes state to assign a drive letter to the “System Reserve”, and then try again. And many pulled the, “It worked for me”, but that didn’t work for me.

    Next another fix that didn’t work for me, I hit F8 to get to the Safe Mode menu, and from there, you’re supposed to choose the option, “Repair Your Computer”, usually the very first option at the top of the list. When I choose that option, Windows just continues to boot into a normal Windows session. (??) Don’t think that’s supposed to happen.

    Next, I have even connected a separate, clean, “bootable” hard drive, with Windows 7 installed, to my system, booted from this “new” hard drive, and tried checking my C: drive, from the new bootable hard drive. Now of course my original, problematic, C: drive on this new hard drive is now designated as E:. So, from this “new” hard drive, within Windows Explorer, I right click on E: choose Properties, and then the Tools Tab, and under Error Checking, I choose, “Check Now”, and make sure both check marks are ticked, and hit Start. It actually starts to check my C: drive, and as all of us know, this process, depending on the size of your hard drive, takes quite a while to complete. So, I walk away, …go to bed really. Get up in the morning expecting a report on errors found, and here, the computer has rebooted itself, somewhere in the night. Thats not good either, I should have still been in the OS of the "new" hard drive.

    Other than not being able to do a full chkdsk on my C: drive, the system works perfectly. No BSOD, nothing.

    So, again, I have tried everything that others say worked for them, to no avail. What’s left?

    Thanks
    Attached Thumbnails Attached Thumbnails Chkdsk Error (766f6c756d652e63 3f1)-error.png  
      My Computer


  2. Posts : 6,458
    x64 (6.3.9600) Win8.1 Pro & soon dual boot x64 (6.1.7601) Win7_SP1 HomePrem
       #2

    If you have a repair disc, if not create one, and boot with that.
    Select Command prompt option
    use diskpart command to determine which drive letter is assigned to your original "C:\" drive.
    diskpart
    lis dis
    sel dis 0
    lis vol
    exit
    exit

    chkdsk /r c:
    amend: diskpart might identify the drive letter as something other than C: - chkdsk the disk that really is the system disk.
    reboot using HDD
    open an elevated command prompt
    Might help

    Bill
    Last edited by Slartybart; 29 Sep 2013 at 15:52. Reason: might not be C:
      My Computer


  3. Posts : 16
    Microsoft Windows 7 Ultimate x64 / 6.1.7601 Service Pack 1 Build 7601
    Thread Starter
       #3

    Out of all fairness to the good people of the forum, I have discovered the reason for my Chkdsk not working.

    The problem deals with Kaspersky Anti Virus, and I kind of thought, that, that was just about the time I had not been able to setup a Chkdsk.

    A couple good Google searches, and enough people experiencing the same problem as me, revealed the truth of this issue.

    As an example:

    Kaspersky AV Breaking CHKDSK? - Security forum regulars lament 'iSwift' technology | DSLReports, ISP Information

    Apparently, from what I am reading, even after uninstalling Kaspersky, the problem remains. Great.
      My Computer


 

  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 00:58.
Find Us