An Unspecified Error Occurred During Chkdsk
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Fri, 30 Sep 2016 04:52:57 GMT by s_hv997 (squid/3.5.20)
Posted on December 2, 2012 by Ray Woodcock I wanted to test a hard drive. I put it into an external USB enclosure and connected it to an ASUS Eee PC. I booted the Eee using a multiboot
An Unspecified Error Occurred During System Restore 0x81000204
USB jump drive. Upon booting, I chose the Windows 7 Recovery Disk and ran an unspecified error occurred during system restore 0x800700b7 CHKDSK from the Command Prompt. I made many attempts to check and fix that external hard drive, using CHKDSK /R and CHKDSK an unspecified error occurred during system restore windows 8 /B. They all failed. Attempts using /I (e.g., CHKDSK /B /I) did not fail, but of course those produced a warning that /I would not necessarily repair disk problems. When the attempts failed, they failed in stage http://answers.microsoft.com/en-us/windows/forum/windows_7-performance/check-disk-unspecified-error-occurred/705a4f06-6843-4300-9d02-5c4f8fd16483 2 of 5, and most if not all produced this error message: An unspecified error occurred (696e647863686b2e e19). I hoped that, by running CHKDSK many times, perhaps the program would slowly eat its way through whatever corruption it might be encountering. At first it appeared that this might be taking place. But at some point I became convinced that we were not getting past the 25% mark, and in some cases the number https://raywoodcockslatest.wordpress.com/2012/12/02/unspecified-error-hkdsk/ of index entries processed was actually less than had been processed on the previous try. I ran a search on the "unspecified error" message. This produced a plethora of plausible possibilities. It tentatively appeared that there might be different causes of the unspecified error. Mine, for instance, might have been caused by something that would only produce the "e19" at the right end of the error message shown above. Some of the solutions suggested in those webpages, or coming to mind as I read, were that trying with a different machine might solve the problem; perhaps the (Samsung) hard drive manufacturer's diagnostic CD would help; maybe I could accomplish something with other DOS-like commands (e.g., FIXMBR); maybe some other program (e.g., TestDisk) would do a better job than CHKDSK; possibly I could boot into Windows 7 and use its disk checking feature to fix the problem (i.e., in Windows Explorer, right-click on the drive > Properties > Tools > Check Now > check both boxes); conceivably an Eee driver update would help. I dismissed the possibility that the Eee's copy of CHKDSK was bad; I had just used it successfully in that same configuration with a different external USB drive in a different USB enclosure (actually, a mere drive dock); I did wonder, though, whether the probl
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies http://superuser.com/questions/871110/chkdsk-an-unspecified-error-occurred-6c6f6766696c652e-29c of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Super User Questions Tags Users Badges Unanswered Ask http://www.windowsfilerecovery.com/chkdsk/unspecified-error-766f6c756d652e633f1.html Question _ Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute: Sign up Here's how it works: Anybody can unspecified error ask a question Anybody can answer The best answers are voted up and rise to the top Chkdsk An unspecified error occurred 6c6f6766696c652e 29c up vote 1 down vote favorite UPDATE: It was a bad SATA cable. I ran the chkdsk /R command on an external WD 1TB hardrive connected via SATA. Here is the output log from chkdsk from event viewer. Not an unspecified error sure what the error message means? Chkdsk was executed in read/write mode. Checking file system on E: The type of the file system is NTFS. Volume label is Backup Drive. CHKDSK is verifying files (stage 1 of 5)... 768 file records processed. File verification completed. 0 large file records processed. 0 bad file records processed. 0 EA records processed. 0 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)... 884 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)... 768 file SDs/SIDs processed. Cleaning up 6 unused index entries from index $SII of file 0x9. Cleaning up 6 unused index entries from index $SDH of file 0x9. Cleaning up 6 unused security descriptors. Security descriptor verification completed. 58 data files processed. CHKDSK is verifying file data (stage 4 of 5)... 752 files processed. File data verification completed. CHKDSK is verifying free space (stage 5 of 5)... 196108954 free clusters processed. Free space verification is complete. Read failure with status 0xc000009d at offset 0xb62f1000 for 0x10000 bytes. Read failure with statu
(766f6c756d652e63 3f1)". This article explains when this error message is encountered, what can be the reasons & possible solutions for the issue. When this error 766f6c756d652e63 3f1 occur? This unspecified error 766f6c756d652e63 3f1 is mostly encountered during the execution of "chkdsk /r /f C:" command. Besides, you can see the same error while rebooting or booting the system. Causes of CHKDSK 766f6c756d652e63 3f1 Error Some of the reasons are listed below for an unspecified error code 766f6c756d652e63 3f1 while running Check Disk: Some system files or CHKDSK-related files got damaged by any malicious program. Indication of Hard Disk failure. Recently made changes to a system like a newly installed software, which may not be compatible with the OS. Deletion of Windows CHKDSK related files accidentally. Installation of a program during CHKDSK is running. Corruption in Windows registry file. How to resolve an unspecified error occurred in Windows There are some solutions that can fix error code 766f6c756d652e63 3f1 in Windows 7, 8, XP, Vista when running CHKDSK: Run Windows Check Disk- Start a command prompt & execute the following CHKDSK command to repair the issues related to a file system structure or a hard disk. chkdsk d: /f Run System File Checker- Start a command prompt & execute the following System file checker command to scan system files & replace damaged files with a cached copy. Sfc / scannow Go for System Restore option that will undo all the changes you made recently that causes the unspecified error. It will help you in reverting to a previous healthy state. Is your system still in an unhealthy state: What now? After going through all the above steps, if you still find an unspecified error 766f6c756d652e63 3f1 on startup that means your computer is in an unhealthy state & your computer files are either highly corrupted, damaged or lost. Moreover, they