lots of bluescreens after cloning boot drive twice

[sharki]

This is the thrid time I'm writing this post so I'll keep it short. All prevorious text got erased by chrashes  <_<

 

After cloning my boot drive twice for this problem:

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

 

I have experienced quitt a few bluescreens. Does anyone know what might be the problem?

 

reports from WhoCrashed:

On Sat 28-3-2015 20:37:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032815-10420-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800032B25A2, 0xFFFFF8800F071CE0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 20:31:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032815-9500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF800032BA5A2, 0xFFFFF880009A9758, 0xFFFFF880009A8FB0)
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.



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. 

[blu4]

Drive related mate A fresh install will definitely fix this.

[sharki]

I thought so too, but if there is an easyer way that would be nice. 

HD tune sayd the ssd is fine, windows itself is then broken I guess?

 

One more for the list:

On Sat 28-3-2015 20:44:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032815-11122-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. 

 

I'm currently trying to reinstall Battlefield 4, wich also doensn't work. My pc ran OK for a while, but when opening Origin to install Battlefield it crashes again.