From - Fri Sep 12 15:05:03 1997 Path: news.mitre.org!blanket.mitre.org!philabs!newsjunkie.ans.net!newsfeeds.ans.net!portc02.blue.aol.com!pitt.edu!dsinc!spool.mu.edu!uwm.edu!vixen.cso.uiuc.edu!news-peer.sprintlink.net!news.sprintlink.net!Sprint!worldnet.att.net!newsadm From: "Eric van Tassell" Newsgroups: comp.os.ms-windows.programmer.nt.kernel-mode Subject: Re: MULTIPLE_IRP_COMPLETE_REQUESTS Date: Fri, 12 Sep 1997 13:40:38 -0500 Organization: AT&T WorldNet Services Lines: 22 Message-ID: <5vbus4$m2l@bgtnsc03.worldnet.att.net> References: <34103CF4.42CB@networktools.com> <1997Sep5.121549.8135@cmkrnl> NNTP-Posting-Host: 207.116.210.146 X-Newsreader: Microsoft Outlook Express 4.71.1008.3 X-MimeOle: Produced By Microsoft MimeOLE Engine V4.71.1008.3 An equally simple but perhaps a tad more helpful answer (if you have SoftICE) and is to break in @IofCompleteRequest when the afflicted irp goes by. This will allow you to get a stack trace and shed a little light on why - you already know what is happening. The incantation (assuming Irp = 0xdeadbeef) is: bpx @IofCompleteRequest if ecx == 0xdeadbeef HTH -evt Jamie Hanrahan wrote in article <1997Sep5.121549.8135@cmkrnl>... > >In article <34103CF4.42CB@networktools.com>, David Huang writes: >Simple - IoCompleteRequest has been called more than once for the same >IRP.