Skip to content

Latest commit

 

History

History
141 lines (95 loc) · 5.32 KB

ns-wdm-_kbugcheck_secondary_dump_data_ex.md

File metadata and controls

141 lines (95 loc) · 5.32 KB
UID title description tech.root ms.date keywords ms.keywords req.header req.include-header req.target-type req.target-min-winverclnt req.target-min-winversvr req.kmdf-ver req.umdf-ver req.lib req.dll req.ddi-compliance req.unicode-ansi req.max-support req.typenames targetos f1_keywords topic_type api_type api_location api_name
NS:wdm._KBUGCHECK_SECONDARY_DUMP_DATA_EX
_KBUGCHECK_SECONDARY_DUMP_DATA_EX
Learn more about: _KBUGCHECK_SECONDARY_DUMP_DATA_EX structure
devtest
06/03/2019
KBUGCHECK_SECONDARY_DUMP_DATA_EX structure
KBUGCHECK_SECONDARY_DUMP_DATA_EX, KBUGCHECK_SECONDARY_DUMP_DATA_EX, *PKBUGCHECK_SECONDARY_DUMP_DATA_EX,
wdm.h
KBUGCHECK_SECONDARY_DUMP_DATA_EX, *PKBUGCHECK_SECONDARY_DUMP_DATA_EX
Windows
_KBUGCHECK_SECONDARY_DUMP_DATA_EX
wdm/_KBUGCHECK_SECONDARY_DUMP_DATA_EX
PKBUGCHECK_SECONDARY_DUMP_DATA_EX
wdm/PKBUGCHECK_SECONDARY_DUMP_DATA_EX
KBUGCHECK_SECONDARY_DUMP_DATA_EX
wdm/KBUGCHECK_SECONDARY_DUMP_DATA_EX
apiref
HeaderDef
wdm.h
_KBUGCHECK_SECONDARY_DUMP_DATA_EX
PKBUGCHECK_SECONDARY_DUMP_DATA_EX
KBUGCHECK_SECONDARY_DUMP_DATA_EX

_KBUGCHECK_SECONDARY_DUMP_DATA_EX structure

-description

The KBUGCHECK_SECONDARY_DUMP_DATA_EX structure describes multipart data to be written by KBUGCHECK_REASON_CALLBACK_ROUTINE callback routine to the crash dump file.

-struct-fields

-field InBuffer

Pointer to a buffer that is allocated by the system.

-field InBufferLength

Specifies the size of the buffer, in bytes, specified by the InBuffer member.

-field MaximumAllowed

Specifies the maximum amount of data that the KBUGCHECK_REASON_CALLBACK_ROUTINE routine can write to the crash dump file.

-field Guid

Specifies a GUID that identifies the driver's crash dump data. (Drivers must use unique GUIDs to mark their crash dump data. Use the GuidGen.exe tool to generate GUIDs for your driver.

-field OutBuffer

Pointer to the buffer where the driver writes its crash dump data, or NULL.

-field OutBufferLength

Specifies the size of the buffer, in bytes, that was specified by the OutBuffer member.

-field Context

Contains private context data for the exclusive use of the callback routine. The callback routine can set this member to any value. Typically, if the callback routine needs to be called more than one time, the routine sets this member to point to a driver-supplied buffer during the initial call. During subsequent calls, the callback routine can read the previous contents of this buffer and update its contents. Before the initial call to the callback routine, Context is NULL.

-field Flags

Contains flags that describe the add-page request. The callback routine must set the value of this member. Set this member to the bitwise OR of one or more of the following flag bits:

KB_ADD_PAGES_FLAG_VIRTUAL_ADDRESS

Indicates that the Address member contains a virtual address.

KB_ADD_PAGES_FLAG_PHYSICAL_ADDRESS

Indicates that the Address member contains a physical address.

KB_ADD_PAGES_FLAG_ADDITIONAL_RANGES_EXIST

Indicates that the callback routine requests that it be called again so that it can add more pages.

The callback routine must set either the KB_ADD_PAGES_FLAG_VIRTUAL_ADDRESS flag or the KB_ADD_PAGES_FLAG_PHYSICAL_ADDRESS flag, but not both. On entry to the callback routine, Flags is initialized to zero.

-field DumpType

One of the following dump types.

    DUMP_TYPE_INVALID           = -1,
    DUMP_TYPE_UNKNOWN           = 0,
    DUMP_TYPE_FULL              = 1,
    DUMP_TYPE_SUMMARY           = 2,
    DUMP_TYPE_HEADER            = 3,
    DUMP_TYPE_TRIAGE            = 4,
    DUMP_TYPE_BITMAP_FULL       = 5,
    DUMP_TYPE_BITMAP_KERNEL     = 6,
    DUMP_TYPE_AUTOMATIC         = 7

-field BugCheckCode

Contains a bug check code, which specifies the reason for the bug check. The callback routine can use this information to decide whether to add any pages to the crash dump file. For a full list of bug check codes, see the Bugcodes.h header file included in the WDK.

-field BugCheckParameter1

Bug Check Parameter 1. The bug check parameters inform the callback the bugcheck parameters that were passed to KeBugcheckEx.

-field BugCheckParameter2

Bug Check Parameter 2. The bug check parameters inform the callback the bugcheck parameters that were passed to KeBugcheckEx.

-field BugCheckParameter3

Bug Check Parameter 3. The bug check parameters inform the callback the bugcheck parameters that were passed to KeBugcheckEx.

-field BugCheckParameter4

Bug Check Parameter 4. The bug check parameters inform the callback the bugcheck parameters that were passed to KeBugcheckEx.

-remarks

For more information about bug check callback routines, see Writing a Bug Check Callback Routine.

-see-also

Writing a Bug Check Callback Routine. KBUGCHECK_REASON_CALLBACK_ROUTINE