Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results

More Info on Driver Writing and Debugging


The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.


Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/


Before Posting...

Please check out the Community Guidelines in the Announcements and Administration Category.

No trace of my driver in stack trace

OSR_Community_UserOSR_Community_User Member Posts: 110,217
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.

Comments

  • OSR_Community_UserOSR_Community_User Member Posts: 110,217
    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, [email protected] 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: [email protected]
    >To unsubscribe send a blank email to %%email.unsub%%
  • OSR_Community_UserOSR_Community_User Member Posts: 110,217
    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
    [email protected]
    [email protected]

    wrote in message news:[email protected]
    >
    > 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.
    >
    >
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. Sign in or register to get started.

Upcoming OSR Seminars
OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!
Writing WDF Drivers 24 January 2022 Live, Online
Internals & Software Drivers 7 February 2022 Live, Online
Kernel Debugging 21 March 2022 Live, Online
Developing Minifilters 23 May 2022 Live, Online