I'm on windows 7 64 bit and every time I run vs_Community.exe after downloading it, it stops working and the problem details show this:
Problem Event Name: APPCRASH
Application Name: vs_setup_bootstrapper.exe
Application Version: 2.7.3132.26759
Application Timestamp: 9b581caf
Fault Module Name: KERNELBASE.dll
Fault Module Version: 6.1.7601.17514
Fault Module Timestamp: 4ce7c78c
Exception Code: c06d007e
Exception Offset: 000000000000a49d
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 2057
Additional Information 1: 7283
Additional Information 2: 72836eb6216b49be15302fdb224c1b5d
Additional Information 3: 3a01
Additional Information 4: 3a018db631e662ba3d328203cc490b3a
It worked on windows 7 32 bit just fine so it can't be the fact that I'm on windows 7.
Related
Simply, I cannot run App verifier (WOW or 64-bit). It simply does not start. Event viewer says:
Faulting application name: appverif.exe, version: 10.0.18362.1, time stamp: 0x58ca3409
Faulting module name: ntdll.dll, version: 10.0.18362.1139, time stamp: 0x335bbdaf
Exception code: 0xc0000374
Fault offset: 0x000dfa1d
Faulting process ID: 0x2ad0
Faulting application start time: 0x01d6aa7ad4a12bf6
Faulting application path: C:\Windows\SysWOW64\appverif.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report ID: 235c3a4d-2d54-4436-99bf-b54a217c9a7f
Additionally, I tried to run appverif.exe (in system and syswow64) under Visual Studio and I see:
EDIT (Update based on comments)
Some are suggesting that Application Verifier does not have a GUI. However, last time I ran it, I saw the following:
I asked Microsoft employee Gov Maharaj (from application compatibility team) and they already know about the issue and the issue is fixed in an update for the Windows 10 2004 SDK which was released in December 2020 (19041.685.201201-2105.vb_release_svc_prod1_WindowsSDK.iso):
The Windows 10 SDK, Version 2004 SDK servicing update (released
12/16/2020) contains the following fixes. If you encounter these
issues, we recommend that you update your version of the SDK as soon
as possible to avoid them:
Resolved issue that prevented AppVerifier from working
Download and install the update to fix it.
I managed to run the verifier under a SYSTEM account using PsExec:
...PsTools\PsExec64.exe -i -s C:\Windows\System32\appverif.exe
I've tried the recommended methods - installing the latest windows SDK and running the program through 'PsExec64.exe -i -s' but neither worked. This program seems to be something Microsoft periodically breaks, judging by what I've read.
I ran appverif.exe through visual studio and saw the following call stack on crash:
ntdll.dll!RtlReportCriticalFailure() Unknown
ntdll.dll!RtlpHeapHandleError() Unknown
ntdll.dll!RtlpHpHeapHandleError() Unknown
ntdll.dll!RtlpLogHeapFailure() Unknown
ntdll.dll!RtlpFreeHeapInternal() Unknown
ntdll.dll!RtlFreeHeap() Unknown
msvcrt.dll!00007ffd44449c9c() Unknown
appverifUI.dll!00007ffc9a41f9d6() Unknown
appverifUI.dll!00007ffc9a411636() Unknown
appverif.exe!00007ff64965281b() Unknown
appverif.exe!00007ff6496615ed() Unknown
kernel32.dll!00007ffd43957034() Unknown
ntdll.dll!RtlUserThreadStart() Unknown
It seems to be crashing after a heap free.
When executing a newly built "Hello World" console application in CMD or PowerShell inside ConEmu (frames and tabulates everything), the application will fail with "MyApp has stopped working" after printing "Hello World".
Execution in a regular CMD/PowerShell works fine.
Setup:
Windows 7 Enterprise
Visual Studio 2015
ConEmu 150816
.Net 4.5.2
Problem details/signature:
Problem Event Name: APPCRASH
Application Name: PerforceSSOClient.exe
Application Version: 1.0.0.0
Application Timestamp: 55e5acb4
Fault Module Name: nvd3d9wrap.dll
Fault Module Version: 9.18.13.3182
Fault Module Timestamp: 5280d7e2
Exception Code: c00000fd
Exception Offset: 0000583d
OS Version: 6.1.7601.2.1.0.256.4
Locale ID: 1030
Additional Information 1: c859
Additional Information 2: c859befd7e6cd7469e4e4ec59e24adda
Additional Information 3: fd58
Additional Information 4: fd581380868e58459acc52bac65d582b
The crash is caused by the nVIDIA driver dll nvd3d9wrap.dll. You use the driver version 331.82. Try to use the latest driver 355.82:
32Bit: http://www.nvidia.com/download/driverResults.aspx/90493/en-us
64Bit: http://www.nvidia.com/download/driverResults.aspx/90494/en-us
I have an app which is running perfectly in my system and also on a few other customers as well. But I have a particular customer for which this is not working. I have tried the following:
Updating Windows.
turning off firewall.
turning off DEP.
turning off UAC.
But none of this works. Following are the errors that come.
First:
Problem signature:
Problem Event Name: APPCRASH
Application Name: myApp.exe
Application Version: 3.1.0.98
Application Timestamp: 52931ef4
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7601.18205
Fault Module Timestamp: 51db96c5
Exception Code: c0000005
Exception Offset: 00056018
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: d492
Additional Information 2: d4929f89b5901f5adaff2902c08af6fa
Additional Information 3: fd01
Additional Information 4: fd01b5c431f746d7526bc265e84208c2
Second:
Problem signature:
Problem Event Name: APPCRASH
Application Name: myApp.exe
Application Version: 3.1.0.98
Application Timestamp: 51d51f8b
Fault Module Name: msado15.dll
Fault Module Version: 6.1.7601.17857
Fault Module Timestamp: 4fcee2cc
Exception Code: c0000005
Exception Offset: 000302d8
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 3047
Additional Information 2: 304731efac0f2df745479a919b6ba54b
Additional Information 3: c5d9
Additional Information 4: c5d92a2744df3b35f2cd5ee4004f8239
Third:
Problem signature:
Problem Event Name: APPCRASH
Application Name: myApp.exe
Application Version: 3.1.0.98
Application Timestamp: 51d51f8b
Fault Module Name: StackHash_753d
Fault Module Version: 6.1.7600.16385
Fault Module Timestamp: 4a5bd98a
Exception Code: c0000374
Exception Offset: 00008518
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 753d
Additional Information 2: 753d342126021b53e7ba0868794c2464
Additional Information 3: a931
Additional Information 4: a931d4a14b5a731fcf5350897f9ad699
I run a Windows application which suddenly crashes in between since last week.
It shows following error:
Description:
Stopped working
The following Windows Event is logged in the Event Viewer:
Problem signature:
Problem Event Name: APPCRASH
Application Name: abc.exe
Application Version: 1.0.0.0
Application Timestamp: 510fbb25
Fault Module Name: KERNELBASE.dll
Fault Module Version: 6.1.7601.18015
Fault Module Timestamp: 50b8479b
Exception Code: e053534f
Exception Offset: 0000000000009e5d
OS Version: 6.1.7601.2.1.0.274.10
Locale ID: 1033
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
The system OS is Windows Server 2008 R2.
downgrade from .net framework 4.7.2 or 4.8 to 4.6.2
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.