Help - Search - Members - Calendar
Full Version: crash under windows 2003?
Hydrogenaudio Forums > Hosted Forums > foobar2000 > Support - (fb2k)
cacko
is there somebody else experience crashes on windows server 2003 while using foobar2003 ?

my pc crashed several times when using foobar 0.667, i switched to 666 and for two days no crash.
carmen
0.667 is working well on windows2003 here. in fact i just switched over because winamp 2.91 is running into serious problems, it won't even launch properly at this point...previously i was able to get it to launch by removing MAD and mp3cue.... good luck!
Canar
QUOTE(cacko @ Jun 9 2003 - 07:52 AM)
is there somebody else experience crashes on windows server 2003 while using foobar2003 ?

my pc crashed several times when using foobar 0.667, i switched to 666 and for two days no crash.

Delete it and re-install. That may fix your problem. I ran fb2k on 2003, and it was rock-solid.
cacko
the problem is with kxproject drivers for sblive, but only foobar crashes them that's why i posted this. it for sure that kxdrivers cause some problems but it's for sure that foobar causes too. i will be glad if i can help the developers with some debug build if they send me.
Garf
QUOTE(cacko @ Jun 10 2003 - 12:15 AM)
the problem is with kxproject drivers for sblive, but only foobar crashes them that's why i posted this. it for sure that kxdrivers cause some problems but it's for sure that foobar causes too. i will be glad if i can help the developers with some debug build if they send me.

It's not because foobar is the only program that crashes with the drivers that it's necessarily foobars fault. Since you're the only one seeing the crashes, the conclusion should be rather obvious. Dump the broken drivers.
TrNSZ
Windows Server 2003 is extremely picky about drivers.

I was reading two different WinS-2003 reviews and both of them noted that they experienced BSOD/crashing of audio related software when testing. I know they tested Wa2/Wa3/CP and one reviewer I e-mailed tested Foobar2000 and they all had the same issues, which were later resovled by a driver update from the sound card manufacturer in one case.

The other reviewer, who was using some Yamaha sound card, never had his system stable until he removed the Yamaha drivers and went without sound - as soon as he did this, all the crashes stopped and there weren't any more BSODs; and that Yamaha driver (made for 2K/XP) was the only third party driver that had been installed.

Take special care when installing third-part drivers on WS2K3 - just because they seem to work doesn't mean they work fully or correctly. Wait until all your hardware is properly supported before upgrading to Windows Server 2003.
cacko
QUOTE(Garf @ Jun 9 2003 - 02:32 PM)
QUOTE(cacko @ Jun 10 2003 - 12:15 AM)
the problem is with kxproject drivers for sblive, but only foobar crashes them that's why i posted this. it for sure that kxdrivers cause some problems but it's for sure that foobar causes too. i will be glad if i can help the developers with some debug build if they send me.

It's not because foobar is the only program that crashes with the drivers that it's necessarily foobars fault. Since you're the only one seeing the crashes, the conclusion should be rather obvious. Dump the broken drivers.

oh thank you very much.
RIV@NVX
I used Windows Server 2003 + kX Drivers + foobar2000 0.667 and no problems.

(except that all HW acceleration needed to be set to max)
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2008 Invision Power Services, Inc.