1.    25 Jan 2016 #1
    Join Date : Jan 2016
    Posts : 1
    Windows 10

    Bsod ntkrnlmp.exe


    Hi, hoping someone can help me narrow down the exact cause of this blue screen. I believe it is something related to the drivers. When plugging in a video camera drop box displayed a message, after clicking okay this blue screen appeared and the computer restarted. I don't have to much more information unfortunately as this issue happened to an employee at my work. Any insight would be great!

    Thank you,

    Code:
    Microsoft (R) Windows Debugger Version 10.0.10586.567 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    Loading Dump File [C:\Users\rpratt\Desktop\MEMORY.DMP]
    Kernel Summary Dump File: Kernel address space is available, User address space may not be available.
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.19110.amd64fre.win7sp1_gdr.151230-0600
    Machine Name:
    Kernel base = 0xfffff800`02a1d000 PsLoadedModuleList = 0xfffff800`02c64730
    Debug session time: Mon Jan 25 10:25:57.501 2016 (UTC - 5:00)
    System Uptime: 0 days 1:37:12.795
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...........................
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 000007ff`fffdc018).  Type ".hh dbgerr001" for details
    Loading unloaded module list
    .........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck F4, {3, fffffa8007a7e520, fffffa8007a7e800, fffff80002d98750}
    Probably caused by : ntkrnlmp.exe ( nt!PspCatchCriticalBreak+92 )
    Followup:     MachineOwner
    ---------
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    CRITICAL_OBJECT_TERMINATION (f4)
    A process or thread crucial to system operation has unexpectedly exited or been
    terminated.
    Several processes and threads are necessary for the operation of the
    system; when they are terminated (for any reason), the system can no
    longer function.
    Arguments:
    Arg1: 0000000000000003, Process
    Arg2: fffffa8007a7e520, Terminating object
    Arg3: fffffa8007a7e800, Process image file name
    Arg4: fffff80002d98750, Explanatory message (ascii)
    Debugging Details:
    ------------------
    
    DUMP_CLASS: 1
    DUMP_QUALIFIER: 401
    BUILD_VERSION_STRING:  7601.19110.amd64fre.win7sp1_gdr.151230-0600
    SYSTEM_MANUFACTURER:  ASUS
    SYSTEM_PRODUCT_NAME:  All Series
    SYSTEM_SKU:  All
    SYSTEM_VERSION:  System Version
    BIOS_VENDOR:  American Megatrends Inc.
    BIOS_VERSION:  1802
    BIOS_DATE:  01/28/2014
    BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.
    BASEBOARD_PRODUCT:  Z87-A
    BASEBOARD_VERSION:  Rev 1.xx
    DUMP_TYPE:  1
    BUGCHECK_P1: 3
    BUGCHECK_P2: fffffa8007a7e520
    BUGCHECK_P3: fffffa8007a7e800
    BUGCHECK_P4: fffff80002d98750
    PROCESS_NAME:  csrss.exe
    CRITICAL_PROCESS:  csrss.exe
    EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
    ERROR_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
    CPU_COUNT: 8
    CPU_MHZ: d4d
    CPU_VENDOR:  GenuineIntel
    CPU_FAMILY: 6
    CPU_MODEL: 3c
    CPU_STEPPING: 3
    CPU_MICROCODE: 6,3c,3,0 (F,M,S,R)  SIG: 1C'00000000 (cache) 12'00000000 (init)
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    BUGCHECK_STR:  0xF4
    CURRENT_IRQL:  0
    ANALYSIS_SESSION_HOST:  WOCGL010
    ANALYSIS_SESSION_TIME:  01-25-2016 11:20:59.0714
    ANALYSIS_VERSION: 10.0.10586.567 amd64fre
    TRAP_FRAME:  fffff880053d8ae0 -- (.trap 0xfffff880053d8ae0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000210 rbx=0000000000000000 rcx=0000000000000630
    rdx=0000000000000421 rsi=0000000000000000 rdi=0000000000000000
    rip=00000000773e8f72 rsp=0000000000381570 rbp=00000000003becc0
     r8=0000000000000210  r9=0000000000000000 r10=00000000774f0010
    r11=000007fefd0fc000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe cy
    0033:00000000`773e8f72 ??              ???
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff80002e27c02 to fffff80002a90c00
    STACK_TEXT:  
    fffff880`053d7e38 fffff800`02e27c02 : 00000000`000000f4 00000000`00000003 fffffa80`07a7e520 fffffa80`07a7e800 : nt!KeBugCheckEx
    fffff880`053d7e40 fffff800`02d4b6ab : ffffffff`ffffffff fffffa80`08424680 fffffa80`07a7e520 fffffa80`07a7e520 : nt!PspCatchCriticalBreak+0x92
    fffff880`053d7e80 fffff800`02d48234 : ffffffff`ffffffff 00000000`00000001 fffffa80`07a7e520 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x29c66
    fffff880`053d7ed0 fffff800`02a8fe93 : fffffa80`07a7e520 fffff800`c0000006 fffffa80`08424680 00000000`00380e40 : nt!NtTerminateProcess+0xf4
    fffff880`053d7f50 fffff800`02a8c450 : fffff800`02b11ae9 fffff880`053d8a38 fffff880`053d8790 fffff880`053d8ae0 : nt!KiSystemServiceCopyEnd+0x13
    fffff880`053d80e8 fffff800`02b11ae9 : fffff880`053d8a38 fffff880`053d8790 fffff880`053d8ae0 00000000`00381b50 : nt!KiServiceLinkage
    fffff880`053d80f0 fffff800`02a90282 : fffff880`053d8a38 00000000`0000d928 fffff880`053d8ae0 00000000`00381628 : nt! ?? ::FNODOBFM::`string'+0x48154
    fffff880`053d8900 fffff800`02a8edfa : 00000000`00000000 000007fe`fd0fd8c0 00000000`00000001 00000000`0000d928 : nt!KiExceptionDispatch+0xc2
    fffff880`053d8ae0 00000000`773e8f72 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
    00000000`00381570 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773e8f72
    
    STACK_COMMAND:  kb
    THREAD_SHA1_HASH_MOD_FUNC:  323fc2762880972d7780d6f3d445163f6549cd8c
    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  db18c5ed0ac59e2698226f7c10c4527946f52eef
    THREAD_SHA1_HASH_MOD:  9f457f347057f10e1df248e166a3e95e6570ecfe
    FOLLOWUP_IP: 
    nt!PspCatchCriticalBreak+92
    fffff800`02e27c02 cc              int     3
    FAULT_INSTR_CODE:  5c8b48cc
    SYMBOL_STACK_INDEX:  1
    SYMBOL_NAME:  nt!PspCatchCriticalBreak+92
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME:  ntkrnlmp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP:  5684191c
    IMAGE_VERSION:  6.1.7601.19110
    FAILURE_BUCKET_ID:  X64_0xF4_csrss.exe_BUGCHECK_CRITICAL_PROCESS_IOERR_nt!PspCatchCriticalBreak+92
    BUCKET_ID:  X64_0xF4_csrss.exe_BUGCHECK_CRITICAL_PROCESS_IOERR_nt!PspCatchCriticalBreak+92
    PRIMARY_PROBLEM_CLASS:  X64_0xF4_csrss.exe_BUGCHECK_CRITICAL_PROCESS_IOERR_nt!PspCatchCriticalBreak+92
    TARGET_TIME:  2016-01-25T15:25:57.000Z
    OSBUILD:  7601
    OSSERVICEPACK:  1000
    SERVICEPACK_NUMBER: 0
    OS_REVISION: 0
    SUITE_MASK:  272
    PRODUCT_TYPE:  1
    OSPLATFORM_TYPE:  x64
    OSNAME:  Windows 7
    OSEDITION:  Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS
    OS_LOCALE:  
    USER_LCID:  0
    OSBUILD_TIMESTAMP:  2015-12-30 12:49:16
    BUILDDATESTAMP_STR:  151230-0600
    BUILDLAB_STR:  win7sp1_gdr
    BUILDOSVER_STR:  6.1.7601.19110.amd64fre.win7sp1_gdr.151230-0600
    ANALYSIS_SESSION_ELAPSED_TIME: 814
    ANALYSIS_SOURCE:  KM
    FAILURE_ID_HASH_STRING:  km:x64_0xf4_csrss.exe_bugcheck_critical_process_ioerr_nt!pspcatchcriticalbreak+92
    FAILURE_ID_HASH:  {8b124c16-87d3-ee13-7e28-497d8bb5f53f}
    Followup:     MachineOwner
    Last edited by Brink; 25 Jan 2016 at 11:46. Reason: code box
      My ComputerSystem Spec
  2.    25 Jan 2016 #2
    Join Date : Jun 2015
    Posts : 12,952
    Windows 10 Pro

    You have the new Windbg version 10.0xxxxxx?

    I would advice you to create a new thread at BSOD Help and Support - Windows 7 Help Forums as it seems you are running Windows 7. The Windows 10 Help Forums is only meant for Windows 10 users.
      My ComputersSystem Spec

 


Similar Threads
Thread Forum
BSOD ntkrnlmp.exe CRITICAL_STRUCTURE_CORRUPTION
I was getting a random reboot about once every 36 hours, this is the 1st time I got a BSOD before rebooting All I was doing when the BSOD hit was listening to music using Spotify I've replaced the power supply and reinstalled windows. I also...
BSOD Crashes and Debugging
BSOD because of ntkrnlmp.exe
Hi, my computer keeps on crashing when playing games and WhoCrashed says the problem is to do with ntkrnlmp.exe. I ran the verifier and the dmp and msinfo are below. dmp: Dropbox - 122215-31218-01.dmp msinfo: Dropbox - msinfo.nfo speccy:...
BSOD Crashes and Debugging
ntkrnlmp.exe bsod windows 10
Hi! I've been getting BSOD for quite som time. i tried to analyse with WhoCrashed, and the message says that it was caused by ntkrnlmp.exe. I dont really know how to fix this problem, so i was hoping annyone could give me a hand. The BSOD...
BSOD Crashes and Debugging
ntkrnlmp.exe bsod windows 10 (again & again & again & again)
Hello everyone, I keep on getting bsod's due to ntkrnlmp.exe in Windows 10 Pro 64 bit. This is the analysis carried out by WhoCrashed. Crash dump directory: C:\WINDOWS\Minidump Crash dumps are enabled on your computer. On Wed...
BSOD Crashes and Debugging
BSOD - ntkrnlmp.exe
Experiencing what appears to be random BSOD events. This has been going on for some time now. I've recently switched from Windows 7 to 10, but the problem followed. Bug check points to ntkrnlmp.exe. An internet search has left...
BSOD Crashes and Debugging
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 05:48.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums