Memory issues with .NET 2.0 on x64 machines

So there have been a few issues we have seen with .NET 2.0 when it is running on large 64-bit machines that have a lot of memory.  This is commonly seen if the machine in question has at least 4GB of RAM per CPU.  So like 32 GB of RAM with 8 processors.

There are a few issues that have been addressed around this situation.  There has been a hotfix to address one issue:

But now we have released SP1 and that has even more fixes that address this situation.  To get more info on where to get SP1, check out my previous posting on this: .NET Framework 2.0 SP1 has released

With my most recent customer that has this problem, we saw that as memory increased to a higher level, we saw a great deal of paging even though there was enough physical memory to hold the data.  We saw the page file jump up to about 20 GB even though we had enough RAM to handle the growth.  We also saw the # Induced GC's increase.  All of these fixes are included in SP1.

So if you are using .NET 2.0 on a x64 machine, I would strongly recommend upgrading to SP1.

Comments (4)

  1. Phillip Klatt says:

    After installing .Net 2.0 SP1 x64, I am seeing an event log error ".NET Runtime Optimization Service (clr_optimization_v2.0.50727_32)-Failed to compile: Microsoft ReportingServices.QueryDesigners, Version= …

    What is the significance of this error? The error references the clr_optimization_v2.0.50727_32 but not the _64 version?. Any ideas about this?

  2. This error is telling you that the ngen failed for this file.  If you use Reporting Services, you may want to try to NGen the file yourself.  Otherwise I’d just ignore it.  For information on NGen, check out:

  3. Leonard says:

    Any suggestions on how to fix this?

    .NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) – Failed to compile: C:Program FilesPC Drivers HeadquartersDriver DetectiveDriverHQ.DriverDetective.Client.exe . Error code = 0x80131047

Skip to main content