Advertisement
Guest User

Untitled

a guest
Jan 16th, 2013
283
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 5.05 KB | None | 0 0
  1. Crash dump directory: C:\Windows\Minidump
  2.  
  3. Crash dumps are enabled on your computer.
  4.  
  5. On Wed 16/01/2013 16:59:13 GMT your computer crashed
  6. crash dump file: C:\Windows\Minidump\011613-21028-01.dmp
  7. This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCD10)
  8. Bugcheck code: 0x4E (0x99, 0xC6A8C, 0x1, 0x5258C)
  9. Error: PFN_LIST_CORRUPT
  10. file path: C:\Windows\system32\ntkrnlpa.exe
  11. product: Microsoft® Windows® Operating System
  12. company: Microsoft Corporation
  13. description: NT Kernel & System
  14. Bug check description: This indicates that the page frame number (PFN) list is corrupted.
  15. 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.
  16. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  17.  
  18.  
  19.  
  20. On Wed 16/01/2013 16:59:13 GMT your computer crashed
  21. crash dump file: C:\Windows\memory.dmp
  22. This was probably caused by the following module: ntkrpamp.exe (nt!KeBugCheckEx+0x1E)
  23. Bugcheck code: 0x4E (0x99, 0xC6A8C, 0x1, 0x5258C)
  24. Error: PFN_LIST_CORRUPT
  25. Bug check description: This indicates that the page frame number (PFN) list is corrupted.
  26. 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.
  27. 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: ntkrpamp.exe .
  28. Google query: ntkrpamp.exe PFN_LIST_CORRUPT
  29.  
  30.  
  31.  
  32. On Wed 16/01/2013 16:05:07 GMT your computer crashed
  33. crash dump file: C:\Windows\Minidump\011613-23244-01.dmp
  34. This was probably caused by the following module: npfs.sys (Npfs+0x9F09)
  35. Bugcheck code: 0x50 (0xFFFFFFFF80B137E8, 0x1, 0xFFFFFFFF90C80F09, 0x0)
  36. Error: PAGE_FAULT_IN_NONPAGED_AREA
  37. file path: C:\Windows\system32\drivers\npfs.sys
  38. product: Microsoft® Windows® Operating System
  39. company: Microsoft Corporation
  40. description: NPFS Driver
  41. Bug check description: This indicates that invalid system memory has been referenced.
  42. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  43. 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.
  44.  
  45.  
  46.  
  47. On Wed 16/01/2013 15:52:02 GMT your computer crashed
  48. crash dump file: C:\Windows\Minidump\011613-24148-01.dmp
  49. This was probably caused by the following module: ntkrnlpa.exe (nt+0x858E3)
  50. Bugcheck code: 0x50 (0xFFFFFFFF80001C34, 0x0, 0xFFFFFFFF82C6965A, 0x0)
  51. Error: PAGE_FAULT_IN_NONPAGED_AREA
  52. file path: C:\Windows\system32\ntkrnlpa.exe
  53. product: Microsoft® Windows® Operating System
  54. company: Microsoft Corporation
  55. description: NT Kernel & System
  56. Bug check description: This indicates that invalid system memory has been referenced.
  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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  59.  
  60.  
  61.  
  62. On Wed 16/01/2013 14:17:10 GMT your computer crashed
  63. crash dump file: C:\Windows\Minidump\011613-25443-01.dmp
  64. This was probably caused by the following module: ntkrnlpa.exe (nt+0x467EB)
  65. Bugcheck code: 0xA (0xFFFFFFFFC4F08AA5, 0x2, 0x0, 0xFFFFFFFF82A6CE86)
  66. Error: IRQL_NOT_LESS_OR_EQUAL
  67. file path: C:\Windows\system32\ntkrnlpa.exe
  68. product: Microsoft® Windows® Operating System
  69. company: Microsoft Corporation
  70. description: NT Kernel & System
  71. Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
  72. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  73. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  74.  
  75.  
  76.  
  77. On Wed 16/01/2013 07:30:32 GMT your computer crashed
  78. crash dump file: C:\Windows\Minidump\011613-29094-01.dmp
  79. This was probably caused by the following module: ntkrnlpa.exe (nt+0x4342A)
  80. Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82005037, 0xFFFFFFFF9EFC3CA8, 0x0)
  81. Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
  82. file path: C:\Windows\system32\ntkrnlpa.exe
  83. product: Microsoft® Windows® Operating System
  84. company: Microsoft Corporation
  85. description: NT Kernel & System
  86. Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
  87. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  88. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement