Windows 7 program "has stopped working"

Question

0.00/5 (No votes)

See more:

Hello,

I am developing a C# application using Visual Studio 2008. The development is using Windows XP SP 3.

My problem is with the generic "has stopped working" window that comes up in Windows 7; the one that does not offer any information! I tried using the Compatibility Wizard or whatever, but that report's "details" is the application name and development platform.

I think there may be an obscure missing DLL somewhere, and had it been Windows XP I would know exactly which one.

Does anyone know of a way to figure this out?

Thanks,
Adam

Posted 12-Jul-10 6:17am

ahiggins1986

Add a Solution

3 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

LNogueira · Answer 1 · 2010-07-12T06:30:00

Solution 1

I think your exception is being buried somewhere inside your code.
You need to raise it in order to get more information about what's happening.

Please take a look here.[^]

Posted 12-Jul-10 6:30am

LNogueira

Comments

ahiggins1986 12-Jul-10 13:16pm

No, my program doesn't even begin to run when the error occurs. I added in an Application.ThreadException event to no avail.

LNogueira · Answer 2 · 2010-07-12T11:33:00

Solution 2

Have you tried changing the default debugger [^], automatically launch the debugger[^] or even remote debugging to help you get more information on what in happening?

Posted 12-Jul-10 11:33am

LNogueira

Christian Graus · Answer 3 · 2010-07-12T11:45:00

This happened to me, and it's because my main thread stopped for a moment, while the system loaded some videos. It's really a bug in Windows 7, in my opinion, the app works fine sometimes, and other times does not, but it works fine on every other OS. Try to figure out if your app takes a while to do something on startup ( in my case, it was a WPF databinding command that takes a while to finish ) and see if you can make the process more manual, so that Win7 recognises that your process is working.