Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Startup repair + corrupted software + chkdsk errors


  • Please log in to reply
7 replies to this topic

#1 PODxt

PODxt

  • Members
  • 41 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:30 PM

Posted 18 September 2013 - 10:46 AM

Hi, I'm having some troubles with my computer that prevent me from working (this is my music work station) so thanks in advance for your help.

 

First, here are my computer specs:

Motherboard/Laptop Model: Asus P8P67 standard
System BIOS/EFI/UEFI Version: American Megatrends v1401
CPU: Intel i7 2600K
CPU Speed: 3.8 GHz
CPU Heatsink: Noctua NH-D14
Amount of Installed Memory (GB): 4x G.Skill Ripjaws X 4 GB 1600MHz CL9 (=16GB)
Memory Voltage: 1.5v
Video Card(s): Gigabyte 4050 HD
PSU Model Number: Seasonic 600W 80+ Bronze
SSD Model: OCZ Vertex Turbo 60GB
HDD Model: Seagate 1TB + Seagate 3TB
OS: Windows 7 64bit
 
I installed my system in April 2011 and everything has run smoothly until 2 days ago.
 
The only system change I made was Sunday, when I installed QT Lite because Cubase needs QT to display videos. I didn't want to install the full QT so I installed QT Lite instead. This may not have anything to do with my problem but I guess everything is worth mentionning.

 

On monday morning I turned on the computer as usual but I saw a new green loading bar after the BIOS check. I thought I still wasn't awake but I then got an error message from Windows (Win7 64 Home ed) stating the computer couldn't boot properly because of errors and a startup repair needed to be executed. So be it, I waited for 3 minutes and once the diagnosis was complete, it said there were errors in the registry that got fixed in the process.

 

I remembered that I had a similar problem in 2011 and that was the cause of my system format/Windows reinstall and gear upgrade (went from a Q9650 to a 2600K, I also changed the motherboard, RAM, Heatsink and PSU). 

 

After the startup repair, Windows boots as usual, except for the NOD32 virus database that was 2 days old, as were the Windows Defender virus signature. I guess the startup repair rolled some data back. I do the updates and everything seems fine.

 

Yesterday morning, nothing happened. I worked with Cubase as usual but got errors from Cubase video engine complaining about QT each time I exited Cubase. Strangely the videos were working fine in Cubase after I installed QT Lite on Sunday so I don't understand why I'm having these messages. I decided to uninstall QT Lite but Windows said something went wrong in the uninstall process.

 

This morning I had a new startup repair. After the system boot, I saw that my FileZilla shortcut on my desktop was corrupted (see picture). I tried to click on it but I got this error message: "These files can't be opened. Your Internet security settings prevented one or more files from being opened." Now I browse to the FileZilla install folder and explorer starts hanging, it doesn't respond for 15 seconds (see picture) and then I can access the folder. Everything seems fine except the filezilla exe which has no icon (see pic).

 

Now I start a chkdsk on my system (SSD) to see if there are some errors. The process is VERY slow. I then get "file record segment ##### is unreadable." errors... lots of them. The process is so slow I always terminated chkdsk before it finishes its check up.

 

Not sure what to do now... what would you suggest?

Attached Files



BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 55,544 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:09:30 AM

Posted 18 September 2013 - 11:26 AM

Well...I would never terminate a chkdsk...unless I think that the hard drive itself is the problem.  Chkdsk /r doesn't actually repair the hard drive...it's a file system tool and tries to repair file or file system problems it detects.  Terminating it is self-defeating, IMO, since it may result in file corruption that did not have to occur.

 

If the system boots now...please run the chkdsk /r command to completion.

 

Louis



#3 chrisd87

chrisd87

  • Members
  • 811 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NC
  • Local time:09:30 AM

Posted 18 September 2013 - 11:32 AM

Just to add to what hamluis mentioned, I would also open an elevated command prompt and run a sfc /scannow to check for any corrupted windows installation files and attempt to repair any that's found.


"Like car accidents, most hardware problems are due to driver ɹoɹɹǝ."

 


#4 PODxt

PODxt
  • Topic Starter

  • Members
  • 41 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:30 PM

Posted 18 September 2013 - 12:21 PM

Hi guys, thanks for the feedback. I did what you suggested and ran a new chkdsk (cmd / chkdsk c: /r). I had to reboot the computer to perform the chkdsk. Now my computer seems to hang on reboot (black screen and strange pixel lines at the top). I leave the computer alone or stop the process and do a hard reset (push the PSU on/off knob)?

 

Attached File  18092013162_.jpg   10.28KB   3 downloads



#5 Netghost56

Netghost56

  • Members
  • 973 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Texas
  • Local time:09:30 AM

Posted 18 September 2013 - 12:26 PM

chkdsk normally takes hours, especially on 500+ GB drives. It will take longer if you DO have errors or corrupted sectors.

 

Based on your latest post, did you actually get to run chkdsk? The error checking app that runs after a reboot isn't actually the same as chkdsk.



#6 PODxt

PODxt
  • Topic Starter

  • Members
  • 41 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:30 PM

Posted 18 September 2013 - 02:26 PM

Well, I typed cmd / chkdsk c: /r and chksk told me the drive needed to be unmounted because it was used by the system and had to launch while rebooting.

 

It found and corrected many many errors. Is chkdsk repair enough or do you think my SSD is about to RIP?

Now I understand why I couldn't access FileZilla.

 

CHKDSK is verifying files (stage 1 of 5)...
Read failure with status 0xc0000185 at offset 0xc15e2000 for 0x1000 bytes.
File record segment 22408 is unreadable.
Read failure with status 0xc0000185 at offset 0xc15e2000 for 0x1000 bytes.
File record segment 22409 is unreadable.
Read failure with status 0xc0000185 at offset 0xc15e2000 for 0x1000 bytes.
File record segment 22410 is unreadable.
Read failure with status 0xc0000185 at offset 0xc15e2000 for 0x1000 bytes.
File record segment 22411 is unreadable.
Read failure with status 0xc0000185 at offset 0xc15e3000 for 0x1000 bytes.
File record segment 22412 is unreadable.
Read failure with status 0xc0000185 at offset 0xc15e3000 for 0x1000 bytes.
File record segment 22413 is unreadable.
Read failure with status 0xc0000185 at offset 0xc15e3000 for 0x1000 bytes.
File record segment 22414 is unreadable.
Read failure with status 0xc0000185 at offset 0xc15e3000 for 0x1000 bytes.
File record segment 22415 is unreadable.
222720 file records processed. 
File verification completed.
1050 large file records processed. 
Read failure with status 0xc0000185 at offset 0xc15e2000 for 0x400 bytes.
Read failure with status 0xc0000185 at offset 0xc15e2c00 for 0x400 bytes.
Read failure with status 0xc0000185 at offset 0xc15e3000 for 0x400 bytes.
 
CHKDSK is verifying indexes (stage 2 of 5)...
The object id index entry in file 0x19 points to file 0x578c 
but the file has no object id in it.
Deleting an index entry from index $O of file 25.
 
Index entry Microsoft-Windows-Branding-Ultimate-Client-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum of index $I30 in file 0x978 points 
 
to unused file 0x578b.
Deleting index entry Microsoft-Windows-Branding-Ultimate-Client-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum in index $I30 of file 2424.
Index entry MIFF20~1.MUM of index $I30 in file 0x978 points to unused file 0x578b.
Deleting index entry MIFF20~1.MUM in index $I30 of file 2424.
Index entry b01b4355c9e3e1b081dccac4f4353c8dcf0bb1e6b58af4ff6b7fb372cbf2674b.cat of index $I30 in file 0x2722 points to unused file 0x5788.
Deleting index entry b01b4355c9e3e1b081dccac4f4353c8dcf0bb1e6b58af4ff6b7fb372cbf2674b.cat in index $I30 of file 10018.
Index entry B01B43~1.CAT of index $I30 in file 0x2722 points to unused file 0x5788.
Deleting index entry B01B43~1.CAT in index $I30 of file 10018.
Index entry filezilla.exe of index $I30 in file 0x113e6 points to unused file 0x578c.
Deleting index entry filezilla.exe in index $I30 of file 70630.
Index entry FILEZI~1.EXE of index $I30 in file 0x113e6 points to unused file 0x578c.
Deleting index entry FILEZI~1.EXE in index $I30 of file 70630.
Read failure with status 0xc0000185 at offset 0x9150b4000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x9150a8000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x9150b4000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x9150b5000 for 0x3000 bytes.
Read failure with status 0xc0000185 at offset 0x9150b5000 for 0x1000 bytes.
42 41 41 44 28 00 09 00 09 01 58 95 11 00 00 00  BAAD(.....X.....
7b 00 00 00 00 00 00 00 28 00 00 00 e0 03 00 00  {.......(.......
 
yada yada yada
 
e5 97 02 00 00 00 8d 03 70 00 52 00 01 00 00 00  ........p.R.....
f1 ee 01 00 00 00 f5 00 4e e9 31 2d 50 ab ce 01  ........N.1-P...
5f 10 32 2d 50 ab ce 01 5f 10 32 2d 50 ab ce 01  _.2-P..._.2-P...
4e e9 31 2d 50 ab ce 01 00 a0 02 00 00 00 00 00  N.1-P...........
0b 92 02 00 00 00 00 00 20 20 00 00 00 00 00 00  ........  ......
08 03 66 00 5f 00 30 00 36 00 38 00 30 00 38 00  ..f._.0.6.8.0.8.
36 00 00 00 00 00 00 00 ff ff ff ff ff ff ff ff  6...............
c3 36 01 00 00 00 b3 01 70 00 52 00 01 00 00 00  .6......p.R.....
 
yada yada yada
 
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.
Adding 17 bad clusters to the Bad Clusters File.
Correcting errors in the master file table's (MFT) DATA attribute.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.
 
62417919 KB total disk space.
47299308 KB in 176859 files.
104252 KB in 41503 indexes.
68 KB in bad sectors.
326915 KB in use by the system.
65536 KB occupied by the log file.
3671844 KB available on disk.
 
4096 bytes in each allocation unit.
15604479 total allocation units on disk.
5737161 allocation units available on disk.
 
Data:
00 66 03 00 ff 54 03 00 85 00 06 00 00 00 00 00  .f...T..........
83 05 00 00 41 00 00 00 00 00 00 00 00 00 00 00  ....A...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

 



#7 Netghost56

Netghost56

  • Members
  • 973 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Texas
  • Local time:09:30 AM

Posted 18 September 2013 - 02:40 PM

And this was before the bad reboot, correct?

 

I was told (I'm an IT tech) that it's best to run chkdsk 3 times before making any final judgements. You could also try the /b switch, which will force it to reevaluate sectors that it marked "bad" in a previous run.

 

If you're not able to get back into the desktop at this point I would say that the corrupted sectors on your drive were located where your OS and drivers were- which is a pickle.

 

DEFINITELY DEFINITELY pull the drive and stick it in another system and do a back up of your personal data ASAP (if you haven't already done so)



#8 PODxt

PODxt
  • Topic Starter

  • Members
  • 41 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:30 PM

Posted 18 September 2013 - 03:02 PM

Thanks for your input, I'll look into that!






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users