TS 2 RC1 (Bluescreen)

Cocomoe · #1 27-08-2002, 07:03

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.

Makull · #2 27-08-2002, 19:10

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 · #3 28-08-2002, 03: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

Cocomoe · #4 28-08-2002, 04:21

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.

Makull · #5 28-08-2002, 10:12

Same thing here. Uninstalled, redownloaded the client. After installation I immediately get a blue screen on starting the client :
MULTIPLE_IRP_COMPLETE_REQUESTS

Makull · #6 28-08-2002, 10:38

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.

Cocomoe · #7 28-08-2002, 15:01

Yeah, it did _not_ need to install any of the codex.

Gearbone · #8 28-08-2002, 15: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???

Makull · #9 29-08-2002, 09:41

*BUMP* Come on TS support!!

Solitaire · #10 29-08-2002, 10: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.

Makull · #11 29-08-2002, 12:43

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.

Cocomoe · #12 29-08-2002, 17:05

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

Cocomoe · #13 29-08-2002, 18:54

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 · #14 29-08-2002, 19: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 · #15 29-08-2002, 22: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