View Full Version : TS 2 RC1 (Bluescreen)
TeamSpeak version: 2 rc1
Operation System + Service packs: XP Pro (ALL UPDATES)
Soundcard + Driver versions:Auditgy Gamer / 5.12.010134
DirectX Version: 8.1
What error message you receive?
blue screen of death, multiple_irp_requetss
Does this error happen always?
Yes, soon as I try to execute the client, even in windows compatibility mode.
What did you do to receive this problem?:
Reinstalled my drivers. Checked my bios settings, and currently combing the net for info on that error. Redownloaded and reinstalled teamspeak, ran dxdiag.
I have EXACTLY the same problem. Installed the client, doubleclicked on the icon and POOOF my computers reboots. Every time...... Did you guys beta test this thing?
WinXP Pro (all updates)
SoundBlaster Live LiveDriverPack (23/07/02)
DirectX 8.1
Just a normal install of the RC1 client... It didn't install any codecs (it said it already found them on my system).
Gearbone
28-08-2002, 02:12
I have a squad mate that had THE same problem.
Here is what he did and now is working fine.
UNINSTALL TS 2.0, RE Download, DONT use the same one, delete the .exe you downloaded, and try again from a different source.
Reload it again and try. Worked for him
hope it helps
Still no go, got the latest sound card drivers, downloaded another copy with my vscan off. And installed it.
Still Blue screen.
multiple_irp_complete_requests.
Same thing here. Uninstalled, redownloaded the client. After installation I immediately get a blue screen on starting the client :
MULTIPLE_IRP_COMPLETE_REQUESTS
I might have found something interesting....
Cocomoe, when you installed the client for the first time did it install any codecs on your system? It didn't on mine because it said it already found all of them (which I think where installed by the program SoundForge which I am using). On my other system, when I installed the client (also running WinXP, without soundforge) it said it couldn't find any of the codecs and installed them all, and then the client worked.
TS Support is there a way to tell the clientinstall to overwrite the existing codecs? I have a feeling that the versions that are installed on my system are causing the reboot of the computer.
Yeah, it did _not_ need to install any of the codex.
Gearbone
28-08-2002, 14:49
Running XP here and I got the message DID NOT INSTALL any codecs and its running fine on my machine No special sound programs just updated drivers like normal.
Still, your idea is a good one. If we could force the codecs to install even if they dont need it, it might stop an incompatibilty
TS support???
*BUMP* Come on TS support!!
Solitaire
29-08-2002, 09:03
it is not a TS 2.0 issue, it is a driver issue following lines are quotes from MS
Cause
This behavior can occur because a driver has requested (by using the IoCompleteRequest function) that an I/O request packet (IRP) needs to be completed, but the packet has already been completed.
Resolution
To resolve this behavior, contact the vendor of the driver and request an update for the driver.
<end of quote>
now this is uncommon for a sound driver to cause this error. more than likely your sound drivers have become corrupted. what you need to do is download the drivers again and uninstall your current drivers reboot and then install the drivers you freshly downloaded do not use the old drivers you dl'ed in the past as this will do nothing. also do not install the driver over the top of the old one as this more than likely will not cure your problem.
Okay, first of all... I did try downloading the drivers again and reinstalling them but to no avail.. still the same blue screen...
and I DO think this is a TS 2 issue.. it does not happen with TS 1 or ANY other program I use....
And also.. look in the forum.. more and more people are reporting the EXACT same thing... are you going to tell us that on all of these systems the drivers are corrupt?? I hope not....
The error description of MS is probably correct.. but the problem is more then likely then the way TS 2 interacts with these drivers then the driver itself.
Solitare did you even read what was done so far.
I still get that error.
I've downloaded FRESH copies my my soundcard driver amd installed it. I've even went back to an older copy, just in case, no go. (I'm back to running the latest audigy drivers.)
I've done the same for TS2. (Downloaded fresh from diffrent sites.)
How is it TS1/RW/BC/others and everything else I want to play does not have that issue (MOHAA/NWN/RTCW/Medevil:totalwar/others).
Though I appreciate your response to this issue, blind loyalty to 1 product is not needed, I just want help to get it to work, so I can get jamming again. Do you have any other suggestions?
Driver update: Creative Labs Audigy / 5.12.01.0253
OS: XP Pro/ Latest updates as of 8-29
Ok I did a system roll back to a few months ago, didn't work. (System abck to where it was previous post)
Short of reformating, I am stumped.
Solitaire
29-08-2002, 18:31
trouble shooting and fixing windows systems can be well troublesome at times. I recently had a friend that when he played certain games that use directx for graphics his video would run smooth for 2 seconds and then freeze for 2 and repeat that over and over. he could play openGL games just fine. we tried to reinstall vid drivers and directx (even tried directx 9 beta) of course but to no avail. we ended up reinstallling the os over the top of it so he wouldnt lose any data off his hd. in that instance you are saying its the game causing the issue and not directx? whether it was an api that called the directx api's and thus it was not replaced on a reinstall of directx or not, im not sure, but it was a directx issue. I am by no stretch of the imagination saying TS 2.0 is perfect or anything even close. what i am saying is that BSOD is a known error to people that work in the IT/IS profession. it is very annoying and sometimes a hard problem to resolve, the 3 times i have run across that error in my professional career it happened with adobe acrobat, scanner software, and i forget the 3rd app but it was the system that was in an "unhealthy" state and not the software package.
N. Werensteijn
29-08-2002, 21:13
BSOD are an ultimate failure of the os to handle an error, usualy hardware related.
Most common reasons why a BSOD pops up:
1: Bad driver software.
2: Failing hardware.
When a user program crashes windows so hard, a BSOD pops up, ms has made some big errors. Normal user programs should not be able to BSOD an os.
Therefore, with all BSOD that occur while using TS, i blame the soundcard drivers first :)
Well the drivers I am using is the LiveDriverPack released 23 July 2002. And these drivers solved a LOT of problems I had with the SBLive under Windows XP.
The drivers work fine for TS 1 and any other application I work with. TS 2 is the only application I ever tried to use that gives me this error (or any problem with those drivers for that matter).
But I see where this is heading off too... I guess you don't read the rest of the forum and have seen that we are not the only ones with these problems.. oh well...
just looking on the main page, I already found two other people with the same problems as us :
http://forum.teamspeak.org/showthread.php?s=&threadid=1073
and
http://forum.teamspeak.org/showthread.php?s=&threadid=1064
Are you still saying that we all have driver problems when all other programs work just fine?
N. Werensteijn
30-08-2002, 00:24
Yes :)
Again: BSOD's should NOT be able to be invoked by user programs :)
IF you are using Realtime priority, it is possible that your pc is having a hard time with ts2, but still BSOD is not an option.
Ts calls the same driver api's for all soundcards. So when it works for most and not for others, is mostly a driver problem.
IF you are having this problem, only when you are using realtime priority, try the file from my posting on this page:
http://www.teamspeak.org/forums/showthread.php?s=&threadid=918&pagenumber=2
Replaced soundcard and drivers still same error. (I work for a retailer so it was simple enuff to do.)
As you say should not, BUT not unheard of. And can you explain why EVERYTHING else from rogerwilco, teamsound, battlecomm work without issues .
On top of all my games have no issues either.
I'm not the onlyone in my group with problems with this software.
I would suggest again reading what was done so far, so far only original suggestion has been to replace the sound card.
Ok, for shit's and giggles. I just ran the teamspeak executable on it's own.
Of course missing DLL's, etc. Strange thing is once it was done erroring, it loaded even got the list of servers, of course I could not connect to any.
Least it's not BSOD or IRP error. Wonder if it's possible the codex that teamspeak wants to use.
Originally posted by N. Werensteijn
IF you are using Realtime priority, it is possible that your pc is having a hard time with ts2, but still BSOD is not an option.
Ts calls the same driver api's for all soundcards. So when it works for most and not for others, is mostly a driver problem.
I don't think you understand the problem we are having.. what realtime priority? I just doubleclick on the ts2 exe file and the system reboots.. that's it.. No window, no option.. nada.. the first thing I see the computer doing when I start TS 2 is my system counting the memory banks again...
I still think it's due to the codecs... read the first few posts.. if there is a way for forcefully install the codecs we could clear this up..
I have yet to get TS2 working on my XP pro. Its a new computer in May and I had no problems with TS1.5. I hope this problem gets fixed soon. Our squad uses TS2 for WW2 online. I have the same crash with the multiple_IRP_Requests error. No driver files were updated before the TS2 install so how could the sound drivers be corupted? THX
N. Werensteijn
30-08-2002, 21:51
ok try this
http://www.teamspeak.org/files/TeamSpeak_patch15.zip
unzip it over the RC1 client and see if it wil start now
WOOHOOO!!!! I CONNECTED NO BSOD< NO IRP ERROR!!!!!!!
N. Werensteijn
30-08-2002, 22:28
:)
N. Werensteijn
31-08-2002, 04:57
Could you please test this version?
See if it BSOD of you?
http://www.teamspeak.org/files/TeamSpeak_patch17.zip
BSOD - the IRP error.
I feel blue, blue, blue monday. Dropped back to 15.
N. Werensteijn
31-08-2002, 05:14
OK..
The culperate is gamevoice hardware support, altough it could be a general USB hardware problem.
What USB hard ware is connected to your pc if i may ask?
NP.
I use a NEC based USB 2.0 Controller, made by Buslink
Logitech Wingman Extreme Force Feedback joystick.
Canon C755 printer.
Microsoft Optical Wheel Mouse.
That's all my use devices.
N. Werensteijn
31-08-2002, 06:46
well..
Ill rewrite the code so the gv is not initialized by default.
meanwhile, u can try to see if there are new drivers for those 4 devices. I stronly suspect one of those drivers has a BIG BUG.
OK,
I updated my joystick, and my mouse driver. My printer is current.
My mouse driver actually is a older version than the stiock one that comes with WINXP. But it's the current one fore that specific mouse.
Loaded up that .17 patch and no blue screen, so you were right one of them had a bug. But like an idiot I did install one then the other to tell you which one was bad. All I can say is both were the 'stock' drivers that WINXP supplied.
Cocomoe
I have two USB devices connected to my computer, a printer with updated drivers and (the same as Cocomoe) a Logitech Wingman Extreme Force Feedback joystick, which uses the standard drivers that were supplied with Windows XP.
I've downloaded and installed the latest drivers for it (4.20) and after that copied the .17 build over the old teamspeak.exe file. There is no blue screen now and everything seems to work okay.
Thanks a lot
siegfried
08-09-2002, 01:18
Thanks a lot for finding the bug with the USB drivers! Indeed, I can confirm that it is a bug with the default M$ drivers for Logitech USB game controllers. I had the same problem, the BSOD, and just installed the Logitech drivers for my wheel, Wingman Formula Force, and no more BSOD, with the patch 17. Maybe want to add this to the FAQ for easy reading.
BigRedBrent
10-09-2002, 11:46
My computer has many of the same problems. My computer reboots when trying to run this new teamspeak. It is very anoying. I don't think this is a problem with so many computers. This must be a problem with the program. This is a bug that needs to be fixed. Do not just tell us that our computers are not perfectly set up so your program will not work on them. This can not be the problem. There is somthing this program does that is the root of this problem. I am not a programer but there must be some way to fix this bug. I have not had this problem with any audio program I have ever used and probobly (other than this program) never will again. PS I just read the new messages and I as well have the USB Logitech Wingman Extreme Force Feedback joystick, which uses the standard drivers that were supplied with Windows XP. I will look into this....... I installed the newest drivers for the Logitech Wingman Extreme Force Feedback joystick and the client worked. But the server will not work if I lock the computer, even if I set the server as a system service.
vBulletin® v3.7.0, Copyright ©2000-2008, Jelsoft Enterprises Ltd.