New
#1
PFN_LIST_CORRUPT 0x4E (0x99, 0x253353, 0x0, 0x153B54)
I've been having various BSODs for a couple of months. PFN_LIST_CORRUPT is only the latest one. Others include KMODE_EXCEPTION_NOT_HANDLED and MEMORY_MANAGEMENT. I am lead to believe there is a faulty driver causing all these problems.
I am hoping someone may be able to help analyse the minidump and tell me which driver is causing problems.
minidump files:
https://my.mixtape.moe/frzgme.dmp
https://my.mixtape.moe/lfvpoz.dmp
Attached BlueScreenView analysis
Attached DM log
WHO Crashed analysis:
Code:On Tue 07/08/2018 18:39:35 GMT your computer crashed crash dump file: C:\Windows\Minidump\080718-49764-01.dmp This was probably caused by the following module: unknown_module_00000000`000e000c.sys (Unloaded_Unknown_Module_00000000`000e000c+0x1FAA35) Bugcheck code: 0x4E (0x99, 0x253353, 0x0, 0x153B54) 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: unknown_module_00000000`000e000c.sys . Google query: unknown_module_00000000`000e000c.sys PFN_LIST_CORRUPT On Tue 07/08/2018 18:39:35 GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: ntkrnlmp.exe (nt!KeRemoveQueueEx+0x1839) Bugcheck code: 0x4E (0x99, 0x253353, 0x0, 0x153B54) 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. 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 16/07/2018 18:03:36 GMT your computer crashed crash dump file: C:\Windows\Minidump\071618-41652-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70180) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003862E51, 0x0, 0xFFFFFFFFFFFFFFFF) Error: KMODE_EXCEPTION_NOT_HANDLED 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 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.
Quote