Dealing with .Net Runtime Errors

.NET Framework is a software framework from Microsoft that is used for building and executing applications and services based on .Net technology.

The .Net Framework consists of three major components – ASP.Net, the Common Language Runtime, and the Framework Class Library. Since their introduction, Microsoft has released several versions of .Net frameworks.

.Net Runtime Error

While working on your Windows computer and using applications based on .Net frameworks, you may come across different .Net runtime errors. A couple of .net runtime errors and their solutions are discussed below.

.Net Framework 2.0 Error

A .NET framework 2.0 application may crash when it is run under a user account context that is not associated with any user profile. When this happens, an access violation error message may also appear on your computer screen.

Error Message

When the above problem occurs in a Microsoft .Net Framework application, error messages, similar to the ones displayed below are added to the event log.

Error Message 1

“Event ID : 1023
Raw Event ID : 1023
Record Nr. : 14
Category : None
Source : .NET Runtime
Message : NET Runtime version 2.0.50727.42 – Fatal Execution Engine Error (7A05E2B3) (80131506)”

Error Message 2

“Event ID : 1000
Raw Event ID : 1000
Record Nr. : 15
Category : None
Source : .NET Runtime 2.0
Error Reporting Type : Error
Message : Faulting application w3wp.exe, version 6.0.3790.1830, stamp 42435be1, faulting module mscorwks.dll, version 2.0.50727.42, stamp 4333e7ec, debug? 0, fault address 0x000e9f96.”

Note: The first error message is usually followed by the second error message.


Microsoft has released a hotfix for the above problem. You can download it from the Microsoft website and install it on your computer to repair the errors.

Notes: This hotfix applies only to this specific problem. Do not download the hotfix if your problem is different than the one discussed above. Also, to apply the above hotfix, you need to have Net Framework 2.0 installed on your computer.  You will need to restart your system after you apply the hotfix.

.Net Framework 3.5 Error

An exception occurs on a computer which has .Net Framework 3.5 Service Pack 1 installed when an application calls either the GetOptionalCustomModifiers or the GetRequiredCustomModifiers method on a ParameterInfo object of a generic interface.

Error Message

The following error message is displayed when the above issue occurs:

“An unhandled exception of type ‘System.ExecutionEngineException’ occurred in mscorlib.dll”

The above error also logs event ID 1023 in the application log. The event reads similar to the text listed below:

“.NET Runtime version 2.0.50727.3053 – Fatal Execution Engine Error (734E7706) (80131506)”
You may also find Event ID 1000 logged in the Application log, which reads similar to the text displayed below:

“Faulting application ConsoleApplication1.exe, version, time stamp 0x48dce3f5, faulting module mscorwks.dll, version 2.0.50727.3053, time stamp 0x4889dc18, exception code 0xc0000005, fault offset 0x0002d2b5, process id 0x%9, application start time 0x%10”


To fix this .net runtime error, you can download a hotfix from the Microsoft website.

Note: The above hotfix applies only to this specific problem. Also, ensure .Net Framework 3.5 SP1 is installed on the PC on which you are applying this hotfix. Restart your system after applying the above hotfix.

Runtime errors may also frequently occur if your system is infected with malware. To prevent malware, such as virus, worms, and trojans from breaching your system’s security and disrupt the way system and other important files function, install a reliable and advanced malware tool such as Spyware Cease on your computer.

You may also experience various runtime errors if invalid, corrupt, and obsolete entries creep into your system registry. Maintain a clean and health registry by scheduling regular registry scans and cleanup using an efficient registry cleaning utility, such as RegServe.