How to reslove wpf clr issue

Question

1.00/5 (1 vote)

See more:

Hello All,
I have created a wpf application in vs2010. it runs in my system correctly but when i run it into different system it gives below error:

Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: Game.exe
Problem Signature 02: 1.0.0.0
Problem Signature 03: 52efe810
Problem Signature 04: PresentationFramework
Problem Signature 05: 4.0.0.0
Problem Signature 06: 4ba1f8db
Problem Signature 07: 78ff
Problem Signature 08: 0
Problem Signature 09: System.Windows.Markup.XamlParse
OS Version: 6.1.7600.2.0.0.256.4
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Please help me to resolve this.

Thanks,

Posted 3-Feb-14 8:25am

User-8621695

Add a Solution

Comments

Sergey Alexandrovich Kryukov 3-Feb-14 15:11pm

That is pretty amazing. Do you really think that staring at this output makes any sense without seeing your code?
—SA

User-8621695 3-Feb-14 15:43pm

But code is working and it's setup is also works in same system and many of other systems but few of systems throw this error.

Sergey Alexandrovich Kryukov 3-Feb-14 16:04pm

Okay, if you don't want to prepare and share some code sample, don't. But then, how can you expect any help?
Good luck,
—SA

1 solution

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)

Pete O'Hanlon · Answer 1 · 2014-02-03T09:19:00

Solution 1

The easiest way to diagnose this is to incorporate Windows Error Reporting. You need to convert this crash dump into a richer format. You might find this[^] helpful.

Posted 3-Feb-14 9:19am

Pete O'Hanlon