After installing latest haxe toolkit (3.2.0), I have tried to install some libraries to start work on my project. But library manager (haxelib.exe) seems not working properly on my computer. It always crashes and windows showing alert:
The application was unable to start correctly (0xc000000d). Click OK
to close the application
I have also installed toolkit on wife computer and everything working fine. Wife has Windows 7 x64. On my computer is installed Windows 8.1 x64.
In Windows event viewer I found logs:
(Error description)
Faulting application name: haxelib.exe, version: 0.0.0.0, time stamp: 0x5128e2cf
Faulting module name: ntdll.dll, version: 6.3.9600.17936, time stamp: 0x55a68dd1
Exception code: 0xc000000d
Fault offset: 0x0009d4f2
Faulting process id: 0x1710
Faulting application start time: 0x01d0f85f90454af3
Faulting application path: C:\HaxeToolkit\haxe\haxelib.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: d9781581-6452-11e5-82b6-94de80bc77ca
Faulting package full name:
Faulting package-relative application ID:
(Information)
Fault bucket 116025787538, type 5
Event Name: BEX
Response: Not available
Cab Id: 0
Problem signature:
P1: haxelib.exe
P2: 0.0.0.0
P3: 5128e2cf
P4: ntdll.dll
P5: 6.3.9600.17936
P6: 55a68dd1
P7: 0009d4f2
P8: c000000d
P9: 00000000
P10:
Attached files:
C:\Users\stanosky\AppData\Local\Temp\WER95F7.tmp.WERInternalMetadata.xml
C:\Users\stanosky\AppData\Local\Temp\WERA1B0.tmp.appcompat.txt
C:\Users\stanosky\AppData\Local\Temp\WERA1E0.tmp.dmp
C:\Users\stanosky\AppData\Local\Temp\WERA21F.tmp.WERDataCollectionFailure.txt
These files may be available here:
C:\Users\stanosky\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_haxelib.exe_2b43177c7b6b1557ce91e7560961d98719c3f54_0b7bc880_0bf3a5b6
Analysis symbol:
Rechecking for solution: 0
Report Id: d9781581-6452-11e5-82b6-94de80bc77ca
Report Status: 4104
Hashed bucket: f45888bea7f3cfaa0a11620b03ca7f6a
Any ideas what is going wrong with my computer/windows?
It turns out that my computer was infected by rootkit. It injects some bits of code into Windows dll files and that caused malfunction of haxelib.exe. I have removed it and my problem has gone.
Related
I am developing an app for windows, and I need it to work on Windows server 2019.
The flutter docs website mentions support for: Win 7 and above, and I'm not sure if that includes Windows server.
So, does flutter Desktop support Windows server 2019 and above?
I tried to run the application on windows server 2019, the application does not open, an error is logged:
Faulting application name: logbook.exe, version: 1.0.0.0, time stamp: 0x62fc7c7c
Faulting module name: logbook.exe, version: 1.0.0.0, time stamp: 0x62fc7c7c
Exception code: 0xc0000005
Fault offset: 0x0000000000005680
Faulting process id: 0x2590
Faulting application start time: 0x01d8b200df09b765
Faulting application path: C:\dev\logbook\logbook.exe
Faulting module path: C:\dev\logbook\logbook.exe
Report Id: fb88d338-89c8-4697-b637-5922dd9ad358
Faulting package full name:
Faulting package-relative application ID:
When trying to run my executable program on a Windows Server 2008 R2 (x64), it fails immediately and Windows says "Program (x64) has stopped working".
The same executable works on many other machines.
Even on other machines with the same OS.
The program comes with its own Dlls in the folder.
Even if it would require other Dlls that arent present i think the system would say so?
Here is the output from Windows Event Viewer:
Faulting application name: dscp.exe, version: 19.0.0.398, time stamp: 0x5d8b42ef
Faulting module name: VERSION.dll_unloaded, version: 0.0.0.0, time stamp: 0x4a5be082
Exception code: 0xc0000005
Fault offset: 0x000007fefbcc15b4
Faulting process id: 0x1db4
Faulting application start time: 0x01d5744a0d493693
Faulting application path: C:\TEMP\DebugW\dscp.exe
Faulting module path: VERSION.dll
Report Id: 50adb64b-e03d-11e9-a7b2-000c29b302dd
I have looked up VERSION.dll and it seems to be a Windows system Dll.
I dont' know how to debug this issue.
I'm a little stumped as to why this windows service is not running when using the Network Service account (but does so on other machines using the same code), getting me these two subsequent errors in event viewer:
Application: MyApplication.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 06F3C67E
Stack:
and
Faulting application name: MyApplication.exe, Version: 1.0.0.0, time stamp: 0x87654321
Faulting module name: ReferencedComLib.dll, Version: 1.0.0.0, time stamp: 0x12345678
Exception code: 0xc0000005
Fault offset: 0x0000c67e
Faulting process ID: 0x148c
Faulting application start time: 0x01d4df2e591220f2
Faulting application path: C:\Program Files (x86)\MyApplication\MyApplication.exe
Faulting module path: C:\Windows\SYSTEM32\ReferencedComLib.dll
Report ID: 9d8df956-4b21-11e9-80c8-00155dc82141
Faulting package full name:
Faulting package-relative application ID:
This seems to indicate that the service is looking for ReferencedComLib.dll under C:\Windows\SYSTEM32...
But ReferencedComLib.dll is actually located under C:\Windows\SysWOW64 - it's a COM-library from third party (and their installer correctly installs it into SysWOW64)
Running under Local System however this error does not even show up and the service runs without problems - and this problem is currently only reproducable on one stage, on all others it is running fine with Network Service.
How could changing the service account running the service result in a faulting module?
Simon Mourier was right, the problem was internal to the third party dlls I am using and it was trying to access a directory that was under C:\Users....
Reinstalling under a different path that Network Service could access fixed the problem.
I frequently have the following crash from cl.exe. This happens both when compiling and running other a help command on cl. This is happening on Windows Server 2008, but I think this happens sometimes on Windows XP also. This is occurring very frequently within Jenkins when when running waf configure.
I haven't been able to find anything online to fix this problem, although there are mentions of kernelbase.dll crashing in other programs.
Does anyone have any thoughts on how to avoid this problem?
Thanks
Log Name: Application
Source: Application Error
Date: 1/24/2012 4:25:51 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer:
Description:
Faulting application name: cl.exe, version: 15.0.30729.1, time stamp: 0x488ef6ea
Faulting module name: KERNELBASE.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdbdf
Exception code: 0x0eedfade
Fault offset: 0x0000b727
Faulting process id: 0xd74
Faulting application start time: 0x01ccdae720a1cbbd
Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\BIN\cl.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: 5e9f206e-46da-11e1-a28d-bc305bd1c68c
Event Xml:
1000
2
100
0x80000000000000
55240
Application
cl.exe
15.0.30729.1
488ef6ea
KERNELBASE.dll
6.1.7600.16385
4a5bdbdf
0eedfade
0000b727
d74
01ccdae720a1cbbd
C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\BIN\cl.exe
C:\Windows\syswow64\KERNELBASE.dll
5e9f206e-46da-11e1-a28d-bc305bd1c68c
Check:
http://social.msdn.microsoft.com/Forums/en-US/netfxbcl/thread/05764562-0133-4e6d-a613-bfe1ec2f0c1d/.
This seems to be an issue with updated dlls. I would also suggest compiling your program outside of Jenkins just to be sure that it is not an issue with Jenkins (either paths, or anything else).
I've got an application we use at our company.
All of our Windows XP PCs and Windows 7 PCs use it.
I can run it in the debugger under Visual Studio 2008 and build the Installer that all of the other PCs use to install it with, but I can not get it to run after installing on my PC (the installation shows no errors).
Under Event Viewer > Windows Logs > Application, two (2) events are fired:
The Error thrown when I try to run the installed application:
Faulting application name: Suite.exe, version: 2.2.21.0, time stamp: 0x4d389f32
Faulting module name: ntdll.dll, version: 6.1.7600.16559, time stamp: 0x4ba9b802
Exception code: 0xc00000fd
Fault offset: 0x00000000000076cf
Faulting process id: 0x1424
Faulting application start time: 0x01cbb8f485a2a9d8
Faulting application path: C:\Program Files\Aaon Coil Products, Inc\ACP Software Suite\Suite.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: c58bd590-24e7-11e0-b398-00248103a942
An Informational message fires up immediately after with Windows Error Reporting:
Fault bucket 28268826, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: Suite.exe
P2: 2.2.21.0
P3: 4d389f32
P4: ntdll.dll
P5: 6.1.7600.16559
P6: 4ba9b802
P7: c00000fd
P8: 00000000000076cf
P9:
P10:
Attached files:
C:\Users\cp-jpool\AppData\Local\Temp\WER492A.tmp.WERInternalMetadata.xml
These files may be available here:
C:\Users\cp-jpool\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Suite.exe_e131a0d577e0788f7db9b54fd53b35e27d8860e2_11df4dea
Analysis symbol:
Rechecking for solution: 0
Report Id: c58bd590-24e7-11e0-b398-00248103a942
Report Status: 0
This repeats every time I try to run the application I made with this PC ...on this PC, but no where else.
Could someone give me some idea of what's going on and how to fix it?
Do you get prompted to elevate Visual Studio when you run it?
If so, try running the app elevated.
Basically, isolate what's different between the two:
Can you run it in Visual Studio without debugging? Including when you set it to "Release"?
How about if you build and install it as "Debug" then start it and try to attach to it as it crashes? (You can set the JIT debugger via the registry here: http://msdn.microsoft.com/en-us/library/5hs4b7a6.aspx)
Good luck!
It turned out that my application uses a control that does not run on 64-bit environments.
Apparently, the debugger in VS2008 will not throw an error whenever one of these old style DLLs fails.