Check Disk Unexpected Error
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn chkdsk an unspecified error occurred (766f6c756d652e63 461) more about hiring developers or posting ads with us Super User Questions Tags Users Badges Unanswered
Chkdsk An Unspecified Error Occurred (766f6c756d652e63 3f1)
Ask Question _ Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a chkdsk an unspecified error occurred 696 minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top CHKDSK error code 766f6c756d652e63 3f1 up vote 5 down vote favorite 1
Chkdsk Unspecified Error Occurred
On a Windows 7 computer, running chkdsk /r /f C: in repair mode, it gives the error, Unspecified error 766f6c756d652e63 3f1. or something like that. I have tried the following: uninstalling all antivirus software scanning with MalwareByte's Anti-Malware doing a Disk Cleanup running Disk Defrag booting TRK and running fsck -t ntfs (gives error Unsupported case. and not implemented). I have also tried a System Restore, but there is a Temporary Internet file that appears to be in chkdsk unspecified error 461 all restore points, and that file must be corrupted or something, because System Restore always grinds to a halt when it gets to that file. What should I try next? Thanks in advance. windows chkdsk share|improve this question asked Dec 8 '12 at 1:54 BenjiWiebe 4,68872551 4 Check your HDD for errors using its manufacturer's utility. If your HDD has bad sectors (since you ran chkdsk /r), best to copy as much data off it as possible and replace the disk. Moreover, if it has bad sectors, stressing it further with defrag before getting your data off it is a really bad idea. –Karan Dec 8 '12 at 2:02 1 @Karan The problem has existed for a long time, and no files seem to be missing. Do you think that this error indicates a hardware failure? –BenjiWiebe Dec 8 '12 at 2:04 1 chkdsk /r /f C: in repair mode, it gives the error, Unspecified error 766f6c756d652e63 3f1. … booting TRK and running fsck -t ntfs (gives error Unsupported case. and not implemented). Hmm, it sounds like your file-system is damaged/corrupted. What you can try is to use a partition-management program to check the volume and possible repair it. Otherwise, you may want to copy your data (hopefully you won’t need to resort to a data-recovery program) and wipe it. –Synetech Dec 8 '12 at 2:04 1 @
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us
6e74667363686b2e
Learn more about Stack Overflow the company Business Learn more about hiring developers
An Unspecified Error Occurred. Your Request Cannot Be Processed At This Time
or posting ads with us Super User Questions Tags Users Badges Unanswered Ask Question _ Super User is a question and 75736e6a726e6c2e 4f6 answer site for computer enthusiasts and power users. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are http://superuser.com/questions/516527/chkdsk-error-code-766f6c756d652e63-3f1 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 sure what the error message means? Chkdsk was executed in read/write mode. Checking file system http://superuser.com/questions/871110/chkdsk-an-unspecified-error-occurred-6c6f6766696c652e-29c 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 status 0xc000009d at offset 0xb62f1000 for 0x1000 bytes. An unspecified error occurred (6c6f6766696c652e 29c). windows-7 hard-drive chkdsk share|improve this question edited Jan 30 '15 at 1:04 asked Jan 29 '15 at 13:
Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks. Windows 7 Help Forums Windows 7 help and http://www.sevenforums.com/performance-maintenance/225944-chkdsk-unspecified-error-occurred-6672732e637878.html support Performance & Maintenance » User Name Remember Me? Password Advanced Search Show Threads https://raywoodcockslatest.wordpress.com/2012/12/02/unspecified-error-hkdsk/ Show Posts Advanced Search Go to Page... Windows 7: chkdsk - "An unspecified error occurred <6672732e637878>" 22 Apr 2012 #1 bluedino Windows 7 Home Premium SP1-U 64bit 16 posts chkdsk - "An unspecified error occurred <6672732e637878>" I started a chkdsk on a Win7 64bit computer that got stuck at startup repair. Before that though, I was looking around, unspecified error the damage seems to be the windows files got messed up after an update. My computer data was intact when I looked around booted through a recovery cd and I checked again via a ubuntu live cd. My question is that the chkdsk d: /f apparently stopped in the middle and gave the following message: An unspecified error occurred <6672732e637878> Failed to transfer logged messages to the event log with status 50 What does that mean? Is unspecified error occurred it terrible? I just restarted the chkdsk anyway and as of now, it is finding less unreadable segments, but is there a risk of data loss? My System Specs OS Windows 7 Home Premium SP1-U 64bit CPU Intel Core i7 860(2.8GHz) Motherboard Intel H55 Memory 4GB (2GB x 2) DDR3 1600 Graphics Card NVIDIA GeForce GTS250 1GB Sound Card Sound card - Integrated Keyboard usb Mouse usb Other Info http://www.newegg.com/Product/Product.aspx?Item=83-227-243&SortField=0&SummaryType=0&Pagesize=10&PurchaseMark=&SelectedRating=-1&VideoOnlyMark=False&VendorMark=&IsFeedbackTab=true&Page=1#scrollFullInfo bluedino View Public Profile Find More Posts by bluedino . 22 Apr 2012 #2 bluedino Windows 7 Home Premium SP1-U 64bit 16 posts Also before this, I attempted to sfc /scannow /offbootdir=c:\ /offwindir=d:\windows and sfc /scannow when the first command didn't work. I also tried following the instructions here (Startup Repair Infinite Loop Recovery) but the numbers were off in SAM and one other one, Default I think. If the chkdsk doesn't work, would the only option be a clean sweep? and is there a way that I can get a list of programs that I have saved on my computer (like how I could retrieve documents from Copy & Paste - in Windows Recovery Console Edit: Looking some more in the forums, my list of actions most closely resemble the advice of this thread SFC error - Windows Resource Protection could not perform... My System Specs OS Windows 7 Home Premium SP1-U
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 USB jump drive. Upon booting, I chose the Windows 7 Recovery Disk and ran CHKDSK from the Command Prompt. I made many attempts to check and fix that external hard drive, using CHKDSK /R and CHKDSK /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 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 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