The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    6860 Corrupt file problem

    Discussion in 'Gateway and eMachines' started by LeeGro, Jun 22, 2008.

  1. LeeGro

    LeeGro Notebook Geek

    Reputations:
    1
    Messages:
    85
    Likes Received:
    0
    Trophy Points:
    15
    I get balloon notifications saying that I have a corrupt file. It is always and exe. file. Also it refers to its location as logitech setpoint or something like that. I think it is the program that is used for my logitech mouse. THe mx 518. The problem is that it tells me to run chkdsk and when I try to run it says it cannot do it now and will do it on the next startup. But it never happens... What is going on?
     
  2. id10t error dfw

    id10t error dfw Notebook Consultant

    Reputations:
    28
    Messages:
    130
    Likes Received:
    0
    Trophy Points:
    30
    Uninstall the Logitech software, then go to logitech.com and download the latest version and install it. The mouse will also work just fine without their software installed.
     
  3. LeeGro

    LeeGro Notebook Geek

    Reputations:
    1
    Messages:
    85
    Likes Received:
    0
    Trophy Points:
    15
    i did an unistall through add remove programs but that didnt work. I got the balloon again. So now i got the error code:0x80070091: the directory is not empty... so it will not delete it or something
     
  4. Rasu

    Rasu Notebook Enthusiast

    Reputations:
    0
    Messages:
    24
    Likes Received:
    0
    Trophy Points:
    5
    LeeGro:

    Restart your computer and tap F8 as it boots (when it gets to the BIOS screen) when you get to the startup menu select safe mode. In safe mode open the command prompt and run the command chkdsk /f. It should fix the problem.
     
  5. LeeGro

    LeeGro Notebook Geek

    Reputations:
    1
    Messages:
    85
    Likes Received:
    0
    Trophy Points:
    15
    Rasu:

    When I do what u say it still says it is going to schedule it for the next startup. Should i choose safe mode with command prompt because i chose just the normal safe mode.. And I also just ran chkdsk in safe mode and it got to 9 percent and got an error or something and stopped.
     
  6. Tom1222

    Tom1222 Notebook Consultant

    Reputations:
    0
    Messages:
    103
    Likes Received:
    0
    Trophy Points:
    30
    LeeGro,
    Give this program a try: http://www.tune-up.com/products/tuneup-utilities/
    I have been using it for many years now (Since 2005) and it has really solved a little issued and made it easy for tweaking Windows and such. You don't have to buy it. They have a 30 free trial which gives you enough time to clear up some things and tweak your system. After just uninstall it if you don't like it and be done with it.

    I don't really go for those kind of programs but I tried it once when Norton Systemworks just got to much of a memory hog and liked it ever since.
     
  7. Rasu

    Rasu Notebook Enthusiast

    Reputations:
    0
    Messages:
    24
    Likes Received:
    0
    Trophy Points:
    5
    LeeGro:

    If Tom's program does not work, I have something else for you to try out. Go to start => Programs => Accessories => Right Click Command Prompt and select Run as Administrator. If it asks, enter the password. From there type this:

    sfc /scannow

    If it says it cannot repair a file please do this (in a Run as Administrator Command Prompt):

    findstr /C:"[SR] Cannot repair member file" %windir%\logs\cbs\cbs.log >sfcdetails.txt

    Then type in edit sfcdetails.txt, it'll bring up that file in a notepad, please copy and paste what it says.
     
  8. spaceoddity

    spaceoddity Notebook Enthusiast

    Reputations:
    5
    Messages:
    17
    Likes Received:
    0
    Trophy Points:
    5
    I had this same exact problem! Weird. I wonder what the cause is? Do you have a RAID 0 setup?

    Anyway, here's how I fixed mine:
    I booted from the Gateway Windows Vista DVD that came with my Laptop and when a menu came up I think I picked something like Repair Installation, which thru some series of choices I was able to get to a command prompt. (Sorry about the imprecise nature of my steps, I'm at work and don't have access to my stuff! If you need more specific instructions pm me and I can get them to you later).
    Anyway, when I got to that command prompt I think I did "chkdsk /f /v /r"
    I can't remember exactly what the modifiers are, except /r tries to repair bad sectors. It will eventually give you a choice whether or not to unmount the partition, and you want to say yes, then it should preform the checkdisk. When its all done you should be able to boot up and reinstall setpoint, I'd suggest deleting the Logitech folder in Program Files first tho.

    This worked for me, however I recently did another checkdisk and it found more bad sectors, I really wish I knew what was causing it so if I replaced the drives I could prevent it! I'm starting to think the chipset's RAID controller is just a POS, but if you aren't in RAID that would throw a wrench into that theory...
     
  9. LeeGro

    LeeGro Notebook Geek

    Reputations:
    1
    Messages:
    85
    Likes Received:
    0
    Trophy Points:
    15
    im not using raid
     
  10. LeeGro

    LeeGro Notebook Geek

    Reputations:
    1
    Messages:
    85
    Likes Received:
    0
    Trophy Points:
    15
    2008-06-22 22:16:39, Info CSI 00000023 [SR] Cannot repair member file [l:22{11}]"autochk.exe" of Microsoft-Windows-Autochk, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2008-06-22 22:16:44, Info CSI 00000026 [SR] Cannot repair member file [l:22{11}]"autochk.exe" of Microsoft-Windows-Autochk, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2008-06-22 22:20:28, Info CSI 00000119 [SR] Cannot repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2008-06-22 22:20:30, Info CSI 0000011b [SR] Cannot repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2008-06-22 22:26:52, Info CSI 0000027f [SR] Cannot repair member file [l:22{11}]"autochk.exe" of Microsoft-Windows-Autochk, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2008-06-22 22:26:53, Info CSI 00000281 [SR] Cannot repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2008-06-22 22:26:54, Info CSI 00000285 [SR] Cannot repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2008-06-22 22:26:54, Info CSI 0000028b [SR] Cannot repair member file [l:22{11}]"autochk.exe" of Microsoft-Windows-Autochk, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2008-06-22 22:26:55, Info CSI 00000299 [SR] Cannot repair member file [l:22{11}]"autochk.exe" of Microsoft-Windows-Autochk, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2008-06-22 22:26:55, Info CSI 0000029b [SR] Cannot repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2008-06-22 22:26:56, Info CSI 0000029f [SR] Cannot repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2008-06-22 22:26:57, Info CSI 000002a5 [SR] Cannot repair member file [l:22{11}]"autochk.exe" of Microsoft-Windows-Autochk, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2008-06-23 20:48:17, Info CSI 00000023 [SR] Cannot repair member file [l:22{11}]"autochk.exe" of Microsoft-Windows-Autochk, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2008-06-23 20:48:22, Info CSI 00000026 [SR] Cannot repair member file [l:22{11}]"autochk.exe" of Microsoft-Windows-Autochk, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2008-06-23 20:52:24, Info CSI 00000117 [SR] Cannot repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2008-06-23 20:52:27, Info CSI 00000119 [SR] Cannot repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2008-06-23 20:58:41, Info CSI 0000027c [SR] Cannot repair member file [l:22{11}]"autochk.exe" of Microsoft-Windows-Autochk, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2008-06-23 20:58:41, Info CSI 0000027e [SR] Cannot repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2008-06-23 20:58:41, Info CSI 00000280 [SR] Cannot repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2008-06-23 20:58:42, Info CSI 00000285 [SR] Cannot repair member file [l:22{11}]"autochk.exe" of Microsoft-Windows-Autochk, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
     
  11. Rasu

    Rasu Notebook Enthusiast

    Reputations:
    0
    Messages:
    24
    Likes Received:
    0
    Trophy Points:
    5
    LeeGro:

    That'd definitely explain why Check Disk doesn't run at startup. That output says that autochk.exe is corrupted. Auto Check is what runs Check Disk before your computer boots.

    Anyhow, you can try a few things now. You need to boot Vista DVD, you'll get to a language screen, select your language. From there select "Repair Your Computer" you'll get a few more options, select "Command Prompt". From here you can try Space's suggestion of chkdsk /f /r (/v isn't needed, /r really isn't needed either, but won't hurt). That should fix the directory problem.

    Another thing you can do is use the command prompt to replace the autochk.exe program, but try Space's suggestion first and see if that fixes it. If it doesn't, we can try to replace the autochk.exe.

    Also, do you have a virus scanner? This goes for Space too, corrupted files like that could indicate a virus, so do a scan if you have one, if not try Trend Micro's Housecall
     
  12. LeeGro

    LeeGro Notebook Geek

    Reputations:
    1
    Messages:
    85
    Likes Received:
    0
    Trophy Points:
    15
    yea i have avira for virus, comodo firewall and spybot for spyware. And I will try that. Thanks so much for the help guys! Rasu are u in computing or something?
     
  13. Rasu

    Rasu Notebook Enthusiast

    Reputations:
    0
    Messages:
    24
    Likes Received:
    0
    Trophy Points:
    5
    LeeGro: Yeah :p My major is Information Technology and I have several certifications. Though most of my certs are for XP/Server 2003, so I have to look some stuff up about Vista since I've only recently started to use it, but I'm learning!
     
  14. LeeGro

    LeeGro Notebook Geek

    Reputations:
    1
    Messages:
    85
    Likes Received:
    0
    Trophy Points:
    15
    Rasu:
    Well I did the boot from vista disc and followed your instructions and this is what it said:
    The type of file system is NTFS.
    Cannot lock current drive.
    Windows cannot run disk checking on this volume b/c it is write protected.
    uhhhhhh...
     
  15. Johnksss

    Johnksss .

    Reputations:
    11,536
    Messages:
    19,465
    Likes Received:
    12,863
    Trophy Points:
    931
    chkdsk c: /f /r

    it was trying to check your dvd.
     
  16. Rasu

    Rasu Notebook Enthusiast

    Reputations:
    0
    Messages:
    24
    Likes Received:
    0
    Trophy Points:
    5
    Ah, thanks John! Forgot to put c: in my instructions.
     
  17. Johnksss

    Johnksss .

    Reputations:
    11,536
    Messages:
    19,465
    Likes Received:
    12,863
    Trophy Points:
    931
    no problem!
     
  18. LeeGro

    LeeGro Notebook Geek

    Reputations:
    1
    Messages:
    85
    Likes Received:
    0
    Trophy Points:
    15
    haha thanks guys that makes sense now