Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- Crash dump directory: C:\Windows\Minidump
- Crash dumps are enabled on your computer.
- On Wed 16/01/2013 16:59:13 GMT your computer crashed
- crash dump file: C:\Windows\Minidump\011613-21028-01.dmp
- This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCD10)
- Bugcheck code: 0x4E (0x99, 0xC6A8C, 0x1, 0x5258C)
- Error: PFN_LIST_CORRUPT
- file path: C:\Windows\system32\ntkrnlpa.exe
- product: Microsoft® Windows® Operating System
- company: Microsoft Corporation
- description: NT Kernel & System
- Bug check description: This indicates that the page frame number (PFN) list is corrupted.
- 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 Wed 16/01/2013 16:59:13 GMT your computer crashed
- crash dump file: C:\Windows\memory.dmp
- This was probably caused by the following module: ntkrpamp.exe (nt!KeBugCheckEx+0x1E)
- Bugcheck code: 0x4E (0x99, 0xC6A8C, 0x1, 0x5258C)
- Error: PFN_LIST_CORRUPT
- Bug check description: This indicates that the page frame number (PFN) list is corrupted.
- 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. It is suggested you look for an update for the following driver: ntkrpamp.exe .
- Google query: ntkrpamp.exe PFN_LIST_CORRUPT
- On Wed 16/01/2013 16:05:07 GMT your computer crashed
- crash dump file: C:\Windows\Minidump\011613-23244-01.dmp
- This was probably caused by the following module: npfs.sys (Npfs+0x9F09)
- Bugcheck code: 0x50 (0xFFFFFFFF80B137E8, 0x1, 0xFFFFFFFF90C80F09, 0x0)
- Error: PAGE_FAULT_IN_NONPAGED_AREA
- file path: C:\Windows\system32\drivers\npfs.sys
- product: Microsoft® Windows® Operating System
- company: Microsoft Corporation
- description: NPFS Driver
- 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 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 16/01/2013 15:52:02 GMT your computer crashed
- crash dump file: C:\Windows\Minidump\011613-24148-01.dmp
- This was probably caused by the following module: ntkrnlpa.exe (nt+0x858E3)
- Bugcheck code: 0x50 (0xFFFFFFFF80001C34, 0x0, 0xFFFFFFFF82C6965A, 0x0)
- Error: PAGE_FAULT_IN_NONPAGED_AREA
- file path: C:\Windows\system32\ntkrnlpa.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 Wed 16/01/2013 14:17:10 GMT your computer crashed
- crash dump file: C:\Windows\Minidump\011613-25443-01.dmp
- This was probably caused by the following module: ntkrnlpa.exe (nt+0x467EB)
- Bugcheck code: 0xA (0xFFFFFFFFC4F08AA5, 0x2, 0x0, 0xFFFFFFFF82A6CE86)
- Error: IRQL_NOT_LESS_OR_EQUAL
- file path: C:\Windows\system32\ntkrnlpa.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 Wed 16/01/2013 07:30:32 GMT your computer crashed
- crash dump file: C:\Windows\Minidump\011613-29094-01.dmp
- This was probably caused by the following module: ntkrnlpa.exe (nt+0x4342A)
- Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82005037, 0xFFFFFFFF9EFC3CA8, 0x0)
- Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
- file path: C:\Windows\system32\ntkrnlpa.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.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement