Users of one of our VO programs sometimes encounter a "APPCRASH" error. The application log shows a "Faulting module path: C:WindowsSYSTEM32ntdll.dll". This clients starts the exe from a directory on C: while the server's DBF files are on F:, a construction of their system supplier.
Does anyone know how this specific error can occur?
Faulting application name: MyVoExe.exe, version: 2.5.0.2838, time stamp: 0x00000000
Faulting module name: ntdll.dll, version: 6.3.9600.20144, time stamp: 0x615be385
Exception code: 0xc0000006
Fault offset: 0x0001a3e7
Faulting process id: 0x6ef0
Faulting application start time: 0x01d7d4783c3c1932
Faulting application path: C:MyprogramDirMyVoExe.exe
Faulting module path: C:WindowsSYSTEM32ntdll.dll
Report Id: 31d31cad-4074-11ec-8173-00155d134101
Faulting package full name:
Faulting package-relative application ID:
Dick
Faulting module path: C:WindowsSYSTEM32ntdll.dll
Faulting module path: C:WindowsSYSTEM32ntdll.dll
Hi Dick,
I have seen such crashes when there was a Windows Update waiting for a reboot.
Wolfgang
I have seen such crashes when there was a Windows Update waiting for a reboot.
Wolfgang
Wolfgang Riedmann
Meran, South Tyrol, Italy
wolfgang@riedmann.it
https://www.riedmann.it - https://docs.xsharp.it
Meran, South Tyrol, Italy
wolfgang@riedmann.it
https://www.riedmann.it - https://docs.xsharp.it
Faulting module path: C:WindowsSYSTEM32ntdll.dll
Hello Wolfgang,
That is quite interesting remark, thanks.. The server doesn't auto update but is sometimes mentioning in yellow on logging in as RD administrator, or with a screen wide message, that updates are due. We applied the updates yesterday and from 5 entries in the Application log yesterday from our program we have not had 1 (yet) but there is still one from path: C:WindowsExplorer.EXE.
It's one of those messages where more detail in the error handling (in this case of Windows) would have been very helpful.
Dick
That is quite interesting remark, thanks.. The server doesn't auto update but is sometimes mentioning in yellow on logging in as RD administrator, or with a screen wide message, that updates are due. We applied the updates yesterday and from 5 entries in the Application log yesterday from our program we have not had 1 (yet) but there is still one from path: C:WindowsExplorer.EXE.
It's one of those messages where more detail in the error handling (in this case of Windows) would have been very helpful.
Dick
-
- Posts: 113
- Joined: Mon May 02, 2016 9:10 am
- Location: Schweiz
Faulting module path: C:WindowsSYSTEM32ntdll.dll
Hi Dick
on some operating systems we had the same errors. E.g. using a standard open file dialog.
The solultion was to disable DEP (Data Execution Prevention).
HTH Markus
on some operating systems we had the same errors. E.g. using a standard open file dialog.
The solultion was to disable DEP (Data Execution Prevention).
HTH Markus
Faulting module path: C:WindowsSYSTEM32ntdll.dll
Hello Markus,
Thanks for your remark; I've passed this on to the company who maintains the server.
Dick
Thanks for your remark; I've passed this on to the company who maintains the server.
Dick