Event Viewer Error - .Net Framework v4

[pdoth]

Every single time I boot up (from cold) I get the following error in Event Viewer. It seems to be on a continuous loop repeating approx every 1sec. This goes on for about 5min.

I've read 2 replies to this in other Forums -
1) Don't worry about it, it will go away, probably after a reboot.
2) Re-install .Net Framework v4.

To me the first reply is just nonsense, makes no sense at all. It's obviously reporting for a reason.

Tried the second - no difference, error still shows each and every boot.

Anybody know what is going on and how to correct it?

Log Name: Application
Source: .NET Runtime Optimization Service
Date: 17/04/2012 09:50:05
Event ID: 1101
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: MUS
Description:
.NET Runtime Optimization Service (clr_optimization_v4.0.30319_32) - 1>Failed to compile: System.Xaml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 . Error code = 0x80131f06

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name=".NET Runtime Optimization Service" />
<EventID Qualifiers="0">1101</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-04-17T08:50:05.000000000Z" />
<EventRecordID>39154</EventRecordID>
<Channel>Application</Channel>
<Computer>MUS</Computer>
<Security />
</System>
<EventData>
<Data>.NET Runtime Optimization Service (clr_optimization_v4.0.30319_32) - 1>Failed to compile: System.Xaml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 . Error code = 0x80131f06
</Data>
<Data>System.Xaml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Data>
</EventData>
</Event>

 

[Jacee]

Try to troubleshoot the problem by performing a 'Clean Boot'
How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7

 

[pdoth]

You know, I completely forgot about this facility. I'm gonna try it right now. I only hope that the first piece of advice I read was wrong........ that is, that the problem goes away if the system is re-booted.

Well, here goes everything

 

[pdoth]

This is probably why people refer to computers in human terms, such as............ "it's thinking about it", etc.

I started to use the above technique to find what was causing this issue and, don't ya just know it....... it's stopped doing it. All by it's self. I've done nothing to it, made no changes, and yet, it's not producing the error........ for the moment anyway.

This is what I just do not understand. Why should it do this for about 1 week, every single boot, then, correct it's self?

There's more going on inside this little black box than meets the eye.

Thanks anyway Jacee for the help. I shall remember it next time it goes wrong, which could be any day soon.

 

[Jacee]

You're welcome pdoth Hope there isn't a 'next' time!