What is the bugcheck info, stack?

Bryan S. Burgin
bburgin@microsoft.com

This posting is provided "AS IS" with no warranties, and confers no rights.

Bryan,
Should I post the stack here or you want me to send it your email address?

--
Naveen K Kohli
http://www.netomatix.com
""Bryan S. Burgin [MSFT]"" <bburgin@online.microsoft.com> wrote in message
news:NUrNUgNbDHA.304@cpmsftngxa06.phx.gbl...

I am debugging my own filter driver. But before I can even start my driver,
the system bug checks because of this issue. One thing I have noticed is
that filter will not crash unless debugger gets attached to the target
computer through null modem cable.
I am using sysmserver for symbol download. So I Am assuming that I already
have the latest symbols on my host machine.

--
Naveen K Kohli
http://www.netomatix.com
""Bryan S. Burgin [MSFT]"" <bburgin@online.microsoft.com> wrote in message
news:yX664NObDHA.460@cpmsftngxa06.phx.gbl...

Check your code when you indicate status up -- the binding context is
probably NULL.

Bryan S. Burgin
bburgin@microsoft.com

This posting is provided "AS IS" with no warranties, and confers no rights.

As I mentioned earlier, there is no issue with my driver. It works
perfectly. All of a sudden packet scheduler will crash. So now the only way
I can debug is by not connecting my PC to network. Otherwise my machine will
not survive for more than 5 minutes.

--
Naveen K Kohli
http://www.netomatix.com
"James Antognini" <antognini@mindspring.nospam.com> wrote in message
news:3F4E217B.44DDFA0E@mindspring.nospam.com...

Does the problem occur if your driver has not been loaded? If it does not, the
first possibility to investigate is that the problem starts in your driver. I'd
start investigating by running ndistest with your driver.

Naveen K Kohli wrote:

--
If replying by e-mail, please remove "nospam." from the address.

James Antognini
Windows DDK MVP

I checked the source for psched!ClStatusIndication. It gets called when a
miniport calls NdisMIndicateStatus. I didn't resolve the offset 0xb
(psched!ClStatusIndication+b) to a specific line; however, early in the
code it uses the binding context it is passed as a pointer to its own
adapter structure and reads from a member of that structure. Not sure is
that member is at offset 0x238 of that structure, but it might be -- and
with the d1 error indicating a address read of 0x00000238, I suspected that
something is calling NdisMIndicateStatus with a NULL binding context.

Also, a miniport would normally call NdisMIndicateStatus when the network
cable is pulled to indicate its change of state. The problem isn't in
psched, just getting reported there. The problem is in the stack below
psched.

Bryan S. Burgin
bburgin@microsoft.com

This posting is provided "AS IS" with no warranties, and confers no rights.

Here is one more piece of information. Packer scheduler driver is the only
one that reports that it took 10+ seconds to load. On average it is taking
8-10s to load this driver. I don't know if this info is of any help.

--
Naveen K Kohli
http://www.netomatix.com
""Bryan S. Burgin [MSFT]"" <bburgin@online.microsoft.com> wrote in message
news:gNCArnabDHA.2108@cpmsftngxa06.phx.gbl...

Naveen,
Debugger is asking you to do analyze -v. Did you do it and if you did what
was the output? What is the full stack trace? (the output of kb)

Just to be sure:
1- You have a system that suddenly crashes with stack showing psched even if
you never ever install your filter driver on it. correct? i.e. if you clean
install OS on this system, it will crash after a few minutes, right !? (This
is at least what you are implying)

2- It always crashes in the same spot, correct?

In general, unexpected crashes in components other than the one you are
testing is the result of memory corruption caused by the new driver. Memory
corruptions sometimes could take a while to show up and then they will show
up in unexpected places. -Make sure- you are running with driver verifier
enabled.

-ali

--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Naveen K Kohli" <naveenkohli@hotmail.com> wrote in message
news:%23yTcsuibDHA.2672@tk2msftngp13.phx.gbl...