On Thu 8/23/2012 4:44:40 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082312-23571-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xBE (0xFFFFF8A0096B4B80, 0x8000000172C75820, 0xFFFFF8800DE37320, 0xE)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 Thu 8/23/2012 4:44:40 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1!VidMmInterface+0x9C4A)
Bugcheck code: 0xBE (0xFFFFF8A0096B4B80, 0x8000000172C75820, 0xFFFFF8800DE37320, 0xE)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 Mon 8/20/2012 4:32:26 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082012-15163-01.dmp
This was probably caused by the following module: unknown_module_00000000`0000000a.sys (Unloaded_Unknown_Module_00000000`0000000a+0xF)
Bugcheck code: 0x19 (0x3, 0xFFFFF8A00FB61590, 0xFFFFF8A00FB61590, 0xFFFFF8A0039CC6C8)
Error: BAD_POOL_HEADER
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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.
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: unknown_module_00000000`0000000a.sys .
Google query: unknown_module_00000000`0000000a.sys BAD_POOL_HEADER
On Fri 8/17/2012 6:18:57 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081712-22105-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x5001, 0xFFFFF70001080000, 0xDB, 0xDEFF7FFFFE)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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 Mon 8/13/2012 3:39:07 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081312-15912-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0xFFFFF683FF765E70, 0x0, 0x0, 0xFFFFF8000329C168)
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 8/7/2012 12:32:55 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080612-19718-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x31E79)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88004831E79, 0xFFFFF8800879C868, 0xFFFFF8800879C0C0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 which cannot be identified at this time.
On Wed 8/1/2012 1:10:01 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073112-22152-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x4E (0x99, 0x167E88, 0x0, 0x48088)
Error: PFN_LIST_CORRUPT
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 page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 Fri 7/27/2012 5:29:20 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072712-27284-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x504B0606, 0xFFFFFA800A25B282)
Error: BAD_POOL_CALLER
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 current thread is making a bad pool request.
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 Thu 7/19/2012 6:21:50 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071912-21824-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x1790C0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
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 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 Fri 7/6/2012 4:08:51 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070612-14991-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0xA (0xFFFFFA7FE7FFFFD8, 0x2, 0x1, 0xFFFFF800030F7B74)
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.
10 crash dumps have been found and analyzed. A third party driver has 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:
unknown_module_00000000`0000000a.sys
Facebook
Twitter
Instagram