BSOD PFN_LIST_CORRUPT Dumpfile

Kann wer das Dumpfile entschlüsseln?

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000002, A list entry was corrupt
Arg2: 0000000000178c0c, entry in list being removed
Arg3: 000000000021efff, highest physical page number
Arg4: 0000000000000001, reference count of entry being removed

Debugging Details:
------------------


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10586.306.amd64fre.th2_release_sec.160422-1850

SYSTEM_MANUFACTURER: MSI

SYSTEM_PRODUCT_NAME: MS-7917

SYSTEM_SKU: To be filled by O.E.M.

SYSTEM_VERSION: 1.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: V1.13

BIOS_DATE: 02/16/2016

BASEBOARD_MANUFACTURER: MSI

BASEBOARD_PRODUCT: Z97 GAMING 5 (MS-7917)

BASEBOARD_VERSION: 1.0

DUMP_TYPE: 2

BUGCHECK_P1: 2

BUGCHECK_P2: 178c0c

BUGCHECK_P3: 21efff

BUGCHECK_P4: 1

BUGCHECK_STR: 0x4E_2

CPU_COUNT: 8

CPU_MHZ: fa0

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R) SIG: 1E'00000000 (cache) 1E'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: MicrosoftEdgeC

CURRENT_IRQL: 2

ANALYSIS_SESSION_HOST: DESKTOP-HG1PNNN

ANALYSIS_SESSION_TIME: 05-26-2016 01:28:17.0793

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

LAST_CONTROL_TRANSFER: from fffff801a898edb4 to fffff801a895e780

STACK_TEXT:
ffffd000`223f26b8 fffff801`a898edb4 : 00000000`0000004e 00000000`00000002 00000000`00178c0c 00000000`0021efff : nt!KeBugCheckEx
ffffd000`223f26c0 fffff801`a8836386 : fffffa80`046a4240 fffffa80`00000000 00000000`00000000 ffffe000`fa84e580 : nt! ?? ::FNODOBFM::`string'+0x21cb4
ffffd000`223f2780 fffff801`a888a23a : 00000000`00000000 000001ff`2c47db00 fffff680`ff9623e8 ffffe000`fa84e580 : nt!MiResolveTransitionFault+0x1b6
ffffd000`223f2840 fffff801`a888737b : b0800001`78c0c824 000001ff`2c47db00 00000000`00000000 fffff801`00000000 : nt!MiDispatchFault+0xb7a
ffffd000`223f29a0 fffff801`a89679bc : ffffe000`fdec86c0 000001f7`062a0c60 00000000`00000000 ffffe000`ff4e45b0 : nt!MmAccessFault+0x34b
ffffd000`223f2b00 00007ffc`38742904 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x13c
0000001f`7ef3fa00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`38742904


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: e782e291de85ceb9a0b6577363fb2444449f0a0f

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 2a1238a71d0ebc4988510429a6e87fb3accd649b

THREAD_SHA1_HASH_MOD: ee8fcf1fb60cb6e3e2f60ddbed2ec02b5748a693

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+21cb4
fffff801`a898edb4 cc int 3

FAULT_INSTR_CODE: fa8b4ccc

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+21cb4

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 571af445

IMAGE_VERSION: 10.0.10586.306

BUCKET_ID_FUNC_OFFSET: 21cb4

FAILURE_BUCKET_ID: 0x4E_2_nt!_??_::FNODOBFM::_string_

BUCKET_ID: 0x4E_2_nt!_??_::FNODOBFM::_string_

PRIMARY_PROBLEM_CLASS: 0x4E_2_nt!_??_::FNODOBFM::_string_

TARGET_TIME: 2016-05-25T21:17:53.000Z

OSBUILD: 10586

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2016-04-23 06:04:21

BUILDDATESTAMP_STR: 160422-1850

BUILDLAB_STR: th2_release_sec

BUILDOSVER_STR: 10.0.10586.306.amd64fre.th2_release_sec.160422-1850

ANALYSIS_SESSION_ELAPSED_TIME: 717

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x4e_2_nt!_??_::fnodobfm::_string_

FAILURE_ID_HASH: {671accad-0815-551a-02ba-7ab2c5ff32b5}

Followup: MachineOwner
---------

Tja und genau da ist das Problem: Weder HDD noch SSD oder Ram sind defekt.