I have recently installed a windows update which only says Security update.
Now when I open my Visual Studio 2010 project I receive an error message saying "Microsoft Visual Studio has stopped working" and here are the other details:
Problem signature:
Problem Event Name: APPCRASH
Application Name: devenv.exe
Application Version: 10.0.30319.1
Application Timestamp: 4ba1fab3
Fault Module Name: fpeditax.dll
Fault Module Version: 10.0.30319.1
Fault Module Timestamp: 4ba20479
Exception Code: c0000005
Exception Offset: 0018b03a
OS Version: 6.1.7601.2.1.0.256.28
Locale ID: 1033
Additional information about the problem:
LCID: 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
Please can anyone assist me with this issue?
Thank you in advance
Really sounds like a .EXE (devenv.exe) or an associated DLL (fpeditax.dll) has become corrupted. You can waste days on trying to figure out which one and why. I recommend you just do a fresh install of VS2010 - will take you a lot less time.
Related
I am facing this issue for last few days. My Visual studio 2015 crashes abruptly.
On checking the application event log, i found that for each crash, following log is entered in it.
Faulting application name: devenv.exe, version: 14.0.24720.0, time stamp: 0x564ea97e
Faulting module name: MSWB7.dll, version: 10.0.14291.1001, time stamp: 0x56e7c254
Exception code: 0xc0000005
Fault offset: 0x0000ed3a
Faulting process id: 0x1224
Faulting application start time: 0x01d18d0ac67af6bd
Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv.exe
Faulting module path: C:\WINDOWS\System32\MSWB7.dll
Report Id: 6a7487d3-693c-4bd1-b48b-9b2262d8b27f
I tried to find about this MSWB7.dll. So far, I have only found out that it is a part of windows system and used as word breaker for the system.
First result on google for "MSWB7.dll" is https://msdn.microsoft.com/en-us/library/gg509108.aspx
My system has Windows 10 with Office 2016. I have all the updates installed for Windows, VS, Office etc.
I am unable to find any solution for this. Had lost quite many hours of work due to it too.
Please Help.
Thanks In Advance...
Uninstall or disable the "Spell Checker" extension, if you have it installed, as it may be responsible.
Doing some Googling I see people are encountering near identical error logs with this extension in VS 2010 and later. It appears this popular extension has become unstable in newer versions of Visual Studio, see Q&A section here:
https://visualstudiogallery.msdn.microsoft.com/7c8341f1-ebac-40c8-92c2-476db8d523ce/view/Reviews
If it's not that extension try disabling other extensions as it appears this kind of crash is often indicative of an extension that becomes incompatible with the newer versions of the IDE.
Visual Studio dies/crashes after resuming from lock Win-L with this error screen. This seems to happen only when docked to dual monitor.
Problem details shows:
Problem signature:
Problem Event Name: APPCRASH
Application Name: devenv.exe
Application Version: 14.0.23107.0
Fault Module Name: StackHash_f6a7
Fault Module Version: 6.3.9600.18007
Exception Code: c0000374
Exception Offset: PCH_1F_FROM_ntdll+0x0003CA2C
OS Version: 6.3.9600.2.0.0.256.48
Locale ID: 1033
What I have:
Windows 8.1
Visual Studio 2013 and 2015
ReSharper 9
Things I have tried:
Run DELL Command Update. Drivers are all up to date.
Upgrade display drivers. All up to date.
Use Visual Studio 2015.
Run as Administrator.
Downgrade NVIDIA driver per this MSFT Ticket. I have an NVIDIA Quadro K1100M. Driver version from 10.18.13.5382 to 348.07 (9.18.13.4807).
Event Viewer. It does not show much info (Below), but it does indicate that the crash happened when I locked, not when I resumed from lock.
Faulting application name: devenv.exe, version: 14.0.23107.0
Faulting module name: ntdll.dll, version: 6.3.9600.18007
Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
I fixed it. Indeed downgrading the video card driver did the trick. Here is exactly the driver I downloaded. I had downgraded twice because I really didn't know which one to pick.
Downgrade driver to 341.61-quadro-grid-desktop-notebook-win8-win7-64bit-international-whql.exe.
In the end, this link helped the most. I wish MS would re-open it. Search for "driver" in the page.
PS: Seems kind of dumb that this question and answer is really not related to coding, but Visual Studio is a pretty commonly used IDE. I only hope this answer helps someone in the future.
Recently, I've installed VS 2015 RC. It uses IntelliTrace in the version 14. Since then I've had a problem with earlier versions of IntelliTrace.
The problem occurs when I try to collect the call information (if I want to collect only diagnostic events there is no problem). Regardless, if I use the Standalone Collector or VS I'm receiving the following error:
Unhandled Exception: System.AccessViolationException: Attempted to read or write
protected memory. This is often an indication that other memory is corrupt.
Re-installation of VS 2015 didn't help. In the event log I see the following list of events (starting from the earliest):
TraceLog Profiler component initialized successfully, process Example.exe
.NET Runtime version 4.0.30319.0 - The profiler was loaded successfully.
Profiler CLSID: '{f1260058-1a1f-4738-8be2-0bf9d3a64219}'. Process ID
(decimal): 7196. Message ID: [0x2507].
TraceLog Profiler in process Example.exe experienced an internal failure.
The accuracy of the collected trace may be affected.
Application: Example.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
Faulting application name: Example.exe, version: 1.0.0.0, time stamp: 0x4ecfa3a5
Faulting module name: Microsoft.IntelliTrace.Profiler.11.0.0.SC.dll, version: 11.0.50522.1, time stamp: 0x4fbadafb
Exception code: 0xc0000005
Fault offset: 0x0000000000040d24
Faulting process id: 0x1c1c
Faulting application start time: 0x01d0ad8432baa357
Faulting application path: C:\Temp\Example.exe
Faulting module path: C:\StandaloneCollector\Microsoft.IntelliTrace.Profiler.11.0.0.SC.dll
Report Id: 709fb3dd-1977-11e5-9c79-240a644a5a8d
Faulting package full name:
Faulting package-relative application ID:
At the beginning everything is ok but then something goes wrong. Example.exe is a console application.
Before VS 2015 RC I had a beta version installed and I didn't spot any problems like that.
I could use IntelliTrace for VS 2015 RC but I'd like to know why other versions don't work. There is probably some conflict. I also wonder why the Standalone Collector was affected. I was sure that it is independent from VS binaries.
Did you experience something similar? Any ideas?
***** EDIT *****
It looks like that I wasn't clear enough. IntelliTrace distributed with VS 2015 (version 14) works correctly. However, earlier versions of IntelliTrace (version 11 and 12) don't work. They stopped working after installing VS 2015 RC.
Thanks for raising the issue.
If you are running an old version of IntelliTrace standalone collector with Visual Studio 2015 installed, this is likely a known issue. The problem is .Net 4.6 will be installed with VS 2015, the old IntelliTrace code will have problem work with the latest version of .Net. The solution I want to suggest would be upgrading your standalone collector to the latest version.
Please let me know if you are still seeing the issue with latest standalone collector and good luck.
You should be able to pick up a copy of the newest standalone collector from your drop of Visual Studio. It can be found in C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\CommonExtensions\Microsoft\IntelliTrace\14.0.0\IntelliTraceCollection.cab
Try using that cab. The problem may have been fixed there.
Visual Studio Express 2013 for Desktop crashes immediately when started. Can someone please help with the issue?
Problem signature:
Problem Event Name: APPCRASH
Application Name: WDExpress.exe
Application Version: 12.0.30110.0
Application Timestamp: 52cfa049
Fault Module Name: clr.dll
Fault Module Version: 4.0.30319.34011
Fault Module Timestamp: 52968a96
Exception Code: c0000005
Exception Offset: 0002122c
OS Version: 6.3.9600.2.0.0.256.48
Locale ID: 1033
Additional Information 1: 782b
Additional Information 2: 782be157f2d91021756bc06173db3dc9
Additional Information 3: 46e5
Additional Information 4: 46e5747e5031a1cc13ede01b86f04375
I think that I have found the problem. The framework version 4.5.1 is the problem. I installed the VS Express version and then removed the Framework 4.5 which seems to have fixed the problem.
I guess its either you didn't install it cleanly else you are trying to install VS 2013 which 64 bit into your 32 bit operating system. The only solution which I think can help you is try compatibility option in the properties.. try running it at windows 7 service pack 1. try hit n trial method..
I have developing in Visual Studio 2010 on the same machine for the past year. Yesterday I installed the Java JDK as well as the Android SDK and since then I cannot run ANY project in Visual Studio. I reveive the following error:
vshost32.exe has stopped working
Problem signature:
Problem Event Name: APPCRASH
Application Name: xxxMyApp.vshost.exe
Application Version: 10.0.30319.1
Application Timestamp: 4ba2084b
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7601.17514
Fault Module Timestamp: 4ce7b96e
Exception Code: c0000008
Exception Offset: 0004708f
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 7177
Additional Information 1: 62c6
Additional Information 2: 62c6367c0a4a7a6a13fec4af66486182
Additional Information 3: b338
Additional Information 4: b338e77b24caadf81f02d002dd08805e
I have tried enabling/disabling the hosting process, have rebuilt, have run registry cleaners, etc.
Has anyone come across something like this before? Any suggestions?
I managed to solve this by uninstalling both JDK and Android, reinstalling VS 2010, and then reinstalling JDK and Android again.
I am none the wiser as to why this long process needed to take place... but it works now...