No trace of my driver in stack trace

Hi all,

I have started getting BSODs in my FS filter driver. But the BSODs are
such that if i do a stack trace then there is no trace of my driver in it.
Also every time I try to generate the bug, I get different error codes.

How can I find the problem area?

Regards.

Hi,

Do you use the driver verifier to determine the problem? It can be that the
driver verifier can find a problem before the stack gets eaten up by a
faulty process. The driver verifier can be found in the DDK. Make sure to
use the latest debugger 4.0.0018 in combination with serial debugging. The
command !analyze -v is very usefull to get more info on the BSOD.

grtx Marco.

At 12:07 AM 2/28/2002 -0500, xxxxx@hotmail.com wrote:

Hi all,

I have started getting BSODs in my FS filter driver. But the BSODs are
such that if i do a stack trace then there is no trace of my driver in it.
Also every time I try to generate the bug, I get different error codes.

How can I find the problem area?

Regards.


You are currently subscribed to windbg as: xxxxx@thunderstore.com
To unsubscribe send a blank email to %%email.unsub%%

Ain’t it lovely , this kernel mode work we all do? You spend hours, days
even, chasing down evil little critters that you know you created, even
though there is no direct evidence linking them back to you … well, other
than the old reliable “remove my driver and it don’t crash no more” litmus
test.

This evil little critter sounds remarkably like a synchronization bug.
Specifically, you are completing, or causing to complete, an IRP that has a
reference on a queue, and which controls some sort of memory. When other
elements of the system attempt to access the items controlled by that IRP,
which has already been completed, all kinds of nasty little things happen
… and that wicked wicked driver that caused all this crumbling and
tumbling is no where to be seen.


Gary G. Little
xxxxx@broadstor.com
xxxxx@inland.net

wrote in message news:xxxxx@windbg…
>
> Hi all,
>
> I have started getting BSODs in my FS filter driver. But the BSODs are
> such that if i do a stack trace then there is no trace of my driver in it.
> Also every time I try to generate the bug, I get different error codes.
>
> How can I find the problem area?
>
> Regards.
>
>