Crash Dump Analysis
--------------------------------------------------------------------------------
 
Crash dump directory: C:\Windows\Minidump
 
Crash dumps are enabled on your computer.
 
On Wed 15/04/2015 12:45:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041515-18220-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x10CE0)  
Bugcheck code: 0xFC (0xFFFFF8800CA358A0, 0x800000032F60E963, 0xFFFFF8800CA353B0, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
Bug check description: This indicates that an attempt was made to execute non-executable memory.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware.  
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 Wed 15/04/2015 12:32:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041515-18283-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x5E1C)  
Bugcheck code: 0x50 (0xFFFFF800073CBFA0, 0x8, 0xFFFFF800073CBFA0, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
Bug check description: This indicates that invalid system memory has been referenced.
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 Sun 12/04/2015 11:33:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041215-30482-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)  
Bugcheck code: 0xA (0xFFFFF70040077C80, 0x2, 0x0, 0xFFFFF800030AB492)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Sun 12/04/2015 10:42:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041215-30544-01.dmp
This was probably caused by the following module: iusb3xhc.sys (0xFFFFF88003CBE604)  
Bugcheck code: 0xD1 (0xFFFFFA802DEBAFAB, 0x2, 0x0, 0xFFFFF88003CBE604)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\iusb3xhc.sys
product: USB 3.0 Device Driver
company: Intel Corporation
description: Intel(R) USB 3.0 eXtensible Host Controller Driver
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.  
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: iusb3xhc.sys (Intel(R) USB 3.0 eXtensible Host Controller Driver, Intel Corporation).  
Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL
 
 
 
On Sat 11/04/2015 16:49:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041115-31340-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 11/04/2015 14:32:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041115-32058-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)  
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800033861EC, 0xFFFFF880137C9FC0, 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 Fri 10/04/2015 13:44:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041015-24180-01.dmp
This was probably caused by the following module: dxgmms1.sys (0xFFFFF8800532D666)  
Bugcheck code: 0x3D (0xFFFFF800043C7B00, 0x0, 0x0, 0xFFFFF8800532D666)
Error: INTERRUPT_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This bug check appears very infrequently.  
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 Thu 09/04/2015 16:04:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040915-30778-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF88004767274)  
Bugcheck code: 0xD1 (0x1A4, 0x5, 0x0, 0xFFFFF88004767274)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 347.88  
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 347.88  
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.  
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 347.88 , NVIDIA Corporation).  
Google query: NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL
 
 
 
On Wed 08/04/2015 23:02:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040915-33306-01.dmp
This was probably caused by the following module: teedriverx64.sys (0xFFFFF88003D171F4)  
Bugcheck code: 0x10D (0x4, 0x0, 0xFFFFF88003D171F4, 0xFFFFFA800DA9A800)
Error: WDF_VIOLATION
file path: C:\Windows\system32\drivers\teedriverx64.sys
product: Intel(R) Management Engine Interface
company: Intel Corporation
description: Intel(R) Management Engine Interface
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.  
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: teedriverx64.sys (Intel(R) Management Engine Interface, Intel Corporation).  
Google query: Intel Corporation WDF_VIOLATION
 
 
 
On Wed 08/04/2015 18:34:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040815-15990-01.dmp
This was probably caused by the following module: Unknown (0x00000000)  
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003381972, 0xFFFFF8800C40D090, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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.  
A third party driver was identified as the probable root cause of this system error.  
Google query: SYSTEM_SERVICE_EXCEPTION
 
 
 
 
 
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
 
14 crash dumps have been found and analyzed. Only 10 are included in this report. 3 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:  
 
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 347.88 , NVIDIA Corporation)
teedriverx64.sys (Intel(R) Management Engine Interface, Intel Corporation)
iusb3xhc.sys (Intel(R) USB 3.0 eXtensible Host Controller Driver, Intel Corporation)
 
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
 
 
Read the topic general suggestions for troubleshooting system crashes for more information.  
 
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.