Windows 10: KMODE_EXCEPTION_NOT_HANDLED - No Driver - BSOD - Assistance Needed

Discus and support KMODE_EXCEPTION_NOT_HANDLED - No Driver - BSOD - Assistance Needed in Windows 10 Drivers and Hardware to solve the problem; Hello, I have a Dell Latitude E5470 that was given a fresh image of WIndows 10 about one month ago. I updated the hardware drivers through Dell Command... Discussion in 'Windows 10 Drivers and Hardware' started by Jon_4K, Mar 18, 2019.

  1. JON_4K
    Jon_4K Win User

    KMODE_EXCEPTION_NOT_HANDLED - No Driver - BSOD - Assistance Needed


    Hello, I have a Dell Latitude E5470 that was given a fresh image of WIndows 10 about one month ago. I updated the hardware drivers through Dell Command Update and recently received the following BSOD. I disabled fast start up as I have read that may resolve this particular bsod and all my drivers are up to date. There are also no details of a faulty driver and I am at a loss in making sense of the dump file. Any assistance whatsoever would be appreciated.


    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: fffff801ac6ddde8, The address that the exception occurred at

    Arg3: 0000000000000000, Parameter 0 of the exception

    Arg4: ffffffffffffffff, Parameter 1 of the exception



    Debugging Details:

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





    KEY_VALUES_STRING: 1





    STACKHASH_ANALYSIS: 1



    TIMELINE_ANALYSIS: 1





    DUMP_CLASS: 1



    DUMP_QUALIFIER: 400



    BUILD_VERSION_STRING: 15063.0.amd64fre.rs2_release.170317-1834



    SYSTEM_MANUFACTURER: Dell Inc.



    SYSTEM_PRODUCT_NAME: Latitude E5470



    SYSTEM_SKU: 06DE



    BIOS_VENDOR: Dell Inc.



    BIOS_VERSION: 1.19.3



    BIOS_DATE: 08/20/2018



    BASEBOARD_MANUFACTURER: Dell Inc.



    BASEBOARD_PRODUCT: 0VHKV0



    BASEBOARD_VERSION: A00



    DUMP_TYPE: 2



    BUGCHECK_P1: ffffffffc0000005



    BUGCHECK_P2: fffff801ac6ddde8



    BUGCHECK_P3: 0



    BUGCHECK_P4: ffffffffffffffff



    READ_ADDRESS: fffff801aca61358: Unable to get MiVisibleState

    Unable to get NonPagedPoolStart

    Unable to get NonPagedPoolEnd

    Unable to get PagedPoolStart

    Unable to get PagedPoolEnd

    ffffffffffffffff



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



    FAULTING_IP:

    nt!IopGetFileObjectExtension+18

    fffff801`ac6ddde8 488b54c808 mov rdx,qword ptr [rax+rcx*8+8]



    EXCEPTION_PARAMETER2: ffffffffffffffff



    BUGCHECK_STR: 0x1E_c0000005_R



    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: C6'00000000 (cache) C6'00000000 (init)



    BLACKBOXBSD: 1 (!blackboxbsd)





    CUSTOMER_CRASH_COUNT: 1



    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT



    PROCESS_NAME: explorer.exe



    CURRENT_IRQL: 0



    ANALYSIS_SESSION_HOST: DAL2F663M2



    ANALYSIS_SESSION_TIME: 03-18-2019 11:02:31.0740



    ANALYSIS_VERSION: 10.0.17763.132 amd64fre



    EXCEPTION_RECORD: ffffcd8312e1d050 -- (.exr 0xffffcd8312e1d050)

    ExceptionAddress: 00000000000f8dff

    ExceptionCode: 72657355

    ExceptionFlags: 00203233

    NumberParameters: 667102

    Parameter[0]: 00000000000a2de1

    Parameter[1]: 7fffffffffffffff

    Parameter[2]: ffffa304acfd3660

    Parameter[3]: 00000000000a2ded

    Parameter[4]: 0000000402880000

    Parameter[5]: 0000000000800000

    Parameter[6]: 0000000000800000

    Parameter[7]: 0000000000000000

    Parameter[8]: 0000000000000000

    Parameter[9]: 0000000000000000

    Parameter[10]: 0001000000000000

    Parameter[11]: 0000004500000001

    Parameter[12]: 00000b4000000000

    Parameter[13]: 0000000000001000

    Parameter[14]: 0000000000000000



    LAST_CONTROL_TRANSFER: from fffff801ac6aab7c to fffff801ac7ec4c0



    STACK_TEXT:

    ffffe081`cc707b98 fffff801`ac6aab7c : 00000000`0000001e ffffffff`c0000005 fffff801`ac6ddde8 00000000`00000000 : nt!KeBugCheckEx

    ffffe081`cc707ba0 fffff801`ac7f798e : ffffcd83`12e1d050 ffffe081`cc7086c8 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x23c

    ffffe081`cc708250 fffff801`ac7f5c34 : 00000000`ffffffff 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xce

    ffffe081`cc708430 fffff801`ac6ddde8 : fffff801`ac745bb0 00000000`30000000 00000000`00000000 fffff801`aad49460 : nt!KiGeneralProtectionFault+0xf4

    ffffe081`cc7085c8 fffff801`ac745bb0 : 00000000`30000000 00000000`00000000 fffff801`aad49460 fffff801`ac8ff4b0 : nt!IopGetFileObjectExtension+0x18

    ffffe081`cc7085d0 fffff801`ac74593b : 00000000`00000000 ffffe081`cc708621 ffffe081`cc70862a fffff800`0de55b2f : nt!IoGetOplockKeyContextEx+0x10

    ffffe081`cc708600 fffff801`ac7443cd : ffffcd83`1642ecb0 ffffa304`aa56e8b0 00000000`00000000 ffffcd83`1c012d50 : nt!FsRtlpOplockKeysEqual+0x5f

    ffffe081`cc708630 fffff801`acb5d455 : 00000000`00000600 ffffa304`aa56edb8 ffffa304`30000000 ffffa304`00010000 : nt!FsRtlpRequestShareableOplock+0x50d

    ffffe081`cc7086e0 fffff801`acb5d184 : ffffcd83`13d9e1a8 ffffcd83`1c012d50 00000000`00000002 00000000`00000000 : nt!FsRtlpOplockFsctrlInternal+0x2a9

    ffffe081`cc708780 fffff800`0de569a7 : ffffa304`aa56edb8 00000000`00000002 ffffa304`00000002 ffffcd83`13d9e150 : nt!FsRtlOplockFsctrl+0x14

    ffffe081`cc7087c0 fffff800`0de54439 : ffffa304`b19c2018 ffffa304`aa56edb8 ffffe081`dc644100 ffffcd83`13d9e420 : NTFS!NtfsOpenAttribute+0x817

    ffffe081`cc7088d0 fffff800`0de53adc : ffffe081`dc644170 00000000`00000001 ffffcd83`13d9e420 ffffcd83`0000006c : NTFS!NtfsOpenExistingAttr+0x1f9

    ffffe081`cc708990 fffff800`0de52d15 : ffffe081`dc644170 ffffa304`aa56e8b0 ffffcd83`13d9e420 ffffe081`0000006c : NTFS!NtfsOpenAttributeInExistingFile+0x13c

    ffffe081`cc708b70 fffff800`0de27245 : ffffa304`b19c2018 00000000`00000001 ffffcd83`13d9e420 00000000`00000000 : NTFS!NtfsOpenExistingPrefixFcb+0x1e5

    ffffe081`cc708c50 fffff800`0de27ff7 : ffffa304`b19c2018 ffffa304`aa56e8b0 00000000`00000000 ffffe081`cc708e80 : NTFS!NtfsFindStartingNode+0x465

    ffffe081`cc708d10 fffff800`0de26d9d : ffffa304`b19c2018 ffffa304`aa56e8b0 ffffe081`dc644170 ffffa304`af193700 : NTFS!NtfsCommonCreate+0x487

    ffffe081`cc708f50 fffff801`ac7ef377 : ffffe081`dc644100 00000000`00000000 00000000`00000000 00000000`00000000 : NTFS!NtfsCommonCreateCallout+0x1d

    ffffe081`cc708f80 fffff801`ac7ef33d : 00000000`00000012 ffffa304`b6b12080 ffffe081`cc709000 fffff801`ac6964ac : nt!KxSwitchKernelStackCallout+0x27

    ffffe081`dc643f20 fffff801`ac6964ac : fffff800`00000012 00000000`00000000 fffff800`0db82b88 00000000`00000007 : nt!KiSwitchKernelStackContinue

    ffffe081`dc643f40 fffff801`ac6962ee : 00000000`00000005 00000000`00006000 00000000`00000000 ffffe081`dc643fc0 : nt!KiExpandKernelStackAndCalloutOnStackSegment+0x12c

    ffffe081`dc643fc0 fffff801`ac6961af : 00000000`00000008 ffffe081`dc644100 00000000`00000001 ffffa304`aa56e8b0 : nt!KiExpandKernelStackAndCalloutSwitchStack+0x9e

    ffffe081`dc644030 fffff800`0de2b4ab : 00000000`00000000 00000000`00000000 ffffa304`b19c2018 ffffa304`aa56e8b0 : nt!KeExpandKernelStackAndCalloutInternal+0x2f

    ffffe081`dc644080 fffff800`0ca0563d : ffffa304`9da4d030 ffffa304`aa56e8b0 ffffa304`aa56ee00 fffff800`0ca26060 : NTFS!NtfsFsdCreate+0x1cb

    ffffe081`dc6442d0 fffff800`0ca3612b : ffffe081`dc644380 ffffa304`aa56ee00 ffffe081`dc644408 ffffa304`acfd36c0 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x18d

    ffffe081`dc644340 fffff801`acb17265 : 00000000`00000000 00000000`00000085 ffffa304`a51e78d0 ffffa304`00000000 : FLTMGR!FltpCreate+0x2eb

    ffffe081`dc6443f0 fffff801`acb2261b : fffff801`acb16a50 fffff801`acb16a50 ffffe081`00000000 ffffa304`a51d8ac0 : nt!IopParseDevice+0x815

    ffffe081`dc6445d0 fffff801`acb26150 : ffffa304`b1715900 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObpLookupObjectName+0x46b

    ffffe081`dc6447a0 fffff801`acb2a0ca : 00000000`00000001 ffffa304`b3101bb0 00000000`60cdd018 00000000`00000000 : nt!ObOpenObjectByNameEx+0x1e0

    ffffe081`dc6448e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopCreateFile+0x3aa





    THREAD_SHA1_HASH_MOD_FUNC: 179939b95f136a08fa19c9bc01927c0c27d5819f



    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: c8c456ced9472337bfc16ca5eec333bd7ea2bb7c



    THREAD_SHA1_HASH_MOD: fd24fc30b080b2156184e12dc20d6400d45d0a4c



    FOLLOWUP_IP:

    nt!IopGetFileObjectExtension+18

    fffff801`ac6ddde8 488b54c808 mov rdx,qword ptr [rax+rcx*8+8]



    FAULT_INSTR_CODE: c8548b48



    SYMBOL_STACK_INDEX: 4



    SYMBOL_NAME: nt!IopGetFileObjectExtension+18



    FOLLOWUP_NAME: MachineOwner



    MODULE_NAME: nt



    IMAGE_NAME: ntkrnlmp.exe



    DEBUG_FLR_IMAGE_TIMESTAMP: 595f24eb



    IMAGE_VERSION: 10.0.15063.483



    STACK_COMMAND: .thread ; .cxr ; kb



    BUCKET_ID_FUNC_OFFSET: 18



    FAILURE_BUCKET_ID: 0x1E_c0000005_R_nt!IopGetFileObjectExtension



    BUCKET_ID: 0x1E_c0000005_R_nt!IopGetFileObjectExtension



    PRIMARY_PROBLEM_CLASS: 0x1E_c0000005_R_nt!IopGetFileObjectExtension



    TARGET_TIME: 2019-03-11T21:46:32.000Z



    OSBUILD: 15063



    OSSERVICEPACK: 483



    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: 2017-07-07 01:06:35



    BUILDDATESTAMP_STR: 170317-1834



    BUILDLAB_STR: rs2_release



    BUILDOSVER_STR: 10.0.15063.0.amd64fre.rs2_release.170317-1834



    ANALYSIS_SESSION_ELAPSED_TIME: 249d



    ANALYSIS_SOURCE: KM



    FAILURE_ID_HASH_STRING: km:0x1e_c0000005_r_nt!iopgetfileobjectextension



    FAILURE_ID_HASH: {f4e1f65b-04ce-4baf-56fa-236e70cc3e1d}



    Followup: MachineOwner

    :)
     
    Jon_4K, Mar 18, 2019
    #1
  2. SANGEETA SARKAR
    Sangeeta Sarkar Win User

    BSOD - KMODE_EXCEPTION_NOT_HANDLED

    Hello Nathan,

    We realize the inconvenience you are experiencing with frequent BSOD after upgrading to Windows 10. We will certainly help you.

    The KMODE_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000001E. This indicates that a kernel-mode program generated an exception which the error handler did not catch

    Blue screens (BSOD) is mostly occur due to hardware and sometimes due to incompatible software. In a lot of cases it is a corrupted driver or a driver conflict. The most common causes of blue screens are overheating, faulty RAM,
    and video card problem.

    We suggest you to follow the steps from the links below and check if it helps:

    Troubleshoot blue screen errors

    How to troubleshoot blue screen errors in Windows 10

    Let us know the results. We will be happy to assist you further.

    Thank you.
     
    Sangeeta Sarkar, Mar 18, 2019
    #2
  3. ASWIN_ANAND
    Aswin_Anand Win User
    Kmode_exception_not_handled BSOD in Windows 10

    Hi Lucas,



    Thank you for posting your query in Microsoft Community. I regret the inconvenience caused to you. Let me help you.




    • When did the BSOD screen appeared?

    • Have you made any changes in settings or installed any third party software prior to the issue?


    I would suggest you to refer to the troubleshooting steps suggested by
    Babu V     in the link below and check if it helps:

    How to troubleshoot blue screen
    errors in Windows 10

    For more information regarding this error code, you can refer to the link below:

    Bug Check 0x1E: KMODE_EXCEPTION_NOT_HANDLED

    Check if it helps.



    If you need any further assistance, please feel free to contact us again. We will be happy to assist you further.
     
    Aswin_Anand, Mar 18, 2019
    #3
  4. CARING1
    Caring1 Win User

    KMODE_EXCEPTION_NOT_HANDLED - No Driver - BSOD - Assistance Needed

    BSOD KMODE_EXCEPTION_NOT_HANDLED

    Not CPU drivers sorry, I can't think at the moment, it's 3am here *Laugh :laugh: and I am off to bed finally.
    They should be listed on the motherboard site under Intel in the driver downloads.
     
    Caring1, Mar 18, 2019
    #4
Thema:

KMODE_EXCEPTION_NOT_HANDLED - No Driver - BSOD - Assistance Needed

Loading...

  1. KMODE_EXCEPTION_NOT_HANDLED - No Driver - BSOD - Assistance Needed - Similar Threads - KMODE_EXCEPTION_NOT_HANDLED Driver BSOD

  2. Need assistance with BSOD

    in Windows 10 Gaming
    Need assistance with BSOD: Hello,I've tried to fix this issue myself, but it has been futile. Any help would be greatly appreciated.The culprit seems to be fwpkclnt.sysI have attached a file with the dmp file as well as system information.Thanks in...

  3. Need assistance with BSOD

    in Windows 10 Software and Apps
    Need assistance with BSOD: Hello,I've tried to fix this issue myself, but it has been futile. Any help would be greatly appreciated.The culprit seems to be fwpkclnt.sysI have attached a file with the dmp file as well as system information.Thanks in...

  4. Need assistance with BSoDs.

    in Windows 10 Software and Apps
    Need assistance with BSoDs.: I have recently been getting Blue Screen Errors consistently. In order of what happened over the time: KERNAL_SECURITY_CHECK_FAILURE, UNEXPECTED_KERNAL_MODE_TRAP, IRQL_NOT_LESS_OR_EQUAL. This occured once on 02/26/2023, and twice on 02/28/2023, in order of the errors above. I...

  5. Need assistance with BSoDs.

    in Windows 10 BSOD Crashes and Debugging
    Need assistance with BSoDs.: I have recently been getting Blue Screen Errors consistently. In order of what happened over the time: KERNAL_SECURITY_CHECK_FAILURE, UNEXPECTED_KERNAL_MODE_TRAP, IRQL_NOT_LESS_OR_EQUAL. This occured once on 02/26/2023, and twice on 02/28/2023, in order of the errors above. I...

  6. Need assistance with BSoDs.

    in Windows 10 Gaming
    Need assistance with BSoDs.: I have recently been getting Blue Screen Errors consistently. In order of what happened over the time: KERNAL_SECURITY_CHECK_FAILURE, UNEXPECTED_KERNAL_MODE_TRAP, IRQL_NOT_LESS_OR_EQUAL. This occured once on 02/26/2023, and twice on 02/28/2023, in order of the errors above. I...

  7. HELP NEEDED BSOD - KMODE_EXCEPTION_NOT_HANDLED

    in Windows 10 Gaming
    HELP NEEDED BSOD - KMODE_EXCEPTION_NOT_HANDLED: Even after reinstalling windows 11 on my laptop, it still manages to blue screen. After around 15 minutes of using the newly installed windows, it blue screens with the error stating KMODE_EXCEPTION_NOT_HANDLED.Google Drive Dump File:...

  8. HELP NEEDED BSOD - KMODE_EXCEPTION_NOT_HANDLED

    in Windows 10 Software and Apps
    HELP NEEDED BSOD - KMODE_EXCEPTION_NOT_HANDLED: Even after reinstalling windows 11 on my laptop, it still manages to blue screen. After around 15 minutes of using the newly installed windows, it blue screens with the error stating KMODE_EXCEPTION_NOT_HANDLED.Google Drive Dump File:...

  9. KMODE_EXCEPTION_NOT_HANDLED without any driver listed in the BSOD

    in Windows 10 BSOD Crashes and Debugging
    KMODE_EXCEPTION_NOT_HANDLED without any driver listed in the BSOD: Ok so since July I've been getting lots of bsod out of nowhere, and i mean a lot, i get around 7 to 8 everyday since that date, and i have no idea what causing this, i didn't make any changes to my system at all prior to that day, i've done so many researching and going...

  10. BSOD KMODE_EXCEPTION_NOT_HANDLED

    in Windows 10 BSOD Crashes and Debugging
    BSOD KMODE_EXCEPTION_NOT_HANDLED: Ah yes, the blue screen of death. The last time I saw this beast was when i accidentally updated my BIOS. Very nasty. I don't know when it started. Basically, around 7 minutes after the computer turns on and I login in, regardless of what i'm doing, the blue screen pops. Not...
  1. DAYTONA6752
    Thread

    Windows 10 BSOD after update, kmode_exception_not_handled, tried all troubleshooting found

    Hi There, completely stumped with troubleshooting. Hope someone here can provide some insight. Please see below for all troubleshooting I have...
    Thread by: daytona6752, Feb 14, 2021, 3 replies, in forum: Windows 10 BSOD Crashes and Debugging
  2. MAURICIOFX
    Thread

    KMODE_EXCEPTION_NOT_HANDLED

    Hi, I am having this error since when i Installed W10, right after the installation i began to have this error, then going after this tool i saw...
    Thread by: MauricioFX, Feb 7, 2021, 3 replies, in forum: Windows 10 BSOD Crashes and Debugging
  3. RICHARD WITTEMAN
    Thread

    BSOD KMODE_EXCEPTION_NOT_HANDLED 1e

    A friend gets BSOD all the time after reboot in 1~10 min. The memory dump file gives the following information. I dont know how to pinpoint witch...
    Thread by: Richard Witteman, Feb 7, 2021, 3 replies, in forum: Windows 10 BSOD Crashes and Debugging
  4. CYMLINE87
    Thread

    KMODE_EXCEPTION_NOT_HANDLED on startup

    windows 10 20h2 19042.746 As of now, I get this blue screen on initial startup, it does a scan and restart then it boots into windows correctly....
    Thread by: cymline87, Feb 2, 2021, 3 replies, in forum: Windows 10 BSOD Crashes and Debugging
  5. SILVERHAWK20
    Thread

    IRQL_NOT_LESS_OR_EQUAL and kmode_exception_not_handled BSOD on a new laptop

    Hi! I bought a Lenovo Idepad Gaming 3 laptop with a dedicated Nvidia GTX 1650ti video card 2 weeks ago and have been dealing with multiple...
    Thread by: SilverHawk20, Feb 1, 2021, 3 replies, in forum: Windows 10 BSOD Crashes and Debugging
Tags:

Users found this page by searching for:

  1. km:0x1e_c0000005_r_fltmgr