Jump to content

Welcome to Geeks to Go - Register now for FREE

Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!

How it Works Create Account
Photo

Solve PC Issues and Disk Scan


  • Please log in to reply

#1
woodhj_uk

woodhj_uk

    New Member

  • Member
  • Pip
  • 7 posts

Hiya,

 

I am helping my friend fix his computer as it was originally refusing to boot and had the error message that the boot configuration data for the PC was missing....etc. It runs windows 8.1 on an intel spec with Nvidia graphics. 

 

I have managed to fix that and also resolved a number of driver issues, fixed windows update (it refused to download anything) and resolved the fact that it also would not shut down (it would just sit on the shutdown screen for ages).

 

One thing that I cannot solve though is I keep getting a solve pc issues message that says "restart to repair drive errors (important)" When I do this it then scans the E drive, gets to 72% and then just carries on to load windows.

 

The PC has a SSD drive that it boots windows from and then an E drive. I have tried running chkdsk for both drives and it doesnt seem to find any errors. Any clues as to what it may be or how to resolve would be great.

 

Many Thanks

 


  • 0

Advertisements


#2
woodhj_uk

woodhj_uk

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts

Hiya,

 

Thanks for this, it cam up at Good and Good 98% for the C drive which is the SSD, It is however saying 98% lifetime used, may be time to suggest he orders a new one.

 

Its odd that once I repaired the boot file, everything seems to work fine, apart from this error message.

 

I shall try let windows repair, or just give it him back with the advice of, get yourself a new drive pronto! Unless there is something I have missed.


  • 0

#3
woodhj_uk

woodhj_uk

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts

It is up to date. The error still arises but....

 

Weirdly, I caught glimpse of another message saying the file history needs fixing too, on the E - drive and I think that is the culprit. As it boots it seeks to scan it (E drive) and gets to 71% then goes straight to the log in screen.

 

Same happens with chkdsk. C drive is fine, E drive, will only allow it to be scanned as it boots, then it goes straight to log in screen. I thought if chkdsk was successful, it triggered a reboot.

 

Im wondering if it is worth trying to run a disk scanner from a simple OS running off USB or DVD. Any recommendations on how I could do this?

 

Thanks for suggestions so far!


  • 0

#4
woodhj_uk

woodhj_uk

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts
Ok. So doing this in recovery mode yielded better info.

The c drive has an error in index $I30 for file 35. When trying to correct an unspecified error occurs (766f6c756d652e63 461).

Googling this seems to suggest a problem with chkdsk itself or registry issues?
  • 0

#5
woodhj_uk

woodhj_uk

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts
Yes several times. It always seems to get stuck at the same place in stage 2
  • 0

#6
woodhj_uk

woodhj_uk

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts
So it's the HDD that is the issue with the above as opposed to the ssd. In the win recovery environment for some reason the c drive was the HDD and the e drive was the ssd. When windows boots it is vice versa.

The problem drive is a Toshiba. No diagnotic so using seatools instead. All tests passed so far. Going to do a long generic but will take a good 2 hours. Will post tomorrow if anything found. The SSD passed all tests.
  • 0

#7
woodhj_uk

woodhj_uk

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts

So I tried chkdsk again, ran the diagnostic tools again on both drives.

 

Chkdsk reports the same issue as above on the HDD and stops. But the diagnostic tool finds no errors. The SSD is fine.

 

Maybe its just a corrupt file and Chkdsk cannot mend it.


  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP