Prev: Check .NET Framework exists from managed assembly
Next: Passing URI Parameters to WPF App Affecting Deployment
From: James Lamanna on 11 Dec 2007 16:59 Hi, A couple of users have been getting this same .NET Runtime 2.0 error from an app that I have written, and I haven't been able to diagnose or debug the problem: Faulting application.....faulting module kernel32.dll version 5.1.2600.3119 stamp 46239bd5 debug? 0, fault address 0x00012a5b. Any help would be greatly appreciated. Thanks. -- James
From: Kerem G�mr�kc� on 11 Dec 2007 23:14 Hi James, without a callstack, some code and knowing what is going on there before this instruction at this address has been executed, it is impossible to tell what this error exactly means. You need to attach a debugger at this point and go down the callstack to see what instruction/operation made this "fault" exception appear,... Do you Pinvoke, read/write to raw app memory? Do you have any native code pinvoking from .NET? Do you use hooking methods? We need more Information about your application,... Regards Kerem -- ----------------------- Beste Gr�sse / Best regards / Votre bien devoue Kerem G�mr�kc� Microsoft Live Space: http://kerem-g.spaces.live.com/ Latest Open-Source Projects: http://entwicklung.junetz.de ----------------------- "This reply is provided as is, without warranty express or implied."
From: Michael Nemtsev [MVP] on 12 Dec 2007 07:33 Hello James, just to add to previous post make sure that u have all latest .NET SP installed coz very rare it can be .NET FW bug :) --- WBR, Michael Nemtsev [.NET/C# MVP] :: blog: http://spaces.live.com/laflour "The greatest danger for most of us is not that our aim is too high and we miss it, but that it is too low and we reach it" (c) Michelangelo JL> Hi, JL> A couple of users have been getting this same .NET Runtime 2.0 error JL> from an app that I have written, and I haven't been able to diagnose JL> or debug the problem: JL> Faulting application.....faulting module kernel32.dll version JL> 5.1.2600.3119 stamp 46239bd5 debug? 0, fault address 0x00012a5b. JL> JL> Any help would be greatly appreciated. JL> JL> Thanks. JL>
From: James Lamanna on 12 Dec 2007 18:51
Hi, Unfortunately I haven't been able to reproduce this error on any of my systems, this only occurs on a couple of client machines. I do use P/Invoke in some places. I guess I'll keep trying to duplicate the error here so I can get a debugger on it. Thanks. -- James On Dec 12, 4:33 am, Michael Nemtsev [MVP] <nemt...(a)msn.com> wrote: > Hello James, > > just to add to previous post make sure that u have all latest .NET SP installed > > coz very rare it can be .NET FW bug :) > > --- > WBR, > Michael Nemtsev [.NET/C# MVP] :: blog:http://spaces.live.com/laflour > > "The greatest danger for most of us is not that our aim is too high and we > miss it, but that it is too low and we reach it" (c) Michelangelo > > JL> Hi, > JL> A couple of users have been getting this same .NET Runtime 2.0 error > JL> from an app that I have written, and I haven't been able to diagnose > JL> or debug the problem: > JL> Faulting application.....faulting module kernel32.dll version > JL> 5.1.2600.3119 stamp 46239bd5 debug? 0, fault address 0x00012a5b. > JL> > JL> Any help would be greatly appreciated. > JL> > JL> Thanks. > JL> |