W2K BSOD "STOP MULTIPLE IRP COMPLETE REQUESTS"

[MichaelD]

I'm getting this BSOD way too much. Anyone know what's going on? I usually get it as I'm clicking closed multiple windows, with diff proggies running.

 

[NogginBoink]

A driver is attempting to complete an IRP (I/O Request Packet) that has already been completed.

Suspect antivirus drivers, disk defrag drivers, disk quota drivers, network drivers, any driver that wedges itself into the filesystem or networking stack, and start uninstalling those.

If it was working fine before and isn't now, determine which driver(s) were installed between then and now.

I've searched my resources and there are many many drivers that are known to cause this problem.

I'd start by going to Windows Update and updating drivers there.

-Noggin

 

[MichaelD]

Hi Noggin. Cool nik, BTW. Noggin'Bonk..LOL!

Thanks for the info. Good Lord, that's quite a list! Here's what's interesting. These probs are happening on a fresh install of W2K, on a new mobo/CPU. My previous setup was Athlon/Via Mobo and so is my new setup. I'm using the same vidcard, same HDs same NIC and same soundcard. And the same drivers.

What HAS changed is that Microsoft came out with some kind of new "hotfix patch" or some crap like that. I DL'd and installed it off the W2K update page. I wonder if that is causing my probs? I've gone to the Update page and there's nothing new for me to DL....maybe I'll look at the drivers page and see what I can see.

Traditionally, I avoid MS's device drivers like the plague; I feel much more comfortable using the manufacturer's drivers; i.e. NVidia/Creative/Netgear, etc.

Thanks for pointing me in the right direction.

 

[NogginBoink]

<< Traditionally, I avoid MS's device drivers like the plague; I feel much more comfortable using the manufacturer's drivers; i.e. NVidia/Creative/Netgear, etc. >>


This shows how little experience you have with device driver issues on NT platforms.