Member Avatar for bhagawatshinde

Hi guys,
I am trouble to find out the solution can anybody help me,
I am developing an windows application in 2.0 framework in vs2005 and making exe but on some operating system (Windows7 service pack1 64 bit Home premium, windows xp service pack 3) it throws an error while double clicking on exe "Windows has stopped working"


Thanks in advance....

  • 2 Contributors
  • 3 Replies
  • 112 Views
  • 9 Hours Discussion Span
  • Latest Post Latest Post by skatamatic

Dani AI

Generated

As suggested, start by getting facts instead of guessing. Crashes that happen only on some machines are usually caused by one of: a native dependency or VC++ runtime that is missing or the wrong bitness, an assembly-binding failure, DEP/UAC/antivirus interaction, or an unhandled exception during static initialization. The immediate goal is to capture the faulting module and a stack trace so you can tell managed vs native failure.

Check the Windows Application log (Event Viewer) for the Error recorded at the crash time and copy the fields: Faulting application name, Faulting module name, Exception code and Fault offset. Windows Error Reporting docs explain what those entries mean: Windows Error Reporting.

If the event log is not enough, capture a user-mode crash dump and open it in Visual Studio or WinDbg to see the stack. Sysinternals ProcDump is the usual tool; see the docs and examples here: ProcDump. For assembly-binding failures enable the Fusion log viewer to capture load failures: Fuslogvw - Assembly Binding Log Viewer.

Typical quick checks: verify native DLL bitness with a dependency tool and install the appropriate Visual C++ Redistributable for any native components (VC++ redistributables). Run the app from an elevated command prompt or under a debugger/VM to reproduce; temporarily disable third-party AV/DEP for testing. When asking for more help, paste the exact Event Viewer error text, the faulting module name/exception code, and a dump or call stack — that information lets helpers identify whether it’s bitness, missing runtime, managed Exception, or native access violation.

Recommended Answers

All 3 Replies

Member Avatar for skatamatic

Was it compiled for a x86 architecture or a 64 bit one?
What assemblies are you referencing in it?
What does the program do? (Some relevant code maybe)

There's quite a bit of possible problems... We need to know a bit more about the application and how it was compiled.

Member Avatar for bhagawatshinde

It was compiled for a x86 architecture, also i have added all the assemblies in package.

Member Avatar for skatamatic

Try compiling it for Any architecture or compile it seperately for 64 bit systems. And ensure that the included assemblies are compatible with a 64 bit architecture as well.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.