[SOLVED] Random Windows 10 Blue screen cloned SSD

[martinatremblay]

I recently purchased a new Crucial MX500 and installed a successful clone of my old Hitachi drive into my Samsung laptop. Everything worked perfectly the first week, although I originally experienced software upgrade/installation issues with Chrome and Windows update. I have been able to remedy the upgrade/install issue by adjusting BIOS settings and windows update now runs and chrome is installed as are windows updates.

I also started to have random Blue Screens. To remedy, I re-cloned several times in attempt to repair but random Blue Screens continued. I also attempted and was unsuccessful in attempting to do a clean install of windows onto the cloned drive (after wiping partitions and reformatting) and was unsuccessful in having windows do a reset of the cloned drive.
I have already successfully run; DISM /Online /Cleanup-Image /RestoreHealth and SFC Scannow. I have not been able to successfully run Chkdsk.
If I revert back to the original 750gb Hitachi drive the issues go away. To date I have not been able to resolve and need your expertise to eliminate the blue screens. Could the blue screens be caused by permissions that did not copy over when the SSD was cloned using Acronis?

System Details:
Windows 10 Professional (x64) Version 1803 (build 17134.556)
Boot Mode: Legacy BIOS in UEFI (Secure Boot not supported)
SAMSUNG RC512 07VQ
Intel Core i7-2630QM 2.00 gigahertz
UEFI: American Megatrends Inc. 07VQ.M026.20110307.SSH 03/07/2011
Drives
500.11 Gigabytes Usable Hard Drive Capacity
371.36 Gigabytes Hard Drive Free Space
TSSTcorp DVDWBD TS-LB23D [Optical drive]
CT500MX500SSD1 [Hard drive] (500.11 GB) -- drive 0, rev M3CR023, SMART Status: Healthy
Memory Modules 6056 Megabytes Usable Installed Memory
Local Drive Volumes c: (NTFS on drive 0) 500.11 GB 371.36 GB free

Error Dump
==================================================
Dump File : 020919-15000-01.dmp
Crash Time : 2/9/2019 11:45:41 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000006
Parameter 2 : fffff801`704fe812
Parameter 3 : ffff8000`c3808ca0
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+1aa0c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.17134.556 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+1aa0c0
==================================================
Thanks in advance for your help!

 

[karenjoly]

Have you tried a clone with Macrium Reflect Free ? See here

http://knowledgebase.macrium.com/display/KNOW/Cloning+a+disk

You say

I was unsuccessful in attempting to do a clean install of windows onto the cloned drive (after wiping partitions and reformatting) and was unsuccessful in having windows do a reset of the cloned drive.

What errors arise when installing windows ?


You say

I have not been able to successfully run Chkdsk.

What errors arise ?

Are you sure this new drive has ever worked properly ?

 

[martinatremblay]

Thanks Karenjoly - I tried clones with Acronis (came with Drive when purchased), with Macrium, EaseUS and with Clonezilla. All with similar results. I'm still using the Clonezilla clone. Windows updates and a clean install would not work on the Acronis nor the Macrium clones. error was something like "windows cannot be installed to this disk". Windows update troubleshooter also did not help. Now that I have adjusted the BIOS settings it is possible that the fresh install would work, but I have not tried a fresh install or restore since I was able to remedy the updates error as I will lose some software I am unable to get keys for (MS Office Pr) that was originally installed under the Microsoft Home Use Program so I would prefer to remedy the current clone if possible.

Chkdsk gets stuck at 12% with no errors, it just stops. I am unable to interrupt the Chkdsk while running, and have to do a hard shutdown and press any key during startup or I am stuck in the Chkdsk repair loop.

and no, I'm not certain the drive ever worked properly! Maybe it has bad sectors or whatever it is that SSDs get.

 

[karenjoly]

The BSOD details are very common and may refer to a memory malfunction arising from a driver error and from a disk read/write problem, one after another ! You could try a memory test but why bother since there is no problem when using the original 750 drive.

I would let chkdsk run ( such as it is) overnight. If it does not complete by then I suggest you contemplate returning the drive under warranty.

 

[martinatremblay]

Ran Chkdsk overnight and ran into multiple various BSOD failures. Will be looking to return drive as suggested.