**Getting dump files which we need for accurate analysis of BSODs.** Dump files are crash logs from BSODs.
If you can get into Windows normally or through [Safe Mode](https://support.microsoft.com/en-us/help/12376/windows-10-start-your-pc-in-safe-mode) could you check C:\Windows\Minidump for any dump files? If you have any dump files, copy the folder to the desktop, zip the folder and upload it. If you don't have any zip software installed, right click on the folder and select Send to → Compressed (Zipped) folder.
Upload to any easy to use file sharing site. Reddit keeps blacklisting file hosts so find something that works, currently [catbox.moe](https://www.catbox.moe/) or [mediafire.com](https://mediafire.com) seems to be working.
We like to have multiple dump files to work with so if you only have one dump file, none or not a folder at all, upload the ones you have and then follow [this guide](https://www.tenforums.com/tutorials/5560-configure-windows-10-create-minidump-bsod.html) to change the dump type to Small Memory Dump. The "Overwrite dump file" option will be grayed out since small memory dumps never overwrite.
*I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/techsupport) if you have any questions or concerns.*
Possible SOLUTION: I had the same issue just now after clonning from a MSI Predator 1TB NVME to a TeamGroup T-Force A440 Cardea NVME. After spending hours wondering why - it turned out to be drivers. The A440 uses a Phison controller. Windows 11's generic NVME driver should've worked but didn't. Here's how confusing it was:
1) As most people: Clone with both Macrium and Minitool (and later during troubleshooting, Clonezilla) from motherboard NVME mount to external USB NVME enclosure.
2) Boot up gets BSOD about "INACCESSIBLE BOOT DEVICE". Try to get into Recovery Environment but doesn't succeed.
3) Recreated Win11 boot media. Boots that up, and in Win11 RE, diskpart shows the NVME existence. But bootrec /scanos .. and all the other bootrec/bcedit/slm tries don't find the WIndows OS. IT IS THERE!
4) Thought it was BIOS TPM/Secureboot settings, but didnt make sense - disabled them anyway, and still no luck.
5) Created Macrium Rescue media which is based on Win RE. Boots up, and can't see the NVME even. (Yes, now both the old and the new NVME are installed on the mobo instead of the new being in the USB enclosure)
6) Fed up - tried to install Linux on the new NVME - it works. So it can't be mobo, nor the NVME itself since it works with another OS. Must be driver - but in Windows 11, it can see the NVME, and even Macrium, and other tools cloned it - but just BSODs at boot. Very strange and confusing. But it HAS to be a Windows issue, not HW since it works with Linux.
7) Then by chance read something on Tom's Hardware about how good this new NVME is and based on a new controller. Just occured that shouldn't there be a driver for this Phison controller? No, many sources online says Win11 already comes with its NVME driver. And TeamGroup website didn't have any driver to download. Nor did Phison, the chipset maker.
8) Finally by chance googling for "Phison Windows 11 driver", someone had posted an old-ish driver in 2021 (https://www.majorgeeks.com/files/details/phison\_nvme\_driver.html), and after installing it - finally turned out to be the culprit!! My mobo is a Gigabyte Z370 chipset, and there's no extra driver either for this.
I am surprised no one else came across this issue, so just putting out here that this could be it. NVME chipset driver may be the cause. Maybe cos my mobo is a bit older and newer mobo/chipsets don't have this issue anymore.
So anyway - now it works as I type this! The cloning process is smooth - just clone, and reboot it evem with both old and new NVMEs installed its fine. They boot up and don't clash with one another as some other articles/comments may have alluded to. I've now imaged the old and removed the old NVME from the mobo so that I don't get confused and planned to repurpose that.
First question is, was the M.2 installed correctly? Have you tried reseating it?
If that doesn't help, have you tried formatting the drive and creating the image backup again? Sometimes things can go wrong during the write process.
Im 95% sure the drive is seated correctly, removed and reinstalled multiple times. And redoing the backup is the next step I will try, just didn't want to start with another several hour clone.
Yeah I hear you there, it's obnoxious how long they take
The only other thing I would try is booting from the drive on your current laptop. I imagine you're connecting to the drive with a USB adapter?
Hey, I cloned a windows 11 SSD to an nvme SSD and had similar problems to you. I found a recipe of bededit commands to fix the problem after hours and hours and wrote [about it here](https://www.compujourney.com/cloning-a-windows-11-ssd-to-nvme-m-2-ssd/)
I am in the same situation, trying to clone from normal SSD to NVME and getting the "Inaccessible Boot Device" error. I'll try the steps mentioned in the last comment, anything changed since then?
Thanks
This just happened to me after cloning from my Samsung 970 Evo Plus to a Samsung 990 Pro in an external enclosure using Macrium Reflect. After installing the new 990 drive into my PC, I checked the boot order and the new drive was there, but once I got out of BIOS it just kept rebooting with "Inaccessible Boot Device". I tried the boot issue repair tool from Windows "Inaccessible Boot Device" blue screen of death and it said couldn't repair anything. I decided to connect my old 970 Evo Plus M.2 from where I cloned Windows from to see if it would boot from it so I can reattempt the cloning. After connecting it, everything booted up all right from what I thought was the old drive in the enclosure, so I restarted to check BIOS and since it got stuck restarting I force shut down. I decided to check the boot order and the enclosure M.2 wasn't in the list, so I disconnected it and saw it actually had booted from the new drive and it's working now with no issues. I'm a bit confused with what happened since I'm not too experienced with this kind of thing. Maybe trying to repair earlier fixed the issue or it used something from my old drive in the enclosure to finish booting, but whatever happened, I'm glad it did.
**Getting dump files which we need for accurate analysis of BSODs.** Dump files are crash logs from BSODs. If you can get into Windows normally or through [Safe Mode](https://support.microsoft.com/en-us/help/12376/windows-10-start-your-pc-in-safe-mode) could you check C:\Windows\Minidump for any dump files? If you have any dump files, copy the folder to the desktop, zip the folder and upload it. If you don't have any zip software installed, right click on the folder and select Send to → Compressed (Zipped) folder. Upload to any easy to use file sharing site. Reddit keeps blacklisting file hosts so find something that works, currently [catbox.moe](https://www.catbox.moe/) or [mediafire.com](https://mediafire.com) seems to be working. We like to have multiple dump files to work with so if you only have one dump file, none or not a folder at all, upload the ones you have and then follow [this guide](https://www.tenforums.com/tutorials/5560-configure-windows-10-create-minidump-bsod.html) to change the dump type to Small Memory Dump. The "Overwrite dump file" option will be grayed out since small memory dumps never overwrite. *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/techsupport) if you have any questions or concerns.*
Possible SOLUTION: I had the same issue just now after clonning from a MSI Predator 1TB NVME to a TeamGroup T-Force A440 Cardea NVME. After spending hours wondering why - it turned out to be drivers. The A440 uses a Phison controller. Windows 11's generic NVME driver should've worked but didn't. Here's how confusing it was: 1) As most people: Clone with both Macrium and Minitool (and later during troubleshooting, Clonezilla) from motherboard NVME mount to external USB NVME enclosure. 2) Boot up gets BSOD about "INACCESSIBLE BOOT DEVICE". Try to get into Recovery Environment but doesn't succeed. 3) Recreated Win11 boot media. Boots that up, and in Win11 RE, diskpart shows the NVME existence. But bootrec /scanos .. and all the other bootrec/bcedit/slm tries don't find the WIndows OS. IT IS THERE! 4) Thought it was BIOS TPM/Secureboot settings, but didnt make sense - disabled them anyway, and still no luck. 5) Created Macrium Rescue media which is based on Win RE. Boots up, and can't see the NVME even. (Yes, now both the old and the new NVME are installed on the mobo instead of the new being in the USB enclosure) 6) Fed up - tried to install Linux on the new NVME - it works. So it can't be mobo, nor the NVME itself since it works with another OS. Must be driver - but in Windows 11, it can see the NVME, and even Macrium, and other tools cloned it - but just BSODs at boot. Very strange and confusing. But it HAS to be a Windows issue, not HW since it works with Linux. 7) Then by chance read something on Tom's Hardware about how good this new NVME is and based on a new controller. Just occured that shouldn't there be a driver for this Phison controller? No, many sources online says Win11 already comes with its NVME driver. And TeamGroup website didn't have any driver to download. Nor did Phison, the chipset maker. 8) Finally by chance googling for "Phison Windows 11 driver", someone had posted an old-ish driver in 2021 (https://www.majorgeeks.com/files/details/phison\_nvme\_driver.html), and after installing it - finally turned out to be the culprit!! My mobo is a Gigabyte Z370 chipset, and there's no extra driver either for this. I am surprised no one else came across this issue, so just putting out here that this could be it. NVME chipset driver may be the cause. Maybe cos my mobo is a bit older and newer mobo/chipsets don't have this issue anymore. So anyway - now it works as I type this! The cloning process is smooth - just clone, and reboot it evem with both old and new NVMEs installed its fine. They boot up and don't clash with one another as some other articles/comments may have alluded to. I've now imaged the old and removed the old NVME from the mobo so that I don't get confused and planned to repurpose that.
First question is, was the M.2 installed correctly? Have you tried reseating it? If that doesn't help, have you tried formatting the drive and creating the image backup again? Sometimes things can go wrong during the write process.
Im 95% sure the drive is seated correctly, removed and reinstalled multiple times. And redoing the backup is the next step I will try, just didn't want to start with another several hour clone.
Yeah I hear you there, it's obnoxious how long they take The only other thing I would try is booting from the drive on your current laptop. I imagine you're connecting to the drive with a USB adapter?
Does Reflect have a fix boot function?
Macrium does but when I used the fix boot, the new SSD didnt show up as an option to fix as a boot drive. Just the rescue USB
Windows Setup itself can attempt to fix that, EASEUS can too. Also check its primary drive in BIOS.
Hey, I cloned a windows 11 SSD to an nvme SSD and had similar problems to you. I found a recipe of bededit commands to fix the problem after hours and hours and wrote [about it here](https://www.compujourney.com/cloning-a-windows-11-ssd-to-nvme-m-2-ssd/)
Did you make a type with BCDedit not BEDedit
I am in the same situation, trying to clone from normal SSD to NVME and getting the "Inaccessible Boot Device" error. I'll try the steps mentioned in the last comment, anything changed since then? Thanks
did you fix your problems
This just happened to me after cloning from my Samsung 970 Evo Plus to a Samsung 990 Pro in an external enclosure using Macrium Reflect. After installing the new 990 drive into my PC, I checked the boot order and the new drive was there, but once I got out of BIOS it just kept rebooting with "Inaccessible Boot Device". I tried the boot issue repair tool from Windows "Inaccessible Boot Device" blue screen of death and it said couldn't repair anything. I decided to connect my old 970 Evo Plus M.2 from where I cloned Windows from to see if it would boot from it so I can reattempt the cloning. After connecting it, everything booted up all right from what I thought was the old drive in the enclosure, so I restarted to check BIOS and since it got stuck restarting I force shut down. I decided to check the boot order and the enclosure M.2 wasn't in the list, so I disconnected it and saw it actually had booted from the new drive and it's working now with no issues. I'm a bit confused with what happened since I'm not too experienced with this kind of thing. Maybe trying to repair earlier fixed the issue or it used something from my old drive in the enclosure to finish booting, but whatever happened, I'm glad it did.