BSOD after cloning to SSD

Solved
Mika5716 Posted messages 43 Status Member -  
Mika5716 Posted messages 43 Status Member -
Hello everyone,

I used Acronis True Image to clone the HDD of a laptop to a WD 250GB SSD with a desktop PC, everything goes well during the boot on the SSD, Windows starts up fine and I reach the desktop, it detects the SSD and automatically installs the driver associated with it and asks me to restart. I do this, but at the moment the W7 loading bar appears after the restart, I get a BSOD with error 0x0000007b.

The source disk was in MBR and Acronis converted the target SSD to GPT during cloning, so I had to change the SATA mode in the BIOS to UEFI. I don't think this matters since W7 booted fine the first time.

I tried downgrading the BIOS, same result. Reverted to the latest version of the BIOS, same result.

I am on a HP Elitebook 840 G1, W7 64

Any idea what the problem might be?

10 answers

  1. Anonymous user
     
    Hello

    A SSD does not require a driver, but the "Sata" controller on the motherboard probably does!!

    Is your BIOS up to date?

    You can find all the drivers on the HP support site -> https://support.hp.com/fr-fr/drivers/selfservice/hp-elitebook-840-g1-notebook-pc/5405360

    But why are you still on Windows 7, which is no longer updated and less secure?
    Your browser will gradually no longer be able to access HTTPS sites that are regularly updated for security!!

    Have you tried upgrading to Windows 10, which is fully supported by your HP Elitebook 840 G1?

    Cheers
    --
    If the answer helped you: a little thank you is nice. If it's resolved: the green button at the top is better ;-)

    Let him who has never opened a user manual throw the first mouse.
    0
    1. Anonymous user
       
      Je ne peux pas accéder à des articles ou des liens externes.
      0
  2. Mika5716 Posted messages 43 Status Member
     
    Upon the first startup, I saw a pop-up in the taskbar with the SSD model name "WD250GXXX" and the installation of the device driver, and after the restart and installation of this driver, I still have this BSOD. My BIOS is up to date.
    0
  3. Mika5716 Posted messages 43 Status Member
     
    Yes, I read this article, but I can't use the W7 installation key because it detects the OS as different from the one on the key, even though both are the same: W7 Pro 64-bit. I still use W7 because I installed W10, but I had hardware and software compatibility issues.
    0
  4. Anonymous user
     
    Hello
    Have you tried "Safe Mode"?
    Press F8 during startup before the Windows logo..
    See you+
    --
    If the answer helped you: a little thank you is nice. If it's resolved: the green button at the top is better ;-)

    Let he who has never opened a user manual throw me the first mouse.
    0
  5. Mika5716 Posted messages 43 Status Member
     
    I cannot access it, it crashes beforehand.
    0
  6. Anonymous user
     
    Hello
    It's curious because the "safe mode" is offered before Windows and its drivers load...

    If it "crashes" (I hardly believe it...) before, then it's not a Windows or driver issue...

    It would rather be a "boot partition" problem. Try to "reset" the BIOS to "default" or perform a "reset" on it!!

    See you later
    --
    If this answer helped you: a little thank you is nice. If it's resolved: the green button at the top is better ;-)

    Let the one who has never opened a user manual throw the first mouse at me.
    0
  7. Mika5716 Posted messages 43 Status Member
     
    The BIOS reset doesn't change anything.
    I would be tempted to redo the cloning and when I boot for the first time, I uninstall the driver that Windows installs for me.
    0
  8. Anonymous user
     
    Hello
    If Windows installs a driver on its own, it's because it needs it...
    But try to find that driver on the support I provided in the link and install it manually to see.
    See you later
    --
    If the answer helped you: a little thank you is nice. If it's resolved: the green button at the top is better ;-)

    Let he who has never opened a user manual throw the first mouse at me.
    0
  9. Mika5716 Posted messages 43 Status Member
     
    It seems that when you tried to clone your PC, it accidentally booted from the SSD, which triggered a CHKDSK that completed successfully. However, it then appears to retry the operation unsuccessfully, showing an error message that it "cannot execute autochk due to a recently installed software package." Eventually, you were able to boot into Windows 7 on your laptop with the SSD. The only issue is that it continues to attempt a CHKDSK at startup with the same error message, although Windows 7 is functioning.

    You want to disable the check at startup.

    Thank you for your help.
    0
    1. Mika5716 Posted messages 43 Status Member
       
      By putting the SSD back on my desktop, it booted from it unintentionally, performed a CHKDSK, and then started correctly on the desktop.

      I reinsert the SSD into my laptop, and it tries a CHKDSK but fails, telling me it can't "execute autochk due to a recently installed software package"; it continues to boot and the desktop opens, miracle.

      However, each time I start, it attempts a CHKDSK with the same error. It seems to me that we can disable this check at startup; I need to find out how.

      Thank you.
      0
  10. Anonymous user
     
    Hello
    If this issue is resolved, that's perfect!
    For chkdsk, you can do it once in Windows, in 2 ways...

    1) Right-click on the disk (SSD), Properties, Tools, Error Checking...
    Since it's in use, it will offer to do it at the next restart...

    2) Open a cmd window in Admin mode (right-click) and on the disk
    c:
    type
    chkdsk /f
    and press Enter.

    See you!
    If the answer helped you: a little thank you is nice. If it's resolved: the green button at the top is better ;-)

    Let him who has never opened a user manual throw the first mouse.
    0
    1. Mika5716 Posted messages 43 Status Member
       
      Great, thank you and have a good Sunday.
      0