Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- System Information (local)
- --------------------------------------------------------------------------------
- computer name: USER-PC
- windows version: Windows 7 Service Pack 1, 6.1, build: 7601
- windows dir: C:\Windows
- CPU: GenuineIntel Intel(R) Core(TM) i5 CPU 650 @ 3.20GHz Intel586, level: 6
- 4 logical processors, active mask: 15
- RAM: 8513904640 total
- VM: 2147352576, free: 1965506560
- --------------------------------------------------------------------------------
- Crash Dump Analysis
- --------------------------------------------------------------------------------
- Crash dump directory: C:\Windows\Minidump
- Crash dumps are enabled on your computer.
- On Tue 22/01/2013 5:08:09 PM GMT your computer crashed
- crash dump file: C:\Windows\Minidump\012313-20732-01.dmp
- This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
- Bugcheck code: 0xA (0xFFFFF6FC40E50A60, 0x2, 0x0, 0xFFFFF80003D138C2)
- 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/01/2013 5:08:09 PM 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 (0xFFFFF6FC40E50A60, 0x2, 0x0, 0xFFFFF80003D138C2)
- 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 Tue 22/01/2013 1:35:57 PM GMT your computer crashed
- crash dump file: C:\Windows\Minidump\012213-29109-01.dmp
- This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
- Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000E2EAE0, 0xFFFF, 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 Mon 21/01/2013 4:10:23 PM GMT your computer crashed
- crash dump file: C:\Windows\Minidump\012213-27783-01.dmp
- This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
- Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000E2EB10, 0xFFFF, 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 Mon 21/01/2013 7:52:00 AM GMT your computer crashed
- crash dump file: C:\Windows\Minidump\012113-17893-01.dmp
- This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
- Bugcheck code: 0x50 (0xFFFFF700018CA238, 0x0, 0xFFFFF80003C97C43, 0x2)
- 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 Mon 21/01/2013 6:54:08 AM GMT your computer crashed
- crash dump file: C:\Windows\Minidump\012113-20888-01.dmp
- This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
- Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000E2EAE0, 0xFFFF, 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 Sun 20/01/2013 4:47:04 PM GMT your computer crashed
- crash dump file: C:\Windows\Minidump\012113-20560-01.dmp
- This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
- Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000E2EB10, 0xFFFF, 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 Sun 20/01/2013 1:14:40 PM GMT your computer crashed
- crash dump file: C:\Windows\Minidump\012013-19141-01.dmp
- This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
- Bugcheck code: 0x50 (0xFFFFFA000737B4D0, 0x0, 0xFFFFF80003D05E2A, 0x7)
- 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 Sun 20/01/2013 12:07:47 PM GMT your computer crashed
- crash dump file: C:\Windows\Minidump\012013-22744-01.dmp
- This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
- Bugcheck code: 0x19 (0x3, 0xFFFFFA80066920D0, 0xFFFFFA80066920D0, 0xFFDFFA80066920D0)
- Error: BAD_POOL_HEADER
- 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 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.
- The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
- On Sat 19/01/2013 7:51:50 AM GMT your computer crashed
- crash dump file: C:\Windows\Minidump\011913-20545-01.dmp
- This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
- Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000E2EAE0, 0xFFFF, 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 Sat 19/01/2013 2:41:16 AM GMT your computer crashed
- crash dump file: C:\Windows\Minidump\011913-22323-01.dmp
- This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
- Bugcheck code: 0x50 (0xFFFFF8A00F60E000, 0x0, 0xFFFFF80003F16B9B, 0x2)
- 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 Thu 17/01/2013 2:31:34 PM GMT your computer crashed
- crash dump file: C:\Windows\Minidump\011813-21590-01.dmp
- This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
- Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000E2EB10, 0xFFFF, 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 17/01/2013 2:05:57 AM GMT your computer crashed
- crash dump file: C:\Windows\Minidump\011713-21746-01.dmp
- This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
- Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80003CD2F90)
- Error: UNEXPECTED_KERNEL_MODE_TRAP
- file path: C:\Windows\system32\ntoskrnl.exe
- product: Microsoft® Windows® Operating System
- company: Microsoft Corporation
- description: NT Kernel & System
- Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
- 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 14/01/2013 4:29:36 AM GMT your computer crashed
- crash dump file: C:\Windows\Minidump\011413-56519-01.dmp
- This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
- Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000E2EAE0, 0xFFFF, 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 Sun 13/01/2013 2:47:02 PM GMT your computer crashed
- crash dump file: C:\Windows\Minidump\011413-25958-01.dmp
- This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
- Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000E2EAE0, 0xFFFF, 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.
- --------------------------------------------------------------------------------
- Conclusion
- --------------------------------------------------------------------------------
- 51 crash dumps have been found and analyzed. Only 15 are included in this report. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.
- 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.
Add Comment
Please, Sign In to add comment