Results 1 to 5 of 5
  1. #1
    New Lounger
    Join Date
    Oct 2012
    Thanked 0 Times in 0 Posts

    Sudden problems with Disk Errors

    Quote Originally Posted by Just Plain Fred View Post
    Try entering "BIOS" (configure) usually "Esc, or F-10 " depends on your PC ...Check to see that the "Boot order" is set to boot from
    1st ...CD\DVD's
    2nd... Hard Drive group
    3rd,4th anything else

    Also check "Boot Menu" and make sure that the Boot partition is first in the Que... if there are partitions..
    If you can borrow a repair disk (Win 7 made on another PC) you could try to repair the "MBR" (boot portion of your HD)

    Regards Fred

    PS: See MBR
    Hi Fred,

    I am having a similar issue with my father's desktop pc. He has an HP Pavilion p6310f:
    AMD Athlon II X4 630(2.8GHz) Quadcore Processor
    6GB of memory

    Anyways, this computer has run perfectly the past 2+ years we've had it until tonight. I have been borrowing the keyboard that came along with it (wired USB kb) at night, as I spilled coffee on my wireless one and haven't replaced it yet. Several times today, the Pavilion would "freeze up" and the only way I could get it to shut down was by either hitting CTRL-Alt-DLT, then unplugging the kb or manually turning the PC off. The third time I went to restart it I got an error stating
    "Checking file system on C: The type of the file system is NTFS, volume label is HP. One of your disks needs to be checked for consistency"

    So, I allowed the chkdsk to run and when it got to about 40% complete it started saying things like "deleting such and such file on label xyz etc....". It did this for about 2-3 minutes. By the time the OS finally loaded we got multiple error messages that Adobe and several other applications were corrupted. I opened up the "HP ADVISOR/HP TOTAL CARE application that comes with the computer and it mentioned several things needed to be fixed and downloaded. It got halfway thru that and gave me and error saying:
    "at HPAssistant.Data.dsActiveCheckRes.load ACResults(String filterCategory, Boolean include Ignored)".

    This was in a popup message so I just closed it. I was finally able to run "Startup Repair" and it told me "Attempting repairs....Repairing disk errors. This might take over an hour to complete."
    Well about 10 minutes later it said it thought it had solved the problem and asked us to press a key to restart and make sure there were no more issues.
    As soon as we rebooted, we got the final error message:

    "Reboot and Select proper Boot Device or Insert Boot Media in Selected Boot Device and press a key"

    Tried to reboot several times after that and now the PC is stuck at the initial screen where it lists "F10-Setup ESC-Boot Menu F11-System Recovery F9-Diagnostics".
    I cannot get the computer past this point now and it will not recognize the keyboard at all.

    Could switching in and out the keyboard several times, along with manually shutting down the PC have damaged the main hard drive? Every time I re-attached the keyboard to the PC it would have to find and then reinstall new drivers from the web. Could I have gotten a virus, etc from this?

    Any help is GREATLY appreciated and sorry for the novel.


  2. #2
    Super Moderator CLiNT's Avatar
    Join Date
    Dec 2009
    California & Arizona
    Thanked 609 Times in 557 Posts
    Not likely, check your hard drive's integrity with a bootable Windows 7 disk and use the recovery console's command prompt to perform a
    thorough checkdisk with the "R" switch enabled. (may need to repeat)

    chkdsk c: /r

    Shutting down the computer manually, as in a forced restart, is far more likely to cause damage and or file corruption.
    The Keyboard will have nothing whatsoever to do with it.

    Of course too, you could be experiencing other hardware related issues as well.
    After the above checkdisk has been completed I would run Windows memory diagnostic, or Memtest86, for at least 6 hrs or overnight.
    Invest a little time and energy in a well thought out BACKUP regimen and you will have minimal down time, and headache.

    Build your own system; get everything you want and nothing you don't.
    Latest Build:
    ASUS X99 Deluxe, Core i7-5960X, Corsair Hydro H100i, Plextor M6e 256GB M.2 SSD, Corsair DOMINATOR Platinum 32GB DDR4@2666, W8.1 64 bit,
    EVGA GTX980, Seasonic PLATINUM-1000W PSU, MountainMods U2-UFO Case, and 7 other internal drives.

  3. #3
    WS Lounge VIP
    Join Date
    Dec 2009
    Thanked 1,117 Times in 1,040 Posts
    You might want to make a backup before you start. If you have an external disk you can connect it when you are at the Recovery Console and then use the "copy" command to copy your data to the external disk. Assuming you have enough space on your external disk and it shows up as drive E:, you can run this command. It will take quite a while to run.

    xcopy c:\ e:\Backup-C /s/e/i

    cheers, Paul

  4. #4
    WS Lounge VIP mrjimphelps's Avatar
    Join Date
    Dec 2009
    Thanked 453 Times in 422 Posts
    The keyboard swap had nothing to do with it. The most likely problem is a bad hard drive / hard drive controller / cable. Or maybe some critical Windows data got corrupted on your hard drive.

    If the following works, then you likely don't have a bad hard drive: Do a complete backup of the hard drive, and then run a fresh windows install on it. Don't format the drive; however, you should install a fresh copy of Windows over the current copy. This will preserve your data while fixing Windows.

    If that doesn't work, you could put in a new hard drive and run your factory rebuild disks on it. Then install the old hard drive as your second hard drive. In this way, you could hopefully copy the data from the old drive to the new. Once you have copied the data, remove the old hard drive.

  5. #5
    2 Star Lounger
    Join Date
    Mar 2010
    Midwest USA
    Thanked 2 Times in 2 Posts
    Smells like a failing hard drive to me. Make that backup ASAP if there's any data you want to keep. Most important is the /Users folder and everything underneath.

    Perhaps a chkdsk as Clint says will do the job, at least it might get you to the point where the backup works.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts