bananalint
New Member
- Messages
- 3
I am at my wits end trying to figure out what the problem is. I have tried everything. I get these bsod once a day. Sometimes they occur twice a day. I ran Memtest86+ and only got errors with the new hammer tests in v6.0. I didn't think that could be the problem since it's a new test. I did get like 12 hammer test errors. I've tried DISM, sfc /scannow and everything came back ok. I've reinstalled my video drivers, I scanned my HD with Seatools. The drivers that are mostly affected are ntoskrnl.exe and ntfs.sys. Please can anyone help me find out what the problem is? I just built this PC four months ago.
On Tue 4/14/2015 11:20:31 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041415-27328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0xDE (0x2, 0xFFFFC0008C2C3300, 0xFFFFC0008C2C3201, 0x86B338C0)
Error: POOL_CORRUPTION_IN_FILE_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 a driver has corrupted pool memory that is used for holding pages destined for disk.
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 4/14/2015 11:20:31 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1CBFD)
Bugcheck code: 0xDE (0x2, 0xFFFFC0008C2C3300, 0xFFFFC0008C2C3201, 0x86B338C0)
Error: POOL_CORRUPTION_IN_FILE_AREA
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a driver has corrupted pool memory that is used for holding pages destined for disk.
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 Tue 4/14/2015 11:13:59 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041415-40984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x4E (0x2, 0xC3726, 0x21EFFF, 0xFFFE)
Error: PFN_LIST_CORRUPT
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 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 Tue 4/14/2015 8:46:07 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041415-23671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x1A (0x402, 0xFFFFC00107B09128, 0x80000000C61E4882, 0xFFFFC00107B09029)
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 4/12/2015 11:13:10 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041215-29078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0xA (0x20, 0x2, 0x0, 0xFFFFF803337805C3)
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 4/14/2015 11:20:31 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041415-27328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0xDE (0x2, 0xFFFFC0008C2C3300, 0xFFFFC0008C2C3201, 0x86B338C0)
Error: POOL_CORRUPTION_IN_FILE_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 a driver has corrupted pool memory that is used for holding pages destined for disk.
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 4/14/2015 11:20:31 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1CBFD)
Bugcheck code: 0xDE (0x2, 0xFFFFC0008C2C3300, 0xFFFFC0008C2C3201, 0x86B338C0)
Error: POOL_CORRUPTION_IN_FILE_AREA
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a driver has corrupted pool memory that is used for holding pages destined for disk.
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 Tue 4/14/2015 11:13:59 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041415-40984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x4E (0x2, 0xC3726, 0x21EFFF, 0xFFFE)
Error: PFN_LIST_CORRUPT
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 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 Tue 4/14/2015 8:46:07 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041415-23671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x1A (0x402, 0xFFFFC00107B09128, 0x80000000C61E4882, 0xFFFFC00107B09029)
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 4/12/2015 11:13:10 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041215-29078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0xA (0x20, 0x2, 0x0, 0xFFFFF803337805C3)
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.
Last edited:
My Computer
System One
-
- OS
- windows 8.1
