I have a filter driver for the ScsiPort driver that is
working on 99% of the hosts I connect it to. But, Our
test group has found the one that is killing me. This
is only occuring with my windows NT 4.0 driver. Host
is Windows NT 4.0 sp6a with all hotfixes released on
MS www site.
Host works fine without my driver installed. When
my driver is installed I can see that I have compeleted
my Driver Entry successfull and filtered the ScsiPort#s
of interest to me. There are no outstanding IRPs on
for my driver based on !irpfind information. I also have
a SystemThread that acts as a watchdog it’s firing like
clock work.
The problem seems to be that the host never even gets
to the point of starting the winlogon service.
Digging through the !process 0 1 or 0 7, plus individual
!thread information hasn’t pointed out anything too straight
foward. !locks tends to show a couple help but now are mine.
I’m not sure what to start looking at next. Any suggestions
would be very helpful. Thanks! -dcw
Do a !stacks 2 and spend a while poring over every stack trace to see if
anything looks amiss. But it looks like you’ve done this and haven’t
found anything obvious. Next step is to successively reduce the
functionality of your filter until the hang stops occuring (just comment
out code). This will quickly help you narrow down the suspect code. If
you’ve gotten your driver as simple as possible and the hang still
occurs, there may something buggy about how you’re doing your filtering;
the SCSI guys on the ntdev list would be able to help you here.
xxxxx@weibeltech.com wrote:
I have a filter driver for the ScsiPort driver that is
working on 99% of the hosts I connect it to. But, Our
test group has found the one that is killing me. This
is only occuring with my windows NT 4.0 driver. Host
is Windows NT 4.0 sp6a with all hotfixes released on
MS www site.
Host works fine without my driver installed. When
my driver is installed I can see that I have compeleted
my Driver Entry successfull and filtered the ScsiPort#s
of interest to me. There are no outstanding IRPs on
for my driver based on !irpfind information. I also have
a SystemThread that acts as a watchdog it’s firing like
clock work.
The problem seems to be that the host never even gets
to the point of starting the winlogon service.
Digging through the !process 0 1 or 0 7, plus individual
!thread information hasn’t pointed out anything too straight
foward. !locks tends to show a couple help but now are mine.
I’m not sure what to start looking at next. Any suggestions
would be very helpful. Thanks! -dcw
You are currently subscribed to windbg as: xxxxx@nryan.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
–