random bluescreens after cloning bootdrive twice

[sharki]

So after cloning my boot drive to a different drive, and cloning it back because the bootdrive didn't work, I have experienced quitte a lot of crashes.

 

Why I started all this:

http://linustechtips.com/main/topic/335048-blue-screen-after-15-minutes-in-sleep-mode/#entry4598089

 

 

But now I'm stuck with what seems like a boot drive with some errors. Battlefield 4 showed errors when starting, and now completely won't start. 

WhoCrashed says all of the bluescreens are caused by tthe windows operating system.

 

Is there a way to repair this?

 

Recent crash reports:

 

On Sat 28-3-2015 18:36:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032815-10795-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xF163C)
Bugcheck code: 0xD1 (0xFFFFF8800132563C, 0x2, 0x8, 0xFFFFF8800132563C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ntfs.sys
product: Besturingssysteem Microsoft® Windows®
company: Microsoft Corporation
description: NT-bestandssysteemstuurprogramma
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 28-3-2015 15:44:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032815-8970-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74E90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 28-3-2015 15:38:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032815-7503-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF800032C05A2, 0xFFFFF880035E06D8, 0xFFFFF880035DFF30)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 

[Enderman]

This is why you DONT CLONE DRIVES.

 

Stop doing it people. Don't be lazy and take the time and effort to do a proper clean install and you won't need to deal with issues like this.

The best thing you can do now is format and reinstall everything from scratch.