.dll 'ghost' In The P3D Machine

[darthranger 1]

I also posted this in The CTD Forum in hopes of finding an answer...

 

I have been running P3D V2 exclusively for some time now, and all was well until recently...

 

P3D has started to CTD about 10 minutes into a flight.

 

Faulting module: clr.dll, version 4.030319

Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.319\clr.dll

Faulting application path: D:\Lockheed Martin\P3Dv2\P3d.exe

 

P3D forum says this is NOT a P3D issue, but rather a Microsoft issue.

 

Microsoft Support says:   "Faulting Module name clr.dll when you run .NET Framework based application"

 

"CAUSE:  The issue occurs because an object that is being referenced is dereferenced by the collector in common language runtime 4 (CLR4).  Therefore, an access violation occurs during garbage collection or when the application tries to access the released object"

 

I'm hoping someone here that has more computer 'Savy' than me can explain what the heck they're talking about... and/or how to fix this.  

 

P.S.  Microsoft says that there was a Hotfix for this in 2011...  but I would think that was dalt with in updates. 

        (I have .NET Framework 4.5.1 installed)

 

Rick / Canada

[denali 74]

http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx

[darthranger 1]

Thanks for the pointer !

[Richard Sennett 2,499]

Thanks for the pointer !

 

Are you overclocking - a bad overclock will give you all kinds of misleading errors - happened to me - after I got a stable OC I never had a crash again in P3D - its rock solid so dont look at P3D - cant say that for fsx that's a whole different animal that's for sure all set with that adios FSX

[darthranger 1]

No... not overclocking, but thanks for the response !