BSOD - Ntoskrnl.exe


  1. Posts : 4
    Windows 10 Pro, 64BIT
       #1

    BSOD - Ntoskrnl.exe


    Hello,

    I'm having BSOD on my laptop. Below the link with the logs:
    JFF-NTB-0025-(2019-10-30_13-43-26).zip - Google Drive

    Windows 10 PRO version 1809

    I've reinstalled the drivers from the HP site, but the issue persist.

    Please let me know if any other information is needed.

    Thank you.
    A.
      My Computer


  2. Posts : 1,495
    Windows 8.1 Enterprise x64
       #2

    Update:
    Windows 10 to version 1903 (https://support.microsoft.com/pl-pl/...date-assistant)
    Check SSD with SeaTools (SeaTools for DOS - Hard Drive Diagnostic)
      My Computer


  3. Posts : 4
    Windows 10 Pro, 64BIT
    Thread Starter
       #3

    Hello,

    Is not an option to update Windows 10 to version 1903 (https://support.microsoft.com/pl-pl/...date-assistant)
    Check SSD with SeaTools (SeaTools for DOS - Hard Drive Diagnostic) -> checking the program, seem that SeaTools is an easy-to-use that helps you determine what could be wrong with your machine. This tool works with all hard drives (NOT SSDs). -> i'm using an SSD
      My Computer


  4. Posts : 1,495
    Windows 8.1 Enterprise x64
       #4

    Regarding Windows 10, I would recommend upgrading to version 1903 because it may contain patches for your hardware (including those that solve the BSoD problem)
    As for SSD, I found this for SanDisk - SanDisk SSD Dashboard Support Information
      My Computer


  5. Posts : 4
    Windows 10 Pro, 64BIT
    Thread Starter
       #5

    No error on SSD as you see in the picture Attachment 252927

    Regarding the update to version 1903, is not an option as this is a company computer. They still using 1809. I'm having a colleague with the same computer and version 1809 and doesn't receive BSOD.
      My Computer


  6. Posts : 1,495
    Windows 8.1 Enterprise x64
       #6

    In that case, use Driver Verifier (Enable and Disable Driver Verifier in Windows 10)
      My Computer


  7. Posts : 4
    Windows 10 Pro, 64BIT
    Thread Starter
       #7

    what about the logs that I've added in my first post? Any luck there?:)
      My Computer


  8. Posts : 1,495
    Windows 8.1 Enterprise x64
       #8

    The CRITICAL_PROCESS_DIED bug check has a value of 0x000000EF. This indicates that a critical system process died.
    Code:
    Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\102919-5250-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*
    Symbol search path is: SRV*
    Executable search path is: 
    Windows 10 Kernel Version 17763 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 17763.1.amd64fre.rs5_release.180914-1434
    Machine Name:
    Kernel base = 0xfffff803`312a3000 PsLoadedModuleList = 0xfffff803`316be690
    Debug session time: Tue Oct 29 14:54:41.250 2019 (UTC + 1:00)
    System Uptime: 0 days 6:29:59.813
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................................................
    .................................
    Loading User Symbols
    Loading unloaded module list
    ......................................
    For analysis of this file, run !analyze -v
    3: kd> !analyze
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck EF, {ffffe305a8e5c500, 0, 0, 0}
    
    *** WARNING: Unable to verify timestamp for win32k.sys
    Probably caused by : ntkrnlmp.exe ( nt!PspCatchCriticalBreak+fd )
    
    Followup:     MachineOwner
    ---------
    
    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    CRITICAL_PROCESS_DIED (ef)
            A critical system process died
    Arguments:
    Arg1: ffffe305a8e5c500, Process object or thread object
    Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    
    Debugging Details:
    ------------------
    
    
    KEY_VALUES_STRING: 1
    
    
    PROCESSES_ANALYSIS: 1
    
    SERVICE_ANALYSIS: 1
    
    STACKHASH_ANALYSIS: 1
    
    TIMELINE_ANALYSIS: 1
    
    
    DUMP_CLASS: 1
    
    DUMP_QUALIFIER: 400
    
    BUILD_VERSION_STRING:  17763.1.amd64fre.rs5_release.180914-1434
    
    SYSTEM_MANUFACTURER:  HP
    
    SYSTEM_PRODUCT_NAME:  HP EliteBook 1040 G4
    
    SYSTEM_SKU:  1EP77EA#ABB
    
    BIOS_VENDOR:  HP
    
    BIOS_VERSION:  P96 Ver. 01.29
    
    BIOS_DATE:  07/15/2019
    
    BASEBOARD_MANUFACTURER:  HP
    
    BASEBOARD_PRODUCT:  8417
    
    BASEBOARD_VERSION:  KBC Version 62.54
    
    DUMP_TYPE:  2
    
    BUGCHECK_P1: ffffe305a8e5c500
    
    BUGCHECK_P2: 0
    
    BUGCHECK_P3: 0
    
    BUGCHECK_P4: 0
    
    PROCESS_NAME:  services.exe
    
    CRITICAL_PROCESS:  services.exe
    
    EXCEPTION_RECORD:  0000000000001000 -- (.exr 0x1000)
    Cannot read Exception record @ 0000000000001000
    
    EXCEPTION_CODE: (HRESULT) 0xab866080 (2877710464) - <Unable to get error code text>
    
    ERROR_CODE: (NTSTATUS) 0xab866080 - <Unable to get error code text>
    
    CPU_COUNT: 4
    
    CPU_MHZ: a98
    
    CPU_VENDOR:  GenuineIntel
    
    CPU_FAMILY: 6
    
    CPU_MODEL: 8e
    
    CPU_STEPPING: 9
    
    CPU_MICROCODE: 6,8e,9,0 (F,M,S,R)  SIG: B4'00000000 (cache) B4'00000000 (init)
    
    BLACKBOXBSD: 1 (!blackboxbsd)
    
    
    BLACKBOXPNP: 1 (!blackboxpnp)
    
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    BUGCHECK_STR:  0xEF
    
    CURRENT_IRQL:  0
    
    ANALYSIS_SESSION_HOST:  MICHAL
    
    ANALYSIS_SESSION_TIME:  10-30-2019 15:23:27.0331
    
    ANALYSIS_VERSION: 10.0.18362.1 amd64fre
    
    TRAP_FRAME:  ffff800000000000 -- (.trap 0xffff800000000000)
    Unable to read trap frame at ffff8000`00000000
    
    LAST_CONTROL_TRANSFER:  from fffff80331b2fc8d to fffff80331457050
    
    STACK_TEXT:  
    ffffdb81`eaffec18 fffff803`31b2fc8d : 00000000`000000ef ffffe305`a8e5c500 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
    ffffdb81`eaffec20 fffff803`31a6cf07 : 00000000`00000001 fffff803`313d27e5 ffffe305`a8e5c500 fffff803`313d26e4 : nt!PspCatchCriticalBreak+0xfd
    ffffdb81`eaffecc0 fffff803`3192780c : ffffe305`00000000 00000000`00000000 ffffe305`a8e5c500 ffffe305`a8e5c7d8 : nt!PspTerminateAllThreads+0x146873
    ffffdb81`eaffed30 fffff803`31929349 : ffffffff`ffffffff ffffdb81`eaffee60 ffffe305`a8e5c500 fffff803`31375300 : nt!PspTerminateProcess+0xe0
    ffffdb81`eaffed70 fffff803`31468305 : 00000000`00000218 ffffe305`ab866080 ffffe305`a8e5c500 ffffdb81`eaffefb0 : nt!NtTerminateProcess+0xa9
    ffffdb81`eaffede0 fffff803`3145ad60 : fffff803`31480748 ffffdb81`eafff958 ffffdb81`eafff958 ffffdb81`eaffefb0 : nt!KiSystemServiceCopyEnd+0x25
    ffffdb81`eaffef78 fffff803`31480748 : ffffdb81`eafff958 ffffdb81`eafff958 ffffdb81`eaffefb0 00000000`00047dfd : nt!KiServiceLinkage
    ffffdb81`eaffef80 fffff803`314689c2 : 00000000`00001000 ffffdb81`eafffa00 ffff8000`00000000 000000b1`80100f38 : nt!KiDispatchException+0x1bac68
    ffffdb81`eafff820 fffff803`31464cae : 00000000`00000026 ffffdb81`eafffa80 00007ff6`18f27dfd ffffdb81`eafffa80 : nt!KiExceptionDispatch+0xc2
    ffffdb81`eafffa00 00007ff9`e647481c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x42e
    000000b1`80100e90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`e647481c
    
    
    THREAD_SHA1_HASH_MOD_FUNC:  f6b0f7fafbd5253fc3d42ad0a11af14fddabdcf0
    
    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  b84451654cc11f448e4b9448067c77071f4cfe6e
    
    THREAD_SHA1_HASH_MOD:  bc100a5647b828107ac4e18055e00abcbe1ec406
    
    FOLLOWUP_IP: 
    nt!PspCatchCriticalBreak+fd
    fffff803`31b2fc8d cc              int     3
    
    FAULT_INSTR_CODE:  ed8440cc
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt!PspCatchCriticalBreak+fd
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  320760b6
    
    IMAGE_VERSION:  10.0.17763.802
    
    STACK_COMMAND:  .thread ; .cxr ; kb
    
    BUCKET_ID_FUNC_OFFSET:  fd
    
    FAILURE_BUCKET_ID:  0xEF_services.exe_BUGCHECK_CRITICAL_PROCESS_ab866080_nt!PspCatchCriticalBreak
    
    BUCKET_ID:  0xEF_services.exe_BUGCHECK_CRITICAL_PROCESS_ab866080_nt!PspCatchCriticalBreak
    
    PRIMARY_PROBLEM_CLASS:  0xEF_services.exe_BUGCHECK_CRITICAL_PROCESS_ab866080_nt!PspCatchCriticalBreak
    
    TARGET_TIME:  2019-10-29T13:54:41.000Z
    
    OSBUILD:  17763
    
    OSSERVICEPACK:  802
    
    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:  1996-08-06 17:11:50
    
    BUILDDATESTAMP_STR:  180914-1434
    
    BUILDLAB_STR:  rs5_release
    
    BUILDOSVER_STR:  10.0.17763.1.amd64fre.rs5_release.180914-1434
    
    ANALYSIS_SESSION_ELAPSED_TIME:  67c4
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0xef_services.exe_bugcheck_critical_process_ab866080_nt!pspcatchcriticalbreak
    
    FAILURE_ID_HASH:  {77050d7c-ffe4-f6b0-66c5-aaf48ec9353b}
    
    Followup:     MachineOwner
    ---------
    
    3: kd> .load pde
    =========================================================================================
     PDE v11.3 - Copyright 2017 Andrew Richards
    =========================================================================================
    3: kd> !dpx
    Start memory scan  : 0xffffdb81eaffec18 ($csp)
    End memory scan    : 0xffffdb81eb000000 (Kernel Stack Base)
    
                   rsp : 0xffffdb81eaffec18 : 0xfffff80331b2fc8d : nt!PspCatchCriticalBreak+0xfd
    0xffffdb81eaffec18 : 0xfffff80331b2fc8d : nt!PspCatchCriticalBreak+0xfd
    0xffffdb81eaffec78 : 0xfffff803313ccc64 : nt!EtwTraceKernelEvent+0xa8
    0xffffdb81eaffecc8 : 0xfffff803313d27e5 : nt!EtwTraceProcessTerminate+0x61
    0xffffdb81eaffecd8 : 0xfffff803313d26e4 : nt!KeSetProcessSchedulingGroup+0x5c
    0xffffdb81eaffece8 : 0xfffff80331375189 : nt!ExAcquirePushLockExclusiveEx+0xe9
    0xffffdb81eaffed28 : 0xfffff8033192780c : nt!PspTerminateProcess+0xe0
    0xffffdb81eaffed68 : 0xfffff80331929349 : nt!NtTerminateProcess+0xa9
    0xffffdb81eaffed88 : 0xfffff80331375300 : nt!ExAcquirePushLockSharedEx+0xb0
    0xffffdb81eaffedd8 : 0xfffff80331468305 : nt!KiSystemServiceCopyEnd+0x25
    0xffffdb81eaffef48 : 0xfffff8033145ad60 : nt!KiServiceLinkage
    0xffffdb81eafff730 : 0xfffff803312c5e6b : nt!KiDispatchException+0x38b
    0xffffdb81eafff818 : 0xfffff803314689c2 : nt!KiExceptionDispatch+0xc2
    0xffffdb81eafff9f8 : 0xfffff80331464cae : nt!KiPageFault+0x42e
    0xffffdb81eafffa00 : 0x0000000000000026 :  Trap @ ffffdb81eafffa00
    Well, I can't tell which driver is to blame. The reason is found, but there is no guilty
      My Computer


  9. Posts : 39,994
    windows 10 professional version 1607 build 14393.969 64 bit
       #9

    1) The logs displayed drive problems.

    2) Run HD Tune (free version) (all drives)
    HD Tune website
    Post images into the thread for results on these tabs:
    a) Health
    b) Benchmark
    c) Full error scan

    3) Make a backup image using Macrium
    4) Save the image to another disk drive or to the cloud

    Macrium Software | Your Image is Everything
    Backup and Restore with Macrium Reflect

    5) Open administrative command prompt and type or copy and paste:
    chkdsk /r /v
    This may take hours to run so plan to run overnight.
    Run on all drives using the syntax: chkdsk /r /v C: or chkdsk /r /v D: changing the drive letter to the applicable drive.

    C:\Windows\system32>chkdsk /r /v
    The type of the file system is NTFS.
    Cannot lock current drive.

    Chkdsk cannot run because the volume is in use by another
    process. Would you like to schedule this volume to be
    checked the next time the system restarts? (Y/N)

    Type: Y
    reboot


    6) Use the information in this link to find the chkdsk report in the event viewer. Copy and paste into notepad > save to desktop > post into the thread using one drive or drop box share link:
    Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
    Read Chkdsk Log in Event Viewer in Windows 10


    7) Open administrative command prompt and type or copy and paste:
    8) sfc /scannow
    9) dism /online /cleanup-image /scanhealth
    10) dism /online /cleanup-image /restorehealth
    11) sfc /scannow
    12) wmic recoveros set autoreboot = false
    13) wmic recoveros set DebugInfoType = 7
    14) bcdedit /enum {badmemory}

    15) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

    16) Make sure that there is no over clocking while troubleshooting.

    17) Uninstall Conexant and Intel audio software/drivers
    https://answers.microsoft.com/en-us/...0-8d22254aa1c1

    18) Reinstall from the HP website
    https://support.hp.com/us-en/drivers...ok-pc/11623738

    19) Run HP Hardware diagnostics UEFI extensive tests overnight in loop until failure > the next AM run component tests as needed (some are interactive)
    https://support.hp.com/us-en/drivers...Id/ob-209569-1
    An alternative is to download HP diagnostics UEFI to a flash drive:
    https://www8.hp.com/us/en/campaigns/.../pc-diags.html
      My Computer


 

  Related Discussions
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 01:55.
Find Us




Windows 10 Forums