Hello everyone,
I have recently purchased a laptop and have been getting random BSOD's a couple of times over the past 2 weeks. First it was "memory management", then "pfn list corrupt", and today it came up with "page fault in nonpaged area".
I ran a memtest and it came out clean. I ran Blue Screen View and WhoCrashed, reports attached. I updated all the drivers after purchase so I can't determine what could be causing the crash. Any help would be greatly appreciated & thank you in advance!
System Information (local)
--------------------------------------------------------------------------------
Windows version: Windows 8.1 , 6.3, build: 9600
Windows dir: C:\Windows
Hardware: NC-E5-571G-59C1, Acer, Type2 - Board Product Name1
CPU: GenuineIntel Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4205133824 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 28-Dec-15 9:53:25 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122815-28906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E8A0)
Bugcheck code: 0x50 (0xFFFFF6BFFE226D70, 0x0, 0xFFFFF801646CD9F2, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_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 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 Mon 28-Dec-15 9:53:25 AM 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: 0x50 (0xFFFFF6BFFE226D70, 0x0, 0xFFFFF801646CD9F2, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 Fri 25-Dec-15 1:57:12 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122515-35546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E8A0)
Bugcheck code: 0x4E (0x99, 0x12335F, 0x3, 0x80000000004839B)
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 15-Dec-15 2:34:50 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\121515-33546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E8A0)
Bugcheck code: 0x1A (0x41201, 0xFFFFF680419BFDF0, 0xD110000030636867, 0xFFFFE00045FD01B0)
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.
I have recently purchased a laptop and have been getting random BSOD's a couple of times over the past 2 weeks. First it was "memory management", then "pfn list corrupt", and today it came up with "page fault in nonpaged area".
I ran a memtest and it came out clean. I ran Blue Screen View and WhoCrashed, reports attached. I updated all the drivers after purchase so I can't determine what could be causing the crash. Any help would be greatly appreciated & thank you in advance!
System Information (local)
--------------------------------------------------------------------------------
Windows version: Windows 8.1 , 6.3, build: 9600
Windows dir: C:\Windows
Hardware: NC-E5-571G-59C1, Acer, Type2 - Board Product Name1
CPU: GenuineIntel Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4205133824 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 28-Dec-15 9:53:25 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122815-28906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E8A0)
Bugcheck code: 0x50 (0xFFFFF6BFFE226D70, 0x0, 0xFFFFF801646CD9F2, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_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 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 Mon 28-Dec-15 9:53:25 AM 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: 0x50 (0xFFFFF6BFFE226D70, 0x0, 0xFFFFF801646CD9F2, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 Fri 25-Dec-15 1:57:12 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122515-35546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E8A0)
Bugcheck code: 0x4E (0x99, 0x12335F, 0x3, 0x80000000004839B)
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 15-Dec-15 2:34:50 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\121515-33546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E8A0)
Bugcheck code: 0x1A (0x41201, 0xFFFFF680419BFDF0, 0xD110000030636867, 0xFFFFE00045FD01B0)
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.