Results 1 to 3 of 3
  1. #1
    Super Moderator bbearren's Avatar
    Join Date
    Dec 2009
    Polk County, Florida
    Thanked 451 Times in 357 Posts

    Follow-up on replacing HDD with SSD

    In the thread, "No boot device...", in my last post I wrote, "Everything's like it should be now, all partitions aligned, and both sides of my dual boot working as they should."

    I had booted and rebooted, hibernated and woke up that laptop a number of times over the weekend. Evidently, the last time I closed the lid, I had the AC charger plugged in and it just didn't register in my mind. It didn't hibernate, it went to sleep, which means it keeps enough power on to keep the RAM refreshed, and doesn't write it out to hiberfil.sys.

    Monday at work, when I opened the laptop, I got the blue Windows 8 logo, then it shut down. I tried a couple of times, but nothing. I broke out the pencil, and got what needed to be done accomplished, then put the laptop on the charger in my truck, and tried to wake it up again; same story. So I booted into the Dell Diagnostics, discovered that the battery was at 1% and charging. I let the diagnostics run, stopped it on the memory test and rebooted, and it booted into Windows.

    I transferred my penciled work to my working file, closed the lid, and went to my next stop. Again, Windows 8 logo, then shutdown. I finished out my morning, got my work done on my desktop, then started looking into the laptop. The logo meant that it was trying to resume, but it wouldn't even get as far as the spinning marbles before it would shut down. So I decided to go back to square one.

    I still had the full drive image I had made when I made the changeover to SSD, so I booted my Image For Windows Rescue USB stick, and found the image on my NAS. I decided to pay closer attention this time. Image For Windows is GPT aware, and it is SSD aware. The first time I ticked "Align to target" on the restore options. This time I ticked that again, and also "Fit to target"; IFW will expand to fill a larger drive. The old drive was 240GB, the SSD is 256GB.

    That worked, and I booted into Windows 8. I used Msinfo32 to check my partition alignment, and they were all good. Next I took a closer look at the "unknown"s in my BCD Store" using BootIt Bare Metal; it has its own BCD Edit function. The failed wake seemed to me that Windows was calling for the wrong resumeobject in the BCD Store. And it was. It was calling for the MBR restore and not the GPT restore (invalid GUID). So I deleted the invalid entries in the BCD store.

    Next I tried booting into Windows 7, and got a yellow fuzzy screen. So back into BootIt BM, and the BCD Store. Sure enough, there was a \windows\system32\winload.exe entry for Windows 7, so I deleted that and a couple more invalid entries. Now I could boot into Windows 7.

    I booted back into Windows 8, tried a couple of hibernations, no difficulties. At work today, everything was normal once again.

    Moral of the story: you just can't beat a good drive image, and extraneous entries in the BCD Store can come back to bite.
    Last edited by bbearren; 2014-07-09 at 10:39. Reason: clarity
    Create a fresh drive image before making system changes, in case you need to start over!

    "The problem is not the problem. The problem is your attitude about the problem. Savvy?"—Captain Jack Sparrow "When you're troubleshooting, start with the simple and proceed to the complex."—M.O. Johns "Experience is what you get when you're looking for something else."—Sir Thomas Robert Deware.
    Unleash Windows

  2. #2
    Super Moderator RetiredGeek's Avatar
    Join Date
    Mar 2004
    Manning, South Carolina
    Thanked 1,609 Times in 1,453 Posts

    Thanks for the update and useful information.
    May the Forces of good computing be with you!


    PowerShell & VBA Rule!

    My Systems: Desktop Specs
    Laptop Specs

  3. #3
    WS Lounge VIP
    Join Date
    Dec 2009
    Thanked 1,125 Times in 1,048 Posts
    I admire your perseverance but this really is beyond mere mortals. I can't imagine anyone I know being able to diagnose BCD errors. I know it'd take me some serious thinking and I've been doing this for over 20 years.

    cheers, Paul

Posting Permissions

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