Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Automatic repair/recovery loop, C:/ empty
#11
well if C drive is wipe it would not be able to boot to windows
Reply

#12
A Found.xxxx file is created when chkdsk finds corrupted files. At this point... I would suggest to stop doing anything with the system and recover those important files before they end up unrecoverable. After that, do a fresh install.
L.S. Computer Systems
807 East Broadway
Hopewell, VA. 23860, USA
+1 (804) 715-8185
https://www.lscomputersystems.com
Reply

#13
If I were you I would try these commands:
(Go to command prompt at bootup)
type these commands:
bootrec.exe /rebuildbcd
bootrec.exe /fixmbr
bootrec.exe /fixboot
type exit
Reboot
This should fix the MBR and you can then cancel that reason off the board as an error. Make sure to make a backup before doing it, if you haven't already.
Paul
Reply

#14
Like a said ages ago

Quote:Could be any of these reasons:



  • Bad MBR Configuration
  • Bad IDE/SATA cables
  • Bad Hard Drive
  • Bad Partition Table
  • Bad RAM memory
  • Check BIOS settings
  • Update BIOS version

Its One of the above. Check drive would be my first test.
<left><form action="https://www.paypal.com/cgi-bin/webscr" method="post">If you are satisfied with my help, consider a donation. Thank you so much for your continued support! 
<input type="hidden" name="cmd" value="_s-xclick">
<input type="hidden" name="hosted_button_id" value="Y4ZDLXGFS4F8Q">
<input type="image" src="https://www.paypalobjects.com/en_US/GB/i/btn/btn_donateCC_LG.gif" border="0" name="submit" alt="PayPal — The safer, easier way to pay online.">
<img alt="" border="0" src="https://www.paypalobjects.com/en_GB/i/scr/pixel.gif" width="0" height="0">
</form>

   </div></left> 
Reply

#15
(02-12-2018, 09:42 PM)Britec Wrote:  Like a said ages ago

Quote:Could be any of these reasons:


  • Bad MBR Configuration
  • Bad IDE/SATA cables
  • Bad Hard Drive
  • Bad Partition Table
  • Bad RAM memory
  • Check BIOS settings
  • Update BIOS version

Its One of the above. Check drive would be my first test.


Just checked the drive with a relative of mine the C: drive is empty size changed from GB to MB I'll update for the results
Reply

#16
(02-17-2018, 07:21 PM)JohnGrussland Wrote:  
(02-12-2018, 09:42 PM)Britec Wrote:  Like a said ages ago


Quote:Could be any of these reasons:



  • Bad MBR Configuration
  • Bad IDE/SATA cables
  • Bad Hard Drive
  • Bad Partition Table
  • Bad RAM memory
  • Check BIOS settings
  • Update BIOS version

Its One of the above. Check drive would be my first test.


Just checked the drive with a relative of mine the C: drive is empty size changed from GB to MB I'll update for the results

ok so my relative had a spare hard drive so we hooked it up installed windows connected the other hard drive and came to a conclusion the whole drive was wiped now i'm looking for a free data recovery software so i could recover the files since the one who gave us windows 10 has created a backup of our files on his pc but he is out of town till summer i believe
Reply

#17
it sounds like  to me if the hard drive failing  I would check the health  status of the hard drive

before trying to recover any data how to check your hard drive health status with crystal disk info
Reply



Forum Jump:


Users browsing this thread:
2 Guest(s)

Powered By MyBB, © 2002-2024 Melroy van den Berg.