-
Security Expert- Emeritus
Hello intentional_22 ,
Please attempt fixing with Chkdsk first before trying ESET again. If you have already obtained the ESET scan result, please post them and continue the Chkdsk step anyway.
--------------------
Repair your hard disk with Chkdsk in elevated command prompt
- Go to Start, then type cmd in the search box.
- You will see a cmd listed in the search result. Right click on it and select Run as administrator.
- A command prompt window will appear. Please type chkdsk c: /f, then press Enter.
- You will be prompted to schedule the scan on the next reboot, type Y and press Enter.
- Close the command prompt, reboot your computer and Chkdsk will perform the repair tasks accordingly.
You may need to perform Chkdsk more than one time to solve all problems detected.
--------------------
Please perform a memtest and let me know the results.
Windows Memory Diagnostic Tool steps available here or here.
--------------------
Please post back:
1. how did the chkdsk fix go
2. ESET log
3. memory diagnostic result
-
ESET and CHKDSK
Ok, so the ESET scan completed with the log below (nothing found). I will continue CHKDSK.
ESETSmartInstaller@High as downloader log:
all ok
# version=8
# OnlineScannerApp.exe=1.0.0.1
# OnlineScanner.ocx=1.0.0.6844
# api_version=3.0.2
# EOSSerial=4a19a05f3905304ca0bb8681a5ce15ff
# end=finished
# remove_checked=false
# archives_checked=true
# unwanted_checked=true
# unsafe_checked=true
# antistealth_checked=true
# utc_time=2012-12-07 04:22:50
# local_time=2012-12-06 11:22:50 (-0500, Eastern Standard Time)
# country="United States"
# lang=1033
# osver=6.0.6002 NT Service Pack 2
# compatibility_mode=5892 16776574 100 100 3541963 191452876 0 0
# scanned=189372
# found=0
# cleaned=0
# scan_time=5927
ESETSmartInstaller@High as downloader log:
all ok
# version=8
# OnlineScannerApp.exe=1.0.0.1
# OnlineScanner.ocx=1.0.0.6844
# api_version=3.0.2
# EOSSerial=4a19a05f3905304ca0bb8681a5ce15ff
# end=finished
# remove_checked=false
# archives_checked=true
# unwanted_checked=true
# unsafe_checked=true
# antistealth_checked=true
# utc_time=2012-12-10 03:46:27
# local_time=2012-12-09 10:46:27 (-0500, Eastern Standard Time)
# country="United States"
# lang=1033
# osver=6.0.6002 NT Service Pack 2
# compatibility_mode=5892 16776574 100 100 3798980 191709893 0 0
# scanned=189224
# found=0
# cleaned=0
# scan_time=5921
-
Chkdsk
Ran CHKDSK several times and it apparently wont complete. See below.
The type of the file system is NTFS.
Volume label is OS.
WARNING! F parameter not specified.
Running CHKDSK in read-only mode.
CHKDSK is verifying files (stage 1 of 3)...
File verification completed.
1091 large file records processed.
0 bad file records processed.
0 EA records processed.
44 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
Index verification completed.
Errors found. CHKDSK cannot continue in read-only mode.
Invalid parameter - lfind
The type of the file system is NTFS.
Volume label is OS.
WARNING! F parameter not specified.
Running CHKDSK in read-only mode.
CHKDSK is verifying files (stage 1 of 3)...
File verification completed.
1092 large file records processed.
0 bad file records processed.
0 EA records processed.
44 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
Index verification completed.
Errors found. CHKDSK cannot continue in read-only mode.
The type of the file system is NTFS.
Volume label is OS.
WARNING! F parameter not specified.
Running CHKDSK in read-only mode.
CHKDSK is verifying files (stage 1 of 3)...
File verification completed.
1092 large file records processed.
0 bad file records processed.
0 EA records processed.
44 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
Index verification completed.
Errors found. CHKDSK cannot continue in read-only mode.
The type of the file system is NTFS.
Volume label is OS.
WARNING! F parameter not specified.
Running CHKDSK in read-only mode.
CHKDSK is verifying files (stage 1 of 3)...
File verification completed.
1092 large file records processed.
0 bad file records processed.
0 EA records processed.
44 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
Index verification completed.
Errors found. CHKDSK cannot continue in read-only mode.
-
Security Expert- Emeritus
Hello intentional_22 ,
You need to run Chkdsk as:
chkdsk c: /f
It appears the /f switch is missing.
-
chkdsk
Ok, so I have run the chkdsk with the f switch a couple of times, and it runs on a reboot. While it runs, I noticed it keeps mentioning 44 reparsed files (doesnt change after each subsequent reboot) and addresses a dll file but without a log I don't know what to post. Apologies for being dos command naive...but should I be inserting the /f switch into the original command you had directed me to use in order to get a .txt log file to post?
Also, the memory diagnostic tool links you provided sent me to pages where, once clicking on the link to the tool download...received 404 messages.
Assuming those links were old, and because I am on Vista, there is a Memory Diagnostic Tool in the Control Panel under Admin tools...or I can access by typing 'Memory' into the Start Menu Search box...I will wait on your direction before doing anything there...but I will continue to run chkdsk to hopefully fix any issues until I hear back and will stay up late to hopefully hear back from you and wrap this up. You have been more than patient and generous with your time and expertise!
-
ChkDsk info
Ok, so the message I kept receiving during stage 2 of 3 was that ChkDsk was deleting index entry slwga.dll in index $I30 in file 304555...then it says it recovered 1 lost file...orphaned file slwga.dll...then goes on to verify security descriptors and seems to complete ok. anything after that message appears too quickly for me to capture before going to the windows login screen.
I will run Memory diagnostic tool upon your cue.
note: I have Windows updates waiting to install but have not done so, so as to not muddle your help. Pls advise if I should do otherwise.
Again, thank you for all of your help!
-
Security Expert- Emeritus
Hello intentional_22 ,
You are most welcome.
You can use the following for the memory test:
How to use the Vista Windows Memory Diagnostics Tool.
Windows update will need to wait until we are done.
-
mem diagnostic test
Ran the memory diagnostic test, it ran and completed (the standard or normal version of the test).
PC is now struggling to start up and seems bogged down again...
-
Security Expert- Emeritus
Hello intentional_22 ,
So far, we are not seeing much from the scans or logs. It is in my opinion that very likely it could be either Windows experienced some sort of corruption or there is some hardware issue. I suggest that you create backups of your data if you haven't yet, then get help from someone who can sit directly in front of the computer.
Help through online forums are somewhat limited in that aspect and I am not seeing any malware so far.
-
Security Expert- Emeritus
As we reach a point where we could not proceed further and you need to seek help from alternative sources, this topic is now closed.
We are glad to be of help up to this point. If you are satisfied with our assistance and wish to donate to help with the costs of this volunteer site, please read :
Your donation helps in improving Spybot-S&D!
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules