Forum

Results 1 to 13 of 13

Hybrid View

  1. #1
    Join Date
    December 2009
    Location
    Czech Republic
    Posts
    2

    Bsod

    Hi,
    I tried to use TS3 client in WinXP 32bit with Sound Blaster Live! 5.1 soundcard (driver version: 3516.0.0.0). Client causes BSOD instantly after starting of sound capture (when I connect to a server or when I perform voice test).

    The error is BAD_POOL_CALLER and first parameter is 0x41.

    Tried to use DirectSound and Windows Multimedia. Both with the same result.

    Any other application (including ts2) which uses sound capture never caused BSOD on my system.

    Does anybody have same problem, or... better... solution? Thanks in advance.

  2. #2
    Join Date
    December 2009
    Location
    stuttgart
    Posts
    1
    the same probleme here

    Sound Blaster Live! 5.1 PCI
    windows xp 32

  3. #3
    Join Date
    December 2009
    Location
    Germany
    Posts
    3
    Same problem on my second PC.

    Win XP 32Bit SP2 with SoundBlaster Live!

  4. #4
    Join Date
    October 2006
    Posts
    64
    Normally BSOD's occur from faulty ram or bad drivers. I'd suggest that you make sure everything is up to date on your computers and maybe run some memory scans.

  5. #5
    Join Date
    December 2009
    Location
    Czech Republic
    Posts
    2
    It is obviously a driver issue. The problem is that Live! 5.1 is an older soundcard and I have installed probably the most recent drivers available. On the other hand, other applications work correctly so it could be caused by something specific in ts3's sound system. I would like to know if is there any chance that it will be fixed or that any workaround can be found.

    New soundcard is the last option

  6. #6
    Join Date
    October 2006
    Posts
    64
    You could try taking out your soundcard and running TS3 without one and see if it still crashes.

  7. #7
    Join Date
    March 2010
    Location
    Germany
    Posts
    1

    TS3 crashes (bluescreen)

    Hi there,
    i don't know if it's allowed to post in german so i post it in english.
    I have problems connecting to TS3 servers, every time i try to connect to a server a bluescreen appears and my comp is restarting. The funny thing is i'm able to connect to a TS3 server if i'm connected to a TS2 server at the same time. I don't really know what could cause this.

    I'm on Win Xp with a Soundblaster Live 5.1 Soundcard (newest drivers), and using TS3 ver. 3.0.0-beta17..

    I would appreciate it if someone could help me out

  8. #8
    Join Date
    April 2008
    Location
    Next to Hannover
    Posts
    212
    hello,
    can you make a picture from your bluescreen?
    I need the code that you can see under the texte.
    one of them is:
    "Driver IRQL Not less or equal"

    have you a other? show me

  9. #9
    Join Date
    March 2010
    Location
    Poland, Gdańsk
    Posts
    1
    Hi there, I have the same problem. My pc get BSoD when i click connect to server or microphone test.
    Here are my numbers, maybe you can help me.

    BAD_POOL_CALLER

    STOP 0x000000C2 (0x00000041, 0x88641000, 0x00008641, 0x000CFEDF)

    Sound card : Sound Blaster Live 5.1 Digital (SB0100)
    System: Windows XP SP3

  10. #10
    Join Date
    April 2010
    Location
    Bend, Oregon
    Posts
    2

    Computer Reboots

    Any time I try to initialize the Microphone on TS3 my computer will reboot. I am using a Soundblaster 512 ( yes i know it is an old card, but I have never had a problem with it till now) and the drivers are up to date. While doing the setup mic test or attempting to connect to a server it reboots my computer. Is there a fix for this or do I have to get a new soundcard to be able to use TS3?

  11. #11
    Join Date
    February 2006
    Location
    Texas, USA
    Posts
    4,143
    Are you certain your mic/sound card are causing the problem? Have you tried changing your capture device in the TS client?

  12. #12
    Join Date
    April 2010
    Location
    Bend, Oregon
    Posts
    2
    Pretty sure it is the sound device causing the issue. When I get back into windows after the reboot windows asks me to send an error report and informs me that it was my sound device that caused the fault.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •