Windows 10: Friend's desktop BSOD - 0x139 ntkrnlmp.exe

Discus and support Friend's desktop BSOD - 0x139 ntkrnlmp.exe in Windows 10 BSOD Crashes and Debugging to solve the problem; An online friend of mine has been getting BSODs for half a year now and I asked for the minidump files. Looking at the most recent one (it was the only... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by FizzyBubblech, Aug 17, 2016.

  1. Friend's desktop BSOD - 0x139 ntkrnlmp.exe


    An online friend of mine has been getting BSODs for half a year now and I asked for the minidump files. Looking at the most recent one (it was the only file he had in his minidumps folder) in WinDBG I get the following:

    Code: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 139, {3, ffffc10069c7f780, ffffc10069c7f6d8, 0} Probably caused by : ntkrnlmp.exe ( nt!KiFastFailDispatch+d0 )[/quote] Code: kd> !thread THREAD ffff960400ac9400 Cid 1bac.4890 Teb: 000000000033b000 Win32Thread: ffff9603feabdac0 RUNNING on processor 2 Not impersonating GetUlongFromAddress: unable to read from fffff8026497c924 Owning Process ffff9603efe9e080 Image: game.bin Attached Process N/A Image: N/A fffff78000000000: Unable to get shared data Wait Start TickCount 14920749 Context Switch Count 4852731 IdealProcessor: 1 ReadMemory error: Cannot get nt!KeMaximumIncrement value. UserTime 00:00:00.000 KernelTime 00:00:00.000 Win32 Start Address 0x00000000005023d5 Stack Init ffffc10069c7fc10 Current ffffc10069c7f900 Base ffffc10069c80000 Limit ffffc10069c79000 Call 0000000000000000 Priority 11 BasePriority 8 PriorityDecrement 2 IoPriority 2 PagePriority 5 Child-SP RetAddr : Args to Child : Call Site ffffc100`69c7f458 fffff802`647db129 : 00000000`00000139 00000000`00000003 ffffc100`69c7f780 ffffc100`69c7f6d8 : nt!KeBugCheckEx ffffc100`69c7f460 fffff802`647db490 : 00000000`8000e00c 00000000`00000000 ffff2047`f7e2dcfb ffffc100`69c7f830 : nt!KiBugCheckDispatch+0x69 ffffc100`69c7f5a0 fffff802`647da473 : ffff9603`fe6f7748 00000000`00000001 ffff9603`f944e010 fffff802`64a86b34 : nt!KiFastFailDispatch+0xd0 ffffc100`69c7f780 fffff802`647f121e : ffff9604`00ac9400 ffff9603`fe6f7700 0012019f`00000000 ffffc100`69c7fb01 : nt!KiRaiseSecurityCheckFailure+0xf3 (TrapFrame @ ffffc100`69c7f780) ffffc100`69c7f910 fffff802`646b7ba4 : ffff9603`fa69a370 00000000`00000000 00000000`00000000 00000000`00000003 : nt! ?? ::FNODOBFM::`string'+0x1205e ffffc100`69c7f970 fffff802`64b5e6c8 : ffffc100`69c7fa28 00000000`00000000 ffffc100`69c7fb00 00000000`00000003 : nt!KeReleaseSemaphore+0x114 ffffc100`69c7f9f0 fffff802`647dac93 : ffff9604`00ac9400 00000000`530c7cf0 00000000`00000000 00000000`0033b001 : nt!NtReleaseSemaphore+0x98 ffffc100`69c7fa80 00000000`530b222c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 (TrapFrame @ ffffc100`69c7fa80) 00000000`0009ef68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x530b222c[/quote] Code: ffffc100`69c7f3b8 fffff807`23aa45b0*** WARNING: Unable to verify timestamp for Wdf01000.sys *** ERROR: Module load completed but symbols could not be loaded for Wdf01000.sys Wdf01000+0xa45b0[/quote] Code: ffffc100`69c7fa48 ffff93b9`3564bddd*** WARNING: Unable to verify timestamp for win32kfull.sys *** ERROR: Module load completed but symbols could not be loaded for win32kfull.sys win32kfull+0x4bddd[/quote] Code: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KERNEL_SECURITY_CHECK_FAILURE (139) A kernel component has corrupted a critical data structure. The corruption could potentially allow a malicious user to gain control of this machine. Arguments: Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove). Arg2: ffffc10069c7f780, Address of the trap frame for the exception that caused the bugcheck Arg3: ffffc10069c7f6d8, Address of the exception record for the exception that caused the bugcheck Arg4: 0000000000000000, Reserved Debugging Details: ------------------ DUMP_CLASS: 1 DUMP_QUALIFIER: 400 BUILD_VERSION_STRING: 10.0.14393.0 (rs1_release.160715-1616) SYSTEM_MANUFACTURER: System manufacturer SYSTEM_PRODUCT_NAME: System Product Name SYSTEM_SKU: SKU SYSTEM_VERSION: System Version BIOS_VENDOR: American Megatrends Inc. BIOS_VERSION: 1801 BIOS_DATE: 03/24/2016 BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC. BASEBOARD_PRODUCT: Z170-A BASEBOARD_VERSION: Rev 1.xx DUMP_TYPE: 2 BUGCHECK_P1: 3 BUGCHECK_P2: ffffc10069c7f780 BUGCHECK_P3: ffffc10069c7f6d8 BUGCHECK_P4: 0 TRAP_FRAME: ffffc10069c7f780 -- (.trap 0xffffc10069c7f780) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=ffff9603ff0c18d8 rbx=0000000000000000 rcx=0000000000000003 rdx=ffff9603f723e8d8 rsi=0000000000000000 rdi=0000000000000000 rip=fffff802647f121e rsp=ffffc10069c7f910 rbp=ffffc10054c40180 r8=0000000000000000 r9=0000000000000000 r10=fffff80264b5e600 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe cy nt! ?? ::FNODOBFM::`string'+0x1205e: fffff802`647f121e cd29 int 29h Resetting default scope EXCEPTION_RECORD: ffffc10069c7f6d8 -- (.exr 0xffffc10069c7f6d8) ExceptionAddress: fffff802647f121e (nt! ?? ::FNODOBFM::`string'+0x000000000001205e) ExceptionCode: c0000409 (Security check failure or stack buffer overrun) ExceptionFlags: 00000001 NumberParameters: 1 Parameter[0]: 0000000000000003 Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY CPU_COUNT: 4 CPU_MHZ: db0 CPU_VENDOR: GenuineIntel CPU_FAMILY: 6 CPU_MODEL: 5e CPU_STEPPING: 3 CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: 74'00000000 (cache) 74'00000000 (init) CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: LIST_ENTRY_CORRUPT BUGCHECK_STR: 0x139 PROCESS_NAME: game.bin CURRENT_IRQL: 2 ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application. EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application. EXCEPTION_CODE_STR: c0000409 EXCEPTION_PARAMETER1: 0000000000000003 ANALYSIS_SESSION_HOST: DESKTOP-53APAMQ ANALYSIS_SESSION_TIME: 08-18-2016 23:47:55.0574 ANALYSIS_VERSION: 10.0.14321.1024 amd64fre LAST_CONTROL_TRANSFER: from fffff802647db129 to fffff802647cff90 STACK_TEXT: ffffc100`69c7f458 fffff802`647db129 : 00000000`00000139 00000000`00000003 ffffc100`69c7f780 ffffc100`69c7f6d8 : nt!KeBugCheckEx ffffc100`69c7f460 fffff802`647db490 : 00000000`8000e00c 00000000`00000000 ffff2047`f7e2dcfb ffffc100`69c7f830 : nt!KiBugCheckDispatch+0x69 ffffc100`69c7f5a0 fffff802`647da473 : ffff9603`fe6f7748 00000000`00000001 ffff9603`f944e010 fffff802`64a86b34 : nt!KiFastFailDispatch+0xd0 ffffc100`69c7f780 fffff802`647f121e : ffff9604`00ac9400 ffff9603`fe6f7700 0012019f`00000000 ffffc100`69c7fb01 : nt!KiRaiseSecurityCheckFailure+0xf3 ffffc100`69c7f910 fffff802`646b7ba4 : ffff9603`fa69a370 00000000`00000000 00000000`00000000 00000000`00000003 : nt! ?? ::FNODOBFM::`string'+0x1205e ffffc100`69c7f970 fffff802`64b5e6c8 : ffffc100`69c7fa28 00000000`00000000 ffffc100`69c7fb00 00000000`00000003 : nt!KeReleaseSemaphore+0x114 ffffc100`69c7f9f0 fffff802`647dac93 : ffff9604`00ac9400 00000000`530c7cf0 00000000`00000000 00000000`0033b001 : nt!NtReleaseSemaphore+0x98 ffffc100`69c7fa80 00000000`530b222c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0009ef68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x530b222c STACK_COMMAND: kb THREAD_SHA1_HASH_MOD_FUNC: 7b1b1b678c193293d57e31051cdfc86482a154c8 THREAD_SHA1_HASH_MOD_FUNC_OFFSET: f1f42a15c3b1873086e7b45d6c7c55af090ccd17 THREAD_SHA1_HASH_MOD: cb5f414824c2521bcc505eaa03e92fa10922dad8 FOLLOWUP_IP: nt!KiFastFailDispatch+d0 fffff802`647db490 c644242000 mov byte ptr [rsp+20h],0 FAULT_INSTR_CODE: 202444c6 SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: nt!KiFastFailDispatch+d0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 578998f1 IMAGE_VERSION: 10.0.14393.0 BUCKET_ID_FUNC_OFFSET: d0 FAILURE_BUCKET_ID: 0x139_3_nt!KiFastFailDispatch BUCKET_ID: 0x139_3_nt!KiFastFailDispatch PRIMARY_PROBLEM_CLASS: 0x139_3_nt!KiFastFailDispatch TARGET_TIME: 2016-08-18T13:54:27.000Z OSBUILD: 14393 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-07-16 10:16:17 BUILDDATESTAMP_STR: 160715-1616 BUILDLAB_STR: rs1_release BUILDOSVER_STR: 10.0.14393.0 ANALYSIS_SESSION_ELAPSED_TIME: 12ffc ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x139_3_nt!kifastfaildispatch FAILURE_ID_HASH: {36173680-6f08-995f-065a-3d368c996911}[/quote] All drivers are updated according to him.

    Here's the dump I requested from him: Attachment 96815

    :)
     
    FizzyBubblech, Aug 17, 2016
    #1
  2. skydean Win User

    BSOD cause by ntkrnlmp.exe

    Hi Sumit,

    here the minidumps file.

    BSOD by ntkrnlmp.exe

    122117-13890-01.dmp

    122117-14796-01.dmp

    many thanks for replying
     
    skydean, Aug 17, 2016
    #2
  3. Jccm668 Win User
    Win 10 BSOD 0x139

    Hi

    Getting the BSOD

    ried to analyze the dumps myself but couldn't get anything specific from them due to lack of experience. So now I am updating drivers on my system but I fear the problem would be with something I am missing.

    Here you can find couple of latest crash dumps:

    091917-14703-01.dmp

    i have my drivers updated

    Assistance is much appreciated.

    Who Crashed

    On Tue 19/09/2017 11:41:39 p. m. your computer crashed

    This was probably caused by the following module: ntoskrnl.exe (nt+0x141F80)

    Error: KERNEL_SECURITY_CHECK_FAILURE

    file path: C:\Windows\system32\ntoskrnl.exe

    product: Microsoft® Windows® Operating System

    company: Microsoft Corporation

    description: NT Kernel & System
     
    Jccm668, Aug 17, 2016
    #3
  4. Friend's desktop BSOD - 0x139 ntkrnlmp.exe

    Hello.

    You can recommend to your for friend to do these steps:


    • Use the event log to see if there are higher level events that occur leading up to this stop code.
    • If you recently added hardware to the system, try removing or replacing it. Or check with the manufacturer to see if any patches are available.
    • If new device drivers or system services have been added recently, try removing or updating them. Try to determine what changed in the system that caused the new bug check code to appear.
    • Check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing the error. For more information, see Open Event Viewer. Look for critical errors in the system log that occurred in the same time window as the blue screen.
    • Look in Device Manager to see if any devices are marked with the exclamation point (!). Review the events log displayed in driver properties for any faulting driver. Try updating the related driver.
    • Run a virus detection program. Viruses can infect all types of hard disks formatted for Windows, and resulting disk corruption can generate system bug check codes. Make sure the virus detection program checks the Master Boot Record for infections.

    Also in the dump file it says that the process that was running when this BSOD happened was game.bin. Does your friend play an outdated game maybe?
     
    BorisTheAnimal, Aug 18, 2016
    #4
  5. axe0 New Member
    Hi FizzyBubblech,

    Welcome to the 10forums *Smile

    Let your friend try the following to see if system stability improves *Smile
    1. Remove all overclocking, RAM, CPU, GPU, while troubleshooting.
    2. Remove Daemon Tools, a program using drivers known for causing instability on Windows.
    3. Remove all ASUS programs while troubleshooting, most of them are known for causing BSODs but we cannot risk the others to be causing problems.
    4. Uninstall Driver Booster 3 and installed drivers (if any)
    5. Check ASUS for BIOS updates
    6. Check the SSD for firmware updates

    Please remove / disable items from the startup in taskmanager
    These programs could interfere with the boot process giving you trouble and increase the boot time.


    Friend's desktop BSOD - 0x139 ntkrnlmp.exe [​IMG]
    Warning Programs that claim to update your drivers install either the wrong or corrupted drivers.
    If you have installed any driver with Driver Booster 3, please remove them as it may cause trouble.
    An easy way to get remove these drivers is by using a restore point prior the installation.



    What has your online friend tried in this half year?
     
  6. Hi, and thanks for the replies!

    I just talked to him earlier and I got this:
    • He has tried turning off overclock, still got BSOD
    • He's gonna let me know if it still crashes once he removes Daemon
    • He replaced the processor, motherboard and RAM after he got the crashes and he still gets them. His SSD is also brand new and with a relatively new install of Windows on it
    • Driver Booster was installed only a few weeks ago and he got crashes way before installing any drivers
    • NVIDIA driver was cleanly installed
    • He tried running Twin Sagas (game.bin) again and the BSOD didn't happen, it seems to occur randomly

    To summarize again, he got crashes on his previous system and replaced his processor, RAM, and motherboard along with a new SSD. Crashes still occur, and at random.

    I've suggested removing Daemon and a few drivers and to send to me any new minidumps if he gets another BSOD.

    I'll post it here once I get it, cheers!
     
    FizzyBubblech, Aug 18, 2016
    #6
  7. axe0 New Member
    Driver update programs such as Driver Booster can make the current problem worse and add many other problems like
    • system freezes,
    • application errors,
    • performance issues,
    • etc.
    It is why I suggest to remove it and all installed drivers by this program.
     
    axe0, Apr 5, 2018
    #7
Thema:

Friend's desktop BSOD - 0x139 ntkrnlmp.exe

Loading...
  1. Friend's desktop BSOD - 0x139 ntkrnlmp.exe - Similar Threads - Friend's desktop BSOD

  2. Random BSOD ntoskrnl, ntkrnlmp executables

    in Windows 10 BSOD Crashes and Debugging
    Random BSOD ntoskrnl, ntkrnlmp executables: I have a Lenovo laptop with the following specs: Intel Core i7-8550U 4C / 8T, 1.8 / 4.0GHz, 8MB Integrated Intel UHD Graphics 620 Intel SoC Platform 16GB Soldered DDR4-2400 512GB SSD M.2 2280 PCIe NVMe 13.9" UHD 3840x2160 IPS 300nits Glossy I started getting random...
  3. 0xa0 and 0x139 BSOD's

    in Windows 10 BSOD Crashes and Debugging
    0xa0 and 0x139 BSOD's: Hello, I have a pesky BSOD problem. I've tried to deal with it by flashing BIOS, removing and updating graphics, network and sound card drivers. I've also changed hibernation file size to 100% and did memory diagnostic. Still my system was crashing even when left alone with...
  4. Windows 10 - BSOD from KERNEL_SECURITY_CHECK_FAILURE (Bugcheck Code: 0x139)

    in Windows 10 BSOD Crashes and Debugging
    Windows 10 - BSOD from KERNEL_SECURITY_CHECK_FAILURE (Bugcheck Code: 0x139): My laptop has been experiencing BSODs for about a month, and I'm not sure where it's coming from. I've tried doing a re-install of Windows 10 on my laptop and even performed a complete factory reset on it to see no success. I've also played around with some drivers by...
  5. Bugcheck BSOD 0x139 Kernel Security Check Failure

    in Windows 10 BSOD Crashes and Debugging
    Bugcheck BSOD 0x139 Kernel Security Check Failure: I've been suffering from this BSOD for months now, and its getting real annoying. The BSOD just happens out of nowhere and I am often forced to do a hard reset of the computer because the automatic restart bugs out on me. I have already run sfc scannow, as well as several...
  6. BSOD ntoskrnl.exe (nt+0x16C580) 0x139 0x1E, 0xFFFFF8017685BA40

    in Windows 10 BSOD Crashes and Debugging
    BSOD ntoskrnl.exe (nt+0x16C580) 0x139 0x1E, 0xFFFFF8017685BA40: Please take a look at the log and attached files! BSOD happened while computer was almost IDLE (but downloading in background). ntoskrnl.exe (nt+0x16C580) Bugcheck code: 0x139 (0x1E, 0xFFFFF8017685BA40, 0xFFFFF8017685B998, 0x0) crash dump file:...
  7. BSOD appearing randomly, error 0x122 0x124 and 0x139

    in Windows 10 BSOD Crashes and Debugging
    BSOD appearing randomly, error 0x122 0x124 and 0x139: So, I built my dad a computer specs are as follows: cpu: i5-6500 mobo: gigabyte ga z170-d3h (bios version f2) gpu: asus strix gtx 950 ram: pny anarchy 2400 2x8gb ddr4 (they are colored blue) psu: it's a seasonic 620 watt, not sure exactly which one, can find out if...
  8. BSOD - 0x139 during gaming

    in Windows 10 BSOD Crashes and Debugging
    BSOD - 0x139 during gaming: Hi! I've had this problem since I bought my PC back in November 2015. Mostly BSODs but can also completely freeze and reboot without any BSOD or dump, the only pattern I can find is that it happens during gaming. 49161
  9. 0x139 BSODs daily when waking up from sleep

    in Windows 10 BSOD Crashes and Debugging
    0x139 BSODs daily when waking up from sleep: Hello and thank you in advance for your assistance, if you have any. I'm open to any suggestions at this point. See my DM files attached at the bottom of this post. This is my Dell Inspiron 13 7359. The problem started about a week ago; 0x139 KERNEL_SECURITY_CHECK_FAILURE....
  10. BSOD - 0x139 KERNEL_SECURITY_CHECK_FAILURE

    in Windows 10 BSOD Crashes and Debugging
    BSOD - 0x139 KERNEL_SECURITY_CHECK_FAILURE: Hello, I assembled my desktop several weeks ago, and got several BSOD per day. After a fresh reinstall, I still got problems... Thanks for your help *Smile 46221