Develop Reference

Winform Application run on windwos 10 but sending error on windows 7

I have developed a winform application targeting The 4.5 .Net framework , I packed it using advanced installer and then I installed it on several computers run windows 10 , the application is working fine , but when some of my client installed it on windows 7 computer ,when he click to open it an error pop up :
The error window
I know that .Net framework is the one who causing the problem but I want a solution that prevent my intervention on the clients computers .
And here is the details of the error :
CLR20r3
Signature du problème 01: MM Restauration.exe
Signature du problème 02: 1.0.0.0
Signature du problème 03: 5e20f0d8
Signature du problème 04: System.Drawing
Signature du problème 05: 4.7.2558.0
Signature du problème 06: 59d41483
Signature du problème 07: 8ca
Signature du problème 08: 27
Signature du problème 09: System.IO.FileNotFoundException
Version du système: 6.1.7601.2.1.0.256.48
Identificateur de paramètres régionaux: 1036
Information supplémentaire n° 1: 3b3c
Information supplémentaire n° 2: 3b3cffb8c795063b1fa88be1915a2504
Information supplémentaire n° 3: 9fe7
Information supplémentaire n° 4: 9fe705241c4e5c4cc4e9d65dd39fd1f8
Lire notre déclaration de confidentialité en ligne :
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x040c
Si la déclaration de confidentialité en ligne n’est pas disponible, lisez la version hors connexion :
C:\Windows\system32\fr-FR\erofflps.txt

Interpreting Windows Error Reporting ouput

I am trying to track down an error occurring on a target machine running Windows 7 64-bit for a C# WinForms application written in Visual Studio 2008. All I have to go on is the Windows Error Reporting output from the Event Viewer. I found a lot of helpful information here: http://www.codeilove.com/2012/09/debugging-using-windows-error-reporting.html.
Problem signature:
P1: myprogram.exe // filename of the executable
P2: 1.44.0.0 // assembly version for the executable in P1
P3: 560be2df // assembly timestamp for the executable in P1
P4: mscorlib // assembly where the fault occurred
P5: 2.0.0.0 // assembly version for the assembly in P4
P6: 4ca2b889 // assembly timestamp for the assembly in P4
P7: c43 // token for the method where the fault occurred
P8: 59 // IL offset into the method specified in P7
P9: System.FormatException // name of the exception that caused the fault
From the link it appears that P7, P8, and P9 are the most important, and that I should be able to find the method def for "c43" using ILDASM by looking for 06000c43. In C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorlib.dll I find the following in System.Number:
.method /*06000C43*/ assembly hidebysig static
uint64 ParseUInt64(string 'value',
valuetype System.Globalization.NumberStyles/*020003B6*/ options,
class System.Globalization.NumberFormatInfo/*020003B5*/ numfmt) cil managed
Based on this information there is a System.FormatException occurring in System.Number.ParseUInt64, right? I have searched through my project in Visual Studio, and I can't find any instances where my code calls this function. Where do I go from here?
I have a top-level exception handler for Application.ThreadException that logs unhandled exceptions to a file. In this case I am getting an application crash and nothing in my log file. Is it safe to assume this Exception is happening in a thread other than my UI?

Starting with Vista SP1 you can configure Windows Error Reporting to collect local crash dumps. Just set registry settings on the target machine as described in that article and wait till your program crashes again. After that, check the directory that you've configured as DumpFolder. You should find a .dmp file in there. Open it in WinDbg or with Visual Studio and you should be able to see a full stack trace of where the exception happened.

CLR20r3 when running C# app on another PC [duplicate]

I'm trying to decipher the meaning on the P1...P10 parameters associated with a clr20r3 that is written to the event log when my application experiences an exception.
The best I've been able to find is:
P1: the hosting process (e.g. w3wp.exe)
P2: the hosting process version (e.g. 6.0.3790.1830)
P3: ??? (e.g. 42435be1)
P4: the assembly from which the exception was raised (e.g. mrtables.webservice)
P5: the assembly version (e.g. 2.1.2.0)
P6: ??? (e.g. 4682617f)
P7: ??? (e.g. 129)
P8: ??? (e.g. 50)
P9: the exception type raised (e.g. system.argumentexception)
P10: ??? (e.g. NIL)
Googling for clr20r3 provides thousands of sample parameter values, from which someone can try to derive a pattern.
But I'm hoping for documentation on the parameter meanings, as opposed to educated guesses.
Edit: While I can hope for canonical documentation, really I'd be happy to see the exception being thrown, at what line, complete with a stack trace.
Bonus Reading
Unhandled exception that caused the application to crash with "EventType clr20r3, P1 w3wp.exe" in the log, but no details there (asking for help with a problem, while we're asking for a canonical explanation of what the parameters mean)

P7 and P8 are the important ones to find out where the P9 exception was raised. Use P4 to know what assembly to look for. Run ildasm.exe and open that assembly. File + Dump, tick the "Token values" checkbox, OK and save the .il file somewhere.
Open the file in a text editor. P7 gives you the method token, it starts with 0x06, producing token value "06000129". Search for:
.method /*06000129*/
Which gives you the method name, look up from there to find the .class, that gives you the class name.
P8 gives you the IL offset. From the found .method, look for IL_0050 for the instruction that raised the exception. Mapping it back to your source code is a bit tricky but you'll probably figure it out. Use Reflector if necessary.
In general, write an event handler for AppDomain.UnhandledException to avoid the pain of reverse-engineering these Watson crash buckets. Log the value of e.ExceptionObject.ToString() to get both the exception message and a stack trace.

Here is the information on Watson Buckets
Exe File Name
Exe File assembly version number
Exe File Stamp
Exe file full assembly name
Faulting assembly version
Faulting assembly timestamp
Faulting assembly method def
Faulting method IL Offset within the faulting method
Exception type
And also here is a MSDN article on the same.
Sample:
Problem Signature 01: devenv.exe
Problem Signature 02: 11.0.50727.1
Problem Signature 03: 5011ecaa
Problem Signature 04: Microsoft.VisualStudio.SharePoint.Project
Problem Signature 05: 11.0.60226.0
Problem Signature 06: 512c2dba
Problem Signature 07: 18a8
Problem Signature 08: 1d
Problem Signature 09: System.NullReferenceException

windows store app App Verifier failed

windows store app App Verifier failed
-------------------------------------
Problem signature:
Problem Event Name: MoAppCrash
Package Full Name: **************
Application Name: praid:App
Application Version: 1.0.0.0
Application Timestamp: 52d3b719
Fault Module Name: vrfcore.dll
Fault Module Version: 6.2.9200.16384
Fault Module Timestamp: 5010ae28
Exception Code: 4000001f
Exception Offset: 00003355
OS Version: 6.2.9200.2.0.0.256.48
Locale ID: 1033
Additional Information 1: 9d42
Additional Information 2: 9d4286768e3a38f958aebc07f5606189
Additional Information 3: dc25
Additional Information 4: dc25a044c0907dfc8f3ef7768cf61489
I am trying to debug my app using app verifier and I got this error.Anybody know about this?

Finding method def for error signature on Windows XP SP3 PC

I am trying to find the System.dll file to open with ILDASM.exe and find the method definition and offset and see why my application is crashing on Windows XP machines only. Am I trying to open the correct dll for this assembly listed in this error signature? I'm looking in C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\v3.5 at System.Core.dll because it has the System namespace in it when opened by ILDASM.exe.
The same program runs just fine on a windows 7 PC.
I have the following Error signature from attempting to run my application on a Windows XP machine with service pack 3.
Error signature
EventType: clr20r3
P1: myapplication.exe >Is the exe file name
P2: 1.0.0.0 >Is the exe file assembly version number
P3: 51e6a3d8 >Is the exe file stamp
P4: system >Is the faulting assembly full name
P5: 4.0.0.0 >Is the faulting assembly version
P6: 5073c71b >Is the faulting assembly timestamp
P7: 3d57 >Is the faulting assembly method def
P8: bd >Is faulting method IL Offset within the faulting method
P9: system.invalidoperationexception >Exception type that was thrown