Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
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
FreeBooter

FreeBooter

    Member 1K

  • Member
  • PipPipPipPip
  • 1,126 posts

Check SMART health report of the drive in question with CrystalDiskInfo program.


  • 0

#3
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

#4
FreeBooter

FreeBooter

    Member 1K

  • Member
  • PipPipPipPip
  • 1,126 posts

Update the SSD firmware see what happens.


  • 0

#5
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

#6
FreeBooter

FreeBooter

    Member 1K

  • Member
  • PipPipPipPip
  • 1,126 posts

Create yourself a Windows 8.1 Setup DVD using Windows 8.1 Media Creation Tool .

Please boot your computer with Windows Setup Media and from Windows Recovery Environment start the Command Prompt.

Please type below command into Command Prompt and press Enter key.

Following command will  fixes errors on the disk and locates bad sectors and recovers readable information.

Chkdsk D: /f

Please replace partition letter D: with Windows installed partition letter.  When computer boots into Windows Recovery Environment (WinRE) environment the drive letter assign to Windows partition may not be C: drive letter because Windows 7, 8 , 8.1 and 10 creates a separate system partition when it's installed from scratch. The system partition contains boot files WinRE assigns the system partition the C: drive letter and the Windows installed partition will be assign any other drive letter usually D: drive letter is assign to Windows installed partition. The Bcdedit /enum | find "osdevice" command can be use to find out the drive letter of the Windows installed partition the output of the Bcdedit command is similar to this osdevice partition=D:. The drive letter after partition= is the drive letter of the Windows partition.


Edited by FreeBooter, 24 April 2017 - 09:42 PM.

  • 0

#7
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

#8
FreeBooter

FreeBooter

    Member 1K

  • Member
  • PipPipPipPip
  • 1,126 posts

Have you run the chkdsk command more then once?


  • 0

#9
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

#10
FreeBooter

FreeBooter

    Member 1K

  • Member
  • PipPipPipPip
  • 1,126 posts

See if SSD manufacturer has a diagnostic tool.


  • 0

#11
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

#12
FreeBooter

FreeBooter

    Member 1K

  • Member
  • PipPipPipPip
  • 1,126 posts

If its HDD has the issue then execute Chkdsk C:  /r  command.


  • 0

#13
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

#14
FreeBooter

FreeBooter

    Member 1K

  • Member
  • PipPipPipPip
  • 1,126 posts

There is a chance there are too many bad sectors which indicates HDD failing which could be reason Chkdsk cannot repair HDD errors there may be no good spare sectors left in this case i suggest you replace the HDD with brand new one. You can also try reinstalling Windows OS.


  • 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