Catching a BugCheck near its beginning

NTDEV
1

With .NET Microsoft has changed the bug check callback,
so that drivers that register for this are called after the dump is
written. I have two questions on this:

  1. Is there still a way to take information off your device,
    and record it in the dump?

  2. I have a system with an external watchdog timer, in the
    past I coul use the callback to turn off the timer so the
    dump would complete. Now I have the problem that
    the system is externally rebooted before completing
    the dump, since I have no way to indicate that the dump
    (a slow operation) is occuring to the external device. Is
    there a way around this?

Don Burn
Egenera, Inc.

2

You need to talk to Microsoft about this. There are solutions. I have no
idea what the ‘final’ plans are for the new dump interface, but they are
aware of the issues.

===========================
Mark Roddy
Consultant, Microsoft DDK MVP
Hollis Technology Solutions
xxxxx@hollistech.com
www.hollistech.com
603-321-1032

-----Original Message-----
From: “Don Burn”
To: “NT Developers Interest List”
Date: Thu, 26 Sep 2002 08:00:29 -0400
Subject: [ntdev] Catching a BugCheck near its beginning

> With .NET Microsoft has changed the bug check callback,
> so that drivers that register for this are called after the dump is
> written. I have two questions on this:
>
> 1. Is there still a way to take information off your device,
> and record it in the dump?
>
> 2. I have a system with an external watchdog timer, in the
> past I coul use the callback to turn off the timer so the
> dump would complete. Now I have the problem that
> the system is externally rebooted before completing
> the dump, since I have no way to indicate that the dump
> (a slow operation) is occuring to the external device. Is
> there a way around this?
>
> Don Burn
> Egenera, Inc.
>
>
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@hollistech.com
> To unsubscribe send a blank email to %%email.unsub%%