Share via

Explorer Windows 10 ucrtbase.dll fault

Anonymous
2018-04-09T12:06:55+00:00

Hi There

I have already been searching in the forums for a solution tot his and cant find one, considering most issues with other programs other than explorer itself.

Explorer keeps crashing, stays open for a few moments then closes, gui also refreshes constantly (obviously being part of Explorer).

Faulting application name: explorer.exe, version: 10.0.16299.248, time stamp: 0x18ee648b

Faulting module name: ucrtbase.dll, version: 10.0.16299.248, time stamp: 0xe71e5dfe

Exception code: 0xc0000409

Fault offset: 0x000000000006b79e

Faulting process ID: 0x332c

Faulting application start time: 0x01d3cff980fd1e8b

Faulting application path: C:\Windows\explorer.exe

Faulting module path: C:\Windows\System32\ucrtbase.dll

Report ID: e4f8b76b-698c-48fd-adf5-b1ef8f4cca28

Faulting package full name:

Faulting package-relative application ID:

As its explorer its not like I can just reinstall the darn thing and this is also quite a new issue, nothing new installed or changed on the system just out of the blue.

Any solutions would be very welcome :)

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

5 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2018-04-09T13:59:07+00:00

    Open Start, type: file explorer options

    Hit Enter

    Under the General tab, click in the Open File Explorer to then choose "This PC".

    Try WinKey + E now. If it opens fine, then the problem is with Quick access cache, which can be cleared by deleting *.automaticDestinations-ms from the following directory, using Command Prompt.

    %AppData%\Microsoft\Windows\Recent\AutomaticDestinations

    Press Windows key + R

    Type: %AppData%

    Hit Enter

    Then navigate to that folder.

    Could be an issue with your display driver.

    uninstall your display driver then restart

    Boot to the Windows 10 desktop

    Press Windows key + X

    Click Device Manager

    Expand Display adapters

    Right click the current display adapter

    Click Uninstall

    Exit Device Manager

    Restart

    Was this answer helpful?

    20+ people found this answer helpful.
    0 comments
  2. Anonymous
    2018-04-10T12:45:41+00:00

    thx for hte quick reply!

    looks like clearing the cache solved it thx.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  3. Anonymous
    2018-05-18T16:21:13+00:00

    Hi Andre, my problem is also related to ucrtbase.dll, but demonstrates itself differently.

    (And yes, I already cleaned up ...\Recent\AutomaticDestinations _and_ ...\Recent\CustomDestinations).

    We develop software that uses Nuance speech recognition engine that runs as nte.exe.

    After I installed Windows 10 April 2018 Update on my Windows 10 Pro (64 bit) I use for development, nte.exe started crashing arbitrarily, sometimes during transcribing speech, sometimes when it's idle.

    Crashes always showed almost the same stack:

    <different value here>                      ...  mov         al,81h  

    ucrtbase.dll!00007fff460a0a07()   00007FFF460A0A01  call        qword ptr [7FFF460E54B8h]

    kernel32.dll!00007fff48513034()   00007FFF4851302E  call        qword ptr [7FFF48579B08h]

    ntdll.dll!00007fff496a1551()          00007FFF496A154B  call        qword ptr [7FFF497A3000h]

    I saw different value here> to be 00000281854cc5a0 or 00000195090dbd10, but the contents of the culprit is always mov al,81h and the rest of the stack is always the same.

    Ok, I reverted the OS to previous version (back from 1803, build 17134.1 to 1703, build 15063.1088), and nte.exe works just wonderfully as it did before.

    Any ideas/comments?

    Thanks in advance.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2018-05-18T16:32:29+00:00

    Sorry, have to add what I forgot to mention: the exception is

    Unhandled exception at 0x00000281854CC5A0 in nte.exe: 0xC0000005: Access violation executing location 0x00000281854CC5A0.

    and the address (like 0x00000281854CC5A0 or whatever it happens to be) is in fact outside of process memory.

    And no, nte.exe does not create a memory dump and does not write into any of windows logs so eventvwr.exe shows nothing.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2018-04-10T12:54:21+00:00

    Glad you got it resolved!

    Was this answer helpful?

    0 comments