foobar2000 Tech Support Forum Rules

Please read foobar2000 Tech Support Forum Rules before posting and comply with all the points.Failure to provide all the information pointed out in the above document in your post is considered wasting other people's time and in extreme cases will lead to your topic getting locked without a reply.

Foobar2000 has a bug! Reasons:1. System is clean - installed it a week ago and Antivirus scanned.2. All the drivers are installed correctly (compatible with Windows 8).3. Other applications that use the hard drive works fine (e.g. utorrent, aimp).4. Foobar is clean - fresh installation.5. The hard drive works fine - scanned the hd tune, no bad sectors.6. Actions copy / paste on the hard drive work fine.7. The last most important reason - I tested today at a friend's foobar and it is this error (also has Windows 8 x64).

No other application does not cause this error, so the conclusion is simple: FOOBAR HAS THIS BUG.

if i were you, i'll start be remove all the extra plugins, and just test foobar2000 alone. If you still have you problem, you'll be able to say it's a foobar2000 problem, otherwize, it could be a plugin! add plugins one by one by testing between each new add, you sould find in time which plugin sucks (if it's not foobar2000 core of course)

if i were you, i'll start be remove all the extra plugins, and just test foobar2000 alone. If you still have you problem, you'll be able to say it's a foobar2000 problem, otherwize, it could be a plugin! add plugins one by one by testing between each new add, you sould find in time which plugin sucks (if it's not foobar2000 core of course)

HTH

I know... The computer I have over 10 years... Of course, I tested a clean foobar (with default plugins, no dsp) - in my computer and friend computer (the tests lasted 5 hours). The same bug on Windows 8 x64.If you are interested, we listened to this http://img821.imageshack.us/img821/931/schowek01cn.jpg

Preliminary conclusions: foobar choking on a few (10-15) long wav files (over 20 minutes). You have to listen to about 2 - 3 hours.Process Explorer shows the same as the system - increased disk activity by foobar.Continuing tests... Peter will help finally?

You also said you tried with a fresh installation and you had the same problem, did the "fresh installation" included your components and DSPs? Can you try to run the same test without the mslive component?

You also said you tried with a fresh installation and you had the same problem, did the "fresh installation" included your components and DSPs? Can you try to run the same test without the mslive component?

CorrectionThis happens only with long wav files - after 2-4 hours. I listen to music a long time - foobar is enabled all day. But I have to continue testing.As I wrote above. The problem has only foobar. Other applications work fine e.g. AIMP. The whole system works fine and reliably.