Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- System Information (local)
- --------------------------------------------------------------------------------
- computer name: BEN
- windows version: Windows 7 Service Pack 1, 6.1, build: 7601
- windows dir: C:\Windows
- CPU: AuthenticAMD AMD Turion(tm) II Neo N40L Dual-Core Processor AMD586, level: 16
- 2 logical processors, active mask: 3
- RAM: 4294111232 total
- VM: 2147352576, free: 1956618240
- --------------------------------------------------------------------------------
- Crash Dump Analysis
- --------------------------------------------------------------------------------
- Crash dump directory: C:\Windows\Minidump
- Crash dumps are enabled on your computer.
- On Tue 6/26/2012 11:22:36 PM GMT your computer crashed
- crash dump file: C:\Windows\Minidump\062612-68047-01.dmp
- This was probably caused by the following module: fltmgr.sys (fltmgr+0x4CB3)
- Bugcheck code: 0xA (0xFFFFFA8027943120, 0x2, 0x1, 0xFFFFF80002D7E366)
- Error: IRQL_NOT_LESS_OR_EQUAL
- file path: C:\Windows\system32\drivers\fltmgr.sys
- product: Microsoft® Windows® Operating System
- company: Microsoft Corporation
- description: Microsoft Filesystem Filter Manager
- 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 6/26/2012 11:22:36 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 (0xFFFFFA8027943120, 0x2, 0x1, 0xFFFFF80002D7E366)
- 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 which cannot be identified at this time.
- On Fri 6/22/2012 3:23:16 AM GMT your computer crashed
- crash dump file: C:\Windows\Minidump\062112-65395-01.dmp
- This was probably caused by the following module: fltmgr.sys (fltmgr+0x4CB3)
- Bugcheck code: 0xA (0xFFFFFA80279310A0, 0x2, 0x1, 0xFFFFF80001B8C366)
- Error: IRQL_NOT_LESS_OR_EQUAL
- file path: C:\Windows\system32\drivers\fltmgr.sys
- product: Microsoft® Windows® Operating System
- company: Microsoft Corporation
- description: Microsoft Filesystem Filter Manager
- 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 Thu 6/21/2012 8:46:19 PM GMT your computer crashed
- crash dump file: C:\Windows\Minidump\062112-64646-01.dmp
- This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
- Bugcheck code: 0xA (0xFFFFFA80278B0110, 0x2, 0x1, 0xFFFFF80001B9B366)
- 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.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement