On Fri 5/23/2014 6:28:33 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052314-5631-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x24, 0x2, 0x0, 0xFFFFF8000307077F)
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 Fri 5/23/2014 6:28:33 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: iusb3xhc.sys (iusb3xhc+0x6337B)
Bugcheck code: 0xA (0x24, 0x2, 0x0, 0xFFFFF8000307077F)
Error: 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 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.
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 IRQL_NOT_LESS_OR_EQUAL
On Fri 5/23/2014 6:11:21 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052314-4414-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x8DBC)
Bugcheck code: 0xD1 (0x188, 0x2, 0x1, 0xFFFFF88004208DBC)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 Fri 5/23/2014 6:08:54 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052314-4742-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFD8, 0x0, 0xFFFFF800030CDC1A, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 5/23/2014 5:35:05 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052314-4680-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFC2, 0x1, 0xFFFFF80003084990, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 5/23/2014 5:20:40 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052314-4648-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B90)
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 Fri 5/23/2014 5:08:40 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052314-4992-01.dmp
This was probably caused by the following module: cng.sys (cng+0x7585)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88001614585, 0xFFFFF880035CB388, 0xFFFFF880035CABE0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\cng.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Cryptography, Next Generation
Bug check description: This indicates that a system thread 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 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 Fri 5/23/2014 2:30:44 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052214-5865-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xA825, 0xF, 0x1, 0xFFFFF800030BB15E)
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 Fri 5/23/2014 1:58:24 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052214-5506-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xFFFFF8A007BDB024, 0xE, 0x0, 0xFFFFF800030AAA9F)
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 Fri 5/23/2014 1:43:02 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052214-5616-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFD8, 0x0, 0xFFFFF8000308EC1A, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.