New
#1
Random BSOD Stop Codes Looks like ntoskrnl.exe?
Attachment 180987
Logs attached and here is the WhoCrashed Report below, as well. This crash keeps happening every 20 to 30 minutes. I recently updated my Bios and a network driver a couple of days ago.
System Information (local)
Computer name: X
Windows version: Windows 10 , 10.0, build: 16299
Windows dir: C:\WINDOWS
Hardware: Intel Corporation, NUC7i7BNB
CPU: GenuineIntel Intel(R) Core(TM) i7-7567U CPU @ 3.50GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 17024200704 bytes total
Crash Dump Analysis
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Thu 3/15/2018 2:27:36 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031518-4562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175510)
Bugcheck code: 0x4E (0x99, 0x18475B, 0x2, 0xA00015FFFFFFFFF)
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 bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 3/15/2018 2:27:36 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!PsChargeProcessNonPagedPoolQuota+0x85A5)
Bugcheck code: 0x4E (0x99, 0x18475B, 0x2, 0xA00015FFFFFFFFF)
Error: PFN_LIST_CORRUPT
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 3/15/2018 2:11:39 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031518-4578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175510)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80339D201EC, 0xFFFFFC8F4FD9EC50, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Thu 3/15/2018 2:01:03 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031518-4093-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175510)
Bugcheck code: 0xA (0x4110, 0x2, 0x0, 0xFFFFF802D07320B3)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 3/15/2018 1:39:09 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031518-4390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175510)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF801B4A14370, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 3/15/2018 1:27:55 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031518-5421-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175510)
Bugcheck code: 0xA (0x5560010, 0x2, 0x1, 0xFFFFF801AF4F888D)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Quote
