Application Error - NTDLL.dll

J

jtitton

New member
Hi guys,

I don't know how this started. In the last week I tryed everything, from repair to full reinstall of Pix and nothing changes.
I cant use Pix last week.

Somebody can help me?

Thanks


Nome do aplicativo com falha: PixInsight.exe, versão: 1.8.8.5, carimbo de data/hora: 0x5e58eb9a
Nome do módulo com falha: ntdll.dll, versão: 10.0.19041.207, carimbo de data/hora: 0xcad89ab4
Código de exceção: 0xc000041d
Deslocamento da falha: 0x0000000000037aae
ID do processo com falha: 0x9a8
Hora de início do aplicativo com falha: 0x01d64b11ea45291f
Caminho do aplicativo com falha: C:\Program Files\PixInsight\bin\PixInsight.exe
Caminho do módulo com falha: C:\WINDOWS\SYSTEM32\ntdll.dll
ID do Relatório: c77afc4c-b63f-41a2-a627-bc49cb8b1a13
Nome completo do pacote com falha:
ID do aplicativo relativo ao pacote com falha:



Falha no bucket 2242083050180906988, tipo 4
Nome do Evento: APPCRASH
Resposta: Não disponível
ID do CAB: 0

Assinatura do problema:
P1: PixInsight.exe
P2: 1.8.8.5
P3: 5e58eb9a
P4: ntdll.dll
P5: 10.0.19041.207
P6: cad89ab4
P7: c000041d
P8: 0000000000037aae
P9:
P10:

Arquivos anexados:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6945.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER81A0.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER81C0.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER81CE.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER81EE.tmp.txt

Esses arquivos talvez estejam disponíveis em:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_PixInsight.exe_dddfee109f6841732353f5e47776ac397b3c91e_7254eabb_e61c3d0b-f957-407d-9e6c-c526c8f61b38

Símbolo da análise:
Verificando novamente se há uma solução: 0
ID do Relatório: c77afc4c-b63f-41a2-a627-bc49cb8b1a13
Status do Relatório: 268435456
Bucket com hash: 515f75166fca574e8f1d7aa7b2f50fecGuid do CAB: 0
 
Hi.

As this is a local problem to your computer, not affecting anyone else and ntdll.dll is a kernel Windows component it could be that there is corruption of the Windows OS after an OS update, system crash, hard drive failure or the installation of additional software.

Assuming this is Windows 8.1 or 10 then:

Open an elevated Command Prompt window by typing CMD in the lower left search box, in the pop-up search results list, mouse-right-click on “Command Prompt App“ and click “Run as Administrator” in the context menu.

An elevated Command Prompt window will appear.

(It must state “Administrator” at the top of the Command Prompt window, if not, type exit at the prompt followed by return/enter and begin again following the instructions above)

Run the Windows Deployment Image Servicing & Management tool (DISM).

To do this.....

Type or copy/paste the following text string at the Command Prompt followed by carriage return/enter:

DISM.exe /Online /Cleanup-image /Restorehealth

(Note the spaces before the “/“ character, the command won’t run if these are missing)

The DISM tool will check the Windows image file against the local stored updates repository and repair any Windows image files it finds are broken or missing.

Allow at least an hour for DISM to run and don‘t play with the computer while this tool is running.

When DISM completes execution, hopefully successfully, type or copy/paste the following text string at the Command Prompt followed by return/enter:

sfc /scannow

(Note the space before the “/“ character, the command wont run if this is missing)

Windows system file checker tool (SFC) will compare the computers newly restored Windows image file with the live Windows OS files used to run the computer and repair any it finds missing or corrupted, it may take up to an hour so do not interfere with the computer until the sfc tool reports completed.

Once complete, and depending on the report visible in the command line tool, window, type: exit followed by return/enter to close the command window, reboot the computer and test PixInsight to see if the problem is solved.

If the DISM or SFC tools fail due to unrepairable Windows corruption or a bad update file in the local update repository then you will need to use advanced DISM processes, or seek expert Microsoft support that is beyond the scope of this forum, refer to the following Microsoft documents for further guidance:



Update your thread and let us know if you were able to fix the problem using DISM and SFC but note I am not a Microsoft technician and unable to suggest anything else beyond the above.

William.
 
Last edited:
You must log in or register to reply here.
Back
Top