Advertisement
BennyB79

Untitled

Jun 26th, 2012
70
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.94 KB | None | 0 0
  1. System Information (local)
  2. --------------------------------------------------------------------------------
  3.  
  4. computer name: BEN
  5. windows version: Windows 7 Service Pack 1, 6.1, build: 7601
  6. windows dir: C:\Windows
  7. CPU: AuthenticAMD AMD Turion(tm) II Neo N40L Dual-Core Processor AMD586, level: 16
  8. 2 logical processors, active mask: 3
  9. RAM: 4294111232 total
  10. VM: 2147352576, free: 1956618240
  11.  
  12.  
  13.  
  14. --------------------------------------------------------------------------------
  15. Crash Dump Analysis
  16. --------------------------------------------------------------------------------
  17.  
  18. Crash dump directory: C:\Windows\Minidump
  19.  
  20. Crash dumps are enabled on your computer.
  21.  
  22.  
  23. On Tue 6/26/2012 11:22:36 PM GMT your computer crashed
  24. crash dump file: C:\Windows\Minidump\062612-68047-01.dmp
  25. This was probably caused by the following module: fltmgr.sys (fltmgr+0x4CB3)
  26. Bugcheck code: 0xA (0xFFFFFA8027943120, 0x2, 0x1, 0xFFFFF80002D7E366)
  27. Error: IRQL_NOT_LESS_OR_EQUAL
  28. file path: C:\Windows\system32\drivers\fltmgr.sys
  29. product: Microsoft® Windows® Operating System
  30. company: Microsoft Corporation
  31. description: Microsoft Filesystem Filter Manager
  32. Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
  33. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  34. 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.
  35.  
  36.  
  37. On Tue 6/26/2012 11:22:36 PM GMT your computer crashed
  38. crash dump file: C:\Windows\memory.dmp
  39. This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
  40. Bugcheck code: 0xA (0xFFFFFA8027943120, 0x2, 0x1, 0xFFFFF80002D7E366)
  41. Error: IRQL_NOT_LESS_OR_EQUAL
  42. Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
  43. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  44. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
  45.  
  46.  
  47. On Fri 6/22/2012 3:23:16 AM GMT your computer crashed
  48. crash dump file: C:\Windows\Minidump\062112-65395-01.dmp
  49. This was probably caused by the following module: fltmgr.sys (fltmgr+0x4CB3)
  50. Bugcheck code: 0xA (0xFFFFFA80279310A0, 0x2, 0x1, 0xFFFFF80001B8C366)
  51. Error: IRQL_NOT_LESS_OR_EQUAL
  52. file path: C:\Windows\system32\drivers\fltmgr.sys
  53. product: Microsoft® Windows® Operating System
  54. company: Microsoft Corporation
  55. description: Microsoft Filesystem Filter Manager
  56. Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
  57. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  58. 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.
  59.  
  60.  
  61. On Thu 6/21/2012 8:46:19 PM GMT your computer crashed
  62. crash dump file: C:\Windows\Minidump\062112-64646-01.dmp
  63. This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
  64. Bugcheck code: 0xA (0xFFFFFA80278B0110, 0x2, 0x1, 0xFFFFF80001B9B366)
  65. Error: IRQL_NOT_LESS_OR_EQUAL
  66. file path: C:\Windows\system32\ntoskrnl.exe
  67. product: Microsoft® Windows® Operating System
  68. company: Microsoft Corporation
  69. description: NT Kernel & System
  70. Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
  71. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  72. 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