On Tue 15/11/2011 20:16:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111511-17160-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)  
Bugcheck code: 0xA (0x10, 0x2, 0x0, 0xFFFFF80002AAAA41)
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 which cannot be identified at this time.  
 
 
On Tue 15/11/2011 20:16:48 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: netio.sys (NETIO!KfdAleRemoveFlowContextTable+0x99)  
Bugcheck code: 0xA (0x10, 0x2, 0x0, 0xFFFFF80002AAAA41)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.  
 
 
On Tue 15/11/2011 18:28:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111511-16302-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)  
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80002ACC3F8)
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 which cannot be identified at this time.  
 
 
On Tue 15/11/2011 16:36:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111511-15724-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)  
Bugcheck code: 0x109 (0xA3A039D8985D56AB, 0x0, 0x516A87F27A877637, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
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.  
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.  
 
 
On Tue 15/11/2011 15:53:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111511-18969-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)  
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80002ACA3F8)
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 which cannot be identified at this time.  
 
 
On Tue 15/11/2011 11:28:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111511-16146-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)  
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80002AFC3F8)
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 which cannot be identified at this time.  
 
 
On Tue 15/11/2011 11:02:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111511-17518-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)  
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8008477B30, 0xFFFFFA8008477E10, 0xFFFFF80002DDB300)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.  
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 which cannot be identified at this time.  
 
 
On Tue 15/11/2011 10:55:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111511-17300-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)  
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80002ABD3F8)
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 which cannot be identified at this time.  
 
 
On Tue 15/11/2011 10:23:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111511-24226-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)  
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80002B073F8)
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 which cannot be identified at this time.  
 
 
On Tue 15/11/2011 09:31:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111511-18033-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)  
Bugcheck code: 0x109 (0xA3A039D898E47823, 0xB3B7465EEB614869, 0xFFFFF80002B21AE9, 0x0)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
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.  
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.  
 
 
On Tue 15/11/2011 07:42:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111511-19125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)  
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80002B0E3F8)
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 which cannot be identified at this time.  
 
 
On Tue 15/11/2011 07:25:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111511-17222-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)  
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80002B003F8)
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 which cannot be identified at this time.  
 
 
On Tue 15/11/2011 07:20:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111511-19203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)  
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80002B083F8)
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 which cannot be identified at this time.  
 
 
On Tue 15/11/2011 03:31:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111511-21356-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)  
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80002B043F8)
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 which cannot be identified at this time.  
 
 
On Tue 15/11/2011 03:22:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111511-22900-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)  
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80002AB23F8)
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 which cannot be identified at this time.