Hello,

I have some trouble when playing sound files with Windows Media Player or Media Monkey. When I play music there are very short interruptions. What could be causing this?

My system has 4GB RAM, an Athlon X2 and Soundblaster Audigy soundcard. It runs Windows XP

Thank you.

where are the sound files located !

Well I found the problem: it was the microsoft indexing service. I disabled indexing for all harddrives, and then I opened services.msc and disabled the indexing service.

Well I did some closer examination of my system. The sound interruptions are not fixed and they aren't really sound interruptions at all. In fact the entire system freezes for just a few moments. What I managed to figure out was that there are some spikes in the CPU-usage when the hick-ups happen: two things called DPCs and Interrupts give a spike.

Disabling the indexing service didn't help and nor did reversing to Windows XP SP2.

wanna scatter you brain a bit ,it did mine .
advanced dcp's.
http://technet.microsoft.com/en-ca/s.../bb963898.aspx

The soundcard should be placed in the furtherest slot away from the cpu.

Creative SoundBlaster Audigy Audio may cause an error message. Describes how to work around this problem by setting Creative SoundBlaster Audigy Audio to be the default Sound Playback device.
http://support.microsoft.com/kb/319595

God bless you jupiter 2,
How do the error messages described in kb/319595 have anything to do with the posters problem?

"Ctplay2.exe has encountered a problem and needs to close. We are sorry for the inconvenience.

Eacontrol.exe has encountered a problem and needs to close. We are sorry for the inconvenience.

SoundBlaster card needs to be installed."

Well given the questionable quality of your usual "advice" offerings, you might want to pull your head in. There is actually some merit to his line of thought....

The OP has listed having 4GB of RAM installed - meaning that is his Windows installation is going to actually be capable of using all that, he is using XP x64. The biggest problem this OS has always had is that many manufacturers never released more than buggy HW drivers for that OS version.... Creative being leader of that rather ugly pack.

In Win7 x64, MS has finally taken the initiative, rolling out a large number of generic drivers to fill that void, thus making the transition to x64 Windows much easier.... this was never the case with XP x64, and likely will remain that way.

Another line of thought is this:
Given the high-end (and quite modern) specifications of his machine, it is highly likely that he has either bought a system designed for Vista and downgraded it to XP - not a good idea by the way - or has built a system with parts not fully supported by XP. Either way, a migration to Win7 would be a better alternative, and would likely solve the problems he is encountering. Either that, or swap out offending hardware (such as the sound card) for devices which were indeed designed for the XP environ.

Ok kaninelupus,
There is no need to use that sort of language in an open forum. I was being nice to Jupiter 2 and pointing out that the site he has given clearly states that if when you install a Creative Audigy sound card you may get an error message... Copied from site "After you install a Creative Audigy sound card and software, you may receive any of the following error messages:
Ctplay2.exe has encountered a problem and needs to close. We are sorry for the inconvenience.

Eacontrol.exe has encountered a problem and needs to close. We are sorry for the inconvenience.

SoundBlaster card needs to be installed.
If you view the data that the error report contains, the following error signature information is listed:"

Now the poster is not getting any error message like that and therefore, no mater what train of thought he (jupiter 2) may have, it is not about getting these error messages. For you to jump to his defense is very admirable. You being such a busy teacher, with exams and all, but it would be good if you could show how the error messages are relevant, because I have no idea, and that is why we have open forums, so we all can learn from others with more knowledge like you. So I am asking you nicely, please explain the error messages in relation to the posters problem of his sound having "very short interruptions"
I have learned something from you already, I did not know that there were systems and components that were too advance for the proper functioning caperbilities of XP.

It is not a case of being "to advanced for XP". It is a case of many recent components not being supported for XP... ie, manufacturers/designers not providing any XP-based drivers for their wares. Yes Vista/Win7 provide hardware-based options which were only at conception form at the time of XP's delivery - CPU-GPU collaboration, hybrid HDD's (ie, turbo caching), many of the hardware accelerations found post-XP.

The simple fact is this; yes some hardware is incompatible with XP solely on the basis that the relevant manufacturer saw no compelling reason to continue to support that OS in their hardware offerings, but also true is the fact that other recent hardware offerings move beyond the capabilities of what XP is capable of supporting.