Windows 10: BSOD caused by windows feature upgrade 1903 Latitude E7470

Discus and support BSOD caused by windows feature upgrade 1903 Latitude E7470 in Windows 10 Drivers and Hardware to solve the problem; I have a problem I cant really seam to get rid of. Tried updating all driver and bios. Cant seam to find consistency in what causes the BSOD, any... Discussion in 'Windows 10 Drivers and Hardware' started by OCTDK, May 4, 2020.

  1. OCTDK Win User

    BSOD caused by windows feature upgrade 1903 Latitude E7470


    I have a problem I cant really seam to get rid of.
    Tried updating all driver and bios.

    Cant seam to find consistency in what causes the BSOD, any hints would be greatly appreciated.


    ////

    crash dump file: C:\WINDOWS\MEMORY.DMP
    This was probably caused by the following module: ntkrnlmp.exe nt!setjmpex+0x81D9
    Bugcheck code: 0x3B 0xC0000005, 0xFFFFF80327EB588D, 0xFFFFBD8F2A41E9B0, 0x0
    Error: SYSTEM_SERVICE_EXCEPTION
    Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

    /////

    ////.DMP analasys via WinDbg..



    Microsoft R Windows Debugger Version 10.0.18362.1 AMD64
    Copyright c Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Users\punk_\Downloads\Minidump\043020-12421-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: srv*
    Executable search path is:
    Windows 10 Kernel Version 18362 MP 4 procs Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 18362.1.amd64fre.19h1_release.190318-1202
    Machine Name:
    Kernel base = 0xfffff803`27800000 PsLoadedModuleList = 0xfffff803`27c48150
    Debug session time: Thu Apr 30 14:06:03.124 2020 UTC + 2:00
    System Uptime: 0 days 23:08:35.939
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................................................
    ......................................
    Loading User Symbols
    Loading unloaded module list
    ..................................................
    For analysis of this file, run !analyze -v
    0: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    SYSTEM_SERVICE_EXCEPTION 3b
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff80327eb588d, Address of the instruction which caused the bugcheck
    Arg3: ffffbd8f2a41e9b0, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.

    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: 18362.1.amd64fre.19h1_release.190318-1202

    SYSTEM_MANUFACTURER: Dell Inc.

    SYSTEM_PRODUCT_NAME: Latitude E7470

    SYSTEM_SKU: 06DC

    BIOS_VENDOR: Dell Inc.

    BIOS_VERSION: 1.22.8

    BIOS_DATE: 10/08/2019

    BASEBOARD_MANUFACTURER: Dell Inc.

    BASEBOARD_PRODUCT: 0T6HHJ

    BASEBOARD_VERSION: A00

    DUMP_TYPE: 2

    BUGCHECK_P1: c0000005

    BUGCHECK_P2: fffff80327eb588d

    BUGCHECK_P3: ffffbd8f2a41e9b0

    BUGCHECK_P4: 0

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

    FAULTING_IP:
    nt!ObCloseHandleTableEntry+9d
    fffff803`27eb588d 4c8b97a8000000 mov r10,qword ptr [rdi+0A8h]

    CONTEXT: ffffbd8f2a41e9b0 -- .cxr 0xffffbd8f2a41e9b0
    rax=fffff80327800000 rbx=ffffe202a1d78cd0 rcx=00000000000000f3
    rdx=ffffc08b93424a80 rsi=ffffe202a1d78ca0 rdi=0000000000000000
    rip=fffff80327eb588d rsp=ffffbd8f2a41f3a0 rbp=ffffbd8f2a41f489
    r8=ffffe2029e9d8080 r9=ffffe2029e9d8080 r10=0000000000000016
    r11=000000000000019d r12=0000000000000000 r13=00000000000032a0
    r14=ffffc08b93424a80 r15=ffffc08b9564ca00
    iopl=0 nv up ei pl nz na po nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050206
    nt!ObCloseHandleTableEntry+0x9d:
    fffff803`27eb588d 4c8b97a8000000 mov r10,qword ptr [rdi+0A8h] ds:002b:00000000`000000a8=????????????????
    Resetting default scope

    BUGCHECK_STR: 0x3B_c0000005

    CPU_COUNT: 4

    CPU_MHZ: 9c0

    CPU_VENDOR: GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 4e

    CPU_STEPPING: 3

    CPU_MICROCODE: 6,4e,3,0 F,M,S,R SIG: CC'00000000 cache CC'00000000 init

    BLACKBOXBSD: 1 !blackboxbsd


    BLACKBOXNTFS: 1 !blackboxntfs


    BLACKBOXPNP: 1 !blackboxpnp


    BLACKBOXWINLOGON: 1

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    PROCESS_NAME: explorer.exe

    CURRENT_IRQL: 0

    ANALYSIS_SESSION_HOST: xxx

    ANALYSIS_SESSION_TIME: 05-04-2020 11:21:56.0921

    ANALYSIS_VERSION: 10.0.18362.1 amd64fre

    LAST_CONTROL_TRANSFER: from fffff80327df8955 to fffff80327eb588d

    STACK_TEXT:
    ffffbd8f`2a41f3a0 fffff803`27df8955 : 00000000`00000103 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObCloseHandleTableEntry+0x9d
    ffffbd8f`2a41f4e0 fffff803`27e6ac5d : ffffe202`a05983a0 ffffe202`a0598080 ffffffff`ffffff01 ffffe202`9e9d8380 : nt!ExSweepHandleTable+0xd5
    ffffbd8f`2a41f590 fffff803`27dde461 : ffffffff`ffffffff ffffe202`9e9d8080 ffffbd8f`2a41f5e0 ffffc08b`00000000 : nt!ObKillProcess+0x35
    ffffbd8f`2a41f5c0 fffff803`27ed1473 : ffffe202`9e9d8080 ffffc08b`9413b830 ffffbd8f`2a41f7e9 00000000`00000000 : nt!PspRundownSingleProcess+0x131
    ffffbd8f`2a41f640 fffff803`27eced53 : 00000000`40010004 00000000`00000001 00000000`00a44000 00000000`00000000 : nt!PspExitThread+0x60b
    ffffbd8f`2a41f750 fffff803`27916e11 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSchedulerApcTerminate+0x33
    ffffbd8f`2a41f790 fffff803`279c68f0 : 00000000`00000001 ffffbd8f`2a41f850 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x481
    ffffbd8f`2a41f850 fffff803`279d3cbf : ffffe202`a0598080 00000000`02f6f388 ffffe202`00002710 fffff803`00000048 : nt!KiInitiateUserApc+0x70
    ffffbd8f`2a41f990 00007fff`8c329a84 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9f
    00000000`02f6f368 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`8c329a84


    THREAD_SHA1_HASH_MOD_FUNC: 1bce861c5b19a65cdcf08104f477dfbab7487b95

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: ec5c30bffbddf0fdb9246c0543e76e60cf8b6252

    THREAD_SHA1_HASH_MOD: 9f457f347057f10e1df248e166a3e95e6570ecfe

    FOLLOWUP_IP:
    nt!ObCloseHandleTableEntry+9d
    fffff803`27eb588d 4c8b97a8000000 mov r10,qword ptr [rdi+0A8h]

    FAULT_INSTR_CODE: a8978b4c

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nt!ObCloseHandleTableEntry+9d

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 5629d63a

    IMAGE_VERSION: 10.0.18362.778

    STACK_COMMAND: .cxr 0xffffbd8f2a41e9b0 ; kb

    BUCKET_ID_FUNC_OFFSET: 9d

    FAILURE_BUCKET_ID: 0x3B_c0000005_nt!ObCloseHandleTableEntry

    BUCKET_ID: 0x3B_c0000005_nt!ObCloseHandleTableEntry

    PRIMARY_PROBLEM_CLASS: 0x3B_c0000005_nt!ObCloseHandleTableEntry

    TARGET_TIME: 2020-04-30T12:06:03.000Z

    OSBUILD: 18362

    OSSERVICEPACK: 778

    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-10-23 08:39:54

    BUILDDATESTAMP_STR: 190318-1202

    BUILDLAB_STR: 19h1_release

    BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202

    ANALYSIS_SESSION_ELAPSED_TIME: 9884

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:0x3b_c0000005_nt!obclosehandletableentry

    FAILURE_ID_HASH: {6d2b6af8-c878-f9a4-39b8-9f62c5d0ad0d}

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

    :)
     
    OCTDK, May 4, 2020
    #1

  2. Shutdown problems since upgrading to 1903

    I recently installed upgrade 1903 to Windows 10 on my Dell Latitude and to my Surface 3 Professional. Since the upgrade the Dell latitude takes 20 minutes or more to fully shut down. The Surface is running fine. Any suggestions would be appreciated.
     
    RobertAmbrose, May 4, 2020
    #2
  3. Windows Feature Update 1903

    Hi Sara209

    Greetings! I am Vijay, an Independent Advisor. The steps which you have undertaken to block updates won't work for any feature update. Feature updates need to be blocked temporarily by using different steps.

    But, I will suggest that you should not try to stop 1903 feature update. Let it happen.

    Do let me know if you have any more question or require further help.
     
    Vijay_Verma, May 4, 2020
    #3
  4. BSOD caused by windows feature upgrade 1903 Latitude E7470

    BSOD Dell Latitude 3540

    I need help with a BSOD case on two Dell Latitude 3540 notebooks: First, these notebooks showed the blue screen with the message

    so in research I found that the error can be caused by Fast Boot in Windows 10, I deactivated the Fast Boot feature and the machines worked without error for a few days.

    Recently, the machines returned the BSOD error, but the message was changed to

    After this last error, I ran some tests, such as sfc, chkdisk, hardware test using Dell software and no error was detected.

    So can you help me how I solve this problem?

    Thank you.
     
    Tecnologia Matrix, May 4, 2020
    #4
Thema:

BSOD caused by windows feature upgrade 1903 Latitude E7470

Loading...
  1. BSOD caused by windows feature upgrade 1903 Latitude E7470 - Similar Threads - BSOD caused feature

  2. Dell latitude e7470 os recovery.etc etc .

    in Windows 10 Gaming
    Dell latitude e7470 os recovery.etc etc .: Its dell latitude e7470 no os was broke no screen ram ssd . No battery . I have replaced them got dell os download .put it in e7470. Now it says use installation disc with windows. Only usb ports so I'm guessing windows 7 pro .usb from dell . Any help thank you....
  3. Dell latitude e7470 os recovery.etc etc .

    in Windows 10 Software and Apps
    Dell latitude e7470 os recovery.etc etc .: Its dell latitude e7470 no os was broke no screen ram ssd . No battery . I have replaced them got dell os download .put it in e7470. Now it says use installation disc with windows. Only usb ports so I'm guessing windows 7 pro .usb from dell . Any help thank you....
  4. Dell latitude e7470

    in Windows 10 Gaming
    Dell latitude e7470: I bought 2 dell latitude e7470 broken screen no hdd no ssd . Guess no os I got os recovery downloading windows 7 pro 64 from dell but will it work I'm planning on plugging usb in . Then f12 I believe. Not sure I'm a noob. Any help thank you for your time . Plus one e7470 on...
  5. Dell latitude e7470

    in Windows 10 Software and Apps
    Dell latitude e7470: I bought 2 dell latitude e7470 broken screen no hdd no ssd . Guess no os I got os recovery downloading windows 7 pro 64 from dell but will it work I'm planning on plugging usb in . Then f12 I believe. Not sure I'm a noob. Any help thank you for your time . Plus one e7470 on...
  6. My laptop Dell Latitude E7470 Windows Cant Active

    in Windows 10 Updates and Activation
    My laptop Dell Latitude E7470 Windows Cant Active: I buy republished laptop it's come with windows 10 pro, but I can't active it, it says log in with the same account Microsoft account that login before, I buy from this retailer store so I no longer know who uses this laptop before. that screenshot taken from this laptop...
  7. My laptop Dell Latitude E7470 Windows Cant Active

    in Windows 10 Updates and Activation
    My laptop Dell Latitude E7470 Windows Cant Active: [ATTACH] I buy republished laptop next week, Can I active windows? or not possible to active since it republished. ThankQ Everyones https://answers.microsoft.com/en-us/windows/forum/all/my-laptop-dell-latitude-e7470-windows-cant-active/4afe1892-e828-42d3-b886-215d7d79df3a
  8. Feature upgrade to 1903 issue

    in Windows 10 Support
    Feature upgrade to 1903 issue: My Dell Inspiron 5759 laptop started off with an early version of Windows 10 and automatic upgrades have updated it as MS required. I think it was 1809 that started giving me trouble, Windows would load up to the desktop, show the desktop shortcuts, many without icons, no...
  9. Windows 10 1903 causes BSOD

    in Windows 10 BSOD Crashes and Debugging
    Windows 10 1903 causes BSOD: A few months ago after upgrading to Windows 10 1903, I was getting BSOD at a very high frequency (several times a day). They would happen at any moment. I got some on the login screen, when opening the windows menu, when playing games, when browsing the internet, or when...
  10. Win 10 1903 Features Upgrade

    in Windows 10 Installation and Upgrade
    Win 10 1903 Features Upgrade: I downloaded and installed the latest Win 10 - 1903 feature upgrade this morning. 1. I was forced to log back in to much of my gaming software. 2. After the upgrade I was left with a light blue glaring desktop background that had to be deleted, it was just too bright...