Forum Thread

BSOD After OS to SSD Migration

mickey4paws 4,849 1,297 January 23, 2014 at 12:34 PM
So I have a new Dell XPS 8700 and a new Crucial M500 240gb SSD drive. I used Paragon Migrate OS to SSD and after rebooting, I am getting BSOD, with error code that has a bunch of zero's ending in 1E. Safemode also reproduces BSOD. I did a search but so far, not finding anything helpful. The SSD was fine before I did the migration as far as accessing and partitioning it. I do have another drive, so maybe I'll try that just to rule out a faulty drive.

Does anyone have any ideas to trouble shoot this? Thanks.

49 Comments

1 2 3 4

Sign up for a Slickdeals account to remove this ad.

#2
Quote from mickey4paws View Post :
So I have a new Dell XPS 8700 and a new Crucial M500 240gb SSD drive. I used Paragon Migrate OS to SSD and after rebooting, I am getting BSOD, with error code that has a bunch of zero's ending in 1E. Safemode also reproduces BSOD. I did a search but so far, not finding anything helpful. The SSD was fine before I did the migration as far as accessing and partitioning it. I do have another drive, so maybe I'll try that just to rule out a faulty drive.

Does anyone have any ideas to trouble shoot this? Thanks.
I don't know Paragon and what settings there are to be made, if at all.
Was it a simple clone, like "Clone HDD to SSD", end of story, or were there all sorts of settings, like IDE, AHCI, RAID choices, etc?
Have you verified the bios to make sure that the SATA setting is still in AHCI, or whatever they might call it on your Dell, in other words, not IDE, as that would definitely make it blue screen.
Reply Helpful Comment? 0 0
Joined Dec 2004
Deal Addict
4,849 Posts
1,297 Reputation
Original Poster
#3
Quote from RockySosua View Post :
I don't know Paragon and what settings there are to be made, if at all.
Was it a simple clone, like "Clone HDD to SSD", end of story, or were there all sorts of settings, like IDE, AHCI, RAID choices, etc?
Have you verified the bios to make sure that the SATA setting is still in AHCI, or whatever they might call it on your Dell, in other words, not IDE, as that would definitely make it blue screen.
The first time, I put the SSD in a USB 3.0 caddy and did a simple clone HDD to SSD with Paragon which is supposed to work great from reviews I've read. Then I took out the SSD and put it in the case, changed boot options in Bios (AHCI was already selected). It starts booting into Windows and then bam, BSOD.

So next I deleted the partition on the SSD and went through the HDD to SSD process again, only this time I left the SSD connected in the case. Same results with BSOD.

Then I checked the firmware on the SSD, but it's already the latest version. I'm so frustrated, I don't know what to do next. I do have 2 more of these Crucial SSD's so wonder if I should try another one. Although I don't think it's hardware failure as before I did the cloning the disk worked fine as a USB mass storage device.

One thought or question is I know you've worked on Dell's. I see in the HDD that there are 3 partitions: 1. Dell Utlities 2. Recovery 3. OS

When I did the clone, I only cloned the OS and programs. Should I have copied over the first 2 partitions too? I can't see them in Windows Explorer so I don't know exactly what's on them.
Reply Helpful Comment? 0 0
Some days you are the windshield, some days the bug.
#4
Quote from mickey4paws View Post :
The first time, I put the SSD in a USB 3.0 caddy and did a simple clone HDD to SSD with Paragon which is supposed to work great from reviews I've read. Then I took out the SSD and put it in the case, changed boot options in Bios (AHCI was already selected). It starts booting into Windows and then bam, BSOD.

So next I deleted the partition on the SSD and went through the HDD to SSD process again, only this time I left the SSD connected in the case. Same results with BSOD.

Then I checked the firmware on the SSD, but it's already the latest version. I'm so frustrated, I don't know what to do next. I do have 2 more of these Crucial SSD's so wonder if I should try another one. Although I don't think it's hardware failure as before I did the cloning the disk worked fine as a USB mass storage device.

One thought or question is I know you've worked on Dell's. I see in the HDD that there are 3 partitions: 1. Dell Utlities 2. Recovery 3. OS

When I did the clone, I only cloned the OS and programs. Should I have copied over the first 2 partitions too? I can't see them in Windows Explorer so I don't know exactly what's on them.
One is most likely the dell recovery, and the other a reserved partition for the OS which you need .
Reply Helpful Comment? 0 0
....


...
#5
Quote from mickey4paws View Post :
The first time, I put the SSD in a USB 3.0 caddy and did a simple clone HDD to SSD with Paragon which is supposed to work great from reviews I've read. Then I took out the SSD and put it in the case, changed boot options in Bios (AHCI was already selected). It starts booting into Windows and then bam, BSOD.

So next I deleted the partition on the SSD and went through the HDD to SSD process again, only this time I left the SSD connected in the case. Same results with BSOD.

Then I checked the firmware on the SSD, but it's already the latest version. I'm so frustrated, I don't know what to do next. I do have 2 more of these Crucial SSD's so wonder if I should try another one. Although I don't think it's hardware failure as before I did the cloning the disk worked fine as a USB mass storage device.

One thought or question is I know you've worked on Dell's. I see in the HDD that there are 3 partitions: 1. Dell Utlities 2. Recovery 3. OS

When I did the clone, I only cloned the OS and programs. Should I have copied over the first 2 partitions too? I can't see them in Windows Explorer so I don't know exactly what's on them.
I can't say for sure what's the right way to do it with Paragon, but just as an example, when I clone Samsung drives from a Dell XPS, it only brings the boot partitions and the OS and does not bring the recovery sector along.
In theory, the user would make a recovery drive on a thumb drive, from the original HDD, then if they run into problems with the SSD, they can still attain all the recovery options.
So, in short, the fact that the recovery partition was not copied over to the SSD should have no negative effect on the SSD and the OS.
Reply Helpful Comment? 0 0
#6
Another one of those SSD's that you have.
Swap the SATA data and power cables with the DVD player, just as a test.
Maybe do a Google search on Paragon clones producing blue screens.
I can't think of anything else right now.
Reply Helpful Comment? 0 0
#7
Quote from mickey4paws View Post :
So I have a new Dell XPS 8700 and a new Crucial M500 240gb SSD drive. I used Paragon Migrate OS to SSD and after rebooting, I am getting BSOD, with error code that has a bunch of zero's ending in 1E. Safemode also reproduces BSOD. I did a search but so far, not finding anything helpful. The SSD was fine before I did the migration as far as accessing and partitioning it. I do have another drive, so maybe I'll try that just to rule out a faulty drive.

Does anyone have any ideas to trouble shoot this? Thanks.
Check your registry and make certain that Windows is expecting to boot in AHCI mode. There's a tutorial here: http://www.tomshardware.com/forum...-mode-hdds
Reply Helpful Comment? 0 0
#8
Quote from HarryH3 View Post :
Check your registry and make certain that Windows is expecting to boot in AHCI mode. There's a tutorial here: http://www.tomshardware.com/forum...-mode-hdds
I've read about that before and although it's a great solution, I don't think that the OP can use it as he can't get the SSD to boot up, so as to attain the registry.
Reply Helpful Comment? 0 0

Sign up for a Slickdeals account to remove this ad.

#9
Quote from RockySosua View Post :
I've read about that before and although it's a great solution, I don't think that the OP can use it as he can't get the SSD to boot up, so as to attain the registry.
Yeah, it has to be done before cloning the disk. Frown But it sounds like he's already becoming an expert at the clone process. Wink
Reply Helpful Comment? 0 0
Joined Dec 2004
Deal Addict
4,849 Posts
1,297 Reputation
Original Poster
#10
Thanks so much for the replies. Tomorrow when I get to work, I'll try another one of the SSD's I have.

Now I can still boot to the HDD no problem. So I updated all the drivers, including chipset, sata and video. I'm going to try doing the cloning again and see if that makes any difference. Although if I didn't have a problem in the OS on the HDD, I don't understand why I'm having a problem booting the same OS on the SSD. It just doesn't make any sense to me.

One last thing I did was I downloaded the new version of Paragon, just to see if that makes any difference. I've had such good luck with backup and restore with Paragon but I've never used their cloning before.

I've done some googling and found this. Not sure if this would be helpful or not.

"1. Insert the Windows 7 installation disc in the drive and start the computer.
Select a language, a time, a currency, a keyboard or an input method, and then click Next.
Click on Repair your computer.
Select the Operating System that you want to repair, and then click Next.
In the System Recovery Options window, click option Command Prompt.
Now type Bootrec.exe in the Command Prompt and hit ENTER key.
You will get options as shown in screen-shot below.


Now type bootrec.exe /FixMbr. If there is problem in Master Boot Record (MBR), you should now get message as The operation completed successfully.

Type bootrec.exe /FixBoot.

Finally, type bootrec.exe /RebuildBcd.

After finishing, type exit and close the window.

Now reboot and check, whether the problem is solved. In most cases, the Booting problem should vanish, and your Windows should boot normally."

Anyway, thanks again and I'll post back tomorrow and hopefully get this thing fixed.

I can check the registry to see if it's expecting to boot into AHCI and I would assume the cloned OS would have the same registry settings?
Reply Helpful Comment? 0 0
Joined Dec 2004
Deal Addict
4,849 Posts
1,297 Reputation
Original Poster
#11
I'll also check the cables. One thing I did was the HDD used to be Sata0 and when I connected the SSD, I made that Sata0 and the HDD Sata1. That shouldn't matter though, should it?
Reply Helpful Comment? 0 0
#12
Quote from mickey4paws View Post :
Thanks so much for the replies. Tomorrow when I get to work, I'll try another one of the SSD's I have.

Now I can still boot to the HDD no problem. So I updated all the drivers, including chipset, sata and video. I'm going to try doing the cloning again and see if that makes any difference. Although if I didn't have a problem in the OS on the HDD, I don't understand why I'm having a problem booting the same OS on the SSD. It just doesn't make any sense to me.

One last thing I did was I downloaded the new version of Paragon, just to see if that makes any difference. I've had such good luck with backup and restore with Paragon but I've never used their cloning before.

I've done some googling and found this. Not sure if this would be helpful or not.

"1. Insert the Windows 7 installation disc in the drive and start the computer.
Select a language, a time, a currency, a keyboard or an input method, and then click Next.
Click on Repair your computer.
Select the Operating System that you want to repair, and then click Next.
In the System Recovery Options window, click option Command Prompt.
Now type Bootrec.exe in the Command Prompt and hit ENTER key.
You will get options as shown in screen-shot below.


Now type bootrec.exe /FixMbr. If there is problem in Master Boot Record (MBR), you should now get message as The operation completed successfully.

Type bootrec.exe /FixBoot.

Finally, type bootrec.exe /RebuildBcd.

After finishing, type exit and close the window.

Now reboot and check, whether the problem is solved. In most cases, the Booting problem should vanish, and your Windows should boot normally."

Anyway, thanks again and I'll post back tomorrow and hopefully get this thing fixed.

I can check the registry to see if it's expecting to boot into AHCI and I would assume the cloned OS would have the same registry settings?
if its blue screening its not the MBR. my guess its looking for the 2nd partition windows now makes. I would try just cloning all 3 partitions over
Reply Helpful Comment? 0 0
Joined Mar 2004
L11: Monkey's Apprentice
17,199 Posts
2,789 Reputation
#13
I would reiterate the clone ALL partitions, that can rather easily screw things up. If you want to get rid of the extra partitions I would do a fresh install.
Reply Helpful Comment? 0 0
Quote :
Reading comprehension isn't just for school children!
#14
Quote from mickey4paws View Post :
I'll also check the cables. One thing I did was the HDD used to be Sata0 and when I connected the SSD, I made that Sata0 and the HDD Sata1. That shouldn't matter though, should it?
Do you mean that you swapped inputs on the mobo, or something you did in the bios?
Quote from brbubba View Post :
I would reiterate the clone ALL partitions, that can rather easily screw things up. If you want to get rid of the extra partitions I would do a fresh install.
I think that the major stumbling block for most people is that they don't have access to a Win 8 installation disc.
Reply Helpful Comment? 0 0
Joined Mar 2004
L11: Monkey's Apprentice
17,199 Posts
2,789 Reputation
#15
Quote from RockySosua View Post :
I think that the major stumbling block for most people is that they don't have access to a Win 8 installation disc.
All the more reason to make sure you clone all the partitions, including the recovery partition. Big Grin
Reply Helpful Comment? 0 0
Page 1 of 4
1 2 3 4
Join the Conversation
Add a Comment
 
Copyright 1999 - 2016. Slickdeals, LLC. All Rights Reserved. Copyright / Infringement Policy  •  Privacy Policy  •  Terms of Service  •  Acceptable Use Policy (Rules)  •  Interest-Based Ads
Link Copied to Clipboard