Home Dashboard Directory Help
Search

.NET Runtime Optimization Service interrupted by event ID 1108 & continual windows exclamation sounds by 8A361077-648C-48A8-A960-096CAB3D2F2A


Status: 

Closed
 as External Help for as External


0
0
Sign in
to vote
Type: Bug
ID: 181926
Opened: 8/17/2006 3:31:50 AM
Access Restriction: Public
Duplicates: 181927
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

HI All,

I hope you can help me before we all go insane. I have two PC's, one with XP home and the other with XP pro. Both are loaded with Office 2003 pro and are part of a home network. Both emit the windows exclamation sound throughout the work day. The window sounds are set to default on both PC's.

The event viewer shows that .NET Runtime Optimization Service is running at the time of the sound and that it has been interrupted (event id 1108). The description is:- .NET Runtime Optimization Service (clr_optimization_v2.0.50727_32)- Service work was interrupted due to the following reason(s): USER_INTERRUPT (Mask: 0x04). The ngen_service.log confirms this.

I have no idea what ngen or .NET Framework 2.0 does, I just want it to do it quietly. Can you help before I go crazy ;-)

Regards, BooBoo_UK

P.S. Please don't tell me its by design. That does not help & reflects badly on the designer.
Details
Sign in to post a comment.
Posted by Microsoft on 9/6/2006 at 2:47 PM
Thanks for contacting us about this issue! Why do you think the sound is caused by event 1108?

The best way to debug this is:
Start->Control Panel->Sound and Audio Devices
Click on sounds tab
Track down which sound you are hearing. Disable it one event at a time until you find the one at fault.

One interesting candidate is "Open program". By default there is no sound associated with this, but if you override the default you will hear the sound for each new process creation (generally happens frequently in Windows, in particular once per worker process created by the NGen Service).

Ori Gershony

Please let us know what you find.

Thanks!
Sign in to post a workaround.