well idk if this is what you need for a diagnosis:
On Sun 15/12/2013 4:31:35 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\121413-22448-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x118, 0x2, 0x0, 0xFFFFF8000338BD47)
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 15/12/2013 4:31:35 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x118, 0x2, 0x0, 0xFFFFF8000338BD47)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Mon 09/12/2013 4:27:45 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120813-20014-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4688)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800CFC8EF8, 0xFFFFF8800CFC8750, 0xFFFFF80003287770)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
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 Mon 09/12/2013 4:10:55 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120813-27596-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x14A, 0x2, 0x1, 0xFFFFF8000332BC9F)
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 Thu 21/11/2013 5:33:18 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112013-15085-01.dmp
This was probably caused by the following module: alsysio64.sys (0xFFFFF88009F1461E)
Bugcheck code: 0x50 (0xFFFFFA800AE00000, 0x0, 0xFFFFF88009F1461E, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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.
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: alsysio64.sys .
Google query: alsysio64.sys PAGE_FAULT_IN_NONPAGED_AREA
On Wed 20/11/2013 5:21:59 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111913-16270-01.dmp
This was probably caused by the following module: alsysio64.sys (0xFFFFF88009CBC61E)
Bugcheck code: 0x50 (0xFFFFFA8015A00000, 0x0, 0xFFFFF88009CBC61E, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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.
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: alsysio64.sys .
Google query: alsysio64.sys PAGE_FAULT_IN_NONPAGED_AREA
On Wed 20/11/2013 4:31:09 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111913-14632-01.dmp
This was probably caused by the following module: alsysio64.sys (0xFFFFF880099C061E)
Bugcheck code: 0x50 (0xFFFFFA8015A00000, 0x0, 0xFFFFF880099C061E, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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.
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: alsysio64.sys .
Google query: alsysio64.sys PAGE_FAULT_IN_NONPAGED_AREA
On Fri 15/11/2013 6:07:50 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111413-14149-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x47, 0x2, 0x1, 0xFFFFF8000337DC9F)
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 Tue 22/10/2013 3:26:03 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\102113-14929-01.dmp
This was probably caused by the following module: alsysio64.sys (0xFFFFF8800ACF161E)
Bugcheck code: 0x50 (0xFFFFFA8015A00000, 0x0, 0xFFFFF8800ACF161E, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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.
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: alsysio64.sys .
Google query: alsysio64.sys PAGE_FAULT_IN_NONPAGED_AREA
On Wed 09/10/2013 3:33:43 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100813-21528-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88002D65180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
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 expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
11 crash dumps have been found and analyzed. Only 10 are included in this report. 2 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:
iomap64.sys
alsysio64.sys
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 actually 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.
Facebook
Twitter
Instagram