Windows 10: Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+225b0

Hi Guys,

When booting Windows 10 I am presented with a BSOD, when using the debugging tools to look at the dump files this error is coming out all the time.

Any ideas? - Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+225b0 )

It's a new build so any help much appreciated. Weirdly once the system is up and running there is no problems, always occurs the same time on boot, have tried new SSD with a fresh install of Windows 10.

:)

 

Frequently BSOD KMODE_EXCEPTION_NOT_HANDLED 0x0000001e

Hi, I've already used winDbg to debug the dmp file. And I get the information that "

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+29f8e )

"

And i searched about the ntkrnlmp.exe but didn't find any useful information.

I don't know what should I do next... Check the hardware or check the drivers ?

I really need help. The BSOD is so frequently. I could get a BSOD even if I start the OS no more than ten minutes.

Here is the dmp files: Minidump.zip

 

2 Different BSOD w/ Dump Files

BugCheck 50, {fffff9014a75b500, 0, fffff960197c73ba, 2}

Could not read faulting driver name

Probably caused by : memory corruption

------------------------------------------------------------------------------------

BugCheck A, {38, 2, 0, fffff801ae38abf2}

Probably caused by : memory corruption ( nt!MiResolvePageFileFault+6ca )

------------------------------------------------------------------------------------

BugCheck 18, {ffffe0016e55a980, ffffe0016fe355a0, 1, 2d}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+92c0 )

------------------------------------------------------------------------------------

If you overclocked something set to DEFAULT

Run Memtest and video memory test more hours.Download Memtest86 Free Edition - MajorGeeks

Download Video Memory Stress Test - MajorGeeks

Update the Drivers.

Regards.

 

Have attached the ZIP files.

 

Also got this when I looked at more detailed information:



Microsoft (R) Windows Debugger Version 10.0.10586.567 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.




Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.


Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10586.17.amd64fre.th2_release.151121-2308
Machine Name:
Kernel base = 0xfffff800`2bc90000 PsLoadedModuleList = 0xfffff800`2bf6ec70
Debug session time: Tue Jan 12 22:26:49.653 2016 (UTC + 0:00)
System Uptime: 0 days 1:40:03.275
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000067`a3199018). Type ".hh dbgerr001" for details
Loading unloaded module list
..................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************


Use !analyze -v to get detailed debugging information.


BugCheck 1E, {ffffffffc0000005, fffff8002bdd7f47, 0, ffffffffffffffff}


Page 1180 not present in the dump file. Type ".hh dbgerr004" for details
Page 1180 not present in the dump file. Type ".hh dbgerr004" for details
Page 1180 not present in the dump file. Type ".hh dbgerr004" for details
Page 1180 not present in the dump file. Type ".hh dbgerr004" for details
Page 1180 not present in the dump file. Type ".hh dbgerr004" for details
Page 1180 not present in the dump file. Type ".hh dbgerr004" for details
Page 1180 not present in the dump file. Type ".hh dbgerr004" for details
Page 1180 not present in the dump file. Type ".hh dbgerr004" for details
Page 1180 not present in the dump file. Type ".hh dbgerr004" for details
Page 1180 not present in the dump file. Type ".hh dbgerr004" for details
Page 1180 not present in the dump file. Type ".hh dbgerr004" for details
Page 1180 not present in the dump file. Type ".hh dbgerr004" for details
Page 1180 not present in the dump file. Type ".hh dbgerr004" for details
Page 1180 not present in the dump file. Type ".hh dbgerr004" for details
Page 1180 not present in the dump file. Type ".hh dbgerr004" for details
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+225b0 )


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


1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************


KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8002bdd7f47, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception


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


Page 1180 not present in the dump file. Type ".hh dbgerr004" for details
Page 1180 not present in the dump file. Type ".hh dbgerr004" for details
Page 1180 not present in the dump file. Type ".hh dbgerr004" for details
Page 1180 not present in the dump file. Type ".hh dbgerr004" for details
Page 1180 not present in the dump file. Type ".hh dbgerr004" for details
Page 1180 not present in the dump file. Type ".hh dbgerr004" for details
Page 1180 not present in the dump file. Type ".hh dbgerr004" for details
Page 1180 not present in the dump file. Type ".hh dbgerr004" for details
Page 1180 not present in the dump file. Type ".hh dbgerr004" for details
Page 1180 not present in the dump file. Type ".hh dbgerr004" for details
Page 1180 not present in the dump file. Type ".hh dbgerr004" for details
Page 1180 not present in the dump file. Type ".hh dbgerr004" for details
Page 1180 not present in the dump file. Type ".hh dbgerr004" for details
Page 1180 not present in the dump file. Type ".hh dbgerr004" for details
Page 1180 not present in the dump file. Type ".hh dbgerr004" for details


DUMP_CLASS: 1


DUMP_QUALIFIER: 401


BUILD_VERSION_STRING: 10586.17.amd64fre.th2_release.151121-2308


SYSTEM_MANUFACTURER: MSI


SYSTEM_PRODUCT_NAME: MS-7978


SYSTEM_SKU: Default string


SYSTEM_VERSION: 2.0


BIOS_VENDOR: American Megatrends Inc.


BIOS_VERSION: C.30


BIOS_DATE: 12/18/2015


BASEBOARD_MANUFACTURER: MSI


BASEBOARD_PRODUCT: H170 GAMING M3 (MS-7978)


BASEBOARD_VERSION: 2.0


DUMP_TYPE: 1


BUGCHECK_P1: ffffffffc0000005


BUGCHECK_P2: fffff8002bdd7f47


BUGCHECK_P3: 0


BUGCHECK_P4: ffffffffffffffff


READ_ADDRESS: ffffffffffffffff


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.


FAULTING_IP:
nt!ExpInterlockedPopEntrySListFault+0
fffff800`2bdd7f47 498b08 mov rcx,qword ptr [r8]


EXCEPTION_PARAMETER2: ffffffffffffffff


BUGCHECK_STR: 0x1E_c0000005_R


CPU_COUNT: 4


CPU_MHZ: cf0


CPU_VENDOR: GenuineIntel


CPU_FAMILY: 6


CPU_MODEL: 5e


CPU_STEPPING: 3


CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: 55'00000000 (cache) 55'00000000 (init)


DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT


PROCESS_NAME: MsMpEng.exe


CURRENT_IRQL: 2


ANALYSIS_SESSION_HOST: DESKTOP-D9IJ2NR


ANALYSIS_SESSION_TIME: 01-12-2016 22:44:25.0788


ANALYSIS_VERSION: 10.0.10586.567 amd64fre


LAST_CONTROL_TRANSFER: from fffff8002be036b0 to fffff8002bdd2760


STACK_TEXT:
ffffd000`249a29a8 fffff800`2be036b0 : 00000000`0000001e ffffffff`c0000005 fffff800`2bdd7f47 00000000`00000000 : nt!KeBugCheckEx
ffffd000`249a29b0 fffff800`2bddd3c2 : ffffe000`3402f010 ffffe000`3402f010 ffffe000`30829590 ffffe000`3402f2db : nt! ?? ::FNODOBFM::`string'+0x225b0
ffffd000`249a3090 fffff800`2bddb87d : ffffd000`249a3410 00000000`00008000 ffffe000`31357600 ffffc000`d4398010 : nt!KiExceptionDispatch+0xc2
ffffd000`249a3270 fffff800`2bdd7f47 : 00000000`00000022 fffff800`2bcf179a 00000000`21d07041 fffffa80`04e48600 : nt!KiGeneralProtectionFault+0xfd
ffffd000`249a3400 fffff800`2bcf179a : 00000000`21d07041 fffffa80`04e48600 ffffe000`345ba190 00000000`00000000 : nt!ExpInterlockedPopEntrySListFault
ffffd000`249a3410 fffff800`2bcf15da : 00000000`00000000 00000000`00000022 ffffe000`33bc5580 00000000`00000220 : nt!MiGetFreeOrZeroPage+0xea
ffffd000`249a3480 fffff800`2bced993 : fffff800`2bf8cbc0 fffff800`00000000 e000348f`508804c0 ffffc000`00000001 : nt!MiGetPage+0x7a
ffffd000`249a34f0 fffff800`2bd28d16 : ffffe000`345ba190 fffffa80`03455a30 ffffc000`cd265d60 fffff800`2bf8cbc0 : nt!MiBuildMdlForMappedFileFault+0xf3
ffffd000`249a3580 fffff800`2bcce1ef : 0000021d`07051ff0 00000000`00000006 ffffe000`33bc5580 fffffa80`03455a30 : nt!MiResolveMappedFileFault+0x2b6
ffffd000`249a3680 fffff800`2bccb519 : e000348f`508804c0 0000021d`07051ff0 fffff681`0e838288 ffffe000`33bc5580 : nt!MiResolveProtoPteFault+0x79f
ffffd000`249a3730 fffff800`2bcc8e9f : ffffffff`00000420 0000021d`07051ff0 ffff8000`00000000 fffff800`00000000 : nt!MiDispatchFault+0x3a9
ffffd000`249a3890 fffff800`2bddb9bc : ffffe000`336b3080 00000000`00000000 ffffe000`348d2060 ffffe000`348d2060 : nt!MmAccessFault+0x34f
ffffd000`249a3a00 00007ffe`6cef3cc0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x13c
00000067`a3d7cc08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`6cef3cc0




STACK_COMMAND: kb


THREAD_SHA1_HASH_MOD_FUNC: d21235489dc272e20ee10552d6084fbdf9f22c71


THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 8d546285b5108b5a162518e4b49c3bbd9a3f9bcf


THREAD_SHA1_HASH_MOD: fe34192f63d13620a8987d294372ee74d699cfee


FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+225b0
fffff800`2be036b0 cc int 3


FAULT_INSTR_CODE: 7886f7cc


SYMBOL_STACK_INDEX: 1


SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+225b0


FOLLOWUP_NAME: MachineOwner


MODULE_NAME: nt


IMAGE_NAME: ntkrnlmp.exe


DEBUG_FLR_IMAGE_TIMESTAMP: 565189c8


BUCKET_ID_FUNC_OFFSET: 225b0


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


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


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


TARGET_TIME: 2016-01-12T22:26:49.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: 2015-11-22 09:24:24


BUILDDATESTAMP_STR: 151121-2308


BUILDLAB_STR: th2_release


BUILDOSVER_STR: 10.0.10586.17.amd64fre.th2_release.151121-2308


ANALYSIS_SESSION_ELAPSED_TIME: eed


ANALYSIS_SOURCE: KM


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


FAILURE_ID_HASH: {8fc04943-cbe8-d7c5-c06f-9b7efeebfcb7}


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