Windows 10: windows stop code 0x0000001e

Discus and support windows stop code 0x0000001e in Windows 10 BSOD Crashes and Debugging to solve the problem; Hello Microsoft, I had this blue screen with windows stop code 0x0000001e I only had this occurred once when i clean dust of my pc with compressed... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Badr Eddine NeoIbn Yahia, Jul 26, 2018.

  1. BADR EDDINE NEOIBN YAHIA
    Badr Eddine NeoIbn Yahia Win User

    windows stop code 0x0000001e


    Hello Microsoft,

    I had this blue screen with windows stop code 0x0000001e

    I only had this occurred once when i clean dust of my pc with compressed air but i didn't touch anything and i didn't remove any hardware

    I have a Alienware Aurora R4 with Windows 10

    I opened memory.dmp with Windbg and this is the result


    Microsoft (R) Windows Debugger Version 10.0.17712.1000 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Users\Neo\Desktop\MEMORY.DMP]
    Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.


    ************* Path validation summary **************
    Response Time (ms) Location
    Deferred srv*
    Symbol search path is: srv*
    Executable search path is:
    Windows 10 Kernel Version 17134 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 17134.1.amd64fre.rs4_release.180410-1804
    Machine Name:
    Kernel base = 0xfffff802`0549f000 PsLoadedModuleList = 0xfffff802`058591f0
    Debug session time: Thu Jul 26 11:43:52.719 2018 (UTC + 1:00)
    System Uptime: 0 days 0:00:03.469
    Loading Kernel Symbols
    ...............................................................
    ...............................................................
    Loading User Symbols
    PEB address is NULL !
    Loading unloaded module list
    ....
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use     !analyze -v to get detailed debugging information.

    BugCheck 1E, {ffffffffc0000005, fffff802059ccc49, 0, ffffffffffffffff}

    Probably caused by : ntkrnlmp.exe ( nt!CmpGetNameControlBlock+129 )

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

    nt!KeBugCheckEx:
    fffff802`05637430 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff387`c9f859f0=000000000000001e
    2: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    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: fffff802059ccc49, 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: 401

    BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804

    SYSTEM_MANUFACTURER: Alienware

    SYSTEM_PRODUCT_NAME: Aurora-R4

    SYSTEM_SKU: Aurora-R4

    SYSTEM_VERSION: 00

    BIOS_VENDOR: Alienware

    BIOS_VERSION: A11

    BIOS_DATE: 11/26/2013

    BASEBOARD_MANUFACTURER: Alienware

    BASEBOARD_PRODUCT: 07JNH0

    BASEBOARD_VERSION: A00

    DUMP_TYPE: 1

    BUGCHECK_P1: ffffffffc0000005

    BUGCHECK_P2: fffff802059ccc49

    BUGCHECK_P3: 0

    BUGCHECK_P4: ffffffffffffffff

    READ_ADDRESS: ffffffffffffffff

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

    FAULTING_IP:
    nt!CmpGetNameControlBlock+129
    fffff802`059ccc49 413b18 cmp ebx,dword ptr [r8]

    EXCEPTION_PARAMETER2: ffffffffffffffff

    BUGCHECK_STR: 0x1E_c0000005_R

    CPU_COUNT: 8

    CPU_MHZ: e10

    CPU_VENDOR: GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 2d

    CPU_STEPPING: 7

    CPU_MICROCODE: 6,2d,7,0 (F,M,S,R) SIG: 710'00000000 (cache) 710'00000000 (init)

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    PROCESS_NAME: Registry

    CURRENT_IRQL: 0

    ANALYSIS_SESSION_HOST: ALIENWARE-AUROR

    ANALYSIS_SESSION_TIME: 07-26-2018 13:44:56.0718

    ANALYSIS_VERSION: 10.0.17712.1000 amd64fre

    LAST_CONTROL_TRANSFER: from fffff802054f82bd to fffff80205637430

    STACK_TEXT:
    fffff387`c9f859e8 fffff802`054f82bd : 00000000`0000001e ffffffff`c0000005 fffff802`059ccc49 00000000`00000000 : nt!KeBugCheckEx
    fffff387`c9f859f0 fffff802`05648042 : 00000000`00000000 fffff802`055234cc 00020410`c9f86400 00000000`4463bf70 : nt!KiDispatchException+0x58d
    fffff387`c9f860a0 fffff802`0564479c : ffffbf81`0d71a320 fffff802`05793b56 00000000`00000003 00000000`00000001 : nt!KiExceptionDispatch+0xc2
    fffff387`c9f86280 fffff802`059ccc49 : 00000000`0c1d8bed fffff802`00000000 ffffaf89`00000002 00000000`00000001 : nt!KiGeneralProtectionFault+0x2dc
    fffff387`c9f86410 fffff802`059cc5fe : fffff387`c9f868f0 ffff8188`0c1d8bed 005c0073`00650063 005c0073`0065005b : nt!CmpGetNameControlBlock+0x129
    fffff387`c9f86490 fffff802`059cc1c6 : 00000000`ffffffff 00000000`cbbb88c4 00000000`00000000 00000000`00000000 : nt!CmpCreateKeyControlBlock+0x14e
    fffff387`c9f86500 fffff802`0599dd34 : ffff8188`44bb5be8 fffff387`c9f867f0 fffff387`c9f86748 fffff387`c9f86810 : nt!CmpWalkOneLevel+0x5c6
    fffff387`c9f86600 fffff802`05994e1d : 00000000`0000001c fffff387`c9f86a90 fffff387`c9f86a48 00000000`00000000 : nt!CmpDoParseKey+0x1414
    fffff387`c9f869d0 fffff802`0599b3eb : ffffaf89`97c453e0 ffff8188`446df001 00000000`00000000 fffff387`c9f87100 : nt!CmpParseKey+0x26d
    fffff387`c9f86bb0 fffff802`059ace5f : ffffaf89`97c45220 fffff387`c9f86e28 ffff8188`00000240 ffffaf89`97d77e00 : nt!ObpLookupObjectName+0x73b
    fffff387`c9f86d90 fffff802`059acb08 : 00000000`00000001 ffffaf89`97d77e00 00000000`00000000 00000000`00000000 : nt!ObOpenObjectByNameEx+0x1df
    fffff387`c9f86ed0 fffff802`059a917a : ffff8188`451f3c90 00000000`00000000 00000000`00000000 00000000`0000007a : nt!CmOpenKey+0x298
    fffff387`c9f87120 fffff802`05647a43 : ffff8188`451f3cc0 00000000`00000000 ffff80d4`5a0ed560 00000000`2079654b : nt!NtOpenKey+0x12
    fffff387`c9f87160 fffff802`0563ae50 : fffff802`059fd193 00000000`00000004 ffffaf89`97dfdd50 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    fffff387`c9f872f8 fffff802`059fd193 : 00000000`00000004 ffffaf89`97dfdd50 00000000`00000000 00000000`00000010 : nt!KiServiceLinkage
    fffff387`c9f87300 fffff802`059fd0da : 00000000`00000000 ffffffff`800000dc ffff8188`451f3ccc ffff8188`451f3ccc : nt!_RegRtlOpenKeyTransacted+0xa3
    fffff387`c9f873a0 fffff802`059fc5c0 : 00000000`0000002e fffff387`c9f87460 00000000`000000f0 fffff802`00000000 : nt!SysCtxRegOpenKey+0x3a
    fffff387`c9f873e0 fffff802`059fbb00 : fffff387`c9f87610 ffffaf89`97dfdd50 fffff387`00000031 fffff387`c9f87610 : nt!_CmOpenDeviceRegKeyWorker+0x1b0
    fffff387`c9f874a0 fffff802`05ae9fa5 : 00000000`00000000 ffffaf89`97def1b0 ffffffff`8000008c 00000000`00000001 : nt!_CmOpenDeviceRegKey+0xdc
    fffff387`c9f875a0 fffff802`05a823cc : ffffaf89`00000000 00000000`00000000 00000135`00000001 00000000`00000000 : nt!PiDevCfgProcessDeviceCallback+0x95
    fffff387`c9f876b0 fffff802`05a8238e : ffffaf89`97df0b00 ffffaf89`97df9d01 ffffaf89`97dfae00 00000000`00000000 : nt!PipForAllDeviceNodesCallback+0x1c
    fffff387`c9f876e0 fffff802`05a8234b : ffffaf89`97df9d20 00000135`0ac04800 ffffaf89`97ce8ee0 00000000`00000002 : nt!PipForAllChildDeviceNodes+0x2a
    fffff387`c9f87710 fffff802`05ac7f67 : ffffaf89`9cd300f0 fffff802`055d8135 00000000`00000000 00000000`00000000 : nt!PipForDeviceNodeSubtree+0x27
    fffff387`c9f87750 fffff802`05ac7ebd : ffffaf89`00000000 00000000`00000000 00000135`00000000 00000000`00000000 : nt!PpDevCfgProcessDevices+0x53
    fffff387`c9f877d0 fffff802`05ac83bd : 00000000`00000000 fffff387`c9f87800 fffff802`0564ad90 ffffffff`80000424 : nt!PnpBootPhaseComplete+0x51
    fffff387`c9f87820 fffff802`05ab9b9b : ffffaf89`9cd07040 00000000`00000000 00000135`0ac04880 fffff802`05528dc6 : nt!CmCompleteRegistryInitialization+0x13d
    fffff387`c9f87900 fffff802`05647a43 : 00000000`00000000 ffffaf89`97d711b0 00000000`00000001 00000000`00000001 : nt!NtInitializeRegistry+0x5f
    fffff387`c9f87930 fffff802`0563ae50 : fffff802`05ab9b66 fffff387`c9f87b18 00000000`00000000 00000000`0000007c : nt!KiSystemServiceCopyEnd+0x13
    fffff387`c9f87ac8 fffff802`05ab9b66 : fffff387`c9f87b18 00000000`00000000 00000000`0000007c 00000000`00000000 : nt!KiServiceLinkage
    fffff387`c9f87ad0 fffff802`05647a43 : ffffaf89`9cd07040 00000135`0ac04880 ffffaf89`00000000 ffffaf89`97d739c0 : nt!NtInitializeRegistry+0x2a
    fffff387`c9f87b00 00007ff8`bb35bdc4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000005`cfc7edf8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`bb35bdc4


    THREAD_SHA1_HASH_MOD_FUNC: a7dfeb01dc94537d5f29dc40c0b9f18a962a6e5b

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 6fbe5619d607050c7babf83b1cff54444c3d546b

    THREAD_SHA1_HASH_MOD: 64bb2a6f8dc36ac820f4065966be5acdf18c8cca

    FOLLOWUP_IP:
    nt!CmpGetNameControlBlock+129
    fffff802`059ccc49 413b18 cmp ebx,dword ptr [r8]

    FAULT_INSTR_CODE: f183b41

    SYMBOL_STACK_INDEX: 4

    SYMBOL_NAME: nt!CmpGetNameControlBlock+129

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME:     nt

    IMAGE_NAME: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 5b48247f

    IMAGE_VERSION: 10.0.17134.167

    STACK_COMMAND: .thread ; .cxr ; kb

    BUCKET_ID_FUNC_OFFSET: 129

    FAILURE_BUCKET_ID: 0x1E_c0000005_R_nt!CmpGetNameControlBlock

    BUCKET_ID: 0x1E_c0000005_R_nt!CmpGetNameControlBlock

    PRIMARY_PROBLEM_CLASS: 0x1E_c0000005_R_nt!CmpGetNameControlBlock

    TARGET_TIME: 2018-07-26T10:43:52.000Z

    OSBUILD: 17134

    OSSERVICEPACK: 167

    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: 2018-07-13 05:03:11

    BUILDDATESTAMP_STR: 180410-1804

    BUILDLAB_STR: rs4_release

    BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804

    ANALYSIS_SESSION_ELAPSED_TIME: a47

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:0x1e_c0000005_r_nt!cmpgetnamecontrolblock

    FAILURE_ID_HASH: {ce15e346-d049-a1d6-077d-1515ae36a725}

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

    :)
     
    Badr Eddine NeoIbn Yahia, Jul 26, 2018
    #1
  2. SMITTYCHAT.
    Smittychat. Win User

    Stop Code - apc mismatch

    Hello,

    Follow the steps listed by
    Reymichael Ros
     
    Smittychat., Jul 26, 2018
    #2
  3. EXODUSPRIME1337
    exodusprime1337 Win User
    windows xp installation and dual core am

    could someone please list the steps they follow to install windows with a dual core processor and windows xp service pack to. I'm reletively new to amd dual core and i feel i'm missing a step. All help will be appreciated. thanx
     
    exodusprime1337, Jul 26, 2018
    #3
  4. ERIC BER
    Eric Ber Win User

    windows stop code 0x0000001e

    stop code

    Hi,

    Conflicts with the hardware driver is one of hte possible reasons why you are having a blue screen error with stop code, NTFS.sys. For us to assist you better, kindly answer the following questions:

    • Have you made any changes to your computer prior to this issue?
    • What troubleshooting steps have you done so far?
    • Which Version and OS Build number of Windows 10 is currently installed? To check, press the
      Windows key, type winver, and press the
      Enter       key.
    • Can you provide us the complete stop code message?

    Meanwhile, you can try the troubleshooting steps on this
    link     to resolve blue screen issues.

    We will be looking forward to your response.
     
    Eric Ber, Jul 26, 2018
    #4
Thema:

windows stop code 0x0000001e

Loading...

  1. windows stop code 0x0000001e - Similar Threads - stop code 0x0000001e

  2. BSOD stop code: KMODE_EXCEPTION_NOT_HANDLED Bugcheck was: 0x0000001e 0xffffffffc0000096,...

    in Windows 10 BSOD Crashes and Debugging
    BSOD stop code: KMODE_EXCEPTION_NOT_HANDLED Bugcheck was: 0x0000001e 0xffffffffc0000096,...: For the past few weeks I have been getting the BSOD seemingly randomly at again random intervals. When the blue screen pops up it reads, Stop code: KMODE_EXCEPTION_NOT_HANDLED, without anything else. When going into the event viewer, this error message pops up:The computer...

  3. BSOD stop code: KMODE_EXCEPTION_NOT_HANDLED Bugcheck was: 0x0000001e 0xffffffffc0000096,...

    in Windows 10 Gaming
    BSOD stop code: KMODE_EXCEPTION_NOT_HANDLED Bugcheck was: 0x0000001e 0xffffffffc0000096,...: For the past few weeks I have been getting the BSOD seemingly randomly at again random intervals. When the blue screen pops up it reads, Stop code: KMODE_EXCEPTION_NOT_HANDLED, without anything else. When going into the event viewer, this error message pops up:The computer...

  4. BSOD stop code: KMODE_EXCEPTION_NOT_HANDLED Bugcheck was: 0x0000001e 0xffffffffc0000096,...

    in Windows 10 Software and Apps
    BSOD stop code: KMODE_EXCEPTION_NOT_HANDLED Bugcheck was: 0x0000001e 0xffffffffc0000096,...: For the past few weeks I have been getting the BSOD seemingly randomly at again random intervals. When the blue screen pops up it reads, Stop code: KMODE_EXCEPTION_NOT_HANDLED, without anything else. When going into the event viewer, this error message pops up:The computer...

  5. 10 BugCheck 1001 : 0x0000001e

    in Windows 10 BSOD Crashes and Debugging
    10 BugCheck 1001 : 0x0000001e: 10 bugcheck 1001 . : 0x0000001e 0xffffffffc0000005, 0xfffff801811072ab, 0x0000000000000000, 0xffffffffffffffff. : C:\Windows\MEMORY.DMP. ID: 6359840f-d869-4db8-aef5-3bf63d446d23 . -<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> -<System>...

  6. Blue Screen of Death -- 0x0000001e

    in Windows 10 BSOD Crashes and Debugging
    Blue Screen of Death -- 0x0000001e: hello fellow internet-goers! Hope your day is going better than mine at the moment. Today I started getting the awful BSOD, with this showing in Event Viewer: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e 0xffffffffc0000005, 0xfffff80465173882,...

  7. Reboot from bugcheck: 0x0000001e

    in Windows 10 Drivers and Hardware
    Reboot from bugcheck: 0x0000001e: My computer has been crashing regularly, every time I've tried playing a game after anywhere from 10 minutes to an hour, and occasionally when using browsers as well. Since reinstalling Windows 10 while trying to fix this there have been less problems with the browser but the...

  8. BSOD on Startup. The bugcheck was: 0x0000001e

    in Windows 10 BSOD Crashes and Debugging
    BSOD on Startup. The bugcheck was: 0x0000001e: Hi, I received a BSOD on startup on the 7th of August at 6:57 pm. I have been trying to look into why this has happened but couldn't find out. Could you please help me find out the cause of the BSOD and how to fix it? 14470

  9. BSOD with 0x0000001e Kernel_mode_exception_not_handled

    in Windows 10 BSOD Crashes and Debugging
    BSOD with 0x0000001e Kernel_mode_exception_not_handled: I had two blue screens for this month (first one was Cities: Skylines After Dark, second was from The Sims 4). I was thinking it was about my memory but when I was looking at it, the task manager was just using 66 percent of the memory and I have been playing Sims 4 for a...

  10. Rebooted from BugCheck error 0x0000001e

    in Windows 10 BSOD Crashes and Debugging
    Rebooted from BugCheck error 0x0000001e: Rebooted from BugCheck, and created a report zipped as attached. Anybody able to read the file and diagnosis fault? 77735
  1. MINHOKIM4
    Thread

    10 BugCheck 1001 : 0x0000001e

    10 bugcheck 1001 . : 0x0000001e 0xffffffffc0000005, 0xfffff801811072ab, 0x0000000000000000, 0xffffffffffffffff. : C:\Windows\MEMORY.DMP. ID:...
    Thread by: minhokim4, Oct 15, 2020, 3 replies, in forum: Windows 10 BSOD Crashes and Debugging
  2. AMBER J.WOLFE
    Thread

    KMODE_EXCEPTION_NOT_HANDLED 0x0000001e and System_Service_Exception 0x0000003b

    Early this morning my new computer BSoD on me. When checking the mini dump file, this is what it says: KMODE_EXCEPTION_NOT_HANDLED 0x0000001e...
    Thread by: Amber J.Wolfe, Jun 23, 2020, 3 replies, in forum: Windows 10 BSOD Crashes and Debugging
  3. HCVD
    Thread

    Blue Screen of Death -- 0x0000001e

    hello fellow internet-goers! Hope your day is going better than mine at the moment. Today I started getting the awful BSOD, with this showing in...
    Thread by: hcvd, May 19, 2020, 3 replies, in forum: Windows 10 BSOD Crashes and Debugging
  4. ALEX BANY
    Thread

    Reboot from bugcheck: 0x0000001e

    My computer has been crashing regularly, every time I've tried playing a game after anywhere from 10 minutes to an hour, and occasionally when...
    Thread by: Alex Bany, Aug 28, 2019, 3 replies, in forum: Windows 10 Drivers and Hardware
  5. GEARAD11011
    Thread

    Got wfplwfs.sys BSOD

    I just got a replacement motherboard last week because the previous one had faulty DIMM slots. I got this BSOD today and wondering if it could be...
    Thread by: Gearad11011, Jan 21, 2019, 3 replies, in forum: Windows 10 BSOD Crashes and Debugging
Tags:

Users found this page by searching for:

  1. windows stop code 0x 0000001