System Information (local)
--------------------------------------------------------------------------------
computer name: BLOOM
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASUSTeK Computer INC., Crosshair IV Formula
CPU: AuthenticAMD AMD Phenom(tm) II X6 1090T Processor AMD586, level: 16
6 logical processors, active mask: 63
RAM: 4292988928 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 2015-02-07 10:43:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020715-14929-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF8800550C6E4)
Bugcheck code: 0x19 (0x3, 0xFFFFFA800517E2C0, 0x460001, 0xFFFFF6FD4003E5C8)
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.
Google query: BAD_POOL_HEADER
On Thu 2015-02-05 15:58:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020515-13790-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x76E80)
Bugcheck code: 0x1A (0x41287, 0x30, 0x0, 0x0)
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 that cannot be identified at this time.
On Thu 2015-02-05 14:58:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020515-15022-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF880045906E4)
Bugcheck code: 0x50 (0xFFFFF88003154CD0, 0x1, 0xFFFFF80002D916B3, 0x0)
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.
Google query: PAGE_FAULT_IN_NONPAGED_AREA
On Wed 2015-02-04 14:18:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020415-15990-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xE9090)
Bugcheck code: 0xD1 (0xFFFFF880012EB090, 0x0, 0x8, 0xFFFFF880012EB090)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ntfs.sys
product: Operativsystemet Microsoft® Windows®
company: Microsoft Corporation
description: NTFS-drivrutin
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 Wed 2015-02-04 14:17:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020415-14430-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR
On Wed 2015-02-04 14:15:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020415-13260-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x76E80)
Bugcheck code: 0xD1 (0xF955000, 0x2, 0x1, 0x1EC3598)
Error: DRIVER_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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 2015-02-01 18:20:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020115-15194-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x76E80)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF80002C82069, 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 Sun 2015-02-01 14:27:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020115-14523-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x76E80)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002DC9D8A)
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 2015-01-29 15:27:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012915-23400-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF8800450C6E4)
Bugcheck code: 0xFC (0xFFFFF900C1F2ACE0, 0xBC30000111504863, 0xFFFFF8800654B440, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
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.
A third party driver was identified as the probable root cause of this system error.
Google query: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
On Thu 2015-01-29 14:51:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012915-14508-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF880041526E4)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880095CAB18, 0xFFFFF880095CA370, 0xFFFFF80002CF3912)
Error: NTFS_FILE_SYSTEM
Bug check description: This indicates a problem occurred in the NTFS file system.
A third party driver was identified as the probable root cause of this system error.
Google query: NTFS_FILE_SYSTEM