Visual Studio 2010 Premium crash with error 4ba1fab3 on opening files in solution
-
Monday, July 26, 2010 10:19 AM
I have a new installation of Windows 7 64-bit with Visual Studio 2010 Premium, both downloaded with my MSDN subscription. I am getting constant crashes trying to open files in my solutions (any file type .cs, aspx, css, etc). Some files do open OK, it seems random on the files it crashes on. I work with two other developers with the same setup, I am the only one getting the problem.
Here's a copy of the error:
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: devenv.exe
Problem Signature 02: 10.0.30319.1
Problem Signature 03: 4ba1fab3
Problem Signature 04: PresentationCore
Problem Signature 05: 4.0.0.0
Problem Signature 06: 4ba1f865
Problem Signature 07: e06
Problem Signature 08: 147
Problem Signature 09: System.IO.FileNotFoundException
OS Version: 6.1.7600.2.0.0.256.4
Locale ID: 2057
Additional information about the problem:
LCID: 1033
I am tried to unintsall VS 2010 and the .NET framework and reinstall, neither helped. I have a mini debug dump of the error which I can upload, but not sure where to..
I'd be grateful for some help with this!
Thank you,
Sharon
All Replies
-
Monday, July 26, 2010 3:43 PM
UPDATE:
We have managed to resolve this issue. In case it's of assistance to anyone else with this error (searching finds other similar issues, but none with a definitive solution).
I did manage to get some further information on the error, which seemed to indicate a problem with font loading, but nothing more specific than that.
Here's what we tried:
- logged on as Administrator in VS safe mode - no change, still crashing
- logged on as another another user - problem fixed
- deleted and recreated my user profile (for domain account) - no change, still crashing
- restarted PC in safe mode - problem fixed
We then did a comparison of installed products with another developer. He had WPF Toolkit February 2010 installed, I did not. I downloaded and installed the WPF Toolkit, restarted machine and the crash went away.
It doesn't make a great deal of sense (at least to me!) why this resolved the problem, or why recreating my user profile didn't work, but it is fixed now and I'm happy !
Hope the update helps someone with the same problem...
- Marked As Answer by SharonWest Monday, July 26, 2010 3:43 PM
- Unmarked As Answer by SharonWest Wednesday, July 28, 2010 2:18 PM
- Marked As Answer by YiChun ChenModerator Friday, July 30, 2010 1:51 AM
-
Tuesday, July 27, 2010 10:27 AMModeratorHi SharonWest,
Thank you for your kindly sharing here!
I'm so glad to hear that your problem is solved. I believe that this will benefit other community members as well.
Have a nice day!
Best regards,
Yichun Chen
MSDN Subscriber Support in Forum
If you have any feedback on our support, please contact msdnmg@microsoft.com
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.- Edited by YiChun ChenModerator Thursday, July 29, 2010 10:31 AM typo
-
Wednesday, July 28, 2010 2:18 PM
Me again...
I think I may have spoken too soon with regard to what fixed the issue. I rebooted my PC this morning, and the problem came back :(
I have managed to work out that booting first into safe mode and then booting into normal mode does fix the problem, at least until I have to reboot again. Not exactly ideal, but I'm kind of putting up with it for the moment, having already lost almost 2 days dev work trying to get working.
Longer term though I'm definitely going to need to try to fix this, so if someone can offer some assistance/guidance, I'd be really grateful.
Thanks,
Sharon
-
Thursday, July 29, 2010 10:30 AMModerator
Hi Sharon,
Thank you for your feedback.
For crash issue, usually, we need to look into the memory dump to know what the cause is.
I would suggest you to use some tool like Procdump to get the dump file of the crash. Then you can report your issue with dump file to MSDN feedback site: http://connect.microsoft.com.
Or you can use Windbg Tool to analyze dump file.
Please see: http://blogs.msdn.com/b/msdnts/archive/2006/11/24/how-to-debug-application-crash-hang-in-production-environment.aspx
Hope this helps. If you have any concern, please feel free to let me know.
Best regards,
Yichun Chen
MSDN Subscriber Support in Forum
If you have any feedback on our support, please contact msdnmg@microsoft.com
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.- Edited by YiChun ChenModerator Thursday, July 29, 2010 10:31 AM typo
- Marked As Answer by YiChun ChenModerator Friday, July 30, 2010 1:51 AM
-
Thursday, July 29, 2010 11:57 AMThanks YiChun, I'll get that dump file created and will report to the connect website. If/when I get any feedback on the cause, I'll report back.
-
Friday, July 30, 2010 1:51 AMModeratorHi Sharon,
Thank you for your help.
I've marked your and my reply as answer here temporarily since this will benefit other community members who have similar concern as you. They can follow the suggestions in your and my reply to have a try.
It would be great if you can also paste the link to the submitted feedback here, so that other community members can see it as well.
If you need any further help, please feel free to let me know. I'm willing to help you on that!
Look forward to your good news.
Best regards,
Yichun Chen
MSDN Subscriber Support in Forum
If you have any feedback on our support, please contact msdnmg@microsoft.com
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.- Edited by YiChun ChenModerator Friday, July 30, 2010 1:53 AM typo
-
Monday, March 07, 2011 2:43 PM

